diff options
Diffstat (limited to 'man/man1/projinfo.1')
| -rw-r--r-- | man/man1/projinfo.1 | 73 |
1 files changed, 50 insertions, 23 deletions
diff --git a/man/man1/projinfo.1 b/man/man1/projinfo.1 index eb15ebc4..29017cb2 100644 --- a/man/man1/projinfo.1 +++ b/man/man1/projinfo.1 @@ -1,6 +1,6 @@ .\" Man page generated from reStructuredText. . -.TH "PROJINFO" "1" "Feb 14, 2019" "6.0.0" "PROJ.4" +.TH "PROJINFO" "1" "May 06, 2019" "6.1.0" "PROJ.4" .SH NAME projinfo \- Geodetic object and coordinate operation queries . @@ -36,26 +36,39 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .nf \fBprojinfo\fP .in +2 -[\-o formats] [\-k crs|operation] [\-\-summary] [\-q] -[[\-\-area name_or_code] | [\-\-bbox west_long,south_lat,east_long,north_lat]] -[\-\-spatial\-test contains|intersects] -[\-\-crs\-extent\-use none|both|intersection|smallest] -[\-\-grid\-check none|discard_missing|sort] [\-\-show\-superseded] -[\-\-pivot\-crs none|{auth:code[,auth:code]*}] -[\-\-boundcrs\-to\-wgs84] -[\-\-main\-db\-path path] [\-\-aux\-db\-path path]* -[\-\-identify] -[\-\-c\-ify] [\-\-single\-line] +[\-o formats] [\-k crs|operation|ellipsoid] [–summary] [\-q] +[[–area name_or_code] | [–bbox west_long,south_lat,east_long,north_lat]] +[–spatial\-test contains|intersects] +[–crs\-extent\-use none|both|intersection|smallest] +[–grid\-check none|discard_missing|sort] [–show\-superseded] +[–pivot\-crs always|if_no_direct_transformation|never|{auth:code[,auth:code]*}] +[–boundcrs\-to\-wgs84] +[–main\-db\-path path] [–aux\-db\-path path]* +[–identify] +[–c\-ify] [–single\-line] {object_definition} | (\-s {srs_def} \-t {srs_def}) .in -2 .fi .sp .sp -where {object_definition} or {object_definition} is a PROJ string, a -WKT string, an object name or a AUTHORITY:CODE -(where AUTHORITY is the name of a CRS authority and CODE the code of a CRS -found in the proj.db database). +where {object_definition} or {srs_def} is +.INDENT 0.0 +.IP \(bu 2 +a proj\-string, +.IP \(bu 2 +a WKT string, +.IP \(bu 2 +an object code (like “EPSG:4326”, “urn:ogc:def:crs:EPSG::4326”, +“urn:ogc:def:coordinateOperation:EPSG::1671”), +.IP \(bu 2 +a OGC URN combining references for compound coordinate reference systems +(e.g “\fI\%urn:ogc:def:crs,crs:EPSG::2393,crs:EPSG::5717\fP” or custom abbreviated +syntax “EPSG:2393+5717”), +.IP \(bu 2 +a OGC URN combining references for concatenated operations +(e.g. “\fI\%urn:ogc:def:coordinateOperation,coordinateOperation:EPSG::3895,coordinateOperation:EPSG::1618\fP”) +.UNINDENT .UNINDENT .UNINDENT .SH DESCRIPTION @@ -80,16 +93,16 @@ Except \fBall\fP and \fBdefault\fP, other formats can be preceded by \fB\-\fP to .UNINDENT .INDENT 0.0 .TP -.B \-k crs|operation +.B \-k crs|operation|ellipsoid When used to query a single object with a AUTHORITY:CODE, determines the (k)ind of the object -in case there are CRS or coordinate operations with the same CODE. +in case there are CRS, coordinate operations or ellipsoids with the same CODE. The default is crs. .UNINDENT .INDENT 0.0 .TP .B \-\-summary When listing coordinate operations available between 2 CRS, return the -result in a summary format, mentionning only the name of the coordinate +result in a summary format, mentioning only the name of the coordinate operation, its accuracy and its area of use. .sp \fBNOTE:\fP @@ -112,7 +125,7 @@ potentially compatible of being piped in other utilities. .B \-\-area name_or_code Specify an area of interest to restrict the results when researching coordinate operations between 2 CRS. The area of interest can be specified either -as a name (e.g "Denmark \- onshore") or a AUTHORITY:CODE (EPSG:3237) +as a name (e.g “Denmark \- onshore”) or a AUTHORITY:CODE (EPSG:3237) This option is exclusive of \fI\%\-\-bbox\fP\&. .sp \fBNOTE:\fP @@ -145,7 +158,7 @@ only used for coordinate operation computation .B \-\-spatial\-test contains|intersects Specify how the area of use of coordinate operations found in the database are compared to the area of use specified explicitly with \fI\%\-\-area\fP or \fI\%\-\-bbox\fP, -or derivedi implictly from the area of use of the source and target CRS. +or derived implicitly from the area of use of the source and target CRS. By default, projinfo will only keep coordinate operations whose are of use is strictly within the area of interest (\fBcontains\fP strategy). If using the \fBintersects\fP strategy, the spatial test is relaxed, and any @@ -223,12 +236,15 @@ only used for coordinate operation computation .UNINDENT .INDENT 0.0 .TP -.B \-\-pivot\-crs none|{auth:code[,auth:code]*} +.B \-\-pivot\-crs always|if_no_direct_transformation|never|{auth:code[,auth:code]*} Determine if intermediate (pivot) CRS can be used when researching coordinate operation between 2 CRS. A typical example is the WGS84 pivot. By default, -projinfo will consider any potential pivot. If using the \fBnone\fP strategy, +projinfo will consider any potential pivot if there is no direct transformation +( \fBif_no_direct_transformation\fP). If using the \fBnever\fP strategy, only direct transformations between the source and target CRS will be -used. It is also possible to restrict the pivot CRS to consider by specifying +used. If using the \fBalways\fP strategy, intermediate CRS will be considered +even if there are direct transformations. +It is also possible to restrict the pivot CRS to consider by specifying one or several CRS by their AUTHORITY:CODE. .sp \fBNOTE:\fP @@ -263,6 +279,17 @@ The option may be repeated to specify several auxiliary databases. .UNINDENT .INDENT 0.0 .TP +.B \-\-identify +When used with an object definition, this queries the PROJ database to find +known objects, typically CRS, that are close or identical to the object. +Each candidate object is associated with an approximate likelihood percentage. +This is useful when used with a WKT string that lacks a EPSG identifier, +such as ESRI WKT1. This might also be used with PROJ strings. +For example, \fI+proj=utm +zone=31 +datum=WGS84 +type=crs\fP will be identified +with a likelihood of 70% to EPSG:32631 +.UNINDENT +.INDENT 0.0 +.TP .B \-\-c\-ify For developers only. Modify the string output of the utility so that it is easy to put those strings in C/C++ code |