Hi Daniel, Great ! At least there is a workaround :)
Thanks Bart for your answer as well. Y. Le Thursday 25 October 2007 21:54:26 Daniel Morissette, vous avez écrit : > The postgis implementation in MapServer may not support reading the real > data extents automatically (I just don't know), but you should be able > to set the ows_extent metadata in your layer to tell MapServer which > extents to use for the BoundingBox in capabilities. By default if > ows_extent is not specified then MapServer tries to get the extents from > PostGIS and it seems that it returns something that's way larger than > the actual data. > > Daniel > > Bart van den Eijnden wrote: > > Hi Yves, > > > > unfortunately this is not implemented for PostGIS. > > > > Best regards, > > Bart > > > > On 10/25/07, *Jacolin Yves* < [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > Hi list, > > > > I am working on an application using only OGC standards. I am > > successfully > > create my list of layer from a GetCapabilities request. I would like > > to add > > an overview for each of this layer, and so I processed the bbox, > > scaleHint to > > send a GetMap. > > > > However, I have a problem with all postgis layer because the bbox > > for all of > > my bbox are something like this : > > <BoundingBox SRS="EPSG:27582" minx="-2.5e+07" miny="-2.5e+07" > > maxx="2.5e+07" maxy="2.5e+07" /> > > > > which is obviously incorrect. > > > > My srid postgis layer is set to -1, but the data are in srid = > > 27582. Do you > > think my problem come from this set up ? My projections are always > > set up to > > EPSG:27572 in my mapfile. > > > > Thanks, > > > > Y. > > -- > > Yves Jacolin > > --- > > http://softlibre.gloobe.org -- Yves Jacolin --- http://softlibre.gloobe.org
