Mercurial > gemma
view example_conf.toml @ 5075:aeb100b4c41b time-sliding
timeslider: prerequisites for time travel
* splitting selected time to
a) the actual time visible on map (in the toolbar)
b) the actual selected time with the timeslider
Analogous to an event "ongoing refresh" we have "ongoing timeslide".
During this event (a) stays the same according to the information presented on the screen.
(b) is not affected. As soon as the loaders settle, the next requests are started with the
then "selected time" and the actual time visible on map is set to this new value.
Reloading the layers "jumps back to now".
author | Thomas Junk <thomas.junk@intevation.de> |
---|---|
date | Fri, 13 Mar 2020 10:37:44 +0100 |
parents | 209b10f7bb2c |
children | 492fc5870330 |
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" # Duration until sessions expire if not renewed #session-timeout = "3h" # ---------------------------------------------------------------------- # 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 # geoserver-startup-sql can be used to add SQL commands to GeoServers database # session start script. See # https://docs.geoserver.org/stable/en/user/data/database/sqlsession.html # Note that the commands will be executed as the user configured as 'db-user'. # This can be used for example to set query planer configurations that fix # bad query plans during GeoServer accessing the published layers. # Currently, the published layer 'bottlenecks_geoserver' is known to trigger # inefficient nested loop joins due to underestimation of the number of entries # in the bottlenecks table. Hence the example setting: geoserver-startup-sql = "SET enable_nestloop TO off" # 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" # ---------------------------------------------------------------------- # SOAP/XML-based importer setup: # soap-timeout = "3m" # Schema for "Testclient imports" # schema-dirs = "$PATH_TO_SCHEMATA" # published-config ="$PATH/pub-config.json"