This page last changed on Sep 21, 2009 by jive.

This roadmap represents some of the ideas for the future of GeoServer we are excited about.

Please note this is not a plan fixed in stone. To be a responsible (and responsive) open source project we need to take into account feedback from you - the members of our community. For organizations working directly on GeoServer we also need to take into account feedback from our customers.

As such we have broken down the GeoServer roadmap into sections; short term project goals (for which we have funding and/or a volunteer mandate); medium term goals (which are planned and at least partially backed by funding; but have not yet established a delivery date) and finally long term ideas and opportunities which we need your help with.

Help Define the Roadmap

This road map is defined by consensus, and is adjusted to match available resources. If you want to see any of these move faster, then you can work with the community, and provide resources, and we will work with you to make it happen.

We have provided a contact person for each idea represented here; please feel free to get in touch and ask for opportunities to take part financially or as a volunteer.

Short Term Project Roadmap

These projects are currently funded, and being performed by core developers. You can expect to see them in the code base in the coming months. If you are working on something that should be added to GeoServer soon, let the list know, and we can schedule it in for release.

GeoServer 1.7.x Short Term Project Roadmap

Better docs

Yes, oh, yes. We are finally going to spend some time really improving the documentation, hopefully making some screen casts, and just making GeoServer more friendly and accessible, especially for new users.

This work is in progress; the user docs have mostly been ported; but work on developer docs is ongoing.

Contact: Mike Pumphrey, Justin Deoliveira

Javascript preview replacement

Now that we've got some OpenLayers developers closer to GeoServer we're working on using it to fully replace our map 'preview' stuff, with a real mapping application that can add multiple layers instead of just a bunch of links that one can click on. It should hopefully be the basis of more functionality exposed directly through the javascript map.

This work is ongoing - see the great progress being made on GeoExplorer.

Contact: David Winslow

KML 3D Support

GIS data is starting to move beyond a flat map - and GeoServer is being asked to support the publication of 3D data to formats such as KML for display in google earth.

This work looks to be completed (GEOS-2645) http://jira.codehaus.org/browse/GEOS-2645 and scheduled for the next release cycle.

contact: Andrea Aime

Hibernate based GeoServer configuration

At GeoSolutions we have decided to implement a new GeoServer internal configuration presistence mechanism that leverages on Hibernate as its persistence engine to not keep the whole configuration into memory and to not rely on XML files. Our goal is to be able to support at least Postgis, Oracle and H2 as the target database, but, as you know, many more are supported by Hibernate.

The range of features that this work would open up is pretty wide, just think about using Hibernate distributed caching, simplified GeoServer replication, etc., etc.. However the main objectives are more scalability and more robustness wen employing GeoServer in a dnymaic scenario, where new layers are added on the fly.

The work is in progress, we have started to describe the details on the GeoServer wiki and we will be committing a first version soon.

contact: Simone Giannecchini

GeoServer 2.0.x Short Term Project Roadmap

GeoServer 2.0 represents the last major step towards GeoServer's evolution to be a platform for web-based geospatial software; and features an all new configuration user interface!

New Web Interface (Core)

The main shift in 2.0 is to drop the old STRUTS-based web administration tool in favor of one built on Wicket. There is a working prototype available for download: GeoServer 2.0.0-alpha1. This needs to be refined and improved to be completely bug free and user friendly for 2.0. It should have a big advantage of being pluggable, so plug-ins to GeoServer can define their own user interface and have it picked up by the core. This makes non-core additions to GeoServer completely pluggable, so we can keep the core very tight.

contact: Andrea Aime, Justin Deoliveira

Application Schema Support (Core)

At long last, we'll have support for the full complexity of GML application schemas, with the ability to define feature types derived from different table structures. GeoTools received the improvements to support this awhile ago, and a GeoServer Improvement Proposal just recently brought those improvements to trunk. Next steps are to define new more complex outputs, and get the mapping and data outputs to reflect those. This work is primarily supported by AuScope.

contact: Ben Caradoc-Davies

Printing

See Printing in GeoServer

Contact: Alan Gerber

Proxy Module

See http://www.nabble.com/Proxy-Community-Module-td24058307.html

Contact: David Winslow, Alan Gerber

Hibernate based GeoServer configuration

