Wrong directions, given a roundabout way to a destination instead of a shorter direct way. It's very unreliable, especially when on a schedule for business Apple Maps simply cannot be trusted.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The (lack of) quality of Apple Maps.
- Thread starter IGI2
- Start date
-
- Tags
- apple maps google maps maps sygic
- Sort by reaction score
Okay, I get you
So you've probable acknowledged the topic and my issues, then go and check post by Mlrollin91 on 2nd page of this topic.Hah! Because you used it against your folder's name
There's been one place that's been bugging me - it's in Apple Maps and in one of the "other" mapping sources, and it just dawned on me yesterday when I was going to a job site of mine where all of this crap mapping information/data could be coming from.
Mapquest. Part of AOL. Owned by Verizon.
I do travel, here and abroad. I only care about getting where I want to go, and there's several places in my mind that just "stick" with me. One place, an island, is very near where my mom lives and also where one of my clients is. The misspelling of the island has just stuck with me, silly me. This thread, and all its whining (and I resemble that remark...) is spot on with several comments and observations. I made a correction request less than two weeks ago about the name of the island, which was showing up in Apple Maps as a "park" - and Apple fixed it last week. Yet, the misspelled name remained - Puget Island, nowhere near Seattle but named for the same explorer/mapper...
If you're familiar with AutoCAD and apps like that, you're familiar with "base maps" - referenced-in underlays upon which drafting is done but without altering the source base map. Often, it's up to the supplier of the base map to make alterations or the rest of the overlay will reflect the errors in the referenced-in underlying base map. I've been using AutoCAD for almost 30 years, and have been platting property for about 25 of those years.
Yesterday I was searching for a property and saw it for myself in Mapquest - Pugget Island, not Puget Island. Just as it appears in Apple Maps. Not in Google/Sygic/Bing/Here we are (ugh)/OpenStreet Maps.
Traveling about, routing in Mapquest was identical to Apple Maps. IMHO they're using the same trip routing company (these mapping suppliers buy recommended routes from companies that do this for a living, if you didn't know that already?). I'm seeing traffic data identical to TomTom's offerings, but with some overlay issues (I know Apple isn't getting their traffic info from INRIX - I work with them periodically).
Two iPhone screenshots, taken within the hour:
I've worked on GIS data on that island, and no source I work with (including the County) includes that misspelling. Notice how the tagged "Little Island" and "Pugget Island" are in the same relative and general geographical area - Mapquest Maps on the left, Apple Maps on the right. Notice how, in the Mapquest map that most of the data is in UPPERCASE letters and some of the data is in lowercase letters - it's pretty much the same in both mapping apps.
I compared these two apps in several locations that I'm familiar with, and the same GIS errors exist in both apps (desktop and mobile). AFAIK, Mapquest has generally kept their directions/routing API in-house (https://developer.mapquest.com/products/directions). To the users and non-US users of Apple Maps, I can only offer that I'd offer my mapping changes to both Mapquest and Apple, hoping that Apple cuts Verizon's Mapquest loose when their contract runs out...
Mapquest. Part of AOL. Owned by Verizon.
I do travel, here and abroad. I only care about getting where I want to go, and there's several places in my mind that just "stick" with me. One place, an island, is very near where my mom lives and also where one of my clients is. The misspelling of the island has just stuck with me, silly me. This thread, and all its whining (and I resemble that remark...) is spot on with several comments and observations. I made a correction request less than two weeks ago about the name of the island, which was showing up in Apple Maps as a "park" - and Apple fixed it last week. Yet, the misspelled name remained - Puget Island, nowhere near Seattle but named for the same explorer/mapper...
If you're familiar with AutoCAD and apps like that, you're familiar with "base maps" - referenced-in underlays upon which drafting is done but without altering the source base map. Often, it's up to the supplier of the base map to make alterations or the rest of the overlay will reflect the errors in the referenced-in underlying base map. I've been using AutoCAD for almost 30 years, and have been platting property for about 25 of those years.
Yesterday I was searching for a property and saw it for myself in Mapquest - Pugget Island, not Puget Island. Just as it appears in Apple Maps. Not in Google/Sygic/Bing/Here we are (ugh)/OpenStreet Maps.
Traveling about, routing in Mapquest was identical to Apple Maps. IMHO they're using the same trip routing company (these mapping suppliers buy recommended routes from companies that do this for a living, if you didn't know that already?). I'm seeing traffic data identical to TomTom's offerings, but with some overlay issues (I know Apple isn't getting their traffic info from INRIX - I work with them periodically).
Two iPhone screenshots, taken within the hour:
I've worked on GIS data on that island, and no source I work with (including the County) includes that misspelling. Notice how the tagged "Little Island" and "Pugget Island" are in the same relative and general geographical area - Mapquest Maps on the left, Apple Maps on the right. Notice how, in the Mapquest map that most of the data is in UPPERCASE letters and some of the data is in lowercase letters - it's pretty much the same in both mapping apps.
I compared these two apps in several locations that I'm familiar with, and the same GIS errors exist in both apps (desktop and mobile). AFAIK, Mapquest has generally kept their directions/routing API in-house (https://developer.mapquest.com/products/directions). To the users and non-US users of Apple Maps, I can only offer that I'd offer my mapping changes to both Mapquest and Apple, hoping that Apple cuts Verizon's Mapquest loose when their contract runs out...
Actually, the whole list of data providers can be found here (essentially, the About Maps page): http://gspe21.ls.apple.com/html/attribution-34.html
But I agree with your point: if Apple doesn't control the base map, it can't necessarily fix the issue itself. I think their goal is to insource as much of this info as possible, but since they are playing catch up, they had to outsource, with predictable consequences. They're improving, but, as was said earlier, if they aren't good in your locale, use Google.
I know that, I've read the list - to me, that list means nothing. Respectfully put, very much so, I've been in the civil engineering/surveying/GIS business for about 30 years and attributions are only a formality in most instances, often just a legal requirement. There's more than a few buildings and miles of my work showing up in those maps...
I've been notifying Apple of errors going back to iOS 6 Betas that still aren't showing up in Maps. My clients really only care about one thing - their POI can be found, and the route is accurate; pretty much the same gripes aired here in this thread (and in several of my related posts...). Now that I know it's Mapquest that's feeding Apple a lot of bad data, I get to sick a few agencies' dogs after them - somebody screwed up, and part of what I do (and those in my industry) is fix stuff like this. You're a consumer, I'm both a consumer and supplier of this data. To be fair to VZ, they've been pretty active lately with their updates but they still need to get after their base maps - I listed only one item, I found over 70 today in my work region. Cheers!
Can't speak to NV or AZ, but I live in Los Angeles and work in Orange County, and Haven't had any issues with Apple Maps since ~2012
I almost pointed this out in my preceding post, but it is possible that both Mapquest and Apple are deriving the erroneous info from a common source (perhaps one listed in the attributions page). Just trying to keep y ou out of trouble! ;-) (and congrats for your years in the business!!)
No worries. I never get in trouble, FWIW - I'm constantly bailing out my clients, counties and DOTs are on that list. I've notified Apple of a roadway that isn't lit but was breached by the Corps of Engineers 3 frickin' years ago - it's essentially "closed" but it's in a wildlife preserve that gets thousands of visitors each year - and it's still shown as "navigable" by Apple, while Google "fixed" it in 3 days. For those lovers of GMaps, I can pick them apart any day of the week too...
Apple-flavored lipstick on Mapquest Maps pig.
The source of this data is generally a local surveyor (PLS) and/or the local agency (the GIS staff for larger entities, or a civil tech). The PLS and GIS staff are supposed to verify *everything*, or they send me in to fix it. If it was one locale or county, the issue would be easy to fix or isolate, however, I work in the PNW and SW Canada and travel home to NY and visit several states and this kind of error is present in more than just my mom's beloved Wahkiakum County. I've referenced so many ESRI SHAPE files that I've had to block out (isolate) and edit, well, so many goofs going back years I'm considering starting a distillery and getting out of this business. :doh:
NO! I drive for a living in metro New York and Apple Maps is horrible. It would constantly have me make turns that are illegal or have me go up one way roads the wrong way. Example would be downtown Brooklyn Apple maps would have you making turns off Flatbush Ave that's illegal and impossible. How about Queens Blvd Apple maps does not know the difference between a main road and service road it thinks you can just make turns off the main road. Apple maps can get you killed in New York.
But if you read my entire posts you would know that I actually enjoy submitting changes, I posted screenshots before, that I added myself about thousand of POIs
It's very motivating when you see changes and you can use it.
I appreciate Apple Maps are improving, just saying, as the OP does, that we had already submitted corrections to Apple and they have not yet been implemented, in my particular case for over a year. And we are happy to contribute, Apple just need to act on it. I also do not think that Apple are interested in people using Google, as it will be going back to the initial Maps fiasco. So we all want the Maps to get better, we just need to find a way to crowdsource the road data/POI, as the roads and traffic conditions change super fast.
Just a little example from this morning. It is a major highway/motorway leading from Lyon (France) to Geneva (Switzerland). There was an accident that was first reported by Waze, instantly picked up by Google (no surprise), but totally skipped Maps, that was still considering there was nothing special going on (see the screen shots above).
But like one more said, we:
When it comes to the
It was probably mentioned on WWDC 2016, they don't want crowdsource data, they don't want any of your help because they count on.... AI.
Maybe later I will go through WWDC16 videos and find it, but he said sth like that:
"If there is a bridge closed, you don't need to tell us, it can be picked up by AI simply because no one will go through that bridge. That AI can act even if there was no reports at all, just by analyzing traffic."
Of course, less attended places or privacy concern may limit those AI capabilities but still.
It seems to be very dependent on where you are.
I'm in the UK, and for me, Google and Waze have been unreliable sometimes. For example, a bridge was closed near my house for repair and no traffic was allowed across it. However, Google and Waze both indicated that, while there was construction, the road was open and continued to route across the bridge. Only Apple Maps correctly knew the bridge was closed to traffic and routed around it.
I'm in the UK, and for me, Google and Waze have been unreliable sometimes. For example, a bridge was closed near my house for repair and no traffic was allowed across it. However, Google and Waze both indicated that, while there was construction, the road was open and continued to route across the bridge. Only Apple Maps correctly knew the bridge was closed to traffic and routed around it.
Major city in North East England.
https://1drv.ms/i/s!Ar9WGUSFwcSfgvcthWmUWp5hwMda4g
https://1drv.ms/i/s!Ar9WGUSFwcSfgvcsdnF4vd6wWZNMcA
https://1drv.ms/i/s!Ar9WGUSFwcSfgvcthWmUWp5hwMda4g
https://1drv.ms/i/s!Ar9WGUSFwcSfgvcsdnF4vd6wWZNMcA
Last edited:
Something is wrong with your pics. Or is it only my problem?Major city in North East England.
No they don't appear to be working. They are links from my OneDrive so no idea why they aren't working.
I've just edited them to see if that works.
I've just edited them to see if that works.
Well...I think as you can see from many responses, it is mostly "great" from a poi standpoint.
I do not use it for many reasons including bad routing options, visually difficult for me to read...I simply prefer Maps for the way it looks and operates...and the routes are awesome in my area.
I just wish its parsing and poi's were better...but they are WAY better than before and I haven't had any issues recently.
And that would be a very sensible answer if I could make Google Maps the default nav app.
I posted it in another thread I think, but there has been a new entrance to a major highway that has been in place for more than two years and causes people to turn across the main road to enter instead of just turning right into the entrance.
I've suggested the change multiple times.
Maps directs you turn left across the main road to enter.
Their own satellite image shows the new onramp that lets you just turn right to enter.
Well...the onramp is there now...but directions are still incorrect. Still says to turn left instead of right onto the onramp...getting there.
Sure wished there was a way to make Google Maps the default...this Apple Maps is a complete turd. My biggest peeve is when navigating to a large strip mall with several suites. Google will direct me directly to the front door of the suite....Apple? I get directed randomly to the middle of the parking lot. Just had this happen two times within the last week and on one instance, I had to drive back out into major traffic and around the building after being directed to a random parking lot next to the strip mall. Of course, both apps do this for indoor malls.
I'm also getting a lot of random turn and exit ramp instructions for no apparent reason. Couple weeks ago it directed me to an off ramp, through an intersection, and right back onto the expressway. Clear traffic. I've had at least five or six instances like this....
In my experience, Apple Maps in Asian countries (Japan, Taiwan) is really inconsistent and lackluster. Thanks God Apple allow you to turn of "English (Romanized) labels" otherwise it would be hell.
I also live in Poznan OP (apparently we live in the same place as I also shop in that Auchan).
I have submitted so many reports to fix POI's in Poznan and always thought I was the only one
I tried submitting changes to TomTom Map Editor, but it's utter garbage and no one actually approves the changes for months...
I have submitted so many reports to fix POI's in Poznan and always thought I was the only one
I tried submitting changes to TomTom Map Editor, but it's utter garbage and no one actually approves the changes for months...