[mapserver-dev] MOTION to adopt RFC 118 - Vendor-specific WMS FILTER param

[Daniel Morissette]

Hi Jukka,

That's a very good question and I thought the same as you at first, but 
when I think about it some more I'm not sure if the risk is real or not: 
since the FILTER is combined with whatever pre-existing filter was 
already in the layer, it can only reduce the number of features 
returned/drawn, so it can hardly add much load, unless the number of 
features returned/drawn was already excessively high.

I didn't research this in details so I may be missing something obvious. 
What do you think?

Daniel

On 2017-08-16 5:12 AM, Rahkonen Jukka (MML) wrote:
> Hi,
> 
> One thing that came late into my mind: it will be rather easy to write 
> FILTER params which are very heavy to execute in the database. Same 
> applies to SLD, see https://github.com/mapserver/mapserver/pull/4703, 
> and because of that server admin can deny the use of SLD by setting 
> ows_sld_enabled metadata into false.
> 
> Unlike  %variable% it is not easy to validate OGC filters, but should we 
> have at least a method for disabling it with some metadata like 
> “wms_filter_enabled”
> 
> -Jukka Rahkonen-
> 
> *Lähettäjä:*mapserver-dev [mailto:mapserver-dev-bounces at lists.osgeo.org] 
> *Puolesta *Rahkonen Jukka (MML)
> *Lähetetty:* 16. elokuuta 2017 7:12
> *Vastaanottaja:* Lime, Steve D (MNIT) <steve.lime at state.mn.us>; Daniel 
> Morissette <dmorissette at mapgears.com>; 'MapServer Dev List' 
> <mapserver-dev at lists.osgeo.org>
> *Aihe:* Re: [mapserver-dev] MOTION to adopt RFC 118 - Vendor-specific 
> WMS FILTER param
> 
> +1
> 
> -Jukka Rahkonen-
> 
> ------------------------------------------------------------------------
> 
> *Lähettäjä: *Lime, Steve D (MNIT) <mailto:steve.lime at state.mn.us>
> *Lähetetty: *‎16.‎8.‎2017 3:01
> *Vastaanottaja: *Daniel Morissette <mailto:dmorissette at mapgears.com>; 
> 'MapServer Dev List' <mailto:mapserver-dev at lists.osgeo.org>
> *Aihe: *Re: [mapserver-dev] MOTION to adopt RFC 118 - Vendor-specific 
> WMS FILTER param
> 
> +1
> 
> ------------------------------------------------------------------------
> 
> *From:*mapserver-dev <mapserver-dev-bounces at lists.osgeo.org 
> <mailto:mapserver-dev-bounces at lists.osgeo.org>> on behalf of Daniel 
> Morissette <dmorissette at mapgears.com <mailto:dmorissette at mapgears.com>>
> *Sent:* Tuesday, August 15, 2017 4:41:33 PM
> *To:* 'MapServer Dev List'
> *Subject:* [mapserver-dev] MOTION to adopt RFC 118 - Vendor-specific WMS 
> FILTER param
> 
> We had the discussion on RFC 118 back in February and the code in my
> fork (https://github.com/dmorissette/mapserver/tree/rfc118-filter) has
> been in use in a few apps since, but we haven't voted to include it
> officially in 7.2 yet.
> 
> So unless there is more feedback, I'll move to adopt MS RFC 118 -
> Support Vendor-Specific OGC FILTER parameter in WMS requests:
> 
> http://mapserver.org/development/rfc/ms-rfc-118.html
> 
> And I start with my +1
> 
> Daniel
> -- 
> Daniel Morissette
> Mapgears Inc
> T: +1 418-696-5056 #201
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org <mailto:mapserver-dev at lists.osgeo.org>
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
> 
> 
> 
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
> 


-- 
Daniel Morissette
Mapgears Inc
T: +1 418-696-5056 #201