Difference between revisions of "Software Stack"

From OSGeo
Jump to navigation Jump to search
(comment added)
(then put it in :-))
Line 1: Line 1:
−
From Arnulf:
+
We move to install and maintain a stable version of a basic SDI stack consisting of:
−
 
+
* PostgreSQL as database
−
We suggest to install and maintain a
 
−
stable version of a basic stack. ('basic stack' refers to the below
 
−
software list that most of our client's sites run as productive
 
−
systems). The stack includes:
 
−
 
 
−
* PostgreSQl as database
 
 
* PostGIS as spatial extension
 
* PostGIS as spatial extension
−
* MapServer as WMS
+
* MapServer as WMS (and WFS)
−
* GeoServer as WFS-T
+
* GeoServer as WFS-T (and WMS)
 
* Mapbender and MapBuilder as WMS and WFS-T Client
 
* Mapbender and MapBuilder as WMS and WFS-T Client
 +
* GRASS GIS (via ssh?)
  
−
We have this package running on FreeBSD, Debian, Ubuntu, SuSE, Mandrake,
+
== Applications and Demos ==
−
Gentoo (and probably some others including good old windoze). You will
+
* MapServer automatically brings some HTML demos that just need to get set up
−
know which OS it should be.
+
* 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)
−
MapServer automatically brings some HTML demos that just need to get set
+
* Mapbender brings in a hundred maintained OGC service URL
−
up. GeoServer packages with MapBuilder, so we'd have that one too almost
+
* WMS service meta data (cap url) are added as records/features to both WFS and WMS services
−
automatically. They also provide for some demo data that could be moved
+
* Each WMS/WFS is a rectangle (corresponding bbox) to serve as source for discovery and harvesting (delivery for the [[Public Geospatial Data Committee]]
−
into the PostgreSQL database. We'd throw in some Open/Free data for
+
* MapServer WMS getFeatureInfo request returns Capabilities URL and description (meta data)
−
Germany (nothing special, just some very rough topography,
+
* GeoServer WFS getFeature request returns a GML with the bbox and meta data.
−
infrastructure, place names and postal code polygons). Mapbender brings
+
* enhanced with a Wiki page adding some human readable discussion for each service.
−
in a hundred OGC service URL that are operated all over the world. All
 
−
of these would be added as records/features to both WFS and WMS service
 
−
as rectangles (the corresponding bboxes) to serve as source for
 
−
discovery and harvesting (delivery for the [[Public Geospatial Data Committee]] ). A WMS getFeatureInfo request on MapServer would return the
 
−
respective Capabilities URL and a description, the coresponding
 
−
GeoServer WFS getFeature request additionally the bbox rectangle and
 
−
some meta data. This could be enhanced with a Wiki page adding some
 
−
human readable discussion for each service. We have started doing this
 
−
at the Mapbender Wiki but as it is a central thing we suggest to move
 
−
the efforts to the OSGeo right away.
 
−
 
 
−
One of the next services that we would suggest to get done is an OSGeo
 
−
member WMS and WFS-T. Everybody who entered a coordinate to:
 
−
[[All Members]]
 
−
could easily be transferred as a WKT point to the PostgreSQL/PostGIS
 
−
database and served as a map by MapServer and as WFS GML by GeoServer,
 
−
display and editing can be done with Mapbender and MapBuilder. Something
 
−
like that. All the projects have a user map (GRASS, Mapbender,
 
−
GeoServer, MapServer, etc.) and the OSGeo should also have one.
 
−
 
 
−
 
 
−
From Markus:
 
  
−
I would like to see a GIS here as well...
+
== 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.

Revision as of 14:55, 18 April 2006

We move to install and maintain a stable version of a basic SDI stack consisting of:

  • PostgreSQL as database
  • PostGIS as spatial extension
  • MapServer as WMS (and WFS)
  • GeoServer as WFS-T (and WMS)
  • Mapbender and MapBuilder as WMS and WFS-T Client
  • GRASS GIS (via ssh?)

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.

Retrieved from "http://wiki.osgeo.org/w/index.php?title=Software_Stack&oldid=3537"