Iris INSEE on the territory of m2A

Open data API in a single place

Provided by Mulhouse Alsace Agglomération

Get early access to Iris INSEE on the territory of m2A API!

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

Dataset information

Country of origin
Updated
2017.10.19 13:09
Created
2017.10.19
Available languages
English
Keywords
insee, statistiques, territoire, iris
Quality scoring

Dataset description

Perimeters of the IRIS Iots of INSEE. The communes of at least 10000 inhabitants and most communes of 5000 to 10000 inhabitants are divided into IRIS. This division, the basic mesh for the dissemination of infra-communal statistics, constitutes a partition of the territory of these municipalities into “neighbourhoods”. By extension, in order to cover the entire territory, we assimilate to an IRIS each of the municipalities not cut into IRIS. Space Coverage: Baldersheim – Bantzenheim – Battenheim – Berrwiller – Bollwiller – Bruebach – Brunstatt-Didenheim – Chalampé – Dietwiller – Eschentzwiller- Feldkirch – Flaxlanden – Galfingue – Habsheim – Heimsbrunn – Hombourg – Illzach – Kingersheim – Lutterbach – Morschwiller-le-Bas – Mulhouse – Niffer – Ottmarsheim – Petit-Landau – Pfastatt – Pulversheim – Reiningue – Richwiller – Riedisheim – Rixheim – Ruelisheim – Sausheim – Staffelfelden – Steinbrunn-le-Bas – Ungersheim – Wittelsheim – Wittenheim – Zillisheim – Zimmersheim
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