3 ms·
I've migrated much of our mapping capabilities to MapBox's API.. but we're still facing mapping bills in the hundreds of dollars. My next step is going to be t
by blantonl 8y ago
I've migrated much of our mapping capabilities to MapBox's API.. but we're still facing mapping bills in the hundreds of dollars.
My next step is going to be to setup a caching Open Street Map tile server and using https://leafletjs.com/ https://leafletjs.com/ javascript library. The costs now for mapping solutions are going to drive us to run our own GIS infrastructure.
- Waterluvian 8y agoBe sure you've considered OpenLayers if you're going to be doing GIS and not just mapping. It's my go-to for the front end of all my Geomatics-Robotics tools.
- linsomniac 8y agoWe also looked at MapBox but ended up going with local tile server from OpenStreetMap data. We are using the geofabrik.de data bundles, mod_tile and renderd to serve up the tiles, and we pre-generate the tiles so all our requests are served from disk rather than being rendered (which really slows down mapping). We are lucky that we are only dealing with one state, so our data is around 25GB for map tiles and another 10GB for "street overlay" tiles that we lay on top of aerial tiles that we generate from NAIP data. We customized the CartoCSS a bit to get the maps closer to the way we wanted them. For example, we took out building outlines, and reduced the frequency of highway shields, which required removing exit numbers. It's a good solution for us, but we already had some mapping experience and lots of system deployment experience, so YMMV.