Mercurial > gemma
view schema/demo-data/README @ 5030:737d7859dd86
Store fairway dimensions as MultiPolygon
This avoids storing a single invalid geometry from the data source
as multiple valid geometries with duplicate attribute sets.
The previous behaviour was not correctly handled in import tracking,
because only the ID of the first item in a set of multiple geometries
generated from a single entry from the data source was tracked.
author | Tom Gottfried <tom@intevation.de> |
---|---|
date | Wed, 18 Mar 2020 18:42:30 +0100 |
parents | 5e38667f740c |
children |
line wrap: on
line source
------------------------------------------------------------------------ !!!!!! WARNING !!!!!! Data within this directory is provided for the sole purpose of testing and demonstration of the Gemma software. It is neither intended nor suitable for any kind of production use. THIS DATA CONTAINS UNSAFE AND PUBLICLY KNOWN PASSWORDS. DO NOT INSTALL ON REMOTE ACCESSIBLE SYSTEMS! ------------------------------------------------------------------------ Defined Users: | Username | Password | Role | Country | |----------+----------+------------------------+---------| | sophie | so2Phie4 | System Administrator | AT | | lucian | lu2Cian4 | Waterway Administrator | RO | | oana | oa2Na2 | Waterway User | RO | | penka | pe2Nka3 | Waterway Administrator | BG | | vanja | va2Nja3 | Waterway User | BG | Installation: We assume, you already have a database "gemma" with the Gemma schema in place. As postgres super user ("postgres" on most default installations): psql -f roles.sql -d gemma psql -f users.sql -d gemma