City Policy Priority Neighbourhoods (QPV) – Orléans Métropole

Open data API in a single place

Provided by Agence Nationale de la Cohésion de Territoires

Get early access to City Policy Priority Neighbourhoods (QPV) – Orléans Métropole API!

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

Dataset information

Country of origin
Updated
2018.01.23 10:00
Created
2018.01.23
Available languages
English
Keywords
services-social
Quality scoring

Dataset description

**Priority neighbourhood of the city’s policy – Orléans Métropole** The perimeters of the priority districts of the city’s policy are fixed by [Decree No. 2014-1750 of 30 December 2014](https://www.legifrance.gouv.fr/affichTexte.do?cidTexte=JORFTEXT000030007934&categorieLien=id) for the metropolis and by [Decree No 2014-1751 of 30 December 2014] for the overseas departments, in Saint-Martin and in French Polynesia. The Programming Act for the City and Urban Cohesion of 21 February 2014 provides, in its article 5, the modalities for the reform of the priority geography of the city’s policy. These are detailed, for the metropolis, in Decree No. 2014-767 of 3 July 2014 on the national list of priority districts of the city’s policy and its specific modalities of determination in the metropolitan departments and, for ultra-marine territories, in Decree No 2014-1575 of 22 December 2014 on the modalities for determining the priority districts of the city’s policy particular to the overseas departments, Saint-Martin and French Polynesia. These perimeters replace sensitive urban areas (Zus) and neighbourhoods in an urban contract for social cohesion (CUCS) from 1 January 2015. For more information on the territories concerned by the city policy you can consult the [Geographic Information System of City Policy](https://sig.ville.gouv.fr/).
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