Knowledge Base
Recent Changes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
dev:technology:3d_mapping:supported_resources [2018/10/29 11:18]
jve@orbitgt.com [DTM] 		dev:technology:3d_mapping:supported_resources [2024/03/11 14:01] (current)
glen [Video]
Line 1: Line 1:
-====== Supported 3D Mapping Resources ======+====== Supported Mapping Resources ======
  
-This page describes the supported Mobile Mapping, UAS and Oblique resources, any combination of the listed resources can be used.+This page documents all supported data types for Mobile Mapping, Aerial, and Aerial Oblique Mappin Resources. \\ 
 +To read more about concepts of a Mapping Run and Resource Groups, see [[dev:technology:3d_mapping:about_resources|]]
  
-====== Special Notes ====== 
  
-=== Import Template ===+====== General Notes ======
  
-Orbit imports 3D mapping data using intelligent templates. An import template is configured according to a well known set of configurations, given carrier (vehicle, UAV, aircraft, etc..) setup and available data. \\ +=== Required vs Optional Mapping Run resources ===
-The use of templates simplifies and standardizes the import procedure for a well known set of data.+
  
-**Download Templates** \\ +Mapping run is a combination of multiple individual resources that have a logical relation and are collected together by a mapping system. 
-system and custom custom import templates can be downloaded here : [[dev:desktop_ext:mobile_mapping:manage_import:templates|]].+A mapping run is a flexible structure, not all components as listed below are mandatory. 
  
-**Customize Import** \\ +=== Import Data === 
-In addition to the available templates the Orbit engine offers all configuration possibilities to customize and optimize the import for using any kind or combination of 3D mapping data. Once the configuration is known, it can be added as a new import template to 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 imports 3D mapping data using intelligent templates. An import template is configured according to a well-known set of configurations, given carrier (vehicle, UAV, aircraft, etc..) setup and available data. \\ 
 +The use of templates simplifies and standardizes the import procedure for a well-known set of data. 
 + 
 +Read more and download templates here: [[dev:desktop_ext:mapping:manage_import:templates|]].
  
 === Coordinate Reference Systems === === Coordinate Reference Systems ===
  
