SEOUL 3D ATLAS — DATA AND SOFTWARE ATTRIBUTIONS

Map geometry and buildings: © OpenStreetMap contributors, made available through OpenFreeMap and OpenMapTiles.
OpenStreetMap data is available under the Open Database License (ODbL) 1.0:
https://www.openstreetmap.org/copyright
https://opendatacommons.org/licenses/odbl/1-0/
This derived map database is offered under ODbL 1.0 as well. The processed vector snapshot is 2026-08-30.
Download /data/seoul.json, /data/buildings.bin and /data/trails.json to obtain the derived data.
Riverside activity v1.8: /data/traffic-routes.json and
/data/han-river-centerline.json are additional derived ODbL 1.0 data assets.
OpenStreetMap / Overpass snapshots: 2026-09-09T02:34:00Z (roads) and
2026-09-09T02:38:16Z (river). Ordered WGS84 coordinates, way IDs, source tags
and provenance are retained. Road directions follow oneway=yes source order;
main carriageways join at identical OSM nodes. The river centerline is a
clipped part of OSM way 378066781, not a surveyed navigable channel.
Building facades, passengers, vehicles, boat models and motion are original
procedural miniature artwork. Window layouts and actor positions are scenic,
not surveyed facade records, real vessel positions or live traffic data.
Mountain forests v1.9 use the existing attributed terrain and map data with
deterministic illustrative placement. Tree density, model types, flowering,
foliage, autumn colors and winter branches are original procedural artwork,
not surveyed tree locations, species, counts or live seasonal observations.
The binary building format is little-endian float32: [x_km, z_km, width_km, depth_km, angle_radians, height_m], repeated for each building.
Projection origin and coordinate scale are in seoul.json meta. Building heights can be source estimates; footprints are simplified oriented boxes.

District boundary source: southkorea/seoul-maps / Statistics Korea (KOSTAT), 2013.
https://github.com/southkorea/seoul-maps
Historical boundaries are shown as optional reference boundaries.

Elevation: Mapzen / AWS Terrain Tiles.
Global ETOPO1 terrain data: U.S. National Oceanic and Atmospheric Administration.
Global GMTED2010 and SRTM terrain data courtesy of the U.S. Geological Survey.
https://registry.opendata.aws/terrain-tiles/
https://github.com/tilezen/joerd/blob/master/docs/attribution.md
Elevation is smoothed, shorelines are flattened for display, and vertical scale is exaggerated by 4.

Three.js r180 / OrbitControls — MIT license follows.

The MIT License

Copyright © 2010-2025 three.js authors

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

Hiking overlay v1.7: © OpenStreetMap contributors, ODbL 1.0.
Source: Overpass API snapshot 2026-09-08T05:36:51Z.
https://www.openstreetmap.org/copyright
https://overpass-api.de/
Coverage: longitude 126.70–127.35, latitude 37.25–37.85.
804 mapped peaks, 13,719 mountain walking/hiking way sections, 1,595 computed
connected summit approaches. Coordinates and way IDs are retained in trails.json.
Sections are geographically grouped around peaks; groups overlap. Public path,
footway, steps and track ways are filtered by mountain proximity and elevation.
Private/prohibited, conditional-access, informal and area features are excluded.
Summit approaches are shortest paths along connected mapped pedestrian edges,
not official designated courses. Start/finish markers identify actual polyline
endpoints. A connection may end near a summit rather than at the peak node.
Mapped distance is horizontal polyline length, not an on-site measurement.
Unmapped trails, changes, hazards and live access restrictions are not complete.
Additional outer terrain/water uses the same attributed elevation/vector sources.