Mercurial > gemma

comparison README.md @ 610:f62ee9d5bff1

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Document adding of layers to internal OGC services.
author Tom Gottfried <tom@intevation.de>
date Mon, 10 Sep 2018 17:01:24 +0200
parents d68dfbe768e2
children 4ffdb922db44
comparison
equal deleted inserted replaced
609:6dc1b586328e 610:f62ee9d5bff1
26 26
27 - The script must be run as a user with PostgreSQL super user rights. 27 - The script must be run as a user with PostgreSQL super user rights.
28 By convention this is the "postgres" on most systems. 28 By convention this is the "postgres" on most systems.
29 29
30 30
31 ## Setup GeoServer
32
33 - Install and run GeoServer as described here:
34 http://docs.geoserver.org/stable/en/user/installation/
35
36 - Add tables you want to publish as OGC-Service Layers via GeoServer in
37 the database. For example publish the bottleneck areas:
38 ```
39 INSERT INTO sys_admin.published_services (name, as_wfs) VALUES
40 ('waterway.bottlenecks', true);
41 ```
42 In case your gemma is already running (see next section), restart it.
43 Published WFS services will be available at `/api/internal/wfs`. Currently,
44 the same layers will also be available as WMS services at
45 `/api/internal/wms`, regardless of the value of `as_wms` in
46 `sys_admin.published_services`.
47
31 ## Running gemma 48 ## Running gemma
32 49
33 - Best is to create a configuration file. Copy the example from 50 - Best is to create a configuration file. Copy the example from
34 `example_conf.toml` to get started: 51 `example_conf.toml` to get started:
35 ``` 52 ```