aboutsummaryrefslogtreecommitdiff
path: root/_sources/apps/projinfo.rst.txt
diff options
context:
space:
mode:
authorPROJ deploybot <proj.bot@proj.bot>2022-03-22 20:00:06 +0000
committerPROJ deploybot <proj.bot@proj.bot>2022-03-22 20:00:06 +0000
commita3f43744feec86272fe532124679d3a013ef9a8c (patch)
tree27e4198db6011e3097eb7bcfe7197684aba7583a /_sources/apps/projinfo.rst.txt
downloadPROJ-gh-pages.tar.gz
PROJ-gh-pages.zip
update with results of commit https://github.com/OSGeo/PROJ/commit/53c07a8bd211b7aee4bc07a9c6726005504b7181gh-pages
Diffstat (limited to '_sources/apps/projinfo.rst.txt')
-rw-r--r--_sources/apps/projinfo.rst.txt606
1 files changed, 606 insertions, 0 deletions
diff --git a/_sources/apps/projinfo.rst.txt b/_sources/apps/projinfo.rst.txt
new file mode 100644
index 00000000..04ee7578
--- /dev/null
+++ b/_sources/apps/projinfo.rst.txt
@@ -0,0 +1,606 @@
+.. _projinfo:
+
+================================================================================
+projinfo
+================================================================================
+
+.. Index:: projinfo
+
+.. only:: html
+
+ .. versionadded:: 6.0.0
+
+ Geodetic object and coordinate operation queries
+
+Synopsis
+********
+
+ | **projinfo**
+ | [-o formats] [-k crs|operation|datum|ensemble|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|known_available]
+ | [--pivot-crs always|if_no_direct_transformation|never|{auth:code[,auth:code]*}]
+ | [--show-superseded] [--hide-ballpark] [--accuracy {accuracy}]
+ | [--allow-ellipsoidal-height-as-vertical-crs]
+ | [--boundcrs-to-wgs84]
+ | [--authority name]
+ | [--main-db-path path] [--aux-db-path path]*
+ | [--dump-db-structure]
+ | [--identify] [--3d]
+ | [--output-id AUTH:CODE]
+ | [--c-ify] [--single-line]
+ | --searchpaths | --remote-data |
+ | --list-crs [list-crs-filter] |
+ | --dump-db-structure [{object_definition} | {object_reference}] |
+ | {object_definition} | {object_reference} | (-s {srs_def} -t {srs_def})
+ |
+
+ where {object_definition} or {srs_def} is one of the possibilities accepted
+ by :c:func:`proj_create`
+
+ - a proj-string,
+ - a WKT string,
+ - an object code (like "EPSG:4326", "urn:ogc:def:crs:EPSG::4326",
+ "urn:ogc:def:coordinateOperation:EPSG::1671"),
+ - 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.
+ - a OGC URN combining references for compound coordinate reference systems
+ (e.g "urn:ogc:def:crs,crs:EPSG::2393,crs:EPSG::5717" or custom abbreviated
+ syntax "EPSG:2393+5717"),
+ - a OGC URN combining references for references for projected or derived CRSs
+ e.g. for Projected 3D CRS "UTM zone 31N / WGS 84 (3D)":
+ "urn:ogc:def:crs,crs:EPSG::4979,cs:PROJ::ENh,coordinateOperation:EPSG::16031"
+ (*added in 6.2*)
+ - a OGC URN combining references for concatenated operations
+ (e.g. "urn:ogc:def:coordinateOperation,coordinateOperation:EPSG::3895,coordinateOperation:EPSG::1618")
+ - a PROJJSON string. The jsonschema is at https://proj.org/schemas/v0.4/projjson.schema.json (*added in 6.2*)
+ - a compound CRS made from two object names separated with " + ". e.g. "WGS 84 + EGM96 height" (*added in 7.1*)
+
+ {object_reference} is a filename preceded by the '@' character. The
+ file referenced by the {object_reference} must contain a valid
+ {object_definition}.
+
+Description
+***********
+
+:program:`projinfo` is a program that can query information on a geodetic object,
+coordinate reference system (CRS) or coordinate operation, when the ``-s`` and ``-t``
+options are specified, and display it under different formats (PROJ string, WKT string
+or PROJJSON string).
+
+It can also be used to query coordinate operations available between two CRS.
+
+The program is named with some reference to the GDAL :program:`gdalsrsinfo` that offers
+partly similar services.
+
+
+The following control parameters can appear in any order:
+
+.. program:: projinfo
+
+.. option:: -o formats
+
+ formats is a comma separated combination of:
+ ``all``, ``default``, ``PROJ``, ``WKT_ALL``, ``WKT2:2015``, ``WKT2:2019``, ``WKT1:GDAL``, ``WKT1:ESRI``, ``PROJJSON``, ``SQL``.
+
+ Except ``all`` and ``default``, other formats can be preceded by ``-`` to disable them.
+
+ .. note:: WKT2_2019 was previously called WKT2_2018.
+
+ .. note:: Before PROJ 6.3.0, WKT1:GDAL was implicitly calling --boundcrs-to-wgs84.
+ This is no longer the case.
+
+ .. note:: When SQL is specified, :option:`--output-id` must be specified.
+
+.. option:: -k crs|operation|datum|ensemble|ellipsoid
+
+ When used to query a single object with a AUTHORITY:CODE, determines the (k)ind of the object
+ in case there are CRS, coordinate operations or ellipsoids with the same CODE.
+ The default is crs.
+
+.. option:: --summary
+
+ When listing coordinate operations available between 2 CRS, return the
+ result in a summary format, mentioning only the name of the coordinate
+ operation, its accuracy and its area of use.
+
+ .. note:: only used for coordinate operation computation
+
+.. option:: -q
+
+ Turn on quiet mode. Quiet mode is only available for queries on single objects,
+ and only one output format is selected. In that mode, only the PROJ, WKT or PROJJSON
+ string is displayed, without other introduction output. The output is then
+ potentially compatible of being piped in other utilities.
+
+.. option:: --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)
+ This option is exclusive of :option:`--bbox`.
+
+ .. note:: only used for coordinate operation computation
+
+.. option:: --bbox west_long,south_lat,east_long,north_lat
+
+ Specify an area of interest to restrict the results when researching
+ coordinate operations between 2 CRS. The area of interest is specified as a
+ bounding box with geographic coordinates, expressed in degrees in a
+ unspecified geographic CRS.
+ `west_long` and `east_long` should be in the [-180,180] range, and
+ `south_lat` and `north_lat` in the [-90,90]. `west_long` is generally lower than
+ `east_long`, except in the case where the area of interest crosses the antimeridian.
+
+ .. note:: only used for coordinate operation computation
+
+.. option:: --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 :option:`--area` or :option:`--bbox`,
+ or derived implicitly from the area of use of the source and target CRS.
+ By default, :program:`projinfo` will only keep coordinate operations whose are of use
+ is strictly within the area of interest (``contains`` strategy).
+ If using the ``intersects`` strategy, the spatial test is relaxed, and any
+ coordinate operation whose area of use at least partly intersects the
+ area of interest is listed.
+
+ .. note:: only used for coordinate operation computation
+
+.. option:: --crs-extent-use none|both|intersection|smallest
+
+ Specify which area of interest to consider when no explicit one is specified
+ with :option:`--area` or :option:`--bbox` options.
+ By default (``smallest`` strategy), the area of
+ use of the source or target CRS will be looked, and the one that is the
+ smallest one in terms of area will be used as the area of interest.
+ If using ``none``, no area of interest is used.
+ If using ``both``, only coordinate operations that relate (contain or intersect
+ depending of the :option:`--spatial-test` strategy) to the area of use of both CRS
+ are selected.
+ If using ``intersection``, the area of interest is the intersection of the
+ bounding box of the area of use of the source and target CRS
+
+ .. note:: only used for coordinate operation computation
+
+.. option:: --grid-check none|discard_missing|sort|known_available
+
+ Specify how the presence or absence of a horizontal or vertical shift grid
+ required for a coordinate operation affects the results returned when
+ researching coordinate operations between 2 CRS.
+ The default strategy is ``sort`` (if :envvar:`PROJ_NETWORK` is not defined).
+ In that case, all candidate
+ operations are returned, but the actual availability of the grids is used
+ to determine the sorting order. That is, if a coordinate operation involves
+ using a grid that is not available in the PROJ resource directories
+ (determined by the :envvar:`PROJ_LIB` environment variable, it will be listed in
+ the bottom of the results.
+ The ``none`` strategy completely disables the checks of presence of grids and
+ this returns the results as if all the grids where available.
+ The ``discard_missing`` strategy discards results that involve grids not
+ present in the PROJ resource directories.
+ The ``known_available`` strategy discards results that involve grids not
+ present in the PROJ resource directories and that are not known of the CDN.
+ This is the default strategy is :envvar:`PROJ_NETWORK` is set to ``ON``.
+
+ .. note:: only used for coordinate operation computation
+
+.. option:: --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,
+ :program:`projinfo` will consider any potential pivot if there is no direct transformation
+ ( ``if_no_direct_transformation``). If using the ``never`` strategy,
+ only direct transformations between the source and target CRS will be
+ used. If using the ``always`` 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.
+
+ .. note:: only used for coordinate operation computation
+
+.. option:: --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,
+ whereas deprecated operations have been determined to be erroneous and are
+ not considered at all.
+
+ .. note:: only used for coordinate operation computation
+
+.. option:: --hide-ballpark
+
+ .. versionadded:: 7.1
+
+ Hides any coordinate operation that is, or contains, a
+ :term:`Ballpark transformation`
+
+ .. note:: only used for coordinate operation computation
+
+.. option:: --accuracy {accuracy}
+
+ .. versionadded:: 8.0
+
+ Sets the minimum desired accuracy for returned coordinate operations.
+
+ .. note:: only used for coordinate operation computation
+
+.. option:: --allow-ellipsoidal-height-as-vertical-crs
+
+ .. versionadded:: 8.0
+
+ Allows exporting a geographic or projected 3D CRS as a compound CRS whose
+ vertical CRS represents the ellipsoidal height.
+
+ .. note:: only used for CRS, and with WKT1:GDAL output format
+
+.. option:: --boundcrs-to-wgs84
+
+ When specified, this option researches a coordinate operation from the
+ base geographic CRS of the single CRS, source or target CRS to the WGS84
+ geographic CRS, and if found, wraps those CRS into a BoundCRS object.
+ This is mostly to be used for early-binding approaches.
+
+.. option:: --authority name
+
+ Specify the name of the authority into which to restrict looks up for
+ objects, when specifying an object by name or when coordinate operations are
+ computed. The default is to allow all authorities.
+
+ When used with SQL output, this restricts the authorities to which intermediate
+ objects can belong to (the default is EPSG and PROJ). Note that the authority
+ of the :option:`--output-id` option will also be implicitly added.
+
+.. option:: --main-db-path path
+
+ Specify the name and path of the database to be used by :program:`projinfo`.
+ The default is :file:`proj.db` in the PROJ resource directories.
+
+.. option:: --aux-db-path path
+
+ Specify the name and path of auxiliary databases, that are to be combined
+ with the main database. Those auxiliary databases must have a table
+ structure that is identical to the main database, but can be partly filled
+ and their entries can refer to entries of the main database.
+ The option may be repeated to specify several auxiliary databases.
+
+.. option:: --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, `+proj=utm +zone=31 +datum=WGS84 +type=crs` will be identified
+ with a likelihood of 70% to EPSG:32631
+
+.. option:: --dump-db-structure
+
+ .. versionadded:: 8.1
+
+ Outputs the sequence of SQL statements to create a new empty valid auxiliary
+ database. This option can be specified as the only switch of the utility.
+ If also specifying a CRS object and the :option:`--output-id` option, the
+ definition of the object as SQL statements will be appended.
+
+.. option:: --list-crs [list-crs-filter]
+
+ .. versionadded:: 8.1
+
+ Outputs a list (authority name:code and CRS name) of the filtered CRSs from the database.
+ If no filter is provided all authority names and types of non deprecated CRSs are dumped.
+ list-crs-filter is a comma separated combination of: allow_deprecated,geodetic,geocentric,
+ geographic,geographic_2d,geographic_3d,vertical,projected,compound.
+ Affected by options :option:`--authority`, :option:`--area`, :option:`--bbox` and :option:`--spatial-test`
+
+.. option:: --3d
+
+ .. versionadded:: 6.3
+
+ "Promote" the CRS(s) to their 3D version. In the context of researching
+ available coordinate transformations, explicitly specifying this option is
+ not necessary, because when one of the source or target CRS has a vertical
+ component but not the other one, the one that has no vertical component is
+ automatically promoted to a 3D version, where its vertical axis is the
+ ellipsoidal height in metres, using the ellipsoid of the base geodetic CRS.
+
+.. option:: --output-id=AUTH:NAME
+
+ .. versionadded:: 8.1
+
+ Identifier to assign to the object (for SQL output).
+
+ It is strongly recommended that new objects should not be added in common
+ registries, such as ``EPSG``, ``ESRI``, ``IAU``, etc.
+ Users should use a custom authority name instead. If a new object should be
+ added to the official EPSG registry, users are invited to follow the
+ procedure explained at https://epsg.org/dataset-change-requests.html.
+
+ Combined with :option:`--dump-db-structure`, users can create
+ auxiliary databases, instead of directly modifying the main :file:`proj.db` database.
+ See the :ref:`example how to export to an auxiliary database <projinfo_aux_db_example>`.
+
+ Those auxiliary databases can be specified through
+ :cpp:func:`proj_context_set_database_path` or the :envvar:`PROJ_AUX_DB`
+ environment variable.
+
+.. option:: --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
+
+.. option:: --single-line
+
+ Output PROJ, WKT or PROJJSON strings on a single line, instead of multiple
+ indented lines by default.
+
+.. option:: --searchpaths
+
+ .. versionadded:: 7.0
+
+ Output the directories into which PROJ resources will be looked for
+ (if not using C API such as :cpp:func:`proj_context_set_search_paths`
+ that will override them.
+
+.. option:: --remote-data
+
+ .. versionadded:: 7.0
+
+ Display information regarding if :ref:`network` is enabled, and the
+ related URL.
+
+Examples
+********
+
+1. Query the CRS object corresponding to EPSG:4326
+
+.. code-block:: console
+
+ projinfo EPSG:4326
+
+Output:
+
+::
+
+ PROJ.4 string:
+ +proj=longlat +datum=WGS84 +no_defs +type=crs
+
+ WKT2:2019 string:
+ GEOGCRS["WGS 84",
+ DATUM["World Geodetic System 1984",
+ ELLIPSOID["WGS 84",6378137,298.257223563,
+ LENGTHUNIT["metre",1]]],
+ PRIMEM["Greenwich",0,
+ ANGLEUNIT["degree",0.0174532925199433]],
+ CS[ellipsoidal,2],
+ AXIS["geodetic latitude (Lat)",north,
+ ORDER[1],
+ ANGLEUNIT["degree",0.0174532925199433]],
+ AXIS["geodetic longitude (Lon)",east,
+ ORDER[2],
+ ANGLEUNIT["degree",0.0174532925199433]],
+ USAGE[
+ SCOPE["unknown"],
+ AREA["World"],
+ BBOX[-90,-180,90,180]],
+ ID["EPSG",4326]]
+
+
+2. List the coordinate operations between NAD27 (designed with its CRS name)
+ and NAD83 (designed with its EPSG code 4269) within an area of interest
+
+.. code-block:: console
+
+ projinfo -s NAD27 -t EPSG:4269 --area "USA - Missouri"
+
+Output:
+
+::
+
+ DERIVED_FROM(EPSG):1241, NAD27 to NAD83 (1), 0.15 m, USA - CONUS including EEZ
+
+ PROJ string:
+ +proj=pipeline +step +proj=axisswap +order=2,1 +step +proj=unitconvert \
+ +xy_in=deg +xy_out=rad +step +proj=hgridshift +grids=conus \
+ +step +proj=unitconvert +xy_in=rad +xy_out=deg +step +proj=axisswap +order=2,1
+
+ WKT2:2019 string:
+ COORDINATEOPERATION["NAD27 to NAD83 (1)",
+ SOURCECRS[
+ GEOGCRS["NAD27",
+ DATUM["North American Datum 1927",
+ ELLIPSOID["Clarke 1866",6378206.4,294.978698213898,
+ LENGTHUNIT["metre",1]]],
+ PRIMEM["Greenwich",0,
+ ANGLEUNIT["degree",0.0174532925199433]],
+ CS[ellipsoidal,2],
+ AXIS["geodetic latitude (Lat)",north,
+ ORDER[1],
+ ANGLEUNIT["degree",0.0174532925199433]],
+ AXIS["geodetic longitude (Lon)",east,
+ ORDER[2],
+ ANGLEUNIT["degree",0.0174532925199433]]]],
+ TARGETCRS[
+ GEOGCRS["NAD83",
+ DATUM["North American Datum 1983",
+ ELLIPSOID["GRS 1980",6378137,298.257222101,
+ LENGTHUNIT["metre",1]]],
+ PRIMEM["Greenwich",0,
+ ANGLEUNIT["degree",0.0174532925199433]],
+ CS[ellipsoidal,2],
+ AXIS["geodetic latitude (Lat)",north,
+ ORDER[1],
+ ANGLEUNIT["degree",0.0174532925199433]],
+ AXIS["geodetic longitude (Lon)",east,
+ ORDER[2],
+ ANGLEUNIT["degree",0.0174532925199433]]]],
+ METHOD["CTABLE2"],
+ PARAMETERFILE["Latitude and longitude difference file","conus"],
+ OPERATIONACCURACY[0.15],
+ USAGE[
+ SCOPE["unknown"],
+ AREA["USA - CONUS including EEZ"],
+ BBOX[23.81,-129.17,49.38,-65.69]],
+ ID["DERIVED_FROM(EPSG)",1241]]
+
+3. Export an object as a PROJJSON string
+
+.. code-block:: console
+
+ projinfo GDA94 -o PROJJSON -q
+
+Output:
+
+.. code-block:: json
+
+ {
+ "type": "GeographicCRS",
+ "name": "GDA94",
+ "datum": {
+ "type": "GeodeticReferenceFrame",
+ "name": "Geocentric Datum of Australia 1994",
+ "ellipsoid": {
+ "name": "GRS 1980",
+ "semi_major_axis": 6378137,
+ "inverse_flattening": 298.257222101
+ }
+ },
+ "coordinate_system": {
+ "subtype": "ellipsoidal",
+ "axis": [
+ {
+ "name": "Geodetic latitude",
+ "abbreviation": "Lat",
+ "direction": "north",
+ "unit": "degree"
+ },
+ {
+ "name": "Geodetic longitude",
+ "abbreviation": "Lon",
+ "direction": "east",
+ "unit": "degree"
+ }
+ ]
+ },
+ "area": "Australia - GDA",
+ "bbox": {
+ "south_latitude": -60.56,
+ "west_longitude": 93.41,
+ "north_latitude": -8.47,
+ "east_longitude": 173.35
+ },
+ "id": {
+ "authority": "EPSG",
+ "code": 4283
+ }
+ }
+
+.. _projinfo_aux_db_example:
+
+4. Exporting the SQL statements to insert a new CRS in an auxiliary database.
+
+.. code-block:: console
+
+ # Get the SQL statements for a custom CRS
+ projinfo "+proj=merc +lat_ts=5 +datum=WGS84 +type=crs +title=my_crs" --output-id HOBU:MY_CRS -o SQL -q > my_crs.sql
+ cat my_crs.sql
+
+ # Initialize an auxiliary database with the schema of the reference database
+ echo ".schema" | sqlite3 /path/to/proj.db | sqlite3 aux.db
+
+ # Append the content of the definition of HOBU:MY_CRS
+ sqlite3 aux.db < my_crs.db
+
+ # Check that everything works OK
+ projinfo --aux-db-path aux.db HOBU:MY_CRS
+
+or more simply:
+
+.. code-block:: console
+
+ # Create an auxiliary database with the definition of a custom CRS.
+ projinfo "+proj=merc +lat_ts=5 +datum=WGS84 +type=crs +title=my_crs" --output-id HOBU:MY_CRS --dump-db-structure | sqlite3 aux.db
+
+ # Check that everything works OK
+ projinfo --aux-db-path aux.db HOBU:MY_CRS
+
+Output:
+
+.. code-block:: sql
+
+ INSERT INTO geodetic_crs VALUES('HOBU','GEODETIC_CRS_MY_CRS','unknown','','geographic 2D','EPSG','6424','EPSG','6326',NULL,0);
+ INSERT INTO usage VALUES('HOBU','USAGE_GEODETIC_CRS_MY_CRS','geodetic_crs','HOBU','GEODETIC_CRS_MY_CRS','PROJ','EXTENT_UNKNOWN','PROJ','SCOPE_UNKNOWN');
+ INSERT INTO conversion VALUES('HOBU','CONVERSION_MY_CRS','unknown','','EPSG','9805','Mercator (variant B)','EPSG','8823','Latitude of 1st standard parallel',5,'EPSG','9122','EPSG','8802','Longitude of natural origin',0,'EPSG','9122','EPSG','8806','False easting',0,'EPSG','9001','EPSG','8807','False northing',0,'EPSG','9001',NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,0);
+ INSERT INTO usage VALUES('HOBU','USAGE_CONVERSION_MY_CRS','conversion','HOBU','CONVERSION_MY_CRS','PROJ','EXTENT_UNKNOWN','PROJ','SCOPE_UNKNOWN');
+ INSERT INTO projected_crs VALUES('HOBU','MY_CRS','my_crs','','EPSG','4400','HOBU','GEODETIC_CRS_MY_CRS','HOBU','CONVERSION_MY_CRS',NULL,0);
+ INSERT INTO usage VALUES('HOBU','USAGE_PROJECTED_CRS_MY_CRS','projected_crs','HOBU','MY_CRS','PROJ','EXTENT_UNKNOWN','PROJ','SCOPE_UNKNOWN');
+
+::
+
+ PROJ.4 string:
+ +proj=merc +lat_ts=5 +lon_0=0 +x_0=0 +y_0=0 +datum=WGS84 +units=m +no_defs +type=crs
+
+ WKT2:2019 string:
+ PROJCRS["my_crs",
+ BASEGEOGCRS["unknown",
+ ENSEMBLE["World Geodetic System 1984 ensemble",
+ MEMBER["World Geodetic System 1984 (Transit)"],
+ MEMBER["World Geodetic System 1984 (G730)"],
+ MEMBER["World Geodetic System 1984 (G873)"],
+ MEMBER["World Geodetic System 1984 (G1150)"],
+ MEMBER["World Geodetic System 1984 (G1674)"],
+ MEMBER["World Geodetic System 1984 (G1762)"],
+ ELLIPSOID["WGS 84",6378137,298.257223563,
+ LENGTHUNIT["metre",1]],
+ ENSEMBLEACCURACY[2.0]],
+ PRIMEM["Greenwich",0,
+ ANGLEUNIT["degree",0.0174532925199433]],
+ ID["HOBU","GEODETIC_CRS_MY_CRS"]],
+ CONVERSION["unknown",
+ METHOD["Mercator (variant B)",
+ ID["EPSG",9805]],
+ PARAMETER["Latitude of 1st standard parallel",5,
+ ANGLEUNIT["degree",0.0174532925199433],
+ ID["EPSG",8823]],
+ PARAMETER["Longitude of natural origin",0,
+ ANGLEUNIT["degree",0.0174532925199433],
+ ID["EPSG",8802]],
+ PARAMETER["False easting",0,
+ LENGTHUNIT["metre",1],
+ ID["EPSG",8806]],
+ PARAMETER["False northing",0,
+ LENGTHUNIT["metre",1],
+ ID["EPSG",8807]]],
+ CS[Cartesian,2],
+ AXIS["(E)",east,
+ ORDER[1],
+ LENGTHUNIT["metre",1]],
+ AXIS["(N)",north,
+ ORDER[2],
+ LENGTHUNIT["metre",1]],
+ ID["HOBU","MY_CRS"]]
+
+5. Get the WKT representation of EPSG:25832 in the WKT1:GDAL output format and on a single line
+
+.. code-block:: console
+
+ projinfo -o WKT1:GDAL --single-line EPSG:25832
+
+Output:
+
+::
+
+ WKT1:GDAL string:
+ PROJCS["ETRS89 / UTM zone 32N",GEOGCS["ETRS89",DATUM["European_Terrestrial_Reference_System_1989",SPHEROID["GRS 1980",6378137,298.257222101,AUTHORITY["EPSG","7019"]],AUTHORITY["EPSG","6258"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.0174532925199433,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4258"]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",0],PARAMETER["central_meridian",9],PARAMETER["scale_factor",0.9996],PARAMETER["false_easting",500000],PARAMETER["false_northing",0],UNIT["metre",1,AUTHORITY["EPSG","9001"]],AXIS["Easting",EAST],AXIS["Northing",NORTH],AUTHORITY["EPSG","25832"]]
+
+.. only:: man
+
+ See also
+ ********
+
+ **cs2cs(1)**, **cct(1)**, **geod(1)**, **gie(1)**, **proj(1)**, **projsync(1)**
+
+ .. include:: common_man.rst