Database: change ESRI deprecated records back to their deprecated state #4519
Conversation
rouault
added
the
funded through GSP
Fixes OSGeo/PROJ-CRS-Explorer#36 (comment) During the ArcGIS Pro 3.5 database import, the import script wrongly considered the new value 'codechange' as meaning not deprecated, which resulted in deprecated CRS no longer being flagged as such.
rouault
force-pushed
the
db_esri_deprecated_fix
branch
from
64f298b to
b12746a
Compare
jjimenezshaw
left a comment
jjimenezshaw
left a comment
There was a problem hiding this comment.
What does it actually mean codechange?
This change in the database is reason for a bugfix release? (just asking)
My intuition is that they deprecate an old ESRI code in favor of the regular EPSG one.
I'm not sure if the impact is that strong |
I can think on this use case: If any application is showing the list of (ESRI) available CRSs, removing the deprecated ones, with PROJ 9.6.1 they will have a "few more" (hundreds?) in the combo box. @kbevers any opinion? |
Well... I guess the list of CRS's in QGIS and similar apps will be longer and somewhat incorrect. It's not a problem for me personally and preparing a new release is not a priority at this time. I'm not against a quick 9.6.2 release if someone else takes the lead. |
I'll tackle a 9.6.2 release |
A rarer case is when EPSG has done a deprecate/replace but Esri already had the correct definition, or the change is something that Esri doesn't support anyway. (sorry, made 2 edits to fix my original comment made when distracted) |
4 participants
Fixes OSGeo/PROJ-CRS-Explorer#36 (comment)
During the ArcGIS Pro 3.5 database import, the import script wrongly considered the new value 'codechange' as meaning not deprecated, which resulted in deprecated CRS no longer being flagged as such.