Geomarketing · INSEE · IGN
IRIS Code Export by Isochrone
From store addresses, get INSEE IRIS codes within an isochrone zone (time or distance) — car, pedestrian or bicycle. Ideal for catchment area analysis, media coverage and geomarketing.
Isochrone Scenarios
Each row = transport mode + time (minutes) or distance (km). Applied to all stores unless the file contains its own iso_minutes / iso_km columns.
Example: Car 15 min, Walk 2 km, Bike 10 min. Use + Add or the ⧉ button to duplicate a scenario.
BAN geocoding then IGN Géoplateforme isochrones (bdtopo-valhalla).
Paste or import up to 500 addresses (Excel, CSV). Recognized columns:
store_name, address, iso_minutes, iso_km.
Download Excel template.
Format: store;address;minutes;km — separator ; or tab.
Automatic column detection (or position A/B/C/D).
Processing Errors
How It Works
- Define your isochrone scenarios (transport mode, duration or distance) and intersection buffer (100 m default).
- Enter an address or import a list of stores (Excel/CSV).
- Review the table of IRIS codes by scenario and export to CSV or Excel.
Frequently Asked Questions
What is the source for IRIS boundaries?
IRIS boundaries come from the INSEE geographic division (France-wide vintage). The intersection is calculated server-side by Flownect.
Which transport profiles are supported?
Car (car), pedestrian (pedestrian) and bicycle (bicycle) via the IGN Géoplateforme isochrone API (bdtopo-valhalla).
Difference between detail and compact view?
The detail view lists one row per IRIS code. The compact view groups all IRIS codes from a scenario on a single row (separated by ;), like the iris_list_compact tab from the original script.