This page describes the supported resources for Orbit Oblique solutions, any combination of the listed resources can be used.

Two important notes before diving into the details :

Orbit imports oblique data using intelligent templates. An import template is configured according a well known set of configurations and available data.
The use of templates simplifies and standardizes the import procedure.

Generic Import
The default website download includes some generic import templates.
The specifications and data structure can be viewed here : Prepare Oblique Data for Generic Import.

Customize Import
In addition on the available templates the Orbit engine offers all configuration possibilities to customize and optimize the import for using any kind of oblique data. Once the configuration is known, it can be added as new import template to extremely simplify all future imports.
Please contact the Orbit support team (support at orbitgt dot com) for more information or to create your customized template.

Orbit supports any combination of oblique data and any coordinate system on import. But be wise :

• The coordinate reference system should be part of the metadata of each resource.
• It is advised that all georeferenced resources are using the same CRS to avoid processing time of continuous coordinate transformation. If required convert CRS on import run.
• When converting the coordinate system of image positions apply the according adjustments on all orientation angles referring the reference direction of the coordinate systems (most probably north).

• Imagery
  • Image files
  • Positions and Orientations
    • Absolute positions and orientations at time of recording
    • Relative position and orientation
  • Camera calibration
  • Image Metadata
• DTM
• Reference data

There are no limitations on the number of oblique cameras.
One camera import requires one set of images and one positions and orientations file.

Supported formats
Preferably .jpg files.
But any supported image resource can be used.

Supported types
Orbit supports any distorted picture, independently of file size or pixel resolution.

The absolute position and orientations at time of recording of all images must be available unambiguously.
Two possibilities :

• absolute position and orientation for each camera at time of recording
• combining the absolute position and orientation of a reference frame at time of recording with the fixed relative position and orientation for each camera to this reference frame (aka lever arm corrections).

Supported formats
Preferably .txt or .csv file.
But any supported point vector resource can be used.

Specifications

• One EO text file for each camera containing at least the below described information for each image.
• Column names are optional and free of choice.
• Columns and order of columns can be customized.
• Positional information can be expressed using any supported coordinate system.
• Orientations can be expressed in one of the listed orientation systems :
  • Omega, Phi, Kappa ¹⁾.
    Reference direction is pointing eastwards, but can be customized.
  • Pan (heading, yaw), Tilt (pitch), Roll ²⁾
    Reference direction and orientation are documented below, but can be customized.
  • Normalized direction and up vector (direction Easting, direction Northing, direction Elevation, up Easting, up Northing, up Elevation)
• Origin (rotation = 0°) or rotation offset and positive sense of rotation of orientation angles can be customized.

Only when using an absolute position and orientation of a reference frame at time of recording, the fixed relative position and orientations for each camera to the used reference frame must be given.
If the absolute position and orientations of the images at time of recording are known, these relative positions and orientations can be ignored.

Origin (rotation = 0°) and positive sense of rotation of orientation angles can be customized.

For each camera following camera and sensor specifications will be used to optimize the integration and accuracy in Orbit.

Metadata is optional, there is no limitation on the number of added image meta-attributes on import.

• date
• timestamp
• date time
• accuracy
• GPS information
• photo group id
• …

A Digital Terrain Model with indication of it's accuracy covering the same area as the Obliques is strongly advised and a must for one click Oblique measurements.

Supported formats
Preferably one geotif raster.
But one or more supported raster resource can be used : Supported Formats

Specifications

• Any supported coordinate system can be used.
• A DTM is as advised, a DSM can be used as well : Wikipedia Digital Elevation Model

Any supported reference data can be added optionally. An Ortho image with similar resolution of oblique photos is advised. If not available other (online) basemaps can be used.