PIMs2Mnt - Historique des versions

Mgaudin : Redirect PIMs2Mnt to PIMs2MNT

2018-07-25T07:43:49Z

Redirect PIMs2Mnt to PIMs2MNT

XavierR le 3 juillet 2017 à 13:13

2017-07-03T13:13:45Z

XavierR : Creation

2017-07-03T13:10:20Z

Creation

Nouvelle page

[[Image:picto-liste.png|25px]] [[Command|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 requires an argument :
<pre>mm3d PIMs2Mnt PIMsType </pre>

===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 [[PIMs|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
<pre> mm3d PIMs2Mnt -help </pre> 

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

[[Image:Picto-previous.png|20px]] Previous Command : [[PIMs]] 
[[Image:Picto-next.png|20px]] Next Command : [[Tawny]].

==Example==
An example included in the [[GrandLeez|GrandLeez tutorial]] :

<pre> mm3d Pims2MNT MicMac DoOrtho=1 </pre>

==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 :
<pre> ...\PIMs-TmpBasc\PIMs-Merged_Prof.tif </pre>

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 :
<pre>...\PIMs-TmpBasc\PIMs-ZNUM-Merged.xml </pre>

Example of this file:
<pre><?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>
</pre>

'' '''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?''

@@ Ligne 78 : / Ligne 78 : @@
 '' '''FIXME''' which parameters has to be applied? <br>
-- ResolutionPlani as Z scale factor? <br>
+''- ResolutionPlani as Z scale factor? <br>''
-- ResolutionAlti as Z scale factor? <br>
+''- ResolutionAlti as Z scale factor? <br>''
-- +'OriginePlani' for the XY translation? <br>
+''- +OriginePlani for the XY translation? <br>''
-- +'OrigineAlti' for the Z translation?'' <br>
+''- +OrigineAlti for the Z translation?'' <br>''

@@ Ligne 1 : / Ligne 1 : @@
-[[Image:picto-liste.png|25px]] [[Command|List of commands]]
+#REDIRECT [[PIMs2MNT]]
-==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.
-<br>
-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 requires an argument :
-<pre>mm3d PIMs2Mnt PIMsType </pre>
-−
-===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). <br>
-The chosen type must have been computed at the prior step with the [[PIMs|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
-<pre> mm3d PIMs2Mnt -help </pre> <br>
-−
-−
-==Workflow==
-PIms2MNT is part of the new pipeline of simplified tools for dense patching and orthorectification.<br>
-−
-[[Image:Picto-previous.png|20px]] Previous Command : [[PIMs]]<br>
-[[Image:Picto-next.png|20px]] Next Command : [[Tawny]].
-−
-−
-==Example==
-An example included in the [[GrandLeez|GrandLeez tutorial]] :
-−
-<pre> mm3d Pims2MNT MicMac DoOrtho=1 </pre>
-−
-−
-==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 :
-<pre> ...\PIMs-TmpBasc\PIMs-Merged_Prof.tif </pre>
-−
-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 :
-<pre>...\PIMs-TmpBasc\PIMs-ZNUM-Merged.xml </pre>
-−
-Example of this file:
-<pre><?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>
-</pre>
-−
-'' '''FIXME''' which parameters has to be applied? <br>
-''- ResolutionPlani as Z scale factor? <br>''
-''- ResolutionAlti as Z scale factor? <br>''
-''- +OriginePlani for the XY translation? <br>''
-''- +OrigineAlti for the Z translation?'' <br>''