Software Stack

Scope
(The scope of the Software Stack is currently in definition process)


 * The technological scope of the OSGeo Software Stack comprises all OSGeo Open Source Projects [1]
 * The geographical scope is worldwide. The stack is populated with Public Geospatial Data [2] by the Public Geospatial Data Committee
 * The Education and Curriculum Committee uses the populated Stack to implement Online tutorials, and disseminate and presentat spatial data and software
 * The OSGeo Software Projects maintain the OSGeo Software Stack for different purposes
 * Develeopment Server with Automated Build / Smoke Test System nightly builds, kitchen sink, bleeding edge. This/these server/s hurt/s.
 * Operative test server with feature frozen pre release software. Used to broaden the scope of people who want (and through this infrastucture are empowered to) test the newest stuff hands on [3]
 * The Reference Server hosts productive/stable versions with comprehensive Demo Sites
 * The Promotion and Visibility Committee promotes the visible infrastructure


 * References
 * [1] https -> stable docs
 * [2] http -> docs in work progress
 * [3] Example: http://www.mapbender.org/index.php/Development_Server

Software used
We move to install and maintain a stable version of a basic SDI stack consisting of:
 * Community MapBuilder as WMS and WFS-T Client
 * GDAL as Geo Data Access Layer
 * GeoTools (in the guise of GeoServer as WFS-T)
 * GRASS GIS (via ssh, PHP, SWIG)
 * Mapbender as WMS and WFS-T Client
 * MapServer as WMS (and WFS)
 * OSSIM as awsome
 * PostGIS as spatial extension

The server(s) needs to run a basic LAMP stack ++
 * LDAP (authenticate)
 * Apache http Server
 * Apache Tomcat
 * Java (1.4, 1.5?)
 * PostgreSQL
 * MySQL
 * PHP, Perl, Python, Pomething pelse
 * MediaWiki
 * Plone

Applications and Demos

 * MapServer automatically brings some HTML demos that just need to get set up
 * GeoServer packages with MapBuilder and some demo data demo data should be moved into the PostgreSQL database
 * some Open/Free data (vmap0 and postal code polygons in Germany)
 * Mapbender brings in a hundred maintained OGC service URL
 * WMS service meta data (cap url) are added as records/features to both WFS and WMS services
 * Each WMS/WFS is a rectangle (corresponding bbox) to serve as source for discovery and harvesting (delivery for the Public Geospatial Data Committee
 * MapServer WMS getFeatureInfo request returns Capabilities URL and description (meta data)
 * GeoServer WFS getFeature request returns a GML with the bbox and meta data.
 * enhanced with a Wiki page adding some human readable discussion for each service.

OSGeo Member Location Service
Everybody who entered a coordinate to All Members could be added to the above WMS/WFS-T infrastructure. Members could locate each other, show their current position (Gary as a multipolygon), etc. using MapServer map and GeoServer WFS-T and editing with Mapbender and MapBuilder. Some privacy should be added for those who do not want to appear in the map by allowing each registered user to edit exactly their own position and their visibility. Only needs an LDAP a certificate and some glue.

Collaboration tools
(... Jo has developed some ideas about geolocating email traffic, contributions, automated news feed analysis, needs some more explanation)

This probably doesn't belong here to be honest but on a collaboration tools page - remind me to link something from the Infrastructure Working Group page

Security, Privacy, Geowiki, Certification
The Stack can be used to develop a comprehensive SSO solution (software & architecture) to address Security and Privacy issues from a Geowiki point of view using Certificates.