Jolly drivers

[gerben]

Took me to Apple maps, but those look just like the old gmaps...

[gerben]

I very nearly submitted an unintelligible update request for this gem. Behold, the finest parking lot editing I have ever seen:

What about this one:

https://www.waze.com/editor/?zoom=3&lat ... TT&env=row

[GermanGallardo]

Lol, This is the funniest post so far hahaha

[gettingthere]

I have seen a couple of Update Requests: 'missing stop sign'.

[gettingthere]

Plus it's in a strip mall that I guarantee doesn't have the correct address/GPS coordinate relation. The level of accuracy in routing to a particular storefront within a strip mall is what we should be worried about. I think I'll go make separate landmarks for every store in the strip mall to enhance the navigation experience.

A lot of this depends on the POI provider that the Wazer chooses. Bing results tend to route to a location on a mapped road vs. Google results which are more likely to have the destination off of the road and at the actual location in a shopping center, mall etc.

Of course Google may be better if the Wazer expects to know exactly where the POI is. But this is complicating the mapping in Waze since we then need to deal with the horrible support for Parking Lots in Waze.

[gettingthere]

Here's a good one! Apparently this is one vote against more communications for the WME Update Request system. This Wazer is really jolly.

"wtf. I keep sending this and I keep getting emails asking for more details. this pos told me to get off a main road, now it's going to put me back on on. it needs to keep people on main roads instead on residential streets! and please don't email me about it."

[gettingthere]

"mulberry street does not go through Smokestone St.. Does NOT extend beyond south of Smokestone St. Mulberry St is a T intersection with Smokestone St, not a cross-intersection."

Am I a bastard for marking it "Not identified"?

Here?

https://www.waze.com/editor/?zoom=6&lat ... ts=7205637

[gettingthere]

I had to clear up dozens of URs in Cartouche from this one guy complaining that waze wasn't navigating exactly to his destination (inaccurate Google data).

They were things like "no it's not here its still down the road" and "ok I am here now"

Did you mark them as solved or "Not Identified"?

If I don't make an edit to the map or know that an edit was made to correct the issue since the last map tile update, I mark as 'not identified'.

The risk here is that the Wazer will get the email and then try to figure out how to fix it themselves. Likely they can't fix the issue since the data that needs to be fixed (POI and Street address lookups) is external to Waze. But I really think solved is not the appropriate response since it is surely not solved.

Best case is the Wazer finds the forum and get search for or ask for help. Then it can be explained how the POI and address lookups function and that likely the best approach is to correct the source data (if it is clearly incorrect), or understand why it works like this.

[gettingthere]

Like I said, Cartouche; so I closed them and wrote a note explaining the situation. They were pretty old.

Sorry, I didn't notice 'Cartouche'. I wouldn't do anything with those. They are obsolete.

[gettingthere]

"the entrance to Costco is here not on Fenton Parkway. I don't get points for reaching mt destination because I enter the Costco lot from a different dire tion than you register on your maps"

No points since you didn't reach your destination? That's a new one.