Parking violations in Helsinki

Open data API in a single place

Provided by Helsingin kaupunkiympäristön toimiala

Get early access to Parking violations in Helsinki API!

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

Dataset information

Country of origin
Updated
Created
2014.10.28
Available languages
English
Keywords
pysäköintivirheet, pysäköinninvalvonta, traffic, liikenne, parking violations, pysäköinti, parking
Quality scoring

Dataset description

Parking offences recorded in Helsinki by parking enforcement and police since January 2014. The data includes the time at which the violation was committed to the nearest month and year, the address at which the fine or notice was issued, the stage of the fine, the main cause of the fine, the person who registered the fine and the postal code area information. Todellinen sijainti -attribute indicates whether the location of the parking error is the actual location. The data is entered into the database approximately every six months. **Previewing the data in the kartta.hel.fi service:** - [In the year 2023](https://kartta.hel.fi/link/dEk6Lr) **Coordinate systems:** - Maintained in ETRS-GK25 (EPSG:3879) **API address:** - WFS: https://kartta.hel.fi/ws/geoserver/avoindata/wfs?request=getCapabilities **Layers:** - Pysakointivirheet **Pysakointivirheet: attributes, data types and translation:** - id (int): unique identifier - kuukausi (string): month - vuosi (int): year - osoite (string): street name and possible address number - virhemaksun_vaihe (string): the stage of the fine, parking fine/notice - virheen_paasyy_ja_paaluokka (string): the main cause for the fine and its category - virheen_kirjaaja (string): the person who registered the fine, police/parking inspector - easting (int) - northing (int) - postinumero (string): postal code - postitoimipaikka (string): post office - suurpiiri (string): name of the metropolitan area, southern/eastern/south-eastern/central/north-eastern/western/northern/Östersundom - kunta (string): municipality - kunta_nro (string): municipality code - kaupunginosa (string): name of the district - osa_alue (string): name of the sub-district - todellinen_sijainti (string): the attribute evaluates whether it is the actual location (Kyllä) or an approximate location (Ei) ##The data covering years 2014 - 2017 contains the following information: - Virheen tekokuukausi / Month of the violation = Month in which the parking fine or notice was written. - Virheen tekovuosi / Year of the violation = Year in which the parking fine or notice was written. - Osoite / Address = the address at which the fine or notice was issued. The address may not be visible in all cases, e.g. handwritten fines/notices given by the police, or it may be incomplete. - Virhemaksun vaihe / Stage of the fine = Parking fine or notice - Virheen pääluokka / Pääsyy Main category/main reason of the fine = May include one to three different categories - Virheen kirjaaja / Person registering the fine = Parking inspector or police - Kaupunginosa / District In addition the geospatial dataset (SHP) regarding 2014-2017 contains postal code area information (y, x, postal code, city, region, municipality, municipality number). The source was the 2015 postal code division of the Helsinki Metropolitan Area. **The data contains some points outside of Helsinki. The table-form data (CSV) contains some parking fines without an address; they do not exist in the geospatial datasets (SHP). The geospatial datasets regarding 2018-2021 are geocoded from table-form data with the QGIS Digitransit Geocoding add-on (see additional information by clicking on each resource) and those contain errors. Data regarding year 2022 is available only as table-form data (CSV). Data regarding year 2023 and onwards, only the WFS api will be available for the new data, which require applications like QGIS or ArcGIS to be opened.**
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