Mercurial > gemma
view example_conf.toml @ 2425:4c16f5ad1905
Make area generation more robust
Valid geometries can become invalid geometries during transformation
e.g. due to very small 'minimum clearance' (see PostGIS docs) and
numerical inaccuracy of the transformation. Thus, try to repair
polygons of the input area after transformation and calculate
the union of the result polygons before transformation to avoid
'TopologyException' in the union operations.
The simulated waterway area of the changed axis in the test data
is affected here, but real waterway area data with complex shore
lines could likely be affected, too.
author | Tom Gottfried <tom@intevation.de> |
---|---|
date | Thu, 28 Feb 2019 16:36:49 +0100 |
parents | 783c1454ab47 |
children | 0db742c7813d |
line wrap: on
line source
# ---------------------------------------------------------------------- # Example configuration for gemma back end # ---------------------------------------------------------------------- # ---------------------------------------------------------------------- # Basic Setup: # Host and port to listen on: host = "0.0.0.0" #port = 8000 # Where to find the data of the web client (SPA) to serve: web = "./web" # File to persist session data: sessions = "/tmp/gemma_session.data" # ---------------------------------------------------------------------- # Database: # DB connection configuration: db-host = "gemma_db" #db-name = "gemma" #db-port = 5432 #db-ssl = "prefer" db-user = "meta_login" db-password = "geo2Serv" # ---------------------------------------------------------------------- # Mail setup: # SMTP connection configuration: #mail-host = "localhost" #mail-password = "SECRET" #mail-port = 465 #mail-user = "gemma" # Client data to use: #mail-from = "noreplay@localhost" #mail-helo = "localhost" # ---------------------------------------------------------------------- # OGC services setup: # Connection to GeoServer instance for internal OGC services geoserver-url = "http://gemma_geoserver:8080/geoserver" #geoserver-user = "admin" #geoserver-password = "geoserver" # Clean GeoServer setup on startup # Persisting this is mainly useful in some dev setups. # Cleaning up the GeoServer should be done with # an explicit --geoserver-clean on the command line. #geoserver-clean = true # Proxy settings for external OGC services #proxy-key = "SECRET" #proxy-prefix = "http://localhost:8000" # # Server is known on the outside as: # external-url = "http://localhost:8000" # ---------------------------------------------------------------------- # CORS setup: #allowed-origins = "http://example.com" # ----------------------- # Schema for "Testclient imports" # schema-dirs = "$PATH_TO_SCHEMATA"