[QGIS-Developer] What to do about WFS test failures?

Nyall Dawson nyall.dawson at gmail.com
Mon Sep 3 17:16:28 PDT 2018


On Tue, 4 Sep 2018 at 05:50, Even Rouault <even.rouault at spatialys.com> wrote:
>
> Régis,
>
> Not that I'm against improvements, all the contrary, but just wanted to
> underline that the provider was seriously refactored already in 2.16. Clearly
> the lack of WFS-T support for 1.1 and 2.0 in the scope of those enhancements
> can be a source of confusion currently for users. What do you have in mind as
> refactoring exactly ?

I'm with Even here... please, proceed with extreme caution.

We may be seeing issues with the WFS provider since 3.2, but I do not
think a full rewrite is needed/wanted here, and potentially will cause
many regressions given how finicky WFS servers are and how many
server-specific fixes have been required in the current
implementation.

Nyall


>
> Even
>
> > Hi all,
> > I very much think that the WFS client is an really bad state, and is not
> > really reliable, especially in WFS-T context.
> > The good news is that we just have been funded to refactor it !
> > The work should start in september and land in 3.6. I will let our dev's
> > come here with more technical details about the goals. I hope we will also
> > be able to take benefit of this to this the OGC compliancy of the client
> > here.
> > Best regards,
> > Régis
> >
> > Le lun. 3 sept. 2018 à 11:36, Tom Chadwin <tom.chadwin at nnpa.org.uk> a
> >
> > écrit :
> > > I can't offer any helpful suggestions, but just to let you know I finally
> > > had
> > > to disable all my plugin WFS tests. I used to cope, by rerunning failed
> > > Travis runs, but by about three months ago, it seemed no longer usable -
> > > failure after failure.
> > >
> > > I was using a third-party WFS, and perhaps I could have got round this by
> > > adding a WFS provider to the test docker image, but in this plugin's case,
> > > I
> > > didn't think it worth the significant effort to do so. The WM(T)S tests
> > > also
> > > use third-party sources and seem stable, so perhaps this wasn't the
> > > underlying issue anyway.
> > >
> > > If an improvement or solution could be found, it would be great to
> > > reinstate
> > > these tests.
> > >
> > > Thanks
> > >
> > > Tom
> > >
> > >
> > >
> > > -----
> > > Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
> > > --
> > > Sent from:
> > > http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
> > > _______________________________________________
> > > QGIS-Developer mailing list
> > > QGIS-Developer at lists.osgeo.org
> > > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> --
> Spatialys - Geospatial professional services
> http://www.spatialys.com
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


More information about the QGIS-Developer mailing list