What peoples thoughts about the state of this provider. The currently limitations I see currently with it is:
poor handling of larges datasets (e.g http://hub.qgis.org/issues/4604) doesn't support WFS 1.1 or WFS 2.0 (or GML payloads that go along with those versions) doesn't support setSubsetString. poor operator support for filters e.g no LIKE or spatial stuff Doesn't query GetCapabilities to determine supported functions or operators. Poor user connection UI (i have a patch to improve this to using QSortFilterProxyModel) 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: common code (worked on by more people) handles filters better handles talking to different implementations of the standards better (e.g mapserver, Geoserver, deegree) handles fetching larger datasets better e.g with paging support etc Of course continuing to develop the current driver has the advantage of tighter integration with the QT framework and QGIS. Such as utilising QT network and proxy management. Cheers, Jeremy ________________________________ 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 [email protected]) 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.
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
