In this free webinar, our GeoNode lead Giovanni Allegri will cover the status of GeoNode with particular focus on the new version 4.4 as well as on what to expect next.
management and publication of geospatial data. It brings together mature open-source software projects under an easy to use interface. With GeoNode, non-specialized users can share data and create interactive maps.
thematic maps , dashboards and geostories • Manage granular security, permissions and sharing for users and groups • User with appropriate permissions can edit layer metadata, which are exposed by OGC CSW and REST, to provide search/discovery capability • Users with appropriate permissions can edit layer styles and data (for vector layers) • GeoNode exposes a number of standards for each layer: OGC (WMS, WMS-C, WFS, WFS-T, WCS, CSW) and mass market search standards (OAI-PMH, SRU, OpenSearch) • Full control through a RESTful API
hosted on GitHub under the GeoNode organization • The GeoNode Project Steering Committee (PSC) governs the GeoNode project. • Users and developers mailing list, and a Gitter chat are the main communication channels for the community. https://github.com/GeoNode
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.
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.
GeoSolutions is developing a pipeline for a streamlined processing of 3D data sources (point cloud, Lidar, etc.) to produce 3D Tiles assets ready to be loaded and visualized with MapStore and GeoNode Digital Twin Toolbox https://github.com/geosolutions-it/digital-twin-toolbox
new concept has landed into GeoNode: 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.
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. Eventually a resource can be created from an existing asset at a later stage. • 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 can only be done from the Django admin interface, which is restricted to GeoNode administrators.
introduces changes to the location where uploaded files are stored. A manual command is required to be executed to migrate pre-existing files to the new location and ensure that all GeoNode functionality will work correctly.
the latest versions of MapStore • GeoNode 4.4.1 is updated to MapStore v2024.01.01 • GeoNode 4.4.2, which will be released soon, will integrate MapStore v2024.02.02
editor • Metadata schemas are based on JSON-Schema models. This allows adapting and extending the schema with custom fields and validators, even without implementing custom modules • The JSON Schema also drives the automatic configuration of the client editor • A new /metadata API endpoint, specific to the management of metadata validation and CRUD operations, with fully compliant OpenAPI3 and JSON-Schema support
editor • Sparse fields: a new model that allows implementing new custom fields easily, without needing the creation of custom DB models and tables. It’s being used, as an example, to implement the European INSIPRE Schema • Upgrade to PyCSW3, which introduced support for ISO19115-3 (ISO19115-1:2014)
MapStore teams are collaborating to foster the integration and the alignment of the GeoNode client and MapStore frameworks • The MapStore team is developing a new home page and a new layout, with revamped styling and new features to support custom themes, UIs and components • These enhancements will be integrated back into GeoNode, along with a set of improvements to the templating system to support more control over custom home pages, themes and catalog layouts
• A First step toward “Geoserver Federation” for GeoNode. An external Geoserver can be configured to share the authentication services offered by GeoNode, to allow a deeper integration and allow serving remote layers under authentication and authorization. • This is also the first step toward the review of Remote Services implementation. Yet to be planned…
will receive a review in terms of improved security and sandboxing • Lot of legacy and unsupported functionality will be removed, with important benefits to maintenance and security • Review and cleanup of project’s dependencies and setup scripts • Deprecation of legacy APIs (V1)
simboss
autifyhq
tamaiyutaro
tjun
kawaguti
nagix
.png){kind=icon}
pharma_x_tech
databricksjapan
akuwano
suzuki_tada
kazeburo
snoozer05
danielanewman
mojombo
soudai
caitiem20
maltzj
tenderlove
bkeepers
sugarenia
jonrohan
chriscoyier
samanthasiow
bermonpainter
![The End Questions? [email protected]](https://files.speakerdeck.com/presentations/6c8077e679fd4f0a8c2f36efab56b30e/slide_35.jpg){kind=link}