Hi, I barely ever see the use of a version in decoded EPSG codes, so I do not think it would be a problem to drop support for older EPSG versions in this regard.
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. Otherwise, I do not see any problem on dropping support for EPSG 9.x. Regards, Le jeu. 25 juil. 2024 à 00:11, Martin Desruisseaux < martin.desruisse...@geomatys.com> a écrit : > Hello all > > Apache SIS is capable to connect directly to an EPSG database version > 9.x without the need to convert the database to some project-specific > schema. It allows, for example, to connect to many EPSG databases for > different versions. Therefore, authority codes like "EPSG:9.7:4326" and > "EPSG:9.9:4326" (for example) will use the versions 9.7 and 9.9 > respectively of the EPSG database for the same 4326 code, if those > versions are available on the user's machine. > > We are upgrading the EPSG database from version 9.9.1 to 11.012. But > there is some changes in the EPSG schema introduced in version 10 which > need to be reflected by changes in the Java code. Consequently, it would > be a little bit difficult to support both versions 9.x and versions 11.x > of the EPSG database. Is there any objection to drop support for > versions 9.x of the EPSG database? Note: if support for versions 9.x was > needed, it could be done by creating SQL views. But it would require > some work. > > Martin > > >
