Generate a RPC sensor model

Brief Description

Generate a RPC sensor model from a list of Ground Control Points.

Tags

Geometry

Long Description

This application generates a RPC sensor model from a list of Ground Control Points. At least 20 points are required for estimation without elevation support, and 40 points for estimation with elevation support. Elevation support will be automatically deactivated if an insufficient amount of points is provided. The application can optionally output a file containing accuracy statistics for each point, and a vector file containing segments representing points residues. The map projection parameter allows defining a map projection in which the accuracy is evaluated.

Parameters

Output geom file (outgeom): Geom file containing the generated RPC sensor model
Input file containing tie points (inpoints): Input file containing tie points. Points are stored in following format: col row lon lat. Spaced by a space or tab character. Line beginning with # are ignored.
Output file containing output precision statistics (outstat): Output file containing the following info: ref_lon ref_lat elevation predicted_lon predicted_lat x_error_ref(meters) y_error_ref(meters) global_error_ref(meters) x_error(meters) y_error(meters) overall_error(meters)
Output vector file with residues (outvector): File containing segments representing residues
Map Projection (map): Defines the map projection to be used.
- Universal Trans-Mercator (UTM) (utm): A system of transverse mercator projections dividing the surface of Earth between 80S and 84N latitude.
  - Zone number (map.utm.zone): The zone number ranges from 1 to 60 and allows defining the transverse mercator projection (along with the hemisphere)
  - Northern Hemisphere (map.utm.northhem): The transverse mercator projections are defined by their zone number as well as the hemisphere. Activate this parameter if your image is in the northern hemisphere.
- Lambert II Etendu (lambert2): This is a Lambert Conformal Conic projection mainly used in France.
- Lambert93 (lambert93): This is a Lambert 93 projection mainly used in France.
- WGS 84 (wgs): This is a Geographical projection
- EPSG Code (epsg): This code is a generic way of identifying map projections, and allows specifying a large amount of them. See www.spatialreference.org to find which EPSG code is associated to your projection;
  - EPSG Code (map.epsg.code): See www.spatialreference.org to find which EPSG code is associated to your projection

Elevation management (elev): This group of parameters allows managing elevation values. Supported formats are SRTM, DTED or any geotiff. DownloadSRTMTiles application could be a useful tool to list/download tiles related to a product.
- DEM directory (elev.dem): This parameter allows selecting a directory containing Digital Elevation Model files. Note that this directory should contain only DEM files. Unexpected behaviour might occurs if other images are found in this directory.
- Geoid File (elev.geoid): Use a geoid grid to get the height above the ellipsoid in case there is no DEM available, no coverage for some points or pixels with no_data in the DEM tiles. A version of the geoid can be found on the OTB website(https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb-data/blob/master/Input/DEM/egm96.grd).
- Default elevation (elev.default): This parameter allows setting the default height above ellipsoid when there is no DEM available, no coverage for some points or pixels with no_data in the DEM tiles, and no geoid file has been set. This is also used by some application as an average elevation value.

Load otb application from xml file (inxml): Load otb application from xml file
Save otb application to xml file (outxml): Save otb application to xml file

Limitations

None

Authors

OTB-Team