Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dev:desktop_ext:mapping:manage:runs_version [2018/02/01 11:04] jve@orbitgt.com [Concepts] |
dev:desktop_ext:mapping:manage:runs_version [2024/03/06 18:55] (current) glen [Mapping Run Configurations] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Orbit Mapping Resources - Structure and Configs ====== | ====== Orbit Mapping Resources - Structure and Configs ====== | ||
- | This page describes basic technical configurations of Orbit Mapping Runs and Oblique Projects. | + | This page describes basic technical configurations of Orbit Mapping\UAS Runs and Oblique Projects. |
- | It is strongly recommended to read first [[technology: | + | |
+ | It is strongly recommended to read first | ||
+ | * [[dev:technology:3d_mapping: | ||
+ | * [[dev: | ||
===== Concepts ===== | ===== Concepts ===== | ||
Line 8: | Line 11: | ||
=== Import Templates === | === Import Templates === | ||
- | All advanced technical configurations related to the used resources and mobile mapping system are managed via the import template and applied on import, so called " | + | All advanced technical configurations related to the used resources and mobile mapping system are managed via the import template and applied on import, so-called " |
- | Some additional configurations can be added or updated after import, so called " | + | Some additional configurations can be added or updated after import, so-called " |
=== Backwards compatibility and New Features === | === Backwards compatibility and New Features === | ||
- | Orbit is constantly improving tools and software which may result in an update of the files and structure of an. \\ | + | Orbit is constantly improving tools and software which may result in an update of the files and structure of a Mapping Run. \\ |
- | Backwards | + | Backward |
- | An Orbit Run version 3 uses the “orbit_mm_run.omr” file as reference resource file. \\ | + | An Orbit Run version 3 uses the "orbit_mm_run.omr" |
- | This updated | + | An Orbit Oblique Project version 3 uses the " |
+ | This updated | ||
- | For previous version or to convert existing runs into the updated structure, see [[110: | + | For previous version or to convert existing runs\projects |
- | === Mapping Run Version 3 === | + | ===== |
- | The current structure is in place since Orbit version 11.0. \\ | + | Configurations to be added into the .omr Mapping Resource root file. \\ |
- | Structure updates compared to run version 2 : | + | Edit and save the configuration files using a standard text editor (e.g. Notepad), respect file formatting and structure. |
- | * Point Cloud : ../ | + | |
- | * Trajectory : ../ | + | |
- | * Simplified Trajectory : ../ | + | |
- | * Trajectory Adjustments : ../ | + | |
- | ===== Configurations for Mapping Runs and Oblique Projects ===== | + | ==== Parameters editable at Create Run ==== |
- | === Relative Image Path === | + | To allow the user to enter any parameter through the user interface following structures are used in *.omr and *.oop: |
+ | * **template.parameters**: | ||
+ | * **template.parameters.name_of_the_resource**: | ||
+ | |||
+ | < | ||
+ | Example: | ||
+ | template.parameters.planar1=SensorSizePIXX; | ||
+ | template.parameters.planar2=SensorSizePIXX; | ||
+ | </ | ||
+ | Parameters will be read into corresponding {name_of_the_parameter} variable. | ||
+ | |||
+ | ==== Source and Target CRS ==== | ||
+ | |||
+ | To allow re-projecting of the data from one projection system to another 2 parameters, entered through GUI, are available | ||
+ | * Source projection system - **PARAM_CRS**: | ||
+ | * Target projection system - **PARAM_CRS2**: | ||
+ | <note important> | ||
+ | |||
+ | ==== Images file extension ==== | ||
+ | |||
+ | The used image storage format of original images (panorama or planar). | ||
+ | |||
+ | * File : <Orbit Run>/ | ||
+ | * Parameter : '' | ||
+ | * Values : Any supported image resource can be used, see [[dev: | ||
+ | * Default Value : .jpg | ||
+ | |||
+ | === Example === | ||
+ | |||
+ | < | ||
+ | version 3 | ||
+ | project.type generic | ||
+ | project.file orbit_mm_run.omr | ||
+ | photo.camera.height 2.20 | ||
+ | photo.sequence.key OrbithPhotoId | ||
+ | photo.file.extension .tif | ||
+ | template.parameters=PARAM_CRS | ||
+ | </ | ||
+ | |||
+ | ==== Redirect image file directory | ||
To avoid file copy into the appropriated Orbit run folder a single line ascii text file can be used to specify the image file path prefix. The file path prefix combined with the OrbitFileName attribute value will be used as file pointer. | To avoid file copy into the appropriated Orbit run folder a single line ascii text file can be used to specify the image file path prefix. The file path prefix combined with the OrbitFileName attribute value will be used as file pointer. | ||
- | * Files : \\ '' | + | * File : \\ '' |
* Parameter : not applicable | * Parameter : not applicable | ||
- | * Value : directory path | + | * Values |
+ | * Default Value : | ||
* Example < | * Example < | ||
\\192.168.0.1\images\ | \\192.168.0.1\images\ | ||
</ | </ | ||
- | ===== Configurations for Mapping Runs Only ===== | ||
- | Add/edit and save the listed files using a standard text editor (e.g. Notepad). | + | ==== Camera Height ==== |
- | === orbit_mm_run.omr === | + | Height of the camera above ground expressed in meters, use dot as decimal separator. This height is used to [[dev: |
- | The Orbit run identifier file (required). \\ | + | * File : <Orbit Run>/ |
- | <Orbit Run directory>/ | + | * Parameter : '' |
+ | * Default Value : 2.2 | ||
+ | * Unit : meters | ||
- | ** Camera height ** | + | ==== 2D Vector Visualization Parameters ==== |
- | '' | + | The possible range of the offset of 2D vector data to the height of the photo position (presented as a slider in the vector overlay parameters pop-up of the photo viewer). |
- | Height of camera above the road surface expressed in meters, use dot as decimal separator. This height is used to [[112:mobile_mapping:desktop:core: | + | * File : <Orbit Run>/ |
+ | * Parameters | ||
+ | * Default value : 5 | ||
+ | * Unit : meters | ||
- | ** Image file extension ** | + | Mostly need to be changed for UAS Runs depending on the flying height. |
- | '' | + | ==== Simplified Trajectory ==== |
- | File extension | + | At import |
- | ** Simplified | + | Coordinate will be added if its perpendicular drop distance to the segment between the previous and next coordinate is larger than maximum.distance. |
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | * Default Value : 1 | ||
- | '' | + | Two consecutive original coordinates won't be connected if segment length is larger than part.separation. |
- | '' | + | * File : <Orbit Run>/ |
- | '' | + | * Parameter : '' |
+ | * Values : Integer value | ||
+ | * Units: meter | ||
+ | * Default Value : 10 | ||
- | At import photo positions or trajectory the trajectory simplified (coverage) will be created automatically if not yet exists. | + | The initial |
- | * maximum.distance : coordinate will be added if its perpendicular drop distance to the segment between previous and next coordinate is larger than maximum.distance (meter). | + | * File : <Orbit Run>/ |
- | * part.separation : two consecutive original coordinates won't be connected if segment length is larger than part.separation (meter). | + | * Parameter : '' |
- | * photo.sequence.key : Initial | + | * Values : Any photo position attribute, a combination of attributes |
+ | * Default Value : OrbitPhotoId | ||
- | ** Example | + | Generalization of the trajectory visualization for different viewing scales. It is only recommended to change it in case if trajectory recorded with less than 1 point per meter. |
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | * Default Value : 10 | ||
+ | |||
+ | === Example === | ||
< | < | ||
Line 84: | Line 144: | ||
simplified.trajectory.part.separation 10 | simplified.trajectory.part.separation 10 | ||
photo.sequence.key OrbithPhotoId | photo.sequence.key OrbithPhotoId | ||
- | fixed.local.crs {PARAM_CRS} | ||
template.parameters=PARAM_CRS | template.parameters=PARAM_CRS | ||
</ | </ | ||
+ | If any of the parameters are changed after a Run was already imported the simplified trajectory needs to be recalculated. In order that to happen:\\ | ||
+ | - Delete trajectory_simplified.ovt\\ | ||
+ | - Open the Run --> Edit Run --> Re-Import Panorama. When you import panorama' | ||
+ | |||
+ | ==== Reference Height ==== | ||
+ | |||
+ | Mean terrain height. The value is used as a fall back value for the areas with missing DEM | ||
+ | * File : <Orbit Run>/ | ||
+ | * Parameter : '' | ||
+ | * Unit : meter | ||
+ | * Default value : 0 | ||
+ | |||
+ | ==== Reference Direction ==== | ||
+ | |||
+ | '' | ||
+ | Photo orientation offset (heading) between the reference north direction and the actual north flying axis. | ||
+ | * File : <Orbit Run>/ | ||
+ | * Parameter : '' | ||
+ | * Unit : degrees | ||
+ | * default value : 0° | ||
+ | * Positive rotation : clockwise | ||
+ | |||
+ | Photo orientation maximal deviation (heading) from the reference directions. All oblique images are assigned to one of the four flying axes based on their heading. The total angle which defines one flying axe class is defined as the reference direction of that flying axe plus twice the near margin value (once on each side of the axe). | ||
+ | * File : <Orbit Run>/ | ||
+ | * Parameter : '' | ||
+ | * Unit : degrees | ||
+ | * Default value : 10° | ||
+ | * Positive rotation : not applicable as this is an absolute value | ||
+ | |||
+ | ==== OrbitPhotoId Unique Image ID==== | ||
+ | |||
+ | The OrbitPhotoId must be a unique image id for the entire Mapping Run. \\ | ||
+ | Attention required if one run has multiple planar cameras having images with the same filename. Ensure the OrbitPhotoId value to be unique for all images of the entire Mapping Run. \\ | ||
+ | If needed use the " | ||
+ | |||
+ | ==== Timestamp Offset==== | ||
+ | |||
+ | Convert timestamp values from GPS Week Seconds to Absolute GPS Time and vice versa for Trajectory, Photo Positions and Point Cloud data. \\ | ||
+ | The offset between GPS Week Seconds to Absolute GPS Time. The value can be negative or positive. \\ | ||
+ | At " | ||
+ | |||
+ | === Trigger user to enter time offset at Create Run === | ||
+ | |||
+ | * File: <Orbit Run>/ | ||
+ | |||
+ | === Template Tag to be replaced by user-entered offset value === | ||
+ | |||
+ | Photo Positions | ||
+ | * File: <Orbit Run>/< | ||
+ | AttributeName=OrbitTimestamp | ||
+ | AttributeType=FLOAT8 | ||
+ | AttributeExpression=Add({PARAM_TIMESTAMP_OFFSET}, | ||
+ | |||
+ | Trajectory | ||
+ | * File: <Orbit Run>/ | ||
+ | AttributeName=OrbitTimestamp | ||
+ | AttributeType=FLOAT8 | ||
+ | AttributeExpression=Add({PARAM_TIMESTAMP_OFFSET}, | ||
+ | | ||
+ | Point Cloud | ||
+ | * File: <Orbit Run>/ | ||
+ | |||
+ | ==== Heading and Tilt==== | ||
+ | |||
+ | When no orientation heading and tilt are available, it can be calculated based on previous and next photo positions. | ||
+ | |||
+ | * File : <Orbit Run>/ | ||
+ | * Parameter : '' | ||
+ | * Values : image folder | ||
+ | |||
+ | === Example === | ||
+ | |||
+ | < | ||
+ | version 3 | ||
+ | project.type generic | ||
+ | project.file orbit_mm_run.omr | ||
+ | photo.camera.height 2.20 | ||
+ | template.pan_tilt.calculate panorama1 | ||
+ | template.parameters=PARAM_CRS | ||
+ | </ | ||
+ | |||
+ | ====== Video ====== | ||
+ | |||
+ | ===Supported formats=== | ||
+ | |||
+ | Preferably .mp4 files. \\ | ||
+ | When using cloud blob storage, the storage needs to support "range requests" | ||
- | ===== Configurations for Oblique Projects Only ===== | ||
+ | ===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. | ||
+ |
Last modified:: 2018/06/21 08:13