Let me rephrase it a bit; Apple received their map data set from TomTom. This does not mean they're still current with TomTom. It's still sorta useful to look at their livetraffic map to see if it's an existing problem without having to open Apple Maps on an iDevice and scroll around/search.Dave2084 wrote:bgodette wrote:For NA, Apple Maps uses map data from TomTom. So you can look at the same area using http://www.tomtom.com/livetraffic/
Not quite the case. In my OP, the A46 was opened on 1 Dec 2011, and appeared in Waze about a week later. It appeared in Tomtom in Dec 2012, but is still not in apple maps.
Well yeah. But the same thing may apply, it may have been a one time sale.Dave2084 wrote:Something else that occurred to me is the reason the Waze staff may have not seen this issue previously is that in Israel Apple maps are based on Waze rather than tomtom (according to the iOS6 credits).
bgodette wrote:For NA, Apple Maps uses map data from TomTom. So you can look at the same area using http://www.tomtom.com/livetraffic/
For NA, Apple Maps uses map data from TomTom. So you can look at the same area using http://www.tomtom.com/livetraffic/CBenson wrote:My understanding is that we will continue to see problems from this at least "until the next major release." Can I attribute MPs like these to this issue? Is there an easy way for non-Apple users to know where iOS device tracks are likely to snap to?
Here is what I think happens: Unlike it predecessors iOS 6 has direct access to map data. Once iOS detects you are going faster than a certain threshold (in my testing around 20 mph), it will correlate your GPS data with the location of a nearby street running in parallel to your actual track. I presume this was implemented to improve the turn-by-turn navigation experience for car drivers, in case where the received GPS signal is slightly off.
In theory, this might be a good optimization. However, when used in combination with the map data on iOS 6, it makes accurate GPS recordings impossible in areas where street data is less than perfect.
I was contacted by the developer of another GSP related fitness app. He suggest that Strava simply forgets to set CLActivityType on iOS 6 to CLActivityTypeFitness. Without a correct type being set, Apple guesses and assumes an automotive activity beyond a certain speed threshold.
Users browsing this forum: Baidu [Spider], Bing [Bot]