GeoNode 5 Roadmap (and beyond)

[giohappy]

2025 will bring a new major version for GeoNode, an opportunity to refactor and bring new core features to this great platform, which is growing fast thanks to its community of contributors and customers.

We want to share the plans and ideas we're discussing along the road.
Of course, the list reported below is only a fraction of the many things we would like to do but, hey, step by step...

A list of activities are already on fire:

• 🔥 A brand new Metadata service (GNIP 97: New metadata editor #11511), based on JSON Schema, which includes a new highly customizable metadata model, a new metadata API, and a new editor that autoconfigured based on the API.
• 🔥 The upgrade to PyCSW3
• 🔥 Remove all the current legacy code and templates for metadata editing. The settings currently available inside the Metadata page are being moved to a new "Management" tab of a resource sidebar (you may have already spotted it in the development demo instance). The Attributes editor will use related functionality provided by the MapStore client
• 🔥 A new home page and client layout, that brings more options for customizing the catalog, and sub-catalogs. The re-design is done in collaboration with the MapStore team. You can take a look at what's cooking at New MapStore Home Page geosolutions-it/MapStore2#10631
• 🔥 A new Django Admin area, which will be renamed to "GeoNode Back office", based on unfold. The plan is to revamp the admin area and give it a central role also for non-admin users.
• 🔥 The upgrade to Geoserver 2.26.x
• ⏰ The removal of the deprecated monitoring module.
• ⏰ Removal of legacy project scripts and configurations (distribution packaging, playbooks, pavement, etc.)
• ⏰ Removal of setup.cfg and requirements.txt duplications, and review of pinned dependencies

On the side of deployment and security, we are ready to launch a new infrastructure for the demo instances, based on Kubernetes and GitHub deployment automation. This will allow us to experiment more with k8s deployments for GeoNode, its Helm charts and, last but not least, rootless deployments.

We also plan to work on the side of performances. Once most of the legacy code is dropped, we will have the opportunity to refactor and optimize areas that are currently tied to legacy architectures. These include optimizing the code and queries behind the principal REST API endpoints (resources and permissions), and the introduction of a new caching mechanism.

Many more things are under discussion, sorted by priority and feasibility (not importance!):

• Removal of all legacy Django templates and views for the client. One by one every frontend functionality that depends on legacy templates will either be moved to the client or the (new) Back office. This includes:
  • User profile (including notifications and user activity)
  • Groups management
  • Announcements (which are currently broken)
• For the reasons above, and lack of maintenance, the following functionalities are planned to be removed during the course of GeoNode 5 if nobody raises his hands against it:
  • Messages
  • Popular count
• We would like to resurrect Activity streams since they provide valuable insights on GeoNode usage and auditing.
• We hope we will have the opportunity to work on implementing analytics support inside the client. Tests done with bindings of the MapStore API to analytics clients for Matomo, Google Analytics, and Plausible look promising

These are not planned yet. We're open to contributions, ideas, and... sponsoring! 😊

Thanks to all the people and companies contributing to the project. We hope to extend the participation even more and this discussion goes in that direction.

[t-book]

Wow this is big thanks @giohappy !