WMS GetCapabilities 1.3.0 Ex_GeographicBoundingBox error

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

WMS GetCapabilities 1.3.0 Ex_GeographicBoundingBox error

tellett
Hi all,

I appear to be having a slight problem with the calculation of the Ex_GeographicBoundingBox for the capabilities doc (1.3.0 & 1.1.1) in one of my services. The projection of the service is 32633 (utm zone 33) and the bounding box given in a 1.3.0 capabilities doc is correct for the projected bounds:

<BoundingBox CRS="EPSG:32633" minx="-566158" miny="6.27807e+06" maxx="1.37006e+06" maxy="9.43158e+06"/>

However, it gives the Ex_GBB as:

<EX_GeographicBoundingBox>
<westBoundLongitude>-163.668</westBoundLongitude>
<eastBoundLongitude>178.209</eastBoundLongitude>
<southBoundLatitude>55.4651</southBoundLatitude>
<northBoundLatitude>101.108</northBoundLatitude>
</EX_GeographicBoundingBox>

when I've calculated it should be -1.954, 55.4632, 57.037, 80.728

Getcapabilities call is: http://wms.geonorge.no/skwms1/wms.nmg?version=1.3.0&service=wms&request=getcapabilities

I understand reference systems with central meridian's not through Greenwich used to be a problem but I thought from reading http://trac.osgeo.org/mapserver/ticket/2578 that this was fixed in the 5.6 trunk?

This is all using mapserver 5.6.6, but I've also tried it using mapserver 6.1 and this gives another (also wrong) result:

<EX_GeographicBoundingBox>
<westBoundLongitude>-181.791</westBoundLongitude>
<eastBoundLongitude>162.447</eastBoundLongitude>
<southBoundLatitude>55.4651</southBoundLatitude>
<northBoundLatitude>101.108</northBoundLatitude>
</EX_GeographicBoundingBox>

I wonder if it can be a problem that the projected bounds are outside slightly of the official 32633 grid bounds?

cheers

Tom