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-20T19:39:49Z in 0.141 seconds.

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

Showing 1 of 1 results in compact format.

station_id:
39.2.0
latitude:
59.47989
longitude:
5.30568

Show all fields in HTML

currentLink:

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

apiVersion:

1.0

license:

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

createdAt:

2026-09-20T19:39:49.3765637Z

queryTime:

00:00:00.0010339

itemCount:

data:

1 results

Open the place page for this point
station_id:
39.2.0
stationName:
Kallandsvatnet
latitude:
59.47989
longitude:
5.30568
utmEast_Z33:
-47914
utmNorth_Z33:
6633565
masl:
17
riverName:
KYSTFELT
councilNumber:
1106
councilName:
Haugesund
countyName:
Rogaland
drainageBasinKey:
2278
hierarchy:
Kyst Nedstrand-Haugesund-Tittelsnes
lakeArea:
0
lakeName:
not reported by source
lakeNo:
0
regineNo:
039.80
reservoirNo:
not reported by source
reservoirName:
not reported by source
stationTypeName:
Forvaltningsstasjon
stationStatusName:
Aktiv
drainageBasinArea:
7.68
drainageBasinAreaNorway:
7.68
gradient1085:
16.75
gradientBasin:
not reported by source
gradientRiver:
35.81
heightMinimum:
10
heightHypso10:
24
heightHypso20:
39
heightHypso30:
54
heightHypso40:
57
heightHypso50:
74
heightHypso60:
68
heightHypso70:
78
heightHypso80:
97
heightHypso90:
145
heightMaximum:
241
lengthKmBasin:
4.93
lengthKmRiver:
5.33
percentAgricul:
1.77
percentBog:
9.58
percentEffBog:
not reported by source
percentEffLake:
8.09
percentForest:
33.48
percentGlacier:
0
percentLake:
13.93
percentMountain:
1.05
percentUrban:
0
utmZoneGravi:
not reported by source
utmEastGravi:
not reported by source
utmNorthGravi:
not reported by source
utmZoneInlet:
not reported by source
utmEastInlet:
not reported by source
utmNorthInlet:
not reported by source
utmZoneOutlet:
not reported by source
utmEastOutlet:
not reported by source
utmNorthOutlet:
not reported by source
annualRunoff:
10.05
specificDischarge:
41.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:
HH. Hydrologisk avd./Hydrometri
qNumberOfYears:
20
qStartYear:
2005
qEndYear:
2025
qm:
1.4976
q5:
1.6334
q10:
1.8759
q20:
2.1824
q50:
2.7248
hm:
1.395
h5:
1.4191
h10:
1.4606
h20:
1.5105
h50:
1.5936
culQm:
1.5551
culQ5:
1.6961
culQ10:
1.9479
culQ20:
2.2662
culQ50:
2.8294
culHm:
1.4053
culH5:
1.43
culH10:
1.4725
culH20:
1.5238
culH50:
1.609
seriesList:
4 results
1. parameterName:
  Vannstand
  parameter:
  1000
  versionNo:
  1
  unit:
  m
  serieFrom:
  2005-04-06T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2005-05-18T23:15:00Z
  dataToTime:
  2026-09-20T19:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2005-05-19T00:00:00Z
  dataToTime:
  2026-09-20T19:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2005-05-19T11: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:
  2021-12-31T23:00:00Z
  dataToTime:
  2026-09-20T19:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2005-05-19T00:00:00Z
  dataToTime:
  2026-09-20T19:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2005-05-19T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
3. parameterName:
  Vanntemperatur
  parameter:
  1003
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2015-05-04T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2015-05-04T09:00:00Z
  dataToTime:
  2026-09-20T19:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2015-05-04T10:00:00Z
  dataToTime:
  2026-09-20T19:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2015-05-05T11:00:00Z
  dataToTime:
  2026-09-20T11:00:00Z
4. parameterName:
  Lufttemperatur
  parameter:
  17
  versionNo:
  1
  unit:
  °C
  serieFrom:
  2005-04-06T00:00:00
  serieTo:
  not reported by source
  resolutionList:
  3 results
  resTime:
  0
  method:
  Instantaneous
  timeOffset:
  0
  dataFromTime:
  2005-05-24T00:00:00Z
  dataToTime:
  2026-09-20T19:00:00Z
  resTime:
  60
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2005-05-24T01:00:00Z
  dataToTime:
  2026-09-20T19:00:00Z
  resTime:
  1440
  method:
  Mean
  timeOffset:
  0
  dataFromTime:
  2005-05-24T11: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.