In this work package we will explore the options for providing a low bandwidth, high responsiveness approach to providing remote editing of GeoNode layers from QGIS without needing to run WFS. The normal workflow of using WFS often results in very large data transfers between client and server. In our proposed research we will look to implement a simpler system whereby the following workflow is supported:
User adds a GeoNode layer to their QGIS project as a TMS (tiled map service) layer.
A custom tool is provided in QGIS. When the user clicks the map with the tool active, a getFeatureInfo with geometry request is made to the GeoNode backend.
The geometry is placed into a temporary local layer which the user can proceed to edit.
When the edit is complete, a QGIS Server backend specific GeoNode API call will be used to commit the feature back to the backend.
The cached TMS tiles for the layer on the backend will be invalidated and re-rendered to reflect the updated geometry.
The updated tiles will be refreshed on the client side so that the user can see the rendered changes
We will also evaluate the possibility of dynamically switching between WMS and WFS layer backends (as an alternative to the above approach).
In this work package we will explore the options for providing a low bandwidth, high responsiveness approach to providing remote editing of GeoNode layers from QGIS without needing to run WFS. The normal workflow of using WFS often results in very large data transfers between client and server. In our proposed research we will look to implement a simpler system whereby the following workflow is supported:
We will also evaluate the possibility of dynamically switching between WMS and WFS layer backends (as an alternative to the above approach).