Skip to main content
Skip table of contents

Managing Blocks

Once data QC is done for session data, the user can create blocks to organize data into processing units for the following processing steps.

HxMap blocks are defined by:

  • having a name and description for identification

  • a collection of strips from one or more processed session

  • default elevation source to be used in processing (global DEM, constant height etc)

  • default coordinate system used to process the block in

Blocks are used to subdivide/combine area for triangulation or product generation

Creating a new block

To create a block, first expand the data source tree to the strip/flight plan level for an easy selection of strips. Select the strips to be added to the block.

Webcam images (e.g. captured during a TerrainMapper flight) cannot be added to a block, as they are not supposed to be used for further processing.

From the ‘Edit’ menu, select ‘Create Block …’ and enter the required attributes for the new block as shown below:

Notes on CRS Selection:

  • Horizontal and Vertical coordinate system will default to the last used CRS

  • Most Recent Used dropdown saves the last five used coordinate systems chosen by the user for block creation

Once the Block is created, it is added to the Data Source tree. Furthermore, a block folder is added to the specified location. This folder includes subfolders representing the used camera, a reference to the selected project data as well as a *_QC.xml (optional). The *_QC.xml contains amongst others the link of the image data to any assigned radiometric profile.

Block data layout

*.hexblk

HxMap Block

"Session"

Block Session

Holds folder per processed session
Each Session folder holds separate folders representing included strips from the processed session added to the Block
Each Session folder hold strip/cam metadata from the processed session that is copied to the block

/cam

*.hexstp

Strip files

*.hexrad

Radiometric corrections

Dark pixel, Gradient and Radiometric adjustment correction per strip (depending on the sensor)

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.