Data sources and attribution#
OWRT separates provider access, transient scene geometry and rendered results. The repository contains source code and a small test fixture only; it does not redistribute a national building, terrain, imagery or transmitter dataset. Adding a provider does not transfer its licence to another provider or to the project.
Role |
Source |
Licence and attribution |
|---|---|---|
Buildings and semantic surfaces, worldwide |
Overture Maps (latest release via the official STAC catalog) |
Overture Maps Foundation plus the upstream sources recorded per release |
Building fallback, location search, base map |
OpenStreetMap (Overpass, Nominatim, tiles) |
© OpenStreetMap contributors, ODbL |
Buildings, Netherlands |
3DBAG LoD2.2 |
© 3DBAG by tudelft3d and 3DGI, CC BY 4.0 |
Buildings, Berlin |
Berlin LoD2 CityGML |
Geoportal Berlin / 3D-Gebäudemodelle LoD2 |
Buildings, Boston |
BPDA OBJ 3D models |
Boston Planning and Development Agency |
Terrain, United States |
USGS 3DEP Bare Earth DEM Dynamic |
Public domain; credit to the U.S. Geological Survey requested |
Terrain, global fallback |
Mapzen Terrain Tiles (Skadi HGT) on AWS |
Location-dependent upstream attribution recorded per tile |
Display terrain in the explorer |
Mapzen Terrain Tiles (Terrarium PNG) on AWS, read by the browser |
Same attribution, shown in the map credits; display only |
Detailed provider notes, the Overture surface-classification precedence and the road-width assumptions are kept in [DATA_SOURCES.md](https://github.com/zhiheng-yang/openworld-radio-twin/blob/main/DATA_SOURCES.md) in the repository. The material proxies assigned to surface classes are listed in Surfaces and materials.
Usage rules for the public endpoints#
Nominatim: at most one request per second; repeated results must be cached.
OSM tile service: interactive use only, no bulk download or offline prefetch.
Overpass: best effort; deploy a private instance or another provider for sustained use.
Overture: cloud reads are bounded to the active viewport or simulation area; source data is cached in application memory only.
What generated data must retain#
Generated datasets should keep their terrain/scene_info.json, source_buildings.json and
provenance.json, since the applicable upstream licences depend on the queried release and
location. Every record includes the release, upstream record IDs, update time and licence
where the source provides them. Mapzen terrain requires the applicable regional attribution;
Overture data must not be treated as one universal licence.