[mapserver-users] Mapserver 7.0.3 and disabling default extent for WFS

Even Rouault even.rouault at spatialys.com
Mon Dec 19 14:42:15 PST 2016


On lundi 19 décembre 2016 22:34:10 CET Rahkonen Jukka (MML) wrote:
> If I set "wfs_use_default_extent_for_getfeature" "yes"
> I  see a difference
> [Tue Dec 20 00:28:37 2016].113723 msOGRFileWhichShapes: Setting spatial
> filter to -1e+300 -1e+300 1e+300 1e+300 [Tue Dec 20 00:28:48 2016].950696
> msOGRFileNextShape: Returning shape=9, tile=0
> 
> However, this change does not make is fast, notice 11 seconds between
> WhichShapes and Next shape.

Hum, it is instantaneous for me. 

> 
> -Jukka-
> 
> Lähettäjä: Even Rouault [mailto:even.rouault at spatialys.com]
> Lähetetty: 20. joulukuuta 2016 0:27
> Vastaanottaja: mapserver-users at lists.osgeo.org
> Kopio: Rahkonen Jukka (MML) <jukka.rahkonen at maanmittauslaitos.fi>
> Aihe: Re: [mapserver-users] Mapserver 7.0.3 and disabling default extent for
> WFS
> On lundi 19 décembre 2016 21:46:32 CET Rahkonen Jukka (MML) wrote:
> > Hi,
> > 
> > 
> > 
> > I am running Mapserver 7.0.3, I have a vector layer from a quite large
> > 
> > GeoPackage through OGR connection and I have set the LAYER METADATA item
> > 
> > "wfs_use_default_extent_for_getfeature" "no"
> > 
> > 
> > 
> > Still if I query GetFeature simply with &COUNT=1 I can see that the
> > default
> > 
> > extent is used msOGRFileWhichShapes: Setting spatial filter to 19969.99999
> > 
> > 6597277.99999 749676.00001 7785300.00001 This makes count based request
> > 
> > pretty slow and it take about 15 second to get the first feature.
> > 
> > 
> > 
> > The documentation in http://mapserver.org/ogc/wfs_server.html says that
> > this
> > 
> > option is supported "since MapServer 7.0.3" . So what could be wrong?
> 
> Jukka,
> 
> 
> 
> thanks for spotting my brain damage...
> 
> 
> 
> In fact there are 2 issues :
> 
> - a minor one: the debug message "Setting spatial filter..." was always
> displayed, even when the spatial filter wasn't applied
> 
> - a major one: the logic to interpret the yes/no value of the setting was
> inverted (only when it is explicitly set fortunately, so that doesn't break
> existing mapfiles without the metadata item). I've fixed that, and thus
> modified the doc to advertize the feature only in 7.0.4. I guess I didn't
> notice that since I mixed it with other optimizations.
> 
> 
> 
> Even
> 
> 
> 
> 
> 
> --
> 
> Spatialys - Geospatial professional services
> 
> http://www.spatialys.com


-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20161219/58e39ca5/attachment-0001.html>


More information about the mapserver-users mailing list