This built area can also be described as an “urban task” or an urban envelope and is defined as the area delimiting a set of parcels built on a given date. This envelope is only a spatial reference for locating a boundary of construction according to different design criteria.
However, that envelope does not in any way constitute the currently urbanised part defined by virtue of the application of land law, which is much more restricted, which is determined on the basis of factual elements of the ground and on the basis of jurisprudential criteria.
This built sector serves only as a reference point to contribute to the assessment of the consumption of space in urban planning documents.
Some specific features of the spatial distribution of built-up areas are observed in more detail. These differences can be attributed to the land structure of agricultural areas (cultural typology, parcel geometry, cultural methods of setting up farms, etc.), to land-based urbanisation patterns depending on the territory or, on the contrary, to more intensified forms of this residential development (e.g. regulatory aspect of urban planning documents).
In the department, these different forms of urban envelopes are identifiable. For example, in the Deux-Sèvres, the periphery of Parthenay is composed of a scattered set of habitat represented by an urban envelope in cloud of dots. Whereas in contrast, Niort’s periphery is marked by larger but more concentrated envelopes.
This data specifies the number of parcels that make up each urban envelope. This allows, by simple processing, to select only the corresponding urban envelopes, those consisting of at least four units.
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.