You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to allow users to select the color palette on ncWMS2 endpoints, as shown here on the Godiva3 ncWMS2 client:
On ncWMS2 endpoints, the palettes are not included as styles, but are contained in the GetCapabilities abstract. This would be nasty to parse, but ncWMS2 already supplies an easy way to retrieve this information, via a GetMetadata&item=layerDetails` extension. For example, this request: http://geoport.whoi.edu/ncWMS2/wms?request=GetMetadata&item=layerDetails&layerName=FVCOM-NECOFS-GOM3/temp
returns this simple JSON structure with the palette info:
@rsignell-usgs - The palettes are advertised as styles, it's just that only a subset of them are listed. Implemented palettes as another dimension could be done, but it's not a trivial task.
It would be useful to allow users to select the color palette on ncWMS2 endpoints, as shown here on the Godiva3 ncWMS2 client:
On ncWMS2 endpoints, the palettes are not included as styles, but are contained in the GetCapabilities abstract. This would be nasty to parse, but ncWMS2 already supplies an easy way to retrieve this information, via a GetMetadata&item=layerDetails` extension. For example, this request:
http://geoport.whoi.edu/ncWMS2/wms?request=GetMetadata&item=layerDetails&layerName=FVCOM-NECOFS-GOM3/temp
returns this simple JSON structure with the palette info:
The palette selected, for example
x-Sst
is then used in subsequent requests, like:http://geoport.whoi.edu/ncWMS2/wms?FORMAT=image%2Fpng&TRANSPARENT=TRUE&STYLES=default-scalar%2Fx-Sst&LAYERS=FVCOM-NECOFS-GOM3%2Ftemp&TIME=2016-11-04T10%3A58%3A07.500Z&ELEVATION=0&COLORSCALERANGE=10.73%2C17.1&NUMCOLORBANDS=250&ABOVEMAXCOLOR=0x000000&BELOWMINCOLOR=0x000000&BGCOLOR=transparent&LOGSCALE=false&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&SRS=EPSG%3A4326&BBOX=-72.420933854153,39.933157812517,-71.023803124986,41.330288541684&WIDTH=256&HEIGHT=256
The text was updated successfully, but these errors were encountered: