Permanent base of geolocated equipment – Pays de la Loire

Open data API in a single place

Provided by INSEE

Get early access to Permanent base of geolocated equipment – Pays de la Loire API!

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

Dataset information

Country of origin
Updated
2020.12.04 12:06
Created
2020.12.04
Available languages
English
Keywords
equipement, bpe, geographie, territoire, territoires, amenagement
Quality scoring

Dataset description

The objective of the Permanent Base of Equipment (BPE) is to propose annually a geolocated equipment base built from various administrative sources. The Permanent Base of Equipment is divided into 7 main areas: services to individuals; shops; education; health; transport and travel; sports, leisure and culture; tourism. From BPE 2021, the SIRUS source replaces the SIRENE source. As a result of this change of source, the “ceased statistical” units are excluded from the BPE, so there is a noticeable decrease of 460000 in the number of BPE 2021 equipment. **The constitution of the ranges of equipment** The purpose of classifying equipment in ranges is to bring together equipment that has neighbouring implantation logics, in the sense that they are frequently present in the same municipalities. These groupings make it possible to develop synthetic indicators reflecting the hierarchical organisation of territories in terms of services to the population. The ranges of equipment are updated annually for a new version of the Permanent Base of Equipment. On the one hand, new equipment can be introduced into the base and, on the other hand, the installation of the equipment in the municipalities can be modified, all of which may have consequences on the composition of the ranges. To make up the ranges of equipment, three successive operations are carried out. **Establishment of equipment ranges** The method used to achieve a partition of equipment in ranges results mainly from an analysis of their simultaneous presence in the municipalities. To do this, an automatic classification of the equipment included in the BPE is carried out on the matrix indicating the presence of each type of equipment in each municipality of France. Municipalities with no equipment or one type of equipment are eliminated because they do not provide any information on the simultaneous presence of equipment in the municipalities. Given the volume of data processed, the so-called “dynamic cloud” method is used. It optimises the co-presence in municipalities of equipment belonging to the same range, while ensuring a sufficient number of types of equipment in each range. This typological analysis method makes it possible to quickly process a very large volume of data. **Granularity** 1 recording = 1 equipment **Coverage** Metropolitan France and DROM ** Enrichment** * Names/Codes of administrative divisions * ISO 3166-3 codes **IMPORTANT: There are geocoding errors on certain points. ** **Other related games** * ‘HTTPS://PUBLIC.OPENDATASOFT.COM/EXPLORE/DATASET/BUILDINGREF-FRANCE-BPE-ALL-MILLESIME/’ * ‘https://public.opendatasoft.com/explore/dataset/buildingref-france-bpe-all/’(−) * ‘HTTPS://PUBLIC.OPENDATASOFT.COM/EXPLORE/DATASET/BUILDINGREF-FRANCE-BPE-ALL-GEOLOCATED’
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