Voting district of the City of Oulu

Open data API in a single place

Provided by Oulu

Get early access to Voting district of the City of Oulu API!

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

Dataset information

Catalog

Oulu catalog

Country of origin

Finland

Updated

Created

2017.06.15

Available languages

English

Keywords

äänestysalueet, äänestys, aluejako

Datasource

Official portal for European data link

Quality scoring

Dataset description

Oulu voting district division in accordance with ESRI Shapefile and MapInfo TAB spatial data formats and delivered as WFS interface. ETRS-GK26 (EPSG 3133) is the maintenance co-ordinator of the data and the delivery of the spatial data sets. You can check the supported coordinates of the WFS data in [GetCapabilities document] (https://e-kartta.ouka.fi/TeklaOGCWebOpen/WFS.ashx?service=WFS&request=GetCapabilities). You can use the URL (https://e-kartta.ouka.fi/TeklaOGCWebOpen/WFS.ashx) to access the WFS data for use in the spatial data software. If you open the WFS data in MapInfo Pro, attach the projection parameters used by Mapinfo to the projection file MAPINFOW.PRJ used by the City of Oulu: ‘ETRS-GK26\p3133’, 8, 115, 7, 26, 0, 1.0, 500000, 0 The characteristics of the data are the codes and names of the voting districts. The division of voting districts will be updated if necessary.

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