7 files changed, 91 insertions, 33 deletions
diff --git a/man/man1/cct.1 b/man/man1/cct.1
index c7274fd0..45780009 100644
--- a/man/man1/cct.1
+++ b/man/man1/cct.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "CCT" "1" "Feb 17, 2020" "7.0.0" "PROJ"
+.TH "CCT" "1" "Jul 1, 2020" "7.1.0" "PROJ"
 .SH NAME
 cct \- Coordinate Conversion and Transformation
 .
diff --git a/man/man1/cs2cs.1 b/man/man1/cs2cs.1
index 8efd8706..8ff3cb0a 100644
--- a/man/man1/cs2cs.1
+++ b/man/man1/cs2cs.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "CS2CS" "1" "Feb 17, 2020" "7.0.0" "PROJ"
+.TH "CS2CS" "1" "Jul 1, 2020" "7.1.0" "PROJ"
 .SH NAME
 cs2cs \- Cartographic coordinate system filter
 .
@@ -40,26 +40,24 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 or
 .INDENT 0.0
 .INDENT 3.5
-\fBcs2cs\fP [\fB\-eEfIlrstvwW\fP [args]] {source_crs} +to {target_crs} file …
+\fBcs2cs\fP [\fB\-eEfIlrstvwW\fP [args]] {source_crs} {target_crs} file …
 .sp
 where {source_crs} or {target_crs} is a PROJ string, a WKT string 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), expressing a coordinate reference system.
-.UNINDENT
-.UNINDENT
 .sp
 New in version 6.0.0.
 
 .sp
-or
+\fBNOTE:\fP
 .INDENT 0.0
 .INDENT 3.5
-\fBcs2cs\fP [\fB\-eEfIlrstvwW\fP [args]] {source_crs} {target_crs}
+before 7.0.1, it was needed to add +to between {source_crs} and {target_crs}
+when adding a filename
+.UNINDENT
+.UNINDENT
 .UNINDENT
 .UNINDENT
-.sp
-New in version 6.0.0.
-
 .SH DESCRIPTION
 .sp
 \fBcs2cs\fP performs transformation between the source and destination
@@ -131,14 +129,18 @@ List of all distance units that can be selected with the \fI+units\fP parameter.
 .INDENT 0.0
 .TP
 .B \-r
-This options reverses the order of the expected input from
-longitude\-latitude or x\-y to latitude\-longitude or y\-x.
+This options reverses the order of the first two expected
+inputs from that specified by the CRS to the opposite
+order.  The third coordinate, typically height, remains
+third.
 .UNINDENT
 .INDENT 0.0
 .TP
 .B \-s
-This options reverses the order of the output from x\-y or longitude\-latitude
-to y\-x or latitude\-longitude.
+This options reverses the order of the first two expected
+outputs from that specified by the CRS to the opposite
+order.  The third coordinate, typically height, remains
+third.
 .UNINDENT
 .INDENT 0.0
 .TP
diff --git a/man/man1/geod.1 b/man/man1/geod.1
index a94ff24c..5ba4e995 100644
--- a/man/man1/geod.1
+++ b/man/man1/geod.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "GEOD" "1" "Feb 17, 2020" "7.0.0" "PROJ"
+.TH "GEOD" "1" "Jul 1, 2020" "7.1.0" "PROJ"
 .SH NAME
 geod \- Geodesic computations
 .
diff --git a/man/man1/gie.1 b/man/man1/gie.1
index e5e6aaf9..6cef00e7 100644
--- a/man/man1/gie.1
+++ b/man/man1/gie.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "GIE" "1" "Feb 17, 2020" "7.0.0" "PROJ"
+.TH "GIE" "1" "Jul 1, 2020" "7.1.0" "PROJ"
 .SH NAME
 gie \- The Geospatial Integrity Investigation Environment
 .
@@ -438,6 +438,40 @@ expect  0   110579.9
 .UNINDENT
 .UNINDENT
 .UNINDENT
+.SH STRICT MODE
+.sp
+New in version 7.1.
+
+.sp
+A stricter variant of normal gie syntax can be used by wrapping gie commands
+between \fB<gie\-strict>\fP and \fB</gie\-strict>\fP\&. In strict mode, comment lines
+must start with a sharp character. Unknown commands will be considered as an error.
+A command can still be split on several lines, but intermediate lines must
+end with the space character followed by backslash to mark the continuation.
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+<gie\-strict>
+# This is a comment. The following line with multiple repeated characters too
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+# A command on several lines must use " \e" continuation
+operation proj=hgridshift +grids=nzgd2kgrid0005.gsb \e
+          ellps=GRS80
+tolerance 1 mm
+ignore    pjd_err_failed_to_load_grid
+accept    172.999892181021551 \-45.001620431954613
+expect    173                 \-45
+</gie\-strict>
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .SH BACKGROUND
 .sp
 More importantly than being an acronym for “Geospatial Integrity Investigation
