search_stations

Find NVE hydrological stations and their available time series.

Signature: search_stations(municipality: string, optional, default None; county: string, optional, default None; station_name: string, optional, default None; active_only: yes/no, optional, default True; limit: integer, items, optional, default 25; offset: integer, items, optional, default 0)

Direct GET

For navigating agents: open the HTML page with parameters in the URL. The result is fetched and displayed without screenshots or form filling.

Open this validated HTML GET URL

https://allemannsdata.com/wiki/kilder/nve/search_stations/?municipality={municipality}&county={county}&station_name={station_name}&active_only=true&limit=25&offset=0

Replace {municipality}, {county}, {station_name}, {active_only}, {limit}, {offset} with values. Remove unused optional parameters from the URL.

For software and dashboards: Read the operation descriptor. The JSON GET template is https://allemannsdata.com/wiki/api/v1/kilder/nve/search_stations?municipality={municipality}&county={county}&station_name={station_name}&active_only=true&limit=25&offset=0. Open this exact request as JSON.

ParameterRequirementJSON typeDescription
municipalityoptionalunionMunicipality name (HydAPI field CouncilName).
countyoptionalunionCounty name.
station_nameoptionalunionStation name filter.
active_onlyoptionalbooleanReturn only active stations by default.
limitoptionalintegerMaximum stations returned (default 25, maximum 100). Unit: items.
offsetoptionalintegerNumber of matching stations to skip (default 0). Unit: items.
Generated JavaScript, Python and response structure

Use JSON when the user requests code, machine-readable data, value extraction or further computation. Use the HTML GET page to identify the correct source and verify parameters.

Example for generated JavaScript and Python

https://allemannsdata.com/wiki/api/v1/kilder/nve/search_stations?municipality={municipality}&county={county}&station_name={station_name}&active_only=true&limit=25&offset=0

Replace URL placeholders and remove unused optional parameters.

JavaScript in a dashboard

const url = "https://allemannsdata.com/wiki/api/v1/kilder/nve/search_stations?municipality={municipality}&county={county}&station_name={station_name}&active_only=true&limit=25&offset=0";
const response = await fetch(url);
if (!response.ok) {
  const failure = await response.json();
  throw new Error(`${failure.error.code}: ${failure.error.message} ${failure.suggestion}`);
}
const result = await response.json();
const data = result.data;

Python without additional packages

import json
from urllib.request import urlopen

url = "https://allemannsdata.com/wiki/api/v1/kilder/nve/search_stations?municipality={municipality}&county={county}&station_name={station_name}&active_only=true&limit=25&offset=0"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "nve",
  "operation": "search_stations",
  "parameters": {},
  "data": {},
  "entities": [],
  "_meta": {"retrieved_at": "...", "sources": [], "cache": {}},
  "_links": {"self": "...", "source": "...", "wiki": "...", "feedback": "..."}
}
Form for manual use

The form is a fallback for people and browser agents that cannot open the GET URL directly.

Type: string. Municipality name (HydAPI field CouncilName).
Type: string. County name.
Type: string. Station name filter.
Type: yes/no. Return only active stations by default.
Type: integer. Maximum stations returned (default 25, maximum 100). Unit: items.
Type: integer. Number of matching stations to skip (default 0). Unit: items.

Result

Source: NVE HydAPI. Retrieved 2026-09-20T21:32:14Z in 0.203 seconds.

Search scope: Municipality-filtered results cover all of AURE municipality.

Showing 1 of 1 results in compact format.

  1. station_id:
    114.1.0
    latitude:
    63.22446
    longitude:
    8.13032
Show all fields in HTML
currentLink:
https://hydapi.nve.no/api/v1/Stations?CouncilName=AURE&Active=OnlyActive
apiVersion:
1.0
license:
https://data.norge.no/nlod/en
createdAt:
2026-09-20T21:32:14.4484717Z
queryTime:
00:00:00.0008180
itemCount:
1
data:

