Earlier quoted context omitted.
With auto-discovery of routes, Google might be picking up the most popular routes, but that does that does not mean they are the best ones. For example, on Strava heatmaps you can frequently see routes that are heavily cycled, but they might also be extremely stressful because one has to share the road with traffic. In fact, most cyclists might only be using them because they are sports cyclists with very thin tires…
Funny you should mention Albania: It's exactly where I learned never to doubt Google Maps. Specifically, never to assume that "It's like ten meters between these two points... I don't see a reason why we would need to go all the way around". (There was a 30m deep gorge) More to the point: Given enough position data, Google should be able to assess all those road parameters you mention, far better than manual entry co…
How Facebook, Apple and Microsoft Are Contributing to OpenStreetMap
81–90 of 177 posts
Re: How Facebook, Apple and Microsoft Are Contributing to OpenStreetMap
#82Re: How Facebook, Apple and Microsoft Are Contributing to OpenStreetMap
#83Earlier quoted context omitted.
Our traffic data is generated in house using anonymized location telemetry from our SDKs, much like most other traffic providers. The live speed predictions we generate for congestion and ETA models are competitive globally, providing the most accurate ETAs available in many parts of the world. Our accuracy today is particularly strong in the US, when compared to similar services.
Do you know if Mapbox has any plans to work with the World Bank's OpenTraffic[0]? [0]: http://opentraffic.io
Aspects of the model like noise reduction, modality classification, and speed distribution estimation also require lots of fine tuning that is specific to the telemetry being ingested & the usage patterns of the output. For example, our speed models learn and correct from observed errors in various situations over time, which is coupled to our internal metrics data.
Re: How Facebook, Apple and Microsoft Are Contributing to OpenStreetMap
#84This is competitive pressures at work, similarly to IBM and other's investment in Linux in the early 2000's as a way to place competitive pressure on MS/Windows. If you're not the leader in the field, and won't be able to catch up just by investing, you try to make the leadership in the field (Google's) irrelevant. If the 2nd-best-by-small-margin base map info is open, having the best one isn't a competitive advantag…
Second best? At least in my experience, OSM data is leaps and bounds better than Google Maps in every way possible, and it has been that way for a couple years now. The reason that I still use Google maps is that it's fast and well-integrated with my phone, and it has a lot of added features on top of the actual mapping that makes it very useful --- things like location sharing when you're on a longer road trip, crea…
Re: How Facebook, Apple and Microsoft Are Contributing to OpenStreetMap
#85This website is under heavy load (queue full) We're sorry, too many people are accessing this website at the same time. We're working on this problem. Please try again later.
Re: How Facebook, Apple and Microsoft Are Contributing to OpenStreetMap
#86Earlier quoted context omitted.
> I'm saying that OSM data is objectively better for the rural parts of the world I've been to. Which is a subjective factor. "X is objectively better for the categories that I subjectively selected". Mapping is a subjective topic, simply because there are endless ways to evaluate and compare maps, so attributing any type of weight to any factor is a subjective exercise based on your own personal preferences.
I'll agree that what layers a map ought to show is a subjective matter. But if you have two maps and they both have a shared subset of layers, you can (for that subset) objectively evaluate which map more accurately represents the real world, eg: has more objects than the other map, and/or has objects marked more accurately. And what I'm saying is that for the layers that they have in common, I think OSM wins hands d…
Re: How Facebook, Apple and Microsoft Are Contributing to OpenStreetMap
#87Earlier quoted context omitted.
Do you have a source? I'd be interested to look at the work they're doing.
https://github.com/osmlab/appledata
> The building information was developed with sensors from low altitude aerial imagery.
> The building footprint and height information was captured and developed in 2013.
There's also Atlas[0], not mentioned in the article, which seems to be a (open-source/non-free??[1]) tool released by Apple for use specifically with OSM data. Really interesting stuff.
Re: How Facebook, Apple and Microsoft Are Contributing to OpenStreetMap
#88Earlier quoted context omitted.
Here at Mapbox we're doing navigation on OSM with traffic data - we collect our own telemetry, and use it to guide OSM-based routing. There are numerous Android/iOS apps using our API that you could use, or you could build one yourself.
I've been wondering, given that you've made all of the building blocks, why hasn't Mapbox built and released an open source maps app for Android? It looks like you're just weekend's work away from having an open source app which is competetive with Google Maps on F-Droid.
Re: How Facebook, Apple and Microsoft Are Contributing to OpenStreetMap
#89Earlier quoted context omitted.
Here at Mapbox we're doing navigation on OSM with traffic data - we collect our own telemetry, and use it to guide OSM-based routing. There are numerous Android/iOS apps using our API that you could use, or you could build one yourself.
I've been wondering, given that you've made all of the building blocks, why hasn't Mapbox built and released an open source maps app for Android? It looks like you're just weekend's work away from having an open source app which is competetive with Google Maps on F-Droid.
Re: How Facebook, Apple and Microsoft Are Contributing to OpenStreetMap
#90Earlier quoted context omitted.
Here at Mapbox we're doing navigation on OSM with traffic data - we collect our own telemetry, and use it to guide OSM-based routing. There are numerous Android/iOS apps using our API that you could use, or you could build one yourself.
I've been wondering, given that you've made all of the building blocks, why hasn't Mapbox built and released an open source maps app for Android? It looks like you're just weekend's work away from having an open source app which is competetive with Google Maps on F-Droid.