WFS GetFeature and GML data issue

[Bart van den Eijnden]

Hi Tom,

we experienced similar things with WMS GetLegendGraphic without a Rule
(a.k.a. GetLegend). Mapserver would use the internal scale based on the
values in the MAP file to see if layers should end up in the legend or
not. For scale-dependent layers we ran into problems of them not showing
up in the legend, but showing up in the map. In our case we had to fake a
very small extent in the MAP file to get them to show up, but then your
boundingbox in the WMS capabilities gets ruined again, so you run from one
problem to the next (ofcourse you can use wms_extent METADATA for this,
but it's not straightforward anymore as a workaround).

I think it would be best to at least open up a bugreport for this, since
it is a too big pitfall in my opinion.

Best regards,
Bart

> Any other comments here?  Should we things be as they are and put a
> warning in the docs?  Or do we want to think about a more elaborate way
> to handle this?
>
> ..Tom
>
>
>> -----Original Message-----
>> From: Paul Ramsey [mailto:pramsey at refractions.net]
>> Sent: Wednesday, 16 March, 2005 16:46
>> To: Kralidis,Tom [Burlington]
>> Cc: MAPSERVER-DEV at LISTS.UMN.EDU
>> Subject: Re: [UMN_MAPSERVER-DEV] WFS GetFeature and GML data issue
>>
>>
>> Hooray for the bounding box, our cruel task master! Let no query go
>> unbounded, and let the masses gnash their teeth, and quake in fear!
>>
>> :)
>> P
>>
>> Kralidis,Tom [Burlington] wrote:
>>
>> > Hi,
>> >
>> > After offline email with Frank (thanks Frank!), it seems
>> that this has
>> > to do with  the fact that my GML document bounding box of
>> the data is
>> > outside of MAP/EXTENT in the mapfile.  If I change my MAP/EXTENT to
>> > -180 -90 180 90, I indeed get all the data back.
>> >
>> > I guess the question is the behaviour of MAP/EXTENT for a
>> WFS, and if
>> > a LAYER has extents outside the bounds of MAP/EXTENT, what happens
>> > when a client makes a blanket request and expects all the
>> data?  Mind
>> > you if LAYER extents are larger than MAP/EXTENT, this
>> should trigger
>> > the mapfile creator to think about whether they've applied
>> the right
>> > MAP/EXTENT.  On the other hand, how does MAP/EXTENT, something that
>> > historically applies to the default extent of a mapping app for
>> > MapServer CGI, apply to OWS approaches?
>> >
>> > At the very least (as Frank suggests) the WFS server howto
>> should warn
>> > about this.  I would post a doc bug for this but not until there is
>> > consensus that the way things behave now are the way they should.
>> >
>> > Comments?
>> >
>> > ..Tom
>> >
>> >
>> >
>> >>-----Original Message-----
>> >>From: Frank Warmerdam [mailto:fwarmerdam at gmail.com]
>> >>Sent: Wednesday, 16 March, 2005 15:20
>> >>To: Kralidis,Tom [Burlington]
>> >>Cc: MAPSERVER-DEV at lists.umn.edu
>> >>Subject: Re: [UMN_MAPSERVER-DEV] WFS GetFeature and GML data issue
>> >>
>> >>
>> >>On Wed, 16 Mar 2005 15:15:02 -0500, Kralidis,Tom [Burlington]
>> >><Tom.Kralidis at ec.gc.ca> wrote:
>> >>
>> >>>Hi,
>> >>>
>> >>>I have a LAYER defined with a GML document as the native
>> >>
>> >>data type.
>> >>
>> >>>The GML document has 21 features.
>> >>>
>> >>>When I run a WFS GetFeature against the entire dataset:
>> >>>
>> >>>
>> >>
>> >>http://devgeo.cciw.ca/cgi-bin/mapserv/ecows?version=1.0.0&se
> rvice=WFS&
>>>
>>>>re
>>>>quest=GetFeature&typename=neis&
>>>>
>>>>...I expect to have returned 21 features.  However the
>>>
>>>response only
>>>
>>>>returns 4.
>>>
>>>Tom,
>>>
>>>How does this file look to ogrinfo?  Can you post this GML
>>>file for me to inspect?
>>>
>>>Best regards,
>>>--
>>>---------------------------------------+----------------------
>>>----------
>>>---------------------------------------+------
>>>I set the clouds in motion - turn up   | Frank Warmerdam,
>>>warmerdam at pobox.com
>>>light and sound - activate the windows | http://pobox.com/~warmerdam
>>>and watch the world go round - Rush    | Geospatial
>>>Programmer for Rent
>>
>>
>
>