Releases: GeoNode/geonode
4.4.1
Changelog
4.4.1 (2024-11-06)
Improvements:
- [#1879] Include fullscreen button in embed pages
Fixes
- [#12639] User defined permissions will break the permissions exposed by the API
- [#12651] Map extent calculation throws exception for empty maps
Upgrades
- Updated MapStore to commit 092ecdfafb (branch
2024.02.xx)that includes fixes to the handling of GetFeatureInfo results popup for Geostories
4.4.0
Changelog
4.4.0 (2024-10-09)
New features and improvements
-
3D Tiles: This release extends the work started with GeoNode 4.3.0, where 3D visualization was introduced. Now 3D Tiles resources are first-citizen resources in GeoNode. 3D Tiles assets can be uplaoded from the Dataset upload area. The asset must be uploaded as a .zip file containing an index file named
tileset.json. This file will be parsed by the GeoNode backend to validate and extract metadata and spatial information about the 3D Tiles asset.
3D Tiles resources can also be created from remote URLs. A new option inside the Dataset upload panel gives the option to insert the URL to the index file of an online 3D Tiles resource. The same as for local uploads, the index file will be parsed to obtain the minimal information to setup the GeoNode remote resources.
A new filter has been added for filtering 3D Tiles resources. -
Assets: With this version a new concept has landed into GeoNode, the Assets. This model has been introduced to extend and improve the relationship between resources and any file that exists behind them. These files was kind of hidden behind the scenes, and weren't exposed to the internal GeoNode APIs. Assets introduce a model that makes the management of fiels explicit and decoupled from resources. For the moment this isn't visible to end users, but in the future there are plans to implement an asset manager area, where files can be uploaded and managed independently from catalog resources. Eventually a resoruce can be created from an existing asset at a later stage. This is what GeoNode does now: when a new resource is uploaded, GeoNode creates an asset for the file(s) and then creates a resource connect to the asset(s) through Links.
Assets were also implemented to introduce the option to attach multiple files to a single resource. This is already doable by manually creating an asset and then connecting it to a resource through a link, but this is only doable from the Django admin interface, which is restricted to GeoNode administrators.
Notice that the uploaded files now are stored at the path configured by the newASSETS_FOLDERsettings. -
Map Extent: Map extents calculation has been fixed, finally! When a new map is created or updated the extent of the map is recalculated from the extent of its layers, taking into account the CRSs of the layers.
-
API: The is_published and is_approved attributes are writable now. They can be set inside PATCH requests, and the API will check the required authorizations for their modification (including the specific rules enforces by the advanced workflow mechanism).
Software upgrades:
- Django 4.2.9
- Geoserver 2.24.4
- MapStore 2024.02.00
- PostgreSQL >=12
Important note for the upgrade
GNIP 100: Assets introduces changes to the location where uploaded files are stored. A manual command must be executed to migrate pre-existing files to the new location and ensure that all GeoNode functionality will work correctly.
The full list of changes:
4.3.1
Changelog
4.3.1 (2024-07-19)
- Upgrade to Geoserver 2.24.4. The new version of Geoserver includes the fix for CVE-2024-36401
- 5ac3601: Fixed OSM tiles loading inside 3D views
- 8a2eaa5: Fixed autocomplete for the Group filter
- 750457b: A new regenerate_xml management command is available to regenerate the XML metadata files in batch
- 5ebe7fc: The restore of GWC tile layers during the Backup and Restore procedure has been moved to the
restore.shscript file. This grants that tile layer are recreated only after the catalogue resources have been completely restored - 7197e76: Fixed that layout of the
re-captchafield inside theSignUpandLogInpages - GeoNode/geonode-mapstore-client@676241e: A new "All Resource" button has been to added to viewers to let users navigate back to the full catalogue
- GeoNode/geonode-mapstore-client@8cdee07: Fixes a regression that removed the GeoNode catalogue from Dashboards and Geostories
The full list of changes here
4.3.0
Changelog
4.3.0 (2024-05-30)
New features and improvements
- 3D and MapSore catalog plugins available for maps: This release includes a major upgrade of the MapStore framework upon which the GeoNode client is built. One of the key benefits brought by the alignment to the latest MapStore versions, is the integration of new plugins powered by MapStore. Two of these plugins have been enabled by default for maps: 3D view, powered by Cesium and the Catalog tool which gives users the option to include external layers (from WMS, TMS, CSW, etc. services) directly into a map. The 3D view is the first step toward the publishing of 3D content with GeoNode. Meanwhile external 3D Tiles sources can already be viewed inside a GeoNode map thanks to the Catalog service for 3D Tiles.
- Map Viewers: Thanks again to the work done to extend the integration with MapStore, its concept of Application Contexts have been adapted and integrated in GeoNode under the the name "Map Viewers". With a Map Viewer the list of tools and plugins available in a map can be configured. Map Viewers can be created from a map (the feature is available under the Edit menu) and they can be used by multiple maps. With Map Viewers all the plugins offered by MapStore can be used inside GeoNode maps.
- Hiding resources from catalog listing: There are cases where a resource is created only to be used within other resources. Images uploaded to be included in a geostory, datasets only meant to be viewed inside maps, are examples. Sometimes we don't want these resoruces to be visibile inside the catalog list, or inside search results. For these cases a new "Advertized" attribute is available under the Settings tab of the Metadata editor. When this flag is turned off the resource will only be listed to its owner. This doesn't affect the permissions on the resource. Users with view permissions can still visualize the resource, but it won't be listed in the catalog to them.
- Extended Users API: The User API has been extended to support the full management of GeoNode accounts. This API makes GeoNode compliant with the Data policies that request to give users the option to delete their account and their data from apps. The new APIs also support the transfer of resource ownership to another user and the ability to step down from the Group Manager role for a user.
- Groups facet: A new facet (filter) has been added to the filters panel for filtering resources by Group.
Other minor improvements and fixes
- Backup/Restore: Several improvements that make the B/R service more robust and performant. Code customizations (layouts, etc.) are excluded now from projects backups.
- Owner was update when geoapp were saved: This fixes a problem with geoapps (geostories and dashboards) where the current user was assigned as owner when the resource was saved.
- Fixed textara for rich HTML metadata fields: It wasn't editable due to a regression introduced in previous versions.
- Metadata and SLD file uploads: Fixed a problem with the legacy code that prevented the upload of XML and SLD metadata files for an existing resource.
!! IMPORTANT !! Breaking change
The minimum supported version for PostgreSQL is 12. If you have a previous version installed you will need to perform a backup and restore procedure od the DB.
Software upgrades:
- Django 4.2.9
- Geoserver 2.24.3
- MapStore 2024.01.00
- PostgreSQL >=12
The full list of changes here
4.2.5
What's Changed
- Bump 4.2.x to dev by @giohappy in #12212
- [Backport 4.2.x] [Fixes #12237] Extend tests for permissions assignment by @github-actions in #12264
- [Backport 4.2.x] [Fixes #12261] Current user is assigned as owner on geoapp update by @github-actions in #12265
- Release 4.2.5 by @giohappy in #12289
Full Changelog: 4.2.4...4.2.5
