search_stations

Find NVE hydrological stations and their available time series.

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).
offsetoptionalintegerNumber of matching stations to skip (default 0).
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": "..."}
}
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).
Type: integer. Number of matching stations to skip (default 0).

Result

Source: NVE HydAPI. Retrieved 2026-08-03T00:48:40Z in 0.143 seconds.

Search scope: Municipality-filtered results cover all of TYSVÆR municipality.

Showing 1 of 1 results in compact format.

  1. latitude:
    59.32949
    longitude:
    5.44324
Show all fields in HTML
currentLink:
https://hydapi.nve.no/api/v1/Stations?CouncilName=TYSV%C3%86R&Active=OnlyActive
apiVersion:
1.0
license:
https://data.norge.no/nlod/en
createdAt:
2026-08-03T00:48:40.1797837Z
queryTime:
00:00:00.0016512
itemCount:
1
data:

1 results

  1. stationId:
    39.1.0
    stationName:
    Tysvær
    latitude:
    59.32949
    longitude:
    5.44324
    utmEast_Z33:
    -42586
    utmNorth_Z33:
    6615801
    masl:
    9
    riverName:
    KYSTFELT
    councilNumber:
    1146
    councilName:
    Tysvær
    countyName:
    Rogaland
    drainageBasinKey:
    1054
    hierarchy:
    Kyst Nedstrand-Haugesund-Tittelsnes
    lakeArea:
    0
    lakeName:
    not reported by source
    lakeNo:
    0
    regineNo:
    039.52
    reservoirNo:
    not reported by source
    reservoirName:
    not reported by source
    stationTypeName:
    Forvaltningsstasjon
    stationStatusName:
    Aktiv
    drainageBasinArea:
    3.34
    drainageBasinAreaNorway:
    3.345
    gradient1085:
    4.77
    gradientBasin:
    3.75
    gradientRiver:
    6.61
    heightMinimum:
    10
    heightHypso10:
    25
    heightHypso20:
    29
    heightHypso30:
    31
    heightHypso40:
    31
    heightHypso50:
    35
    heightHypso60:
    34
    heightHypso70:
    36
    heightHypso80:
    42
    heightHypso90:
    47
    heightMaximum:
    65
    lengthKmBasin:
    3.24
    lengthKmRiver:
    3.63
    percentAgricul:
    0.16
    percentBog:
    15.17
    percentEffBog:
    not reported by source
    percentEffLake:
    15.72
    percentForest:
    6.65
    percentGlacier:
    0
    percentLake:
    18.2
    percentMountain:
    0
    percentUrban:
    0
    utmZoneGravi:
    33
    utmEastGravi:
    -43641
    utmNorthGravi:
    6613581
    utmZoneInlet:
    33
    utmEastInlet:
    -44774
    utmNorthInlet:
    6614071
    utmZoneOutlet:
    not reported by source
    utmEastOutlet:
    not reported by source
    utmNorthOutlet:
    not reported by source
    annualRunoff:
    4.39
    specificDischarge:
    41.65
    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:
    50
    qStartYear:
    1975
    qEndYear:
    2024
    qm:
    0.6549
    q5:
    0.7832
    q10:
    0.8503
    q20:
    0.9033
    q50:
    0.9584
    hm:
    0.5286
    h5:
    0.5523
    h10:
    0.564
    h20:
    0.5728
    h50:
    0.5818
    culQm:
    0.7219
    culQ5:
    0.8633
    culQ10:
    0.9373
    culQ20:
    0.9957
    culQ50:
    1.0564
    culHm:
    0.5413
    culH5:
    0.5662
    culH10:
    0.5784
    culH20:
    0.5878
    culH50:
    0.5972
    seriesList:

    4 results

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

      3 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        1974-12-04T11:00:00Z
        dataToTime:
        2026-08-03T00:00:00Z
      2. resTime:
        60
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        1974-12-04T15:00:00Z
        dataToTime:
        2026-08-03T00:00:00Z
      3. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        1974-12-04T11:00:00Z
        dataToTime:
        2026-08-02T11: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:
        1974-12-04T11:00:00Z
        dataToTime:
        2026-08-03T00:00:00Z
      2. resTime:
        60
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        1974-12-04T15:00:00Z
        dataToTime:
        2026-08-03T00:00:00Z
      3. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        1974-12-04T11:00:00Z
        dataToTime:
        2026-08-02T11:00:00Z
    3. parameterName:
      Vanntemperatur
      parameter:
      1003
      versionNo:
      1
      unit:
      °C
      serieFrom:
      2017-04-05T00:00:00
      serieTo:
      not reported by source
      resolutionList:

      3 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        2017-04-05T12:15:00Z
        dataToTime:
        2026-08-03T00:00:00Z
      2. resTime:
        60
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2017-04-05T13:00:00Z
        dataToTime:
        2026-08-03T00:00:00Z
      3. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2017-04-06T11:00:00Z
        dataToTime:
        2026-08-02T11:00:00Z
    4. parameterName:
      Lufttemperatur
      parameter:
      17
      versionNo:
      1
      unit:
      °C
      serieFrom:
      2003-06-01T00:00:00
      serieTo:
      not reported by source
      resolutionList:

      3 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        2003-10-26T18:00:00Z
        dataToTime:
        2026-08-03T00:00:00Z
      2. resTime:
        60
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2003-10-26T19:00:00Z
        dataToTime:
        2026-08-03T00:00:00Z
      3. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2003-10-27T11:00:00Z
        dataToTime:
        2026-08-02T11: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

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.