ok so i’m trying to understand the structure of the whole OSM project. i generally like it but it’s confusing and i’m confused.
i’m specifically looking for satellite image data (landscape as seen from above, no infrastructure data, just real photography). i like satellite images a lot because it provides a much better feel for the landscape than infrastructure data alone. such as: how many trees are there, how much nature is there around, …
does OSM itself do this? (ideally without having to be logged in)
i found OpenMapTiles which seems to also provide satellite data; but i’m not sure what their relation to OSM is. are they a separate project?




No, OpenStreetMap has no aerial imagery of their own.
Editors like iD and JOSM and end-user apps like OsmAnd rely on third-party imagery for over/underlays, and the most prominent among these is Bing.
OpenStreetMap under the hood is simply a database of key–value pairs assigned to nodes, lines, polygons, and “relations” between those three.
Edit: And yes, OpenMapTiles is a separate thing, and any of its aerial imagery would also not be its own. It’s prohibitively difficult for but a few select organizations to maintain aerial imagery like that. You can read more here.
yeah i suspected as much
so this might sound wild at first but i think it makes sense to compare the data structures of a project like OSM to a computer game like minecraft. basically, in the minecraft world, there’s 3 separate types of data storage:
I’ll read the link later, thank you.!
For OSM, such chunk storage might be considered a rendering. It could be akin to “converting” an SVG file to a GIF, with whichever anti-aliasing choices.
The most basic building block of OSM, the node, has only longitude and latitude. Few objects are tagged with ele or height, or other vertical tags (e.g. layer, building:levels, covered, incline, embankment, support).