Napoleonic cadastre (departmental assembly)

Open data API in a single place

Provided by Département des Hauts-de-Seine

Get early access to Napoleonic cadastre (departmental assembly) API!

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

Dataset information

Country of origin
Updated
2020.01.17 08:55
Created
2020.01.16
Available languages
English
Keywords
parcelles, referentiel-geographique, culture-tourisme, napoleonien, cadastre, urbanisme
Quality scoring

Dataset description

Napoleonic cadastre on the Hauts-de-Seine department * * * * The cadastre refers to the documents used to establish the property tax base. This dataset concerns the plans of the “Napoleonian” cadastre, drawn up in 1802 for certain municipalities, but regulatoryly made from 1807 and modified until the 1860s for all the municipalities of the future department of Hauts-de-Seine. Produced by the tax administration, the Napoleonic cadastre entered the Archives départementales des Hauts-de-Seine by devolution of the Archives départementales de Paris (for the municipalities belonging to the former department of the Seine) and Yvelines (for the municipalities belonging to the former department of Seine-et-Oise), as well as by payments from the tax services and the service des Ponts-et-chaussées de Boulogne, which explains the multiple quotes. The plans are thus sided in D6P, 3P1 and 3P3, depending on their origin. There have been several successive revision campaigns for the municipalities of the former Seine department. It should be noted that the territory of Hauts-de-Seine has undergone many changes during the 19th century: creation of the municipalities of Levallois-Perret in 1866 (from the communes of Neuilly-sur-Seine and Clichy), Malakoff in 1883 (from the commune of Vanves), Bois-Colombes in 1896 (from the commune of Colombes), La Garenne-Colombes in 1910 (from the commune of Colombes) and finally Villeneuve-la-Garenne in 1929 (from the commune of Gennevilliers). Moreover, the Haussman reform of 1860 had the effect of integrating into Paris all or part of certain communes, such as Montrouge, Vanves, Issy-les-Moulineaux, Neuilly-sur-Seine, Clichy, while the village of Billancourt, which belonged to the municipality of Auteuil, abolished, was attached to Boulogne. Finally, some territorial exchanges could be carried out, such as between Vélizy and Meudon, or between Arcueil and Montrouge. Land registry plans can be a first step in finding owners of a plot or built property. The section and matrix states should then be consulted. **Specific comments** The Napoleonic cadastre shall be made available in the form of: * 1 km x 1 km georeferenced tiles; * “zip” files containing the JPEG tile and its associated georeferencing file; * the syntax used for the naming of tiles: ‘CADASTRE_NAPOLEONIEN_XXXX_YYY’ uses the XY coordinates in RGF93-CC49 in accordance with the Xmin_Ymax standard of the slab concerned; * the download of a slab is done by clicking on the slab in the table or in the map and downloading the associated zip file. The assembled Napoleonic cadastre is also offered as a standardised map service (WMS). **Related data** Link to the Napoleonic cadastre by leaves [Napoleonian cadastre (section sheets)](https://opendata.hauts-de-seine.fr/explore/dataset/fr-229200506-cadastre-napoleonien-feuilles-de-sections)
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