[mapserver-dev] Implement getNumFeatures for some drivers

Lime, Steve D (MNIT) steve.lime at state.mn.us
Tue May 1 11:38:39 PDT 2018

+1 from me (to include it)...

From: Tamas Szekeres <szekerest at gmail.com>
Sent: Monday, April 30, 2018 5:34:09 PM
To: Lime, Steve D (MNIT)
Cc: mapserver-dev at lists.osgeo.org
Subject: Re: [mapserver-dev] Implement getNumFeatures for some drivers

Created a pull request with the suggested changes:


Keen to have it included in 7.2 if that's sufficient.



2018-04-28 0:48 GMT+02:00 Lime, Steve D (MNIT) <steve.lime at state.mn.us<mailto:steve.lime at state.mn.us>>:
A filter is basically a where statement so I think it should be considered...
From: mapserver-dev <mapserver-dev-bounces at lists.osgeo.org<mailto:mapserver-dev-bounces at lists.osgeo.org>> on behalf of Tamas Szekeres <szekerest at gmail.com<mailto:szekerest at gmail.com>>
Sent: Sunday, April 22, 2018 2:36:44 PM
To: mapserver-dev at lists.osgeo.org<mailto:mapserver-dev at lists.osgeo.org>
Subject: [mapserver-dev] Implement getNumFeatures for some drivers

Hi Devs,

Currently getNumFeatures is supported by the inline layers only. Would that be sufficient to implement this for some other drivers, like  MSSQL, PostGIS and OGR?

The database drivers would probably rely on the count() aggegate in the SQL query, while we could use  OGR_L_GetFeatureCount for the OGR layers.

I could also imagine a default implementation if we use whichShapes on the layer extent and iterate the shapes to calculate the count.

It is also a question whether getNumFeatures should consider the layer filter or not.

Best regards,


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20180501/194e7207/attachment.html>

More information about the mapserver-dev mailing list