3 ms·

I think an easy to setup self-hosted vector/tile server could help increase adoption. I'am currently looking into replacing Mapbox with a self hosted solution.

by adevx 6y ago

I think an easy to setup self-hosted vector/tile server could help increase adoption. I'am currently looking into replacing Mapbox with a self hosted solution. My last attempt ran out of disk space building the docker images (with european maps) from https://github.com/Overv/openstreetmap-tile-server https://github.com/Overv/openstreetmap-tile-server. Haven't found the time to setup a larger VPS but this looks like a great project to get started.

MattBlissett 6y ago
I use https://openmaptiles.org/ https://openmaptiles.org/ at work. For normal, Web Mercator maps we just use the free download of the whole world, available at [1]. Running the OpenMapTiles tools to generate a current tileset for a particular region is straightforward, but if you need all of Europe you will need some decent compute capacity. Unless everything can be done on a single computer, you'll also need to implement some missing pieces, e.g. a message system to distribute the rendering across your computers. [1] https://data.maptiler.com/downloads/dataset/osm/ https://data.maptiler.com/downloads/dataset/osm/
- adevx 6y ago
  Thanks, I looked into this but commercial use is prohibited for the free download which makes it a no go for my use case.
m4rtink 6y ago
There is the OSM Scout Server project, that makes it possible to download various OSM based data packs for offline use: https://github.com/rinigus/osmscout-server https://github.com/rinigus/osmscout-server Then it provides various services (routing, PoI search, geocoding, etc.) over this data set to all applications running locally on your machine. It targets mainly various mobile Linux distros but works perfectly fine on desktop as well and is available in flatpak form. Like this all navigation and mapping can share the same data set and no potentially sensitive location related metadata is leaked to a remote server other than what data packs have been initially downloaded. Also the community run infrastructure just needs to be able to store and store and distribute the ~150 GB of data packs covering Earth but does not need to have any extensive compute and memory requirements to handle lots expensive of individual API queries.

by adevx 6y ago

MattBlissett 6y ago

I use https://openmaptiles.org/ https://openmaptiles.org/ at work. For normal, Web Mercator maps we just use the free download of the whole world, available at [1]. Running the OpenMapTiles tools to generate a current tileset for a particular region is straightforward, but if you need all of Europe you will need some decent compute capacity. Unless everything can be done on a single computer, you'll also need to implement some missing pieces, e.g. a message system to distribute the rendering across your computers. [1] https://data.maptiler.com/downloads/dataset/osm/ https://data.maptiler.com/downloads/dataset/osm/

adevx 6y ago
Thanks, I looked into this but commercial use is prohibited for the free download which makes it a no go for my use case.

m4rtink 6y ago

There is the OSM Scout Server project, that makes it possible to download various OSM based data packs for offline use: https://github.com/rinigus/osmscout-server https://github.com/rinigus/osmscout-server Then it provides various services (routing, PoI search, geocoding, etc.) over this data set to all applications running locally on your machine. It targets mainly various mobile Linux distros but works perfectly fine on desktop as well and is available in flatpak form. Like this all navigation and mapping can share the same data set and no potentially sensitive location related metadata is leaked to a remote server other than what data packs have been initially downloaded. Also the community run infrastructure just needs to be able to store and store and distribute the ~150 GB of data packs covering Earth but does not need to have any extensive compute and memory requirements to handle lots expensive of individual API queries.