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 CRS name and a coordinate epoch, separated with '@'. For example
47 "ITRF2014@2025.0". (added in 9.2)
48 • a OGC URN combining references for compound coordinate reference
50 systems (e.g "urn:ogc:def:crs,crs:EPSG::2393,crs:EPSG::5717" or
51 custom abbreviated syntax "EPSG:2393+5717"),
52 • a OGC URN combining references for references for projected or de‐
54 rived CRSs e.g. for Projected 3D CRS "UTM zone 31N / WGS 84 (3D)":
55 "‐
56 urn:ogc:def:crs,crs:EPSG::4979,cs:PROJ::ENh,coordinateOpera‐
57 tion:EPSG::16031" (added in 6.2)
58 • a OGC URN combining references for concatenated operations (e.g.
60 "‐
61 urn:ogc:def:coordinateOperation,coordinateOperation:EPSG::3895,co‐
62 ordinateOperation:EPSG::1618")
63 • a PROJJSON string. The jsonschema is at
65 https://proj.org/schemas/v0.4/projjson.schema.json (added in 6.2)
66 • a compound CRS made from two object names separated with " + ".
68 e.g. "WGS 84 + EGM96 height" (added in 7.1)
69 {object_reference} is a filename preceded by the '@' character. The
71 file referenced by the {object_reference} must contain a valid {ob‐
72 ject_definition}.
73
75 projinfo is a program that can query information on a geodetic object,
76 coordinate reference system (CRS) or coordinate operation, when the -s
77 and -t options are specified, and display it under different formats
78 (PROJ string, WKT string or PROJJSON string).
79 It can also be used to query coordinate operations available between
81 two CRS.
82 The program is named with some reference to the GDAL gdalsrsinfo util‐
84 ity that offers partly similar services.
85 The following control parameters can appear in any order:
87 -o formats
89 formats is a comma separated combination of: all, default, PROJ,
90 WKT_ALL, WKT2:2015, WKT2:2019, WKT1:GDAL, WKT1:ESRI, PROJJSON,
91 SQL.
92 Except all and default, other formats can be preceded by - to
94 disable them.
95 NOTE:
97 WKT2_2019 was previously called WKT2_2018.
98 NOTE:
100 Before PROJ 6.3.0, WKT1:GDAL was implicitly calling --bound‐
101 crs-to-wgs84. This is no longer the case.
102 NOTE:
104 When SQL is specified, --output-id must be specified.
105 -k crs|operation|datum|ensemble|ellipsoid
107 When used to query a single object with a AUTHORITY:CODE, deter‐
108 mines the (k)ind of the object in case there are CRS, coordinate
109 operations or ellipsoids with the same CODE. The default is
110 crs.
111 --summary
113 When listing coordinate operations available between 2 CRS, re‐
114 turn the result in a summary format, mentioning only the name of
115 the coordinate operation, its accuracy and its area of use.
116 NOTE:
118 only used for coordinate operation computation
119 -q Turn on quiet mode. Quiet mode is only available for queries on
121 single objects, and only one output format is selected. In that
122 mode, only the PROJ, WKT or PROJJSON string is displayed, with‐
123 out other introduction output. The output is then potentially
124 compatible of being piped in other utilities.
125 --area name_or_code
127 Specify an area of interest to restrict the results when re‐
128 searching coordinate operations between 2 CRS. The area of in‐
129 terest can be specified either as a name (e.g "Denmark - on‐
130 shore") or a AUTHORITY:CODE (EPSG:3237) This option is exclusive
131 of --bbox.
132 NOTE:
134 only used for coordinate operation computation
135 --bbox west_long,south_lat,east_long,north_lat
137 Specify an area of interest to restrict the results when re‐
138 searching coordinate operations between 2 CRS. The area of in‐
139 terest is specified as a bounding box with geographic coordi‐
140 nates, expressed in degrees in a unspecified geographic CRS.
141 west_long and east_long should be in the [-180,180] range, and
142 south_lat and north_lat in the [-90,90]. west_long is generally
143 lower than east_long, except in the case where the area of in‐
144 terest crosses the antimeridian.
145 NOTE:
147 only used for coordinate operation computation
148 --spatial-test contains|intersects
150 Specify how the area of use of coordinate operations found in
151 the database are compared to the area of use specified explic‐
152 itly with --area or --bbox, or derived implicitly from the area
153 of use of the source and target CRS. By default, projinfo will
154 only keep coordinate operations whose are of use is strictly
155 within the area of interest (contains strategy). If using the
156 intersects strategy, the spatial test is relaxed, and any coor‐
157 dinate operation whose area of use at least partly intersects
158 the area of interest is listed.
159 NOTE:
161 only used for coordinate operation computation
162 --crs-extent-use none|both|intersection|smallest
164 Specify which area of interest to consider when no explicit one
165 is specified with --area or --bbox options. By default (small‐
166 est strategy), the area of use of the source or target CRS will
167 be looked, and the one that is the smallest one in terms of area
168 will be used as the area of interest. If using none, no area of
169 interest is used. If using both, only coordinate operations
170 that relate (contain or intersect depending of the
171 --spatial-test strategy) to the area of use of both CRS are se‐
172 lected. If using intersection, the area of interest is the in‐
173 tersection of the bounding box of the area of use of the source
174 and target CRS
175 NOTE:
177 only used for coordinate operation computation
178 --grid-check none|discard_missing|sort|known_available
180 Specify how the presence or absence of a horizontal or vertical
181 shift grid required for a coordinate operation affects the re‐
182 sults returned when researching coordinate operations between 2
183 CRS. The default strategy is sort (if PROJ_NETWORK is not de‐
184 fined). In that case, all candidate operations are returned,
185 but the actual availability of the grids is used to determine
186 the sorting order. That is, if a coordinate operation involves
187 using a grid that is not available in the PROJ resource directo‐
188 ries (determined by the PROJ_DATA environment variable), it will
189 be listed in the bottom of the results. The none strategy com‐
190 pletely disables the checks of presence of grids and this re‐
191 turns the results as if all the grids where available. The dis‐
192 card_missing strategy discards results that involve grids not
193 present in the PROJ resource directories. The known_available
194 strategy discards results that involve grids not present in the
195 PROJ resource directories and that are not known of the CDN.
196 This is the default strategy is PROJ_NETWORK is set to ON.
197 NOTE:
199 only used for coordinate operation computation
200 --pivot-crs always|if_no_direct_transforma‐
202 tion|never|{auth:code[,auth:code]*}
203 Determine if intermediate (pivot) CRS can be used when research‐
204 ing coordinate operation between 2 CRS. A typical example is the
205 WGS84 pivot. By default, projinfo will consider any potential
206 pivot if there is no direct transformation ( if_no_direct_trans‐
207 formation). If using the never strategy, only direct transforma‐
208 tions between the source and target CRS will be used. If using
209 the always strategy, intermediate CRS will be considered even if
210 there are direct transformations. It is also possible to re‐
211 strict the pivot CRS to consider by specifying one or several
212 CRS by their AUTHORITY:CODE.
213 NOTE:
215 only used for coordinate operation computation
216 --show-superseded
218 When enabled, coordinate operations that are superseded by oth‐
219 ers will be listed. Note that supersession is not equivalent to
220 deprecation: superseded operations are still considered valid
221 although they have a better equivalent, whereas deprecated oper‐
222 ations have been determined to be erroneous and are not consid‐
223 ered at all.
224 NOTE:
226 only used for coordinate operation computation
227 --hide-ballpark
229 New in version 7.1.
230 Hides any coordinate operation that is, or contains, a Ballpark
233 transformation
234 NOTE:
236 only used for coordinate operation computation
237 --accuracy {accuracy}
239 New in version 8.0.
240 Sets the minimum desired accuracy for returned coordinate opera‐
243 tions.
244 NOTE:
246 only used for coordinate operation computation
247 --allow-ellipsoidal-height-as-vertical-crs
249 New in version 8.0.
250 Allows exporting a geographic or projected 3D CRS as a compound
253 CRS whose vertical CRS represents the ellipsoidal height.
254 NOTE:
256 only used for CRS, and with WKT1:GDAL output format
257 --boundcrs-to-wgs84
259 When specified, this option researches a coordinate operation
260 from the base geographic CRS of the single CRS, source or target
261 CRS to the WGS84 geographic CRS, and if found, wraps those CRS
262 into a BoundCRS object. This is mostly to be used for
263 early-binding approaches.
264 --authority name
266 Specify the name of the authority into which to restrict looks
267 up for objects, when specifying an object by name or when coor‐
268 dinate operations are computed. The default is to allow all au‐
269 thorities.
270 When used with SQL output, this restricts the authorities to
272 which intermediate objects can belong to (the default is EPSG
273 and PROJ). Note that the authority of the --output-id option
274 will also be implicitly added.
275 --main-db-path path
277 Specify the name and path of the database to be used by
278 projinfo. The default is proj.db in the PROJ resource directo‐
279 ries.
280 --aux-db-path path
282 Specify the name and path of auxiliary databases, that are to be
283 combined with the main database. Those auxiliary databases must
284 have a table structure that is identical to the main database,
285 but can be partly filled and their entries can refer to entries
286 of the main database. The option may be repeated to specify
287 several auxiliary databases.
288 --identify
290 When used with an object definition, this queries the PROJ data‐
291 base to find known objects, typically CRS, that are close or
292 identical to the object. Each candidate object is associated
293 with an approximate likelihood percentage. This is useful when
294 used with a WKT string that lacks a EPSG identifier, such as
295 ESRI WKT1. This might also be used with PROJ strings. For exam‐
296 ple, +proj=utm +zone=31 +datum=WGS84 +type=crs will be identi‐
297 fied with a likelihood of 70% to EPSG:32631
298 --dump-db-structure
300 New in version 8.1.
301 Outputs the sequence of SQL statements to create a new empty
304 valid auxiliary database. This option can be specified as the
305 only switch of the utility. If also specifying a CRS object and
306 the --output-id option, the definition of the object as SQL
307 statements will be appended.
308 --list-crs [list-crs-filter]
310 New in version 8.1.
311 Outputs a list (authority name:code and CRS name) of the fil‐
314 tered CRSs from the database. If no filter is provided all au‐
315 thority names and types of non deprecated CRSs are dumped.
316 list-crs-filter is a comma separated combination of: allow_dep‐
317 recated,geodetic,geocentric, geographic,geographic_2d,geo‐
318 graphic_3d,vertical,projected,compound. Affected by options
319 --authority, --area, --bbox and --spatial-test
320 A visual alternative is the webpage CRS Explorer .
322 --3d New in version 6.3.
324 "Promote" 2D CRS(s) to their 3D version, where the vertical axis
327 is the ellipsoidal height in metres, using the ellipsoid of the
328 base geodetic CRS. Depending on PROJ versions and the exact na‐
329 ture of the CRS involved, especially before PROJ 9.1, a mix of
330 2D and 3D CRS could lead to 2D or 3D transformations. Starting
331 with PROJ 9.1, both CRS need to be 3D for vertical transforma‐
332 tion to possibly happen.
333 --output-id=AUTH:NAME
335 New in version 8.1.
336 Identifier to assign to the object (for SQL output).
339 It is strongly recommended that new objects should not be added
341 in common registries, such as EPSG, ESRI, IAU, etc. Users
342 should use a custom authority name instead. If a new object
343 should be added to the official EPSG registry, users are invited
344 to follow the procedure explained at
345 https://epsg.org/dataset-change-requests.html.
346 Combined with --dump-db-structure, users can create auxiliary
348 databases, instead of directly modifying the main proj.db data‐
349 base. See the example how to export to an auxiliary database.
350 Those auxiliary databases can be specified through proj_con‐
352 text_set_database_path() or the PROJ_AUX_DB environment vari‐
353 able.
354 --c-ify
356 For developers only. Modify the string output of the utility so
357 that it is easy to put those strings in C/C++ code
358 --single-line
360 Output PROJ, WKT or PROJJSON strings on a single line, instead
361 of multiple indented lines by default.
362 --searchpaths
364 New in version 7.0.
365 Output the directories into which PROJ resources will be looked
368 for (if not using C API such as proj_context_set_search_paths()
369 that will override them.
370 --remote-data
372 New in version 7.0.
373 Display information regarding if Network capabilities is en‐
376 abled, and the related URL.
377
379 1. Query the CRS object corresponding to EPSG:4326
380 projinfo EPSG:4326
382 Output:
384 PROJ.4 string:
386 +proj=longlat +datum=WGS84 +no_defs +type=crs
387 WKT2:2019 string:
389 GEOGCRS["WGS 84",
390 DATUM["World Geodetic System 1984",
391 ELLIPSOID["WGS 84",6378137,298.257223563,
392 LENGTHUNIT["metre",1]]],
393 PRIMEM["Greenwich",0,
394 ANGLEUNIT["degree",0.0174532925199433]],
395 CS[ellipsoidal,2],
396 AXIS["geodetic latitude (Lat)",north,
397 ORDER[1],
398 ANGLEUNIT["degree",0.0174532925199433]],
399 AXIS["geodetic longitude (Lon)",east,
400 ORDER[2],
401 ANGLEUNIT["degree",0.0174532925199433]],
402 USAGE[
403 SCOPE["unknown"],
404 AREA["World"],
405 BBOX[-90,-180,90,180]],
406 ID["EPSG",4326]]
407 2. List the coordinate operations between NAD27 (designed with its CRS
409 name) and NAD83 (designed with its EPSG code 4269) within an area of
410 interest
411 projinfo -s NAD27 -t EPSG:4269 --area "USA - Missouri"
413 Output:
415 DERIVED_FROM(EPSG):1241, NAD27 to NAD83 (1), 0.15 m, USA - CONUS including EEZ
417 PROJ string:
419 +proj=pipeline +step +proj=axisswap +order=2,1 +step +proj=unitconvert \
420 +xy_in=deg +xy_out=rad +step +proj=hgridshift +grids=conus \
421 +step +proj=unitconvert +xy_in=rad +xy_out=deg +step +proj=axisswap +order=2,1
422 WKT2:2019 string:
424 COORDINATEOPERATION["NAD27 to NAD83 (1)",
425 SOURCECRS[
426 GEOGCRS["NAD27",
427 DATUM["North American Datum 1927",
428 ELLIPSOID["Clarke 1866",6378206.4,294.978698213898,
429 LENGTHUNIT["metre",1]]],
430 PRIMEM["Greenwich",0,
431 ANGLEUNIT["degree",0.0174532925199433]],
432 CS[ellipsoidal,2],
433 AXIS["geodetic latitude (Lat)",north,
434 ORDER[1],
435 ANGLEUNIT["degree",0.0174532925199433]],
436 AXIS["geodetic longitude (Lon)",east,
437 ORDER[2],
438 ANGLEUNIT["degree",0.0174532925199433]]]],
439 TARGETCRS[
440 GEOGCRS["NAD83",
441 DATUM["North American Datum 1983",
442 ELLIPSOID["GRS 1980",6378137,298.257222101,
443 LENGTHUNIT["metre",1]]],
444 PRIMEM["Greenwich",0,
445 ANGLEUNIT["degree",0.0174532925199433]],
446 CS[ellipsoidal,2],
447 AXIS["geodetic latitude (Lat)",north,
448 ORDER[1],
449 ANGLEUNIT["degree",0.0174532925199433]],
450 AXIS["geodetic longitude (Lon)",east,
451 ORDER[2],
452 ANGLEUNIT["degree",0.0174532925199433]]]],
453 METHOD["CTABLE2"],
454 PARAMETERFILE["Latitude and longitude difference file","conus"],
455 OPERATIONACCURACY[0.15],
456 USAGE[
457 SCOPE["unknown"],
458 AREA["USA - CONUS including EEZ"],
459 BBOX[23.81,-129.17,49.38,-65.69]],
460 ID["DERIVED_FROM(EPSG)",1241]]
461 3. Export an object as a PROJJSON string
463 projinfo GDA94 -o PROJJSON -q
465 Output:
467 {
469 "type": "GeographicCRS",
470 "name": "GDA94",
471 "datum": {
472 "type": "GeodeticReferenceFrame",
473 "name": "Geocentric Datum of Australia 1994",
474 "ellipsoid": {
475 "name": "GRS 1980",
476 "semi_major_axis": 6378137,
477 "inverse_flattening": 298.257222101
478 }
479 },
480 "coordinate_system": {
481 "subtype": "ellipsoidal",
482 "axis": [
483 {
484 "name": "Geodetic latitude",
485 "abbreviation": "Lat",
486 "direction": "north",
487 "unit": "degree"
488 },
489 {
490 "name": "Geodetic longitude",
491 "abbreviation": "Lon",
492 "direction": "east",
493 "unit": "degree"
494 }
495 ]
496 },
497 "area": "Australia - GDA",
498 "bbox": {
499 "south_latitude": -60.56,
500 "west_longitude": 93.41,
501 "north_latitude": -8.47,
502 "east_longitude": 173.35
503 },
504 "id": {
505 "authority": "EPSG",
506 "code": 4283
507 }
508 }
509 4. Exporting the SQL statements to insert a new CRS in an auxiliary
511 database.
512 # Get the SQL statements for a custom CRS
514 projinfo "+proj=merc +lat_ts=5 +datum=WGS84 +type=crs +title=my_crs" --output-id HOBU:MY_CRS -o SQL -q > my_crs.sql
515 cat my_crs.sql
516 # Initialize an auxiliary database with the schema of the reference database
518 echo ".schema" | sqlite3 /path/to/proj.db | sqlite3 aux.db
519 # Append the content of the definition of HOBU:MY_CRS
521 sqlite3 aux.db < my_crs.db
522 # Check that everything works OK
524 projinfo --aux-db-path aux.db HOBU:MY_CRS
525 or more simply:
527 # Create an auxiliary database with the definition of a custom CRS.
529 projinfo "+proj=merc +lat_ts=5 +datum=WGS84 +type=crs +title=my_crs" --output-id HOBU:MY_CRS --dump-db-structure | sqlite3 aux.db
530 # Check that everything works OK
532 projinfo --aux-db-path aux.db HOBU:MY_CRS
533 Output:
535 INSERT INTO geodetic_crs VALUES('HOBU','GEODETIC_CRS_MY_CRS','unknown','','geographic 2D','EPSG','6424','EPSG','6326',NULL,0);
537 INSERT INTO usage VALUES('HOBU','USAGE_GEODETIC_CRS_MY_CRS','geodetic_crs','HOBU','GEODETIC_CRS_MY_CRS','PROJ','EXTENT_UNKNOWN','PROJ','SCOPE_UNKNOWN');
538 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);
539 INSERT INTO usage VALUES('HOBU','USAGE_CONVERSION_MY_CRS','conversion','HOBU','CONVERSION_MY_CRS','PROJ','EXTENT_UNKNOWN','PROJ','SCOPE_UNKNOWN');
540 INSERT INTO projected_crs VALUES('HOBU','MY_CRS','my_crs','','EPSG','4400','HOBU','GEODETIC_CRS_MY_CRS','HOBU','CONVERSION_MY_CRS',NULL,0);
541 INSERT INTO usage VALUES('HOBU','USAGE_PROJECTED_CRS_MY_CRS','projected_crs','HOBU','MY_CRS','PROJ','EXTENT_UNKNOWN','PROJ','SCOPE_UNKNOWN');
542 PROJ.4 string:
544 +proj=merc +lat_ts=5 +lon_0=0 +x_0=0 +y_0=0 +datum=WGS84 +units=m +no_defs +type=crs
545 WKT2:2019 string:
547 PROJCRS["my_crs",
548 BASEGEOGCRS["unknown",
549 ENSEMBLE["World Geodetic System 1984 ensemble",
550 MEMBER["World Geodetic System 1984 (Transit)"],
551 MEMBER["World Geodetic System 1984 (G730)"],
552 MEMBER["World Geodetic System 1984 (G873)"],
553 MEMBER["World Geodetic System 1984 (G1150)"],
554 MEMBER["World Geodetic System 1984 (G1674)"],
555 MEMBER["World Geodetic System 1984 (G1762)"],
556 ELLIPSOID["WGS 84",6378137,298.257223563,
557 LENGTHUNIT["metre",1]],
558 ENSEMBLEACCURACY[2.0]],
559 PRIMEM["Greenwich",0,
560 ANGLEUNIT["degree",0.0174532925199433]],
561 ID["HOBU","GEODETIC_CRS_MY_CRS"]],
562 CONVERSION["unknown",
563 METHOD["Mercator (variant B)",
564 ID["EPSG",9805]],
565 PARAMETER["Latitude of 1st standard parallel",5,
566 ANGLEUNIT["degree",0.0174532925199433],
567 ID["EPSG",8823]],
568 PARAMETER["Longitude of natural origin",0,
569 ANGLEUNIT["degree",0.0174532925199433],
570 ID["EPSG",8802]],
571 PARAMETER["False easting",0,
572 LENGTHUNIT["metre",1],
573 ID["EPSG",8806]],
574 PARAMETER["False northing",0,
575 LENGTHUNIT["metre",1],
576 ID["EPSG",8807]]],
577 CS[Cartesian,2],
578 AXIS["(E)",east,
579 ORDER[1],
580 LENGTHUNIT["metre",1]],
581 AXIS["(N)",north,
582 ORDER[2],
583 LENGTHUNIT["metre",1]],
584 ID["HOBU","MY_CRS"]]
585 5. Get the WKT representation of EPSG:25832 in the WKT1:GDAL output
587 format and on a single line
588 projinfo -o WKT1:GDAL --single-line EPSG:25832
590 Output:
592 WKT1:GDAL string:
594 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"]]
595
597 cs2cs(1), cct(1), geod(1), gie(1), proj(1), projsync(1)
598
600 A list of known bugs can be found at
601 https://github.com/OSGeo/PROJ/issues where new bug reports can be sub‐
602 mitted to.
603
605 https://proj.org/
606
608 Even Rouault
609
611 1983-2023
6129.2.1 Jun 1, 2023 PROJINFO(1)