SaisieAppuisPredicQT : Différence entre versions

De MicMac
Aller à : navigation, rechercher
m (Fix typo and add internal link)
(Add notes about S2D S3D files and "Dubious", "Refuted", "Not captured" attributes)
Ligne 33 : Ligne 33 :
 
For example with the Saint-Michel de Cuxa data set :
 
For example with the Saint-Michel de Cuxa data set :
 
<pre>mm3d SaisieAppuisPredicQT "Abbey-.*jpg" RTL-Init AppRTL.xml MesureFinale.xml</pre>
 
<pre>mm3d SaisieAppuisPredicQT "Abbey-.*jpg" RTL-Init AppRTL.xml MesureFinale.xml</pre>
 +
 +
 +
== Notes ==
 +
=== XML file for image measurements  ===
 +
The last mandatory named argument is the name of an XML file where are stored points location relative to the image. But, in fact, if you specify "FileForImageMeasurements.xml" for this argument, two files will be created with slightly different names (and no one "FileForImageMeasurements.xml") :
 +
* FileForImageMeasurements-S2D.xml, which stores points 2D coordinates inside each image;
 +
* FileForImageMeasurements-S3D.xml, which stores points 3D coordinates, computed by spatial resection.
 +
 +
=== Validation of targeted points ===
 +
In the SaisieAppuisInitQt window, when you point a target you have to validate it by right click and "Validate" in the contextual menu to get the coordinates stored.
 +
Other values as "Dubious", "Refuted", "Not captured" [http://forum-micmac.forumprod.com/saisieappuispredicqt-attributes-of-gcp-t1409.html| seems to have the same effect] as a reverse of the validation.

Version du 24 avril 2017 à 10:18

Picto-liste.png List of commands

Description

It runs with the same arguments as SaisieAppuisInitQT.

Syntax

The global syntax for SaisieAppuispredicQT is

mm3d SaisieAppuisPredicQT FullName Orientation FileForGroundControlPoints FileForImageMeasurements NamedArgs

Help

You can access to the help by typing :

mm3d SaisieAppuisPredicQT -help

Mandatory unnamed args :

  • string :: {Full Name (Dir+Pattern)}
  • string :: {Orientation}
  • string :: {File for Ground Control Points}
  • string :: {File for Image Measurements}

Named args :

  • [Name=SzW] Pt2di :: {Size of global window (Def 800 800)}
  • [Name=NbF] Pt2di :: {Number of Sub Window (Def 2 2)}
  • [Name=WBlur] REAL :: {Size IN GROUND GEOMETRY of bluring for target}
  • [Name=Type] string :: {in [MaxLoc,MinLoc,GeoCube]}
  • [Name=ForceGray] bool :: {Force gray image, def=true}
  • [Name=OriMode] string :: {Orientation type (GRID) (Def=Std)}
  • [Name=ZMoy] REAL :: {Average Z, Mandatory in PB}
  • [Name=ZInc] REAL :: {Incertitude on Z, Mandatory in PB}
  • [Name=Masq3D] string :: {3D Masq used for visibility}
  • [Name=PIMsF] string :: {PIMs filter used for visibility}
  • [Name=InputSec] string :: {PIMs filter used for visibility}

Example

For example with the Saint-Michel de Cuxa data set :

mm3d SaisieAppuisPredicQT "Abbey-.*jpg" RTL-Init AppRTL.xml MesureFinale.xml


Notes

XML file for image measurements

The last mandatory named argument is the name of an XML file where are stored points location relative to the image. But, in fact, if you specify "FileForImageMeasurements.xml" for this argument, two files will be created with slightly different names (and no one "FileForImageMeasurements.xml") :

  • FileForImageMeasurements-S2D.xml, which stores points 2D coordinates inside each image;
  • FileForImageMeasurements-S3D.xml, which stores points 3D coordinates, computed by spatial resection.

Validation of targeted points

In the SaisieAppuisInitQt window, when you point a target you have to validate it by right click and "Validate" in the contextual menu to get the coordinates stored. Other values as "Dubious", "Refuted", "Not captured" seems to have the same effect as a reverse of the validation.