Mercurial > gemma
comparison TODOs-historization_ng.md @ 4029:9cfc6f478157 historization_ng
Added TODO file for Historization NextGen...
| author | Sascha Wilde <wilde@intevation.de> |
|---|---|
| date | Wed, 17 Jul 2019 18:47:42 +0200 |
| parents | |
| children | 9f9e62f6f4f9 |
comparison
equal
deleted
inserted
replaced
| 4028:5fed2f5bc104 | 4029:9cfc6f478157 |
|---|---|
| 1 # TODOs for HNG (Historization NextGen) | |
| 2 | |
| 3 ## gauges-reference-water-levels | |
| 4 | |
| 5 Could be seen as direct part of the gauge data and therefore kept with | |
| 6 the foll primary key reference... | |
| 7 | |
| 8 ## Water level diagrams: | |
| 9 | |
| 10 One time range might reference different verions of one gauge: | |
| 11 - How is that hanedled currently? | |
| 12 - How to handle it in HNG? | |
| 13 | |
| 14 ## Map display: | |
| 15 | |
| 16 Ensure only current gauges are shown in all situations | |
| 17 - Gauges layer | |
| 18 - Search | |
| 19 - more? | |
| 20 | |
| 21 ## Bottlenecks: | |
| 22 | |
| 23 Always associate the correct gauge, when: | |
| 24 - Uploading Sounding results (how is that currently handled?) | |
| 25 - Displaying Sounding data | |
| 26 - Creating/showing X-Cuts | |
| 27 - Unclear: what constraints shall we chekc for on bottleneck imports? | |
| 28 | |
| 29 ## EVERYTHING ELSE | |
| 30 | |
| 31 Not being mentioned here, doesn't mean something is done... | |
| 32 | |
| 33 | |
| 34 # DONE | |
| 35 | |
| 36 Stuff done will bemoved moved here for reference: |