dblasby@anonymised.com wrote:
Well, it looks like Geoserver 1.3.0 ("the official release") is coming
out quite soon now. I've been very busy adding functionality,
ease-of-use, and stability. After all this hard work, what I'd like to
know is who is actually using Geoserver and what its being used for!
I'm busy working on my presentation for the OpenSource GeoSpatial
Conference (also known as MUM), and I'd like to mention a few projects.
I'd also like to know why you chose Geoserver over other products.
I'm actually quite interested in hearing about how the fruits of my (and
other's) labour are being used. Sometimes I feel it just gets sent out
to the ether and disappears.
So, if you're using Geoserver, please reply to this message and tell
myself and the rest of the people what you're using it for!
Thanks,
Dave
Hey,
we are using GeoServer in several projects. Seems like we are latecomers. We have comparably limited experience with GeoServer development issues as we are traditional MapServer users.
Here are two very different examples:
+++
We use GeoServer as WFS in the Ministry of Commerce of Rhineland Palatinate to return GML to the user. It is planned to extend the use as WFS-T to write back new digitized objects (currently Mapbender writes WKT directly to PostgreSQL/PostGIS).
The spatial data infrastructure contains one layer with 6.5 million land parcels, 750.000 farmland sections (wiht loads of alpha data) and 1.8 TB aerial photography which we render using UMN MapServer. It is not planned to drop MapServer and use GeoServer instead but to use both. MapServer for the high performance bulk stuff and GeoServer for the edit, query and sotrage stuff.
A partner company currently writes a tiny module which converts GML to Shapefiles so that people can query GeoServer not only for GML but can also obtain the data as Shape files to use in ArcPad when they are in the field. It will find its way back to GeoServer or geotools in time.
The Infastructure is currently open to 20.000 farmers who can digitize their land parcels to request for subventions granted by the European Union.
Find the demo site at
http://www.flo.rlp.de
It shows what the internal system does but uses much less data and a slightly different architecture than the productive system.
+++
We use GeoServer as WFS-T to provide a digitizing front end access for a registered association which helps to enhance safety for motorbikers. This is sort of a non-gov, no-money community project. The goal is to identify roads with safety fences in dangerous curves. The registered association then calcualtes the necessary funds to add underride protection and contacts and organizes sponsors. The system currently links into 11 different spatial data infrastructures for the backdrop data (all larger states in Germany).
GeoServers is used as WFS-T to store newly identified curves, which mostly are collected by the members by GPS or online digitizing in a map (thats a Mapbender there again). All new underride protection devices are also added to the map to show members where their fees are spent.
Very recently police departments and road maintenance staffs seems to be using this application to do whatever they might want to do. This is interesting insofar as only around 50 of the 2000 registered members actively use the Online system to add new data whereas last month we registered more then 1000 individuals from police departmente and maintenance staff using the maps. Seems like it fits better into their workflows than their own system...
+++
Not all is sunshine though, currently we are having a problem with the sheer size of the base geometry of 6.5 million polygons. UMN MapServer renders WMS fine and very fast. But both MapServer and GeoServer will not return a GML if it is requested with alpahnumerical attributing only. Both seem to be missing a bbox thus use the bbox of the Capabilities resulting in a full table scan, which simply flattens performance ot the database.
+++
People here regard GeoServer as a productive, stable Free Software (if you like it better: Open Source) environment which is one of the more efficient base components for operation in larger spatial data infrastructures.
The descision for GeoServer has been based on an evaluation on ease of use, installation and configuration, the vicinity to geotools, the large and friendly user community, helpful user lists and the Mapbuilder project that is tightly integrated and already provides some neat functionality we are still at implementing in Mapbender.
As with all Free projects it is still fairly difficult to get people to fund base development but it is getting better, last year we could fund a tiny development in UMN MapServer and the plan is to enhance funding management to be able to provide leverage more for development.
Thanks for all your good work and it definitely does not disappear in the ether - nonetheless roi is still not rolling very well. Maybe we could set up a profesional support and service agreement which reserves a share to be invested directly into base development like Refractions and Intevation do for PostGIS.
This would be something i'd like to discuss during and after our BOF meeting "How to be Managed by an Open Source Project" friday over lunch.
Best, Arnulf.