Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent use of the "GCS_" and "D_" prefixes #61

Closed
phaarnes opened this issue Dec 16, 2024 · 2 comments
Closed

Inconsistent use of the "GCS_" and "D_" prefixes #61

phaarnes opened this issue Dec 16, 2024 · 2 comments

Comments

@phaarnes
Copy link

Hi,

Almost all of your geographic CRSs have the GCS_ prefix, and the datums have the D_ prefix. However, I have stumbled upon several examples where the geographic CRS does not start with "GCS" and the datum does not start with "D_". Is there a specific reason why the ESRI PE CRS catalog is not 100% consistent with the ESRI naming convention for CRSs and datums?

Examples:

@melitakennedy
Copy link

This is more ancient history of the projection engine library. And many of these 'oddities' are due to me and first developer who went along with it! The GCS_ and D_ prefixes arose out of my desire to be able to identify which object is being used or wanted if you have only the name. Similarly, working with various *nix operating systems, I really wanted names to have underscores--no pesky spaces! Stupid, now in retrospect. A few years back, the team decided to drop the GCS_ and D_ from the names, and internally, if you use the projection engine to compare objects, we ignore those prefixes and underscores within names.

@phaarnes
Copy link
Author

Okay, I see. Thank you for a quick response Melita!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants