Counties -National Statutory Boundaries - Ungeneralised 2026

Open data API in a single place

Provided by Tailte Éireann

Get early access to Counties -National Statutory Boundaries - Ungeneralised 2026 API!

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

Dataset information

Catalog

Tailte Éireann catalog

Country of origin

Ireland

Updated

2026.04.07 02:38

Created

2026.03.25

Available languages

English

Keywords

high-value-dataset, Statutory Boundaries, geospatial, dgigovernment

Datasource

Official portal for European data link

Quality scoring

Dataset description

<p>The division of Ireland into counties was introduced gradually by Norman and English settlers between the 13th and 17th centuries, reflecting their use in in the Kingdom of England as units of local government. Townlands, civil parishes and baronies are subdivisions of counties. The 6” survey of Ireland carried out under the 1825 Boundary Survey Act documented and formalised the boundaries of the thirty-two counties of Ireland. Counties are statute boundaries under the 19th century Boundary Survey Acts and can only be altered by statutory instrument. This dataset is a digital representation of the statutory boundary as shown on the relevant historic mapping and includes alterations brought about by statutory instruments.There are 26 counties in the republic of Ireland. This dataset is provided by Tailte Éireann.</p>

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

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.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service