Thanks all for the much needed updates to sr.org!

This is a minor regression from the old sr.org website. For instance with CRS EPSG:28473, compare old and new pages.

The old version https://web.archive.org/web/20210617073835/https://spatialreference.org/ref/epsg/pulkovo-1942-gauss-kruger-13n/

Deprecated: Change of CRS name to indicate longitude of origin. Use EPSG:2503 instead.

The new version https://spatialreference.org/ref/epsg/28473/ only has a short message:

Deprecated!

But is missing other potentially useful information. The only workaround is to navigate to the linked official source https://epsg.org/crs_28473/Pulkovo-1942-Gauss-Kruger-13N.html to find the replacement and reason.

Also projinfo -k crs EPSG:28473 shows the alternative non-deprecated CRS.

Sometime in the last 30 days (maybe longer), the projections being provided on SpatialReference.org for epsg:3418 (Iowa South) are inaccurate:

• Here's an example of a coordinate in EPSG:3418: 1623863.8131117225, 643763.90620113909
• The expected WGS84 is: lat: 41.766901, lng: -93.560676
• But today's result is: lat: 44.960581, lng: -79.222403

These calculations are performed using https://github.com/proj4php/proj4php which hasn't seen any changes short of changing the URL on spatialreference.org to use a .txt suffix.

I'm noticing the incorrect results on https://epsg.io/3418-1696 are incorrect, too (the map shows the new incorrect bounds, which are in Canada instead of Iowa where they used to be). Apologies if this means it's not isolated to this repository, but I'm not sure exactly where to report this.

Also wrote up some findings here: https://gis.stackexchange.com/questions/474573/projections-for-iowa-south-are-now-inaccurate-epsg-spatialreference

Thanks for your hard work on this project!

This task should be quick to complete by a project maintainer in under a minute.

With the web UI, modify the project "About" settings to add a website to https://spatialreference.org

This allows anyone looing at this GH Project to easily navigate to the rendered website.

• goal is to handle the case for when a user goes to: https://www.spatialreference.org/
• possibly through a missing A Record entry in the DNS settings for the domain

• there are a lot of references out there (returned by Google searches) to urls such as:
  • http://spatialreference.org/ref/user/google-projection/
  • http://spatialreference.org/ref/sr-org/google-projection/

This ticket's purpose is to discuss how to handle those. (If the answer is: "we are not planning to handle those old Google Mercator links" then this ticket can be closed)

For the user's experience, redirects could be created to handle the special case for those "Google Projection" searches returning broken links.