[PROJ] EPSG release once more busted

Martin Desruisseaux martin.desruisseaux at geomatys.com
Wed Jul 22 02:50:59 PDT 2026


Hello Javier

Le 22/07/2026 à 11:26, Javier Jimenez Shaw a écrit :

> We are aware of the "geodetic" problems you mention. However Even is 
> not referring to this kind of consistency problems. The problems we 
> usually encounter are more related to the consistency "inside" the 
> database. Fields that are wrongly filled that cause problems when a 
> user tries to get information from the database.

Indeed, I encountered issues such as some unperseable dates in a column 
where the dates are stored as texts (maybe for storing dates with 
different precision). Those issues are annoying, but since they are 
relatively easy to adapt, I though that the reported inconsistencies 
were something else.


>  For instance (I don't know if this actually happened), the steps of a 
> concatenated operation should be consistent with the operation itself.

I don't know if it was the case, but if the reported inconsistency was 
the source CRS of the concatenated operation not being the source CRS of 
the first step, and being instead the target CRS of the last step, then 
this is intentional. This is a way to specify that the *reverse* of the 
operation chain shall be applied. This is admittedly not obvious, and 
the ISO 19111 group also discussed about making that clearer.

     Martin



More information about the PROJ mailing list