This is the main geOrchestra Spatial Data Infrastructure repository, which hosts the source code.
Branch: 18.06
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Instructions to report a security issue. Jan 16, 2019
analytics Ignore header.jsp, created at build time Nov 27, 2018
atlas http-forwarded jetty module added Nov 15, 2018
cas-server-webapp cas - fix default headerHeight format, removing duplicate suffix px Jan 8, 2019
commons 18.06 release Jul 20, 2018
console Fix a bug in console role management by which isFavorite:false won't … Jan 25, 2019
docs postgresql - fix file loading order to generate docker image Nov 22, 2018
epsg-extension 18.06 release Jul 20, 2018
extractorapp Remove the mention to the custom EmailFactory bc it's no more recomme… Jan 22, 2019
geonetwork @ 11fcee7 geonetwork - add a translation string to geonetwork Jan 16, 2019
geoserver Update the GeoServer submodule Jan 24, 2019
geotools @ 6b08a47 Bumping to customized version of GeoTools (SAX parsing issues) Sep 5, 2014
geowebcache-webapp http-forwarded jetty module added Nov 15, 2018
header http-forwarded jetty module added Nov 15, 2018
ldap Integrate dinkel work in geOr Oct 2, 2018
mapfishapp Merge branch '17.12' into 18.06 Feb 13, 2019
migrations update release notes - closes #2129 Jul 20, 2018
ogc-server-statistics test for layers processing whne getcoverage request Aug 7, 2018
postgresql Fix postgis install & optimize docker image size Nov 29, 2018
security-proxy SP - fixing tests on community CI Feb 6, 2019
tests/nodejs Use a new directory: "tests" May 12, 2013
.gitignore ignore the target directory in the root Nov 27, 2018
.gitmodules cleaning gitmodules May 14, 2018
.travis.yml Add support for IPv6 in travis env Jan 8, 2018
AUTHORS.txt Updating AUTHORS Mar 18, 2016 Create Nov 23, 2017 Update Jan 26, 2017
Makefile Update Makefile Oct 2, 2018 Merge branch '13.09' Dec 19, 2013 Instructions to report a security issue. Jan 16, 2019 update release notes - closes #2129 Jul 20, 2018 update the RELEASE_PROCEDURE Feb 7, 2018
pom.xml Merge branch '17.12' into 18.06 Aug 31, 2018


Build Status Codacy Badge

geOrchestra is a complete Spatial Data Infrastructure solution.

It features a metadata catalog (GeoNetwork 3.4), an OGC server (GeoServer 2.12) with fine-grained access control (based on GeoFence), an advanced viewer and editor, an extractor and many more (security and auth system based on proxy/CAS/LDAP, analytics, admin UIs, ...)


A new release is published every 6 months and is supported during 12 months. Stable versions are named by their release date, eg 18.06 (latest stable) was published in June 2018.

Have a look at the release notes for more information.


Depending on your goals and skills, there are several ways to install geOrchestra:

  • a docker composition, which pulls pre-built images from docker hub, is perfect for a quick start. Provided you have a good download speed and recent machine (8Gb required), you'll be up and running within 10 minutes. Read how to run geOrchestra on Docker here. Not recommended for production as is, since it pulls images tagged latest, matching this repos's master branch (frequently broken).
  • a contributed ansible playbook allows you to spin an instance in a few minutes. This is probably the easiest way to create a small server, since it takes care of installing the middleware, fetching the webapps and configuring them. Same issue as above: it pulls debian packages from the master branch, frequently broken.
  • generic debian (or yum) packages are perfect to create complex production architectures, but you'll have to install and configure the middleware first. The community provides these packages on a "best effort" basis, with no warranty at all.
  • you could also use the generic wars with their "datadir", as an alternate method. The above packages provide both.
  • finally, building from the sources is the most flexible solution. You get custom WAR files, packages or docker images that you can deploy to dev, test, or production servers.

If you opt for the middleware setup by yourself, there are several optimizations, good practices and tutorials that are worth reading. Note that the minimum system requirement is 2 cores and 4Gb RAM, but we recommend at least 4 cores and 8 Gb RAM for a production instance. More RAM is of course better !


If you need more information, please ask on the geOrchestra mailing list.

For help setting up your instance, or for dev-related questions, use the #georchestra IRC channel or the dev/tech list.

If you found a bug or want to propose improvements and new features, please fill a new issue in the GitHub tracker.

If you want to report a security issue, please don't fill an issue. Instead, send a mail to, you will be later contacted for more details.


Additional information can be found in the website and in the following links:

  • catalog: standard GeoNetwork with a light customization,
  • viewer (aka mapfishapp): a robust, OGC-compliant webgis with editing capabilities,
  • extractor (aka extractorapp): able to create zips from data served through OGC web services and send an email when your extraction is done,
  • geoserver: the reference implementation for many OGC web services,
  • geowebcache: a fast and easy to use tile cache,
  • geofence: optional, advanced OGC web services security,
  • analytics: admin-oriented module, a front-end to the ogc-server-statistics module,
  • console: also an admin-oriented module, to manage users and groups,
  • header: the common header which is used by all modules,
  • epsg-extension: a plugin to override the geotools srs definitions.
  • atlas: a server-side component to print multi-page PDF with one geographic feature per page.