For harvested warper instances, form of remote endpoint is incorrect about hypermap-registry HOT 6 CLOSED

I disagree on this. If it would be uncorrect MapProxy wouldn't work - which is not the case (test the MapProxy demo). I have tried both endpoints in QGIS and this one https://mapwarper.h-gis.jp/maps/wms/1621 is the correct one.
Can I close this or did I misunderstand you?

from hypermap-registry.

You are right, it is a good WMS endpoint. We need something else though for any system that has landing pages for layers where data is downloadable and that is the layer page on the remote system. Very important for end users. Perhaps we need to add a line for "Layer Download" and make it first and that would be of the form https://mapwarper.h-gis.jp/maps/1621?. We had that a long time ago and it disappeared. The form of this URL will vary from system to system as we build connectors (CKAN, Warper, Rumsey, Esri Open Data, etc) so the logic for creating the Download or Layer Page endpoint would be part of the connector.

from hypermap-registry.

There is the layer page url for this purpose:

which is https://mapwarper.h-gis.jp/maps/1621 for this case. Link is correct in Hypermap, but it is not correctly rendered on the page. it is an easy fix

from hypermap-registry.

No, I'm talking about the landing page for the layer on the remote system (from which one can download the data). In this case it is on mapwarper.h-gis.jp server and the the URL for this layer is https://mapwarper.h-gis.jp/maps/1621.

from hypermap-registry.

Sorry I misread you response. You got it I think.

from hypermap-registry.

Now I have fixed the html text as well. Only href was correct.
Thanks @blewis for reporting

from hypermap-registry.