Export to third-party applications
For downstream processing of images the WFM allows the user to generate metadata and external orientation for the images and export them in different formats.
The export functionality is accessed from the "Tools -> Export EOP " menu item, which is available in the different perspectives. Prerequisite are selected objects, for which the EOP output is desired. The dialog allows to pick any of the above mentioned formats, the output reference coordinate system and the output location. Select the "Use adjusted orientation" box to export adjusted EOP parameter derived from a triangulation run. If no adjusted EOP exist or is just partially available for the selected items, a warning will be given and no data is exported. Note that Images that have failed QC will also not be exported.
In case the user wishes to export camera parameter alongside with the EOP information, it is required to customize the export options (see next section). For a DMC III, the camera parameter can differ depending on the reference sensor (high resolution PAN or low resolution multispectral camera specification). Therefore the user can pick the reference sensor for exporting the camera parameter.
Supported export options
HxMap currently exports to the following applications:
GORI
Simple Text files that have both Interior and Exterior parameters for each image individually and used in legacy Tridicon 3D Modelling workflows (CityModeller, BuildingFinder, TextureMapper etc) or third-party Mesh engines.
LPS/Orima
Exterior and IPT files for triangulation workflow
Note: only the initial non-adjusted exterior orientation is exported in this format since it is mainly used to execute the bundle block adjustment externally
IPAS CO+
Metadata files required in the self calibration process:
photoId.txt: Photo ID file is an text file. Each line contains the following information:
Event GPS Time (units are seconds)
Photo ID
Installation_settings_RCD30_XXXXX.ini: contains the lever arms values for the camera system installation as entered in the Leica FCMS system for the camera. XXXXX is replaced with the camera head serial number.
event.evt : camera event file is an text file.
CSV
True EOP: a text file providing exterior orientation parameter. In case of a selected map projection, the different scales for horizontal and vertical components are properly considered.
Best Fit EOP to Map projection: a text file providing exterior orientation parameter. In case of a selected map projection, a Z scaling is applied to have an identical scaling in the horizontal and vertical component (single photo resection). This allows to treat the projected coordinate system as an LSR system and is required for various DPW.
Customize CSV Export
HxMap allows to customize the entries exported into the CSV files as well as their order. En- or disable items and change their order via drag & drop using the Export EOP (CSV) feature available in the Tools > Settings menu. Apply with "OK".
If SensorID is part of the the exported items, a user will find an additional CSV (*.iop) alongside with the EOP CSV. The *.iop includes all relevant camera parameter required to setup a camera in a 3rd party DPW.
Export EOP
Allows to export EO parameter into one of the following formats:
GORI
CSV – True EOP
CSV – Best Fit EOP
LPS files (will include beside EO parameter also point measurements)
User can decide to export given or adjusted EO parameter as well as the desired reference frame.
Export Footprints
Exporting footprints is possible for a raw session (in Session Perspective) or a session or block in QC perspective or product generation perspective. Before running export items to export need to be checked first. Once the output folder is selected, HxMap will create a set of shapefiles including metadata into that location.