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-22T13:58:59Z in 0.173 seconds.

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

Showing 1 of 1 results in compact format.

  1. station_id:
    17.13.0
    latitude:
    58.98133
    longitude:
    9.24908
Show all fields in HTML
currentLink:
https://hydapi.nve.no/api/v1/Stations?CouncilName=DRANGEDAL&Active=OnlyActive
apiVersion:
1.0
license:
https://data.norge.no/nlod/en
createdAt:
2026-09-22T13:58:59.9466116Z
queryTime:
00:00:00.0013122
itemCount:
1
data:

1 results

  1. station_id:
    17.13.0
    stationName:
    Nedre Tokevatn
    latitude:
    58.98133
    longitude:
    9.24908
    utmEast_Z33:
    169678
    utmNorth_Z33:
    6552199
    masl:
    63
    riverName:
    Kragerøvassdraget
    councilNumber:
    4016
    councilName:
    Drangedal
    countyName:
    Telemark
    drainageBasinKey:
    712
    hierarchy:
    Kragerøvassdraget
    lakeArea:
    0
    lakeName:
    not reported by source
    lakeNo:
    27509
    regineNo:
    017.D21
    reservoirNo:
    332
    reservoirName:
    TOKEVATN
    stationTypeName:
    Privat, pålagt
    stationStatusName:
    Aktiv
    drainageBasinArea:
    1137.56
    drainageBasinAreaNorway:
    1137.56
    gradient1085:
    3.01
    gradientBasin:
    25.45
    gradientRiver:
    6.92
    heightMinimum:
    58
    heightHypso10:
    150
    heightHypso20:
    185
    heightHypso30:
    259
    heightHypso40:
    303
    heightHypso50:
    401
    heightHypso60:
    442
    heightHypso70:
    576
    heightHypso80:
    616
    heightHypso90:
    715
    heightMaximum:
    911
    lengthKmBasin:
    52.36
    lengthKmRiver:
    74.98
    percentAgricul:
    1.15
    percentBog:
    3.02
    percentEffBog:
    not reported by source
    percentEffLake:
    2.19
    percentForest:
    82.29
    percentGlacier:
    0
    percentLake:
    7
    percentMountain:
    2.97
    percentUrban:
    0.1
    utmZoneGravi:
    33
    utmEastGravi:
    153806
    utmNorthGravi:
    6567494
    utmZoneInlet:
    33
    utmEastInlet:
    134813
    utmNorthInlet:
    6590091
    utmZoneOutlet:
    not reported by source
    utmEastOutlet:
    not reported by source
    utmNorthOutlet:
    not reported by source
    annualRunoff:
    959.02
    specificDischarge:
    26.72
    regulationArea:
    1156.87
    areaReservoirs:
    38.24
    volumeReservoirs:
    175
    regulationPartReservoirs:
    0.18
    transferAreaIn:
    0
    transferAreaOut:
    0
    reservoirAreaIn:
    0
    reservoirAreaOut:
    32.41
    reservoirVolumeIn:
    0
    reservoirVolumeOut:
    150
    remainingArea:
    -19.34
    numberReservoirs:
    5
    firstYearRegulation:
    2004
    catchmentRegTypeName:
    regulert m/magasinregulering
    owner:
    SKAGERAK KRAFT AS
    qNumberOfYears:
    16
    qStartYear:
    2004
    qEndYear:
    2025
    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:
    60.0857
    h5:
    60.3444
    h10:
    60.3613
    h20:
    60.3669
    h50:
    60.3692
    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:
    60.0857
    culH5:
    60.3444
    culH10:
    60.3613
    culH20:
    60.3669
    culH50:
    60.3692
    seriesList:

    1 results

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

      3 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        1989-01-01T11:00:00Z
        dataToTime:
        2026-09-22T13:00:00Z
      2. resTime:
        60
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2005-01-01T00:00:00Z
        dataToTime:
        2026-09-22T13:00:00Z
      3. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        1989-01-01T11:00:00Z
        dataToTime:
        2026-09-21T11: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.