# French Cadastre Parcels – Area, PLU Zoning & Past Sales (`yck69/french-cadastre-parcels`) Actor

Find French cadastral parcels by address, GPS point, parcel ID or commune section: exact area, PLU/PLUi zone (U, AU, A, N) with its description, planning constraints such as maximum height, pre-emption right or flood areas, and every recorded sale (DVF). Land prospecting at scale.

- **URL**: https://apify.com/yck69/french-cadastre-parcels.md
- **Developed by:** [yck](https://apify.com/yck69) (community)
- **Categories:** Real estate, Business
- **Features:** Limited permissions
- **Stats:** 7 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $5.00 / 1,000 parcels

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## French Cadastre Parcels – Area, PLU Zoning & Past Sales

https://www.youtube.com/watch?v=gZL2exUkWd4

**What does French Cadastre Parcels do?** It turns an address, a GPS point, a parcel ID or a whole cadastral section into a complete **land sheet**: the parcel's exact **area**, its **zoning in the local urban plan** (PLU, PLUi or carte communale) with the zone's description, the **planning constraints** that apply (maximum height, social-mix sectors, protected areas, flood areas, pre-emption right…), and every **sale recorded on it** since 2021.

- **Find parcels four ways**: by address (the parcel under or nearest to it), by GPS point, by 14-character parcel ID, or by **listing a whole section** with area filters — ideal for land prospecting.
- **Zoning**: zone code (`UCe1b`, `AUa`, `N`…), type (Urban, Future urban, Agricultural, Natural), full description, plan type and name, approval date and regulation file name.
- **Constraints** from the national urban-planning portal: prescriptions (e.g. `Hauteur Max-25`, `Secteur de mixité sociale`, `Espace boisé classé`) and information areas (pre-emption right, noise exposure, sanitation, archaeology, UNESCO perimeter…).
- **Past sales** on the parcel from DVF: date, price, property type, living and land area.
- **Maps**: Géoportail cadastre link, Google Maps link and optional GeoJSON outline for your GIS.

For property developers and land scouts, architects and surveyors, real-estate agents, notaries, solar and EV-charging site finders, and anyone checking what can be built where.

### What data can you get?

<table>
<tr><td>🆔 Parcel ID</td><td>📏 Area</td><td>🗺️ Zone code and type</td></tr>
<tr><td>📝 Zone description</td><td>📘 Plan name and date</td><td>🚧 Prescriptions</td></tr>
<tr><td>ℹ️ Information areas</td><td>💶 Past sales</td><td>📍 GPS point</td></tr>
<tr><td>🧭 Géoportail link</td><td>🔷 GeoJSON outline</td><td>🔍 Section search</td></tr>
</table>

### How to use it

1. Click **Try for free** and open the Actor.
2. Enter **addresses**, parcel IDs or a commune **section**.
3. Set area filters for land searches.
4. Click **Start** and open the parcels view.
5. Export, or add outlines for your GIS.

### Input examples

**One address and one parcel ID**

```json
{
  "addresses": ["18 rue de la République, 69002 Lyon"],
  "parcelIds": ["69382000AK0030"]
}
```

**Land search: every plot over 5 ha in section 0D of Affoux, largest first**

```json
{
  "sections": [{ "commune": "Affoux", "section": "0D" }],
  "minAreaM2": 50000,
  "maxResults": 50
}
```

**GPS points of candidate sites, with outlines for a map**

```json
{
  "points": [{ "latitude": 45.0627, "longitude": 4.37, "reference": "site-ardeche" }],
  "includeGeometry": true
}
```

### Output

Real parcel from the first example (November 2026):

```json
{
  "parcelId": "69382000AK0030",
  "communeCode": "69382",
  "commune": "Lyon",
  "section": "AK",
  "number": "0030",
  "areaM2": 879,
  "latitude": 45.760034,
  "longitude": 4.835071,
  "zone": "UCe1b",
  "zoneType": "U",
  "zoneTypeLabel": "Urban (buildable)",
  "zoneDescription": "Tissu urbain dense a caractere patrimonial qui regroupe toutes les fonctions des centres urbains...",
  "planType": "PLUi",
  "planName": "PLUI GRAND LYON LA METROPOLE",
  "planValidSince": "2026-03-26",
  "prescriptions": ["Secteur de mixite sociale", "Secteur de taille minimale des logements-1", "Polarite commerciale",
                    "Secteur de stationnement-Aa", "Risque d inondation par ruissellement-ZONE PRODUCTION", "Hauteur Max-25"],
  "informationAreas": ["Zone d exposition au bruit", "Zone d assainissement-COLLECTI", "Perimetre d un bien inscrit au patrimoine mondial"],
  "planningStatus": "covered",
  "salesCount": 0,
  "lastSale": null,
  "geoportailUrl": "https://www.geoportail.gouv.fr/carte?c=4.835071,45.760034&z=19&l0=CADASTRALPARCELS.PARCELLAIRE_EXPRESS..."
}
```

The land search of the second example returned plots of 13.7 ha, 10.1 ha, 8.9 ha and 8.3 ha in natural zones (`N`, `Nco`) of the Affoux PLU; one 7.2 ha plot shows a recorded sale of €16,550.

| Field | Meaning |
|---|---|
| `parcelId` | 14-character cadastral ID: commune (5) + prefix (3) + section (2) + number (4). Paris, Lyon and Marseille use arrondissement codes. |
| `areaM2` | Official cadastral area (*contenance*). |
| `zoneType` | `U` urban, `AUc`/`AUs` future urban (open / closed), `A` agricultural, `N` natural; `ZC` / `ZnC` in communes with a *carte communale*. |
| `planningStatus` | `covered`, or `no-local-plan (RNU: national rules apply)` where the commune has no published plan. |
| `prescriptions` | Planning rules drawn on the parcel: heights, protected trees and woods, social-mix or minimum-size sectors, setbacks, risks… |
| `sales` | Up to 10 sales on the parcel (DVF, since July 2021), newest first. |

### How much does it cost?

**$5 per 1,000 parcels** ($0.005 per parcel returned with its zoning and sales). Inputs that match no parcel are free.

### More Actors from this developer

### FAQ

##### Where does the data come from?

Parcels: the official cadastre (DGFiP Parcellaire Express via IGN's API Carto). Zoning and constraints: the Géoportail de l'urbanisme, where communes publish their plans. Sales: DVF from the tax administration. All are official open data.

##### Is the zoning legally binding?

The Géoportail de l'urbanisme is the reference publication of local plans, but a plan may have been amended since. Always check the regulation file and ask the town hall for a *certificat d'urbanisme* before a transaction.

##### Why does an address return the neighbouring parcel?

Address points are often placed on the street. When no parcel is under the point, the nearest parcel within about 20 m is returned; check the map link for corner plots.

##### Can I find the owner?

No. Owner names of parcels owned by private individuals are not open data in France.

##### Can I use it through the API, Make, Zapier or Google Sheets?

Yes. Every run can be started and read through the [Apify API](https://docs.apify.com/api/v2) (JavaScript and Python clients, CLI, MCP), and Apify integrations connect it to Make, Zapier, n8n, Google Sheets, Slack, webhooks and more.

##### Something isn't working, or you need another field?

Open an issue on the **Issues** tab: feedback is read and answered.

# Actor input Schema

## `addresses` (type: `array`):

French addresses; the parcel under (or nearest to) the address point is returned.

## `parcelIds` (type: `array`):

14-character cadastral IDs (IDU), e.g. <code>69382000AK0030</code> = commune 69382, prefix 000, section AK, number 0030.

## `points` (type: `array`):

<code>\[{"latitude": 45.0627, "longitude": 4.37, "reference": "site-1"}]</code>

## `sections` (type: `array`):

List every parcel of a section, largest first: <code>\[{"commune": "Affoux", "section": "0D"}]</code>. Combine with the area filters to find large plots.

## `minAreaM2` (type: `integer`):

Section search only.

## `maxAreaM2` (type: `integer`):

Section search only.

## `includeZoning` (type: `boolean`):

PLU/PLUi/carte communale zone and its description, prescriptions (height, social mix, protected areas…) and information areas (pre-emption right, noise, sanitation…).

## `includeSales` (type: `boolean`):

Sales recorded on the parcel since July 2021.

## `includeGeometry` (type: `boolean`):

Add the parcel polygon, for maps and GIS.

## `maxResults` (type: `integer`):

Requested parcels come first, then section results.

## Actor input object example

```json
{
  "addresses": [
    "18 rue de la République, 69002 Lyon"
  ],
  "parcelIds": [
    "69382000AK0030"
  ],
  "includeZoning": true,
  "includeSales": true,
  "includeGeometry": false,
  "maxResults": 200
}
```

# Actor output Schema

## `parcels` (type: `string`):

Area, zoning and last sale per parcel.

## `results` (type: `string`):

Every field of every row.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "addresses": [
        "18 rue de la République, 69002 Lyon"
    ],
    "parcelIds": [
        "69382000AK0030"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("yck69/french-cadastre-parcels").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "addresses": ["18 rue de la République, 69002 Lyon"],
    "parcelIds": ["69382000AK0030"],
}

# Run the Actor and wait for it to finish
run = client.actor("yck69/french-cadastre-parcels").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "addresses": [
    "18 rue de la République, 69002 Lyon"
  ],
  "parcelIds": [
    "69382000AK0030"
  ]
}' |
apify call yck69/french-cadastre-parcels --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,yck69/french-cadastre-parcels"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/DHeMb2RXWOYvNNxLo/builds/VaLRuHMAlxD7WyHEB/openapi.json
