More information and instructions are available on the wiki. You’ll need either a Nightly build, or the latest GeoServer beta in order to use this proxy. This proxy is newly in development, so be sure to provide feedback to the GeoServer mailing list with your experiences.
The presentations for FOSS4G 2009 were announced this week. Looking at the presentations and workshops, one thing is obvious: GeoServer will be all over the place this year! Here’s a quick rundown of the currently scheduled events that mention GeoServer, either partially or primarily.
Whether you’re attending for GeoServer, for a greater understanding of all things FOSS4G, or just for the location, it looks like it’s going to be another fabulous conference. Early bird registration ends on August 7th, so if you haven’t registered yet, what are you waiting for?
The GeoServer community is happy to announce the second beta release of GeoServer 2.0, available for download. The developers have been working hard to get the new user interface up to the quality and functionality of the existing interface. This release of 2.0-beta2 brings us 74 issues closer to that goal.
The most noteworthy feature for 2.0-beta2 is the official inclusion of the app-schema extension. Most people probably know app-schema better as complex features, a feature GeoServer has been striving toward for the past three years. The extension gives GeoServer WFS the ability to support complex feature application schemas such as GeoSciML. Much thanks goes out to Ben Caradoc-Davies, Rini Angreani, and the rest of the AuScope* team for seeing this work through and actually making complex feature support a reality in GeoServer.
For those who missed the previous post about it, Ben and the folks from AuScope recently hosted a complex feature workshop in Perth, Australia, in which a number of the GeoServer developers were brought out. Special thanks for AuScope for hosting the event, which was a great success.
A special thanks also goes out to users who have been downloading the 2.0 alpha and beta releases, trying them out and reporting bugs. The more bug reports we get the faster we can get to the official 2.0 release. This should be the final beta release of 2.0 before it moves into release candidate phase, so stay tuned for RC1 coming soon.
- AuScope Ltd is funded under the National Collaborative Research Infrastructure Strategy (NCRIS), an Australian Commonwealth Government Programme.
This week the G8 will take place in L’Aquila, Italy, meanwhile a wide number of organizations are working hard to deliver services, data and information for a correct development of the G8 activities.
Thanks to the contribution of the geoSDI research group belonging to the CNR IMAA Research Center and in collaboration with GeoSolutions, all these organizations are using open source technologies (see here) via the geoSDI stack to provide geospatial services (you can find a few screenshots of the portal on the GeoSolutions blog). Please, note that GeoServer is playing a central role in delivering data via OGC W*S services (see ****here**).**
The GeoSolutions team would like to thank the geoSDI team, in particular Dr. Dimitri Dello Buono, geoSDI project head, Dr. Francesco Izzi, geoSDI technical lead and Dr. Giuseppe La Scaleia, geoSDI technical coordinator, for their effort in bringing the geoSDI concept into reality.
Looking forward to other challenging scenarios.
The latest stable GeoServer version, 1.7.5, was released with a small but critical bug that slows down rendering when a very small polygon or a line is displayed at a high zoom level (so that the displayed area is a very small fraction of the whole). The slowdown increases as one zooms in, and eventually may lead the Java Virtual Machine to crash. The bug also makes for non optimal rendering of cased roads (the typical highway display).
The issue is actually due to a Sun Java bug, but happily we have a workaround for it. If you find you’re affected by this problem, follow these simple instructions:
download this patch jar and save it under geoserver/WEB-INF/lib
Voilà, bug gone.
We want to thank Stefan Ziegler for the quick bug report and the other users that reminded us of how important this patch is.