Mercurial > gemma
changeset 4038:1b6e1d79a0ca historization_ng
Merged
author | Sascha Wilde <wilde@intevation.de> |
---|---|
date | Mon, 22 Jul 2019 15:44:19 +0200 |
parents | 9cfc6f478157 (diff) b10f210af325 (current diff) |
children | 9f9e62f6f4f9 |
files | |
diffstat | 2 files changed, 37 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/TODOs-historization_ng.md Mon Jul 22 15:44:19 2019 +0200 @@ -0,0 +1,36 @@ +# 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? + +## EVERYTHING ELSE + +Not being mentioned here, doesn't mean something is done... + + +# DONE + +Stuff done will bemoved moved here for reference:
--- a/pkg/imports/wg.go Mon Jul 22 11:20:20 2019 +0200 +++ b/pkg/imports/wg.go Mon Jul 22 15:44:19 2019 +0200 @@ -66,7 +66,7 @@ const ( eraseObsoleteGaugesSQL = ` -UPDATE waterway.gauges SET erased = true +UPDATE waterway.gauges SET erased = true, validity = validity - '[now,)' WHERE NOT erased AND (location).country_code = ANY($1) AND isrs_astext(location) <> ALL($2)