4.0.2 (2022-12-20)
- Based on MapStore client 4.0.5
- MapStore client is no more compatible with 3.x train
- GeoNode 4.0.0 architecture is slightly different from the previous versions; please refer to:
-
Python upgrade 3.9/3.10/3.11
-
Django upgrade 3.2.16
-
GeoServer upgrade 2.20.5
-
GDAL 3.3.2/3.4.1
-
Highlights GeoNode 4.0.2:
https://github.com/GeoNode/geonode/compare/4.0.1...4.0.2
4.0.1 (2022-09-14)
4.0.0post1 (2022-08-22)
4.0.0 (2022-08-05)
- Based on MapStore client 4.0.3
- MapStore client is no more compatible with 3.x train
- GeoNode 4.0.0 architecture is slightly different from the previous versions; please refer to:
-
Python upgrade 3.8/3.9/3.10
-
Django upgrade 3.2.15
-
GeoServer upgrade 2.20.5
-
GDAL 3.3.2
-
Highlights GeoNode 4.0.0:
https://github.com/GeoNode/geonode/compare/3.3.1...4.0.0
4.0.0rc1 (2022-07-01)
- Based on MapStore client 4.0.2
- MapStore client is no more compatible with 3.x train
- GeoNode 4.0.0rc1 architecture is slightly different from the previous versions; please refer to:
-
Python upgrade 3.8/3.9/3.10
-
Django upgrade 3.2.13
-
GeoServer upgrade 2.19.6
-
GDAL 3.3.2
-
Highlights GeoNode 4.0.0:
https://github.com/GeoNode/geonode/compare/3.3.1...4.0.0rc1
4.0.0rc0 (2022-04-20)
- Based on MapStore client 4.0.0
- MapStore client is no more compatible with 3.x train
- GeoNode 4.0.0rc0 architecture is slightly different from the previous versions; please refer to:
-
Python upgrade 3.8/3.9/3.10
-
Django upgrade 3.2.13
-
GeoServer upgrade 2.19.6
-
GDAL 3.3.2
-
Highlights GeoNode 4.0.0:
https://github.com/GeoNode/geonode/compare/3.3.1...4.0.0rc0
3.2.1 (2021-07-16)
- Based on MapStore client 3.2.1
- MapStore client is no more compatible with 3.0.x train
- GNIP 88: Upgrade from Django 2.2 to 3.2
- Not compatible anymore with Django 2.2.*
-
Python upgrade 3.7+
-
Django upgrade 2.2.20+
-
GeoServer upgrade 2.18.3
-
Highlights GeoNode 3.2:
https://github.com/GeoNode/geonode/compare/3.2.0...3.2.1
3.2.0 (2021-04-29)
- Bump to postgresql-13; do not upgrade the docker image or be prepared to do a dump/restore of the DB
- Based on MapStore client 2.1.3
- MapStore client is no more compatible with 3.0.x train
- ResourceBase Model
BBOXnow is a geometry; that is no more compatible with the 3.1.x one - GNIP-81: GeoNode Core Cleanup:
- Removed GeoNetwork support
- Removed QGIS-Server support
- Removed SPC GeoNode support
- Advanced Resources Publishing Logic has been revised (see below)
-
Python upgrade 3.7+
-
Django upgrade 2.2.16+
-
GeoServer upgrade 2.18.2
-
MapStore2 Client Updates:
- Save Search Services to the Map
- Save Map Preferences into the adapter model
- Advanced Style Editor with graphical UI
- Improved Map Save Widget, specific for GeoNode
- New MapStore client configuration subsystem
- Group Layer as named groups
-
Upgraded
Dokerfileanddocker-composeto version 3.4 -
Migration of CI from Travis to CircleCI
-
General Code Quality and Performance Improvements
-
Highlights GeoNode 3.2:
- GNIP-76: Add RTL Support
- GNIP-77: GetFeatureInfo Templating For GeoNode
- GNIP-78: GeoNode generic "Apps" model to include pluggable entities into the framework
- Added MapStore GeoStories as part of the GeoNode MapStore client
- GNIP-79: GeoNode REST APIs (v2)
- GNIP-82: Thesauri improvements
- GNIP-83: ResourceBase for metadata-only resources
- GNIP-84: Upload Page Enhancements
- Improved Async Upload of Layers
- GeoServer Importer Uploads are now stateful and can be resumed or canceled
- GNIP-85: Map legend
- GNIP 86: metadata parsing and storing
- GNIP-87: Reduce information returned to users to only what is strictly required and accessible
- Append data to an existing layer
- Improved Metadata Editors, now able to handle HTML tags
- Improved Catalog and Thesauri
- Improved Thumbnails creation logic which is now relies on GetMap instead of outdated GeoServer Print Plugin
- Possibility to Upload RDF thesaurus via web
- Pluggable CSW prefiltering from external apps
- New Contrib module: GeoNode Keycloak Support
- Delete existing table on restore command feature (general improvements to Backup/Restore machinery)
- Advanced Upload Workflow Improvements:
- Non admin user cannot change permission
- Disable edit permissions globally when read-only mode is active
- RESOURCE_PUBLISHING:
- "unpublished" won't be visible to Anonymous users
- "unpublished" will be visible to registered users IF they have view permissions
- "unpublished" will be always visible to the owner and Group Managers By default the uploaded resources will be "unpublished". The owner will be able to change them to "published" UNLESS the ADMIN_MODERATE_UPLOADS is activated. If the owner assigns unpublished resources to a Group, both from Metadata and Permissions, in any case the Group "Managers" will be able to edit the Resource.
- ADMIN_MODERATE_UPLOADS:
- The owner won't be able to change to neither "approved" nor "published" state (unless he is a superuser)
- If the Resource belongs to a Group somehow, the Managers will be able to change the state to "approved" but NOT to "published". Only a superuser can publish a resource.
- Superusers can do anything.
- GROUP_PRIVATE_RESOURCES: The "unapproved" and "unpublished" Resources will be accessible ONLY by owners, superusers and members of the belonging groups.
- GROUP_MANDATORY_RESOURCES: Editor will be FORCED to select a Group when editing the resource metadata.
-
Documentation Updates:
- GetFeatureInfo Templating For GeoNode
- HowTo: Geonode with QGIS
- Improve GeoNode OpenID SP Protocol in order to be able to provide access to external clients
- Document the use of slide show in themes
- Update Advanced Installation steps to work against Ubuntu 20.04LTS
- Update Advanced Installation steps to work against RHEL 7.x
- How to setup rabbitmq, supervisor and memcached in order to fully enable async workers
- How to Upgrade from 2.10.x / 3.0
- Docs to connect production docker to external postgreSQL db server
- Documentation for new metadata settings
- Refers #6925: add documentation for thesaurus configuration
- Refers #6952: add documentation for uuidhandler
- Adding new settings in order to let the optional metadata in metadata wizard to become required
- Remove outdated/misleading SPC GeoNode documentation
- Relates to #7089 Delete existing table on restore
- Allow XSL customization
- Relates to #7150 Doc for upload thesaurus from admin interface
- Relates to #7194 Append data to layer
- Refers to #7214 Sorting Thesauri
- Relates to #6995 Documentation for ADVANCED_EDIT_EXCLUDE_FIELD
-
Improving GeoNode Theme Library: introducing Jumbotron Slides
-
Implementation of an action to assign bulk permissions on layer to users selected from People and/or Group Django admin forms enhancement #6582
-
Review of the current advanced resource workflow implementation enhancement security #6551
-
File system operations do not adhere to Django file storage API enhancement in progress #6414
-
Nav Toolbar gets distorted when multiple navbar items are added by the admin enhancement frontend major #6412
-
Allow only admins to edit/create keywords enhancement regression #6360
-
In home page show only ISO categories currently assigned to some dataset enhancement frontend #6332
-
Modify the admin theme customisation feature to allow for the use of a slide show in the home page enhancement feature frontend #6301
-
Improve GeoNode OpenID SP Protocol in order to be able to provide access to external clients enhancement security #6273
-
Limit "maps using this layer" to maps the user has permission to see enhancement security #6261
-
Prevent integrity errors on singleton model save enhancement #6223
https://github.com/GeoNode/geonode/compare/3.1...3.2.0
3.1 (2020-11-30)
https://github.com/GeoNode/geonode/compare/3.0...3.1