[sdw] SDWBP: Issues with EPSG and OGC CRS registry (#1249)

andrea-perego has just created a new issue for https://github.com/w3c/sdw:

== SDWBP: Issues with EPSG and OGC CRS registry ==
The SDWBP document includes links to specific CRS entries in the EPSG registry - e.g., this is the URL used for EPSG 28992 ("Amersfoort / RD New"):

http://epsg-registry.org/?display=entity&urn=urn:ogc:def:crs:EPSG::28992

Now it seems that the `epsg-registry.org` domain is no longer used, and everything is under `epsg.org`. A redirection has been put in place, but it is not properly working.

In particular, you can stumble upon the following issues, depending on the browser and the security/privacy settings you use:

- URLs as the one above are either broken - so, not redirected (domain not available) - or return an error (invalid certificate) after being redirected to http://www.epsg-registry.org/?display=entity&urn=urn:ogc:def:crs:EPSG::28992
- URLs like http://www.epsg-registry.org/?display=entity&urn=urn:ogc:def:crs:EPSG::28992 are not redirected to the specific CRS page (now https://epsg.org/crs_28992/Amersfoort-RD-New.html), but to the home page of EPSG (https://epsg.org/home.html)

An additional issue concerns the CRS URIs operated by the OGC registry, also included in the SDWBP. Now they redirect to the EPSG API, which is however returning an error (invalid certificate) - see, e.g.:

http://www.opengis.net/def/crs/EPSG/0/28992

Certificate-related issues are supposed to be a temporary problem, but the rest concerns the migration policies of the ESPG Web site. 

We can of course update all the links to the EPSG registry in the SDWBP. However, unless the current EPSG URLs are going to be persistent, this solution is simply not sustainable.


Please view or discuss this issue at https://github.com/w3c/sdw/issues/1249 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 3 March 2021 11:42:27 UTC