<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Alessandro<br>
<br>
<div class="gmail_extra">>in WFS we have the standard OGC
"FILTER" plus the QGIS custom "EXP_FILTER"</div>
<div class="gmail_extra">>in WMS we have QGIS custom "FILTER"</div>
<div class="gmail_extra">><br>
</div>
<div class="gmail_extra">>IMHO the best solution would be to
have the same parameters also in WMS, so:</div>
<div class="gmail_extra">
><br>
</div>
<div class="gmail_extra">>rename WMS QGIS custom "FILTER"
to "EXP_FILTER" and</div>
<div class="gmail_extra">>implement OGC "FILTER" even if it's
not in the standard</div>
<div class="gmail_extra">
<br>
</div>
<div class="gmail_extra">Oh, so we have even three filter
possibilities:<br>
<br>
1. OGC Filter (done via QgsExpression )<br>
2. Filter with QGIS custom syntax (done via QgsExpression)<br>
3. Filter with provider subset with syntax of data provider
(e.g. SQL). Done on provider (DB) side for very fast searches,
therefore needs careful parsing against SQL injections<br>
<br>
WFS server implements 1+2, WMS server implements 3. There are
pros and cons for all of them, so it would be nice to have three
parameter name to call all of them for WMS servers.<br>
<br>
>Do you think that we can re-use the WFS OGC FILTER code for
the WMS OGC FILTER implementation?</div>
<br>
QgsOgcUtils::expressionFromOgcFilter<br>
<br>
Regards,<br>
Marco<br>
<br>
On 11.01.2014 09:47, Alessandro Pasotti wrote:<br>
</div>
<blockquote
cite="mid:CAL5Q670_Q22cmO==UCJ8LgMZHHRX=92oKT0J=SnaCE17oRf5VQ@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">2014/1/9 Alessandro Pasotti <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:apasotti@gmail.com" target="_blank">apasotti@gmail.com</a>></span><br>
<blockquote class="gmail_quote">
<div dir="ltr">
<div class="gmail_extra">
<div class="im">
<div class="gmail_quote">2014/1/9 Marco Hugentobler
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:marco.hugentobler@sourcepole.ch"
target="_blank">marco.hugentobler@sourcepole.ch</a>></span><br>
<blockquote class="gmail_quote">
<div>
<div>
<div>>I thought this OGC filtering stuff
was already implemented for WFS server
isn't it?<br>
</div>
</div>
</div>
</blockquote>
</div>
</div>
<div class="gmail_extra">Ok, summarizing:</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">in WFS we have the standard
OGC "FILTER" plus the QGIS custom "EXP_FILTER"</div>
<div class="gmail_extra">in WMS we have QGIS custom
"FILTER"</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">IMHO the best solution would
be to have the same parameters also in WMS, so:</div>
<div class="gmail_extra">
<br>
</div>
<div class="gmail_extra">rename WMS QGIS custom
"FILTER" to "EXP_FILTER" and</div>
<div class="gmail_extra">implement OGC "FILTER" even
if it's not in the standard</div>
<div class="gmail_extra">
<br>
</div>
<div class="gmail_extra">Do you think that we can
re-use the WFS OGC FILTER code for the WMS OGC
FILTER implementation?</div>
<div class="im">
<div class="gmail_extra"><br>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<br>
</div>
<div>Any comment on this?</div>
<div><br>
</div>
<div>Should I file a [Feature] ticket? </div>
<div><br>
</div>
<div> </div>
</div>
-- <br>
Alessandro Pasotti<br>
w3: <a moz-do-not-send="true" href="http://www.itopen.it">www.itopen.it</a>
</div>
</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Dr. Marco Hugentobler
Sourcepole - Linux & Open Source Solutions
Weberstrasse 5, CH-8004 Zürich, Switzerland
<a class="moz-txt-link-abbreviated" href="mailto:marco.hugentobler@sourcepole.ch">marco.hugentobler@sourcepole.ch</a> <a class="moz-txt-link-freetext" href="http://www.sourcepole.ch">http://www.sourcepole.ch</a>
Technical Advisor QGIS Project Steering Committee </pre>
</body>
</html>