After over two months of bugfixes and user interface tweaks, the GeoNode team is proud to present the second release candidate for GeoNode 1.0. This release improves on the user management, data upload, metadata management, GeoNetwork-powered data search, and an integrated styling and map composing tools from 1.0-beta with many bugfixes and user interface improvements.
Notable changes since RC1 include:
Correcting a critical issue affecting GeoNetwork, search results, and layer detail pages. Systems affected by this issue have invalid metadata in the Django database, so administrators upgrading pre-existing deployments should use the "django-admin.py updatelayers" tool to automatically correct the erroneous records.
Correcting an issue with default styles for raster layers, which prevented multi-band raster data from being rendered in GeoNode maps
You can see the full list of changes on the GeoNode Github project, or the list of closed tickets for 1.0 on the GeoNode issue tracker.
Site administrators should note that with this release, GeoNode has adopted the local_settings.py convention for separating defaults from site-specific settings. Other than this, the 1.0-RC1 release is a drop-in replacement for 1.0-beta.
As usual, the demo site at http://demo.geonode.org/ is updated with the latest release, and the release bundle for deployment is available for download. We welcome bug reports and feature requests at http://projects.opengeo.org/CAPRA/, and any questions are welcome at the project mailing list (geonode@librelist.com).
Posted at - Oct. 25, 2010, 10 a.m.