31–40 of 60 posts
Earlier quoted context omitted.
We build a data store for municipal governments, we have a very light weight data viz tool that allows municipal workers to view the data on a map: http://john.je/mzHm
And why didn't you do it in an open standard data format and just present it on Google Maps?
Congrats to the Mapbox guys. Always looked like a cool team. However personally I'm not sure it's a business case that will survive the time. But doesn't matter, with that kind of investment and their current track record they probably live 10+ years, which is well enough in times like these.
Why not? Some companies don't want to host their own tiles server
Earlier quoted context omitted.
We build a data store for municipal governments, we have a very light weight data viz tool that allows municipal workers to view the data on a map: http://john.je/mzHm
And why didn't you do it in an open standard data format and just present it on Google Maps?
My main gripe with Mapbox and perhaps it's something that's been fixed recently? Is that you could never force place names to English whe available. So if you're making a map of Tourist map of thailand then the default for all places will obviously be in Thai, if you want to use the English translations which is in the underlying OSM data you can't. But you can if you roll your own...
My main gripe with Mapbox and perhaps it's something that's been fixed recently? Is that you could never force place names to English whe available. So if you're making a map of Tourist map of thailand then the default for all places will obviously be in Thai, if you want to use the English translations which is in the underlying OSM data you can't. But you can if you roll your own...
Mapbox is an amazing product, it's super expensive and pretty hard to swallow the bill every month as a small startup, but the product is just so good, their APIs are fantastic. For sure a company to watch, their COO Roy was the COO of Twilio and he knows what he is doing.
My main gripe with Mapbox and perhaps it's something that's been fixed recently? Is that you could never force place names to English whe available. So if you're making a map of Tourist map of thailand then the default for all places will obviously be in Thai, if you want to use the English translations which is in the underlying OSM data you can't. But you can if you roll your own...
Change it to `{name_en}` in your style for place labels, and you'll get English-script names where available.
Earlier quoted context omitted.
Can you name a few usecases where you would pay them? Doesn#t have to include your own.
We build a data store for municipal governments, we have a very light weight data viz tool that allows municipal workers to view the data on a map: http://john.je/mzHm
My main gripe with Mapbox and perhaps it's something that's been fixed recently? Is that you could never force place names to English whe available. So if you're making a map of Tourist map of thailand then the default for all places will obviously be in Thai, if you want to use the English translations which is in the underlying OSM data you can't. But you can if you roll your own...
The `{name}` field that's the default for most place labels in styles is the "local name", in the local symbol system. Change it to `{name_en}` in your style for place labels, and you'll get English-script names where available.