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-20T22:04:18Z in 0.201 seconds.

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

Showing 1 of 1 results in compact format.

station_id:
80.5.0
latitude:
61.16023
longitude:
5.38471

Show all fields in HTML

currentLink:

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

apiVersion:

1.0

license:

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

createdAt:

2026-09-20T22:04:18.6741601Z

queryTime:

00:00:00.0013251

itemCount:

data:

1 results

Open the place page for this point
station_id:
80.5.0
stationName:
Espelandsvatn
latitude:
61.16023
longitude:
5.38471
utmEast_Z33:
-16123
utmNorth_Z33:
6818702
masl:
87
riverName:
Lølandselva
councilNumber:
4637
councilName:
Hyllestad
countyName:
Vestland
drainageBasinKey:
1384
hierarchy:
Lølandselva
lakeArea:
1.24
lakeName:
Espelandsvatnet
lakeNo:
1625
regineNo:
080.4C
reservoirNo:
490
reservoirName:
ESPELANDSVATN
stationTypeName:
Privat, pålagt
stationStatusName:
Aktiv
drainageBasinArea:
89.61
drainageBasinAreaNorway:
89.61
gradient1085:
73.23
gradientBasin:
29.05
gradientRiver:
72.16
heightMinimum:
83
heightHypso10:
212
heightHypso20:
264
heightHypso30:
302
heightHypso40:
356
heightHypso50:
415
heightHypso60:
465
heightHypso70:
527
heightHypso80:
575
heightHypso90:
630
heightMaximum:
754
lengthKmBasin:
11.63
lengthKmRiver:
1.86
percentAgricul:
4.05
percentBog:
4.02
percentEffBog:
not reported by source
percentEffLake:
3.41
percentForest:
43.88
percentGlacier:
0
percentLake:
8.52
percentMountain:
30.83
percentUrban:
0
utmZoneGravi:
33
utmEastGravi:
-11241
utmNorthGravi:
6819046
utmZoneInlet:
33
utmEastInlet:
-10118
utmNorthInlet:
6822270
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
259.02
specificDischarge:
91.79
regulationArea:
66
areaReservoirs:
3.56
volumeReservoirs:
35.6
regulationPartReservoirs:
0.14
transferAreaIn:
23.4
transferAreaOut:
41.18
reservoirAreaIn:
0
reservoirAreaOut:
3.56
reservoirVolumeIn:
0
reservoirVolumeOut:
35.6
remainingArea:
0
numberReservoirs:
2
firstYearRegulation:
1941
catchmentRegTypeName:
Regulert m/magasinregulering og overføringer
owner:
EVINY FORNYBAR 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:
2 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  50
  unit:
  m
  serieFrom:
  1995-01-01T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1995-01-01T11:00:00Z
  dataToTime:
  2026-06-19T22:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2011-01-01T00:00:00Z
  dataToTime:
  2026-06-19T22:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1995-01-01T11:00:00Z
  dataToTime:
  2026-06-19T11:00:00Z
2. parameterName:
  Magasinvolum
  parameter:
  1004
  versionNo:
  50
  unit:
  millioner m³
  serieFrom:
  not reported by source
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1995-01-01T11:00:00Z
  dataToTime:
  2026-06-19T22:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2011-01-01T00:00:00Z
  dataToTime:
  2026-06-19T22:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1995-01-01T11:00:00Z
  dataToTime:
  2026-06-19T11: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.