1PROJINFO(1) PROJ PROJINFO(1)
2
6 projinfo - Geodetic object and coordinate operation queries
7
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 where {object_definition} or {srs_def} is one of the possibilities
33 accepted by proj_create()
34 • a proj-string,
36 • a WKT string,
38 • an object code (like "EPSG:4326", "urn:ogc:def:crs:EPSG::4326",
40 "urn:ogc:def:coordinateOperation:EPSG::1671"),
41 • 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 • 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 • 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 • 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 • a PROJJSON string. The jsonschema is at
62 https://proj.org/schemas/v0.4/projjson.schema.json (added in 6.2)
63 • a compound CRS made from two object names separated with " + ".
65 e.g. "WGS 84 + EGM96 height" (added in 7.1)
66 {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
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 It can also be used to query coordinate operations available between
78 two CRS.
79 The program is named with some reference to the GDAL gdalsrsinfo that
81 offers partly similar services.
82 The following control parameters can appear in any order:
84 -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 Except all and default, other formats can be preceded by - to
91 disable them.
92 NOTE:
94 WKT2_2019 was previously called WKT2_2018.
95 NOTE:
97 Before PROJ 6.3.0, WKT1:GDAL was implicitly calling --bound‐
98 crs-to-wgs84. This is no longer the case.
99 NOTE:
101 When SQL is specified, --output-id must be specified.
102 -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 --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 NOTE:
115 only used for coordinate operation computation
116 -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 --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 NOTE:
131 only used for coordinate operation computation
132 --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 NOTE:
144 only used for coordinate operation computation
145 --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 NOTE:
158 only used for coordinate operation computation
159 --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 NOTE:
174 only used for coordinate operation computation
175 --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_DATA 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 NOTE:
196 only used for coordinate operation computation
197 --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 NOTE:
212 only used for coordinate operation computation
213 --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 NOTE:
223 only used for coordinate operation computation
224 --hide-ballpark
226 New in version 7.1.
227 Hides any coordinate operation that is, or contains, a Ballpark
230 transformation
231 NOTE:
233 only used for coordinate operation computation
234 --accuracy {accuracy}
236 New in version 8.0.
237 Sets the minimum desired accuracy for returned coordinate opera‐
240 tions.
241 NOTE:
243 only used for coordinate operation computation
244 --allow-ellipsoidal-height-as-vertical-crs
246 New in version 8.0.
247 Allows exporting a geographic or projected 3D CRS as a compound
250 CRS whose vertical CRS represents the ellipsoidal height.
251 NOTE:
253 only used for CRS, and with WKT1:GDAL output format
254 --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 --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 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 --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 --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 --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 --dump-db-structure
296 New in version 8.1.
297 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 --list-crs [list-crs-filter]
306 New in version 8.1.
307 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 --3d New in version 6.3.
318 "Promote" 2D CRS(s) to their 3D version, where the vertical axis
321 is the ellipsoidal height in metres, using the ellipsoid of the
322 base geodetic CRS. Depending on PROJ versions and the exact na‐
323 ture of the CRS involved, especially before PROJ 9.1, a mix of
324 2D and 3D CRS could lead to 2D or 3D transformations. Starting
325 with PROJ 9.1, both CRS need to be 3D for vertical transforma‐
326 tion to possibly happen.
327 --output-id=AUTH:NAME
329 New in version 8.1.
330 Identifier to assign to the object (for SQL output).
333 It is strongly recommended that new objects should not be added
335 in common registries, such as EPSG, ESRI, IAU, etc. Users
336 should use a custom authority name instead. If a new object
337 should be added to the official EPSG registry, users are invited
338 to follow the procedure explained at
339 https://epsg.org/dataset-change-requests.html.
340 Combined with --dump-db-structure, users can create auxiliary
342 databases, instead of directly modifying the main proj.db data‐
343 base. See the example how to export to an auxiliary database.
344 Those auxiliary databases can be specified through proj_con‐
346 text_set_database_path() or the PROJ_AUX_DB environment vari‐
347 able.
348 --c-ify
350 For developers only. Modify the string output of the utility so
351 that it is easy to put those strings in C/C++ code
352 --single-line
354 Output PROJ, WKT or PROJJSON strings on a single line, instead
355 of multiple indented lines by default.
356 --searchpaths
358 New in version 7.0.
359 Output the directories into which PROJ resources will be looked
362 for (if not using C API such as proj_context_set_search_paths()
363 that will override them.
364 --remote-data
366 New in version 7.0.
367 Display information regarding if Network capabilities is en‐
370 abled, and the related URL.
371
373 1. Query the CRS object corresponding to EPSG:4326
374 projinfo EPSG:4326
376 Output:
378 PROJ.4 string:
380 +proj=longlat +datum=WGS84 +no_defs +type=crs
381 WKT2:2019 string:
383 GEOGCRS["WGS 84",
384 DATUM["World Geodetic System 1984",
385 ELLIPSOID["WGS 84",6378137,298.257223563,
386 LENGTHUNIT["metre",1]]],
387 PRIMEM["Greenwich",0,
388 ANGLEUNIT["degree",0.0174532925199433]],
389 CS[ellipsoidal,2],
390 AXIS["geodetic latitude (Lat)",north,
391 ORDER[1],
392 ANGLEUNIT["degree",0.0174532925199433]],
393 AXIS["geodetic longitude (Lon)",east,
394 ORDER[2],
395 ANGLEUNIT["degree",0.0174532925199433]],
396 USAGE[
397 SCOPE["unknown"],
398 AREA["World"],
399 BBOX[-90,-180,90,180]],
400 ID["EPSG",4326]]
401 2. List the coordinate operations between NAD27 (designed with its CRS
403 name) and NAD83 (designed with its EPSG code 4269) within an area of
404 interest
405 projinfo -s NAD27 -t EPSG:4269 --area "USA - Missouri"
407 Output:
409 DERIVED_FROM(EPSG):1241, NAD27 to NAD83 (1), 0.15 m, USA - CONUS including EEZ
411 PROJ string:
413 +proj=pipeline +step +proj=axisswap +order=2,1 +step +proj=unitconvert \
414 +xy_in=deg +xy_out=rad +step +proj=hgridshift +grids=conus \
415 +step +proj=unitconvert +xy_in=rad +xy_out=deg +step +proj=axisswap +order=2,1
416 WKT2:2019 string:
418 COORDINATEOPERATION["NAD27 to NAD83 (1)",
419 SOURCECRS[
420 GEOGCRS["NAD27",
421 DATUM["North American Datum 1927",
422 ELLIPSOID["Clarke 1866",6378206.4,294.978698213898,
423 LENGTHUNIT["metre",1]]],
424 PRIMEM["Greenwich",0,
425 ANGLEUNIT["degree",0.0174532925199433]],
426 CS[ellipsoidal,2],
427 AXIS["geodetic latitude (Lat)",north,
428 ORDER[1],
429 ANGLEUNIT["degree",0.0174532925199433]],
430 AXIS["geodetic longitude (Lon)",east,
431 ORDER[2],
432 ANGLEUNIT["degree",0.0174532925199433]]]],
433 TARGETCRS[
434 GEOGCRS["NAD83",
435 DATUM["North American Datum 1983",
436 ELLIPSOID["GRS 1980",6378137,298.257222101,
437 LENGTHUNIT["metre",1]]],
438 PRIMEM["Greenwich",0,
439 ANGLEUNIT["degree",0.0174532925199433]],
440 CS[ellipsoidal,2],
441 AXIS["geodetic latitude (Lat)",north,
442 ORDER[1],
443 ANGLEUNIT["degree",0.0174532925199433]],
444 AXIS["geodetic longitude (Lon)",east,
445 ORDER[2],
446 ANGLEUNIT["degree",0.0174532925199433]]]],
447 METHOD["CTABLE2"],
448 PARAMETERFILE["Latitude and longitude difference file","conus"],
449 OPERATIONACCURACY[0.15],
450 USAGE[
451 SCOPE["unknown"],
452 AREA["USA - CONUS including EEZ"],
453 BBOX[23.81,-129.17,49.38,-65.69]],
454 ID["DERIVED_FROM(EPSG)",1241]]
455 3. Export an object as a PROJJSON string
457 projinfo GDA94 -o PROJJSON -q
459 Output:
461 {
463 "type": "GeographicCRS",
464 "name": "GDA94",
465 "datum": {
466 "type": "GeodeticReferenceFrame",
467 "name": "Geocentric Datum of Australia 1994",
468 "ellipsoid": {
469 "name": "GRS 1980",
470 "semi_major_axis": 6378137,
471 "inverse_flattening": 298.257222101
472 }
473 },
474 "coordinate_system": {
475 "subtype": "ellipsoidal",
476 "axis": [
477 {
478 "name": "Geodetic latitude",
479 "abbreviation": "Lat",
480 "direction": "north",
481 "unit": "degree"
482 },
483 {
484 "name": "Geodetic longitude",
485 "abbreviation": "Lon",
486 "direction": "east",
487 "unit": "degree"
488 }
489 ]
490 },
491 "area": "Australia - GDA",
492 "bbox": {
493 "south_latitude": -60.56,
494 "west_longitude": 93.41,
495 "north_latitude": -8.47,
496 "east_longitude": 173.35
497 },
498 "id": {
499 "authority": "EPSG",
500 "code": 4283
501 }
502 }
503 4. Exporting the SQL statements to insert a new CRS in an auxiliary
505 database.
506 # Get the SQL statements for a custom CRS
508 projinfo "+proj=merc +lat_ts=5 +datum=WGS84 +type=crs +title=my_crs" --output-id HOBU:MY_CRS -o SQL -q > my_crs.sql
509 cat my_crs.sql
510 # Initialize an auxiliary database with the schema of the reference database
512 echo ".schema" | sqlite3 /path/to/proj.db | sqlite3 aux.db
513 # Append the content of the definition of HOBU:MY_CRS
515 sqlite3 aux.db < my_crs.db
516 # Check that everything works OK
518 projinfo --aux-db-path aux.db HOBU:MY_CRS
519 or more simply:
521 # Create an auxiliary database with the definition of a custom CRS.
523 projinfo "+proj=merc +lat_ts=5 +datum=WGS84 +type=crs +title=my_crs" --output-id HOBU:MY_CRS --dump-db-structure | sqlite3 aux.db
524 # Check that everything works OK
526 projinfo --aux-db-path aux.db HOBU:MY_CRS
527 Output:
529 INSERT INTO geodetic_crs VALUES('HOBU','GEODETIC_CRS_MY_CRS','unknown','','geographic 2D','EPSG','6424','EPSG','6326',NULL,0);
531 INSERT INTO usage VALUES('HOBU','USAGE_GEODETIC_CRS_MY_CRS','geodetic_crs','HOBU','GEODETIC_CRS_MY_CRS','PROJ','EXTENT_UNKNOWN','PROJ','SCOPE_UNKNOWN');
532 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);
533 INSERT INTO usage VALUES('HOBU','USAGE_CONVERSION_MY_CRS','conversion','HOBU','CONVERSION_MY_CRS','PROJ','EXTENT_UNKNOWN','PROJ','SCOPE_UNKNOWN');
534 INSERT INTO projected_crs VALUES('HOBU','MY_CRS','my_crs','','EPSG','4400','HOBU','GEODETIC_CRS_MY_CRS','HOBU','CONVERSION_MY_CRS',NULL,0);
535 INSERT INTO usage VALUES('HOBU','USAGE_PROJECTED_CRS_MY_CRS','projected_crs','HOBU','MY_CRS','PROJ','EXTENT_UNKNOWN','PROJ','SCOPE_UNKNOWN');
536 PROJ.4 string:
538 +proj=merc +lat_ts=5 +lon_0=0 +x_0=0 +y_0=0 +datum=WGS84 +units=m +no_defs +type=crs
539 WKT2:2019 string:
541 PROJCRS["my_crs",
542 BASEGEOGCRS["unknown",
543 ENSEMBLE["World Geodetic System 1984 ensemble",
544 MEMBER["World Geodetic System 1984 (Transit)"],
545 MEMBER["World Geodetic System 1984 (G730)"],
546 MEMBER["World Geodetic System 1984 (G873)"],
547 MEMBER["World Geodetic System 1984 (G1150)"],
548 MEMBER["World Geodetic System 1984 (G1674)"],
549 MEMBER["World Geodetic System 1984 (G1762)"],
550 ELLIPSOID["WGS 84",6378137,298.257223563,
551 LENGTHUNIT["metre",1]],
552 ENSEMBLEACCURACY[2.0]],
553 PRIMEM["Greenwich",0,
554 ANGLEUNIT["degree",0.0174532925199433]],
555 ID["HOBU","GEODETIC_CRS_MY_CRS"]],
556 CONVERSION["unknown",
557 METHOD["Mercator (variant B)",
558 ID["EPSG",9805]],
559 PARAMETER["Latitude of 1st standard parallel",5,
560 ANGLEUNIT["degree",0.0174532925199433],
561 ID["EPSG",8823]],
562 PARAMETER["Longitude of natural origin",0,
563 ANGLEUNIT["degree",0.0174532925199433],
564 ID["EPSG",8802]],
565 PARAMETER["False easting",0,
566 LENGTHUNIT["metre",1],
567 ID["EPSG",8806]],
568 PARAMETER["False northing",0,
569 LENGTHUNIT["metre",1],
570 ID["EPSG",8807]]],
571 CS[Cartesian,2],
572 AXIS["(E)",east,
573 ORDER[1],
574 LENGTHUNIT["metre",1]],
575 AXIS["(N)",north,
576 ORDER[2],
577 LENGTHUNIT["metre",1]],
578 ID["HOBU","MY_CRS"]]
579 5. Get the WKT representation of EPSG:25832 in the WKT1:GDAL output
581 format and on a single line
582 projinfo -o WKT1:GDAL --single-line EPSG:25832
584 Output:
586 WKT1:GDAL string:
588 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"]]
589
591 cs2cs(1), cct(1), geod(1), gie(1), proj(1), projsync(1)
592
594 A list of known bugs can be found at
595 https://github.com/OSGeo/PROJ/issues where new bug reports can be sub‐
596 mitted to.
597
599 https://proj.org/
600
602 Even Rouault
603
605 1983-2022
6069.1.1 Dec 1st, 2022 PROJINFO(1)