[mapserver-dev] msPostGISLayerGetExtent should consider layer filter

Tamas Szekeres szekerest at gmail.com
Sun Apr 8 12:29:41 PDT 2018


I think it would be faster to execute the ST_Extent aggregate on a smaller
set of geometries (though it might depend on the implementation).
The benefit would probably be that LayerGetExtent could be used to
calculate the actual extent of the layer.

Best regards,

Tamas


2018-04-06 9:24 GMT+02:00 Rahkonen Jukka (MML) <
jukka.rahkonen at maanmittauslaitos.fi>:

> Hi,
>
>
>
> What would be the benefits of appending the ”where”? How often the query
> is run and can it be slow?
>
>
>
> -Jukka Rahkonen-
>
>
>
> *Lähettäjä:* mapserver-dev [mailto:mapserver-dev-bounces at lists.osgeo.org] *Puolesta
> *Tamas Szekeres
> *Lähetetty:* 6. huhtikuuta 2018 10:19
> *Vastaanottaja:* mapserver-dev at lists.osgeo.org
> *Aihe:* [mapserver-dev] msPostGISLayerGetExtent should consider layer
> filter
>
>
>
> Hi Devs,
>
>
>
> We would require that msPostGISLayerGetExtent would apply the specified
> filter when calculating the layer extent. This would probably be happen by
> appending the "where" clause from  msPostGISBuildSQLWhere to
> sqlExtentTemplate. Does this make sense?
>
> I've checked the code and some of the drivers consider the filter and some
> are not, so I'm not completely sure about the expected behaviour.
>
>
>
> Best regards,
>
>
>
> Tamas
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20180408/46b85ca4/attachment.html>


More information about the mapserver-dev mailing list