1 results

  1. station_id:
    114.1.0
    stationName:
    Myra
    latitude:
    63.22446
    longitude:
    8.13032
    utmEast_Z33:
    155200
    utmNorth_Z33:
    7029084
    masl:
    31
    riverName:
    Storelva
    councilNumber:
    1576
    councilName:
    Aure
    countyName:
    Møre og Romsdal
    drainageBasinKey:
    1614
    hierarchy:
    Storelva
    lakeArea:
    0
    lakeName:
    not reported by source
    lakeNo:
    0
    regineNo:
    114.31Z
    reservoirNo:
    not reported by source
    reservoirName:
    not reported by source
    stationTypeName:
    Forvaltningsstasjon
    stationStatusName:
    Aktiv
    drainageBasinArea:
    16.46
    drainageBasinAreaNorway:
    16.459
    gradient1085:
    26.34
    gradientBasin:
    not reported by source
    gradientRiver:
    38
    heightMinimum:
    29
    heightHypso10:
    50
    heightHypso20:
    67
    heightHypso30:
    100
    heightHypso40:
    196
    heightHypso50:
    232
    heightHypso60:
    331
    heightHypso70:
    414
    heightHypso80:
    499
    heightHypso90:
    645
    heightMaximum:
    895
    lengthKmBasin:
    6.39
    lengthKmRiver:
    7.95
    percentAgricul:
    1.78
    percentBog:
    13.48
    percentEffBog:
    not reported by source
    percentEffLake:
    0.01
    percentForest:
    39.4
    percentGlacier:
    0
    percentLake:
    0.56
    percentMountain:
    42.01
    percentUrban:
    0
    utmZoneGravi:
    not reported by source
    utmEastGravi:
    not reported by source
    utmNorthGravi:
    not reported by source
    utmZoneInlet:
    not reported by source
    utmEastInlet:
    not reported by source
    utmNorthInlet:
    not reported by source
    utmZoneOutlet:
    not reported by source
    utmEastOutlet:
    not reported by source
    utmNorthOutlet:
    not reported by source
    annualRunoff:
    24.03
    specificDischarge:
    46.98
    regulationArea:
    0
    areaReservoirs:
    0
    volumeReservoirs:
    0
    regulationPartReservoirs:
    0
    transferAreaIn:
    0
    transferAreaOut:
    0
    reservoirAreaIn:
    0
    reservoirAreaOut:
    0
    reservoirVolumeIn:
    0
    reservoirVolumeOut:
    0
    remainingArea:
    0
    numberReservoirs:
    0
    firstYearRegulation:
    0
    catchmentRegTypeName:
    Uregulert
    owner:
    HH. Hydrologisk avd./Hydrometri
    qNumberOfYears:
    35
    qStartYear:
    1990
    qEndYear:
    2025
    qm:
    11.0816
    q5:
    13.2001
    q10:
    14.9372
    q20:
    16.6093
    q50:
    18.7823
    hm:
    1.448
    h5:
    1.5394
    h10:
    1.6092
    h20:
    1.6728
    h50:
    1.751
    culQm:
    19.6292
    culQ5:
    23.3817
    culQ10:
    26.4587
    culQ20:
    29.4206
    culQ50:
    33.2697
    culHm:
    1.7803
    culH5:
    1.9034
    culH10:
    1.9973
    culH20:
    2.0829
    culH50:
    2.1881
    seriesList:

    4 results

    1. parameterName:
      Vannstand
      parameter:
      1000
      versionNo:
      1
      unit:
      m
      serieFrom:
      1988-10-26T00:00:00
      serieTo:
      not reported by source
      resolutionList:

      3 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        1988-10-26T16:07:00Z
        dataToTime:
        2026-09-20T20:00:00Z
      2. resTime:
        60
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        1988-10-26T17:00:00Z
        dataToTime:
        2026-09-20T20:00:00Z
      3. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        1988-10-27T11:00:00Z
        dataToTime:
        2026-09-20T11:00:00Z
    2. parameterName:
      Vannføring
      parameter:
      1001
      versionNo:
      1
      unit:
      m³/s
      serieFrom:
      not reported by source
      serieTo:
      not reported by source
      resolutionList:

      3 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        1988-10-26T16:07:00Z
        dataToTime:
        2026-09-20T20:00:00Z
      2. resTime:
        60
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        1988-10-26T17:00:00Z
        dataToTime:
        2026-09-20T20:00:00Z
      3. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        1988-10-27T11:00:00Z
        dataToTime:
        2026-09-20T11:00:00Z
    3. parameterName:
      Vanntemperatur
      parameter:
      1003
      versionNo:
      2
      unit:
      °C
      serieFrom:
      2018-06-19T00:00:00
      serieTo:
      not reported by source
      resolutionList:

      3 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        2024-12-19T21:00:00Z
        dataToTime:
        2026-09-20T20:00:00Z
      2. resTime:
        60
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2024-12-19T21:00:00Z
        dataToTime:
        2026-09-20T20:00:00Z
      3. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2024-12-20T11:00:00Z
        dataToTime:
        2026-09-20T11:00:00Z
    4. parameterName:
      Lufttemperatur
      parameter:
      17
      versionNo:
      1
      unit:
      °C
      serieFrom:
      2006-05-19T00:00:00
      serieTo:
      not reported by source
      resolutionList:

      3 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        2006-05-22T23:30:00Z
        dataToTime:
        2026-09-20T21:00:00Z
      2. resTime:
        60
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2006-05-23T00:00:00Z
        dataToTime:
        2026-09-20T21:00:00Z
      3. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2006-05-23T11:00:00Z
        dataToTime:
        2026-09-20T11:00:00Z
limit:
25
offset:
0
returned:
1
has_more_results:
no
truncated:
no
Will you use the result in generated code?

Open the same result as JSON

Is data missing or incorrect? Send feedback about this result.

Continue exploring

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 the search_stations lookup

  1. Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
  2. Check types, units, limits and ID formats in the parameter table.
  3. Follow linked results to canonical pages before combining sources.

Misreading to avoid: An empty list means "no results for this lookup". An error message or unavailable source does not mean the data does not exist.

Source-specific next step

Go to the source page for other operations. Use the JSON template only after the HTML result shows that the parameters and source are correct.