@@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
27
27
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
28
28
.in \\n[ rst2man-indent\\n[ rst2man-indent-level ] ]u
29
29
..
30
- .TH "CS2CS" "1" "Mar 1 , 2023" "9.2.0 " "PROJ"
30
+ .TH "CS2CS" "1" "May 24 , 2023" "9.2.1 " "PROJ"
31
31
.SH NAME
32
32
cs2cs \- Cartographic coordinate system filter
33
33
.SH SYNOPSIS
@@ -53,29 +53,29 @@ a proj\-string,
53
53
.IP \(bu 2
54
54
a WKT string,
55
55
.IP \(bu 2
56
- an object code (like \( dq EPSG :4326\( dq , \( dq urn :ogc:def:crs:EPSG::4326\( dq ,
57
- \( dq urn :ogc:def:coordinateOperation:EPSG::1671\( dq ),
56
+ an object code (like "EPSG :4326", "urn :ogc:def:crs:EPSG::4326" ,
57
+ "urn :ogc:def:coordinateOperation:EPSG::1671" ),
58
58
.IP \(bu 2
59
- an Object name. e.g \( dq WGS 84\( dq , \( dq WGS 84 / UTM zone 31N\( dq . In that case as
59
+ an Object name. e.g "WGS 84", "WGS 84 / UTM zone 31N" . In that case as
60
60
uniqueness is not guaranteed, heuristics are applied to determine the appropriate best match.
61
61
.IP \(bu 2
62
- a CRS name and a coordinate epoch, separated with
\(aq @
\(aq . For example
\( dq \ fI\% [email protected] \fP \( dq . (
\fI added in 9.2 \fP )
62
+ a CRS name and a coordinate epoch, separated with
\(aq @
\(aq . For example
" \ fI\% [email protected] \fP " . (
\fI added in 9.2 \fP )
63
63
.IP \(bu 2
64
64
a OGC URN combining references for compound coordinate reference systems
65
- (e.g \( dq \ fI\% urn:ogc:def:crs,crs:EPSG::2393,crs:EPSG::5717 \fP \( dq or custom abbreviated
66
- syntax \( dq EPSG :2393+5717\( dq ),
65
+ (e.g " \ fI\% urn:ogc:def:crs,crs:EPSG::2393,crs:EPSG::5717 \fP " or custom abbreviated
66
+ syntax "EPSG :2393+5717" ),
67
67
.IP \(bu 2
68
68
a OGC URN combining references for references for projected or derived CRSs
69
- e.g. for Projected 3D CRS \( dq UTM zone 31N / WGS 84 (3D)\( dq :
70
- \( dq \ fI\% urn:ogc:def:crs,crs:EPSG::4979,cs:PROJ::ENh,coordinateOperation:EPSG::16031 \fP \( dq
69
+ e.g. for Projected 3D CRS "UTM zone 31N / WGS 84 (3D)" :
70
+ " \ fI\% urn:ogc:def:crs,crs:EPSG::4979,cs:PROJ::ENh,coordinateOperation:EPSG::16031 \fP "
71
71
(\fI added in 6.2 \fP )
72
72
.IP \(bu 2
73
73
a OGC URN combining references for concatenated operations
74
- (e.g. \( dq \ fI\% urn:ogc:def:coordinateOperation,coordinateOperation:EPSG::3895,coordinateOperation:EPSG::1618 \fP \( dq )
74
+ (e.g. " \ fI\% urn:ogc:def:coordinateOperation,coordinateOperation:EPSG::3895,coordinateOperation:EPSG::1618 \fP " )
75
75
.IP \(bu 2
76
76
a PROJJSON string. The jsonschema is at \fI \% https://proj.org/schemas/v0.4/projjson.schema.json \fP (\fI added in 6.2 \fP )
77
77
.IP \(bu 2
78
- a compound CRS made from two object names separated with \( dq + \( dq . e.g. \( dq WGS 84 + EGM96 height\( dq (\fI added in 7.1 \fP )
78
+ a compound CRS made from two object names separated with " + " . e.g. "WGS 84 + EGM96 height" (\fI added in 7.1 \fP )
79
79
.UNINDENT
80
80
.sp
81
81
New in version 6.0.0.
@@ -181,7 +181,7 @@ third.
181
181
Where \fI format \fP is a printf format string to control the form of the output values.
182
182
For inverse projections, the output will be in degrees when this option is
183
183
employed. If a format is specified for inverse projection the output data
184
- will be in decimal degrees. The default format is \fB \( dq %.2f \( dq \fP for forward
184
+ will be in decimal degrees. The default format is \fB " %.2f" \fP for forward
185
185
projection and DMS for inverse.
186
186
.UNINDENT
187
187
.INDENT 0.0
@@ -211,7 +211,7 @@ New in version 8.0.0.
211
211
.sp
212
212
Specify an area of interest to restrict the results when researching
213
213
coordinate operations between 2 CRS. The area of interest can be specified either
214
- as a name (e.g \( dq Denmark \- onshore\( dq ) or a AUTHORITY:CODE (EPSG:3237)
214
+ as a name (e.g "Denmark \- onshore" ) or a AUTHORITY:CODE (EPSG:3237)
215
215
.sp
216
216
This option is mutually exclusive with \fI \% \-\- bbox \fP \& .
217
217
.UNINDENT
@@ -288,7 +288,7 @@ This option is mutually exclusive with \fI\%\-\-bbox\fP\&.
288
288
New in version 9.1.
289
289
290
290
.sp
291
- \( dq Promote \( dq 2D CRS(s) to their 3D version, where the vertical axis is the
291
+ "Promote" 2D CRS(s) to their 3D version, where the vertical axis is the
292
292
ellipsoidal height in metres, using the ellipsoid of the base geodetic CRS.
293
293
Depending on PROJ versions and the exact nature of the CRS involved,
294
294
especially before PROJ 9.1, a mix of 2D and 3D CRS could lead to 2D or 3D
@@ -352,7 +352,7 @@ The following script
352
352
.nf
353
353
.ft C
354
354
cs2cs +proj=latlong +datum=NAD83 +to +proj=utm +zone=10 +datum=NAD27 \- r <<EOF
355
- 45°15\(aq 33.1\( dq 111.5W
355
+ 45°15\(aq 33.1" 111.5W
356
356
45d15.551666667N \- 111d30
357
357
+45.25919444444 111d30\(aq 000w
358
358
EOF
@@ -468,7 +468,7 @@ UTM Zone 31N/WGS 84 with WGS84 ellipsoidal height
468
468
.sp
469
469
.nf
470
470
.ft C
471
- echo 45 2 0 | cs2cs \( dq WGS 84 + EGM96 height\( dq \( dq WGS 84 / UTM zone 31N\( dq \-\- 3d
471
+ echo 45 2 0 | cs2cs "WGS 84 + EGM96 height" "WGS 84 / UTM zone 31N" \-\- 3d
472
472
.ft P
473
473
.fi
474
474
.UNINDENT
0 commit comments