Skip to content

Commit 615ea82

Browse files
committed
Update man-pages from Sphinx-docs
1 parent db78a84 commit 615ea82

File tree

7 files changed

+159
-159
lines changed

7 files changed

+159
-159
lines changed

man/man1/cct.1

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
2727
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
2828
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
2929
..
30-
.TH "CCT" "1" "Mar 1, 2023" "9.2.0" "PROJ"
30+
.TH "CCT" "1" "May 24, 2023" "9.2.1" "PROJ"
3131
.SH NAME
3232
cct \- Coordinate Conversion and Transformation
3333
.SH SYNOPSIS
@@ -54,13 +54,13 @@ a proj\-string,
5454
.IP \(bu 2
5555
a WKT string,
5656
.IP \(bu 2
57-
an object code (like \(dqEPSG:1671\(dq \(dqurn:ogc:def:coordinateOperation:EPSG::1671\(dq),
57+
an object code (like "EPSG:1671" "urn:ogc:def:coordinateOperation:EPSG::1671"),
5858
.IP \(bu 2
59-
an object name. e.g. \(dqITRF2014 to ETRF2014 (1)\(dq. In that case as
59+
an object name. e.g. "ITRF2014 to ETRF2014 (1)". In that case as
6060
uniqueness is not guaranteed, heuristics are applied to determine the appropriate best match.
6161
.IP \(bu 2
6262
a OGC URN combining references for concatenated operations
63-
(e.g. \(dq\fI\%urn:ogc:def:coordinateOperation,coordinateOperation:EPSG::3895,coordinateOperation:EPSG::1618\fP\(dq)
63+
(e.g. "\fI\%urn:ogc:def:coordinateOperation,coordinateOperation:EPSG::3895,coordinateOperation:EPSG::1618\fP")
6464
.IP \(bu 2
6565
a PROJJSON string. The jsonschema is at \fI\%https://proj.org/schemas/v0.4/projjson.schema.json\fP
6666
.UNINDENT
@@ -162,7 +162,7 @@ Usage varies with operation.
162162
\fI\%cct\fP is an acronym meaning \fICoordinate Conversion and Transformation\fP\&.
163163
.sp
164164
The acronym refers to definitions given in the OGC 08\-015r2/ISO\-19111
165-
standard \(dqGeographical Information \-\- Spatial Referencing by Coordinates\(dq,
165+
standard "Geographical Information \-\- Spatial Referencing by Coordinates",
166166
which defines two different classes of \fIcoordinate operations\fP:
167167
.sp
168168
\fICoordinate Conversions\fP, which are coordinate operations where input
@@ -319,7 +319,7 @@ Coordinate operation referenced through its name
319319
.sp
320320
.nf
321321
.ft C
322-
$ echo 3541657.3778 948984.2343 5201383.5231 2020.5 | cct \(dqITRF2014 to ETRF2014 (1)\(dq
322+
$ echo 3541657.3778 948984.2343 5201383.5231 2020.5 | cct "ITRF2014 to ETRF2014 (1)"
323323
3541657.9112 948983.7503 5201383.2482 2020.5000
324324
.ft P
325325
.fi

man/man1/cs2cs.1

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
2727
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
2828
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
2929
..
30-
.TH "CS2CS" "1" "Mar 1, 2023" "9.2.0" "PROJ"
30+
.TH "CS2CS" "1" "May 24, 2023" "9.2.1" "PROJ"
3131
.SH NAME
3232
cs2cs \- Cartographic coordinate system filter
3333
.SH SYNOPSIS
@@ -53,29 +53,29 @@ a proj\-string,
5353
.IP \(bu 2
5454
a WKT string,
5555
.IP \(bu 2
56-
an object code (like \(dqEPSG:4326\(dq, \(dqurn:ogc:def:crs:EPSG::4326\(dq,
57-
\(dqurn: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"),
5858
.IP \(bu 2
59-
an Object name. e.g \(dqWGS 84\(dq, \(dqWGS 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
6060
uniqueness is not guaranteed, heuristics are applied to determine the appropriate best match.
6161
.IP \(bu 2
62-
a CRS name and a coordinate epoch, separated with \(aq@\(aq. For example \(dq\fI\%[email protected]\fP\(dq. (\fIadded in 9.2\fP)
62+
a CRS name and a coordinate epoch, separated with \(aq@\(aq. For example "\fI\%[email protected]\fP". (\fIadded in 9.2\fP)
6363
.IP \(bu 2
6464
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 \(dqEPSG: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"),
6767
.IP \(bu 2
6868
a OGC URN combining references for references for projected or derived CRSs
69-
e.g. for Projected 3D CRS \(dqUTM 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"
7171
(\fIadded in 6.2\fP)
7272
.IP \(bu 2
7373
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")
7575
.IP \(bu 2
7676
a PROJJSON string. The jsonschema is at \fI\%https://proj.org/schemas/v0.4/projjson.schema.json\fP (\fIadded in 6.2\fP)
7777
.IP \(bu 2
78-
a compound CRS made from two object names separated with \(dq + \(dq. e.g. \(dqWGS 84 + EGM96 height\(dq (\fIadded in 7.1\fP)
78+
a compound CRS made from two object names separated with " + ". e.g. "WGS 84 + EGM96 height" (\fIadded in 7.1\fP)
7979
.UNINDENT
8080
.sp
8181
New in version 6.0.0.
@@ -181,7 +181,7 @@ third.
181181
Where \fIformat\fP is a printf format string to control the form of the output values.
182182
For inverse projections, the output will be in degrees when this option is
183183
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
185185
projection and DMS for inverse.
186186
.UNINDENT
187187
.INDENT 0.0
@@ -211,7 +211,7 @@ New in version 8.0.0.
211211
.sp
212212
Specify an area of interest to restrict the results when researching
213213
coordinate operations between 2 CRS. The area of interest can be specified either
214-
as a name (e.g \(dqDenmark \- onshore\(dq) or a AUTHORITY:CODE (EPSG:3237)
214+
as a name (e.g "Denmark \- onshore") or a AUTHORITY:CODE (EPSG:3237)
215215
.sp
216216
This option is mutually exclusive with \fI\%\-\-bbox\fP\&.
217217
.UNINDENT
@@ -288,7 +288,7 @@ This option is mutually exclusive with \fI\%\-\-bbox\fP\&.
288288
New in version 9.1.
289289

290290
.sp
291-
\(dqPromote\(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
292292
ellipsoidal height in metres, using the ellipsoid of the base geodetic CRS.
293293
Depending on PROJ versions and the exact nature of the CRS involved,
294294
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
352352
.nf
353353
.ft C
354354
cs2cs +proj=latlong +datum=NAD83 +to +proj=utm +zone=10 +datum=NAD27 \-r <<EOF
355-
45°15\(aq33.1\(dq 111.5W
355+
45°15\(aq33.1" 111.5W
356356
45d15.551666667N \-111d30
357357
+45.25919444444 111d30\(aq000w
358358
EOF
@@ -468,7 +468,7 @@ UTM Zone 31N/WGS 84 with WGS84 ellipsoidal height
468468
.sp
469469
.nf
470470
.ft C
471-
echo 45 2 0 | cs2cs \(dqWGS 84 + EGM96 height\(dq \(dqWGS 84 / UTM zone 31N\(dq \-\-3d
471+
echo 45 2 0 | cs2cs "WGS 84 + EGM96 height" "WGS 84 / UTM zone 31N" \-\-3d
472472
.ft P
473473
.fi
474474
.UNINDENT

man/man1/geod.1

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
2727
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
2828
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
2929
..
30-
.TH "GEOD" "1" "Mar 1, 2023" "9.2.0" "PROJ"
30+
.TH "GEOD" "1" "May 24, 2023" "9.2.1" "PROJ"
3131
.SH NAME
3232
geod \- Geodesic computations
3333
.SH SYNOPSIS
@@ -92,7 +92,7 @@ geographic coordinate values. The default mode is DMS.
9292
.TP
9393
.B \-F <format>
9494
Where \fIformat\fP is a printf format string to control the output form of the distance
95-
value. The default mode is \fB\(dq%.3f\(dq\fP\&.
95+
value. The default mode is \fB"%.3f"\fP\&.
9696
.UNINDENT
9797
.INDENT 0.0
9898
.TP
@@ -141,7 +141,7 @@ azimuthal data must be in decimal degrees or DMS format and
141141
input distance data must be in units consistent with the ellipsoid
142142
major axis or sphere radius units. The latitude must lie
143143
in the range [\-90d,90d]. Output geographic coordinates will be
144-
in DMS (if the \fI\%\-f\fP switch is not employed) to 0.001\(dq with trailing,
144+
in DMS (if the \fI\%\-f\fP switch is not employed) to 0.001" with trailing,
145145
zero\-valued minute\-second fields deleted. Output distance
146146
data will be in the same units as the ellipsoid or sphere
147147
radius.
@@ -189,7 +189,7 @@ which gives the results:
189189
.sp
190190
.nf
191191
.ft C
192-
\-66d31\(aq50.141\(dq 75d39\(aq13.083\(dq 2587.504
192+
\-66d31\(aq50.141" 75d39\(aq13.083" 2587.504
193193
.ft P
194194
.fi
195195
.UNINDENT
@@ -206,7 +206,7 @@ and determine Portland\(aqs location by azimuth and distance:
206206
.nf
207207
.ft C
208208
geod +ellps=clrk66 +units=us\-mi <<EOF
209-
42d15\(aqN 71d07\(aqW \-66d31\(aq50.141\(dq 2587.504
209+
42d15\(aqN 71d07\(aqW \-66d31\(aq50.141" 2587.504
210210
EOF
211211
.ft P
212212
.fi
@@ -219,7 +219,7 @@ which gives:
219219
.sp
220220
.nf
221221
.ft C
222-
45d31\(aq0.003\(dqN 123d40\(aq59.985\(dqW 75d39\(aq13.094\(dq
222+
45d31\(aq0.003"N 123d40\(aq59.985"W 75d39\(aq13.094"
223223
.ft P
224224
.fi
225225
.UNINDENT

man/man1/gie.1

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
2727
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
2828
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
2929
..
30-
.TH "GIE" "1" "Mar 1, 2023" "9.2.0" "PROJ"
30+
.TH "GIE" "1" "May 24, 2023" "9.2.1" "PROJ"
3131
.SH NAME
3232
gie \- The Geospatial Integrity Investigation Environment
3333
.SH SYNOPSIS
@@ -343,7 +343,7 @@ expect 12 55 0 0
343343
.UNINDENT
344344
.UNINDENT
345345
.sp
346-
The default direction is \(dqforward\(dq.
346+
The default direction is "forward".
347347
.UNINDENT
348348
.INDENT 0.0
349349
.TP
@@ -458,7 +458,7 @@ end with the space character followed by backslash to mark the continuation.
458458
<gie\-strict>
459459
# This is a comment. The following line with multiple repeated characters too
460460
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
461-
# A command on several lines must use \(dq \e\(dq continuation
461+
# A command on several lines must use " \e" continuation
462462
operation proj=hgridshift +grids=nzgd2kgrid0005.gsb \e
463463
ellps=GRS80
464464
tolerance 1 mm
@@ -474,8 +474,8 @@ expect 173 \-45
474474
.UNINDENT
475475
.SH BACKGROUND
476476
.sp
477-
More importantly than being an acronym for \(dqGeospatial Integrity Investigation
478-
Environment\(dq, gie were also the initials, user id, and USGS email address of
477+
More importantly than being an acronym for "Geospatial Integrity Investigation
478+
Environment", gie were also the initials, user id, and USGS email address of
479479
Gerald Ian Evenden (1935\-\-2016), the geospatial visionary, who, already in the
480480
1980s, started what was to become the PROJ of today.
481481
.sp
@@ -497,7 +497,7 @@ call like \fBhypot(x,y)\fP\&.
497497
.sp
498498
While today, we may have more formally well defined metadata systems (most
499499
prominent the OGC WKT2 representation), nothing comes close being as easily
500-
readable (\(dqhuman compatible\(dq) as Gerald\(aqs key\-value system. This system in
500+
readable ("human compatible") as Gerald\(aqs key\-value system. This system in
501501
particular, and the PROJ system in general, was Gerald\(aqs great gift to anyone
502502
using and/or communicating about geodata.
503503
.sp

man/man1/proj.1

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
2727
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
2828
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
2929
..
30-
.TH "PROJ" "1" "Mar 1, 2023" "9.2.0" "PROJ"
30+
.TH "PROJ" "1" "May 24, 2023" "9.2.1" "PROJ"
3131
.SH NAME
3232
proj \- Cartographic projection filter
3333
.SH SYNOPSIS
@@ -163,7 +163,7 @@ reciprocal value of \fImult\fP is employed.
163163
.B \-f <format>
164164
Where \fIformat\fP is a printf format string to control the form of the output values.
165165
For inverse projections, the output will be in degrees when this option is
166-
employed. The default format is \fB\(dq%.2f\(dq\fP for forward projection and DMS for
166+
employed. The default format is \fB"%.2f"\fP for forward projection and DMS for
167167
inverse.
168168
.UNINDENT
169169
.INDENT 0.0
@@ -211,7 +211,7 @@ portions of the input line are appended to the output line.
211211
Input geographic data (longitude and latitude) must be in DMS or decimal degrees format and input
212212
cartesian data must be in units consistent with the ellipsoid major axis or
213213
sphere radius units. Output geographic coordinates will be in DMS (if the
214-
\fB\-w\fP switch is not employed) and precise to 0.001\(dq with trailing, zero\-valued
214+
\fB\-w\fP switch is not employed) and precise to 0.001" with trailing, zero\-valued
215215
minute\-second fields deleted.
216216
.SH EXAMPLE
217217
.sp
@@ -222,7 +222,7 @@ The following script
222222
.nf
223223
.ft C
224224
proj +proj=utm +lon_0=112w +ellps=clrk66 \-r <<EOF
225-
45d15\(aq33.1\(dq 111.5W
225+
45d15\(aq33.1" 111.5W
226226
45d15.551666667N \-111d30
227227
+45.25919444444 111d30\(aq000w
228228
EOF

0 commit comments

Comments
 (0)