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-21T00:47:48Z in 0.152 seconds.

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

Showing 1 of 1 results in compact format.

  1. station_id:
    102.1.0
    latitude:
    62.60018
    longitude:
    6.34442
Show all fields in HTML
currentLink:
https://hydapi.nve.no/api/v1/Stations?CouncilName=HARAM&Active=OnlyActive
apiVersion:
1.0
license:
https://data.norge.no/nlod/en
createdAt:
2026-09-21T00:47:48.356466Z
queryTime:
00:00:00.0021158
itemCount:
1
data:

1 results

  1. station_id:
    102.1.0
    stationName:
    Hildreelv
    latitude:
    62.60018
    longitude:
    6.34442
    utmEast_Z33:
    56566
    utmNorth_Z33:
    6970861
    masl:
    37
    riverName:
    Hildreelva
    councilNumber:
    1580
    councilName:
    Haram
    countyName:
    Møre og Romsdal
    drainageBasinKey:
    2284
    hierarchy:
    Hildreelva
    lakeArea:
    0
    lakeName:
    not reported by source
    lakeNo:
    0
    regineNo:
    102.11Z
    reservoirNo:
    not reported by source
    reservoirName:
    not reported by source
    stationTypeName:
    Forvaltningsstasjon
    stationStatusName:
    Aktiv
    drainageBasinArea:
    14.25
    drainageBasinAreaNorway:
    14.25
    gradient1085:
    34.26
    gradientBasin:
    not reported by source
    gradientRiver:
    30.23
    heightMinimum:
    32
    heightHypso10:
    156
    heightHypso20:
    225
    heightHypso30:
    265
    heightHypso40:
    309
    heightHypso50:
    354
    heightHypso60:
    396
    heightHypso70:
    456
    heightHypso80:
    562
    heightHypso90:
    686
    heightMaximum:
    786
    lengthKmBasin:
    6.03
    lengthKmRiver:
    7.28
    percentAgricul:
    0.84
    percentBog:
    0.96
    percentEffBog:
    not reported by source
    percentEffLake:
    1.97
    percentForest:
    29.45
    percentGlacier:
    0
    percentLake:
    6.28
    percentMountain:
    28.9
    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:
    21.04
    specificDischarge:
    46.79
    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:
    19
    qStartYear:
    2006
    qEndYear:
    2025
    qm:
    10.6215
    q5:
    13.1435
    q10:
    14.3317
    q20:
    15.2257
    q50:
    16.1083
    hm:
    1.9005
    h5:
    1.9823
    h10:
    2.0174
    h20:
    2.0427
    h50:
    2.0668
    culQm:
    17.6032
    culQ5:
    21.7829
    culQ10:
    23.7521
    culQ20:
    25.2338
    culQ50:
    26.6965
    culHm:
    2.1057
    culH5:
    2.2047
    culH10:
    2.2472
    culH20:
    2.2778
    culH50:
    2.3069
    seriesList:

    4 results

    1. parameterName:
      Vannstand
      parameter:
      1000
      versionNo:
      1
      unit:
      m
      serieFrom:
      2006-08-16T00:00:00
      serieTo:
      not reported by source
      resolutionList:

      3 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        2006-08-17T05:00:00Z
        dataToTime:
        2026-09-21T00:00:00Z
      2. resTime:
        60
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2006-08-17T06:00:00Z
        dataToTime:
        2026-09-21T00:00:00Z
      3. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2006-08-18T11: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:
        2006-08-17T05:00:00Z
        dataToTime:
        2026-09-21T00:00:00Z
      2. resTime:
        60
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2006-08-17T06:00:00Z
        dataToTime:
        2026-09-21T00:00:00Z
      3. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2006-08-17T11:00:00Z
        dataToTime:
        2026-09-20T11:00:00Z
    3. parameterName:
      Vanntemperatur
      parameter:
      1003
      versionNo:
      1
      unit:
      °C
      serieFrom:
      2017-03-15T00:00:00
      serieTo:
      not reported by source
      resolutionList:

      3 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        2015-06-29T12:00:00Z
        dataToTime:
        2025-05-13T14:12:00Z
      2. resTime:
        60
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2015-06-29T13:00:00Z
        dataToTime:
        2025-05-13T14:00:00Z
      3. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2015-06-30T11:00:00Z
        dataToTime:
        2025-05-12T11:00:00Z
    4. parameterName:
      Lufttemperatur
      parameter:
      17
      versionNo:
      1
      unit:
      °C
      serieFrom:
      2006-08-16T00:00:00
      serieTo:
      not reported by source
      resolutionList:

      3 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        2006-08-17T05:00:00Z
        dataToTime:
        2026-09-21T00:00:00Z
      2. resTime:
        60
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2006-08-17T06:00:00Z
        dataToTime:
        2026-09-21T00:00:00Z
      3. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2006-08-17T11: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.