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-20T23:31:13Z in 0.162 seconds.

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

Showing 1 of 1 results in compact format.

station_id:
81.1.0
latitude:
61.1352
longitude:
4.93712

Show all fields in HTML

currentLink:

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

apiVersion:

1.0

license:

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

createdAt:

2026-09-20T23:31:13.9180294Z

queryTime:

00:00:00.0007918

itemCount:

data:

1 results

Open the place page for this point
station_id:
81.1.0
stationName:
Hersvikvatn (Hagevatnet)
latitude:
61.1352
longitude:
4.93712
utmEast_Z33:
-40448
utmNorth_Z33:
6819567
masl:
27
riverName:
Hageelva
councilNumber:
4636
councilName:
Solund
countyName:
Vestland
drainageBasinKey:
1393
hierarchy:
Hageelva
lakeArea:
0
lakeName:
not reported by source
lakeNo:
2536
regineNo:
081.9B
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Forvaltningsstasjon
stationStatusName:
Aktiv
drainageBasinArea:
7.13
drainageBasinAreaNorway:
7.13
gradient1085:
0
gradientBasin:
28.57
gradientRiver:
13.2
heightMinimum:
19
heightHypso10:
22
heightHypso20:
22
heightHypso30:
50
heightHypso40:
63
heightHypso50:
71
heightHypso60:
88
heightHypso70:
126
heightHypso80:
241
heightHypso90:
327
heightMaximum:
455
lengthKmBasin:
4.95
lengthKmRiver:
3.11
percentAgricul:
0
percentBog:
1.66
percentEffBog:
not reported by source
percentEffLake:
19.42
percentForest:
10.51
percentGlacier:
0
percentLake:
20.06
percentMountain:
12.41
percentUrban:
0
utmZoneGravi:
33
utmEastGravi:
-40864
utmNorthGravi:
6820899
utmZoneInlet:
33
utmEastInlet:
-40900
utmNorthInlet:
6824223
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
13.53
specificDischarge:
60.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:
92
qStartYear:
1934
qEndYear:
2025
qm:
1.8625
q5:
2.1684
q10:
2.3412
q20:
2.4822
q50:
2.6347
hm:
1.3655
h5:
1.4389
h10:
1.4782
h20:
1.5094
h50:
1.5422
culQm:
1.9749
culQ5:
2.2994
culQ10:
2.4825
culQ20:
2.6321
culQ50:
2.7938
culHm:
1.3931
culH5:
1.4688
culH10:
1.5095
culH20:
1.5416
culH50:
1.5755
seriesList:
4 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  1
  unit:
  m
  serieFrom:
  1934-01-01T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  1934-01-01T11:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1976-08-14T12:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1934-01-01T11:00:00Z
  dataToTime:
  2026-09-20T11: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:
  1934-01-01T11:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1976-08-14T12:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  1934-01-01T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
3. parameterName:
  Vanntemperatur
  parameter:
  1003
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2023-11-24T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2024-12-19T21:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  60
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2024-12-19T21:00:00Z
  dataToTime:
  2026-09-20T23:00:00Z
  resTime:
  1440
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2024-12-20T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
4. parameterName:
  Lufttemperatur
  parameter:
  17
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2005-05-03T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2005-05-03T09:00:00Z
  dataToTime:
  2026-09-20T22:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2005-05-03T10:00:00Z
  dataToTime:
  2026-09-20T22:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2005-05-04T11:00:00Z
  dataToTime:
  2026-09-20T11: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.