Overview#
Connect an existing GeoNode spatial data portal to the platform with a single governed sync call, and authoritative government map layers flow straight into your analysts' working environment.
National mapping authorities, civil-protection agencies, and UN and EU programme offices already run GeoNode as the backbone of their spatial data infrastructure. Flood zones, land-use layers, infrastructure footprints, and humanitarian response boundaries live there as published datasets. This module reaches into a remote GeoNode portal over its open REST interface, pulls the dataset metadata your team needs, and stores it under your own organisation's control. There are no manual exports, no spreadsheet hand-offs, and no bespoke connector to commission for each new node.
Every layer brought across keeps its provenance and is filtered by clearance, so an analyst sees only what their organisation holds and only what their secrecy level permits. Existing GeoNode deployments, from a national spatial data infrastructure node to a humanitarian response portal, need no modification of any kind to participate.
Key Features#
-
Single-call dataset sync: One governed operation reaches a remote GeoNode portal, pulls a dataset's full metadata record, and persists it under your organisation. No batch jobs, no manual exports, no per-node custom code.
-
Authoritative metadata capture: Each synced layer carries its dataset name, layer type, thematic category, descriptive abstract, spatial reference identifier, bounding-box geometry, and recorded download count, giving analysts the same context the source authority publishes.
-
Bounding-box geometry in GeoJSON: Every dataset's spatial extent is stored as RFC 7946 GeoJSON, ready to render directly on any modern web map without format conversion.
-
Coordinate reference clarity: The spatial reference identifier travels with each layer, defaulting to the global
EPSG:4326/ CRS84 system so downstream maps and spatial tools place every feature correctly. -
Organisation-scoped isolation: Layers synced by one tenant are architecturally inaccessible to another. The sovereignty check sits in the service layer, not at the data store alone, so cross-tenant leakage is structurally prevented.
-
Clearance-aware delivery: Returned layers are filtered against the requesting user's secrecy clearance, so each analyst sees only the datasets their level permits.
-
Optional remote authentication: The portal connector supports bearer-token authentication against secured GeoNode instances, so private and access-controlled nodes are reachable alongside open ones.
-
Full audit provenance: Every sync writes to the interoperability audit trail with the acting user, organisation, source portal, and record reference, producing a defensible chain of custody for each ingested layer.
Use Cases#
National Mapping and Spatial Data Infrastructure#
National mapping authorities operating a GeoNode spatial data infrastructure node can expose authoritative cadastral, topographic, and land-use layers to authorised analysts. A geographic information officer connects the national node once, and downstream teams pull updated layers on demand rather than circulating exported files.
Civil Protection and Disaster Response#
Civil-protection agencies maintain flood zones, hazard maps, and evacuation boundaries in GeoNode. During an incident, responders bring the current authoritative layers across in seconds, keeping operational maps aligned with the official source of record.
Humanitarian Programme Offices#
UN and EU programme offices that run humanitarian portals, including ReliefWeb-style response sites, can share response boundaries, affected-area footprints, and logistics layers with partner organisations through a governed channel that preserves access controls.
Critical Infrastructure Oversight#
Agencies tracking infrastructure footprints, such as energy corridors, transport networks, and utility coverage, can synchronise those layers from a sector portal and correlate them with operational entities already held on the platform.
Integration#
Customers plug in through a small, consistent set of operations over the curated GraphQL endpoint. A read field, geonodeDatasets, returns the layers held for the calling organisation; a companion field, geonodeStats, reports aggregate dataset and category counts. The write side exposes a single operation that accepts the remote portal address, the target dataset reference, and an optional bearer token, then performs the fetch, persist, and audit cycle in one round trip.
Under the surface, the connector speaks the GeoNode REST API v2 over standard HTTPS with a configurable timeout, reading from /api/v2/datasets and /api/v2/datasets/{id}. Authentication to the calling organisation uses the platform's OAuth2 and JWT model, while authentication to the remote GeoNode portal is handled with an optional Authorization: Bearer token, so secured and open nodes are reached the same way. Ingested layers land in a normalised dataset model shared across the platform's interoperability bridge, which means a synced GeoNode layer is treated identically to spatial entities arriving from any other connector. The benefit for the customer is reach without rework: an existing GeoNode deployment becomes a governed data source with no change to the source system and no bespoke pipeline to maintain.
Open Standards#
- GeoJSON (IETF RFC 7946): The bounding-box extent and geometry of every synced dataset are encoded as RFC 7946 GeoJSON, the interoperable JSON format consumable by any modern web mapping client. https://datatracker.ietf.org/doc/html/rfc7946
- EPSG:4326 / CRS84: The default spatial reference system recorded for each layer, the global geographic coordinate system used across open mapping and spatial analysis tools. https://epsg.io/4326
- GeoNode REST API v2: The open REST interface of the GeoNode open-source content management system, itself underpinned by the OGC WFS, WMS, WMTS, and CSW service families, used to read dataset metadata from remote portals. https://docs.geonode.org/en/master/devel/api/V2/
- OGC Web Feature Service (WFS): The OGC standard for serving geospatial features that GeoNode exposes for its published datasets. https://www.ogc.org/standard/wfs/
- OGC Web Map Service (WMS): The OGC standard for serving rendered map imagery that GeoNode provides for its layers. https://www.ogc.org/standard/wms/
- OGC Catalogue Service for the Web (CSW): The OGC catalogue standard that GeoNode uses to publish discoverable metadata for its spatial holdings. https://www.ogc.org/standard/cat/
Security & Compliance#
Access to every layer is scoped to the requesting organisation, and results are filtered against the user's secrecy clearance before they leave the service. Synced layers from one tenant remain architecturally inaccessible to another. Every sync operation is recorded in the interoperability audit trail with the acting user, organisation, source portal, and record reference, supporting an auditable chain of custody for cross-organisation data exchange. Connections to secured remote portals use bearer-token authentication, and all remote calls run with a bounded timeout.
Last Reviewed: 2026-05-26 Last Updated: 2026-05-26