<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Jeremy<br>
<br>
<div><font face="Verdana" size="2"><span
class="923152606-31012013">> doesn't support
setSubsetString.</span></font></div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013">> poor operator support for
filters e.g no LIKE or spatial stuff</span></font></div>
<br>
This is not a general limitation of the WFS provider. There is the
possibility of writing the filter xml into the filter dialog as a
string if needed. I know, it is not very comfortable. But does the
OGR driver come with a better GUI?<br>
<br>
<span style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: #37ad47;
FONT-SIZE: 10pt" lang="EN-US">
<div align="left"><span class="923152606-31012013"><font
color="#000000">>Of course continuing to develop the
current driver has the advantage of tighter integration
with the QT framework and >QGIS. Such as utilising</font></span><span
class="923152606-31012013"><font color="#000000"> QT network
and proxy management.</font></span></div>
</span><br>
I'd add to that list the possibility of aborting long requests and
receiving status updates (progress bar if server provides total,
number of incoming bytes if not).<br>
<font face="Verdana" size="2"><span class="923152606-31012013"><font
size="2"><font size="2">In my opinion, it is definitely wo<font
size="2">rth to have a native provider. <font size="2">Support
for GML2 is </font></font></font></font></span></font>already
in QgsGeometry and there is no reason why not adding GML3 too.<br>
<br>
Regards,<br>
Marco<br>
<br>
Am 31.01.2013 07:41, schrieb Jeremy Palmer:<br>
</div>
<blockquote
cite="mid:316886599.1266188.1359614663271.JavaMail.root@s-101-LINZ"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="GENERATOR" content="MSHTML 8.00.6001.19328">
<div><font face="Verdana" size="2"><span
class="923152606-31012013">What peoples thoughts about the
state of this provider. The currently limitations I see
currently with it is:</span></font></div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013"></span></font> </div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013">poor handling of larges datasets
(e.g
<a moz-do-not-send="true"
href="http://hub.qgis.org/issues/4604">http://hub.qgis.org/issues/4604</a>)</span></font></div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013">doesn't support WFS 1.1 or WFS
2.0 (or GML payloads that go along with those versions)</span></font></div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013">doesn't support setSubsetString.</span></font></div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013">poor operator support for filters
e.g no LIKE or spatial stuff</span></font></div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013">Doesn't query GetCapabilities to
determine supported functions or operators. </span></font></div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013">Poor user connection UI (i have a
patch to improve this to using QSortFilterProxyModel)</span></font></div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013"></span></font> </div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013">I wondering if one way to deal to
a lot of these issues is to use the OGR WFS implementation
with QGIS. As of OGR 1.9 its support for WFS is very good.
Benefits are:</span></font></div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013"></span></font> </div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013">common code (worked on by more
people)</span></font></div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013">handles filters better</span></font></div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013">handles talking to different
implementations of the standards better (e.g mapserver,
Geoserver, deegree)</span></font></div>
<div><font face="Verdana" size="2"><span
class="923152606-31012013">handles fetching larger datasets
better e.g with paging support etc</span></font></div>
<div align="left"><span style="FONT-FAMILY:
'Verdana','sans-serif'; COLOR: #37ad47; FONT-SIZE: 10pt"
lang="EN-US">
<div align="left"> </div>
<div align="left"><span class="923152606-31012013"><font
color="#000000">Of course continuing to develop the
current driver has the advantage of tighter integration
with the QT framework and QGIS. Such as utilising</font></span><span
class="923152606-31012013"><font color="#000000"> QT
network and proxy management.</font></span></div>
<div align="left"><span class="923152606-31012013"></span> </div>
<div align="left"><span class="923152606-31012013"><font
color="#000000">Cheers,</font></span></div>
<div align="left"><span class="923152606-31012013"><font
color="#000000">Jeremy</font></span></div>
</span></div>
<br>
<hr>
<font color="Black" face="Verdana" size="2">This message contains
information, which is confidential and may be subject to legal
privilege. If you are not the intended recipient, you must not
peruse, use, disseminate, distribute or copy this message. If
you have received this message in error, please notify us
immediately (Phone 0800 665 463 or <a class="moz-txt-link-abbreviated" href="mailto:info@linz.govt.nz">info@linz.govt.nz</a>) and
destroy the original message. LINZ accepts no responsibility for
changes to this email, or for any attachments, after its
transmission from LINZ. Thank You.<br>
</font>
</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>