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-20T20:12:31Z in 0.197 seconds.

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

Showing 1 of 1 results in compact format.

station_id:
82.4.0
latitude:
61.2529
longitude:
5.38535

Show all fields in HTML

currentLink:

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

apiVersion:

1.0

license:

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

createdAt:

2026-09-20T20:12:31.2691218Z

queryTime:

00:00:00.0009208

itemCount:

data:

1 results

Open the place page for this point
station_id:
82.4.0
stationName:
Nautsundvatn
latitude:
61.2529
longitude:
5.38535
utmEast_Z33:
-14569
utmNorth_Z33:
6828940
masl:
48
riverName:
Guddalsvassdraget
councilNumber:
4646
councilName:
Fjaler
countyName:
Vestland
drainageBasinKey:
1396
hierarchy:
Guddalsvassdraget
lakeArea:
0
lakeName:
not reported by source
lakeNo:
28684
regineNo:
082.B4
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Forvaltningsstasjon
stationStatusName:
Aktiv
drainageBasinArea:
218.96
drainageBasinAreaNorway:
218.959
gradient1085:
16.5
gradientBasin:
34.4
gradientRiver:
22.24
heightMinimum:
40
heightHypso10:
172
heightHypso20:
302
heightHypso30:
398
heightHypso40:
449
heightHypso50:
510
heightHypso60:
577
heightHypso70:
614
heightHypso80:
644
heightHypso90:
712
heightMaximum:
906
lengthKmBasin:
22.62
lengthKmRiver:
30.62
percentAgricul:
1.86
percentBog:
2.18
percentEffBog:
not reported by source
percentEffLake:
2.15
percentForest:
43.39
percentGlacier:
0
percentLake:
7.78
percentMountain:
37.65
percentUrban:
0
utmZoneGravi:
33
utmEastGravi:
-4628
utmNorthGravi:
6826562
utmZoneInlet:
33
utmEastInlet:
6691
utmNorthInlet:
6826122
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
665.73
specificDischarge:
96.42
regulationArea:
0
areaReservoirs:
0
volumeReservoirs:
0
regulationPartReservoirs:
0
transferAreaIn:
27.45
transferAreaOut:
0
reservoirAreaIn:
0
reservoirAreaOut:
0
reservoirVolumeIn:
0
reservoirVolumeOut:
0
remainingArea:
0
numberReservoirs:
0
firstYearRegulation:
2020
catchmentRegTypeName:
Uregulert
owner:
HH. Hydrologisk avd./Hydrometri
qNumberOfYears:
117
qStartYear:
1909
qEndYear:
2025
qm:
177.6151
q5:
218.9485
q10:
245.7476
q20:
269.0334
q50:
296.0136
hm:
3.7854
h5:
4.1113
h10:
4.3109
h20:
4.4781
h50:
4.6654
culQm:
217.2396
culQ5:
267.7941
culQ10:
300.5719
culQ20:
329.0526
culQ50:
362.0518
culHm:
4.0983
culH5:
4.4693
culH10:
4.6965
culH20:
4.8868
culH50:
5.1
seriesList:
4 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  2
  unit:
  m
  serieFrom:
  2004-10-07T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2004-11-01T11:00:00Z
  dataToTime:
  2026-09-20T19:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2004-11-02T07:00:00Z
  dataToTime:
  2026-09-20T19:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2004-11-01T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
2. parameterName:
  Vannføring
  parameter:
  1001
  versionNo:
  2
  unit:
  m³/s
  serieFrom:
  not reported by source
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2004-11-01T11:00:00Z
  dataToTime:
  2026-09-20T19:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2004-11-02T07:00:00Z
  dataToTime:
  2026-09-20T19:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2004-11-01T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
3. parameterName:
  Vanntemperatur
  parameter:
  1003
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2024-02-28T00: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-20T19:00:00Z
  resTime:
  60
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2024-12-19T21:00:00Z
  dataToTime:
  2026-09-20T19: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:
  2
  unit:
  °C
  serieFrom:
  2004-10-07T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2004-11-02T07:00:00Z
  dataToTime:
  2026-09-20T19:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2004-11-02T08:00:00Z
  dataToTime:
  2026-09-20T19:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2004-11-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.