Opened 13 years ago
Last modified 13 years ago
#3949 new enhancement
WMS disable no-square requests
Reported by: | assefa | Owned by: | assefa |
---|---|---|---|
Priority: | normal | Milestone: | 6.2 release |
Component: | WMS Server | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: | dmorissette, jmckenna |
Description
The map file level configuration described in the docs as: MS_NONSQUARE [yes|no] :The CONFIG parameter can be used to allow non-square WMS requests.
does not really disable non-square requests in the case of WMS. It will be turned on always.
Is there a reason why It should always be turned in WMS?
This is related to issues we are having for vector type outputs such as KML through WMS (#3928)
Change History (5)
comment:1 by , 13 years ago
Cc: | added |
---|---|
Owner: | changed from | to
comment:2 by , 13 years ago
comment:3 by , 13 years ago
But disabling it for vector type outputs such as KML obtained through WMS GetMap would make sense, right?
comment:4 by , 13 years ago
Cc: | added |
---|
comment:5 by , 13 years ago
Discussion on IRC:
The idea would be to allow some drivers (for now only KML) to be able to adjust the width/height to fit the ratio of the extents for a non-square wms type requests.
This could be triggered by some output format configuration. The idea is to not have ifs with driver name. This would be done between mapwms.c (load parameters function) or mapdraw.c (prepareimage). Quickly checking the code I was not sure where the best place would be that would not afftect existing functionallities.
If I remember correctly, WMS requires that you return non-square pixels if the width/height (pixels) ratio does not match the dx/dy ratio of the geographic bbox. If you want square pixels with WMS then you have to make sure your WMS GetMap request passes a geographic BBOX with the correct proportions for the requested width/height.