diff --git a/man/man1/proj.1 b/man/man1/proj.1
index f1c1bd16..7927c35f 100644
--- a/man/man1/proj.1
+++ b/man/man1/proj.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "PROJ" "1" "Feb 17, 2020" "7.0.0" "PROJ"
+.TH "PROJ" "1" "Jul 1, 2020" "7.1.0" "PROJ"
 .SH NAME
 proj \- Cartographic projection filter
 .
@@ -208,7 +208,7 @@ For ASCII input data the two data values must be in the first two white space
 separated fields and when both input and output are ASCII all trailing
 portions of the input line are appended to the output line.
 .sp
-Input geographic data (longitude and latitude) must be in DMS format and input
+Input geographic data (longitude and latitude) must be in DMS or decimal degrees format and input
 cartesian data must be in units consistent with the ellipsoid major axis or
 sphere radius units. Output geographic coordinates will be in DMS (if the
 \fB\-w\fP switch is not employed) and precise to 0.001” with trailing, zero\-valued
diff --git a/man/man1/projinfo.1 b/man/man1/projinfo.1
index 3dbc41a1..829c1bd1 100644
--- a/man/man1/projinfo.1
+++ b/man/man1/projinfo.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "PROJINFO" "1" "Feb 17, 2020" "7.0.0" "PROJ"
+.TH "PROJINFO" "1" "Jul 1, 2020" "7.1.0" "PROJ"
 .SH NAME
 projinfo \- Geodetic object and coordinate operation queries
 .
@@ -40,8 +40,9 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 [[–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|known_available] [–show\-superseded]
+[–grid\-check none|discard_missing|sort|known_available]
 [–pivot\-crs always|if_no_direct_transformation|never|{auth:code[,auth:code]*}]
+[–show\-superseded] [–hide\-ballpark]
 [–boundcrs\-to\-wgs84]
 [–main\-db\-path path] [–aux\-db\-path path]*
 [–identify] [–3d]
@@ -63,6 +64,9 @@ a WKT string,
 an object code (like “EPSG:4326”, “urn:ogc:def:crs:EPSG::4326”,
 “urn:ogc:def:coordinateOperation:EPSG::1671”),
 .IP \(bu 2
+an Object name. e.g “WGS 84”, “WGS 84 / UTM zone 31N”. In that case as
+uniqueness is not guaranteed, heuristics are applied to determine the appropriate best match.
+.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”),
@@ -76,6 +80,8 @@ a OGC URN combining references for concatenated operations
 (e.g. “\fI\%urn:ogc:def:coordinateOperation,coordinateOperation:EPSG::3895,coordinateOperation:EPSG::1618\fP”)
 .IP \(bu 2
 a PROJJSON string. The jsonschema is at \fI\%https://proj.org/schemas/v0.1/projjson.schema.json\fP (\fIadded in 6.2\fP)
+.IP \(bu 2
+a compound CRS made from two object names separated with ” + “. e.g. “WGS 84 + EGM96 height” (\fIadded in 7.1\fP)
 .UNINDENT
 .sp
 {object_reference} is a filename preceded by the ‘@’ character.  The
@@ -252,7 +258,27 @@ only used for coordinate operation computation
 .UNINDENT
 .INDENT 0.0
 .TP
-.B \-show\-superseded
+.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 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. 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
+.INDENT 7.0
+.INDENT 3.5
+only used for coordinate operation computation
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-show\-superseded
 When enabled, coordinate operations that are superseded by others will be
 listed. Note that supersession is not equivalent to deprecation: superseded
 operations are still considered valid although they have a better equivalent,
@@ -268,16 +294,12 @@ only used for coordinate operation computation
 .UNINDENT
 .INDENT 0.0
 .TP
-.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 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. 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.
+.B \-\-hide\-ballpark
+New in version 7.1.
+
+.sp
+Hides any coordinate operation that is, or contains, a
+Ballpark transformation
 .sp
 \fBNOTE:\fP
 .INDENT 7.0
diff --git a/man/man1/projsync.1 b/man/man1/projsync.1
index 1779bf2e..14e96fb9 100644
--- a/man/man1/projsync.1
+++ b/man/man1/projsync.1
@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "PROJSYNC" "1" "Feb 17, 2020" "7.0.0" "PROJ"
+.TH "PROJSYNC" "1" "Ju1 1, 2020" "7.1.0" "PROJ"
 .SH NAME
 projsync \- Downloading tool of resource files
 .
@@ -144,7 +144,7 @@ Quiet mode
 .INDENT 0.0
 .TP
 .B \-\-dry\-run
-Simulate the behaviour of the tool without downloading resource files.
+Simulate the behavior of the tool without downloading resource files.
 .UNINDENT
 .INDENT 0.0
 .TP