Oblique Task

An Oblique Task processes oblique images so they can be visualized in the VC Map.

To select an Oblique Task from the task list, a valid license key is required. This key must be entered by an administrator in the General Settings of the VC Publisher.
However, existing oblique data sources and layers can be added to the VC Map without a license key.

Step 1

Option Description

Task Name

Name of the task.

Create or overwrite Datasource

Select whether to create a new datasource or overwrite an existing one

Datasource Name

If an existing data source is to be overwritten, select the source here.

Step 2

In this step, you must define the information required to convert the oblique aerial images. The minimum required parameters are immediately visible in the settings. The optional parameters can be found under “Advanced Settings.” The following section describes the minimum required information:

Settings Description

Main directory of the oblique aerial images

Specifies the main directory in which the oblique aerial images are located. These may also be organized into subfolders. The supported image formats are JPEG, PNG and TIFF. It is sufficient to specify only the directory. Specifying the file type is not required! !! IMPORTANT !! All images should be oriented “horizon-up” by default; otherwise, the images will be displayed as they are actually oriented. The converter does not apply any rotation to the images.

Directory of the project file

Directory of the project file from Inpho Match-AT. This PRJ is an additional file and is not related to the project description of a shapefile! It describes the aerotriangulation for each processed image. Important parameters for computing the image transformation are derived from this file. These include the interior and exterior orientation, focal length, and lens distortion of the cameras used. Here, the file including its extension must be specified.

EPSG code

Indicates the coordinate reference system of the image datasets as an EPSG code.

Proj4 string

The coordinate reference system (international CRS) in PROJ.4 definition. For example, such a definition for WGS84 / UTM Zone 32N is: "+proj=utm +zone=32 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0,0 +units=m +no_defs". The appropriate definition of the respective coordinate system can be found, among other sources, using the website https://epsg.io/. Clicking the button “Retrieve Proj4 String” sends a request to https://epsg.io/ and inserts the Proj4 string directly into the corresponding field.

Footprint data type

Selection of whether the footprints are provided as GeoJSON or Shapefile.

Directory of footprint(s) (Shapefile or GeoJSON file) (comma-separated)

Specifies the footprints. The file including the file extension (.geojson/.shp) must be provided. The footprints may be listed in one or multiple files. If multiple files are provided, please separate them with commas.

Attribute in the footprint data that represents the image name

Indicates the column name in the footprint file that represents the image names in the footprint data. The image name must be provided without a file extension.

The following section describes the advanced settings. These settings are optional. If no values are entered in the fields, the default parameters will be used:

Settings Description

JPEG quality

Level of JPEG compression. A value of 100 represents the lowest possible compression / highest quality achievable using the JPEG format. Accordingly, 0 represents the highest possible compression and therefore the lowest image quality. At a quality level of 80, the resulting image file size is roughly half the size compared to quality 100.

Interpolation algorithm

Various interpolation methods for downscaling the input image are available in the drop-down menu: "nearest", "cubic", "mitchell", "lanczos2", "lanczos3". The Lanczos filter is considered the most balanced option in terms of compression capability and image quality for resampling. "lanczos3" is selected by default.

Number of threads

Number of simultaneously allowed operations. More threads allow the converter to use more of the computer’s resources during the tiling process. By default, four threads are executed simultaneously.

Tile images

Optionally, the tiling of images can be disabled. This can be useful, for example, if only the image.json needs to be recalculated in an existing project, but the tiling process should not be triggered again. By deselecting both "Tile images" and "Generate metadata", data processing can be completely disabled, in which case only statistical information about the aggregated dataset from footprint and project file is written to a log file.

Write metadata (image.json)

Optionally, generating the metadata file (image.json) can be disabled. This makes it possible to perform only the image tiling if no metadata needs to be written. By deselecting both "Tile images" and "Generate metadata", data processing is completely disabled, and only statistical information about the aggregated dataset from footprint and project file is written to a log file.

Logging

Selection of whether the footprints are provided as GeoJSON or Shapefile.

Additional optional parameters

--inputImages: Allows referencing an additional directory besides the main directory of the oblique images. Example: --inputImages \\pc227\H\platte3\Bilddaten

--overwriteFalsy: If a previous oblique imagery job ended prematurely, this option processes only the images that were not fully processed in the previous run.

--overwriteAll: All images are reprocessed, and all tiles in the output folder are overwritten.

--tileSize: Allows defining the tile size (width = height in pixels). A pixel value between 2 and 4096 is permitted, provided it is a power of two. The default tile size is 1024 pixels.

--addRotation: This setting allows rotating images on disk afterwards if they do not meet the “horizon-up” requirement. Please note that this setting only rotates the image tiles; any additional adjustment of metadata within the project file does not occur. How to adjust metadata for subsequent image rotations is described in detail in the chapter “Adjusting incorrectly oriented oblique images.” Example:

--addRotation "Camera_a,-90" --addRotation "Camera_b,90" --addRotation "Camera_c,180".

Step 3

Option Description

Start Job as soon as possible

Start the job immediately.

Start Job once at given time

Schedule job for a future time.

Repeat Job

Automatic periodic execution of the job.

Publish Job after Completion

Once conversion is successful, the datasource is published automatically.