Host your own OpenStreetMap Map Tiles
altilunium.my.id
altilunium.my.id
They convert Planet OSM and Natural Earth OSM dumps into the storage format used by their geospatial DB [1] and then distribute them using P2P file storage tools like IPFS [3] or hyperdrive [4].
Because those storage tools make use of content addressing [5] and clever chunking [6], you can download only changes to the (converted) OSM dump.
Because those tools are inherently P2P-focused and come with pluggable transports, the data representing the changes in the (converted) OSM dump don't have to be sent via the internet. For example, Mapeo [7] allows syncing "local" changes to OSM via USB sticks [8].
[1] https://github.com/peermaps/eyros [2] https://github.com/peermaps/data [3] https://ipfs.io/#why [4] https://hypercore-protocol.org/guides/modules/hyperdrive/ [5] https://docs.ipfs.tech/concepts/how-ipfs-works/#content-addr... [6] https://blog.gopheracademy.com/advent-2018/split-data-with-c... [7] https://www.digital-democracy.org/mapeo/ [8] https://docs.mapeo.app/complete-reference-guide/mapeo-deskto...
Peer maps seems to store the entire dataset in a single 107 GB file [1]
It's unclear to me that that eyros produces a file that doesn't change dramatically when data is inserted or removed.
It seems they are doing full imports, which likely means the output file could be completely different, meaning no shared chucks across generations.
In order to make IPFS actually create sharable chunks takes considerable effort, and is not as magically as their documentation and marketing would lead you to believe.
[1] https://bafybeidf5yn56cxk6zkyjmay4wigu2o7ynqh7q62z3kppag5v7j...
Because it's hard to lock down tile servers for public-facing apps, I have always been a bit nervous putting anything online in case someone swipes my key and uses it and one morning I wake up to a huge bill.
For giving back to the community, you can share your proxy server with others.
It’ll do it on what is basically a beefy dev machine. You can host a single city with less.
Also the requirements are for build not hosting. And can be reduced by using ZFS. Apparently.
To use the map in the browser requires nothing special.
Osmand downloads vector data and renders it on the fly. It's both the "server" and the "client".
It's not the same as OsmAnd obviously because it runs in the browser but it does try to fill the same niche. Also 64G of RAM for building the planet is a tiny machine! We don't know how good we have it these days. This used to be completely intractable for mere mortals. :)
Zoom level 20 is over a trillion tiles, most of them worthless blue sea tiles. We’re probably talking hundreds of terabytes just for the file system metadata, to say nothing of the tiles themselves.
Of course, you could forego the ability to zoom in very far.
I'm sure there are newer solutions out there, which might have more features and are actually maintained. But this did (and still does) the job.
I serve the tiles using TileServer GL Light. It works but it requires Node.js v10.
OpenStreetMap is planning to make their own vector tiles style to convert their raster tiles. Looking forward to that! https://github.com/openstreetmap/operations
https://github.com/protomaps/PMTiles/blob/master/js/package....