Build web front-end #97
Description
This is a meta-ticket for major new functionality
Requirement
A responsive web app that implements all of the functionality of the QGIS plugin
Initial design thoughts
Much of the functionality is in the DB, mainly through triggers.
The plugin doesn't use the PostGIS provider, instead using custom DB interaction. It also does not use standard QGIS editing tools, hence is not too dependent on QGIS itself.
Therefore it makes sense to expose the DB operations via an API with something like PostgREST and build the web app against that. Then the app would only need to emulate the logic that is in the plugin.
Potentially available only as a SaaS, in which case it will need adequate user and role management and a way to manage DBs and perform other admin.
Implications and consequences
- review the DB schema and make it more complete with clearer links to title deed and other potential integrations.
- review the market and general GoGo requirements and refactor or extend this accordingly.
- take the opportunity to refactor the plugin to use the API?
@dimasciput is this enough to have a go at estimating the components and sizes of this job? cc @NyakudyaA @holysanta