At GeoSolutions we have decided to implement a new GeoServer internal configuration presistence mechanism that leverages on Hibernate as its persistence engine to not keep the whole configuration into memory and to not rely on XML files. Our goal is to be able to support at least Postgis, Oracle and H2 as the target database, but, as you know, many more are supported by Hibernate.

The range of features that this work would open up is pretty wide, just think about using Hibernate distributed caching, simplified GeoServer replication, etc., etc.. However the main objectives are more scalability and more robustness wen employing GeoServer in a dnymaic scenario, where new layers are added on the fly.

The work is in progress, we have started to describe the details on the GeoServer wiki and we will be committing a first version soon.

contact: Simone Giannecchini

Medium Term Project (2.1.x)

These projects have funding or commitments from developers, but are larger projects that will take more time.

Style Layer Descriptor Styler (New Module)

The definition of styles with GeoServer is handled by the OGC Style Layer Descriptor specification - and is currently presented as a raw XML document. There has some good progress towards defining a user friendly Style Editor (see http://projects.opengeo.org/styler) which we would like to see included in GeoServer.

Contact: [~tim schuab]

3-D, 4-D, n-D Coverage Support (Core)

The main thrust of the Geo-Solutions team has always been to exploit the more advanced capabilities of the WCS, particularly it's ability to return certain bands and dimensions for further analysis, instead of returning just the 2d image. Very few WCS's have this capability, and no open source implementations do (afawk), so it should be a huge step forward. They are currenlty working away in GeoTools land, see: [GEOTOOLS:Multidimensional Georegistered Grid]. Indeed 95% of this work will take place in GeoTools, since it will still just use the WCS interface in GeoServer.

Contact: Simone Giannecchini

Resource vs Service split (Core)

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, perhaps with limited security permissions, accessible from its own end point. Most web servers offer this in some form, so we should as well. Will involve some improvements to the catalog, to handle different views on the core configured resources, plus a web interface and a rest interface. GeoServer Resources has some ideas on how to lay these out.

Contact: Justin Deoliveira

Processing WPS or RESTful (New Module)

One of the things GIS types like is to do all kinds of analysis and spatial operations. There is now a framework for 'operations' that lives in GeoTools and is used in uDig as well. There has been work done to integrate SEXTANTE with its 220+ algorithms to work in GeoTools. In GeoServer there are now bindings, but more work remains to get it to production quality, and to add REST bindings. 4. WPS \- Web Processing Service has information on what's been done thus far. The motivation behind doing WPS as a direct plug-in to GeoServer is to allow it to avoid the performance bottleneck that plagues most existing WPS's - the production and parsing of GML and large image files.

Contact: Andrea Aime, [~jgarnett]

AtomPub / REST feature access implementation (New Module)

This should provide an interface for viewing and editing features that is much easier for programmers to work with than WFS-T. We're hoping to follow the lead of FeatureServer, and now MapGuide, as they've done some great restful work that we can borrow, and it'd be great to have compatible implementations. We eventually hope to get to even versioned editing through a REST interface.

Ingestion Engine (New Module)

While the REST configuration API should help, one step further in automatic configuration of GeoServer is an 'Ingestion Engine', that automatically picks up new files that appear on disk, making those available online. This should be able to not just publish new data, but also perform complex workflows, rectifying, mosiacing, color correction, etc. GeoSolutions has been working on this, and should release an open source version soon, that will likely live as its own project and as a plugin, like GeoWebCache.

User Collaboration Features (New Module)

Right now there is little focus on 'users' of GeoServer. We should give them nice home pages, where they can create maps and upload information they want to be visualized. A number of user centered features should encourage more collaboration, making GeoServer a platform for the sharing and editing of geospatial information.

WMS 1.3 (Standards Implementation)

This is required for INSPIRE, and we imagine that someone will fund GeoServer to upgrade to it soon.

WFS 2.0 (Standards Implementation)

This is also required for INSPIRE. There are not yet CITE tests for it, so this will need to wait for those.

WPS 1.0

See the 'New Modules' section above, we should hopefully do both OGC WPS 1.0 and RESTful access to the same.

CS-W 2.0 integration (Standards Implementation)

It is still very much on our radar to tell the Catalog story better with GeoServer, enabling some sort of integration with a CS-W implementation, as there is lots of potential sharing.

Longer Term Project/Dreams

These are projects that are not currently funded, but that we as a community have thought about and many people have said they'd very much like to see. Feel free to add anything that you'd like to see.

H2 datastore


Contact: Justin Deoliveira

Currently one can work with shapefiles directly, but they weren't really built for lots of transactions. It'd be much more secure to have a real java database embedded in GeoServer. With this in place one could upload a shapefile, but it would be stored in the database, and could then be exported out as a shapefile as well. H2 looks like the current best starting point, as it has full ACID compliance, and performs much more quickly than Derby, the old front runner. |

Oracle Workspace Manager and ArcSDE versioning backend for WFS-V


Contact: Andrea Aime

Right now the versioning WFS extensions we support only work against PostGIS. We should be able to integrate with the existing versioning managers - ArcSDE and Oracle Workspace Manager.

Configure on arcgis/udig/gvsig and export to GeoServer


Contact: Jody Garnett

It would be great if we could allow users to easily convert existing projects to GeoServer, to have an 'export to GeoServer' button in leading open source and proprietary software. The biggest win is probably conversion to SLD. This is trivial with uDig, since it uses SLD natively. Not sure what's needed for gvsig, I think they are working on SLD export. For esri stuff I found some deegree code that converst from AVL to SLD, which is java so we could maybe just use. Then there is arcmap2sld, which looks like it works pretty well. At the very least we should include it in some SLD tutorials. Eventually it'd be great to work on a tool that directly exports a map from the esri desktop to GeoServer.

SVG Output Improvements

Soon most browsers will natively support SVG display. This opens up a wide range of opportunities if geoserver can generate "nice" SVG output. The current SVG support is either streaming with no advanced styling and quite fast, or quite slow, but with full use of SLD. We'd like to get a fast and style conscious SVG renderer.

Contact: Andrea Aime

Open Source ArcSDE

Enough pieces are falling in to place to make it so GeoServer could serve as an open source equivalent to ArcSDE, an extremely powerful piece of GeoSpatial Middleware, spatially enabling databases, managing users and their editing capabilities, doing caching, and linking different datasources. See Open Source ArcSDE for some more ideas.

Contact: [~gabriel]

Tile Processing on EC2/S3

Would be cool if we had a really easy way to defer all tile processing to amazon's ec2, that could fire up a bunch of instances at once and process the tiles incredibly quickly.

Contact: Justin Deoliveira

Platform for a Public Commons of Geographic Data

See: Platform for a Public Commons of Geographic Data

We hope to present a decentralized plan of action, that a variety of community members can take up. This focuses on the broader strokes, but there are many, many small opportunities within it all. Helping with debugging and individual features within the bigger projects, or working on different aspects to make GeoServer even stronger. We just want to have this up to show that there are ways to really get invovled, and to show that when it all comes together we will have something incredible. You can also view a more detailed roadmap on our jira task tracker , and we will try to integrate this document and the individual tasks in the future. Please put up comments and feedback on the roadmap, the direction is shaped by you!

Validation for WFS-T

GeoServer 1.2.x series had support for a validation module (allowing integrity tests to be performed on as data is modified). Restoring this work and providing a nice user interface would be a useful addition to GeoServer 2.0.

Contact: Jody Garnett

h3 Curve Support

PostGIS has been starting to chew down the ISO SQL MultiMedia extension (which is the next logical step after the current OGC Simple Features for SQL implemention). One of the major points things brings to the table is Geometry support for Curve data structures (with both a well known text and well known binary representation). If this is the kind of work that is of interest to you please contact us.

Contact: [~melslie]

ISO 19107 Geometry for 3D

We have had support for 3D Geometry (based around ISO19107) in our planning process for quite some time - and have a couple of Geometry implementations that can be hooked up and evaluated. Recently we have an oppertunity to collaborate with the deegree project on this one which is quite exciting. Anyone want to fund this work?

Contact: {~bencaradocdavies], Andrea Aime, Jody Garnett

GeoCollaborator

GeoServer Modularization

toward a pluggable web GIS framework

SLD Editor

Tiling


h2.png (image/png)
wfs-v.png (image/png)
export.png (image/png)
Document generated by Confluence on May 14, 2014 23:00