Hi Javier,
- GeoTIFF is using its own tags, not WKT
==> ESRI has actually an extension (supported by GDAL) where they
feed ESRI WKT in the PCSCitationGeoKey tag. cf
https://github.com/opengeospatial/geotiff/issues/56#issuecomment-451130281
- Geopackage with this extension
https://www.geopackage.org/guidance/extensions/wkt_for_crs.html
==> WKT1 is part of the core standard. The extension is for
additional WKT:2015 support . And the latest GeoPackage 1.4 spec also
allows WKT:2019
- PAM file in GDAL, but that is cheating ;)
==> almost an industry standard. It has been supported by ArcGIS
for decades
(https://desktop.arcgis.com/fr/arcmap/latest/manage-data/raster-and-images/auxiliary-files.htm).
"grep -r exportToWkt frmts ogr/ogrsf_frmts" in GDAL also shows:
- netCDF. crs_wkt attribute to the CF CRS encoding
- PDF: in GeoPDF (I don't remember if it is the ISO or OGC Best Practice
encoding. but it is the ESRI WKT variant I believe)
- ArcInfo ASCII Grid: ESRI WKT in a .prj
- Oracle GeoRaster: in their spatial_ref_sys table or equivalent. Oracle
WKT: an antique & unique sub-dialect of WKT1
- BAG
- SAGA
- Erdas Imagine. ESRI WKT
- TileDB. WKT1 if PROJJSON not available in a (likely GDAL specific)
attribute
- MySQL. WKT1 in spatial_ref_sys table
- PostGIS. WKT1 in spatial_ref_sys table
- ESRI FileGeodatabase: ESRI WKT
See that I am looking for formats that store some geo-data, and use
WKT to define the CRS (inside or next to it)
Bonus for a "storage format" that uses/supports WKT2!
- FlatGeoBuf, although I realize the spec at
https://github.com/flatgeobuf/flatgeobuf/blob/master/src/fbs/header.fbs#L63
isn't super explicit, but GDAL writes WKT:2019 into it
- Zarr. in a GDAL's extension for CRS support
Even
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
PROJ mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/proj
