1PROJINFO(1)                          PROJ                          PROJINFO(1)
2
3
4

NAME

6       projinfo - Geodetic object and coordinate operation queries
7

SYNOPSIS

9          projinfo
10            [-o formats] [-k crs|operation|datum|ensemble|ellipsoid] [--summary] [-q]
11            [[--area name_or_code] | [--bbox west_long,south_lat,east_long,north_lat]]
12            [--spatial-test contains|intersects]
13            [--crs-extent-use none|both|intersection|smallest]
14            [--grid-check none|discard_missing|sort|known_available]
15            [--pivot-crs always|if_no_direct_transformation|never|{auth:code[,auth:code]*}]
16            [--show-superseded] [--hide-ballpark] [--accuracy {accuracy}]
17            [--allow-ellipsoidal-height-as-vertical-crs]
18            [--boundcrs-to-wgs84]
19            [--authority name]
20            [--main-db-path path] [--aux-db-path path]*
21            [--dump-db-structure]
22            [--identify] [--3d]
23            [--output-id AUTH:CODE]
24            [--c-ify] [--single-line]
25            --searchpaths | --remote-data |
26            --list-crs [list-crs-filter] |
27            --dump-db-structure [{object_definition} | {object_reference}] |
28            {object_definition} | {object_reference} | (-s {srs_def} -t {srs_def})
29
30
31
32          where  {object_definition}  or {srs_def} is one of the possibilities
33          accepted by proj_create()
34
35          • a proj-string,
36
37          • a WKT string,
38
39          • an object code  (like  "EPSG:4326",  "urn:ogc:def:crs:EPSG::4326",
40            "urn:ogc:def:coordinateOperation:EPSG::1671"),
41
42          • an  Object  name.  e.g  "WGS 84", "WGS 84 / UTM zone 31N". In that
43            case as uniqueness is not guaranteed, heuristics  are  applied  to
44            determine the appropriate best match.
45
46          • a  OGC  URN combining references for compound coordinate reference
47            systems  (e.g  "urn:ogc:def:crs,crs:EPSG::2393,crs:EPSG::5717"  or
48            custom abbreviated syntax "EPSG:2393+5717"),
49
50          • a OGC URN combining references for references for projected or de‐
51            rived CRSs e.g. for Projected 3D CRS "UTM zone 31N / WGS 84 (3D)":
52            "‐
53            urn:ogc:def:crs,crs:EPSG::4979,cs:PROJ::ENh,coordinateOpera‐
54            tion:EPSG::16031" (added in 6.2)
55
56          • a  OGC  URN combining references for concatenated operations (e.g.
57            "‐
58            urn:ogc:def:coordinateOperation,coordinateOperation:EPSG::3895,co‐
59            ordinateOperation:EPSG::1618")
60
61          • a     PROJJSON     string.     The      jsonschema      is      at
62            https://proj.org/schemas/v0.4/projjson.schema.json (added in 6.2)
63
64          • a  compound  CRS  made from two object names separated with " + ".
65            e.g. "WGS 84 + EGM96 height" (added in 7.1)
66
67          {object_reference} is a filename preceded by the '@' character.  The
68          file  referenced by the {object_reference} must contain a valid {ob‐
69          ject_definition}.
70

DESCRIPTION

72       projinfo is a program that can query information on a geodetic  object,
73       coordinate  reference system (CRS) or coordinate operation, when the -s
74       and -t options are specified, and display it  under  different  formats
75       (PROJ string, WKT string or PROJJSON string).
76
77       It  can  also  be used to query coordinate operations available between
78       two CRS.
79
80       The program is named with some reference to the GDAL  gdalsrsinfo  that
81       offers partly similar services.
82
83       The following control parameters can appear in any order:
84
85       -o formats
86              formats is a comma separated combination of: all, default, PROJ,
87              WKT_ALL, WKT2:2015, WKT2:2019, WKT1:GDAL,  WKT1:ESRI,  PROJJSON,
88              SQL.
89
90              Except  all  and  default, other formats can be preceded by - to
91              disable them.
92
93              NOTE:
94                 WKT2_2019 was previously called WKT2_2018.
95
96              NOTE:
97                 Before PROJ 6.3.0, WKT1:GDAL was implicitly calling  --bound‐
98                 crs-to-wgs84.  This is no longer the case.
99
100              NOTE:
101                 When SQL is specified, --output-id must be specified.
102
103       -k crs|operation|datum|ensemble|ellipsoid
104              When used to query a single object with a AUTHORITY:CODE, deter‐
105              mines the (k)ind of the object in case there are CRS, coordinate
106              operations  or  ellipsoids  with  the same CODE.  The default is
107              crs.
108
109       --summary
110              When listing coordinate operations available between 2 CRS,  re‐
111              turn the result in a summary format, mentioning only the name of
112              the coordinate operation, its accuracy and its area of use.
113
114              NOTE:
115                 only used for coordinate operation computation
116
117       -q     Turn on quiet mode. Quiet mode is only available for queries  on
118              single  objects, and only one output format is selected. In that
119              mode, only the PROJ, WKT or PROJJSON string is displayed,  with‐
120              out  other  introduction  output. The output is then potentially
121              compatible of being piped in other utilities.
122
123       --area name_or_code
124              Specify an area of interest to restrict  the  results  when  re‐
125              searching  coordinate  operations between 2 CRS. The area of in‐
126              terest can be specified either as a name  (e.g  "Denmark  -  on‐
127              shore") or a AUTHORITY:CODE (EPSG:3237) This option is exclusive
128              of --bbox.
129
130              NOTE:
131                 only used for coordinate operation computation
132
133       --bbox west_long,south_lat,east_long,north_lat
134              Specify an area of interest to restrict  the  results  when  re‐
135              searching  coordinate  operations between 2 CRS. The area of in‐
136              terest is specified as a bounding box  with  geographic  coordi‐
137              nates,  expressed  in  degrees  in a unspecified geographic CRS.
138              west_long and east_long should be in the [-180,180]  range,  and
139              south_lat  and north_lat in the [-90,90]. west_long is generally
140              lower than east_long, except in the case where the area  of  in‐
141              terest crosses the antimeridian.
142
143              NOTE:
144                 only used for coordinate operation computation
145
146       --spatial-test contains|intersects
147              Specify  how  the  area of use of coordinate operations found in
148              the database are compared to the area of use  specified  explic‐
149              itly  with --area or --bbox, or derived implicitly from the area
150              of use of the source and target CRS.  By default, projinfo  will
151              only  keep  coordinate  operations  whose are of use is strictly
152              within the area of interest (contains strategy).  If  using  the
153              intersects  strategy, the spatial test is relaxed, and any coor‐
154              dinate operation whose area of use at  least  partly  intersects
155              the area of interest is listed.
156
157              NOTE:
158                 only used for coordinate operation computation
159
160       --crs-extent-use none|both|intersection|smallest
161              Specify  which area of interest to consider when no explicit one
162              is specified with --area or --bbox options.  By default  (small‐
163              est  strategy), the area of use of the source or target CRS will
164              be looked, and the one that is the smallest one in terms of area
165              will be used as the area of interest.  If using none, no area of
166              interest is used.  If using  both,  only  coordinate  operations
167              that   relate   (contain   or   intersect   depending   of   the
168              --spatial-test strategy) to the area of use of both CRS are  se‐
169              lected.   If using intersection, the area of interest is the in‐
170              tersection of the bounding box of the area of use of the  source
171              and target CRS
172
173              NOTE:
174                 only used for coordinate operation computation
175
176       --grid-check none|discard_missing|sort|known_available
177              Specify  how the presence or absence of a horizontal or vertical
178              shift grid required for a coordinate operation affects  the  re‐
179              sults  returned when researching coordinate operations between 2
180              CRS.  The default strategy is sort (if PROJ_NETWORK is  not  de‐
181              fined).   In  that  case, all candidate operations are returned,
182              but the actual availability of the grids is  used  to  determine
183              the  sorting  order. That is, if a coordinate operation involves
184              using a grid that is not available in the PROJ resource directo‐
185              ries  (determined  by the PROJ_LIB environment variable, it will
186              be listed in the bottom of the results.  The none strategy  com‐
187              pletely  disables  the  checks of presence of grids and this re‐
188              turns the results as if all the grids where available.  The dis‐
189              card_missing  strategy  discards  results that involve grids not
190              present in the PROJ resource directories.   The  known_available
191              strategy  discards results that involve grids not present in the
192              PROJ resource directories and that are not  known  of  the  CDN.
193              This is the default strategy is PROJ_NETWORK is set to ON.
194
195              NOTE:
196                 only used for coordinate operation computation
197
198       --pivot-crs                             always|if_no_direct_transforma‐
199       tion|never|{auth:code[,auth:code]*}
200              Determine if intermediate (pivot) CRS can be used when research‐
201              ing coordinate operation between 2 CRS. A typical example is the
202              WGS84 pivot. By default, projinfo will  consider  any  potential
203              pivot if there is no direct transformation ( if_no_direct_trans‐
204              formation). If using the never strategy, only direct transforma‐
205              tions  between  the source and target CRS will be used. If using
206              the always strategy, intermediate CRS will be considered even if
207              there  are  direct  transformations.  It is also possible to re‐
208              strict the pivot CRS to consider by specifying  one  or  several
209              CRS by their AUTHORITY:CODE.
210
211              NOTE:
212                 only used for coordinate operation computation
213
214       --show-superseded
215              When  enabled, coordinate operations that are superseded by oth‐
216              ers will be listed. Note that supersession is not equivalent  to
217              deprecation:  superseded  operations  are still considered valid
218              although they have a better equivalent, whereas deprecated oper‐
219              ations  have been determined to be erroneous and are not consid‐
220              ered at all.
221
222              NOTE:
223                 only used for coordinate operation computation
224
225       --hide-ballpark
226              New in version 7.1.
227
228
229              Hides any coordinate operation that is, or contains, a  Ballpark
230              transformation
231
232              NOTE:
233                 only used for coordinate operation computation
234
235       --accuracy {accuracy}
236              New in version 8.0.
237
238
239              Sets the minimum desired accuracy for returned coordinate opera‐
240              tions.
241
242              NOTE:
243                 only used for coordinate operation computation
244
245       --allow-ellipsoidal-height-as-vertical-crs
246              New in version 8.0.
247
248
249              Allows exporting a geographic or projected 3D CRS as a  compound
250              CRS whose vertical CRS represents the ellipsoidal height.
251
252              NOTE:
253                 only used for CRS, and with WKT1:GDAL output format
254
255       --boundcrs-to-wgs84
256              When  specified,  this  option researches a coordinate operation
257              from the base geographic CRS of the single CRS, source or target
258              CRS  to  the WGS84 geographic CRS, and if found, wraps those CRS
259              into  a  BoundCRS  object.   This  is  mostly  to  be  used  for
260              early-binding approaches.
261
262       --authority name
263              Specify  the  name of the authority into which to restrict looks
264              up for objects, when specifying an object by name or when  coor‐
265              dinate  operations are computed. The default is to allow all au‐
266              thorities.
267
268              When used with SQL output, this  restricts  the  authorities  to
269              which  intermediate  objects  can belong to (the default is EPSG
270              and PROJ). Note that the authority  of  the  --output-id  option
271              will also be implicitly added.
272
273       --main-db-path path
274              Specify  the  name  and  path of the database to be used by pro‐
275              jinfo.  The default is proj.db in the PROJ resource directories.
276
277       --aux-db-path path
278              Specify the name and path of auxiliary databases, that are to be
279              combined  with the main database. Those auxiliary databases must
280              have a table structure that is identical to the  main  database,
281              but  can be partly filled and their entries can refer to entries
282              of the main database.  The option may  be  repeated  to  specify
283              several auxiliary databases.
284
285       --identify
286              When used with an object definition, this queries the PROJ data‐
287              base to find known objects, typically CRS,  that  are  close  or
288              identical  to  the  object.  Each candidate object is associated
289              with an approximate likelihood percentage.  This is useful  when
290              used  with  a  WKT  string that lacks a EPSG identifier, such as
291              ESRI WKT1. This might also be used with PROJ strings.  For exam‐
292              ple,  +proj=utm  +zone=31 +datum=WGS84 +type=crs will be identi‐
293              fied with a likelihood of 70% to EPSG:32631
294
295       --dump-db-structure
296              New in version 8.1.
297
298
299              Outputs the sequence of SQL statements to  create  a  new  empty
300              valid  auxiliary  database.  This option can be specified as the
301              only switch of the utility.  If also specifying a CRS object and
302              the  --output-id  option,  the  definition  of the object as SQL
303              statements will be appended.
304
305       --list-crs [list-crs-filter]
306              New in version 8.1.
307
308
309              Outputs a list (authority name:code and CRS name)  of  the  fil‐
310              tered  CRSs from the database.  If no filter is provided all au‐
311              thority names and types  of  non  deprecated  CRSs  are  dumped.
312              list-crs-filter  is a comma separated combination of: allow_dep‐
313              recated,geodetic,geocentric,       geographic,geographic_2d,geo‐
314              graphic_3d,vertical,projected,compound.    Affected  by  options
315              --authority, --area, --bbox and --spatial-test
316
317       --3d   New in version 6.3.
318
319
320              "Promote" the CRS(s) to their 3D version. In the context of  re‐
321              searching available coordinate transformations, explicitly spec‐
322              ifying this option is not necessary, because  when  one  of  the
323              source  or target CRS has a vertical component but not the other
324              one, the one that has no  vertical  component  is  automatically
325              promoted  to a 3D version, where its vertical axis is the ellip‐
326              soidal height in metres, using the ellipsoid of  the  base  geo‐
327              detic CRS.
328
329       --output-id=AUTH:NAME
330              New in version 8.1.
331
332
333              Identifier to assign to the object (for SQL output).
334
335              It  is strongly recommended that new objects should not be added
336              in common registries, such  as  EPSG,  ESRI,  IAU,  etc.   Users
337              should  use  a  custom  authority  name instead. If a new object
338              should be added to the official EPSG registry, users are invited
339              to       follow       the       procedure      explained      at
340              https://epsg.org/dataset-change-requests.html.
341
342              Combined with --dump-db-structure, users  can  create  auxiliary
343              databases,  instead of directly modifying the main proj.db data‐
344              base.  See the example how to export to an auxiliary database.
345
346              Those auxiliary databases can  be  specified  through  proj_con‐
347              text_set_database_path()  or  the  PROJ_AUX_DB environment vari‐
348              able.
349
350       --c-ify
351              For developers only. Modify the string output of the utility  so
352              that it is easy to put those strings in C/C++ code
353
354       --single-line
355              Output  PROJ,  WKT or PROJJSON strings on a single line, instead
356              of multiple indented lines by default.
357
358       --searchpaths
359              New in version 7.0.
360
361
362              Output the directories into which PROJ resources will be  looked
363              for  (if not using C API such as proj_context_set_search_paths()
364              that will override them.
365
366       --remote-data
367              New in version 7.0.
368
369
370              Display information regarding if network is enabled, and the re‐
371              lated URL.
372

EXAMPLES

374       1. Query the CRS object corresponding to EPSG:4326
375
376          projinfo EPSG:4326
377
378       Output:
379
380          PROJ.4 string:
381          +proj=longlat +datum=WGS84 +no_defs +type=crs
382
383          WKT2:2019 string:
384          GEOGCRS["WGS 84",
385              DATUM["World Geodetic System 1984",
386                  ELLIPSOID["WGS 84",6378137,298.257223563,
387                      LENGTHUNIT["metre",1]]],
388              PRIMEM["Greenwich",0,
389                  ANGLEUNIT["degree",0.0174532925199433]],
390              CS[ellipsoidal,2],
391                  AXIS["geodetic latitude (Lat)",north,
392                      ORDER[1],
393                      ANGLEUNIT["degree",0.0174532925199433]],
394                  AXIS["geodetic longitude (Lon)",east,
395                      ORDER[2],
396                      ANGLEUNIT["degree",0.0174532925199433]],
397              USAGE[
398                  SCOPE["unknown"],
399                  AREA["World"],
400                  BBOX[-90,-180,90,180]],
401              ID["EPSG",4326]]
402
403       2. List  the coordinate operations between NAD27 (designed with its CRS
404          name) and NAD83 (designed with its EPSG code 4269) within an area of
405          interest
406
407          projinfo -s NAD27 -t EPSG:4269 --area "USA - Missouri"
408
409       Output:
410
411          DERIVED_FROM(EPSG):1241, NAD27 to NAD83 (1), 0.15 m, USA - CONUS including EEZ
412
413          PROJ string:
414          +proj=pipeline +step +proj=axisswap +order=2,1 +step +proj=unitconvert \
415          +xy_in=deg +xy_out=rad +step +proj=hgridshift +grids=conus \
416          +step +proj=unitconvert +xy_in=rad +xy_out=deg +step +proj=axisswap +order=2,1
417
418          WKT2:2019 string:
419          COORDINATEOPERATION["NAD27 to NAD83 (1)",
420              SOURCECRS[
421                  GEOGCRS["NAD27",
422                      DATUM["North American Datum 1927",
423                          ELLIPSOID["Clarke 1866",6378206.4,294.978698213898,
424                              LENGTHUNIT["metre",1]]],
425                      PRIMEM["Greenwich",0,
426                          ANGLEUNIT["degree",0.0174532925199433]],
427                      CS[ellipsoidal,2],
428                          AXIS["geodetic latitude (Lat)",north,
429                              ORDER[1],
430                              ANGLEUNIT["degree",0.0174532925199433]],
431                          AXIS["geodetic longitude (Lon)",east,
432                              ORDER[2],
433                              ANGLEUNIT["degree",0.0174532925199433]]]],
434              TARGETCRS[
435                  GEOGCRS["NAD83",
436                      DATUM["North American Datum 1983",
437                          ELLIPSOID["GRS 1980",6378137,298.257222101,
438                              LENGTHUNIT["metre",1]]],
439                      PRIMEM["Greenwich",0,
440                          ANGLEUNIT["degree",0.0174532925199433]],
441                      CS[ellipsoidal,2],
442                          AXIS["geodetic latitude (Lat)",north,
443                              ORDER[1],
444                              ANGLEUNIT["degree",0.0174532925199433]],
445                          AXIS["geodetic longitude (Lon)",east,
446                              ORDER[2],
447                              ANGLEUNIT["degree",0.0174532925199433]]]],
448              METHOD["CTABLE2"],
449              PARAMETERFILE["Latitude and longitude difference file","conus"],
450              OPERATIONACCURACY[0.15],
451              USAGE[
452                  SCOPE["unknown"],
453                  AREA["USA - CONUS including EEZ"],
454                  BBOX[23.81,-129.17,49.38,-65.69]],
455              ID["DERIVED_FROM(EPSG)",1241]]
456
457       3. Export an object as a PROJJSON string
458
459          projinfo GDA94 -o PROJJSON -q
460
461       Output:
462
463          {
464              "type": "GeographicCRS",
465              "name": "GDA94",
466              "datum": {
467                  "type": "GeodeticReferenceFrame",
468                  "name": "Geocentric Datum of Australia 1994",
469                  "ellipsoid": {
470                      "name": "GRS 1980",
471                      "semi_major_axis": 6378137,
472                      "inverse_flattening": 298.257222101
473                  }
474              },
475              "coordinate_system": {
476                  "subtype": "ellipsoidal",
477                  "axis": [
478                  {
479                      "name": "Geodetic latitude",
480                      "abbreviation": "Lat",
481                      "direction": "north",
482                      "unit": "degree"
483                  },
484                  {
485                      "name": "Geodetic longitude",
486                      "abbreviation": "Lon",
487                      "direction": "east",
488                      "unit": "degree"
489                  }
490                  ]
491              },
492              "area": "Australia - GDA",
493              "bbox": {
494                  "south_latitude": -60.56,
495                  "west_longitude": 93.41,
496                  "north_latitude": -8.47,
497                  "east_longitude": 173.35
498              },
499              "id": {
500                  "authority": "EPSG",
501                  "code": 4283
502              }
503          }
504
505       4. Exporting  the  SQL  statements  to insert a new CRS in an auxiliary
506          database.
507
508          # Get the SQL statements for a custom CRS
509          projinfo "+proj=merc +lat_ts=5 +datum=WGS84 +type=crs +title=my_crs" --output-id HOBU:MY_CRS -o SQL -q > my_crs.sql
510          cat my_crs.sql
511
512          # Initialize an auxiliary database with the schema of the reference database
513          echo ".schema" | sqlite3 /path/to/proj.db | sqlite3 aux.db
514
515          # Append the content of the definition of HOBU:MY_CRS
516          sqlite3 aux.db < my_crs.db
517
518          # Check that everything works OK
519          projinfo --aux-db-path aux.db HOBU:MY_CRS
520
521       or more simply:
522
523          # Create an auxiliary database with the definition of a custom CRS.
524          projinfo "+proj=merc +lat_ts=5 +datum=WGS84 +type=crs +title=my_crs" --output-id HOBU:MY_CRS --dump-db-structure | sqlite3 aux.db
525
526          # Check that everything works OK
527          projinfo --aux-db-path aux.db HOBU:MY_CRS
528
529       Output:
530
531          INSERT INTO geodetic_crs VALUES('HOBU','GEODETIC_CRS_MY_CRS','unknown','','geographic 2D','EPSG','6424','EPSG','6326',NULL,0);
532          INSERT INTO usage VALUES('HOBU','USAGE_GEODETIC_CRS_MY_CRS','geodetic_crs','HOBU','GEODETIC_CRS_MY_CRS','PROJ','EXTENT_UNKNOWN','PROJ','SCOPE_UNKNOWN');
533          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);
534          INSERT INTO usage VALUES('HOBU','USAGE_CONVERSION_MY_CRS','conversion','HOBU','CONVERSION_MY_CRS','PROJ','EXTENT_UNKNOWN','PROJ','SCOPE_UNKNOWN');
535          INSERT INTO projected_crs VALUES('HOBU','MY_CRS','my_crs','','EPSG','4400','HOBU','GEODETIC_CRS_MY_CRS','HOBU','CONVERSION_MY_CRS',NULL,0);
536          INSERT INTO usage VALUES('HOBU','USAGE_PROJECTED_CRS_MY_CRS','projected_crs','HOBU','MY_CRS','PROJ','EXTENT_UNKNOWN','PROJ','SCOPE_UNKNOWN');
537
538          PROJ.4 string:
539          +proj=merc +lat_ts=5 +lon_0=0 +x_0=0 +y_0=0 +datum=WGS84 +units=m +no_defs +type=crs
540
541          WKT2:2019 string:
542          PROJCRS["my_crs",
543              BASEGEOGCRS["unknown",
544                  ENSEMBLE["World Geodetic System 1984 ensemble",
545                      MEMBER["World Geodetic System 1984 (Transit)"],
546                      MEMBER["World Geodetic System 1984 (G730)"],
547                      MEMBER["World Geodetic System 1984 (G873)"],
548                      MEMBER["World Geodetic System 1984 (G1150)"],
549                      MEMBER["World Geodetic System 1984 (G1674)"],
550                      MEMBER["World Geodetic System 1984 (G1762)"],
551                      ELLIPSOID["WGS 84",6378137,298.257223563,
552                          LENGTHUNIT["metre",1]],
553                      ENSEMBLEACCURACY[2.0]],
554                  PRIMEM["Greenwich",0,
555                      ANGLEUNIT["degree",0.0174532925199433]],
556                  ID["HOBU","GEODETIC_CRS_MY_CRS"]],
557              CONVERSION["unknown",
558                  METHOD["Mercator (variant B)",
559                      ID["EPSG",9805]],
560                  PARAMETER["Latitude of 1st standard parallel",5,
561                      ANGLEUNIT["degree",0.0174532925199433],
562                      ID["EPSG",8823]],
563                  PARAMETER["Longitude of natural origin",0,
564                      ANGLEUNIT["degree",0.0174532925199433],
565                      ID["EPSG",8802]],
566                  PARAMETER["False easting",0,
567                      LENGTHUNIT["metre",1],
568                      ID["EPSG",8806]],
569                  PARAMETER["False northing",0,
570                      LENGTHUNIT["metre",1],
571                      ID["EPSG",8807]]],
572              CS[Cartesian,2],
573                  AXIS["(E)",east,
574                      ORDER[1],
575                      LENGTHUNIT["metre",1]],
576                  AXIS["(N)",north,
577                      ORDER[2],
578                      LENGTHUNIT["metre",1]],
579              ID["HOBU","MY_CRS"]]
580
581       5. Get the WKT representation of EPSG:25832  in  the  WKT1:GDAL  output
582          format and on a single line
583
584          projinfo -o WKT1:GDAL --single-line EPSG:25832
585
586       Output:
587
588          WKT1:GDAL string:
589          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"]]
590

SEE ALSO

592       cs2cs(1), cct(1), geod(1), gie(1), proj(1), projsync(1)
593

BUGS

595       A      list      of      known     bugs     can     be     found     at
596       https://github.com/OSGeo/PROJ/issues where new bug reports can be  sub‐
597       mitted to.
598

HOME PAGE

600       https://proj.org/
601

AUTHOR

603       Even Rouault
604
606       1983-2021
607
608
609
610
6118.2.1                             Jan 1, 2022                      PROJINFO(1)
Impressum