Skip to content

GCRI · ژێرخانی هەستیار

داتا و ڕێگا تەکنیکییەکان

The public technical tools of ژێرخانی هەستیار: the models and data behind them, how to reproduce a view and the uncertainty it carries.

01شوێنی کار

The workspace for data and technical methods.

Build workspace

Critical infrastructure · Data and technical methods · Run R-3682 · Example interface, not a record

Run in progressGCRI · ژێرخانی هەستیار

Runs

same inputs, versioned

R-1874Reliabilityv6.10.45کارا
R-7493ئەندازیاری سیستەمەکانv3.40.65Failed test
R-9017زانستی تۆڕv2.20.42Failed test
R-1813Sensors, IoTv7.70.70Passed

کارتی مۆدێل

ڕێگا
ئەندازیاری متمانەپێکراوی و خۆڕاگری
تێکردنەکان
Asset register, Hazard layers
پشتڕاستکردنەوە
held-out period, skill reported
ناونیشان
مۆدێلکراو

Run log

  1. 00:00:56زانیاریIngest asset register
  2. 00:03:12زانیاریSchema and licence checks passed
  3. 00:07:40ئاگادارکردنەوەGap filled by interpolation, flagged
  4. 00:12:03تەواو بووCalibration complete
  5. 00:25:55دەروازەIndependent test queued
Build workspace.ڕووکاری نموونەیی؛ داتای ڕاستەوخۆ نییە.

Critical Infrastructure · Build workspace. Build workspace: example names and illustrative values, not a record.

02ئامرازەکان

What is published here.

نەخشەکان

Released maps

Open the released maps

مۆدێلەکان

Reviewed models and scenarios

Open the reviewed models

Scenarios

Sector scenarios

Open the sector scenarios

03Fitness for purpose

What every infrastructure tool should state about itself.

Infrastructure tools serve operators, regulators and emergency managers. A specialist looks for network coverage, the dependency assumptions behind cascade outputs and the aggregation applied to sensitive assets. They build on network science and resilience engineering and support the interdependency and cascade and electricity and lifelines topics.

  • Network coverage of any infrastructure layer.
  • Aggregation applied to sensitive assets.
  • Dependency assumptions in cascade outputs.
04پرۆسە

چۆن پرۆسەکە کار دەکات.

Process explorer · Process

Data and technical methods: Layers to published map

7 steps4 قۆناغ1 gate

پرۆسە

Data and technical methods: 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.

  1. 01 Data

    1. 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.
  2. 02 Harmonise

    1. 02Coordinate reference and boundary versionتۆمار · 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.
    2. 03Harmonise units, variables and timeهەنگاوUnit metadata, conversion records and transformation logs are required. Alignment is an evidence event, not hidden preprocessing.
  3. 03 Analyse and check

    1. 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.
    2. 05Spatial uncertainty checkدەروازەSpatial uncertainty is recorded and affects downstream use. A high-uncertainty polygon may suit internal review, not public-safe release.
  4. 04 بڵاوکردنەوە

    1. 06Spatial metadata bundleتۆمارThe bundle records boundary type, jurisdiction, geometry version, projection, resolution, source, time window, uncertainty and access class.
    2. 07Public-safe release of the mapبڕیارThe 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.

05Build environment

Working with the tools.

Analysis runs in Foundry for authorised projects. Public pages show released views only, each with its time and space reference and its rights.

06سەرچاوەکان

Where this page’s references lead.

ئەو لەش و بەڵگەنامانەی ئەم لاپەڕەیەیان لەگەڵ دەخوێنرێتەوە. دۆخ و وەشانەکان دەگۆڕێن؛ هەر بەستەرێک دەچێتە لای لەشی دەرکەر.

07لاپەڕەکان

Pages in Data and technical methods.

08پرسیارەکان

پرسیار و وەڵام.

Can I use the data?
Each released view states its licence and terms. Data that is not released is not available through these pages.
Reportsبەشداربە

لەم لاپەڕەیەوە بەڵگە پێشکەش بکە.

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.

GCRIژێرخانی هەستیارسیستەمە ستراتیژییەکانسیناریۆ و تاقیکردنەوەی گوشار
ژێرخانی هەستیار

ڕێگایەک، کۆمەڵە داتایەک یان پرسیارێک بهێنە.

زانیاری و پرسیار ئەمڕۆ کراوەن. پرسیارێک ژمارەی ئاماژەی پێدەدرێت و هەنگاوی دواتر دیاری دەکات؛ داواکاری، پارەدان، تەرخانکردنی کۆمپیوتەر و تۆمارکردن تەنیا کاتێک دەکرێنەوە کە تیم، مەرج و توانای پێداچوونەوەیان هەبێت.