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-22T19:13:36Z in 0.184 seconds.

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

Showing 1 of 1 results in compact format.

  1. station_id:
    242.1.0
    latitude:
    70.00508
    longitude:
    29.08463
Show all fields in HTML
currentLink:
https://hydapi.nve.no/api/v1/Stations?CouncilName=Nesseby&Active=OnlyActive
apiVersion:
1.0
license:
https://data.norge.no/nlod/en
createdAt:
2026-09-22T19:13:36.3815486Z
queryTime:
00:00:00.0011803
itemCount:
1
data:

1 results

  1. station_id:
    242.1.0
    stationName:
    Fuglevatn
    latitude:
    70.00508
    longitude:
    29.08463
    utmEast_Z33:
    1033334
    utmNorth_Z33:
    7828427
    masl:
    189
    riverName:
    Duddajåkka
    councilNumber:
    5636
    councilName:
    Nesseby
    countyName:
    Finnmark
    drainageBasinKey:
    2205
    hierarchy:
    Duddajåkka
    lakeArea:
    2.74
    lakeName:
    Fuglevatnet
    lakeNo:
    2426
    regineNo:
    242.4B
    reservoirNo:
    755
    reservoirName:
    FUGLEVATN
    stationTypeName:
    Privat, pålagt
    stationStatusName:
    Aktiv
    drainageBasinArea:
    39.97
    drainageBasinAreaNorway:
    39.97
    gradient1085:
    12.59
    gradientBasin:
    22.88
    gradientRiver:
    11.61
    heightMinimum:
    186
    heightHypso10:
    253
    heightHypso20:
    290
    heightHypso30:
    294
    heightHypso40:
    307
    heightHypso50:
    321
    heightHypso60:
    338
    heightHypso70:
    343
    heightHypso80:
    361
    heightHypso90:
    379
    heightMaximum:
    408
    lengthKmBasin:
    12.91
    lengthKmRiver:
    15.25
    percentAgricul:
    0
    percentBog:
    1.69
    percentEffBog:
    not reported by source
    percentEffLake:
    7.25
    percentForest:
    5.47
    percentGlacier:
    0
    percentLake:
    13.71
    percentMountain:
    77.51
    percentUrban:
    0
    utmZoneGravi:
    33
    utmEastGravi:
    0
    utmNorthGravi:
    7823913
    utmZoneInlet:
    33
    utmEastInlet:
    0
    utmNorthInlet:
    7815645
    utmZoneOutlet:
    not reported by source
    utmEastOutlet:
    not reported by source
    utmNorthOutlet:
    not reported by source
    annualRunoff:
    16.04
    specificDischarge:
    12.78
    regulationArea:
    39.78
    areaReservoirs:
    2.74
    volumeReservoirs:
    14.5
    regulationPartReservoirs:
    0.9
    transferAreaIn:
    63.77
    transferAreaOut:
    0
    reservoirAreaIn:
    11.27
    reservoirAreaOut:
    0
    reservoirVolumeIn:
    36.2
    reservoirVolumeOut:
    0
    remainingArea:
    0
    numberReservoirs:
    1
    firstYearRegulation:
    1952
    catchmentRegTypeName:
    Regulert m/magasinregulering og overføringer
    owner:
    PASVIK 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:

    1 results

    1. parameterName:
      Vannstand
      parameter:
      1000
      versionNo:
      2
      unit:
      m
      serieFrom:
      2010-09-19T00:00:00
      serieTo:
      not reported by source
      resolutionList:

      3 results

      1. resTime:
        0
        method:
        Instantaneous
        timeOffset:
        0
        dataFromTime:
        2010-09-19T09:00:00Z
        dataToTime:
        2025-12-01T12:00:00Z
      2. resTime:
        60
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2010-09-19T10:00:00Z
        dataToTime:
        2025-12-01T12:00:00Z
      3. resTime:
        1440
        method:
        Mean
        timeOffset:
        0
        dataFromTime:
        2010-09-20T11:00:00Z
        dataToTime:
        2025-11-30T11: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.