- Source
- Weather data from MET Norway (Norwegian Meteorological Institute), licensed under CC BY 4.0, from its Locationforecast 2.0 API (opens in a new tab). Units are converted and the provider’s symbols are mapped to HELPERG’s own condition vocabulary, so the data is modified; the attribution the licence requires is rendered from the response with every reading.
- How far ahead
- This page asks the provider for 48 hours and 10 days — the most it publishes — and shows what comes back. MET Norway documents its forecast as covering the next nine days; in local calendar terms that is ten dates, of which the first and the last are partial. So the heading over the daily rows names the number of days actually rendered, the Extended view is the provider's own range and nothing beyond it, and no day is invented to reach a round number. There is no 14-day forecast here because the provider does not publish one.
- What the numbers are
- Model output for a point, including the hour in progress. MET Norway operates no station at every coordinate, so nothing here is called observed or measured. Where the provider publishes no value for an hour, a dash is shown.
- Sunrise and sunset
- Not shown. They come from a different MET Norway service that this deployment does not call, and computing them here would be HELPERG’s arithmetic presented as the provider’s data.
- Your location
- Asked for only when you press the button, and rounded to two decimal places — about 1.1 km — before any request is made. The point is matched against the cities listed on this page, in your browser and without asking anyone: inside a city you are told the city, near one you are told you are near it, and beyond that the coordinates stand rather than a town being guessed for you. This page sends it in the body of a POST rather than as a parameter in a web address: a request URL, unlike a request body, is part of the metadata a hosting platform records, and HELPERG can neither write nor erase that. It is never attached to analytics, never written to this page’s address bar, and not stored on HELPERG’s servers. Recent places are kept in this browser, and the button above deletes them.
- Your device’s time zone
- Read when the page opens, to decide which city to show you first — and read again if you type a coordinate of your own, because a bare point carries no time zone and the hours still have to be grouped into days. It is treated as a suggestion and never as a statement about where you are: a time zone covers a whole region, travels with a laptop and can be set by hand, so the page says where the choice came from and offers to change it. The matching is a short list inside this page’s own script, so nothing is asked of anyone to perform it, and a zone that is not on that list produces no suggestion at all rather than a nearest guess. What travels is the reading: the chosen city’s two-decimal coordinates and a time-zone identifier go to HELPERG in the body of a POST, and HELPERG asks MET Norway for those coordinates alone — the time zone is used on HELPERG’s side, to group hours into local days, and is not passed on. Nothing here reaches for your IP address: HELPERG looks up no location from one, and this page reads none of the location headers its hosting platform offers. A suggestion is not a choice, so it is not kept in this browser, not added to this page’s address bar, and replaced the moment you pick a city.
- Place search
- Optional, and supplied by a configured provider because MET Norway publishes no gazetteer. Where it is not configured the field is not shown, and the cities, your location and the coordinate entry all reach the same reading. A query is a cache key for a few minutes; HELPERG does not log it, count it or attribute it to a reader, and this page sends it in a request body so that it is not part of any web address.
- Warnings
- None are shown. HELPERG does not derive a warning from a threshold; a warning belongs to the meteorological authority that issued it, and this deployment has no authority feed configured. For official warnings, use your national meteorological service.
- Freshness
- Readings are cached on the server for a bounded time and served with their real age and the provider’s own model-run time. If the provider cannot be reached, the last good reading is served and labelled as such.
- The same data as JSON
- Current conditions at
/api/public/v1/weather/current and the forecast at /api/public/v1/weather/forecast, both public, rate-limited and documented in the developer documentation. Each answers a GET with query parameters and a POST with a JSON body; the parameters of a GET are part of the request URL, which a hosting platform may record in its request metadata, so a caller who does not want a coordinate there should use POST, as this page does.