<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="GENERATOR" content="MSHTML 8.00.6001.19328">
</head>
<body>
<div><font size="2" face="Verdana"><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 size="2" face="Verdana"><span class="923152606-31012013"></span></font> </div>
<div><font size="2" face="Verdana"><span class="923152606-31012013">poor handling of larges datasets (e.g
<a href="http://hub.qgis.org/issues/4604">http://hub.qgis.org/issues/4604</a>)</span></font></div>
<div><font size="2" face="Verdana"><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 size="2" face="Verdana"><span class="923152606-31012013">doesn't support setSubsetString.</span></font></div>
<div><font size="2" face="Verdana"><span class="923152606-31012013">poor operator support for filters e.g no LIKE or spatial stuff</span></font></div>
<div><font size="2" face="Verdana"><span class="923152606-31012013">Doesn't query GetCapabilities to determine supported functions or operators. </span></font></div>
<div><font size="2" face="Verdana"><span class="923152606-31012013">Poor user connection UI (i have a patch to improve this to using QSortFilterProxyModel)</span></font></div>
<div><font size="2" face="Verdana"><span class="923152606-31012013"></span></font> </div>
<div><font size="2" face="Verdana"><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 size="2" face="Verdana"><span class="923152606-31012013"></span></font> </div>
<div><font size="2" face="Verdana"><span class="923152606-31012013">common code (worked on by more people)</span></font></div>
<div><font size="2" face="Verdana"><span class="923152606-31012013">handles filters better</span></font></div>
<div><font size="2" face="Verdana"><span class="923152606-31012013">handles talking to different implementations of the standards better (e.g mapserver, Geoserver, deegree)</span></font></div>
<div><font size="2" face="Verdana"><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"><font color="#000000"></font> </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"><font color="#000000"></font></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></span></div>
</div>
<br>
<hr>
<font face="Verdana" color="Black" 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 info@linz.govt.nz) 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>
</body>
</html>