Logainm Import

From OpenStreetMap Wiki
Jump to: navigation, search


Logainm, which is the Irish for "place name", is the website of the Bunachar Logainmneacha na hÉireann (Placenames Database of Ireland). They recently released their data under ODbL, and the goal is to import as much as possible.

We want to add the offical irish name (name:ga=*), offical english name (name:en=*), and the logainm reference code to Irish administrative boundaries (townlands (admin_level=10), EDs (admin_level=9), Counties (admin_level=6 and admin_level=7), subtownlands (place=locality, locality=subtownland), civil parishes (boundary=civil_parish) and baronies (boundary=barony)).

This will radically improve the coverage of Irish names for administrative boundaries in OSM. It will also allow 2 databases (OSM & Logainm) to be cross-referenced.

The data will be uploaded for the entire island of Ireland (i.e. Republic of Ireland and Northern Ireland), although logainm data seems to be very sparse in NI.

Community support

I, (User:Rorym), plan to do the import using the import account rorym_import_logainm, and am an active member of the Irish OpenStreetMap community, I'm an active mapper of townlands, and have made a website, townlands.ie, which shows the current townland coverage and has various QA tools for townland mapping. The rest of the Irish OSM community is in favour of this. talk-ie thread with much approval


They import will be run as soon as approval has been given, and at regular intervals after that.

The Irish OSM community is currently mapping townlands (etc.), and is about 80% done. We expect to be done in a year. Hence this will be a semi-continuous import process, which will be occassionally run to update the OSM data that has been added since the last run. Additional runs should be considered part of this import.

Import Data


Data Description

Logainm consists of a Semantic Web/RDF data file. Each object has an id, english and irish name, category, optional lat/lon coords, and optional list of 'child objects', based on geographic contains. i.e. "Barony X is within county Y".

We are not using the geographic coordinates from Logainm, only the hierarchy data.

Logainm contains many types of data, like mountains, caves, towns. However we are only going to use the administrative baronies/objects (counties, baronies, civil parishes, EDs, townlands and sub-townlands). All of those (bar sub-townlands) are mapped in OSM as polygons. Subtownlands are points in OSM.

We have already manually added Logainm data to many high level objects in OSM. Townlands.ie provides analysis of these boundaries from OSM, and does spatial queries to "match up" an admin level with it's parent admin level. By using the logainm:ref tag of the parent OSM object, and the english name, we plan to find the corresponding logainm object.

OSM Data Files

This will be a semi-continuous upload, which will be intermittently rerun because the Irish mapping community is continuously adding new boundaries (about 100 per day), and later runs will process these new boundaries, and possibly tighten the code to cover more of the existing, unmatched, boundaries.

The first data change can be downloaded from here

boundaries.osm.xml is the existing data. It's a filtered set of data from the Ireland extract. created here, and new-boundaries.osm.xml is what would be uploaded. It's created here.

Generate it yourself

The code for processing it is on Github. You can download that code and create the data with these commands:

git clone https://github.com/osmie/logainm-osm-import
cd logainm-osm-import
make new-boundaries.osm.xml

That will download all the required data files. The Logainm data will not change (except in exceptional circumstances), the Irish planet file from [1] is downloaded and that updates every 15 minutes. The data extracts from Townlands.ie are used as well. Townlands.ie is a site created and maintained by User:rorym (this importer). It processes data from Ireland to match up the admin bounds with each other to produce a hiearchy that is used in this import script.

Import Type

The Irish OSM community is currently mapping townlands (etc.), and is about 80% done. We expect to be done in a year. Hence this will be a semi-continuous import process, which will be occassionally run to update the OSM data that has been added since the last run. New uploads will be manually run.

JOSM upload will be used.

Data Preparation

Data Reduction & Simplification

There is no need to simplify or reduce the data.

Tagging Plans

OSM Tag Source Justification
logainm:ref Logainm numeric ID Allows one to cross reference OSM data with Logainm at a later date
logainm:url Logainm numeric ID Allows one to easily get the URL of this object on Logainm.
name:ga Logainm Irish name If the object in OSM doesn't have an Irish name, we'll use the one from Logainm
name:en Logainm English name If there is no name:en for an object, we'll use the logianm one
official_name:en Logainm English Name If the name (or name:en) is different from logain, we'll use this as the "offical name"
official_name:ga Logainm Irish Name If the name:ga already in OSM is different from logainm, we'll use this as the offical name

Changeset Tags

We will add these changeset tags

Data Transformation

Code is hosted here, on the OSM-Ireland Github account

Data Transformation Results

new-boundaries.osm.xml from this zipfile

Data Merge Workflow

Since this import will only add tags to existing OSM objects (rather than add new OSM objects), there is no chance of duplication.

When looking at the OSM objects, which already has a (say) a name:ga tag, the software will defer to the exisiting OSM data.


OSM-IE has created Townlands.ie, which is used to help track mapping of townlands, and for QA of the mapped data. We can add features to this.