| Wed, 19 Jun 2019 17:00:08 +0200 |
Sascha Wilde |
Handle updates (vs. historized and new versions) separately.
|
| Wed, 19 Jun 2019 12:34:48 +0200 |
Sascha Wilde |
Don't include calculated area in unchanged bottleneck detection.
|
| Wed, 19 Jun 2019 11:20:47 +0200 |
Sascha Wilde |
Detect and handle unchanged BN during import.
|
| Tue, 18 Jun 2019 12:43:01 +0200 |
Sascha Wilde |
Handle violation of responsibility areas graceful for BN import.
|
| Mon, 17 Jun 2019 18:45:48 +0200 |
Sascha Wilde |
Use infinite validity for bottlenecks with no validity information.
|
| Sat, 15 Jun 2019 14:36:50 +0200 |
Tom Gottfried |
Align bottleneck validity at gauges
|
| Sat, 15 Jun 2019 09:24:28 +0200 |
Tom Gottfried |
Use database triggers to move referencing objects to new versions
|
| Thu, 13 Jun 2019 19:13:42 +0200 |
Tom Gottfried |
Ensure sounding results are associated to matching bottleneck version
|
| Wed, 12 Jun 2019 18:26:26 +0200 |
Tom Gottfried |
Avoid empty validity time ranges
|
| Wed, 12 Jun 2019 17:11:15 +0200 |
Tom Gottfried |
'Historicise' bottlenecks on import
|
| Fri, 31 May 2019 20:06:27 +0200 |
Tom Gottfried |
Introduce hectometer based order for ranges of ISRS location codes
|
| Fri, 31 May 2019 17:24:48 +0200 |
Tom Gottfried |
Improve error message
|
| Wed, 29 May 2019 18:14:20 +0200 |
Tom Gottfried |
Improve error messages if no matching gauge version found
|
| Wed, 29 May 2019 16:56:56 +0200 |
Tom Gottfried |
Improve warning message
|
| Wed, 29 May 2019 16:00:28 +0200 |
Tom Gottfried |
Ignore zero length and whitespace-only values
|
