find_traffic_points

Find traffic registration points (trafikkregistreringspunkt) - the physical counting stations on Norwegian roads that this server's other traffic tools read from. Search by name, spatially around a coordinate, or both; all filters combine.

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.

https://allemannsdata.com/wiki/kilder/vegvesen/find_traffic_points/?query={query}&county_number={county_number}&road_category={road_category}&lat={lat}&lon={lon}&radius_km=50&operational_only=true&limit=20&offset=0

Replace {query}, {county_number}, {road_category}, {lat}, {lon}, {radius_km}, {operational_only}, {limit} 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/vegvesen/find_traffic_points?query={query}&county_number={county_number}&road_category={road_category}&lat={lat}&lon={lon}&radius_km=50&operational_only=true&limit=20&offset=0.

Parameter	Requirement	JSON type	Description
`query`	optional	union	Free-text substring match on the point's name, e.g. "Lodalen". When the query equals a municipality name, only points in that municipality are returned and substring hits elsewhere ("Bergen" also matches "Bergenhus" in Østfold) are dropped but reported in a `note`. When no municipality matches the query, all substring hits are returned as-is.
`county_number`	optional	union	Norwegian county number, e.g. 3 for Oslo.
`road_category`	optional	union	One of E (Europaveg), R (Riksveg), F (Fylkesveg), K (Kommunal veg), P (Privat veg).
`lat`	optional	union	WGS84 coordinate to search around. Adds distance_km to each result and sorts nearest first.
`lon`	optional	union	WGS84 coordinate to search around. Adds distance_km to each result and sorts nearest first.
`radius_km`	optional	number	Max distance from lat/lon (default 50).
`operational_only`	optional	boolean	True (default) to only return currently active stations.
`limit`	optional	integer	Max results to return, 1 to 100 (default 20).
`offset`	optional	integer	Number of list items to skip; default 0.

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/vegvesen/find_traffic_points?query={query}&county_number={county_number}&road_category={road_category}&lat={lat}&lon={lon}&radius_km=50&operational_only=true&limit=20&offset=0

Replace URL placeholders and remove unused optional parameters.

JavaScript in a dashboard

const url = "https://allemannsdata.com/wiki/api/v1/kilder/vegvesen/find_traffic_points?query={query}&county_number={county_number}&road_category={road_category}&lat={lat}&lon={lon}&radius_km=50&operational_only=true&limit=20&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/vegvesen/find_traffic_points?query={query}&county_number={county_number}&road_category={road_category}&lat={lat}&lon={lon}&radius_km=50&operational_only=true&limit=20&offset=0"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "vegvesen",
  "operation": "find_traffic_points",
  "parameters": {},
  "data": {},
  "entities": [],
  "_meta": {"retrieved_at": "...", "sources": [], "cache": {}},
  "_links": {"self": "...", "source": "...", "wiki": "..."}
}

Form for manual use

The form is a fallback for people and browser agents that cannot open the GET URL directly.

query Type: string. Free-text substring match on the point's name, e.g. "Lodalen". When the query equals a municipality name, only points in that municipality are returned and substring hits elsewhere ("Bergen" also matches "Bergenhus" in Østfold) are dropped but reported in a `note`. When no municipality matches the query, all substring hits are returned as-is.

county_number Type: integer. Norwegian county number, e.g. 3 for Oslo.

road_category Type: string. One of E (Europaveg), R (Riksveg), F (Fylkesveg), K (Kommunal veg), P (Privat veg).

lat Type: decimal number. WGS84 coordinate to search around. Adds distance_km to each result and sorts nearest first.

lon Type: decimal number. WGS84 coordinate to search around. Adds distance_km to each result and sorts nearest first.

radius_km Type: decimal number. Max distance from lat/lon (default 50).

operational_only Type: yes/no. True (default) to only return currently active stations.

limit Type: integer. Max results to return, 1 to 100 (default 20).

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 find_traffic_points 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

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.