Mercurial > gemma
view TODOs-historization_ng.md @ 4047:8c6bc85db711 historization_ng
WIP: Remove references to bottleneck validity in DB schema.
author | Sascha Wilde <wilde@intevation.de> |
---|---|
date | Wed, 24 Jul 2019 16:15:21 +0200 |
parents | 39441cdc5021 |
children | 6bfe42f88638 |
line wrap: on
line source
# TODOs for HNG (Historization NextGen) ## gauges-reference-water-levels Could be seen as direct part of the gauge data and therefore kept with the foll primary key reference... ## Water level diagrams: One time range might reference different verions of one gauge: - How is that hanedled currently? - How to handle it in HNG? ## Map display: Ensure only current gauges are shown in all situations - Gauges layer - Search - more? ## Bottlenecks: Always associate the correct gauge, when: - Uploading Sounding results (how is that currently handled?) - Displaying Sounding data - Creating/showing X-Cuts - Unclear: what constraints shall we chekc for on bottleneck imports? Cut end of validit _after_ accepting the new one. ## Sounding Results: - Check during upload that matching bottleneck and reference gauge data is available (and use ist correctly) - Use correct reference gauge for X-Cuts - (Maybe later) use matching BN data for display ## EVERYTHING ELSE Not being mentioned here, doesn't mean something is done... # DONE Stuff done will bemoved moved here for reference: