Mercurial > gemma
view client/src/components/Pane.vue @ 5095:e21cbb9768a2
Prevent duplicate fairway areas
In principal, there can be only one or no fairway area at each point
on the map. Since polygons from real data will often be topologically
inexact, just disallow equal geometries. This will also help to
avoid importing duplicates with concurrent imports, once the history
of fairway dimensions will be preserved.
author | Tom Gottfried <tom@intevation.de> |
---|---|
date | Wed, 25 Mar 2020 18:10:02 +0100 |
parents | fa7dc3f31ef3 |
children |
line wrap: on
line source
<template> <div :id="pane.id" class="pane d-flex position-relative"> <component :is="pane.component" :key="pane.id" /> </div> </template> <script> /* This is Free Software under GNU Affero General Public License v >= 3.0 * without warranty, see README.md and license for details. * * SPDX-License-Identifier: AGPL-3.0-or-later * License-Filename: LICENSES/AGPL-3.0.txt * * Copyright (C) 2018 by via donau * – Österreichische Wasserstraßen-Gesellschaft mbH * Software engineering by Intevation GmbH * * Author(s): * Markus Kottländer <markus.kottlaender@intevation.de> */ export default { props: ["pane"], components: { // all components that are supposed to be displayed in a pane must be registered here Map: () => import("./map/Map"), Fairwayprofile: () => import("./fairway/Fairwayprofile"), AvailableFairwayDepth: () => import("./fairway/AvailableFairwayDepth"), AvailableFairwayDepthLNWL: () => import("./fairway/AvailableFairwayDepthLNWL"), Waterlevel: () => import("./gauge/Waterlevel"), HydrologicalConditions: () => import("./gauge/HydrologicalConditions") } }; </script>