The problem is that, although the station entrance is on the A112 High Rd Leyton, the landmark runs directly alongside the A12. Looking at the available search results in the client:
- Waze results gives "Leyton Underground Station MI". The pin is outside the existing landmark and nearly touching the A12 in the client.
- Google doesn't have a match
- Foursquare has a perfect match for the station entrance
- Bing doesn't have a match
Note that before I looked at this, the station landmark was just marked "Underground Station", so I cannot explain where that Waze result comes from. But since it's closest to the A12, that means that the "route to closest segment" algorithm Waze uses would navigate to the A12.
I've changed the name of the landmark to "Leyton Underground Station" but I don't think that's going to help. Routing to the centre of the landmark will still be closest to the A12. I could change the landmark to be much smaller & closer to the A112, but that would make it invisible on the client and someone is bound to think it's a mistake and change it back.
I recently suggested that Waze landmarks should have a "navigation point" associated with them, to tell Waze which segment to navigate to for that landmark. Apparently Waze once had this sort of functionality, although it didn't work as intended. It's possible that they may try and do this again - without that type of solution, I don't think there's much we can do.