Custom Query (2765 matches)

For OGC 1.3.0 conformance test, a WMS GetMap request which queries on multiple layers (provided by CITE as test layers), each layer has different geo extents and their own resolutions and the result in rasdaman is wrong.

​http://conformance.rasdaman.com/rasdaman/ows?version=1.3.0&request=GetMap&layers=Streams,Lakes,Ponds,Bridges,RoadSegments,DividedRoutes,Buildings,MapNeatline&styles=&crs=CRS:84&bbox=-0.005,-0.0025,.005,0.0025&width=400&height=200&format=image/png&service=WMS

The result should look like below (each object is a separated layer):

In OGC WMS 1.3.0 test, it contains request which needs to show an image with blue pixels (`0x0000FF) as background for transparent pixels.

Hence, BGCOLOR and optional parameter in WMS GetMap request needs to be supported in petascope for this request.

http://conformance.rasdaman.com/rasdaman/ows?
BgCoLoR=0x0000FF
&StYlEs=&VeRsIoN=1.3.0&BbOx=0,-0.0020,0.0040,0&HeIgHt=100&ReQuEsT=GetMap&WiDtH=200&CrS=CRS:84&FoRmAt=image%2Fpng&LaYeRs=Lakes

NOTE: This BGCOLOR parameter is only applied when TRANSPARENT=FALSE (with TRANSPARENT=TRUE then pixels with null values are transparent as usual) and it will convert output to 3 bands PNG.

According to WMS 1.3.0 standard, by default if omitted or TRANSPARENT=FALSE in WMS GetMap request, then, the result should contain white pixel values when encoded in png instead of NULL values as transparent pixels.

Only when WMS GetMap request has TRANSPARENT=TRUE then, it should return null values as transparent pixels.

See default (TRANSPARENT=FALSE) and with TRANSPARENT=TRUE images: