Small Area Statistics of the City of Turku

Open data API in a single place

Provided by Turku

Get early access to Small Area Statistics of the City of Turku API!

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

Dataset information

Catalog

Turku catalog

Country of origin

Finland

Updated

Created

2023.12.18

Available languages

English

Keywords

väestönmuutokset, muuttoliike, väestö, asunnot, rakennukset, tilastot

Datasource

Official portal for European data link

Quality scoring

Dataset description

Statistics by sub-region of the City of Turku. The data includes regional divisions: the whole city (853 Turku) and small areas (853+six digits). The original data were produced by Statistics Finland. For contractual and data protection reasons, the City of Turku’s open data service has limited the scope of the datasets. The published areas have at least 100 inhabitants or 10 buildings, depending on the statistics. Note: csv files have comment lines that contain metadata. Further information: * [city statistics website] (http://www.turku.fi/tilastot) * [small, statistical and sub-areas of the city] (https://www.avoindata.fi/data/fi/dataset/turun-kaupungin-aluejakoja) * [original Statistics Finland databases] (https://www.stat.fi/tup/vaestotilastopalvelu/index.html)

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

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.

api.store Built by Apitalks

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

About api.storePrivacy Terms of Service