All Devices Updated Apple Maps

[tylert120]

Hi everyone...new here. But I’m a huge GIS and mapping person, and probably have submitted thousands of error reports to the Maps team since it’s inception. I was excited for the revamped Maps, and it finally came to the Pittsburgh area several weeks ago. Though my observations though, it’s not all it’s chalked up to be. Over all the maps are better, but I think they need more improvement. They took certain detail away that needs to be brought back.
cemetery
This local cemetery is no longer shaded in gray, like cemeteries are supposed to be.

shopping centers
These two shopping centers have lost their yellow shading.

library / high school
Certain POIs have moved. For example, the library and high school POIs have completely been moved away from the building. They were previously correct. I have since reported them and Apple fixed these issues.

roads before / roads after
Before/after screen shot. Notice many of the main roads lost their yellow or bold shading. This makes roads hard to identify unless you are zoomed in very far. This is one of my biggest issues with the new maps.

I’ve since done some more looking around town. I’ve found several other cemeteries and shopping centers that were originally shaded correctly on the former version of maps which have now lost their shading.

-Cemetery and shopping plaza
-Two very large cemeteries. Interestingly, the POI for the southern location there has completely been removed from maps
-Smaller cemetery
- Shopping center

 

[iOS Geek]

Whoa...I noticed that last night when I was driving home. I had to switch to Waze because it was too bright (was a dark and stormy drive). I'd say it was a bug. I swear it went into dark mode on the drive to my destination 90 minutes earlier. For the life of me, couldn't get it to go into dark mode on the drive home.

Alright, bug report it is, then! I had only experienced it since going to 13.2, but I thought that it might have been intentional (given how many people say they send feedback about dark mode being TOO dark for Maps. Couldn’t imagine that they would just default it to light mode for that instead of changing contrast or something, but I didn’t think that far into it) 😂

 

[G1Ravage]

Maybe I'm going crazy, but...is how Apple CarPlay switches between light and dark different now on iOS 13?

It seems to now be fully contingent on whether my headlights are on or not. Even on a bright day, if I linger in an underpass for too long and my automatic headlights turn on, Apple CarPlay switches to dark mode.

I could swear that on iOS 12, there were times in periods of twilight where my headlights would be on, but there was more than enough ambient light to permit Apple Maps in CarPlay to stay in day mode.

 

[MozMan68]

Maybe I'm going crazy, but...is how Apple CarPlay switches between light and dark different now on iOS 13?

It seems to now be fully contingent on whether my headlights are on or not. Even on a bright day, if I linger in an underpass for too long and my automatic headlights turn on, Apple CarPlay switches to dark mode.

I could swear that on iOS 12, there were times in periods of twilight where my headlights would be on, but there was more than enough ambient light to permit Apple Maps in CarPlay to stay in day mode.

Nope...always based off of headlight.

 

[G1Ravage]

Apple must be in a New York mode today...I woke up to nearly two dozen notifications that various POI corrections I sent in have been modified. And more notifications are still coming in. Unfortunately, I was in the middle of preparing a new report for them, when I suddenly got whisked away mid-typing to a different screen showing me a POI correction. I lost my progress and had to start over.

I had a bad experience with the new maps driving to and from work in Manhattan last night. Well, first the positives. It rerouted me multiple times around changing traffic, and I made great time. The new buildings look great, too.

Unfortunately, I’m seeing more and more instances of Apple Maps just not “understanding” our highway names and intersections here. Things that TomTom had right.

Apple Maps’ directions now often omit critical information visible on highway signs, and instead direct you onto exits or roads using incorrect or historical (but not signed) names for roads.

Despite the Queensboro Bridge being appropriately named on the new maps, directions never mention the bridge at all, instead telling you to turn onto State Route 25, which isn’t even signed anywhere near the bridge.

In addition, the exits from the Queensboro Bridge and Midtown Tunnel into Manhattan are badly misdrawn, so much so that Apple Maps gave me directions to turn the wrong way onto a one-way street! (When in reality, the exit cuts across onto a different road.)

I spent the last week sending in soooooo many road corrections and shield issues. And now I sent in about ten more. They correct POI issues relatively fast, but I wonder how long it’ll take to come through and update roads on the map itself? Do you think they’re maybe too busy rolling out the new maps across the rest of the country?

Check out these map/satellite comparisons.

 

[hibby704]

I’m in the Philly area with the updated maps for iOS 13, but I’m not seeing stop signs or traffic lights during navigation. Are these part of the slow roll out, or an option I’m not seeing? Thanks!

 

[MozMan68]

