Natural hazards (NVE)
Flood, quick-clay, landslide, snow-avalanche, rockfall and debris-flow screening at a point, plus registered landslide events, from NVE's hazard maps.
Explore in the wiki
Related sources
- Weather and natural hazards – Weather and natural-hazard warnings for the same coordinate.
- Geology (NGU) – Quick-clay and marine-limit geology behind the landslide screening.
- Regobs observations – Field observations of the landslides and avalanches the screening maps flag.
All lookup operations
Open HTML operations for navigation. The JSON link for each operation is only for programmatic data access.
Building software or a dashboard? List operation names as JSON, then open the selected operation's descriptor before fetching data.
-
get_hazards_at_point– Run every NVE natural-hazard screening check for one coordinate.
HTML GET template -
find_landslide_events– Registered landslide events near a coordinate, from NVE's event register.
HTML GET template
Programmatic access
First confirm the operation and parameters in HTML, then use the read-only JSON API.
Does the client support MCP? Find the corresponding Allemannsdata server and registered tools.
How an AI agent should use this page
Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.
How to use Natural hazards (NVE)
Flood, quick-clay, landslide, snow-avalanche, rockfall and debris-flow screening at a point, plus registered landslide events, from NVE's hazard maps. Choose a search lookup first when you lack an identifier; use a detail lookup when you already have a stable ID.
- Read requirements, cache time and known usage limits.
- Open the lookup and use the HTML GET template.
- Follow normalized result links onward; use JSON only for structured data work.
Related sources and scope
AI agent? Read the complete navigation and programming guide.