PIMs2MNT

List of commands

Description

In a prior step, PIMs computes depth map for each image. PIMs2Mnt merges these individual depth maps in a global digital surface (or elevation) model.
Name of this tool comes from "Per Image Matching" (PIM) and the French "Modèle Numérique de Terrain" (MNT) which is generally translated by "Digital Elevation Model" (DEM).

Syntax

The basic syntax for PIMs2MNT is:

mm3d PIMs2Mnt PIMsType NamedArgs

Mandatory unnamed arguments

 * string :: {Dir or PIM-Type (QuickMac ...)}

Authorized values are the same the types used with PIMs (Type in (Ground, Statue, Forest, TestIGN, QuickMac, MicMac, BigMac, MTDTmp).
The chosen type must have been computed at the prior step with the this tool.

Unmandatory named arguments

 * [Name=DS] REAL :: {Downscale, Def=1.0}
 * [Name=ZReg] REAL :: {Regularisation, context depend}
 * [Name=Repere] string :: {Repair (Euclid or Cyl)}
 * [Name=Pat] string :: {Pattern, def = all existing clouds}
 * [Name=DoMnt] bool :: { Compute DTM , def=true (use false to return only ortho)}
 * [Name=DoOrtho] bool :: {Generate ortho photo,  def=false}
 * [Name=MasqImGlob] string :: {Global Masq for ortho: if used, give full name of masq (e.g. MasqGlob.tif) }
 * [Name=Debug] bool :: {Debug !!!}
 * [Name=UseTA] bool :: {Use TA as filter when exist (Def=false)}
 * [Name=RI] REAL :: {Resol Im, def=1 }

Help

A basic help can be asked with

 mm3d PIMs2Mnt -help 

Workflow

PIms2MNT is part of the new pipeline of simplified tools for dense patching and orthorectification.

Previous Command : PIMs
Next Command : Tawny.

Example

• In the Cuxa Auto dataset, you can launch :

mm3d PIMs2Mnt BigMac DoMnt=1 DoOrtho=1

• An example included in the GrandLeez tutorial :

 mm3d Pims2MNT MicMac DoOrtho=1 

GUI

As for other tools, arguments can be chosen through a GUI using the command:

 vPIMs2MNT

Notes about DEM

PIMs generates DEMs which can be retrieved in the file :

 ...\PIMs-TmpBasc\PIMs-Merged_Prof.tif 

Generated DEM is not recorded in the coordinates system, even if it is georeferenced (with a TFW file). Difference stands in a translation and scale factor : by this way, it accommodates better the limitations of floating point precision on very high precision data.

They are stored in a local system which can be transform in the initial one using parameters specified in the file :

...\PIMs-TmpBasc\PIMs-ZNUM-Merged.xml 

Example of this file:

<?xml version="1.0" ?>
<FileOriMnt>
     <NameFileMnt>PIMs-Merged_Prof.tif</NameFileMnt>
     <NameFileMasque>PIMs-Merged_Masq.tif</NameFileMasque>
     <NombrePixels>6324 8584</NombrePixels>
     <OriginePlani>300.94499999999999 939.577</OriginePlani>
     <ResolutionPlani>0.00050000000000000001 -0.00050000000000000001</ResolutionPlani>
     <OrigineAlti>144.411</OrigineAlti>
     <ResolutionAlti>0.00050000000000000001</ResolutionAlti>
     <Geometrie>eGeomMNTEuclid</Geometrie>
</FileOriMnt>

FIXME which parameters has to be applied?
- ResolutionPlani as Z scale factor?
- ResolutionAlti as Z scale factor?
- +OriginePlani for the XY translation?
- +OrigineAlti for the Z translation?