Skip to content
Lipas is a nationwide, public GIS service of Finnish sport sites.
Branch: master
Clone or download
Latest commit 20e8c41 Jul 20, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
certs Nginx SSL configuration Jul 30, 2018
db Stopped providing $DB_HOST for db init scripts inside docker May 25, 2018
htpasswd Allow access to Kibana from JYU network with http basic auth Mar 25, 2019
kibana Cleaned up Kibana config Mar 25, 2019
logstash/pipeline Added logstash and changed docker to push logs there Mar 15, 2019
mapproxy Cleanup Mar 15, 2019
nginx Changed Tilastokeskus server to one that can be accessed on port 80 May 31, 2019
webapp Added remaining subsidies Jul 20, 2019 [WIP] integrations to and from old lipas Dec 31, 2018
.gitignore Build uberjar and run jetty server in prod Jul 31, 2018
.travis.yml Added fix for Travis to not conflict with port `5432` Jul 17, 2018
LICENSE Create LICENSE Aug 17, 2018 Updated readme Apr 18, 2019
docker-compose.yml Updated ELK-stack Jun 1, 2019


prod | dev | ci | issues | dev-tasks | use-cases (finnish) | ideas (finnish)

LIPAS is a nationwide, public GIS service of Finnish sport sites. More information here.

LIPAS consists of three main services:

  • Hub for data and information of sports facility conditions
  • Monitoring energy efficiency of public ice stadiums
  • Monitoring energy efficiency of public indoor swimming pools

Tech stack

Architecture diagram


Webapp is written in Clojure(script).


Webapp backend is a simple HTTP(s) service with endpoints for different tasks. Some endpoints require authentication. Authentication is implemented using HTTP-basic authentication and signed JWT-tokens.


Postgis database

Spatial PostGIS for master data storage.


Web facing Nginx reverse proxy, ssl-termination.


Mapproxy basemap proxy and cache.


ELK (ElasticSearch, Logstash, Kibana) is used to provide webapp search funtionalities as well as data and monitoring information.

Old Lipas

All data flows also to old Lipas which exposes the data through Geoserver and legacy REST-Api.


See Api-documentation here.


Geoserver publishing spatial data. See available layers here.

Dev-env setup

# Create env-file from template

# Fill in secrets

# Run setup script


Add following to your hosts file to use same hostnames in both docker and host while developing.

# Lipas dev       postgres       backend-dev       mapproxy       elasticsearch       kibana       logstash       proxy

Production build


docker-compose run backend-build

See certs/


docker-compose run frontend-npm-deps
docker-compose run frontend-npm-bundle
docker-compose run frontend-build
You can’t perform that action at this time.