Mercurial > gemma
view TODOs-historization_ng.md @ 5155:20f338cb4d48
Add forgotten cleanup of fairway dimensions
This is actually a fixup of rev. e21cbb9768a2, that added database
schema version 1431 with a constraint trigger preventing new or
updated rows to have a duplicate area but missed to cleanup existing
data. So cleanup now, before the duplicates hurt in future imports
that try to keep the duplicates in history.
author | Tom Gottfried <tom@intevation.de> |
---|---|
date | Wed, 01 Apr 2020 19:01:08 +0200 |
parents | 6bfe42f88638 |
children |
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: - Maybe add a constraint to check, that a ref gauge is available? Maybe not neccessary as import isn't possible anyway, as the reference gauge is needed for the import process... (So the constraint would never catch anything, as no data could be produced without ref gauge) Only upside: we would triger if there is an error in the backend generating SR with invalid ref data. - 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: