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:

• stop GeoServer

• download this patch jar and save it under geoserver/WEB-INF/lib

• restart GeoServer

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.

Last week AuScope hosted a GeoServer app-schema meeting in Perth, Western Australia, to bring together developers, information modellers, and users:

https://twiki.auscope.org/twiki/bin/view/Grid/AuScopeSissGeoserverMeeting2009

The meeting was attended by Jody Garnett, GeoServer developers Justin Deoliveira and Gabriel Roldán from OpenGeo, AuScope Spatial Information Services Stack developers, GeoSciML gurus, and AuScope participants including GeoScience Victoria, Geoscience Australia, and Landgate. Discussions included the history of GeoServer app-schema, background on AuScope, user perspectives, and future development priorities.

Future development options that received support included:

• Graphical configuration for app-schema (Wicket UI)

• Support for polymorphism in encoded app-schema XML

• 3D geometry support

• GML 3.2

• WFS 2.0

and more. See the minutes for details:

https://twiki.auscope.org/twiki/bin/view/Grid/AppSchemaMeetingMinutes

The developers stayed on for a code sprint and:

• Implemented vocabulary operations in CQL

• Got GeoServer app-schema working with an ArcSDE backend

• Got GeoServer WMS working with a simple feature WFS backend

• Demonstrated encoding failure of ISO 19107 geometries (3D support)

• Debated polymorphism implementation approaches

• Wrapped Justin in org.geotools.xml.Encoder

  • http://svn.osgeo.org/geotools/trunk/modules/extension/xsd/xsd-core/src/main/java/org/geotools/xml/Encoder.java

  • To be fair, Justin is only the most recent maintainer

  • The source is 3.5 metres long when printed in 6 point DejaVu Sans Mono

  • One method alone is 1.2 metres long

AuScope thanks all the participants, especially Jody who helped organise the meeting, and the international visitors Justin and Gabriel who travelled from North and South America respectively. We hope you enjoyed it as much as we did.

Remember the good ol’ days, when the only maps you had were pieces of paper?  The past is now!

Hi, I’m Alan, and I’m interning with OpenGeo this summer.  My first order of business has been plugging MapFish’s printing capability into GeoServer as a community module; right now we’re releasing a developer preview. The module exposes an HTTP interface that allows the user to ask the server to compose an attractive map in PDF format.  MapFish also provides a JavaScript library that allows easy printing from a OpenLayers map.

Up for trying it out? You’ll need to download a nightly build of trunk and add a few files to it. I have written up step-by-step instructions for anyone interested. If you have any feedback, please chime in on the GeoServer developers mailing list.

**EDIT: **The print module instructions have been updated for GeoServer .2.0.x.  Please refer to http://docs.geoserver.org/stable/en/user/community/printing/ instead of the old wiki page.

Update: As of GeoServer 2.0.1, the legacy installer has been merged into the new installer. This means that during installation, you now have a choice on whether to install GeoServer as a Windows service or to run it manually.

GeoServer has provided a Windows installer for the past 4 years (since at least version 1.2.4, if not before). It has always been simple and functional, providing a modest wrapper for the Jetty container found in the binary distribution.

However, there are a number of ways in which GeoServer works in this environment that could be more in the spirit of Windows. So, with the release of GeoServer 1.7.5, we have redesigned the way GeoServer integrates with Windows, in the form of a new installer.

This new installer offers a host of new user-friendly features. First of all, GeoServer now shows up as a Windows service, in line with other server software such as Apache HTTP Server or PostgreSQL . This alleviates the need to have a command line window persist on the desktop when running GeoServer. Integration with Windows Services allows administrators the ability to automate the management of GeoServer, although starting and stopping GeoServer is also still possible from the Start Menu as before.

GeoServer now appears on the Add/Remove Programs list. It was always possible to uninstall via the Start Menu, but the uninstall option is now in a place where more users will expect it to be.

The installer itself has been redesigned as well. It now allows you to link to an existing data directory (if you have previously created one). Also, it allows (and encourages) you to change the username and password for the web administration interface, a feature unique to this installer. (In all other cases, it is necessary to edit the users.properties file.)

There are other some other user-friendly features added, such as the requirement (and check) for administrator rights to run the installer, to prevent errors during the install process.

Since this installer is very new and has not been tested on all platforms, we have included a link to the legacy installer that functions just like previous versions. But we encourage everyone to try out the new installer (and provide feedback on what works and what doesn’t) so that we can make the experience better. All in all, we feel that this is a marked improvement in the GeoServer Windows experience. Enjoy.