GeoServer Roadmap: REST Configuration API
Work has also been happening on a programmatic configuration API built on REST principles. RestConfig has been a community module for awhile, and should move in to extension status, with lots of feedback from users, for 1.7.3 release. This will enable nice scripting to automatically configure GeoServer programatically. The API will also form the basis of javascript configuration tools, and enable shortcuts like uploading Shapefiles and GeoTiffs.
Track progress on this roadmap item at this ticket.
Funding
This roadmap item is currently unfunded.
Add your support for this item by contacting us for a quote and discussion of the particular features you need.
Get a quote now!
Get a quote on road-map development and add your support to a road-map item.
Other Roadmap Items
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.
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.
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.