I’m in the Philly area with the updated maps for iOS 13, but I’m not seeing stop signs or traffic lights during navigation. Are these part of the slow roll out, or an option I’m not seeing? Thanks!

Part of the rollout. Seems to be tied somewhat to LookAround areas.

 

[gwhizkids]

Part of the rollout. Seems to be tied somewhat to LookAround areas.

Only somewhat tied to LookAround: we do not have LookAround in CT but do have the traffic signals.

 

[gwhizkids]

Apple must be in a New York mode today...I woke up to nearly two dozen notifications that various POI corrections I sent in have been modified. And more notifications are still coming in. Unfortunately, I was in the middle of preparing a new report for them, when I suddenly got whisked away mid-typing to a different screen showing me a POI correction. I lost my progress and had to start over.

I had a bad experience with the new maps driving to and from work in Manhattan last night. Well, first the positives. It rerouted me multiple times around changing traffic, and I made great time. The new buildings look great, too.

View attachment 870067

View attachment 870068

View attachment 870069

Unfortunately, I’m seeing more and more instances of Apple Maps just not “understanding” our highway names and intersections here. Things that TomTom had right.

Apple Maps’ directions now often omit critical information visible on highway signs, and instead direct you onto exits or roads using incorrect or historical (but not signed) names for roads.

Despite the Queensboro Bridge being appropriately named on the new maps, directions never mention the bridge at all, instead telling you to turn onto State Route 25, which isn’t even signed anywhere near the bridge.

In addition, the exits from the Queensboro Bridge and Midtown Tunnel into Manhattan are badly misdrawn, so much so that Apple Maps gave me directions to turn the wrong way onto a one-way street! (When in reality, the exit cuts across onto a different road.)

I spent the last week sending in soooooo many road corrections and shield issues. And now I sent in about ten more. They correct POI issues relatively fast, but I wonder how long it’ll take to come through and update roads on the map itself? Do you think they’re maybe too busy rolling out the new maps across the rest of the country?

Check out these map/satellite comparisons.

View attachment 870070

View attachment 870073

View attachment 870074

View attachment 870075

View attachment 870072

View attachment 870071

You meant the 59th Street Bridge, right?

 

[MozMan68]

Only somewhat tied to LookAround: we do not have LookAround in CT but do have the traffic signals.

Right...it’s like it is a separate layer, but obviously using the Look Around data to help.

They always mentioned that they would use their imaging to automatically detect stop lights, stop signs as well as “read” other road signs (speed limit, one way, do not enter, etc.)

I always imagined some person sitting there to manually verify the computer’s analysis of that data and then release it as part of the overall map data.

Seems like stop signs and traffic lights are pretty easy to confirm which is why that feature comes out around the same time as Look Around but doesn’t necessarily match the area released since Look Around as MUCH more info to process (poi’s).

Good theory??

 

[G1Ravage]

After the update to iOS 13.1.3, I’m noticing Apple Maps was a bit smoother in operation. I also think they got tired of me complaining, and they reduced the size of the directional box and ETA bar. Let’s compare.

iOS 12.4, iOS 13, and iOS 13.1.3

Hmmm...maybe there’s no difference after all. Oh well.

Anyway, some more screenshots from my travels today.

And these weird lane arrangements I saw on Google Maps. You want me to do what from where??

 

[Alan Gordon]

Noticed yesterday that my Mac has gotten the Midwest update sometime in the last few days. Hasn't updated on my iPhone yet though.

 

[gwhizkids]

Right...it’s like it is a separate layer, but obviously using the Look Around data to help.

They always mentioned that they would use their imaging to automatically detect stop lights, stop signs as well as “read” other road signs (speed limit, one way, do not enter, etc.)

I always imagined some person sitting there to manually verify the computer’s analysis of that data and then release it as part of the overall map data.

Seems like stop signs and traffic lights are pretty easy to confirm which is why that feature comes out around the same time as Look Around but doesn’t necessarily match the area released since Look Around as MUCH more info to process (poi’s).

Good theory??

I'm hoping it means more LookAround than just major cities.

 

[dk001]

I'm hoping it means more LookAround than just major cities.

If not ... then why have it.

 

[MozMan68]

If not ... then why have it.

Right...it’s their “StreetView” and will be available everywhere.

 

[dk001]

Right...it’s their “StreetView” and will be available everywhere.

Everywhere is/was my assumption. To not .... :O

 

[MozMan68]

Everywhere is/was my assumption. To not .... :O

Yep...I was agreeing with you.

 

[G1Ravage]

