Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
dev:technology:3d_mapping:supported_resources [2020/09/11 09:20] reine |
dev:technology:3d_mapping:supported_resources [2024/03/08 20:49] glen [Video] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Supported | + | ====== Supported Mapping Resources ====== |
+ | |||
+ | 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: | ||
- | This page describes the supported Mobile Mapping, Aerial, and Oblique resources, any combination of the listed resources can be used. | ||
====== General Notes ====== | ====== General Notes ====== | ||
Line 8: | Line 10: | ||
Mapping run is a combination of multiple individual resources that have a logical relation and are collected together by a mapping system. | Mapping run is a combination of multiple individual resources that have a logical relation and are collected together by a mapping system. | ||
- | A mapping run is a flexible structure, | + | A mapping run is a flexible structure, not all components as listed below are mandatory. |
- | exception images require photo positions | + | |
=== Import Data === | === Import Data === | ||
- | |||
- | <note warning> | ||
Orbit imports 3D mapping data using intelligent templates. An import template is configured according to a well-known set of configurations, | Orbit imports 3D mapping data using intelligent templates. An import template is configured according to a well-known set of configurations, | ||
The use of templates simplifies and standardizes the import procedure for a well-known set of 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: | + | Read more and download templates here: [[dev: |
=== 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: | * The [[dev: | ||
* 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 to 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 === | ||
Line 41: | Line 42: | ||
* Orbit doesn' | * Orbit doesn' | ||
* On storing Absolute GPS Time values in Point Cloud LAS files the actual stored value is the Absolute GPS Time minus 1, | * On storing Absolute GPS Time values in Point Cloud LAS files the actual stored value is the Absolute GPS Time minus 1, | ||
+ | |||
====== Trajectory of Mapping System | ====== Trajectory of Mapping System | ||
Line 54: | Line 56: | ||
| Z | Z or Height 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. | | 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. | ||
+ | |||
====== Imagery ====== | ====== Imagery ====== | ||
Line 63: | Line 66: | ||
===== Photo positions, orientations and metadata ===== | ===== Photo positions, orientations and metadata ===== | ||
- | The absolute position and orientations at time of recording | + | The absolute position and orientations at the time of recording |
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 | + | * absolute position and orientation of a reference frame at the time of recording |
=== Absolute positions and orientations === | === Absolute positions and orientations === | ||
- | **Supported formats** \\ | + | === Supported formats |
Preferably .txt or .csv files. \\ | Preferably .txt or .csv files. \\ | ||
But any [[dev: | But any [[dev: | ||
- | **Specifications** | + | |
+ | === Specifications | ||
* One text file for each camera containing at least the below-described information for each image. | * 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. | ||
Line 85: | Line 91: | ||
* 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 | ||
Line 119: | Line 126: | ||
^ Field ^ Description ^ Data type ^ Units ^ Necessity | ^ Field ^ Description ^ Data type ^ Units ^ Necessity | ||
| CameraName| Unique name to identify the camera and to link these camera specifications with the position and orientation file. | string | | CameraName| Unique name to identify the camera and to link these camera specifications with the position and orientation file. | string | ||
- | | CameraDeltaX | Fix distance in X expressed in meters from the origin of the camera reference frame \\ to the IMU/GPS reference frame. | decimal | + | | CameraDeltaX | Fix distance in X expressed in meters from the origin of the camera reference frame \\ to the IMU/GPS reference frame. | decimal |
| 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 | + | | CameraDeltaPan | Fix Pan of camera reference frame to IMU/GPS reference frame. \\ Positive for clockwise rotation of camera frame. | decimal |
| 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 136: | Line 143: | ||
=== Metadata === | === Metadata === | ||
- | |||
- | <note warning> | ||
Metadata is optional, there is no limitation on the number of added image meta-attributes on import. | Metadata is optional, there is no limitation on the number of added image meta-attributes on import. | ||
Line 150: | 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: | But any [[dev: | ||
- | **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. | ||
Line 181: | Line 185: | ||
===== Planar Images ===== | ===== Planar Images ===== | ||
- | There are no limitations on the number of cameras, | + | 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 position and orientation 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: | + | Preferably .jpg files. But any [[dev: |
+ | |||
+ | === Supported types === | ||
- | **Supported types** \\ | + | Any size, any resolution. \\ |
- | Orbit supports any distorted Planar picture, independently of file size or pixel resolution. \\ | + | Preferably undistorted images, see Lens distortion. |
=== Camera calibration === | === Camera calibration === | ||
Line 196: | 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 specifications with the position and orientation file. | string | | CameraName | Unique name to identify the camera and to link these camera specifications with the position and orientation file. | string | ||
| SensorName | Reference of sensor to have the possibility to review the sensor specifications. | string | | SensorName | Reference of sensor to have the possibility to review the sensor specifications. | string | ||
Line 205: | 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:// | | FocalLength | The focal length of the lens, expressed in mm. \\ [[http:// | ||
- | | k1, k2, k3, p1, p2 | Radial distortion parameters, regarding the formulas of D.C. Brown. \\ [[http:// | + | |
+ | === 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, | ||
=== Street Level\Indoor === | === Street Level\Indoor === | ||
+ | |||
{{orbitgis_extensions_mi: | {{orbitgis_extensions_mi: | ||
=== Oblique === | === Oblique === | ||
+ | |||
{{: | {{: | ||
=== Nadir === | === Nadir === | ||
{{: | {{: | ||
- | |||
====== Point Cloud ====== | ====== Point Cloud ====== | ||
LiDAR point cloud or point cloud derived from dense matching. \\ | LiDAR point cloud or point cloud derived from dense matching. \\ | ||
- | There are no limitations on the number of points, files or the total size. | + | There are no limitations on the number of points, files, or the total size. |
- | **Required for** | + | === Required for === |
* Mobile Mapping: Recommended | * Mobile Mapping: Recommended | ||
* Oblique Mapping: Optional | * Oblique Mapping: Optional | ||
* Aerial Mapping: Strongly recommended | * Aerial Mapping: Strongly recommended | ||
- | **Supported formats** | + | === Supported formats |
* One or more supported point cloud resources, see [[dev: | * One or more supported point cloud resources, see [[dev: | ||
* Preferred: *.las files. | * Preferred: *.las files. | ||
- | **Notes** | + | === Additional |
- | <note warning> | + | When using an Ascii text file as point cloud import it is possible to configure the data-structure: |
- | + | ||
- | * 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: Time at recording, see “General Notes” above. | + | |
- | + | ||
- | **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 | * Flat ASCII text file, separated, columns and column headers | ||
- | * R, G, B, I value ranges 0-25, values may be empty | + | * R, G, B, I value ranges 0-255, values may be empty |
* Character to define end of line | * Character to define end of line | ||
Line 250: | Line 259: | ||
[[http:// | [[http:// | ||
- | **Required for** | + | === Required for === |
* Mobile Mapping: Optional | * Mobile Mapping: Optional | ||
* Oblique Mapping: Recommended | * Oblique Mapping: Recommended | ||
* Aerial Mapping: Optional | * Aerial Mapping: Optional | ||
- | **Supported formats** | + | === Supported formats |
* One or more supported raster resources, see [[dev: | * One or more supported raster resources, see [[dev: | ||
* Preferred: single raster GeoTIFF file. | * Preferred: single raster GeoTIFF file. | ||
- | **Notes** | + | === Notes=== |
* CRS: Any [[dev: | * CRS: Any [[dev: | ||
====== Textured Mesh ====== | ====== 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: | ||
+ | |||
+ | ====== | ||
+ | |||
+ | An Orthophoto covering the same area as the Mapping Resources can be used. | ||
+ | Any [[dev: | ||
+ | |||
+ | ====== 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 === | ||
+ | |||
+ | < | ||
+ | <?xml version=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | === Context Insight === | ||
+ | |||
+ | Version 2.0 | ||
+ | |||
+ | < | ||
+ | <?xml version=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | Version 1.0 | ||
+ | |||
+ | < | ||
+ | <?xml version=" | ||
+ | <Scene version=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | <Shot id=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | <Shot id=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | ====== Video ====== | ||
+ | |||
+ | ===Supported formats=== | ||
+ | |||
+ | Preferably .mp4 files. \\ | ||
+ | When using cloud blob storage, the storage needs to support "range requests" | ||
+ | |||
+ | ===Attributes=== | ||
+ | |||
+ | |< 100% 10% 60% 10% 10% 10% >| | ||
+ | ^ What ^ Description ^ Data type ^ Units ^ Necessity | ||
+ | | Video Filename | ||
+ | | Video Time | The time offset from the start of the video. | ||
+ | Video Attributes | ||
+ | * File Example: <Orbit Run>/ | ||
+ | AttributeName=OrbitVideoTime | ||
+ | AttributeType=INT4 | ||
+ | AttributeExpression=[Imported Value]) | ||
+ | | ||
+ | AttributeName=OrbitVideoFileName | ||
+ | AttributeType=STRING | ||
+ | AttributeExpression=[Imported Value])</ | ||
====== References and Geodata ====== | ====== References and Geodata ====== | ||
- | Any [[dev: | + | Any [[dev: |
Last modified:: 2024/03/11 14:01