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.

Parameter	Requirement	JSON type	Description
`municipality`	optional	union	Municipality name (HydAPI field CouncilName).
`county`	optional	union	County name.
`station_name`	optional	union	Station name filter.
`active_only`	optional	boolean	Return only active stations by default.
`limit`	optional	integer	Maximum stations returned (default 25, maximum 100). Unit: items.
`offset`	optional	integer	Number 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.

Result

Source: NVE HydAPI. Retrieved 2026-09-22T09:55:46Z in 0.142 seconds.

Search scope: Municipality-filtered results cover all of KARLSØY municipality.

Showing 1 of 1 results in compact format.

station_id:
200.4.0
latitude:
69.98093
longitude:
19.10412

Show all fields in HTML

currentLink:

https://hydapi.nve.no/api/v1/Stations?CouncilName=KARLS%C3%98Y&Active=OnlyActive

apiVersion:

1.0

license:

https://data.norge.no/nlod/en

createdAt:

2026-09-22T09:55:46.6292189Z

queryTime:

00:00:00.0013837

itemCount:

data:

1 results

Open the place page for this point
station_id:
200.4.0
stationName:
Skogsfjordvatn
latitude:
69.98093
longitude:
19.10412
utmEast_Z33:
656700
utmNorth_Z33:
7769022
masl:
20
riverName:
Skogsfjordelva
councilNumber:
5534
councilName:
Karlsøy
countyName:
Troms
drainageBasinKey:
2101
hierarchy:
Skogsfjordelva
lakeArea:
0
lakeName:
not reported by source
lakeNo:
1713
regineNo:
200.6B
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Forvaltningsstasjon
stationStatusName:
Aktiv
drainageBasinArea:
136.01
drainageBasinAreaNorway:
136.01
gradient1085:
28.11
gradientBasin:
26.84
gradientRiver:
21.53
heightMinimum:
18
heightHypso10:
18
heightHypso20:
100
heightHypso30:
160
heightHypso40:
228
heightHypso50:
286
heightHypso60:
311
heightHypso70:
428
heightHypso80:
481
heightHypso90:
616
heightMaximum:
1045
lengthKmBasin:
17.17
lengthKmRiver:
20.02
percentAgricul:
0.46
percentBog:
1.63
percentEffBog:
not reported by source
percentEffLake:
10.09
percentForest:
22.37
percentGlacier:
0.08
percentLake:
15.02
percentMountain:
48.76
percentUrban:
0
utmZoneGravi:
33
utmEastGravi:
659687
utmNorthGravi:
7763394
utmZoneInlet:
33
utmEastInlet:
660738
utmNorthInlet:
7755119
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
217.67
specificDischarge:
50.73
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:
64
qStartYear:
1958
qEndYear:
2021
qm:
41.1711
q5:
51.9328
q10:
60.6513
q20:
69.0005
q50:
79.7877
hm:
2.2133
h5:
2.3552
h10:
2.4597
h20:
2.5531
h50:
2.6658
culQm:
42.9374
culQ5:
54.1608
culQ10:
63.2533
culQ20:
71.9607
culQ50:
83.2107
culHm:
2.2377
culH5:
2.3827
culH10:
2.4895
culH20:
2.5849
culH50:
2.7
seriesList:
3 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  1
  unit:
  m
  serieFrom:
  1988-09-18T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1988-09-18T11:00:00Z
  dataToTime:
  2026-09-22T09:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1989-10-20T11:00:00Z
  dataToTime:
  2026-09-22T09:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1988-09-18T11:00:00Z
  dataToTime:
  2026-09-21T11: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
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1988-09-18T11:00:00Z
  dataToTime:
  2026-09-22T09:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1989-10-20T11:00:00Z
  dataToTime:
  2026-09-22T09:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1988-09-18T11:00:00Z
  dataToTime:
  2026-09-21T11:00:00Z
3. parameterName:
  Lufttemperatur
  parameter:
  17
  versionNo:
  2
  unit:
  °C
  serieFrom:
  2003-06-01T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2003-09-17T14:00:00Z
  dataToTime:
  2026-09-22T09:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2003-09-17T15:00:00Z
  dataToTime:
  2026-09-22T09:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2003-09-18T11:00:00Z
  dataToTime:
  2026-09-21T11:00:00Z

limit:

offset:

returned:

has_more_results:

truncated:

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

Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
Check types, units, limits and ID formats in the parameter table.
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

Check parameter ID, unit, resolution and quality codes before interpreting observations.

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.