Open place data used by the Japan Homes map layers ================================================== Files in this folder ski-areas.json ski areas (one representative point per resort) surf-spots.json surf breaks: a hand-checked selection of well-known breaks, not a complete list national-parks.json 35 national and 58 quasi-national parks: a marker point each, plus a simplified outline (g) for the 35 national parks (approximate) onsen.json onsen (hot-spring) towns: one point per onsen town, not per bath volcanoes.json the 111 active volcanoes (活火山) listed by the Japan Meteorological Agency; mon=1 marks the ones JMA lists as continuously monitored stations.json open train, metro and tram stations in Japan with a rough service level (1 quiet - 4 major hub) transport-hubs.json airports with scheduled passenger flights, shinkansen stops, expressway interchanges and service/parking areas (one point each) golf-courses.json golf courses (one point per course; driving ranges and practice greens removed) beaches.json named beaches and swimming areas (one point each; a partial list) harbours.json named marinas and fishing ports (one point each; partial) hiking-trails.json named hiking trails (simplified lines) and trailhead points cycling-routes.json named cycling routes (simplified lines) amenities/ convenience stores and supermarkets, split into small map cells Licence The ski, surf and amenity files contain information from OpenStreetMap, which is made available here under the Open Database License (ODbL) 1.0: https://opendatacommons.org/licenses/odbl/1-0/ © OpenStreetMap contributors, https://www.openstreetmap.org/copyright Each of those files is a derived database and is offered under the same licence (ODbL 1.0). You may copy, adapt and reuse it under those terms, keeping the credit above and offering any adapted version under the ODbL. Names and websites in the ski file, and English names and codes in the transport file, also come from Wikidata (CC0 1.0). Nothing else on this site is covered by this licence. Listing counts shown next to a place ("N homes within 15 km") are calculated in your browser and are not part of these files. How the ski file is built node ops/build-ski-areas.js (ops/places/ in the project repository) It reads OpenStreetMap through the Overpass API (landuse=winter_sports areas, aerialway lifts, administrative areas), Wikidata for English names and websites, and uses a public list of closed resorts only to leave closed ones out. The OSM data timestamp is recorded in each file's _meta. How the onsen file is built node ops/build-onsen.js (ops/places/onsen-*.js in the project repository) The unit is the onsen town (onsen-chi). A town is listed when Wikidata has a hot-spring item with coordinates, when OpenStreetMap maps a named onsen place node (names ending 温泉 / 温泉郷 / 温泉街 ...), or when two or more OpenStreetMap public baths (amenity=public_bath, bath:type=onsen or 温泉 in the name) share an onsen name. "baths" is the number of such OSM baths within 2.5 km: a minimum, since OSM coverage of baths is partial. English names come from Wikidata and OSM name:en and are missing for many small onsen. Prefecture and municipality come from Wikidata (located-in chain) or OSM administrative areas. Anything OSM sources from MLIT National-Land Numerical Information (a non-commercial dataset) is dropped, and the Ministry of the Environment onsen statistics are not used (they are prefecture totals, with no locations). How the surf file is built OpenStreetMap tags very few surf breaks in Japan, so this layer is an editorial selection: each break needs at least two independent public sources (one of them not a surf database), and its position is taken from OpenStreetMap (a named element or the nearest coastline point), accurate to roughly a beach. The list lives in ops/places/surf-curated.json; node ops/build-surf-spots.js writes the file. How the transport hubs file is built node ops/build-transport-hubs.js (ops/places/transport-fetch.js fetches; both in the project repository) Source: OpenStreetMap through the Overpass API, English names from Wikidata. No MLIT (国土数値情報) data is used. a airports: aerodromes with an IATA code, minus military-only fields and a short list (kept in the build script, each with its reason) that have no scheduled passenger flights s shinkansen stops: stations on Shinkansen route relations; the Yamagata and Akita mini-shinkansen stops are flagged mini i expressway interchanges: motorway_junction nodes named as interchanges (incl. smart ICs); per-direction ramps are merged into one point; junctions (JCT) are left out p expressway service and parking areas (k: SA, PA or HO for highway oasis), merged the same way Coverage is whatever OpenStreetMap maps, so some English names and a few minor ICs may be missing. In the map, "N homes within X km" uses 50 km for airports, 30 km for shinkansen stops and 10 km for interchanges and service areas; the number is calculated in your browser. How the lifestyle files are built (golf courses, and later beaches, harbours, routes) node ops/places/lifestyle-fetch.js one polite Overpass query per feature family (cached, 3 s gaps) node ops/build-golf-courses.js leisure=golf_course; unnamed objects, driving ranges, mini golf and areas under 350 m across are dropped; the same course mapped twice is merged. English names are only the ones OpenStreetMap carries (about one course in four), the rest show the Japanese name. Coverage is roughly 1,800 of Japan's ~2,100 courses; closed courses may remain and new ones may be missing. node ops/build-beaches.js natural=beach, leisure=beach_resort, leisure=swimming_area; only named beaches (about a quarter of mapped beaches), non-beaches and scraps under 40 m dropped, node+area duplicates merged. t = s marks a bathing beach by name (海水浴場) or tags (beach resort, swimming area, lifeguard/supervised). That is a mapping signal only: it says nothing about water quality, opening dates or safety. node ops/build-harbours.js leisure=marina plus harbour objects (landuse=harbour, harbour=yes, man_made=harbour, seamark) that are fishing ports by name (漁港) or tag (harbour:category=fishing); unnamed objects, angling spots (leisure=fishing) and 漁港 names on bus stops or roads are dropped; the same port mapped twice is merged. t = m marina, f fishing port. Partial: about 400 of Japan's ~2,800 fishing ports are named and mapped in OpenStreetMap. A point does not mean public fishing, mooring or boat access is allowed. node ops/places/lifestyle-fetch.js routegeom && node ops/build-routes.js Hiking: route=hiking relations of the nwn/rwn/lwn networks, cycling: route=bicycle relations of ncn/rcn, named only (lcn, the municipal local network, is not taken). Relations with the same name are merged (long trails are often split into dozens), way members chained, simplified to about 50-60 m and rounded to 4 decimals; fragments under 2 km (hiking) or 4 km (cycling) dropped. Trailheads: named highway=trailhead nodes (about 180 in all of Japan). Each row keeps its OpenStreetMap relation id (osm). Coverage is uneven (Kanto and Kansai are good, much of Hokkaido/Tohoku/Kyushu is thin), the lines are for orientation only and not for navigation, and conditions, closures and permits are not shown. Corrections The best fix is in OpenStreetMap itself. For anything else write to admin@star.computer. National parks file: different source and licence national-parks.json is NOT OpenStreetMap data. Outlines and park facts come from the Ministry of the Environment, Japan (Biodiversity Center, https://www.biodic.go.jp/), used under the Public Data License v1.0 (https://www.digital.go.jp/resources/open_data/public_data_license_v1.0). The outlines were merged and simplified (to about 150 m) by Japan Homes; they are approximate and not an official government product. Marker positions are from Wikidata (CC0 1.0). Rebuild: node ops/places/moe-parks.js then node ops/build-national-parks.js. Volcanoes file: different source and licence volcanoes.json is NOT OpenStreetMap data. Names, positions, elevations, the continuous-monitoring mark and latest eruption years come from the Japan Meteorological Agency (気象庁) regional active-volcano pages (https://www.data.jma.go.jp/vois/), used under the Public Data License v1.0, which is compatible with CC BY 4.0 (https://www.jma.go.jp/jma/en/copyright.html). Japan Homes selected fields, kept one position per volcano and translated labels, so the file is edited material: it is not an official JMA product and JMA does not endorse it. Wikidata item ids (wd) are CC0 1.0. What it is not: it is not an eruption forecast, not a hazard map and not a warning. It holds no eruption alert levels (噴火警戒レベル), which change without notice; read the current level on the JMA site (https://www.jma.go.jp/bosai/map.html#contents=volcano). The "homes within 15 km" figure on the map is a plain distance from the summit, not an evacuation or hazard zone. Positions are JMA's, to 0.01 degree (about 1 km). Hazard-map polygons (火山防災マップ, alert-level zones) are not included because no polygon set with an explicit reuse licence was found. Rebuild: node ops/places/jma-volcanoes.js (optional refresh, 7 fetches) then node ops/build-volcanoes.js. Stations file: rough service level, and what was not used stations.json is built from OpenStreetMap (ODbL 1.0; railway=station / halt / tram_stop; disused, abandoned, proposed and historic features are skipped, so closed lines do not appear) and Wikidata (CC0 1.0: English names and daily passenger counts, property P1373, latest year since 2000). Fields: n, ja = names; op = operator; k = kind (S shinkansen stop, J JR, P private / third-sector, M metro, T tram / monorail / light rail / funicular); ln = line (network tag); pax, py = daily passengers and their year; d = on non-electrified track; lv = ROUGH service level 1-4 (pax >= 50,000 / 10,000 / 2,000 / less; with no count: shinkansen 4, metro 3, tram 2, else 1). It is a guide to how busy a station is, not a timetable. No trains-per-day data is included: no national, openly licensed frequency source exists (GTFS-JP feeds are published bus-first with per-publisher licences, ODPT data needs a key and has its own terms) and timetables were not scraped. The MLIT 国土数値情報 railway dataset (N02) was not used. Rebuild: node ops/places/stations-fetch.js && node ops/places/stations-wd.js && node ops/build-stations.js "Homes within 2 km" and "nearest station" are computed in your browser and are not part of this file.