Mercurial > gemma
changeset 3703:b07511ff859e
Don't include calculated area in unchanged bottleneck detection.
This makes BN imports considerably faster. The only downside is, that
when die waterway area changes there is no easy way to recalculate the
areas of existing BN. But the semantics in that case are somewhat
hard anyway (think of historization for the old area) so this should
be ok.
author | Sascha Wilde <wilde@intevation.de> |
---|---|
date | Wed, 19 Jun 2019 12:34:48 +0200 |
parents | ee7dc0bea083 |
children | 271683dee9bf 7006b92c0334 |
files | pkg/imports/bn.go |
diffstat | 1 files changed, 0 insertions(+), 7 deletions(-) [+] |
line wrap: on
line diff
--- a/pkg/imports/bn.go Wed Jun 19 11:40:58 2019 +0200 +++ b/pkg/imports/bn.go Wed Jun 19 12:34:48 2019 +0200 @@ -119,7 +119,6 @@ objnam, nobjnm, stretch, - area, rb, lb, responsible_country, @@ -136,11 +135,6 @@ $4, $5, (SELECT r FROM r), - ISRSrange_area( - ISRSrange_axis((SELECT r FROM r), - $15), - (SELECT ST_Collect(CAST(area AS geometry)) - FROM waterway.waterway_area)), $8, $9, $10, @@ -459,7 +453,6 @@ limiting, bn.Date_Info, bn.Source, - tolerance, ) if err != nil {