Modelled 50-year ground snow load for the address's 1 km cell (seNorge)
snow_load24 fieldsNot in the demo
Available with: bought bundle or agreed plan (all fields) · Pricing
What this does not say
Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.
- Estimate, not the characteristic snow load of NS-EN 1991-1-3 / TEK and not a roof load: a modelled 50-year ground snow load from NVE's seNorge snow model for the 1 km cell that holds the address.
- Annual maximum of seNorge daily snow water equivalent per hydrological year (1 Sep-31 Aug) from 1957/58, Gumbel distribution fitted by the method of moments to the years with snow, with snow-free years as a point mass at zero; ground_snow_load_50y_kn_m2 = 50-year swe in mm x 0.00981 (1 mm of water weighs 9.81 N/m2). Fewer than 10 snowy years gives status too_few_snow_years and a null load. trend_30y_kn_m2_per_decade is the least-squares slope of the annual maximum over the last 30 complete years with its standard error; it describes the past, not a forecast.
- No height correction: seNorge models the cell at its mean altitude (cell_altitude_m), and snow load rises steeply with height. address_height_above_cell_m shows the gap; a building well above the cell mean can carry a much larger load than the cell value. Shape, exposure, thermal and drift factors of a real roof are not included.
- exceeds_era_design is null for every address: the design values of the building's era (NS 3491-3 / NS-EN 1991-1-3 national annex) are kommune tables in a standard that is not open data, so no comparison is made (era_design_comparison_status says so).
- Licence: NLOD (NVE GridTimeSeries, listed on api.nve.no). Attribution: NVE, seNorge. Model: Approach.
Fields
2 of 24 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.
| Field | Type | Role |
|---|---|---|
| cell_id | string | null | context |
| status | string | null | context |
| method | string | null | context |
| method_version | string | null | context |
| cell_altitude_m | number | null | context |
| address_elevation_m | number | null (m) | context |
| address_height_above_cell_m | number | null | context |
| ground_snow_load_50y_kn_m2 | number | null (m2) | value |
| swe_50y_mm | number | null | context |
| mean_annual_max_kn_m2 | number | null (m2) | context |
| gumbel_location_mm | number | null | context |
| gumbel_scale_mm | number | null | context |
| first_year | integer | null (årstall) | context |
| last_year | integer | null (årstall) | context |
| years | integer | null | context |
| snow_free_years | integer | null | context |
| trend_30y_kn_m2_per_decade | number | null | value |
| trend_30y_stderr | number | null | context |
| trend_30y_years | integer | null | context |
| exceeds_era_design | boolean | null | context |
| era_design_comparison_status | string | null | context |
| validation | object | null | context |
| source_fetched_at | timestamp | null | context |
| updated_at | timestamp | null | context |
Fetch this section
Send the key in the X-API-Key header. The section can be fetched with the rest of the address, or on its own with pagination.
curl --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643?include=snow_load' # paginated, one section at a time curl --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643/sections/snow_load?limit=25'
Why it cannot be tried here
This section is not part of the public demo projection. That is a licensing and privacy decision, not a sign the data is missing: it is served to customers granted the section.