Areas should be stored on an external geodata server and fetched directly using WFS on the frontend

[hav-gerdint]

Currently all areas are stored in custom JSON data in the database and made available using the /service/areas endpoints.

It would be more flexible and easier if all feature (polygon) definitions were moved to a geodata server (such as a Geoserver instance) and fetched using standard protocols (such as WFS). This would make it much easier to upload and administer feature areas in the system.

• Vector layer sources configuration would reside on the backend and sent to the client at startup (when fetching a baseline).
• Metadata for the features can be stored as feature attributes (area type, id, associated sensitivity matrix, etc).

The system previously contained a Geoserver instance, but it was dropped since it was not used much. When doing this it may make sense to move raster data to the geodata server as well (but the multiband data would probably be cached or stored on the application server for calculation performance reasons). The DataLayeREST endpoints can then be replaced with direct WM(T)S-calls on the frontend to the geoserver.

[hav-gerdint]

Special care would need to be taken for in the interaction with the sensitivity matrix code, which would probably be reworked somewhat.