G09 · METHOD · geospatialGCRI dossier · service level R0
GCRINexus FoundryEstablished
Method page · Geospatial information systems

Geospatial infrastructure at Nexus Foundry

Geospatial information systems give every record a place: hazard grids, asset registers, boundaries and imagery brought into one frame. In this field they also carry the sharpest disclosure risks, so the work runs from coordinate reference and catalogue through to a recorded public-safe release decision.

01In brief

The short answer.

Geospatial data infrastructure is the set of catalogues, services, standards and policies that let spatial data be found, combined and served. Here it brings hazard grids, asset registers, boundaries and imagery into one frame, with coordinate references and catalogues, and ends with a recorded decision on what is safe to publish.

02Console

Spatial model, in outline.

The working screen behind this method: its structure, terms and states. Names are placeholders and values illustrative.

Spatial model: the screen's structure, terms and states for Foundry.Placeholder names and illustrative values; a design, not a record or a live system.
03Application

What geospatial information systems does here.

Geospatial information systems capture, store, analyse and present location-referenced data. They provide the common spatial frame for combining hazard, exposure and vulnerability information. In data and compute and methods and modelling, geospatial analysis identifies where hazards overlap critical assets and vulnerable populations. It supports location-based planning across infrastructure, health and finance. The canonical description is on the STEM Commons.

Imagery catalogues through STAC

Satellite and aerial products are indexed as STAC items with footprint, time, sensor and processing level, so analysts query by place and date and analysis runs next to the archive.

Exposure overlays with stated aggregation

Hazard layers are intersected with buildings, population grids and networks on a common equal-area grid, with the aggregation unit and denominators stated beside every count.

Public-safe map release

Before publication, sensitive layers are generalised, small counts are suppressed and combinations with other public data are reviewed; the release record names the person who decided.

04Key terms

Terms used on this page.

Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.

TermDefinition
OGC APIA family of Open Geospatial Consortium web interface standards for serving features, maps, tiles and coverages.
Exposure overlayIntersecting a hazard layer with population or asset layers to estimate what is exposed.
Public-safe releaseA recorded decision on the detail at which a layer may be published without exposing sensitive sites or people.
05Geography

Land surface in Canada.

Surface classes an Earth-observation programme reads: ranges, deserts, glaciers, lakes and reefs, shown for Canada as an example geography for this subject.

Surface classes an Earth-observation programme reads: ranges, deserts, glaciers, lakes and reefs.Indicator derived from Natural Earth at map scale; a screening view, not an assessment.
GCRI · Nexus Foundry · fieldDESIGN FIGURE
06Canvas

The method as a run graph.

Data from the source register feeds the methods; calibration and an independent test gate the estimate and its limits; the decision stays with the competent authority.

Method canvas · Geospatial information systems as applied hereDesign, not a record
Geospatial information systems in Nexus Foundry: from layers to a published mapLayers are ingested with their licences, reprojected and harmonised, analysed (overlay, zonal statistics, indices), checked for uncertainty and published as a map with its passport. Design of the process, not a record of a run.

Fig. 01Nodes carry their type, metrics and state; connectors show what feeds what; the gates are the validation steps; the timeline is one application. Design of the method's use, not a record of a run.

07Data

What the method consumes.

Datasets and records used by geospatial information systems on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.

DataRoleLabel
Copernicus DEMTerrain, drainage and inundationMODELLED
OpenStreetMapRoads, buildings and facilitiesREPORTED
Administrative boundariesReporting unitsOFFICIAL
Sentinel-2 and Landsat imageryLand cover and changeOBSERVED
Gridded populationExposure denominatorsESTIMATED
08Validation

How results are checked.

Positional and attribute accuracy are checked against surveyed control points and reference datasets. Topology rules and metadata standards ensure consistency.

CheckHow it is done
Reference system checkEvery layer's horizontal and vertical reference is declared, and transformations use EPSG definitions
Positional accuracyLayers are compared with surveyed control points and the error is published with the layer
Topology validationGaps, overlaps and invalid geometries are detected before any overlay
Disclosure reviewPublished resolution and layer combinations are checked so no facility or household can be singled out

Errors in projection, scale and data currency propagate through analysis. Aggregation to administrative units can mask local variation.

09Connections

Topics that rely on this method.

10Stewardship

Who maintains the method.

Space and Earth Observation stewards geospatial information systems for the Consortium and reviews how it is applied across platforms.

12Questions

Questions and answers.

What are the limits of geospatial information systems in this field?
Errors in projection, scale and data currency propagate through analysis. Aggregation to administrative units can mask local variation.
How are results checked?
Positional and attribute accuracy are checked against surveyed control points and reference datasets. Topology rules and metadata standards ensure consistency.
Are the values on this page real?
The data names, roles and checks are real descriptions of practice. The canvas shows a design of the method's use, not a run; no result is reported here.
Where else is this method applied?
The canonical method page lists every platform that applies it.
Nexus Foundry

Bring your expertise to this field.

The current service level is R0: information and enquiries. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.

Have questions?