-Orbit supports any combination of 3D mapping data and any coordinate system (CRS) on import. But be wise :+Orbit supports any combination of 3D mapping data and any coordinate system (CRS) on import. But be wise:
   * The [[dev:technology:core:crs|coordinate reference system]] should be part of the metadata of each resource.   * The [[dev:technology:core:crs|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.   * 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). +  * When converting the coordinate system of image positions apply the according adjustments on all orientation angles referring to the reference direction of the coordinate systems (most probably north).  
 + 
 +  * CRS: can be expressed using any supported coordinate system. \\ After import, it is strongly advised that all mobile mapping resources use the same coordinate reference system. If required coordinates can be re-projected or transformed on import.
  
 === Timestamps === === Timestamps ===
  
-Optionally time-stamps can be imported. Time value can be a text string, integer or decimal value.+Optionally time-stamps can be imported. The time value can be a text string, integer, or decimal value.
  
-String values will be displayed as is and cannot be used for Content Manager post processing and point cloud view restrictions. \\ +String values will be displayed as-is and cannot be used for Content Manager post-processing and point cloud view restrictions. \\ 
-For post processing and point cloud view restrictions use of single time reference and "seconds" as time unit is required. A+For post-processing and point cloud view restrictions use of single time reference and "seconds" as time unit is required.
  
 Use of Absolute (Standard) GPS Time is advised. \\ Use of Absolute (Standard) GPS Time is advised. \\
Line 36: Line 40:
  
 Notes on Absolute GPS Time : Notes on Absolute GPS Time :
-  * Orbit doesn't take leap seconds are not taken into account, more information : [[http://en.wikipedia.org/wiki/Global_Positioning_System#Timekeeping|Wikipedia, GPS Timekeeping]] and [[https://en.wikipedia.org/wiki/Leap_second|Leap seconds]].+  * Orbit doesn't take leap seconds into account, more information : [[http://en.wikipedia.org/wiki/Global_Positioning_System#Timekeeping|Wikipedia, GPS Timekeeping]] and [[https://en.wikipedia.org/wiki/Leap_second|Leap seconds]].
   * On storing Absolute GPS Time values in Point Cloud LAS files the actual stored value is the Absolute GPS Time minus 1,000,000,000. More information, see [[http://www.asprs.org/Committee-General/LASer-LAS-File-Format-Exchange-Activities.html|ASPRS LASer File Format Exchange Activities]].   * On storing Absolute GPS Time values in Point Cloud LAS files the actual stored value is the Absolute GPS Time minus 1,000,000,000. More information, see [[http://www.asprs.org/Committee-General/LASer-LAS-File-Format-Exchange-Activities.html|ASPRS LASer File Format Exchange Activities]].
  
-====== Images ======+ 
 +====== Trajectory of Mapping System  ====== 
 + 
 +A trajectory of the mobile mapping vehicle is optional and can be used to display the accuracy or to adjust, clip, or extract a segment of the entire mobile mapping run. \\ 
 +Prepare the trajectory file in the same way as the image position and orientation file: see above. 
 + 
 +|< 100% 15% 55% 10% 10% 10% >| 
 +^ Field ^ Description ^  Data type  ^  Units  ^  Necessity  ^ 
 +| Timestamp | Time at recording, see “General Notes” above.  |  integer \\ decimal \\ string  |  |  optional  | 
 +| X | X, Longitude or Easting of reference point |  decimal  |   degrees \\ meters  |  required  | 
 +| Y | Y, Latitude or Northing of reference point |  ::: | ::: |  ::: | 
 +| Z | Z or Height of reference point |  ::: | ::: |  ::: | 
 +| Accuracy | The Trajectory GPS Accuracy indicator is indeed interpreted as a data manager only resource. Based on the GPS Accuracy indication the data manager can do an estimated guess regarding the absolute accuracy of the data at time of recording. This indication can assist to decide if and where to measure ground control points and apply trajectory adjustments.   |  decimal  |  |  optional  | 
 + 
 + 
 +====== Imagery ======
  
 Orbit supports spherical and planar images. \\ Orbit supports spherical and planar images. \\
-There are no limitations on the number of cameras, the type of camera or the resolution of images. \\ +There are no limitations on the number of cameras, the type of camera, or the resolution of images. \\ 
-One camera import requires one set of images and one positions and orientations file.+One camera import requires one set of images and one position and orientation file.
  
 ===== Photo positions, orientations and metadata ===== ===== Photo positions, orientations and metadata =====
  
-The absolute position and orientations at time of recording of all images must be available unambiguously. \\+The absolute position and orientations at the time of recording the images. \\
 Two possibilities :  Two possibilities : 
-  * absolute position and orientation for each camera at time of recording +  * absolute position and orientation for each camera at the 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).+  * absolute position and orientation of a reference frame at the time of recording combined with the fixed relative offset for each camera to this reference frame (aka lever arm & boresights ).
  
-=== Absolute positions and orientations at time of recording ===+=== Absolute positions and orientations === 
 + 
 +=== Supported formats ===
  
-**Supported formats** \\ 
 Preferably .txt or .csv files. \\ Preferably .txt or .csv files. \\
 But any [[dev:technology:supported_formats:index|supported point vector resource]] can be used. But any [[dev:technology:supported_formats:index|supported point vector resource]] can be used.
  
-**Specifications**  + 
-  * One text file for each camera containing at least the below described information for each image.+=== Specifications === 
 + 
 +  * One text file for each camera containing at least the below-described information for each image.
   * Column headers are optional and free of choice.   * Column headers are optional and free of choice.
   * Columns and order of columns can be customized.    * Columns and order of columns can be customized. 
   * Coordinates can be expressed using any [[dev:technology:core:crs|supported coordinate system]]. \\ After import, it is strongly advised that all mobile mapping resources use the same coordinate reference system. If required coordinates can be re-projected or transformed on import.   * Coordinates can be expressed using any [[dev:technology:core:crs|supported coordinate system]]. \\ After import, it is strongly advised that all mobile mapping resources use the same coordinate reference system. If required coordinates can be re-projected or transformed on import.
   * Orientations can be expressed as :    * Orientations can be expressed as : 
-    * Pan (heading, yaw), Tilt (pitch), Roll ((Pan (heading, yaw), Tilt (pitch), Roll : [[http://en.wikipedia.org/wiki/Aircraft_principal_axes|Wikipedia Aircraft principal axes]])) \\ Reference direction and orientation are documented below, but can be customized.+    * Pan (heading, yaw), Tilt (pitch), Roll ((Pan (heading, yaw), Tilt (pitch), Roll : [[http://en.wikipedia.org/wiki/Aircraft_principal_axes|Wikipedia Aircraft principal axes]])) \\ Reference direction and orientation are documented below but can be customized.
     * Omega, Phi, Kappa ((Omega, Phi, Kappa : (c) [[http://gridkr.com/d/ENVI_4_3/online_help/Building_RPCs.html|http://gridkr.com]] \\  {{orbitgis_extensions_mi:oblique:import:omega_phi_kappa.jpg?nolink|}})). \\ Reference direction is pointing eastwards, but can be customized.     * Omega, Phi, Kappa ((Omega, Phi, Kappa : (c) [[http://gridkr.com/d/ENVI_4_3/online_help/Building_RPCs.html|http://gridkr.com]] \\  {{orbitgis_extensions_mi:oblique:import:omega_phi_kappa.jpg?nolink|}})). \\ Reference direction is pointing eastwards, but can be customized.
     * Normalized direction and up vector (direction Easting, direction Northing, direction Elevation, up Easting, up Northing, up Elevation)     * 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.   * Origin (rotation = 0°) or rotation offset and positive sense of rotation of orientation angles can be customized.
  
-** Attributes **+=== Attributes === 
 |< 100% 15% 55% 10% 10% 10% >| |< 100% 15% 55% 10% 10% 10% >|
 ^ Field ^ Description ^  Data type  ^  Units  ^  Necessity  ^ ^ Field ^ Description ^  Data type  ^  Units  ^  Necessity  ^
 | Filename | Image file name as is on disk or any reference to the image file. |  string  |  |  required  | | Filename | Image file name as is on disk or any reference to the image file. |  string  |  |  required  |
-| Timestamp | Time at recording, see "Special Notes" above. |  string \\ integer \\ decimal  |  |  optional  |+| Timestamp | Time at recording, see "General Notes" above. |  string \\ integer \\ decimal  |  |  optional  |
 | X | X, Longitude or Easting of reference point |  decimal  |   degrees \\ meters  |  required  | | X | X, Longitude or Easting of reference point |  decimal  |   degrees \\ meters  |  required  |
 | Y | Y, Latitude or Northing of reference point |  ::: | ::: |  ::: | | Y | Y, Latitude or Northing of reference point |  ::: | ::: |  ::: |
Line 79: Line 102:
  
 |< 100% 15% 55% 10% 10% 10% >| |< 100% 15% 55% 10% 10% 10% >|
-| Pan | Horizontal angle between reference frame and north. \\ Positive for clockwise rotation of reference frame. \\ Value 0 looking north, value 90 looking east. |  decimal  |  degrees \\ radians \\ grad  |  required  | +| Pan / Heading | Horizontal angle between reference frame and north. \\ Positive for clockwise rotation of reference frame. \\ Value 0 looking north, value 90 looking east. |  decimal  |  degrees \\ radians \\ grad  |  required  | 
-| Tilt | Vertical angle or inclination about the lateral axes \\ between reference frame and horizontal plane. \\ Positive when reference frame goes up / looking up. \\ Value 0 looking horizontally, value 90 looking vertically at the sky, value -90 looking down. | ::: | ::: | ::: | +| Tilt / Pitch | Vertical angle or inclination about the lateral axes \\ between reference frame and horizontal plane. \\ Positive when reference frame goes up / looking up. \\ Value 0 looking horizontally, value 90 looking vertically at the sky, value -90 looking down. | ::: | ::: | ::: | 
-| Roll | Vertical angle or inclination about the longitudinal axes \\ between reference frame and the horizontal plane. \\ Positive when reference frame rolls to the left, right hand turn. |  ::: | ::: | ::: |+| Roll | Vertical angle or inclination about the longitudinal axes \\ between reference frame and the horizontal plane. \\ Positive when reference frame rolls to the left, right-hand turn. |  ::: | ::: | ::: |
  
 |< 100% 15% 55% 10% 10% 10% >| |< 100% 15% 55% 10% 10% 10% >|
Line 98: Line 121:
 === Relative position and orientation === === Relative position and orientation ===
  
-Only when using an absolute position and orientation of a reference frame at time of recording, the fixed relative position and orientation for each camera to the used reference frame must be known. Relative position and orientation can be ignored when using the absolute position and orientation of images at time of recording. +Only when using an absolute position and orientation of a reference frame at time of recording, the fixed relative position and orientation for each camera to the used reference frame must be known. The relative position and orientation can be ignored when using the absolute position and orientation of images at time of recording. 
  
 |< 100% 15% 55% 10% 10% 10% >| |< 100% 15% 55% 10% 10% 10% >|
 ^ Field ^ Description ^  Data type  ^  Units  ^  Necessity  ^ ^ Field ^ Description ^  Data type  ^  Units  ^  Necessity  ^
-| CameraName| Unique name to identify the camera and to link these camera specification with the position and orientation file. |  string  | |  optional  | +| CameraName| Unique name to identify the camera and to link these camera specifications with the position and orientation file. |  string  | |  optional  | 
-| CameraDeltaX | Fix distance in X expressed in meters from the origin of the camera reference frame \\ to the IMU/GPS reference frame. |  decimal  |  meters  |  required  |+| CameraDeltaX | Fix distance in X expressed in meters from the origin of the camera reference frame \\ to the IMU/GPS reference frame. |  decimal  |  meters  |  optional  |
 | CameraDeltaY | Fix distance in Y expressed in meters from the origin of the camera reference frame \\ to the IMU/GPS reference frame. | ::: | ::: | ::: | | CameraDeltaY | Fix distance in Y expressed in meters from the origin of the camera reference frame \\ to the IMU/GPS reference frame. | ::: | ::: | ::: |
 | CameraDeltaZ | Fix distance in Z expressed in meters from the origin of the camera reference frame \\ to the IMU/GPS reference frame. | ::: |  ::: | ::: | | CameraDeltaZ | Fix distance in Z expressed in meters from the origin of the camera reference frame \\ to the IMU/GPS reference frame. | ::: |  ::: | ::: |
  
 |< 100% 15% 55% 10% 10% 10% >| |< 100% 15% 55% 10% 10% 10% >|
-| CameraDeltaPan | Fix Pan of  camera reference frame to IMU/GPS reference frame. \\ Positive for clockwise rotation of camera frame. |  decimal  |  degrees \\ radians \\ grad  |  required  |+| CameraDeltaPan | Fix Pan of camera reference frame to IMU/GPS reference frame. \\ Positive for clockwise rotation of camera frame. |  decimal  |  degrees \\ radians \\ grad  |  optional  |
 | CameraDeltaTilt | Fix tilt of camera reference frame to IMU/GPS reference frame. \\ Positive when camera frame goes up / looking up. | ::: | ::: | ::: | | CameraDeltaTilt | Fix tilt of camera reference frame to IMU/GPS reference frame. \\ Positive when camera frame goes up / looking up. | ::: | ::: | ::: |
 | CameraDeltaRoll | Fix roll of camera reference frame to IMU/GPS reference frame. \\ Positive when camera reference frame rolls to the left. | ::: | ::: | ::: | | CameraDeltaRoll | Fix roll of camera reference frame to IMU/GPS reference frame. \\ Positive when camera reference frame rolls to the left. | ::: | ::: | ::: |
Line 132: Line 155:
 ===== Spherical images ===== ===== Spherical images =====
  
-Panoramas (spherical or 360° images) are optional for Orbit MM Desktop products. The Orbit MM Publisher requires the availability of spherical images (panoramas) to operate.+=== Supported formats ===
  
-**Supported formats** \\ 
 Preferably .jpg files. \\ Preferably .jpg files. \\
 But any [[dev:technology:supported_formats:index|supported image resource]] can be used. But any [[dev:technology:supported_formats:index|supported image resource]] can be used.
  
-**Supported types** \\+=== Supported types ===
 Orbit supports any Spherical and Cubic Panorama, independently of file size or pixel resolution. \\ Orbit supports any Spherical and Cubic Panorama, independently of file size or pixel resolution. \\
 For example, Ladybug 3 and 5 are supported. For example, Ladybug 3 and 5 are supported.
  
-=== Equirectangular Panoramas ===+=== Equi-rectangular Panoramas ===
  
 {{mobile_mapping:stniklaas001937.jpg?nolink&600|}} {{mobile_mapping:stniklaas001937.jpg?nolink&600|}}
Line 149: Line 171:
   * Stitching the images should be done by the camera software, knowing and applying all camera calibration and distortion parameters.   * Stitching the images should be done by the camera software, knowing and applying all camera calibration and distortion parameters.
   * The centered pixel of the picture will be used to affect the orientation angles. If required this can be re-configured via a customized import.   * The centered pixel of the picture will be used to affect the orientation angles. If required this can be re-configured via a customized import.
-  * Any 2 x 1 pixel resolution ratio can be used but an equirectangular panoramic image should always be 360 x 180 degree. \\ There are no limitations on the image pixel resolution. If required Orbit can optimize high resolution images (> 8000 x 4000 pixels) for online use.+  * Any 2 x 1 pixel resolution ratio can be used but an equirectangular panoramic image should always be 360 x 180 degrees. \\ There are no limitations to the image pixel resolution. If required Orbit can optimize high-resolution images (> 8000 x 4000 pixels) for online use.
  
 === Cubic Panoramas === === Cubic Panoramas ===
Line 158: Line 180:
 \\  \\ 
 When working with Cubic panoramic images Orbit is using the 6 original equirectangular images. \\ When working with Cubic panoramic images Orbit is using the 6 original equirectangular images. \\
-  * To display and use cubic panoramas properly it is required to know all orientation, calibration and distortion parameters from the used camera's. +  * To display and use cubic panoramas properly it is required to know all orientation, calibration, and distortion parameters from the used cameras. 
   * Any pixel resolution can be used.   * Any pixel resolution can be used.
  
 ===== Planar Images ===== ===== Planar Images =====
  
-There are no limitations on the number of cameras, the type of camera or the resolution of images.  +There are no limitations on the type of camera or the resolution of images. The maximum amount of planar images is 20.  
-One camera import requires one set of images and one positions and orientations file. +One camera import requires one set of images and one position and orientation file. 
  
-**Supported formats** \\ +=== Supported formats ===
-Preferably .jpg files. \\ +
-But any [[dev:technology:supported_formats:index|supported image resource]] can be used.+
  
-**Supported types** \\ +Preferably .jpg files. But any [[dev:technology:supported_formats:index|supported image resource]] can be used. 
-Orbit supports any distorted Planar picture, independently of file size or pixel resolution. \\+ 
 +=== Supported types === 
 + 
 +Any size, any resolution. \\ 
 +Preferably undistorted images, see Lens distortion.
  
 === Camera calibration === === Camera calibration ===
Line 178: Line 202:
  
 |< 100% 10% 60% 10% 10% 10% >| |< 100% 10% 60% 10% 10% 10% >|
-^ Field ^ Description ^  Data type  ^  Units  ^  Necessity  ^ +^ What ^ Description ^  Data type  ^  Units  ^  Necessity  ^ 
-| CameraName | Unique name to identify the camera and to link these camera specification with the position and orientation file. |  string  | |  optional  |+| CameraName | Unique name to identify the camera and to link these camera specifications with the position and orientation file. |  string  | |  optional  |
 | SensorName | Reference of sensor to have the possibility to review the sensor specifications. |  string  | |  optional  | | SensorName | Reference of sensor to have the possibility to review the sensor specifications. |  string  | |  optional  |
 | SensorPixelSize | Physical size of pixels on the sensor CCD, expressed in mm. |  decimal  |  mm  |  required  | | SensorPixelSize | Physical size of pixels on the sensor CCD, expressed in mm. |  decimal  |  mm  |  required  |
Line 187: Line 211:
 | SensorPixelPPY | The principal point value along the sensor height. |  :::  | ::: |  :::  | | SensorPixelPPY | The principal point value along the sensor height. |  :::  | ::: |  :::  |
 | FocalLength | The focal length of the lens, expressed in mm. \\ [[http://en.wikipedia.org/wiki/Focal_length|Wikipedia Focal Length]] |  decimal  |  mm  |  required  | | FocalLength | The focal length of the lens, expressed in mm. \\ [[http://en.wikipedia.org/wiki/Focal_length|Wikipedia Focal Length]] |  decimal  |  mm  |  required  |
-| k1, k2, k3, p1, p2 | Radial distortion parameters, regarding the formulas of D.C. Brown. \\ [[http://en.wikipedia.org/wiki/Distortion_(optics)|Wikipedia Distortion]] |  decimal  |  |  optional  |+ 
 +=== Lens Distortion === 
 + 
 +The use of undistorted planar images is preferred. \\ 
 +When providing distorted images, lens distortion parameters must be provided corresponding to Brown implementation of OpenCV model.  
 + 
 +|< 100% 10% 60% 10% 10% 10% >| 
 +^ What ^ Description ^  Data type  ^  Units  ^  Necessity  ^ 
 +| k1,k2,k3,p1,p2,fx,fy | Radial distortion parameters, regarding the formulas of D.C. Brown. \\ [[http://en.wikipedia.org/wiki/Distortion_(optics)|Wikipedia Distortion]] |  decimal  |  |  optional  | 
 === Street Level\Indoor === === Street Level\Indoor ===
  
Line 193: Line 226:
  
 === Oblique === === Oblique ===
 +
 {{:dev:technology:3d_mapping:imageoblique1.png?nolink&600|}} {{:dev:technology:3d_mapping:imageoblique1.png?nolink&600|}}
  
 === Nadir === === Nadir ===
 {{:dev:technology:3d_mapping:imagenadir1.png?nolink&600|}} {{:dev:technology:3d_mapping:imagenadir1.png?nolink&600|}}
- 
- 
-====== Trajectory of Vehicle  ====== 
- 
-A trajectory of the mobile mapping vehicle is optional and can be used to display the accuracy or to adjust, clip or extract a segment of the entire mobile mapping run. \\ 
-Prepare the trajectory file in the same way as the image position and orientation file : see above. 
- 
-|< 100% 15% 55% 10% 10% 10% >| 
-^ Field ^ Description ^  Data type  ^  Units  ^  Necessity  ^ 
-| Timestamp | Time at recording, see “Special Notes” above.  |  integer \\ decimal \\ string  |  |  optional  | 
-| X | X, Longitude or Easting of reference point |  decimal  |   degrees \\ meters  |  required  | 
-| Y | Y, Latitude or Northing of reference point |  ::: | ::: |  ::: | 
-| Z | Z or Height of reference point |  ::: | ::: |  ::: | 
-| Accuracy | The Trajectory GPS Accuracy indicator is indeed interpreted as a data manager only resource. Based on the GPS Accuracy indication the data manager can do an estimated guess regarding the absolute accuracy of the data at time of recording. This indication can assist to decided if and where to measure ground control point and apply trajectory adjustments.   |  decimal  |  |  optional  | 
  
 ====== Point Cloud ====== ====== Point Cloud ======
  
-Point clouds are optional, there are no limitations on the number of imported point cloud files nor their size.+LiDAR point cloud or point cloud derived from dense matching. \\ 
 +There are no limitations on the number of points, files, or the total size.
  
-**Supported formats** \\ +=== Required for ===  
-Preferably .las (v1.2) files. \\ +  * Mobile Mapping: Recommended 
-But any [[dev:technology:supported_formats:index|supported LiDAR resource]] can be used.+  * Oblique Mapping: Optional 
 +  * Aerial Mapping: Strongly recommended
  
-**Specifications** +=== Supported formats === 
-  * One or multiple LiDAR resource files can be used +  * One or more supported point cloud resources, see [[dev:technology:supported_formats:index|]]. 
-  * Coordinates can be expressed using any supported coordinate system. \\ After import, it is strongly advised that all mobile mapping resources use the same coordinate reference system. If required coordinates can be re-projected or transformed on import. +  * Preferred: *.las files. 
-  * Timestamps : Time at recording, see “Special Notes” above. +
  
-**Data-structure when using Ascii text files** \\  +=== Additional Notes for ASCII text files ===  
-When using an Ascii text file as point cloud import it is possible to configure the data-structure : + 
-  * Flat ascii text file, separated, columns and column headers +When using an Ascii text file as point cloud import it is possible to configure the data-structure: 
-  * R, G, B, I value ranges 0-25, values may be empty+  * Flat ASCII text file, separated, columns and column headers 
 +  * R, G, B, I value ranges 0-255, values may be empty
   * Character to define end of line   * Character to define end of line
  
-====== DTM ======+====== DEM ======
  
 A Digital Terrain Model or Digital Surface Model covering the same area as the Mapping Resources. \\  A Digital Terrain Model or Digital Surface Model covering the same area as the Mapping Resources. \\ 
 Both a DTM or DSM can be used, but we recommend DTM for measurements and navigation. \\ Both a DTM or DSM can be used, but we recommend DTM for measurements and navigation. \\
-[[http://en.wikipedia.org/wiki/Digital_elevation_model|Wikipedia, Digital Elevation Model]])).+[[http://en.wikipedia.org/wiki/Digital_elevation_model|Wikipedia, Digital Elevation Model]]. 
 + 
 +=== Required for === 
  
-**Required for**  
   * Mobile Mapping: Optional   * Mobile Mapping: Optional
-  * Oblique: Recommended  +  * Oblique Mapping: Recommended  
-  * UAS Mapping: Optional+  * Aerial Mapping: Optional 
 + 
 +=== Supported formats === 
  
-**Supported formats** \\ 
   * One or more supported raster resources, see [[dev:technology:supported_formats:index|]].    * One or more supported raster resources, see [[dev:technology:supported_formats:index|]]. 
-  * Preferred : single raster geotif.+  * Preferred: single raster GeoTIFF file.
  
-**Specifications** +=== Notes===  
-  * Any [[dev:technology:core:crs|supported coordinate system]] can be used.+ 
 +  * CRS: Any [[dev:technology:core:crs|supported projected coordinate system]] can be used. 
 + 
 +====== Textured Mesh ====== 
 + 
 +A Textured Mesh covering the same area as the Mapping Resources can be used. It can be part of the run, but only be visualized using the Map GL component. \\ 
 +Use the [[dev:technology:supported_formats:models:3dtiles|Cesium 3D Tiles]] format. 
 + 
 +====== Orthophoto ====== 
 + 
 +An Orthophoto covering the same area as the Mapping Resources can be used. 
 +Any [[dev:technology:supported_formats:index|supported multiresolution image resource]] can be used. 
 + 
 +====== Image Annotations ====== 
 + 
 +Image annotation xml files are linked to the Mapping Resource images by filename. 
 + 
 +==== Supported formats ===== 
 + 
 +One csv or xml annoation file with annotations for all imagery. 
 +Once xml annotation file per image. 
 + 
 +=== Generic === 
 + 
 +<code> 
 +<?xml version="1.0" ?> 
 +<annotation> 
 + <folder></folder> 
 + <filename>DSC02490.JPG</filename> 
 + <object> 
 + <tags>corrosion,structural_steel,light</tags> 
 + <comment></comment> 
 + <bound> 
 + <xmin>1541</xmin> 
 + <xmax>2008</xmax> 
 + <ymin>4257</ymin> 
 + <ymax>4555</ymax> 
 + </bound> 
 + </object> 
 +</annotation> 
 +</code> 
 + 
 +=== Context Insight === 
 + 
 +Version 2.0 
 + 
 +<code> 
 +<?xml version="1.0" encoding="utf-8"?> 
 +<ContextScene version="2.0"> 
 + <PhotoCollection> 
 + <Photos> 
 + <Photo id="0"> 
 + <ImagePath>D:/DATA/BE Lokeren Orbit - MMS by Topcon TEP/panorama1/original/LB_5000000.jpg</ImagePath> 
 + </Photo> 
 + <Photo id="1"> 
 + <ImagePath>D:/DATA/BE Lokeren Orbit - MMS by Topcon TEP/panorama1/original/LB_5000001.jpg</ImagePath> 
 + </Photos> 
 + </PhotoCollection> 
 + <Annotations> 
 + <Labels> 
 + <Label id="1"> 
 + <Name>person</Name> 
 + </Label> 
 + <Label id="3"> 
 + <Name>car</Name> 
 + </Label> 
 + <Label id="8"> 
 + <Name>truck</Name> 
 + </Label 
 + </Labels> 
 + <Objects2D> 
 + <ObjectsInPhoto> 
 + <PhotoId>0</PhotoId> 
 + <Objects> 
 + <Object2D id="0"> 
 + <LabelInfo> 
 + <Confidence>0.9734092</Confidence> 
 + <LabelId>1</LabelId> 
 + </LabelInfo> 
 + <Box2D> 
 + <xmin>0.694173574447632</xmin> 
 + <ymin>0.540982902050018</ymin> 
 + <xmax>0.717123627662659</xmax> 
 + <ymax>0.666199862957001</ymax> 
 + </Box2D> 
 + </Object2D> 
 + <Object2D id="1"> 
 + <LabelInfo> 
 + <Confidence>0.8548903</Confidence> 
 + <LabelId>3</LabelId> 
 + </LabelInfo> 
 + <Box2D> 
 + <xmin>0.00750905275344849</xmin> 
 + <ymin>0.559191405773163</ymin> 
 + <xmax>0.145229429006577</xmax> 
 + <ymax>0.784758269786835</ymax> 
 + </Box2D> 
 + </Object2D> 
 + </Objects> 
 + </ObjectsInPhoto> 
 + <ObjectsInPhoto> 
 + <PhotoId>1</PhotoId> 
 + <Objects> 
 + <Object2D id="0"> 
 + <LabelInfo> 
 + <Confidence>0.9596778</Confidence> 
 + <LabelId>3</LabelId> 
 + </LabelInfo> 
 + <Box2D> 
 + <xmin>0.00675202906131744</xmin> 
 + <ymin>0.552075982093811</ymin> 
 + <xmax>0.148410230875015</xmax> 
 + <ymax>0.789381384849548</ymax> 
 + </Box2D> 
 + </Object2D> 
 + </ObjectsInPhoto> 
 + </Objects2D> 
 + </Annotations> 
 +</ContextScene> 
 +</code> 
 + 
 +Version 1.0 
 + 
 +<code> 
 +<?xml version="1.0" encoding="utf-8"?> 
 +<Scene version="1.0"> 
 + <PositioningLevel>Unknown</PositioningLevel> 
 + <SpatialReferenceSystems/> 
 + <Devices/> 
 + <Poses/> 
 + <Shots> 
 + <Shot id="0"> 
 + <DeviceId>0</DeviceId> 
 + <PoseId>0</PoseId> 
 + <ImagePath>Z:/Movyon/POC_bridge/Carreggiata_Nord/Carreggiata_Nord/01_Spalla inizio/P5590560.JPG</ImagePath> 
 + <NearDepth>3.41018193441476</NearDepth> 
 + <MedianDepth>5.31374846082021</MedianDepth> 
 + <FarDepth>6.03807500283101</FarDepth> 
 + </Shot> 
 + <Shot id="1"> 
 + <DeviceId>0</DeviceId> 
 + <PoseId>1</PoseId> 
 + <ImagePath>Z:/Movyon/POC_bridge/Carreggiata_Nord/Carreggiata_Nord/01_Spalla inizio/P5600561.JPG</ImagePath> 
 + <NearDepth>3.35579477082049</NearDepth> 
 + <MedianDepth>5.22362535386351</MedianDepth> 
 + <FarDepth>5.86464739324289</FarDepth> 
 + </Shot> 
 + </Shots> 
 + <TiePoints/> 
 + <PointConstraints/> 
 + <Learning> 
 + <Labels> 
 + <Label> 
 + <Id>1</Id> 
 + <Name>person</Name> 
 + </Label> 
 + <Label> 
 + <Id>3</Id> 
 + <Name>car</Name> 
 + </Label> 
 + </Labels> 
 + <ObjectsInImages> 
 + <ObjectsInImage> 
 + <ImageId>0</ImageId> 
 + <Objects2D> 
 + <Object2D> 
 + <Id>0</Id> 
 + <LabelInfo> 
 + <Confidence>0.846392</Confidence> 
 + <LabelId>9</LabelId> 
 + </LabelInfo> 
 + <Box2D> 
 + <xmin>0.059297751635313</xmin> 
 + <ymin>0.145194128155708</ymin> 
 + <xmax>0.999414801597595</xmax> 
 + <ymax>0.438706368207932</ymax> 
 + </Box2D> 
 + </Object2D> 
 + </Objects2D> 
 + </ObjectsInImage> 
 + <ObjectsInImage> 
 + <ImageId>1</ImageId> 
 + <Objects2D> 
 + <Object2D> 
 + <Id>0</Id> 
 + <LabelInfo> 
 + <Confidence>0.9815791</Confidence> 
 + <LabelId>9</LabelId> 
 + </LabelInfo> 
 + <Box2D> 
 + <xmin>0.0492010489106178</xmin> 
 + <ymin>0.213278770446777</ymin> 
 + <xmax>0.978382289409637</xmax> 
 + <ymax>0.549207985401154</ymax> 
 + </Box2D> 
 + </Object2D> 
 + </Objects2D> 
 + </ObjectsInImage> 
 + </ObjectsInImages> 
 + <Objects3D/> 
 + <Segmentations2D/> 
 + <Segmentations3D/> 
 + </Learning> 
 + <PointClouds/> 
 + <Pairs/> 
 + <AutomaticTiePoints/> 
 +</Scene> 
 +</code> 
 + 
 +====== Video ====== 
 + 
 +===Supported formats=== 
 + 
 +Preferably .mp4 files. \\ 
 +When using cloud blob storage, the storage needs to support "range requests" to open the video at a specific time offset from start. 
 + 
 +===Attributes=== 
 + 
 +|< 100% 10% 60% 10% 10% 10% >| 
 +^ What ^ Description ^  Data type  ^  Units  ^  Necessity  ^ 
 +| Video Filename  | - Relative location inside the run's video folder.\\ - Absolute URL pointing to the online storage location of the video.  |  string  | |  required  | 
 +| Video Time  | The time offset from the start of the video.  |  integer  |  milliseconds |  required  |
  
-====== Reference and Geodata ======+Video Attributes 
 +  * File Example: <Orbit Run>/panorama1/import/import_locations.ord \\ <code>   AddAttribute= 
 +    AttributeName=OrbitVideoTime 
 +    AttributeType=INT4 
 +    AttributeExpression=[Imported Value] 
 +   AddAttribute= 
 +    AttributeName=OrbitVideoFileName 
 +    AttributeType=STRING 
 +    AttributeExpression=[Imported Value]</code>  
 +====== References and Geodata ======
  
-Any [[dev:technology:supported_formats:index|supported reference data]] can be added into Orbit. Reference data is not part of a Run or a Project.+Any [[dev:technology:supported_formats:index|supported reference data]] can be added into Orbit. Reference data is not part of a Run.
 
Last modified:: 2018/10/29 11:18