GeoServer Roadmap
Get a quote now!
Get a quote on road-map development and add your support to a road-map item.
GeoServer @ OpenGeo
Andrea is a core GeoServer and GeoTools committer, and a performance optimization expert. Andrea has ten years of programming and consulting experience, focusing on Java and geospatial.
Gabriel has worked on geospatial software since 1997, working on route finding, vehicle tracking, web mapping with ESRI and open source software, desktop editing with uDig, and more.
Chris is the President of OpenGeo, a GeoServer developer since 2002, and a long-time proponent of open geodata and open source. He manages our technology development, advises clients on strategic directions and regularly speaks at international conferences.
Justin is a core GeoServer and GeoTools committer. He is on the steering committee for each project and leads training sessions on GeoServer and the OpenGeo Stack.
David Winslow is Technical Lead of the GeoNode team. As a committer on GeoTools, GeoServer, and GeoExt, as well as a contributor to OpenLayers, his expertise covers the entire OpenGeo Stack. Before coming to OpenGeo, he worked on biological and ecological research projects using graphics hardware to accelerate analysis.
Roadmap Items
Integrated Web Processing Service (WPS)
Perhaps the only true feature that GeoServer lacks relative to traditional GIS servers like ArcGIS Server is the capability to do 'processing' - performing spatial operations and analysis to the geospatial data served by GeoServer. A WPS in GeoServer will be fully integrated to perform real operations at the level of the data, instead of relying on parsing GML or reading large raster files over the network like the standalone WPS implementations.
Currently the layers that GeoServer publishes are the same for all users. We'd like to introduce the concept of “workspaces”, a logical collection of layers, optionally with limited security permissions, accessible from a unique end point.
GeoServer always tries to stay up on the latest standards, but no one has yet funded WMS 1.3. Most of the needed infrastructure is already in place, as it was required for WFS 1.1. But the bindings need to be built and it must pass the CITE compliance tests.
REST configuration will allow AJAX and other clients to configure GeoServer without using the HTML user interface. This will provide the option of scripted configuration, automatic refresh, and other shortcuts useful for production deployments.
A new, cleaner user interface built on the Wicket web framework. The new interface will be “pluggable”, so plug-ins to GeoServer can define their own user interface and have it picked up by the core automatically.
Currently features are only accessible via the Web Feature Service (WFS) API. REST feature access will provide a ”resource oriented“ approach to accessing geographic collections. It will also use the existing AtomPub specification to provide for feature viewing and editing.