KMZ output through WMS Getmap request contains incorrect coordinates

[jmckenna]

• a small test package (see the README.txt inside the package for commands to use) ​http://labs.gatewaygeomatics.com/dl/kmz-output.zip
• a WMS GetMap request with format=kmz returns a kmz/kml file with incorrect coordinates
• this seems to only occur with large extents (the test case is a world polygon file)
• example problem request:

http://127.0.0.1/cgi-bin/mapserv.exe?MAP=/ms4w/apps/kmz-output/map/kmz.map&SERVICE=wms&VERSION=1.1.1&LAYERS=continents&REQUEST=GetMap&SRS=EPSG:4326&BBOX=-180,-90,180,90&FORMAT=kmz&WIDTH=400&HEIGHT=300

With shp2img a correct KMZ/KML file is generated, containing coordinates similar to:

          <outerBoundaryIs>
            <LinearRing>
              <coordinates>
	-60.39371490,46.38618469
	-60.38736343,46.39370728
	-60.38272476,46.39415359
	-60.38175583,46.39162827
	-60.39077759,46.38159561
	-60.39371490,46.38618469
	</coordinates>
            </LinearRing>
          </outerBoundaryIs>

..but the WMS GetMap request generates a KMZ/KML with coordinates similar to:

          <outerBoundaryIs>
            <LinearRing>
              <coordinates>
	132.89587233,227.31030782
	132.90292952,227.32284546
	132.90808360,227.32358932
	132.90916019,227.31938044
	132.89913601,227.30265935
	132.89587233,227.31030782
	</coordinates>
            </LinearRing>
          </outerBoundaryIs>

[jmckenna]

changing component to 'Output-KML'

[assefa]

This is happening for non-square requests (where ratio w/h is different from ratio x/y)

I was expecting the MS_NONSQUARE [yes|no] setting in the map file to turn on/off but from what I can see WMS will always turn it ON if It needs to. I entered a bug on it (#3949). Fixing that bug should be able to allow this kml driver to automatically disallow wms non-square requests and fix this issue.