some of the `.wkt` files here taken from the EPSG database are malformed, the file content is not WKT

[nsajko]

trafficstars

https://github.com/JuliaEarth/CoordRefSystems.jl/blob/ae9c4d5e038e36761a0516db53a62d4237d84172/artifacts/epsg-wkt2/EPSG-CRS-5614.wkt#L1

[juliohm]

That is interesting. The EPSG.org website has the following entry for the code:

https://epsg.org/crs_5614/KOC-WD-depth-ft.html

It is a 1-dimensional coordinate system with a single vertical coordinate in feet. Historically, 3D coordinate systems (with vertical coordinates) have been ill-modeled in software, which probably explains the lack of WKT for this one.

We should probably throw an informative error message if this is not the case already. I wonder if there are many instances of these commited in the repo, that could justify a cleanup in our artifacts/update.jl script.

[nsajko]

Possibly this should be reported to epsg.org.

I wonder if there are many instances of these commited in the repo

In the entire database:

• Four CRS definition files have the above error message as their entire content
  • EPSG-CRS-5614.wkt
  • EPSG-CRS-6358.wkt
  • EPSG-CRS-8051.wkt
  • EPSG-CRS-8053.wkt
• one ConcatenatedOperation (not commited here to the repo) definition file has the error message appear within TARGETCRS:
  • EPSG-ConcatenatedOperation-7987.wkt

[juliohm]

Possibly this should be reported to epsg.org.

We could gather more information, but this may be intended given the limitations of widely used software.

• EPSG-CRS-5614.wkt
• EPSG-CRS-6358.wkt
• EPSG-CRS-8051.wkt
• EPSG-CRS-8053.wkt

All these occurrences fit the same "single vertical coordinate model", which is a good sign in a sense.