We use walking trail for railroads in Belgium. I know the naming is confusing, but it’s like that. I think it’t the gps signal of your phone that isn’t accurate.
And what is the value of indicating railways as walking trails?
People really can’t walk between the 2 lanes on a highway…
It’s not the first time my Waze thinks I’m a train and I’m probably really not the only one.
If the walking trail serves no purpose, but confusing your new users, why not remove it?
@K_Rens The railroad roadtype in Waze has two disadvantages. First, it doesn’t show up in the client. Second, it doesn’t snap your client to it as well as the type we currently use.
Why do you call those disadvantages? I think they are advantages.
I do not want to snap to railroads and I do not need to know in the client that there are railroads?
Waze is meant for cars, not for trains? Or is there a new train update?
There is some higher understanding of how Waze works needed to explain this. We do want people to snap to railroads. People turn Waze on when they are in the train. If they wouldn’t snap to the railroad they’re on, they would be snapped to a nearby road. On that road, historical average speed data would be ruined by it. Traffic jams that are actually there in real life would be swept away by the Wazer in the train.
And yes, we want to see them, because they help determining where you are, they give visual confirmation that what you see on your phone corresponds with reality. It tells you to make a turn just before or just after the railroad crossing. For the same reason we add landmarks like forests, parks, industrial areas.
Your problem is with the GPS fix of your device. We’re not gonna change the map for that.
Walking trail is generally used for public transport, like the train…
There is a convention about how to name the segments, to make clear what kind of ‘public transport’ it’s used for…
But maybe we can have a look how to fix this specific issue.
Normally when driving with a route (did you have one?) you should never be snapped to another nearby road.
You can try to turn on debug mode in the client. (https://wiki.waze.com/wiki/Turn_on_debug_mode)
If it happens again, you can send in logs and then we can investigate the issue.
@Acidoxy: Ok, glad I wasn’t the only one confused by the walking trails.
I guess this is sort of correct, trains in Belgium are often so slow that you consider them as a pedestrian walking on a trail.
@Deeggo: thank you for the explanation. I agree we cannot have train users messing up the road data.
@All: it only happens if I drive on the left lane, the one closest to the walking trail.
And mainly around Vilvoorde.
It often starts if I go under a bridge in a traffic jam, when I get out under the bridge, I’m on the train track.
The Gps is then searching for the new position and in those cases it happens it jumps to the train track.
It only jumps back to the E19 if I go back to the right lane
In average the gps in my phone is about 5m precise. I use it for geocaching as well and then it’s quite correct.
Ps: I indeed had a route set-up I was following, the same one I drive every day.