// the offset order should be swapped // Rasdaman does it // MapServer and GeoServer not
@pomakis cool thank you! do you know offhand what width and height would map to for scalesize ?
Are you asking how a client would request a specific with and height via
the scalesize parameter? If so, the answer (four our two coverages) is scalesize=Long(640),Lat(480)
This should work fine in conjunction with the new behaviour of the bbox parameter.
@pomakis i'm curious , does the 640x480 map to the extended, or cropped extent? And did this behavior change with the new implementation?
You get the requested bbox at the requested size, so pretty much exactly like a WMS request (except for the point-versus-area interpretation of the bounding box - still an item to be resolved).
Back when the requested bbox was trimmed to the extent of the coverage, you got back the requested size, but not necessarily the requested bbox.
@pomakis so that would mean you would receive a different 'scaling factor' tahn you asked for!
Not really. You'd receive an image of the requested size, covering the portion of the coverage that intersects the specified bounding box. (Not as nice as what we have now, I admit, but still reasonably well defined.) There's a separate scalingFactor parameter (e.g., scalingFactor=0.1), but as an alternative to specifying an exact width and height.