Public utility easements (SUPs) are administrative limitations on the right to property, they are established for the benefit of public persons, concessionaires of public works or public works, private persons engaged in an activity in the public interest. The collection and conservation of public utility easements is a sovereign task of the State, which must bring them to the attention of local and regional authorities so that they may annex them to their urban planning documents. The public utility easements concerned are those defined by Articles L. 126-1 and R. 126-1 of the Urban Planning Code and their annexes.
The AC4 type SUPs are the result of the architectural, urban and landscape heritage protection zones (ZPPAUP) which today evolve into “Agreement of Architecture and Heritage Areas” (AVAP). The aim of this new scheme is to develop a new approach to the qualitative management of the territories by integrating the sustainable development objectives into the heritage and urban approach of the ZPPAUP.
In the ZPPAUPs still in force and in AVAPs, works having the object or effect of transforming or modifying the appearance of a building, whether built or not, are subject to prior authorisation, which may be accompanied by special requirements.
Texts in force:
Heritage Code:
—Articles L. 642-1 to L.642-5 and Articles D 642-1 to D 642-10: definition and creation of an AVAP
—Articles L. 642-6 and L.642-7 and Articles D 642-11 to D 642-28: work in AVAP
—Article L. 642-8: the transformation of ZPPAUP into AVAP
link to articles L642-1 et seq. of the Heritage Code:
http://www.legifrance.gouv.fr/WAspad/UnArticleDeCode?code=CPATRIML.rcv&art=L642-1
link to SUP scanning guide: http://www.geomatique-aln.fr/spip.php?article296
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.