Import/Catalogue/Japan KSJ2 Import/Administrative district 2014

From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Import/Catalogue/Japan KSJ2 Import/Administrative district 2014
· Afrikaans · Alemannisch · aragonés · asturianu · Aymar aru · azərbaycanca · Bahasa Indonesia · Bahasa Melayu · bamanankan · Bân-lâm-gú · Basa Jawa · Basa Sunda · Baso Minangkabau · bosanski · brezhoneg · català · čeština · corsu · dansk · Deutsch · eesti · English · español · Esperanto · estremeñu · euskara · français · Frysk · Gaeilge · Gàidhlig · galego · Hausa · hrvatski · Igbo · interlingua · Interlingue · isiXhosa · isiZulu · íslenska · italiano · Kiswahili · Kreyòl ayisyen · kréyòl gwadloupéyen · kurdî · Latina · latviešu · Lëtzebuergesch · lietuvių · Limburgs · magyar · Malagasy · Malti · Nederlands · Nedersaksies · norsk · norsk nynorsk · occitan · Oromoo · oʻzbekcha/ўзбекча · Plattdüütsch · polski · português · română · shqip · slovenčina · slovenščina · Soomaaliga · suomi · svenska · Tagalog · Tiếng Việt · Türkçe · Türkmençe · Vahcuengh · vèneto · walon · Wolof · Yorùbá · Zazaki · isiZulu · српски / srpski · авар · Аҧсшәа · башҡортса · беларуская · български · қазақша · Кыргызча · македонски · монгол · русский · тоҷикӣ · українська · Ελληνικά · Հայերեն · ქართული · नेपाली · भोजपुरी · मराठी · संस्कृतम् · हिन्दी · অসমীয়া · বাংলা · ਪੰਜਾਬੀ · ગુજરાતી · ଓଡ଼ିଆ · தமிழ் · తెలుగు · ಕನ್ನಡ · മലയാളം · සිංහල · བོད་ཡིག · ไทย · မြန်မာဘာသာ · ລາວ · ភាសាខ្មែរ · ⵜⴰⵎⴰⵣⵉⵖⵜ · አማርኛ · 한국어 · 日本語 · 中文(简体)‎ · 中文(繁體)‎ · 吴语 · 粵語 · ייִדיש · עברית · اردو · العربية · پښتو · سنڌي · فارسی · ދިވެހިބަސް

KSJ2 administrative boundary Import 2014 Plan Outline


Replacement of administrative boundary data on Japan. Target administrative levels are 4 - 8. (from Province to City/Town/Village, Suburb)

Why imports?

  • Most of administrative boundaries in Japan are broken since ODbL reduction.
  • Or some were not imported at all.
  • Most of administrative level 5-8 polygon was not created. (only place Node is written)
  • Old imported data contains too many redundant tags.
  • Remaining boundary data is very old (data created at 2007).
  • Remaining boundary data was not imported as Relation. And some boundary line data is missing, so could not fix Relation by manually.
  • Remaining boundary data do not have structured as established tagging scheme.

So I think replacement is the best solution for this activity.


New data will be released at the end of May. (convention of every year)

So actual import action is started at the beginning of June.

Import Data


Data source site:
Data license:
Type of license (if applicable): Same as "CC BY". And the data could be aquired from "" as CC BY 2.1ja. Also, OSMFJ made inquiry to Japanese gevernment agent in 2012.
Link to permission (if required):
OSM attribution (if required): -
ODbL Compliance verified: yes

OSM Data Files

Sample data is here (converted to .osm format using ogr2osm script.)

Import Type

This is One time import.

After import action is done, it is easy to modify even if some municipalities are consolidated.

Data Preparation

Data Reduction & Simplification


Tagging Plans

Original Shapefile

column_ref Attribute in Japanese Attribute in English OSM Tagging
N03_001 都道府県名 name of province/prefecture name=* for admin level 4 relation. (都道府県)
N03_002 支庁名 name of subprovince (for Hokkaido area only) name=* for admin level 5 relation.
N03_003 郡政令都市 name of county (郡) / city (市. for some big cities. which has suburb area) name=* for admin level 6 relation. (county)
name=* for admin level 7 relation. (city)
N03_004 市区町村名 name of municipality (市町村) / suburb (区. for some big cities) name=* for admin level 7 relation.
name=* for admin level 8 relation. (as suburb)
N03_005 成立年月日 start date of the municipality Do not use
N03_006 消滅年月日 end date of the municipality Do not use
N03_007 行政区域コード Reference number of the municipality. Do not use

Type of admin level

Admin_level Meaning Place tag
4 province, prefecture (都道府県) place=province
5 subprovince (振興局. Hokkaido area only) place=subprovince
6 county (郡) place=county
7 city(市), town(町), village(村) place=city, place=town, place=village
8 suburb(区) place=suburb
  • Detail & Sample

translated sample

Tags for Relation

samples are following

type = boundary
boundary = administrative
admin_level = [depends on each area]
name = [Column from Shapefile]
name:ja = [Column from Shapefile]
name:en = [Translation of Column from Shapefile]
name:ja_kana = [Hiragana writing of Japanese, from Column from Shapefile]
name:ja_rm = [Roman writing of Japanese, from Column from Shapefile]
source = KSJ2/N03

Tags for Way Object

boundary = administrative

Changeset Tags

source = KSJ2/N03
source_ref =

Data Transformation

using ogr2osm & manual modification.

translated sample

Data Transformation Results

see above.

Data Merge Workflow

Team Approach

Importing itself will be done by me (user:nyampire ).

Dedicated account is "KSJ2_adm_bnd_imprt".

Validating imported data will be done by me.


  • Deleting old boundary would be dangerous, possibly cause the coastline. So validation is mandatory after the deletion.
  • Existing place=* node would be added to the relation as member of "label" role.


Step by step instructions

  1. Convert the original shapefile to .osm format. Using ogr2osm script.
  2. Download old boundary Way (& Relation if any) with OverPassAPI.
  3. Delete old boundary Way objects. (Relations are remain)
  4. Import new Way data by JOSM. Chunk unit is each municipality.
  5. Integrate old & new Retations.
  6. When importing is done for one prefecture unit, extract those data using OverPassAPI.
  7. Stitch those ways where the ways are piled up. (if any)
  8. Go to next prefecture.

Changeset size policy

Upload per 1 municipality unit. Manually.

Revert plans

Revert using JOSM revert plugin.


See Workflow above.


JOSM validation to correct Relation structure.

OverPass API & Geofabric Japan Extract (with osmfilter) to extract data.