[mapserver-users] WFS with featureID, maxFeatures, & BBOX

[Rahkonen Jukka (Tike)]

Hi,

Right, so it is written into WFS 1.1.0 standard (table 9a):
FEATUREID
(Mutually exclusive with FILTER and BBOX)

You knew it, didn't you? Nobody says "mutually exclusive" in real life ;)

-Jukka Rahkonen-


Eichner, Andreas - SID wrote:
 
> AFAIK FeatureID and BBOX are mutually exclusive.
> ________________________________________
> Von: mapserver-users-bounces at lists.osgeo.org [mapserver-users-
> bounces at lists.osgeo.org]" im Auftrag von "Nathan Smith
> [nsmith13 at nd.edu]
> Gesendet: Montag, 19. Mai 2014 18:05
> An: mapserver-users at lists.osgeo.org
> Betreff: [mapserver-users] WFS with featureID, maxFeatures, & BBOX
> 
> Hi all,
> 
> I've been getting some unexpected results combining BBOX and MaxFeatures
> and was hoping someone might be able to explain why.  I have a web app that
> uses OpenLayers with a MapServer WFS layer.  A typical WFS request is POST
> with a bunch of featureID items, maxfeatures: 1000, & a bbox set by OL.  It
> seems that when the featureID list gets over 1000, instead of first filtering by
> BBOX and then truncating maxFeatures it applies the limit first.  Actually I'm not
> sure bbox is being applied at all.
> 
> Any ideas?  Is the the correct behavior?
> 
> Thanks,
> - Nathan Smith
> 
> _______________________________________________
> mapserver-users mailing list
> mapserver-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-users