I think Apple is "naming" the highways in New York City based on what the adjacent service road is called (except for most of the LIE). And in areas where there are no clear service roads, the road name reverts back to just the Interstate and direction. That would help explain some of the inconsistencies I'm seeing.

 

[gwhizkids]

Here is the next frontier for Some Maps. Competition is good!

The best Waze feature is now available in Google Maps for iPhone

Google has been porting Waze’s best feature to Google Maps for a while now, but only in a limited fashion and only on Android. That’s …

bgr.com

 

[G1Ravage]

It seems Apple is finally getting around to some of the nitty-gritty new maps issues I began reporting around two weeks ago.

To start, they've fixed the I-678 shield issue in the Bronx. It now runs further north to near where it's supposed to actually end. This is a good sign. It suggests to me that part of the team is starting to look at these issues.

And they definitely need to. It's causing directions issues, and I have more to report to Apple after my drive home from work this morning.

 

[MozMan68]

Here is the next frontier for Some Maps. Competition is good!

The best Waze feature is now available in Google Maps for iPhone

Google has been porting Waze’s best feature to Google Maps for a while now, but only in a limited fashion and only on Android. That’s …

bgr.com

They reported this months ago when Google added the speed limit info...and honestly, while I wouldn't mind some of these notifications, to me, it's only an improvement for people who are using Google Maps as a default anyway. If I wanted these features, I have them already with Waze..and I still prefer to use Apple Maps.

It's interesting though that they are adding these and slowly making Waze obsolete. Not sure how long ago this was planned or if it is a targeted attack at Apple Maps based on the recent improvements.

You're definitely right though...competition is awesome. My prediction is Apple will have the same thing soon, but it will be Siri based to stick to their "hands free" preference while driving ("Siri, report a vehicle on the side of the road."). But honestly, outside of police reporting (which Google doesn't seem to be adding), what could Apple add that isn't already covered by their new Maps logic? Add a construction zone that just popped up? A vehicle on the side of the road? Maybe a pothole/object in road? I do like these, but not sure they are a deal breaker for me.

 

[iOS Geek]

Whoa...I noticed that last night when I was driving home. I had to switch to Waze because it was too bright (was a dark and stormy drive). I'd say it was a bug. I swear it went into dark mode on the drive to my destination 90 minutes earlier. For the life of me, couldn't get it to go into dark mode on the drive home.

I sent the report in, but I had some experiences that have led me to think that it IS, in fact, intentional. Even on beta 3, this is still happening, but the behavior seems exactly like pre-iOS 13. I was driving last night around sunset and while it was still light out...the map was light, even though I was using dark mode. As the sun went down and it got dark...the map faded to dark. Had the same experience this morning with the map going from dark to light as the sun came up and it got brighter outside. So I think the color scheme in Maps for turn-by-turn is being overridden by ambient light. Which, given how many people say the map is TOO dark (and I tend to agree)...I actually think this is a somewhat decent compromise.

 

[dk001]

I sent the report in, but I had some experiences that have led me to think that it IS, in fact, intentional. Even on beta 3, this is still happening, but the behavior seems exactly like pre-iOS 13. I was driving last night around sunset and while it was still light out...the map was light, even though I was using dark mode. As the sun went down and it got dark...the map faded to dark. Had the same experience this morning with the map going from dark to light as the sun came up and it got brighter outside. So I think the color scheme in Maps for turn-by-turn is being overridden by ambient light. Which, given how many people say the map is TOO dark (and I tend to agree)...I actually think this is a somewhat decent compromise.

Need the ability to set the darkness level. Dark is too dark at times.

 

[iOS Geek]

Need the ability to set the darkness level. Dark is too dark at times.

Definitely agree. I actually got to the point where overall, not just because of Maps...I changed dark mode settings to sunset to sunrise. Too dark during the day! When driving at night, the dark map is pretty good, in my opinion (but could do with some changes in the colors). I would like to see iOS have the same option as macOS does and be able to set the Maps app to light mode while keeping the rest of the system in dark.

 

[coolsean20]

It seems Apple is finally getting around to some of the nitty-gritty new maps issues I began reporting around two weeks ago.

To start, they've fixed the I-678 shield issue in the Bronx. It now runs further north to near where it's supposed to actually end. This is a good sign. It suggests to me that part of the team is starting to look at these issues.

And they definitely need to. It's causing directions issues, and I have more to report to Apple after my drive home from work this morning.

I got about 100 notifications yesterday from issues I’ve reported. They must have finally gotten to them.

By the way, when the new map rolls around to my area, do you think all/some of the issues I’ve reported will revert back? I’ve heard it changes some POIs and stuff.