Recent Changes

Differences

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

--- dev:desktop_ext:mapping:manage:runs_version [2021/03/22 17:42]
jeroen [Mapping Run Configurations]
+++ dev:desktop_ext:mapping:manage:runs_version [2024/03/06 18:55] (current)
glen [Mapping Run Configurations]
@@ Line 21: / Line 21: @@
 An Orbit Run version 3 uses the "orbit_mm_run.omr" file as a reference resource file. \\
 An Orbit Oblique Project version 3 uses the "orbit_oblique.oop" file as a reference resource file. \\
-This updated structure has been developed to optimize performance and to use new tools of the  [[dev:products:3dm_content_manager|]] and 3D Mapping Cloud.
+This updated structure has been developed to optimize performance and to use new tools of the  [[dev:products:3dm_manage_and_extract|]] and 3D Mapping Cloud.
 For previous version or to convert existing runs\projects into the updated structure, see [[110:mobile_mapping:desktop:mobile_mapping:manage:runs_version|]].
@@ Line 50: / Line 50: @@
 <note important>There is only one case when Orbit requires re-projecting of the data: in case if the input files are provided in feet-based CRS, we strongly recommend re-project into the corresponding meter based CRS. In all other cases, we advise keeping data as is as any conversion introduces in-accuracy.</note>
-==== Original image file extension ====
+==== Images file extension ====
 The used image storage format of original images (panorama or planar).
@@ Line 57: / Line 57: @@
   * Parameter : ''photo.file.extension''
   * Values : Any supported image resource can be used, see [[dev:technology:supported_formats:index|]].\\
-  * Default Value : *.jpg
+  * Default Value : .jpg
+=== Example ===
+<code>
+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
+</code>
 ==== Redirect image file directory ====
@@ Line 93: / Line 105: @@
 ==== Simplified Trajectory ====
-At import of photo positions or trajectory the trajectory simplified (coverage) will be created automatically if does not yet exist. The below settings can be used to adjust the defaults, as used in the example below.
+At import of photo positions or trajectory the trajectory simplified (coverage) will be created automatically if does not yet exist. The below settings can be used to adjust the defaults, as used in the example below. The creation of the Simplified Trajectory required the OrbitPhotoID to be unique for every image.
 Coordinate will be added if its perpendicular drop distance to the segment between the previous and next coordinate is larger than maximum.distance.
@@ Line 163: / Line 175: @@
   * 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 "concat" function to add a the camera name as prefix to create a unique image id.
+==== 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 "Create Run" the offset value can be entered by the user. The entered value will be used to replace the template place holder Tag  {PARAM_TIMESTAMP_OFFSET}.
+=== Trigger user to enter time offset at Create Run ===
+  * File: <Orbit Run>/orbit_mapping_run.omr (or orbit_mm_run.omr) \\ <code>template.parameters=PARAM_TIMESTAMP_OFFSET</code>
+=== Template Tag to be replaced by user-entered offset value ===
+Photo Positions
+  * File: <Orbit Run>/<camera>/import/import_locations.ord \\ <code>   AddAttribute=
+    AttributeName=OrbitTimestamp
+    AttributeType=FLOAT8
+    AttributeExpression=Add({PARAM_TIMESTAMP_OFFSET},[Imported Value])</code>
+Trajectory
+  * File: <Orbit Run>/trajectyory/import/import_trajectory.ord \\ <code>   AddAttribute=
+    AttributeName=OrbitTimestamp
+    AttributeType=FLOAT8
+    AttributeExpression=Add({PARAM_TIMESTAMP_OFFSET},[Imported Value])</code>
+Point Cloud
+  * File: <Orbit Run>/pointcloud/import/import.ini \\ <code>TimeOffset {PARAM_TIMESTAMP_OFFSET}</code>
+==== 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>/orbit_mm_run.omr
+  * Parameter : ''template.pan_tilt.calculate''
+  * Values : image folder
+=== Example ===
+<code>
+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
+</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

Last modified:: 2021/03/22 17:42