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
masterbranch (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.
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 email@example.com, you will be later contacted for more details.
Additional information can be found in the georchestra.org 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.