r.out.vtk: Replace dead WMS server in Spearfish RGB example#7372
Open
mvanhorn wants to merge 1 commit into
Open
r.out.vtk: Replace dead WMS server in Spearfish RGB example#7372mvanhorn wants to merge 1 commit into
mvanhorn wants to merge 1 commit into
Conversation
Closes OSGeo#4844 The Spearfish RGB example pointed at http://wms.jpl.nasa.gov/wms.cgi with the layer name `global_mosaic`. The host stopped resolving some years ago (curl now returns exit code 6 / DNS failure), so any user copy-pasting the example hits a hard error before reaching r.out.vtk. Switch the example to NASA GIBS, which provides a long-running, publicly available WMS that GIBS documentation explicitly recommends for `r.in.wms`-style consumers: https://gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgi The new layer is `BlueMarble_ShadedRelief_Bathymetry`, taken from the GetCapabilities response on that endpoint. It serves the same kind of global RGB satellite coverage the original `global_mosaic` layer did, which keeps the rest of the example (`r.out.vtk rgbmaps=...`) and the Paraview notes meaningful. Updated both the .md (source of truth) and .html (kept in sync).
github-actions
Bot
added
raster
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
raster/r.out.vtk/r.out.vtk.mdandraster/r.out.vtk/r.out.vtk.html(kept in sync per the docs convention): updated the "Spearfish example with RGB data" so it doesn't point at a dead WMS server.r.in.wms layers=global_mosaic mapserver=http://wms.jpl.nasa.gov/wms.cgir.in.wms layers=BlueMarble_ShadedRelief_Bathymetry mapserver=https://gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgiCloses #4844
Why
The original example was added when JPL's WMS endpoint at
wms.jpl.nasa.govwas online. That host stopped resolving some years back (curl http://wms.jpl.nasa.gov/wms.cgi --max-time 10now exits 6 / DNS failure), so anyone copy-pasting the example hits a hard error before they ever reachr.out.vtk.NASA GIBS publishes a long-running WMS at
gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgiand recommends it forr.in.wms-style consumers. I pulled the layer nameBlueMarble_ShadedRelief_Bathymetrystraight from the liveGetCapabilitiesresponse on that endpoint, which serves the same kind of global RGB satellite coverage the oldglobal_mosaiclayer did. That keeps the rest of the example (ther.out.vtk rgbmaps=…step and the Paraview notes) meaningful for a user who just walked through the Spearfish region setup.The Spearfish region (
g.region n=4926990 s=4914840 w=591570 e=607800 res=30 -p) is unchanged.r.in.wmsreprojects from the WMS's EPSG:4326 service into the Spearfish UTM zone the same way it would have for the JPL endpoint.Verification
curl -s -o /dev/null -w '%{http_code}' "https://gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgi"->200.GetCapabilitiesagainst the same endpoint includes<Name>BlueMarble_ShadedRelief_Bathymetry</Name>(alongsideBlueMarble_ShadedReliefandBlueMarble_NextGeneration).curl http://wms.jpl.nasa.gov/wms.cgi --max-time 10returns exit 6 / DNS failure.r.in.wms->r.out.vtkpipeline end-to-end. The change is text-only inside the example block of an existing tool's docs, so the failure mode (URL still dead, layer name still wrong) is the previous state, not a regression. Happy to follow up with screenshots once the change is reviewed.