comparison client/src/components/importconfiguration/types/Fairwaymarks.vue @ 4962:1b309a8e7673 fairway-marks-import

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.
author Tom Gottfried <tom@intevation.de>
date Thu, 27 Feb 2020 21:05:09 +0100
parents d456621404c2
children 58dc06e91c39
comparison
equal deleted inserted replaced
4961:67d78b74fe43 4962:1b309a8e7673
123 this.$emit("sortByChanged", e.target.value); 123 this.$emit("sortByChanged", e.target.value);
124 } 124 }
125 }, 125 },
126 FAIRWAYMARKS: { 126 FAIRWAYMARKS: {
127 BCNISD: "Beacon, isolated danger (MARITIME/Hydro feature)", 127 BCNISD: "Beacon, isolated danger (MARITIME/Hydro feature)",
128 BCNLAT: "Beacon, lateral (MARITIME/Hydro feature)", 128 BCNLAT_hydro: "Beacon, lateral (MARITIME/Hydro feature)",
129 bcnlat_ienc: "Beacon, lateral (IENC feature)",
129 BOYCAR: "Buoy, cardinal (MARITIME/Hydro feature)", 130 BOYCAR: "Buoy, cardinal (MARITIME/Hydro feature)",
130 BOYISD: "Buoy, isolated danger (MARITIME/Hydro feature)", 131 BOYISD: "Buoy, isolated danger (MARITIME/Hydro feature)",
131 BOYLAT: "Buoy, lateral (MARITIME/Hydro feature)", 132 BOYLAT: "Buoy, lateral (MARITIME/Hydro feature)",
132 BOYSAW: "Buoy, safe water (MARITIME/Hydro feature)", 133 BOYSAW: "Buoy, safe water (MARITIME/Hydro feature)",
133 BOYSPP: "Buoy, special purpose/general (MARITIME/Hydro feature)", 134 BOYSPP: "Buoy, special purpose/general (MARITIME/Hydro feature)",