WMS - Wrong BoundingBox in capabilities about mapserver HOT 6 CLOSED

WMS 1.1.0 spec states that one BoundingBox tag is required per advertized SRS... 
and at the moment we return one only for the default SRS.

So at the same time as fixing the above problem we should make sure one 
BoundingBox tag is produced for each advertized SRS... this should likely be 
done by sampling points around the default projection's extent.

Let's see if we can fix the invalid bbox for 4.0.

About producing one BBOX tag per advertized SRS, I don't think we should do 
that, and anyway, the WMS 1.1.1 spec sect 7.1.4.5.7 says that it's optional:

  "A server which has the ability to transform data to different SRSes may
   choose not to provide an explicit BoundingBox for every possible SRS
   available for each Layer. The server should provide BoundingBox information
   for at least the native SRS of the Layer."

The above behavior is already what we do, we just need to fix the case where the 
bbox coordinates aren't properly advertized if the data is not in the default 
advertized SRS.

*** Bug 217 has been marked as a duplicate of this bug. ***

(From update of attachment 38)
OOppps... please disregard attachment above, it was added to the wrong bug

Fixed in 4.0 CVS... finally!

The fix was simpler than I thought: If the MAP (or LAYER) contains a PROJECTION
block in the format "init=epsg:xxxx" then uses that to generate a <BoundingBox>
tag.  Otherwise we don't generate the <BoundingBox> tag since it's optional and
we don't have access to the original SRS and BBOX of the data in this case.

I also added a few notes in the wms-server-howto about this behavior in the
sections of the HOWTO that talk about layer and map projections.

   screengrab showing map in LCC with grid at those extents