Good lord...a sea of orange.

[CBenson]

I'm guessing that is how the areas were label in the census/tiger data used as the base map.

[skapur1]

Your state gives me a headache!

Welcome to the club. My state gives me a headache too

[shawndoc]

No wonder New Jersey is the butt of so many jokes.

[PhantomSoul]

We have the "Greater XXXXX Area" names on the map all over my central NJ area as well. What's worse is their polygons are less accurate than both municipal boundaries and zip code boundaries! I've never seen maps of NJ described like this anywhere, ever, so I'm guessing these came from the initial base maps used to create the database, or some rule somewhere to fill in the gaps where the correct information wasn't available.

[jondrush]

I think it was done by Waze to relieve the conflict when both municipalities had the same name on import of basemap.

[jemay]

The sea of orange is back.... But they appear and then disappear and several screens refresh reappear. Has anybody else noticed this also this morning?

A lot of them are "Turn Problem: The displayed route is frequently not taken by users"

[AndyPoms]

The sea of orange is back.... But they appear and then disappear and several screens refresh reappear. Has anybody else noticed this also this morning?

A lot of them are "Turn Problem: The displayed route is frequently not taken by users"

Yes, but it's a different "sea of orange" problem... See viewtopic.php?f=8&t=37502

[shawndoc]

And its still using ancient outdated data, and I'm pretty sure most of these were flagged the last time around and marked as solved.

What a waste of time and resources. Waze must be trying to spike the volume of "solved" problems's to show high levels of activity to their VC.

I'm almost ready to throw in the towel and tell Waze to F off.

[jasonh300]

And we still have editors who are using this outdated data as an excuse to complicate simple intersections and further damage the maps. I wish they'd just do away with most of the MPs.


iOS Tapatalk 2 sucks.