EPSG release and ArcGIS Projection Engine

101
2
Jump to solution
02-18-2020 01:09 AM
Highlighted
New Contributor III

Hi All,

As stated in the subject I'm investigating to understand if there is an easy way to identify which version of EPSG dataset is bind to a specific version of ArcGIS' Projection Engine.
The scenario includes a legacy application, that I'm maintaining,  that uses EPSG datasets to specify CRS and Datum transformation codes. This application does not use ArcObjects, spatial datasets, mainly raster data, are stored in a proprietary format, bind to an EPSG code specifying CRS and Datum shift operation.
In order to publish datasets to ArcGIS' users a desktop extension ingests this data into an enterprise Geodatabase. Projection definition and Datum shift uses the EPSG codes with functions from the projection engine.
To avoid issues with EPSG codes not recognized I would like to sync the version of EPSG datasets used in the legacy application with the one used in ArcGIS Projection engine.

We are currently running ArcGIS 10.5.1 SP1, planning to migrate to 10.7.1.
So the main question is: where can I find a clear indication of the EPSG version used for a ArcGIS release?

Thanks for any hint

Kind Regards,

Stefano Iacovella

1 Solution

Accepted Solutions
Highlighted
Esri Notable Contributor

Hello Stefano, 

We don't publish the EPSG dataset version with the Esri release. We do keep a list internally. Because we don't fully implement the EPSG dataset, there's usually a subset of objects that have been implemented at any EPSG dataset release.

Note: Between 10.6.1 and 10.7.1, we did add more entries but I was selectively picking what to add so we didn't update the EPSG version number.

ArcGIS   build #   EPSG    Freeze date (not software release date)
10.4.0 5524 8.7.2 12/23/15
10.4.1 5635 8.8 02/15/16

10.5.0 6489 8.9.4 10/28/16
10.5.1 7333 9.0 06/07/17

10.6.0 8321 9.1.2 12/18/17
10.6.1 9270 9.1.2 12/18/17

10.7.0 10450 9.1.2 02/19/19
10.7.1 11595 9.1.2 05/31/19

10.8.0 12790 9.8.2 11/26/19


View solution in original post

2 Replies
Highlighted
Esri Notable Contributor

Hello Stefano, 

We don't publish the EPSG dataset version with the Esri release. We do keep a list internally. Because we don't fully implement the EPSG dataset, there's usually a subset of objects that have been implemented at any EPSG dataset release.

Note: Between 10.6.1 and 10.7.1, we did add more entries but I was selectively picking what to add so we didn't update the EPSG version number.

ArcGIS   build #   EPSG    Freeze date (not software release date)
10.4.0 5524 8.7.2 12/23/15
10.4.1 5635 8.8 02/15/16

10.5.0 6489 8.9.4 10/28/16
10.5.1 7333 9.0 06/07/17

10.6.0 8321 9.1.2 12/18/17
10.6.1 9270 9.1.2 12/18/17

10.7.0 10450 9.1.2 02/19/19
10.7.1 11595 9.1.2 05/31/19

10.8.0 12790 9.8.2 11/26/19


View solution in original post

Highlighted
New Contributor III

Hello Melita,

Thank you very much for your clear answer.

After I posted the question I tried to compare contents of EPSG standard dataset and ESRI projection engine. It was quite easy to compare CRS as arcpy has a SpatialReference() method that can be used, with an EPSG id as argument, to test if a specific CRS is supported by the projection engine.

This way I noted that many CRS are missing also when testing ArcGIS 10.5.1 against old releases of EPSG dataset, like 7.9 that was released 10 years ago.

If I clearly understood your message it seems that when you include information from EPSG you apply a filter to extract only those considered relevant.

Testing the Datum shift operation is a little bit more complicated, but from your answer I assume that also in this case any projection engine release supports a subset of the operation available in a specific EPSG dataset release.

Then, getting back to my original question, the goal of having a one to one match for ArcGIS projection engine and the legacy application using EPSG dataset is impossible.

I think I can try to extract a set of information about CRS and Datum shift operation used in the legacy application and not supported by an ArcGIS release and add them as custom CRS or operations.

Thank you very much again for your detailed information.

All the best,

Stefano

Reply
0 Kudos