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-22T16:25:30Z in 0.144 seconds.

Search scope: Municipality-filtered results cover all of Holtålen municipality.

Showing 1 of 1 results in compact format.

station_id:
122.11.0
latitude:
62.89011
longitude:
11.18388

Show all fields in HTML

currentLink:

https://hydapi.nve.no/api/v1/Stations?CouncilName=Holt%C3%A5len&Active=OnlyActive

apiVersion:

1.0

license:

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

createdAt:

2026-09-22T16:25:30.2790634Z

queryTime:

00:00:00.0008976

itemCount:

data:

1 results

Open the place page for this point
station_id:
122.11.0
stationName:
Eggafoss
latitude:
62.89011
longitude:
11.18388
utmEast_Z33:
306061
utmNorth_Z33:
6979097
masl:
295
riverName:
Gaula
councilNumber:
5026
councilName:
Holtålen
countyName:
Trøndelag
drainageBasinKey:
1661
hierarchy:
Gaula
lakeArea:
0
lakeName:
not reported by source
lakeNo:
0
regineNo:
122.F0
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Forvaltningsstasjon
stationStatusName:
Aktiv
drainageBasinArea:
655.18
drainageBasinAreaNorway:
655.18
gradient1085:
15.12
gradientBasin:
28.58
gradientRiver:
14.59
heightMinimum:
278
heightHypso10:
648
heightHypso20:
742
heightHypso30:
796
heightHypso40:
832
heightHypso50:
869
heightHypso60:
905
heightHypso70:
946
heightHypso80:
999
heightHypso90:
1046
heightMaximum:
1287
lengthKmBasin:
32.97
lengthKmRiver:
45.16
percentAgricul:
1.88
percentBog:
14.35
percentEffBog:
not reported by source
percentEffLake:
0.15
percentForest:
27.16
percentGlacier:
0
percentLake:
3.22
percentMountain:
41.78
percentUrban:
0.03
utmZoneGravi:
33
utmEastGravi:
312226
utmNorthGravi:
6967914
utmZoneInlet:
33
utmEastInlet:
335605
utmNorthInlet:
6964587
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
529.91
specificDischarge:
25.63
regulationArea:
199.11
areaReservoirs:
2.92
volumeReservoirs:
0
regulationPartReservoirs:
0
transferAreaIn:
0
transferAreaOut:
0
reservoirAreaIn:
0
reservoirAreaOut:
0
reservoirVolumeIn:
0
reservoirVolumeOut:
0
remainingArea:
456.07
numberReservoirs:
5
firstYearRegulation:
2009
catchmentRegTypeName:
regulert m/magasinregulering
owner:
HH. Hydrologisk avd./Hydrometri
qNumberOfYears:
not reported by source
qStartYear:
not reported by source
qEndYear:
not reported by source
qm:
192.07
q5:
236.24
q10:
266.84
q20:
300.32
q50:
344.27
hm:
3.36
h5:
3.51
h10:
3.6
h20:
3.7
h50:
3.81
culQm:
220.82
culQ5:
272.69
culQ10:
307.27
culQ20:
346.73
culQ50:
397.47
culHm:
3.46
culH5:
3.62
culH10:
3.71
culH20:
3.82
culH50:
3.94
seriesList:
4 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  1
  unit:
  m
  serieFrom:
  1941-04-05T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1941-04-01T11:00:00Z
  dataToTime:
  2026-09-22T15:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1965-04-26T19:00:00Z
  dataToTime:
  2026-09-22T15:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1941-04-01T11: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:
  1941-04-05T11:00:00Z
  dataToTime:
  2026-09-22T15:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1965-04-26T19:00:00Z
  dataToTime:
  2026-09-22T15:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1941-04-05T11:00:00Z
  dataToTime:
  2026-09-21T11:00:00Z
3. parameterName:
  Vanntemperatur
  parameter:
  1003
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2011-09-01T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2014-05-09T23:00:00Z
  dataToTime:
  2026-09-22T15:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2014-05-10T00:00:00Z
  dataToTime:
  2026-09-22T15:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2014-05-10T11:00:00Z
  dataToTime:
  2026-09-21T11:00:00Z
4. parameterName:
  Lufttemperatur
  parameter:
  17
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2007-08-27T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2007-08-27T16:00:00Z
  dataToTime:
  2026-09-22T15:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2007-08-27T17:00:00Z
  dataToTime:
  2026-09-22T15:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2007-08-28T11: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.