OpenLayers is a javascript tiling web-based client just like Google maps. GeoServer has MapBuilder built in as its map preview tool. There are some others out there and you can refer to the GeoServer client page for more information.Ī javascript client that supports OGC WMS and WFS requests, so you can view and edit spatial data through the web browser. These are some of our favorite client applications. We hope to see the first release candidate in January. Hot on the heels of this release is GeoServer 1.5 with Web Coverage Service support. The more we can hit the server the easier it will be to find problems. So if you have a WMS up and running, feel free to point it at our layers and use our data. We have also worked on stability a fair amount and are currently testing version 1.4.0 on our demo server: Sigma. Of course there are many bug fixes and improvements in this release. That said, I will point you at the documentation that describes just how to write your own plug-in: It used to be a lot more difficult to add extensions, comparatively to what we have now, and this means that we can look forward to new and interesting additions from the many users out there. What we gain from this new framework is the ability to modularize GeoServer into separate components and allow for outside developers to create plug-ins easily. This is quite an exciting release for us because it is taking GeoServer in a new, more developer friendly, direction with the Spring framework it is built on. It’s finally here! Version 1.4.0 is out the door and kicking. Happy Holidays from all of us working on GeoServer! It’s going to be an exciting year for sure. So stay tuned, there’s lots of fun coming from the edges to the mainstream of GeoServer, and there are some other fun things that may be in the works. On the non-technical side of things we’re also going to be working on changing the license of the ‘core’ of GeoServer (configuration of data and access to GeoTools) to LGPL, which should enable others to build even more interesting services on top. Also Social Change Online and Axios are likely going to be doing some more work on bring the new Feature Model home, which should be a huge step forward. And 3d and 4d support in WCS will be in the works as the 2D version works towards the stability of 1.5.0. If people have suggestions of a good web framework let us know, the ones we’re likely going to look at are Wicket, WebWork2, and Google Web Toolkit.Įlsewhere on the horizon we’ve got WFS 1.1 (which includes GML 3.1.1 simple features) from OWS-4 coming home, and Justin’s made some nice improvements on that branch. The only thing we didn’t get to was an improved SLD editor, but I’m hoping we can do it after our web gui overhaul - which made it’s way up to ‘medium term’, as we’ve been feeling the pain too long. We’ve also had some work on tiling/caching with a tutorial on running OSCache. 1.4.0 is out, and the WCS branch not only got up a release, but is a part of the GeoServer main line as 1.5.0-beta1. The demo site is up, GeoCollaborator stuff has moved from discussions to the beginning of an implementation. The roadmap had fallen out of date - the ‘short term’ projects were set to complete in september - so I’ll try to be more vigilant about updating it more regularly.īut I must say it was quite satisfying doing the update, as the GeoServer community had actually managed to hit most of the things we said we would. If I’ve missed anything please don’t hesitate to update it (all our docs are wikis). So this may be about as close as I’m going to get to ‘ Developers notes’ for awhile (though I may let myself work on some GeoJSON or GeoRSS output over the holidays), but wanted to let everyone know that I updated the GeoServer Roadmap in an attempt to capture the latest directions of the community.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |