geOrchestra’s core features a security proxy and a single-sign-on authentication system. Next to this core are independant and interoperable modules to build your own Spatial Data Infrastructure:
- a metadata catalog based on GeoNetwork,
- a map and features server: GeoServer,
- a map tile server: GeoWebCache,
- an advanced web map viewer,
- a data extractor,
- and several other admin-oriented modules.
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,
- simple catalog (aka catalogapp): a very lightweight UI to query CSW services,
- analytics: admin-oriented module, a front-end to the ogc-server-statistics and downloadform modules,
- ldapadmin: 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.
http://www.georchestra.org/
https://github.com/georchestra/georchestra
No comments:
Post a Comment