L-Har
commented
5 days ago - I could add epsg.io before the number and make it a link.
- I could write a SQL query that converts the codes to a string then stores it in a new database column. Then switch it out. (This will allow us to revert if something happens).
@ThorTheDestroyer @mitchellryant Those are two options. Let me know what you guys think.
If you want me to write the SQL that swaps the numeric codes into a human readable format (ex: 4326 to WGS84); then I'm going to wait until @ctrepka @TWDBrob @twdbben and @DipakS28 get back to discuss it with them and see if it's used as a foreign key or something important though. first so it won't be done until next week.
In 2018 when we designed the API DB, the Projections Look Up table was designed to be just the number for the EPSG Code. And on the front end we would add the web site https://epsg.io in front of the number and create an href to that site, ex https://epsg.io/3857. This would all the user to get the technical details of each CRS.
Currently we are just showing a number in this part of the front end. Not all user may know what these numbers mean.
If we no longer want to href out to EPSG.io, should we consider using a common name or abbreviation. This would require a model change.