Measures of the pavement condition of the main street network in Helsinki

Open data API in a single place

Provided by Helsingin kaupunkiympäristön toimiala

Get early access to Measures of the pavement condition of the main street network in Helsinki API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
Created
2023.08.23
Available languages
English
Keywords
kuntomittaus, päällysteet, aluesuunnittelu, liikenne, teiden kunto, traffic
Quality scoring

Dataset description

Results of the condition measurements of Helsinki’s main street network 2018-2022. The condition measurements have been made as so-called service level measurements (PTM), which measure the trails, unevenness and side slope of the coating from the distance data produced by lasers attached to the measuring car and the profile of the pavement. Measures have been carried out on Helsinki’s main street network. Side-gradient, trail-right and trail-left data have only been measured in 2021 and 2022. The general condition of the street grid is described by the division of street length by condition category. Both condition variables (trails, unevenness) are divided into five condition classes. The street cycle (10 m) belongs to the condition category if the limit value for it is exceeded. The data is available for download in several formats, including JSON, KML, GIF, Tiff, GeoTiff, JPEG, PNG CSV, Esri Shape. Available formats can always be found under OutputFormat in the [GetCapabilities query](https://kartta.hel.fi/ws/geoserver/avoindata/wfs?request=GetCapabilities) for the service. **Coordinate systems:** — Maintained in ETRS-GK25 (EPSG:3879), can be projected to other coordinate systems. See GetCapabilities query for other possible coordinate systems. **API addresses:** — WFS API: [https://kartta.hel.fi/ws/geoserver/avoindata/wfs](−) **WFS layers:** — paallyst measurements **Features:** — ID: Unique Identifier of the Object — road: Name of measured street — measuring time: Measurement date — sun: Measured Street Direction (1 or 2) — ka: Measured street direction lane (1, 2 or 3) — AOSA: Part of the street (beginning) (1, 2 or 3) — AET: The distance of the starting point of the measured period from the beginning of the street section (m) — Losa: Part of the street (end) (1, 2 or 3) — let: Distance of the end point of the measured period from the beginning of the street section (m) — measured: Length of the germed cycle (m) — career: Average maximum depth of the measured cycle (mm) — uranium: Average maximum trail depth of right-hand groove of the measured period (mm) — careerv: Average maximum depth of left-hand groove in the measured period (mm) — IRI: Mean longitudinal unevenness of the measured period (mm/m) — side scaltev: Average side slope of the measured period (%) (positive value is side slope inward and negative value is side slope outward) — start_x: X coordinate of the starting point of the measured period (ETRS-GK25, EPSG:3879) — start_y: Y coordinate of the starting point of the measured period (ETRS-GK25, EPSG:3879) — end_x: X coordinate of the end point of the measured period (ETRS-GK25, EPSG:3879) — end_y: Y coordinate of the end point of the measured period (ETRS-GK25, EPSG:3879) — Lat: Latitude of the measured period starting point (WGS84 EPSG:4326) — Lon: Longitude of the measured period starting point (WGS84 EPSG:4326) — career_category: Average maximum trail depth of the measured period classified (classes 1-5) 5 (very good): 0-5 mm — 4 (good): 5-11 mm — 3 (statisfactory): 11-17 mm — 2 (bad): 17-20 mm 1 (very bad): 20 mm -> — iri_category: Mean longitudinal unevenness of the measured period classified (grades 1-5) 5 (very good): 0-3.6 mm/m — 4 (good): 3.6 – 4.6 mm/m — 3 (statisfactory): 4.6-5.6 mm/m — 2 (bad): 5.6-7.6 mm/m 1 (very bad): 7.6 mm/m -> — total_l: Lower value of the measured period Career_Class and IRI_class (classes 1-5) — data owner: Name of the owner of the data — pavemented_information service: Date of update of the data (yyyy-mm-dd) — GEOM: Geometry of the object
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks