Skip to main content
EirePlan

EirePlan — How it works

How it works

Everything about a site is already public.
It is just scattered.

Planning history, ground conditions, services and transport are all published, across 35 sources that were never built to talk to each other. We collect them, resolve them to one address, and keep the source attached to every figure.

  1. 01

    Collect

    Thirty-one planning registers, plus the national datasets for ground, water, services, transport and people. Each on its own schedule, each in its own shape.

  2. 02

    Normalise

    One record per application, carrying the same fields whatever the source register calls them, matched to the statutory authority whose boundary the site sits inside.

  3. 03

    Open the file

    The documents the council published against the application: planner's report, conditions, further-information letters, objections.

  4. 04

    Answer

    Ask a question about a site and get the passage back, with the document and page it came from. Or take the whole record as a report, or over the API.

What we collect

Every layer here is built from public datasets that are licensed for reuse. Where a published figure exists we use it rather than model one of our own.

Planning and deliveryApplications, decisions, appeals and what was actually built.
Ground and environmentGeology, aquifers, flood risk, terrain and designations.
Services and capacityWastewater headroom, grid connections and contracted capacity.
People and movementPopulation, commuting, transport, schools and energy ratings.

From thirty-one registers to one record

A register will tell you an application was refused. The reason is in the planner's report and the conditions attached to the decision, which is why those are the files we open.

Register in, condition out

Thirty-one registers become one record per application, and then the decision notice sitting behind it, quoted with the page it came from.

  1. 31 planning registers

    LADCCLAFingalLASDCCLADLR+27

  2. One record per application

    3352/2514 Oakley Road, Ranelagh, Dublin 6LADCCDecisionGranted

  3. Read from the file

    Condition 7Decision notice, p.4
    “The first-floor rear extension shall be set back a minimum of 1.2 metres from the eastern party boundary, and the window serving it shall be fitted with obscure glazing.”Reason: to protect the residential amenity of adjoining property.

Every figure keeps its source

Each figure on a site page carries the dataset it came from and the date we last read it, so you can check it rather than take it.

SourceLicenceAs at
National planning application databaseCC-BY 4.010 Aug 2026
An Coimisiún Pleanála — appealsCC-BY 4.009 Aug 2026
Tailte Éireann — LA boundariesCC-BY 4.02024 vintage
BCMS — commencement noticesCC-BY 4.008 Aug 2026
EPA — strategic noise, round 4CC-BY 4.020 Aug 2026
Geological Survey Ireland — bedrockCC-BY 4.002 Aug 2026
EPA — radon risk mappingCC-BY 4.002 Aug 2026
National Monuments Service — SMRCC-BY 4.028 Jul 2026
CSO — Census 2022 small areasCC-BY 4.014 Jul 2026
EPA — waste water treatment capacityCC-BY 4.005 Aug 2026

Named, licensed, and listed

Everything we hold, and where each family of it comes from. If you have to stand over a figure in front of a planner or a client, you can point at its source.

People & place

+2 related feeds

Access & transport

+1 related feeds

Explore data provenance

See every source and its licence

Check it yourself.

A full site — boundary, thirteen applications, the documents behind them — is open to the public. No account needed.

Open the siteOpen precedent search