Been scratching my head a little at the UR here. There’s no Waze place for the synagogue and so my first thought was that, as usual, the Google location was wrong. Except it isn’t, it’s spot on.
This is confirmed by searching for “Belsize Square Synagogue” in Livemap - the place marker it plants on the map is correctly located, and asking for a route to the synagogue takes you right up to the front door on Belsize Park.
What’s confusing me therefore is why, if I then open up the app and do the same search, the app shows the place marker in the same location as in Livemap, but then consistently generates routes to the rear wall of the synagogue on Belsize Square - even the chequered flag to mark the end of the route is planted in the correct spot, yet the purple route line and associated list of routing instructions always stops short.
It’s bad enough dealing with routing errors caused by crap Google location data, but when the location is being returned seemingly to within a few microns of the actual spot, it’s even more frustrating as there doesn’t seem to be any reason for it - especially not when Livemap does generate correct routes. Even if I place the starting location for the Livemap route at the point on Belsize Square where the app ends its routes, LM still generates a route to take me around the block onto Belsize Park…
Any ideas?
My Waze navigates OK, with the final instructions being to turn right from Buckland Cr into Belsize Pk, then 450ft to the destination, which is correct.
Initial thought - have you done a map refresh recently, just in case?
Refreshing the map data seemed to have partially resolved the problem, in that the initially returned route did start going to the correct location. However asking the app to use one of the alternate routes then reverted to using the wrong location.
After about 10 minutes of working just fine, the app has now reverted to using the wrong location for the initially offered route, however now asking for one of the alternates does use the correct location…
Meanwhile in Livemap, all of the routes offered continue to consistently end at the correct location.
Looking at the final sections of the three routes Waze gives me in the app, two approach Belsize Park from Buckland Cr, the other comes in from the other end, via Lancaster Dr. All three routes end at the correct point!
I can’t think what might be different that could cause this behaviour, sorry! Hopefully, someone with more brains will come by soon.
I did a quick app test as well - with some trepidation! I haven’t been to a synagogue since my Barmitzvah! :lol:
My initial app route showed the same problem - destination flag in the right place, but purple route ending on the wrong side of the building. And I have some ideas why!
The result returned by Google has the address in it: 51 Belsize Square. Search for that and you’ll find it’s on the building - right between the 2 segments.
Also - the segment labelled Belsize Pk - isn’t. It’s incorrectly named and should be Belsize Square.
So I can see 2 possibilities for the bad routing. First, the pin for “51 Belsize Square” might be closer to the segment behind the synagogue. Second, Waze may be locating the driving destination by address rather than Google GPS result, and choosing the segment with a name that matches the address.
I’d just noticed the address in the result matched that of the road used for the wrong routing results, but I can’t see how that would explain the variation in routes being returned - wouldn’t it then consistently route to the same spot each time you ask for a route to that location, and especially so when you’ve selected it and then asked to see one of the alternate routes?
I see what you mean. Initial route goes to wrong side of the block. Calculate multiple routes and they all go to the correct side of the block.
Now I’m into wild-guess territory. :lol:
The destination point is almost exactly between the 2 segments. Different pieces of code being used to generate the initial route and the alternate routes - and one of them is rounding to a different precision?
The initial route is calculated to the Google GPS point but Waze then (I don’t know how) shows the flag at the “correct location”. When you ask for alternate routes, they are calculated to that flag location?
Redemption isn’t supposed to be easy. Taking the initial route to a place of worship is lazy - you need to search harder for additional routes in order to guide you to salvation?
Bogon emissions?