# HG changeset patch
# User Sascha Wilde <wilde@intevation.de>
# Date 1563803059 -7200
# Node ID 1b6e1d79a0ca0919f525e668962e7dacb2580999
# Parent  9cfc6f4781575c0cdd8663d6540e3f82806b79d3# Parent  b10f210af325094781a4a2247ca2b56b04bbf6f9
Merged

diff -r b10f210af325 -r 1b6e1d79a0ca TODOs-historization_ng.md
--- /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:
diff -r b10f210af325 -r 1b6e1d79a0ca pkg/imports/wg.go
--- 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)