Mercurial > gemma
graph
-
Use database triggers to move referencing objects to new versionsSat, 15 Jun 2019 09:24:28 +0200, by Tom Gottfried
-
SR import: Made error messages symmetrical to multi beam if no matching bottleneck is found for single beam imports.Fri, 14 Jun 2019 17:56:42 +0200, by Sascha L. Teichmann
-
Be more verbose if a SOAP call fails.Fri, 14 Jun 2019 16:21:25 +0200, by Sascha L. Teichmann
-
Added easy to remember and use waterway admin users for all countries.Fri, 14 Jun 2019 13:30:33 +0200, by Sascha Wilde
-
Added handcrafted responsibility areas and matching stretches.Fri, 14 Jun 2019 13:29:40 +0200, by Sascha Wilde
-
Merged single-beam branch into default.Fri, 14 Jun 2019 12:03:47 +0200, by Sascha L. Teichmann
-
Merged default into single-beam branch. single-beamFri, 14 Jun 2019 12:02:58 +0200, by Sascha L. Teichmann
-
Handle th case that a boundary polygon is uploaded along side with the single beam scan. single-beamFri, 14 Jun 2019 11:59:14 +0200, by Sascha L. Teichmann
-
client: changed button color on login screenFri, 14 Jun 2019 11:16:09 +0200, by Markus Kottlaender
-
Ensure sounding results are associated to matching bottleneck versionThu, 13 Jun 2019 19:13:42 +0200, by Tom Gottfried
-
Started with cleaning up the single beam import. single-beamThu, 13 Jun 2019 18:33:54 +0200, by Sascha L. Teichmann
-
Fixed problem with wrong EPSG code. single-beamThu, 13 Jun 2019 17:07:28 +0200, by Sascha L. Teichmann
-
Another attempt to fix the ST_IsValid check contstraint problem ... and also failed. single-beamThu, 13 Jun 2019 16:36:21 +0200, by Sascha L. Teichmann