Topic: Natural hazards Practical guide Evidence: Moderate

Data guide: geological and meteorological hazards on ClearSpot

ClearSpot adds an optional geological and meteorological risk block on the map. It is split into taxa you can toggle individually after enabling the group in the cog menu: seismic, tsunami context, volcanic unrest, flood response, tropical cyclones, tornado outlooks (US-centric), plus mapped baseline zones from OpenStreetMap hazard=* polygons.

Two rhythms: live feeds and slow baselines

Live feeds are polled on a short cadence from public APIs (USGS GeoJSON, GDACS lists, NHC CurrentStorms, SPC CSV). They answer: is something going on right now that should appear as a point or storm track on the map?

Baseline mapping crawls OSM less often and stores closed hazard polygons in the NZOI catalogue. That answers a different question: where do communities already document chronic or zonal exposure (flood plains, avalanche corridors, etc.) even when no headline event is active?

Read geography, not just dots

Example: the summit of Mont Blanc is not in an oceanic tsunami inundation plain. A live offshore centroid can still show up on global feeds because the feed is worldwide—so always cross-check context. ClearSpot is informational cartography; it is not an emergency alerting service, and the UI verdict words stay product tokens: clear, not clear, and all clear when nothing trips your sensitivity.

Where to tune visibility

Use the cog button: enable the parent checkbox, expand the list, and switch off any taxon you do not want drawn. The data sources page lists upstream licences and links.

26 885 punti dati

nell’indice ClearSpot per questa fonte dati

Ultimo ricalcolo totali: 2026-05-03 21:59 UTC.

Torna alle fonti dati