Local Intercommunal Urban Plan (PLUi) of Rennes Métropole - Simplified modification n°3 (MS3)

Open data API in a single place

Provided by Rennes Métropole

Get early access to Local Intercommunal Urban Plan (PLUi) of Rennes Métropole - Simplified modification n°3 (MS3) API!

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

Dataset information

Country of origin
Updated
2026.01.08 07:00
Created
2026.01.08
Available languages
English
Keywords
urbanisme, plui
Quality scoring

Dataset description

Local Intercommunal Urban Plan (PLUi) approved by deliberation of the Council of Rennes Métropole on 15/12/2022. Last Amendment (M n°1) approved by deliberation of the Rennes Métropole council of 15/12/2022, last Simplified Amendment (MS n°3) approved by deliberation of the Rennes Métropole council of 21/03/2024, last Update (MAJ n°6) by order of the President of Rennes Métropole of 06/04/2023. The PLUi regulation is composed of a literal regulation and a graphic regulation that complement each other. The literal regulation lays down the rules applicable to each of the areas that are located on the graphic regulation. * The literal regulation includes definitions of terms taken from the national lexicon, which is sometimes adapted to the local context; implementing rules; graphic provisions applicable to all areas; provisions applicable to all urban areas (U), supplemented by provisions specific to each urban area; literal provisions applicable to all zones; area-specific provisions. * The graphical by-law consists of zoning plans at different scales depending on whether the parts of the territory are urbanized or not. They cover the entire territory. In order to ensure that the extensive information on these plans is legible, specific plans provide information on certain topics: heights, ground right-of-way, vegetative coefficient, parking and social equilibrium rules of the habitat. It also includes detailed plans for certain islands that either supplement certain provisions of the graphic or literal by-law or replace certain rules of the literal by-law. These plans sometimes indicate the heights, right-of-way or building areas, location or scheduling rules or other specific rules to be respected. They are indicated (d). It includes mass plans on certain areas or islands. These plans indicate the heights and the right-of-way or building areas sided in 3 dimensions. They are indicated (m). It also includes splice plans. These plans indicate the heights to be respected. They are indicated (e). The provisions laid down in the Graphic Regulation and their effects are detailed in the dedicated chapter of this Regulation. The general organisation of the PLUi is based on the nomenclature provided for in Articles L151-9 et seq. of the Urban Planning Code: 9 categories of urban areas (7 mixed and 2 specific); 2 areas intended to be open for urbanisation (1AU and 2AU); 2 natural and forest areas (NP and N). Zone N comprises two specific sectors and building sectors of limited size and capacity; 1 agricultural area A comprising building sectors of limited size and capacity. The determination of zoning is carried out on the basis of the initial state of the environment and the project on agricultural, natural and forestry areas and the crossing between existing environments and the development objectives of urbanized or to be urbanized sectors which made it possible to determine the desired urban environments. Details on entering GIS data: The reference database for entering geographical information from the graphic regulation plans is the ©DGFiP data, with the exception of the thematic plans relating to stormwater infiltration (BRGM data) and certain detailed plans. The entry of the geographical information of the plans is carried out in the 1/2000th, with an accuracy to the metre, on the backgrounds of the plans of the building and the cadastral parcel ©DGFiP of 2017. This reference plan background, which supports GIS input, is occasionally supplemented by additional built-up information from the Rennes Métropole local "built-up reference plan background" (e.g. names of routes and paths from the "Referential Routes and Addresses (RVA)"). A discrepancy in the geographical representation of the information is sometimes made voluntarily for better legibility of the plans. Thus, some data represented according to a linear geometry (the EBC, EIPE, plantations or open spaces to be realized, location easements and location principles), precisely entered on a cadastral plane background like the other data of the zoning plan at 1/2000, are sometimes displayed with a voluntary shift for a better readable information that overlaps. For example, if a classified wooded area (CBA) is on a parcel boundary ©DGFiP, and the regulatory zoning is also positioned in the same location, a voluntary shift to the left or right of the CBA parcel boundary line line is applied to display it "above" or "above" the specific zoning line. [**Download PLUi data in standard CNIG GeoPackage format.**](https://public.sig.rennesmetropole.fr/resources/donations/urban planning/rain/rain_rennesmetropole.gpkg) You can find information on the GeoPackage format [here](https://en.wikipedia.org/wiki/Geopackage). And on the v2017d standard for Dematerialised Urban Planning Documents [here] (http://cnig.gouv.fr/?page_id=2732). **We advise you to use the attribute "lib_complete" to classify / differentiate each object class of the PLUi and to refer to the literal regulation for a good understanding of the objects.** **To assist in the exploitation of our data, download the [code and label dictionary](https://public.sig.rennesmetropole.fr/resources/donations/urban planning/rain/rain_dictionnaire_codes_libelles.csv).**
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