One more note related to my earlier
post in this thread. To me, a notable note. Elsewhere in these Forums I'd mentioned AM routing errors in a few regions, specifically related to roadways that had been closed - this post is related to a roadway section that had been demolished by the Corps of Engineers, a breach of a failed bridge that was not and has not been replaced (to the chagrin of local residents). I took a few screen shots but friends with a bottle of Scotch showed up...
My point in this post is that, at least in the geographic area in my earlier post in this thread, AM is using a different routing engine. Think of routing as a layer in an Illustrator file, with companies that do this sort of work providing data that resides on a dynamic layer in that AI file - TomTom's routing companies are IMHO some of the worst or laziest in the industry, at least here in NA. So, building on my earlier post and leaning on MR's Forums as a reference, AM's routing engine appears to me to have been changed in part of the PNW - not the route suppled to TomTom's routing company, rather, the routing "engine" and/or the company that supplies routing to Apple for AM.
Specifically, a section of a roadway was breached by the Corps around 3-4 years ago. If you wanted to drive/bike/walk from Skamokawa WA to a nearby location, AM/TomTom would route you via the roadway that had been closed due to the breach (a completely removed bridge with around a 1000-foot-long breach subject to 10-foot tidal swings in a 12-hour period, with signage but no roadway lighting to indicate the breach). If I - or a visitor to this area dialed in how to get from/to Skamokawa to a point on a nearby island, AM routed the navigator directly across the breach - which I've railed about here in these Forums - until today (yesterday, rather - the Scotch ran out, and so have my friends...). To wit, the following 3 screen shots from my iP6S+:
The three apps are, from left to right - MapQuest, Apple Maps, and Google Maps - taken within a couple of minutes of each other a few hours ago. Some 3-odd years ago I'd notified Apple and TomTom of the aforementioned roadway closure - and so did the County, WA State, and the Corps of Engineers - to no avail. That same day, I passed on the closure to Google - they noted the closure (in their routing "engine") within 48 hours. While killing time, relative to my earlier post, it led me to the above screen shots showing that Apple -
FINALLY - is routing around the breached roadway section.
Above, MapQuest's "Route 1" leads directly across the roadway closure. Apple Maps reflected the same routing options until a week or so ago, the failed route is mentioned in earlier/older posts in these Forums, but now and within the past 48 hours is showing similar options as Google Maps - around the breach. I'm offering "similar" and not "same" solely due to the estimated time shown in the screen shots for the secondary route - 14 minutes in AM compared to 9 minutes in GM; the 14 minutes is more accurate for this very narrow and winding roadway I'd compare to what I've driven in Northern Ireland and backroads in eastern Germany near Marktredwitz and Sommerhau, while that 9 minutes shown in GM is a bit optimistic even with me driving my E63... My point in this is that, if AM were using the same routing engine as GM, the driving times would be very similar or identical. AM is finally reflecting the correct route options (after about 4 years) but not the same routing data as GM, while TomTom via MapQuest is still reflecting incorrect routing in its primary routing option - it's a
nasty drop into the Columbia River onto riprap and pretty fast moving water...
More progress by Apple on this front, at least in this area and IMO, from a mapping geek. I'm heading to Skamokawa (in those screen shots) in about 6 hours for a project meeting. I know which road I'm not taking...