Le 2024-07-25 à 07 h 50, Alexis Manin a écrit :
The only question that comes to mind is: would it affect CRS WKT
serialization in any way ? For interoperability with third-party
systems, WKT is often used. If the EPSG upgrade do not cause
incompatible/breaking changes in this regard, then dropping old EPSG
version might be a problem.
It does in some way. In EPSG:4326, the datum is no longer a datum but a
datum ensemble. It means that in WKT 2, the DATUM["WGS 84", ...] element
become ENSEMBLE["WGS 84", more stuff]. The latter did not existed in ISO
19162:2015 and requires ISO 19162:2019. Therefore, the WKT become
unparseable for applications that haven't upgraded to ISO 19162:2019
yet. It includes Apache SIS itself (the upgrade is in progress, in
parallel with the EPSG upgrade).
However, the WKT 2 strings that I see circulating in other projects and
in OGC testbeds are already ISO 19162:2019 strings. I have not seen an
"old" 19162:2015 string for a long time. So it seems that most of the
market already moved there.
Martin
