3 ms·

Does this do basically the thing as osmand on phones? Why the relatively huge requirements of 64G of ram and 10T of nvme?

quickthrower2 4y ago
Thats to build the server, any you are basically building the data for hosting approximately Google Maps for the entire planet here so seems relatively small really. 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.
- okasaki 4y ago
  But using it in a browser presumably downloads image tiles from the server. Osmand downloads vector data and renders it on the fly. It's both the "server" and the "client".
  - mnutt 4y ago
    The beefy server part is for taking the gigantic OSM world database and turning it into vector data that can be consumed by the client. I believe Osmand runs their own beefy servers to pregenerate vector data for download, though it’s also possible to use Osmand Map Creator to generate your own vector data on your desktop.
ellenhp 4y ago
Headway maintainer here. You don't need 10T of nvme storage unless you want to try and build tiles, a routing graph and a search index for the full planet without using a deduplicated filesystem. Eventually I hope to eliminate the need for deduplication but that's not currently a huge priority, since most Headway users don't run full-planet instances anyway. To my knowledge I'm the only one who does. Most people just run a smaller instance for their city. 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. :)

3 ms·

Does this do basically the thing as osmand on phones? Why the relatively huge requirements of 64G of ram and 10T of nvme?

by okasaki 4y ago

quickthrower2 4y ago
Thats to build the server, any you are basically building the data for hosting approximately Google Maps for the entire planet here so seems relatively small really. 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.
- okasaki 4y ago
  But using it in a browser presumably downloads image tiles from the server. Osmand downloads vector data and renders it on the fly. It's both the "server" and the "client".
  - mnutt 4y ago
    The beefy server part is for taking the gigantic OSM world database and turning it into vector data that can be consumed by the client. I believe Osmand runs their own beefy servers to pregenerate vector data for download, though it’s also possible to use Osmand Map Creator to generate your own vector data on your desktop.
ellenhp 4y ago
Headway maintainer here. You don't need 10T of nvme storage unless you want to try and build tiles, a routing graph and a search index for the full planet without using a deduplicated filesystem. Eventually I hope to eliminate the need for deduplication but that's not currently a huge priority, since most Headway users don't run full-planet instances anyway. To my knowledge I'm the only one who does. Most people just run a smaller instance for their city. 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. :)