Distinguish more clearly between BCNLAT HYDRO and IENC features This allows importing them from different sources while keeping the history of data intact. Additionally, storing them in different tables also allows to have different attributes (here only dirimp via an m:n-table) and different constraints (currently not implemented) according to the IENC feature catalogue. Since both new tables inherit from a table with the same name as the old table, all entries still can be accessed via a table of the same name. Thus, no changes to GeoServer layers are necessary. ToDo: solve layout problems in the client SPA.

#Name of the application, e.g. displayed at login time
VUE_APP_TITLE=Waterway Monitoring system
VUE_APP_WINDOWTITLE=

#Backend URL
VUE_APP_API_URL=/api/
VUE_BACKEND_API_URL=http://gemma-backend:8000

#Path of vendored images is copied during a webpack build
VUE_APP_VENDOR_IMG_PATH=

#Logos to be potentially loaded by the SPA. Can be left blank.
VUE_APP_SECONDARY_LOGO_URL=
VUE_APP_LOGO_FOR_PDF_URL=
VUE_APP_SILENCE_TRANSLATIONWARNINGS =

#Url of user manual
VUE_APP_USER_MANUAL_URL=