[mapserver-dev] WMS GetCapabilities 1.3.0 behaviour

[Guillaume Sueur]

I've found the computation script myself. It relies in mappostgis.c in 
msPostGISLayerGetExtent. it comes with a nice TODO :
Update to use proper PostGIS functions to pull extent quickly and 
accurately when available.

Would it be so complicated to do it hasn't been done yet ? I'm ready to 
go on it if someone can lend a hand on hints/caveats.

Best regards,

Guillaume

Le 22/10/10 14:22, Guillaume Sueur a écrit :
> Hi,
>
> I'm still digging into WMS 1.3.0 getCapabilities behaviour with
> MapServer 5.6.5.
> There is some blur point for me.
> My mapfile is advertised as being EPSG:27562, with an specified metric
> extent of 775000 60800 820000 116000. It gives :
> <EX_GeographicBoundingBox>
> <westBoundLongitude>4.57661</westBoundLongitude>
> <eastBoundLongitude>5.17771</eastBoundLongitude>
> <southBoundLatitude>45.5122</southBoundLatitude>
> <northBoundLatitude>46.0216</northBoundLatitude>
> </EX_GeographicBoundingBox>
> <BoundingBox CRS="EPSG:27562" minx="775000" miny="60800" maxx="820000"
> maxy="116000"/>
>
> which is perfect.
>
> My layer has got the same parameters. It I fill up an EXTENT at the
> layer level with the same values as above, it gives me the same perfect
> result. BUT, if I don't declare any extent for the layer, it returns
> weird results :
> <EX_GeographicBoundingBox>
> <westBoundLongitude>-179.318</westBoundLongitude>
> <eastBoundLongitude>179.829</eastBoundLongitude>
> <southBoundLatitude>-69.2834</southBoundLatitude>
> <northBoundLatitude>-34.8224</northBoundLatitude>
> </EX_GeographicBoundingBox>
> <BoundingBox CRS="EPSG:27562" minx="-2.5e+07" miny="-2.5e+07"
> maxx="2.5e+07" maxy="2.5e+07"/>
>
> How are these values calculated ? Why doesn't the layer inherit from map
> extent when no extent is specified ?
>
> Thanks
>
> Guillaume
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
>