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-21T21:54:08Z in 0.137 seconds.

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

Showing 1 of 1 results in compact format.

station_id:
12.70.0
latitude:
60.95266
longitude:
9.62473

Show all fields in HTML

currentLink:

https://hydapi.nve.no/api/v1/Stations?CouncilName=ETNEDAL&Active=OnlyActive

apiVersion:

1.0

license:

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

createdAt:

2026-09-21T21:54:08.3316675Z

queryTime:

00:00:00.0016317

itemCount:

data:

1 results

Open the place page for this point
station_id:
12.70.0
stationName:
Etna
latitude:
60.95266
longitude:
9.62473
utmEast_Z33:
209068
utmNorth_Z33:
6769458
masl:
403
riverName:
Randselva
councilNumber:
3450
councilName:
Etnedal
countyName:
Innlandet
drainageBasinKey:
426
hierarchy:
Randselva/Drammensvassdraget
lakeArea:
0
lakeName:
not reported by source
lakeNo:
0
regineNo:
012.EF61
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Privat, pålagt
stationStatusName:
Aktiv
drainageBasinArea:
568.53
drainageBasinAreaNorway:
568.53
gradient1085:
11.54
gradientBasin:
13.65
gradientRiver:
12.29
heightMinimum:
397
heightHypso10:
797
heightHypso20:
873
heightHypso30:
900
heightHypso40:
937
heightHypso50:
963
heightHypso60:
999
heightHypso70:
1040
heightHypso80:
1061
heightHypso90:
1097
heightMaximum:
1681
lengthKmBasin:
46.33
lengthKmRiver:
61.34
percentAgricul:
1.44
percentBog:
17.84
percentEffBog:
not reported by source
percentEffLake:
0.3
percentForest:
49.28
percentGlacier:
0
percentLake:
4.66
percentMountain:
12.02
percentUrban:
0
utmZoneGravi:
33
utmEastGravi:
202563
utmNorthGravi:
6787226
utmZoneInlet:
33
utmEastInlet:
192337
utmNorthInlet:
6811908
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
228.61
specificDischarge:
12.74
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:
HAFSLUND KRAFT INNLANDET AS
qNumberOfYears:
57
qStartYear:
1969
qEndYear:
2025
qm:
106.002
q5:
136.6475
q10:
158.0776
q20:
177.332
q50:
200.492
hm:
3.4671
h5:
3.7517
h10:
3.9269
h20:
4.0718
h50:
4.2333
culQm:
114.5581
culQ5:
147.6773
culQ10:
170.8371
culQ20:
191.6457
culQ50:
216.6751
culHm:
3.5513
culH5:
3.8439
culH10:
4.0241
culH20:
4.1731
culH50:
4.3391
seriesList:
3 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  1
  unit:
  m
  serieFrom:
  1919-05-10T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1919-05-10T11:00:00Z
  dataToTime:
  2026-09-21T21:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1983-04-13T14:00:00Z
  dataToTime:
  2026-09-21T21:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1919-05-10T11: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:
  1919-05-10T11:00:00Z
  dataToTime:
  2026-09-21T21:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1983-04-13T14:00:00Z
  dataToTime:
  2026-09-21T21:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1919-05-10T11:00:00Z
  dataToTime:
  2026-09-21T11:00:00Z
3. parameterName:
  Lufttemperatur
  parameter:
  17
  versionNo:
  2
  unit:
  °C
  serieFrom:
  2011-09-22T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2011-10-25T19:00:00Z
  dataToTime:
  2026-09-21T21:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2011-10-25T20:00:00Z
  dataToTime:
  2026-09-21T21:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2011-10-26T11: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.