Territorial administrative units

Open data API in a single place

Provided by Agenția Națională de Cadastru și Publicitate Imobiliară

Get early access to Territorial administrative units API!

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

Dataset information

Country of origin
Updated
2014.11.21 08:12
Created
2013.10.21
Available languages
English
Keywords
NUTS, limite unitati administrative, unitati administrativ teritoriale
Quality scoring

Dataset description

The theme of Administrative Units was obtained from the transformation of data from the RELUAT project (Electronic Register of Territorial Administrative Units) into the INSPIRE application scheme for the theme of Administrative Units. The boundaries of the administrative units are set by involving the following factors: prefectures, town halls, ICOs, ANCPIs, public institutions. The boundaries of neighbouring administrative units that were not agreed by one of the stakeholders were marked as not agreed (see Class Objects: AdministrativeBoundary, Field: LegalStatus, Value: non-Agreed). The format of the data sets (classesObjects) uploaded to this site is KMZ, the compressed form of the KML format, which stores the data in the WGS84 system. The transformation of data into KMZ was done using the ShapeKMLTransdatRO app version 1.02. The description of the fields of the uploaded data sets can be found in the DescriptionClaseObjectsCampsKMZ.xls file. Please note that this data can also be downloaded from the INIS geo-portal to the Download section (http://geoportal.ancpi.ro/geoportal/catalog/main/home.page) after registration and authentication. The formats available for download from Geoportal are: fileGeodataBase, shape, dxf, dgn, in INSPIRE application scheme and Stereographic projection system 1970.
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