What would the process be for adding a new tile service like NowCoast

Question

What would the process be for adding a new tile service like NowCoast

Closed this issue 4 months ago · 5 comments

ahuang11 commented 3 years ago

https://new.nowcoast.noaa.gov/help/#!section=rest-usage

It would unlock a lot, a lot of new tiles (see list @ https://new.nowcoast.noaa.gov/help/#!section=rest-layer-ids)

Answer 1 · 2021-08-08T00:07:36.000Z

See https://xyzservices.readthedocs.io/en/latest/contributing.html#providers

Answer 2 · 2021-08-08T00:09:38.000Z

You can also add it to https://qms.nextgis.com, and then use xyzservices.TileProvider.from_qms("service_name") to load tiles. #63

Answer 3 · 2021-08-08T09:10:59.000Z

@ahuang11 If you can get XYZ URL for NowCoast services, the best option is to follow contributing guide linked by @giswqs and add the metadata to xyzservices-providers.JSON. That way it is easier to find than having it only remotely on QMS (you need to know it is there).

That said, having it in both is the optimal solution for a wider community.

Answer 4 · 2021-11-18T05:14:15.000Z

Before I find a programmatic way to fill out the json with all the services, does this look right? (from https://new.nowcoast.noaa.gov/help/#!section=rest-layer-ids)

I am not sure what {s} stands for in the example, and whether {xmin},{ymin}, etc are accepted (since the example only shows {X},{Y},{Z}.

Example full URL https://new.nowcoast.noaa.gov/arcgis/rest/services/nowcoast/radar_meteo_imagery_nexrad_time/MapServer/export?transparent=true&format=png8&layers=show:3&bbox=-15578640.92640406,2182661.2789739748,-6557848.596303097,7299661.700495453&bboxSR=3857&imageSR=3857&size=922,523&f=image

{
  "analysis_meteohydro_sfc_qpe_time": {
      "1_hr_quantitative_precipitation_accumulation": {
            "url": "https://new.nowcoast.noaa.gov/arcgis/rest/services/nowcoast/analysis_meteohydro_sfc_qpe_time/MapServer/export?transparent=true&format=png8&layers=show:3&bbox={xmin},{ymin},{xmax},{ymax}&bboxSR=3857&imageSR=3857&size=256,256&f=image",
            "max_zoom": 19,
            "attribution": "(C) nowCOAST™",
            "html_attribution": "&copy; <a href=\"https://new.nowcoast.noaa.gov/help/#!section=abstract\">OpenStreetMap</a> contributors",
            "name": "NOAA Quantitative Precipitation Estimates (Time Enabled) 1-Hr Quantitative Precipitation Accumulation (inches)"
      },
      "3_hr_quantitative_precipitation_accumulation": {
            "url": "https://new.nowcoast.noaa.gov/arcgis/rest/services/nowcoast/analysis_meteohydro_sfc_qpe_time/MapServer/export?transparent=true&format=png8&layers=show:7&bbox={xmin},{ymin},{xmax},{ymax}&bboxSR=3857&imageSR=3857&size=256,256&f=image",
            "max_zoom": 19,
            "attribution": "(C) nowCOAST™",
            "html_attribution": "&copy; <a href=\"https://new.nowcoast.noaa.gov/help/#!section=abstract\">OpenStreetMap</a> contributors",
            "name": "NOAA Quantitative Precipitation Estimates (Time Enabled) 3-Hr Quantitative Precipitation Accumulation (inches)"
      },
   },
}

Answer 5 · 2021-11-18T12:33:05.000Z

@ahuang11 this is a WMS data source, not XYZ, that is why the placeholders are different. We currently don't support those but as said in #49 (comment) we could, in theory, do that. It would need some thinking though to ensure we don't mix XYZ and WMS (and potentially other types) together in a confusing way.