GRA · Actuarial and Quantitative Risk
Spatial financeWhere capital meets hazard, exposure and transition
Released maps
Maps in quantitative risk work show where exposure accumulates and how hazard intensity varies, so that dependence between locations can be modelled honestly. This page explains how maps feed loss models and where their resolution limits the result.
The workspace for released maps.
Actuarial and Quantitative Risk · Map workspace. Map workspace: example names and illustrative values, not a record.
Released, referenced and rights-cleared.
- Time and space reference for every view.
- Sources and licence.
- Uncertainty and known limits.
- Version and date of release.
Exposure, hazard and the exceedance curve.
Which places drive loss in a severe year, and how far it reaches into reinsurance. Illustrative design values.
Dependence under stress.
| Dependence | Example | Modelling choice |
|---|---|---|
| Peril to peril | Hurricane wind and storm surge | Joint event footprints |
| Region to region | One storm across several states | Event-level simulation |
| Line to line | Property, marine and business interruption in one event | Common event set |
| Assets to liabilities | Catastrophe and market fall together | Copulas with tail dependence |
How the process runs.
Process
Released maps: Layers to published map
Layers enter with their rights, are aligned, analysed and checked for uncertainty, then released after public-safe review; a map is a governed spatial claim.
01 Data
- 01Source layers with their rightsDataset · NXS-GRX (canonical data, provenance and risk)Spatial views of The Global Risks Index (NXS-GRX) products sit under the boundary licence gate. Rights classification sets how a layer may be used.
02 Harmonise
- 02Coordinate reference and boundary versionRecord · NXS-EOP (earth observation and digital twins)The area of interest preserves its coordinate reference system, polygon validity and observation support. Boundary versions are kept.
- 03Harmonise units, variables and timeStepUnit metadata, conversion records and transformation logs are required. Alignment is an evidence event, not hidden preprocessing.
03 Analyse and check
- 04Analyse with a recorded processing recipeModel · GIS teamA processing recipe records parameters, calibration, inputs and output lineage. The analysis methods are named in each product’s own record.
- 05Spatial uncertainty checkGateSpatial uncertainty is recorded and affects downstream use. A high-uncertainty polygon may suit internal review, not public-safe release.
04 Publish
- 06Spatial metadata bundleRecordThe bundle records boundary type, jurisdiction, geometry version, projection, resolution, source, time window, uncertainty and access class.
- 07Public-safe release of the mapDecisionThe output record names the redactions, uncertainty and public-safe reviewer. A map is a governed spatial claim, never merely a picture.
Spatio-temporal intelligence · Data protocols: semantic, jurisdictional and temporal intelligence · NXS-EOPDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The pages cited are design doctrine.
Exposure, hazard and the exceedance curve.
The figure shows which places drive loss in a severe year. Copula choice changes the tail: a Gaussian copula has no tail dependence, a t or Gumbel copula does. Methods at GCRI uncertainty and validation; topic depth at dependence and correlation.
Releases appear as they are reviewed.
Analysis runs in Foundry; reviewed releases are listed here.
Where this page’s references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Questions and answers.
Can I request a map or model?
Contribute evidence from this page.
Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- EmailGateway GW-GRASend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGlobal Risks AllianceSee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Bring an exposure or capital question to the Alliance.
Information and enquiries are open today. 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.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.