I use autoaddress when I work to manage multiple deliveries. I use Waze to navigate. Autoaddress sends the coordinates to waze, does not use the address search in waze. In the .1% of cases where the co-ordinates are not closer to the correct street, the fake driveway fixes the issue.
Calls to discuss it on the forum or slack, still waiting on slack approval so here’s a forum post to discuss.
The segments here at Cherry Gardens were visible on the map a few days ago so I moved them slightly. Now they are covered by the rendering “chunkification” in the app/livemap.
The other segments at Seagreen, I’ll say they’re kind of… unacceptable.
It’s ok to try an accommodate exceptionally peculiar junctions like the one at Cherry Gardens, but we shouldn’t go as far as distorting reality to accommodate 3rd party apps.
I agree that we shouldn’t distort reality in many locations (maybe it’s OK for one or two places).
Although maybe not many users use autoaddress, this also affects users who navigate using eircodes, since they’re generally to the exact coordinates of a property, not the point on the correct segment where the navigation needs to end up.
We need a more general solution, but I’m not sure what it is. Eircodes are peculiar to Ireland, but so, as it turns out, is autoaddress - so other countries probably aren’t running into this. I’m not aware of postal codes in other countries that are tied to individual properties.
Update: postal codes in Lebanon and Singapore identify individual buildings, so those countries might have similar issues. I’ll see if these countries have a solution, err, later today.
OK; the problem exists in Singapore too when you try to navigate by postcode.
Try navigating to “Singapore 805782” (100 Mimosa Terrace) in Waze - you get navigated to Mimosa Vale, which is an adjacent road. There’s nothing clever on the map to fix that:
These streets all have house numbers, but I can’t see where their stop points are because I don’t have editing rights here. There’s no Singapore-specific information on Wazeopedia, and their discussions are split between the forum and Facebook.
Now, to be fair, if Waze gets a pair of coordinates, it’s obvious for to pick a location on the nearest segment. That said, Google Maps does get it right. Maybe they map postcodes to street name+number.
One possible alternative would be walking trails, although that’d be just as hacky as private roads.
The problem with waverly was similar issue, snapping to the closest road. So it’s hard for me to convince my delivery colleagues to use waze if it doesn’t work for the regular customers. I’m only after recently starting work in Greystones after leaving deliveries in Bray where by and large the nearest road to eircode was fine. I wouldn’t imagine there wouldn’t be a need for more fake driveways in Greystones.
I can understand the purist point of view it doesn’t reflect reality but can you understand if I manage to convince a colleague to use it and waze takes them to the wrong estate they’ll laugh at waze and never use it again.
Yeah, I can’t think of a better solution (just keep the fake segments unnamed though). As I mentioned, Lebanon and Singapore probably have similar issues with their postcodes, and when I looked at Singapore I didn’t see anything on the map to fix them up.
I find Eircodes pretty handy for navigation sometimes, but they have the same issue as autoaddress does. Waze looks up their location from Google and although we’ve asked Waze HQ to store their locations locally, I can’t see them being in a hurry to do that. If Waze did store the locations locally, we could ask for a location override where for selected Eircodes we get to tweak the exact coordinates. That would help for navigating by Eircode but still wouldn’t fix the autoaddress problem.
A question for you: can you use autoaddress with other apps, like Google Maps? If you do, what does happens with these locations? Do you get routed to the right places or does it somehow get it right? I’ve love to know how Google Maps fixes it up.
Either way, let us know if you come across any other similar locations. I’ll keep trying to think of a better solution. Although your fake driveways make me feel a little itchy, they do solve the problem.
aha: Google Maps has the same problem with Eircodes and some of these locations. Try navigating to 12 Waverly Close with its Eircode (A63 TT68) and it takes you to Seagreen Drive.
zzemca: can you check autoaddress and see what happens at this location if you use it with Google Maps (can you use autoaddress with Google Maps?)
No wait: I just realised I have autoaddress on my phone and anyone can use it. I tried and noticed that it does indeed make the same problem with Google Maps, but with Waze it gets it right (thanks to your fake driveway).
@Yanis: even though fake driveways are at risk of being deleted and although they don’t reflect reality, do you think they’re a practical solution to this problem that will have to do for now?
I still think it’s a distortion of reality rather than a workaround as such, but if it’s just for a small bunch of problematic estates in that particular area, I guess I can live with it… :mrgreen:
Not sure it this is off topic, as I’ve never heard of “autoaddress” but on the subject of Eircodes. If there is an issue where an Eircode is sending people to the wrong street (e.g. the house and Eircode point is closer to another street), then there is a hack. You can add a Place, the name is the Eircode, and then link the Eircode Google place. As an example: https://www.waze.com/en-GB/editor?env=row&lon=-7.70601&lat=52.39116&s=1178467711&zoom=5&venues=230883852.-1986194313.23123018
Linking to the Google Eircode is important. Waze being Waze, it defaults to the Google result rather than the Waze result, so it needs linking.
Btw, I’m also not a fan at all of creating fake roads and extra clutter to solve this issue. As zzemca says, its only a v. small number of cases where errors occur.
Wow, that’s pretty cool. It looks like it solves the Eircode problem perfectly.
Try the autoaddress app out though. It’s available on iOS and presumably Android too (I haven’t check for Android). You give it an address and it feeds coordinates to Waze, so Waze just gets a coordinate pair. I still can’t think of a way to get Waze to route right in this situation, other than the fake roads solution (which I don’t like, but may be the only way…)
