new database design

[jkall]

It might be worth to overlook the database design to make it more dynamic and useful for various applications.

Related issues are: duplicate obsid!: https://github.com/jkall/qgis-midvatten-plugin/issues/70 https://github.com/jkall/qgis-midvatten-plugin/issues/67 https://github.com/jkall/qgis-midvatten-plugin/issues/57 https://github.com/jkall/qgis-midvatten-plugin/issues/43 https://github.com/jkall/qgis-midvatten-plugin/issues/34 https://github.com/jkall/qgis-midvatten-plugin/issues/80 https://github.com/jkall/qgis-midvatten-plugin/issues/81 https://github.com/jkall/qgis-midvatten-plugin/issues/205 https://github.com/jkall/qgis-midvatten-plugin/issues/264

should maintain backwards compatibility

[jkall]

Databases and data exchange formats to study: http://ags.org.uk/data-format/ http://archydrogw.com/Main_Page Wojda et al: http://orbi.ulg.ac.be/handle/2268/6168 Chesnaux: https://www.researchgate.net/publication/251507316_Building_a_geodatabase_for_mapping_hydrogeological_features_and_3D_modeling_of_groundwater_systems_Application_to_the_Saguenay-Lac-StJean_region_Canada SGF system of notations http://www.sgf.net/getfile.ashx?cid=483148&cc=3&refid=3

Note: AGS data exchange format is adopted in Australia and New Zealand

AGS also used by: gINT- https://www.bentley.com/en/products/brands/gint keyhole- http://www.keynetix.com/category/keyhole/

[inkenbrandt]

You may also want to consider the ODM design by CUAHSI: http://his.cuahsi.org/

Even though they do mostly surface water stuff, it might be relevant for some of your tables.

[jkall]

Note-to-self: we must not be limited by qgis layers for the new database design.

The layers might as well be views from the database or joins in qgis. Updateable views (http://hub.qgis.org/issues/4787) will probably be useful.

[jkall]

We should also carefully study the proposed standard from OGC: http://www.opengeospatial.org/standards/gwml2