Skip to content

4.4.0
Compare
Choose a tag to compare
@giohappy giohappy released this 09 Oct 15:39
· 23 commits to master since this release
4.4.0
bf532d2

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 new ASSETS_FOLDER settings.

  • 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:

Assets 2
Loading