On Mon, Sep 23, 2019 at 8:51 PM Even Rouault <[email protected]> wrote:
> Hi, > > Just a quick note to mention, to avoid any potential duplication of work > if > someone else is about to do that, that in the coming weeks I'll work on > adding > support for "OGC API - Features" (previously known as WFS3) on the client > side, now that it is about to be finalized to its 1.0 version. > > Hi Even, I'm happy to see you taking this up! > My initial thought would tend towards to try to add it into the existing > WFS > provider. From a UI perspective, I've got some feedback that it would > probably > be best to access it through the existing WFS entry to avoid cluttering > the UI > with a new provider. > I would probably advise against this approach, from the architectural point of view, I think that it would be better to address the new OGC JSON-based API with an abstract base class for providers that consume that kind of API and make WFS3 the first concrete implementation of that base. > On the code level, the choice between having a dedicated provider or > adding > functionnality in the existing WFS one is not so obvious. Technologically, > there is little in common between traditional WFS ( XML & GML based, KVP > based > requests ), and OAPI-F (my own acronym for OGC API - Features) (JSON & > GeoJSON > based, with a linking approach). But the WFS provider has something which > is > quite useful for the OAPI-F context, which is the local Spatialite-based > cache > & the background download capability. Extracting that from the WFS > provider > and be generic enough for multiple providers could be quite involved. > > Re-using the WFS-sqlite feature cache looks a good idea, you might want to refactor it out to core to make it re-usable from a family of providers. > Opinions about above directions welcome. > > Even > Looking forward to test it against QGIS Server, we will be providing a complete client+server solution! Thanks! -- Alessandro Pasotti w3: www.itopen.it
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
