A public bridge across the registers used in Romanian data: 3,181 base UATs and 6 Bucharest sectors linked through SIRUTA (National Institute of Statistics), CUI / CIF tax codes (Ministry of Finance), postal codes, Wikidata (P843), and OpenStreetMap boundary relations (ANCPI). The set also shows where fields still need checking.
The Register of Territorial-Administrative Units maintained by the National Institute of Statistics. The primary key for official censuses (RPL 2021), Eurostat NUTS classifications, and cadastral mapping.
The Unique Fiscal Registration Code of public legal entities (mayoralties and councils). Mandatory for national budget execution (Forexebug), public tenders (SICAP), and state contracts.
Geographic routing system for physical logistics and courier delivery. Connects legal and statistical entities directly to physical street addresses and territorial postal routes.
Global knowledge graph and universal semantic identifier (Linked Open Data). Connects every municipality to Wikidata, Wikipedia in 300+ languages, OpenStreetMap, and international ontologies.
Official administrative boundary polygons from the ANCPI cadastre (data.gov.ro). Linked via Wikidata QID, offering on-demand GeoJSON downloads for geospatial analysis.
The catalog separates field presence from field verification. In this snapshot, 145 records have no publishable CUI from the enrichment source, while 5 present values fail the control-digit check.
A CUI checksum is syntactic and does not confirm current tax status. Coordinates are reference points, not administrative boundaries.
Query by any of the four identifiers or search by city name. The engine resolves all administrative relationships in-memory instantly.
Have a column of Tax CUIs from public procurement, SIRUTA codes from the census, Wikidata QIDs, or postal codes? Paste your list below to resolve and enrich all records client-side in milliseconds with zero server latency.
Each entry is a concrete action for a reader, journalist, researcher, or developer. Filter by the kind of work you want to do with the data.
50 uses shown
Type a commune, town, or municipality name and open its record.
Paste a CUI from a financial table and resolve its associated UAT.
Use the statistical key when your table comes from INS or a census.
Start with a six-digit postal code and see its reference locality in the catalog.
Enter a Q identifier and connect the semantic graph to the administrative register.
The search normalizes names, so a simplified spelling still reaches the correct record.
Share a record with its SIRUTA parameter and preserve the exact item under discussion.
Use the copy controls to move a code into a form, a note, or a script.
Use the county and vehicle code to group or check a local table.
Open the published administrative address before sending a request.
Go straight to the institution website supplied by the catalog's contact source.
Use the published email address for an information request or a verification.
View the reference coordinate in OpenStreetMap and start a geographic check.
Use resident population as an explicit reference with the census date beside the value.
Understand the difference between Bucharest Municipality and its six sector records.
Tie the UAT CUI to the right local entity and avoid mixing it with the county institution.
Use the step-by-step laboratory to see whether the number passes the format check.
Join CUIs from SICAP to the UAT's county, population, and open identifiers.
Add SIRUTA beside a budget execution so units can be compared through a geographic key.
Complete a census table with region, NUTS, and reference coordinates.
Use SIRUTA and NUTS codes to connect transport data to the territory being analyzed.
Export UAT coordinates for a working map, while documenting that they are reference points.
Filter the catalog by county and count or export only the units you need.
Add QIDs to SPARQL queries or linked-data graphs that start from a UAT.
Resolve a Wikidata identifier back to the local administrative codes.
Put CUIs, SIRUTA, QIDs, postal codes, and names in the same working list.
Paste one value per line and receive a crosswalk result for every line.
Load a local working file; its contents are read in the browser to prepare the batch.
Download a spreadsheet-compatible table while keeping unresolved input lines.
Use the structured result in a script, notebook, or application.
For browser-side conversion, the pasted list does not need to be sent to the crosswalk server.
Request JSON by CUI, SIRUTA, QID, postal code, or general search.
Integrate the control-digit check into a form or an import flow.
Use the JSON with metadata, contacts, population, and coordinates as a local working source.
Check field names, types, key, and caveats before integration.
Start a map, directory, or verification form without rebuilding the registers.
Use llms.txt and the schema to explain each field to an agent.
Read the snapshot and version before combining the export with another edition.
Download the quality report for the explicit list of records that need a better source.
Separate a present CUI from one that passes the mathematical format check.
Use the flagged groups to check whether the same value was reused in the source.
Compare a local export with the crosswalk postal field and flag gaps.
Use the QID and linked URL to manually inspect a semantic match.
Keep the export and quality report together so an analysis can be rerun.
Use the caveats beside the data to avoid conclusions stronger than the sources support.
Start from a CUI or SIRUTA, verify the UAT, and keep the direct link as working evidence.
Extract website, email, phone, and address for a set of local authorities.
Record the key, snapshot, source, and caveat before publishing a data join.
Connect a civic project to public identifiers without hiding provenance or gaps.
Compare quality reports between snapshots and see where a new verification is worthwhile.
The fiscal CUI (Ministry of Finance) uses a control digit checked here with Modulo 11. For SIRUTA, this catalogue checks numeric form and length; it does not claim a checksum without a documented reference formula. Test the CUI control digit step by step:
Anyone who has ever built a public spending dashboard, civic map, or census visualization in Romania has hit a frustrating structural wall: the rupture between registries. The public administration operates parallel identifier systems administered by different institutions, created in different eras, and optimized for divergent goals:
A frequent defect in Romanian open data analysis is the accidental conflation of a county capital mayoralty with its county council. For instance, in Cluj County, the Mayoralty of Cluj-Napoca has CUI 4305857 (SIRUTA 54975), whereas the Cluj County Council operates under CUI 4422244.
This universal crosswalk guarantees unambiguous association strictly at the base municipality (UAT) level, decoupling local executive mayoralties from deliberative county councils.
Bucharest Municipality uses SIRUTA 179132 and is kept beside six separate sector records, from 179141 to 179196. The export contains 3,181 base UATs plus those six sector records. Sector population is not repeated because it is already included in the Bucharest total.
All data artifacts are published under the Creative Commons CC0 1.0 Universal (Public Domain) license. You are free to integrate them into commercial apps, civic analytics, GIS workflows, or investigative reporting.
| Format | Description | Size | Direct Download |
|---|---|---|---|
| JSON | Complete dataset with metadata, coordinates, population, Wikidata QID, OSM boundary relation, and contact info | 2.5 MB | crosswalk-uat.json |
| CSV | Excel-compatible CSV table with UTF-8 BOM (3,188 rows, with Wikidata QID and OSM relation ID) | 905 KB | crosswalk-uat.csv |
| JSON Min | Ultra-compact search index for web applications (with Wikidata QID and OSM relation ID) | 687 KB | crosswalk-min.json |
| REST API | Live resolution endpoint (CUI, SIRUTA, QID, Postal Code) | Live | /puntea-administrativa/api/resolve?qid=Q19660 |
| LLMS.txt | Context documentation for AI agents and LLMs | 1.2 KB | llms.txt |
| Schema | Field dictionary, types, and interpretation limits | JSON | schema.json |
| Quality | Reproducible report of missing fields, warnings, and duplicate groups | JSON | data-quality.json |
| Documented API | OpenAPI specification for resolving and checking identifiers | JSON | openapi.json |