Allemannsdata Wiki
Manual search

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-21T09:55:57Z in 0.152 seconds.

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

Showing 2 of 2 results in compact format.

  1. station_id:
    2.210.0
    latitude:
    60.62306
    longitude:
    10.57922
  2. station_id:
    2.212.0
    latitude:
    60.64261
    longitude:
    10.59663
Show all fields in HTML
currentLink:
https://hydapi.nve.no/api/v1/Stations?CouncilName=VESTRE+TOTEN&Active=OnlyActive
apiVersion:
1.0
license:
https://data.norge.no/nlod/en
createdAt:
2026-09-21T09:55:57.1424947Z
queryTime:
00:00:00.0011638
itemCount:
2
data:

2 results

  1. Open the place page for this point

    station_id:
    2.210.0
    stationName:
    Skjelbreia
    latitude:
    60.62306
    longitude:
    10.57922
    utmEast_Z33:
    258195
    utmNorth_Z33:
    6728938
    masl:
    406
    riverName:
    elv fra Skjelbreida
    councilNumber:
    3443
    councilName:
    Vestre Toten
    countyName:
    Innlandet
    drainageBasinKey:
    126
    hierarchy:
    elv fra Skjelbreida/Hunnselva/Vorma-Lågen/Glommavassdraget
    lakeArea:
    2.71
    lakeName:
    Skjelbreida
    lakeNo:
    254
    regineNo:
    002.DCD1B
    reservoirNo:
    64
    reservoirName:
    SKJELBREIA
    stationTypeName:
    Privat, pålagt
    stationStatusName:
    Aktiv
    drainageBasinArea:
    25.4
    drainageBasinAreaNorway:
    25.4
    gradient1085:
    24.98
    gradientBasin:
    13.67
    gradientRiver:
    24.95
    heightMinimum:
    407
    heightHypso10:
    412
    heightHypso20:
    416
    heightHypso30:
    429
    heightHypso40:
    443
    heightHypso50:
    463
    heightHypso60:
    500
    heightHypso70:
    535
    heightHypso80:
    557
    heightHypso90:
    600
    heightMaximum:
    720
    lengthKmBasin:
    7.63
    lengthKmRiver:
    9.66
    percentAgricul:
    5.34
    percentBog:
    5.51
    percentEffBog:
    not reported by source
    percentEffLake:
    10.74
    percentForest:
    77.64
    percentGlacier:
    0
    percentLake:
    11.07
    percentMountain:
    0
    percentUrban:
    0
    utmZoneGravi:
    33
    utmEastGravi:
    256270
    utmNorthGravi:
    6729569
    utmZoneInlet:
    33
    utmEastInlet:
    255749
    utmNorthInlet:
    6735924
    utmZoneOutlet:
    not reported by source
    utmEastOutlet:
    not reported by source
    utmNorthOutlet:
    not reported by source
    annualRunoff:
    9.59
    specificDischarge:
    11.95
    regulationArea:
    25.42
    areaReservoirs:
    2.71
    volumeReservoirs:
    6.75
    regulationPartReservoirs:
    0.7
    transferAreaIn:
    0
    transferAreaOut:
    0
    reservoirAreaIn:
    0
    reservoirAreaOut:
    2.71
    reservoirVolumeIn:
    0
    reservoirVolumeOut:
    6.75
    remainingArea:
    0
    numberReservoirs:
    1
    firstYearRegulation:
    1983
    catchmentRegTypeName:
    regulert m/magasinregulering
    owner:
    VOKKS KRAFT AS
    qNumberOfYears:
    not reported by source
    qStartYear:
    not reported by source
    qEndYear:
    not reported by source
    qm:
    not reported by source
    q5:
    not reported by source
    q10:
    not reported by source
    q20:
    not reported by source
    q50:
    not reported by source
    hm:
    not reported by source
    h5:
    not reported by source
    h10:
    not reported by source
    h20:
    not reported by source
    h50:
    not reported by source
    culQm:
    not reported by source
    culQ5:
    not reported by source
    culQ10:
    not reported by source
    culQ20:
    not reported by source
    culQ50:
    not reported by source
    culHm:
    not reported by source
    culH5:
    not reported by source
    culH10:
    not reported by source
    culH20:
    not reported by source
    culH50:
    not reported by source
    seriesList:

    2 results

    1. parameterName:
      Vannstand
      parameter:
      1000
      versionNo:
      0
      unit:
      m
      serieFrom:
      not reported by source
      serieTo:
      not reported by source
      resolutionList:

      2 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        1951-01-03T11:00:00Z
        dataToTime:
        2026-06-15T07:00:00Z
      2. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        1951-01-03T11:00:00Z
        dataToTime:
        2026-06-15T11:00:00Z
    2. parameterName:
      Magasinvolum
      parameter:
      1004
      versionNo:
      0
      unit:
      millioner m³
      serieFrom:
      not reported by source
      serieTo:
      not reported by source
      resolutionList:

      2 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        1951-01-03T11:00:00Z
        dataToTime:
        2026-06-15T07:00:00Z
      2. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        1951-01-03T11:00:00Z
        dataToTime:
        2026-06-15T11:00:00Z

  2. Open the place page for this point

    station_id:
    2.212.0
    stationName:
    Einavatn
    latitude:
    60.64261
    longitude:
    10.59663
    utmEast_Z33:
    259292
    utmNorth_Z33:
    6731048
    masl:
    401
    riverName:
    Hunnselva
    councilNumber:
    3443
    councilName:
    Vestre Toten
    countyName:
    Innlandet
    drainageBasinKey:
    127
    hierarchy:
    Hunnselva/Vorma-Lågen/Glommavassdraget
    lakeArea:
    13.82
    lakeName:
    Einavatnet
    lakeNo:
    143
    regineNo:
    002.DCC7
    reservoirNo:
    40
    reservoirName:
    EINAVATN
    stationTypeName:
    Privat, pålagt
    stationStatusName:
    Aktiv
    drainageBasinArea:
    155.92
    drainageBasinAreaNorway:
    155.92
    gradient1085:
    3.85
    gradientBasin:
    14.57
    gradientRiver:
    6.99
    heightMinimum:
    395
    heightHypso10:
    418
    heightHypso20:
    435
    heightHypso30:
    447
    heightHypso40:
    473
    heightHypso50:
    501
    heightHypso60:
    529
    heightHypso70:
    569
    heightHypso80:
    603
    heightHypso90:
    650
    heightMaximum:
    756
    lengthKmBasin:
    21.98
    lengthKmRiver:
    24.91
    percentAgricul:
    13.83
    percentBog:
    3.62
    percentEffBog:
    not reported by source
    percentEffLake:
    9.01
    percentForest:
    69.98
    percentGlacier:
    0
    percentLake:
    11.07
    percentMountain:
    0
    percentUrban:
    0.29
    utmZoneGravi:
    33
    utmEastGravi:
    259927
    utmNorthGravi:
    6721539
    utmZoneInlet:
    33
    utmEastInlet:
    262537
    utmNorthInlet:
    6708290
    utmZoneOutlet:
    not reported by source
    utmEastOutlet:
    not reported by source
    utmNorthOutlet:
    not reported by source
    annualRunoff:
    68.22
    specificDischarge:
    13.86
    regulationArea:
    155.95
    areaReservoirs:
    16.65
    volumeReservoirs:
    38.95
    regulationPartReservoirs:
    0.57
    transferAreaIn:
    0
    transferAreaOut:
    0
    reservoirAreaIn:
    0
    reservoirAreaOut:
    16.65
    reservoirVolumeIn:
    0
    reservoirVolumeOut:
    38.95
    remainingArea:
    0
    numberReservoirs:
    2
    firstYearRegulation:
    1983
    catchmentRegTypeName:
    regulert m/magasinregulering
    owner:
    VOKKS KRAFT AS
    qNumberOfYears:
    not reported by source
    qStartYear:
    not reported by source
    qEndYear:
    not reported by source
    qm:
    not reported by source
    q5:
    not reported by source
    q10:
    not reported by source
    q20:
    not reported by source
    q50:
    not reported by source
    hm:
    not reported by source
    h5:
    not reported by source
    h10:
    not reported by source
    h20:
    not reported by source
    h50:
    not reported by source
    culQm:
    not reported by source
    culQ5:
    not reported by source
    culQ10:
    not reported by source
    culQ20:
    not reported by source
    culQ50:
    not reported by source
    culHm:
    not reported by source
    culH5:
    not reported by source
    culH10:
    not reported by source
    culH20:
    not reported by source
    culH50:
    not reported by source
    seriesList:

    2 results

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

      2 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        1994-08-08T11:00:00Z
        dataToTime:
        2026-09-21T06:00:00Z
      2. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        1994-08-08T11:00:00Z
        dataToTime:
        2026-09-21T11:00:00Z
    2. parameterName:
      Magasinvolum
      parameter:
      1004
      versionNo:
      50
      unit:
      millioner m³
      serieFrom:
      not reported by source
      serieTo:
      not reported by source
      resolutionList:

      2 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        1994-08-08T11:00:00Z
        dataToTime:
        2026-09-21T06:00:00Z
      2. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        1994-08-08T11:00:00Z
        dataToTime:
        2026-09-21T11:00:00Z
limit:
25
offset:
0
returned:
2
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.

AI agent? Read the complete navigation and programming guide.