# Wazer provided route x Walking trail

**URL:** https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688
**Category:** Czech Republic And Slovakia
**Created:** [May 29, 2013, 11:49am UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688 "2013-05-29T11:49:45Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![Romcigan](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/r/FFC400/32.png) [@Romcigan](https://www.waze.com/discuss/u/Romcigan)
#### Post date: [May 29, 2013, 11:49am UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/1 "2013-05-29T11:49:45Z")

</div>

Jak zabránit navigaci, aby navigovala skrze Walking trail? viz problém hlášený zde:  
[https://world.waze.com/editor/?lon=14.753&lat=49.95316&zoom=8&layers=BFTFFTTTTTTTFTTTTTTTTTFTT](https://world.waze.com/editor/?lon=14.753&lat=49.95316&zoom=8&layers=BFTFFTTTTTTTFTTTTTTTTTFTT)

---

<div class="post-metadata">

### Author: ![argus-cronos](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/a/963EFF/32.png) [@argus-cronos](https://www.waze.com/discuss/u/argus-cronos)
#### Post date: [May 29, 2013, 11:57am UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/2 "2013-05-29T11:57:48Z")

</div>

It should not be connected to the minor of course 😉

---

<div class="post-metadata">

### Author: ![Romcigan](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/r/FFC400/32.png) [@Romcigan](https://www.waze.com/discuss/u/Romcigan)
#### Post date: [May 29, 2013, 12:17pm UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/3 "2013-05-29T12:17:14Z")

</div>

But it is connected…  
[https://www.google.com/maps/preview#!q=Struhařov&data=!1m8!1m3!1d3!2d14.753254!3d49.953045!2m2!1f231.96!2f90!4f75!2m4!1e1!2m2!1sU4JUWcxnKCFSnZCu-ddeiA!2e0!4m10!1m9!4m8!1m3!1d33790618!2d-95.677068!3d37.0625!3m2!1i1920!2i995!4f13.1&fid=5](https://www.google.com/maps/preview#!q=Struha%C5%99ov&data=!1m8!1m3!1d3!2d14.753254!3d49.953045!2m2!1f231.96!2f90!4f75!2m4!1e1!2m2!1sU4JUWcxnKCFSnZCu-ddeiA!2e0!4m10!1m9!4m8!1m3!1d33790618!2d-95.677068!3d37.0625!3m2!1i1920!2i995!4f13.1&fid=5)

Any solution, workaround, etc? Thanks

---

<div class="post-metadata">

### Author: ![argus-cronos](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/a/963EFF/32.png) [@argus-cronos](https://www.waze.com/discuss/u/argus-cronos)
#### Post date: [May 29, 2013, 12:20pm UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/4 "2013-05-29T12:20:54Z")

</div>

Waze routes over nearly everything what is connected. So the only solution is to disconnect walking trails from the network.

---

<div class="post-metadata">

### Author: ![Romcigan](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/r/FFC400/32.png) [@Romcigan](https://www.waze.com/discuss/u/Romcigan)
#### Post date: [May 29, 2013, 12:29pm UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/5 "2013-05-29T12:29:37Z")

</div>

I understand that it is necessary to submit to a special-purpose maps errors to be repaired in the future… :? 😛 :mrgreen:

---

<div class="post-metadata">

### Author: ![argus-cronos](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/a/963EFF/32.png) [@argus-cronos](https://www.waze.com/discuss/u/argus-cronos)
#### Post date: [May 29, 2013, 12:34pm UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/6 "2013-05-29T12:34:50Z")

</div>

Maybe it helps if you think, that not everything what google may suggest is really correct for waze. The walking trail make sense if it has an adress or a name that is important to find, but even then disconnect it and you’re save from wrong routes. Everything else will not make you happy.

---

<div class="post-metadata">

### Author: ![foxitrot](https://www.waze.com/discuss/user_avatar/www.waze.com/foxitrot/32/25401_2.png) [@foxitrot](https://www.waze.com/discuss/u/foxitrot)
#### Post date: [May 29, 2013, 1:28pm UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/7 "2013-05-29T13:28:59Z")

</div>

> [@Romcigan](#):
>
> But it is connected…  
> [https://www.google.com/maps/preview#!q=Struhařov&data=!1m8!1m3!1d3!2d14.753254!3d49.953045!2m2!1f231.96!2f90!4f75!2m4!1e1!2m2!1sU4JUWcxnKCFSnZCu-ddeiA!2e0!4m10!1m9!4m8!1m3!1d33790618!2d-95.677068!3d37.0625!3m2!1i1920!2i995!4f13.1&fid=5](https://www.google.com/maps/preview#!q=Struha%C5%99ov&data=!1m8!1m3!1d3!2d14.753254!3d49.953045!2m2!1f231.96!2f90!4f75!2m4!1e1!2m2!1sU4JUWcxnKCFSnZCu-ddeiA!2e0!4m10!1m9!4m8!1m3!1d33790618!2d-95.677068!3d37.0625!3m2!1i1920!2i995!4f13.1&fid=5)
> 
> Any solution, workaround, etc? Thanks

If you look at the art [how the trail is connected](https://www.google.com/maps?ll=49.953002,14.753272&spn=0.37818,0.902939&cbp=12,262.66,,0,18.31&layer=c&panoid=IXQRohBsbmqV6KtY7j_ASg&cbll=49.953002,14.753272&t=m&z=11), you’ll see that it is directly attached to [Vilova](https://world.waze.com/editor/?lon=14.75311&lat=49.95307&zoom=7&layers=BFTFFTTTTTTTFTTTTTTTTTTFTT&segments=182534305) and [separated by bollards](https://world.waze.com/editor/?lon=14.75311&lat=49.95307&zoom=7&layers=BFTFFTTTTTTTFTTTTTTTTTTFTT&segments=177645779) [from Ondrejovska](https://world.waze.com/editor/?lon=14.75311&lat=49.95307&zoom=7&layers=BFTFFTTTTTTTFTTTTTTTTTTFTT&segments=177644424). Yet there are green arrows between Ondrejovska and this Waking Trail, but red arrows between WT and Vilova. So, as the first workaround, at least set all four arrows at the junction with Ondrejovska to red. Then wait a few days and try it out.

When creating such “disconnections” between roads using a WT segment, it is a good manner to set at least all arrows from roads to red. Setting also the arrows from WT towards roads red as well will raise the penalty against unwanted navigation.

(Treba pomoct s prekladom? Mozem zhrnut.)

---

<div class="post-metadata">

### Author: ![porubcan](https://www.waze.com/discuss/user_avatar/www.waze.com/porubcan/32/78878_2.png) [@porubcan](https://www.waze.com/discuss/u/porubcan)
#### Post date: [May 29, 2013, 1:43pm UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/8 "2013-05-29T13:43:12Z")

</div>

I think that in this particular case the WT segment is useless and should be removed.

---

<div class="post-metadata">

### Author: ![sindelm](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/s/1BAB50/32.png) [@sindelm](https://www.waze.com/discuss/u/sindelm)
#### Post date: [May 29, 2013, 1:46pm UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/9 "2013-05-29T13:46:35Z")

</div>

Yes, the turn restriction can help.  
Basically, the routing through WT should be deemed as a routing engine fail. Segment disconnecting is a short-sighted workaround. The segments are connected in the fact, so the map should reflect that fact. It could be useful for route planning for pedestrians, cyclists … some day. Making stupid map because of stupid route planner isn’t right solution (at least from my point of view).

---

<div class="post-metadata">

### Author: ![sindelm](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/s/1BAB50/32.png) [@sindelm](https://www.waze.com/discuss/u/sindelm)
#### Post date: [May 29, 2013, 1:53pm UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/10 "2013-05-29T13:53:04Z")

</div>

> [@porubcan](#):
>
> I think that in this particular case the WT segment is useless and should be removed.

But the segment exists in fact… I suggest using of the turn restrictions, in case the route planner is unable to handle the WT correctly.

---

<div class="post-metadata">

### Author: ![porubcan](https://www.waze.com/discuss/user_avatar/www.waze.com/porubcan/32/78878_2.png) [@porubcan](https://www.waze.com/discuss/u/porubcan)
#### Post date: [May 29, 2013, 4:06pm UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/11 "2013-05-29T16:06:17Z")

</div>

> [@sindelm](#):
>
> > [@porubcan](#):
> >
> > I think that in this particular case the WT segment is useless and should be removed.
> 
> But the segment exists in fact… I suggest using of the turn restrictions, in case the route planner is unable to handle the WT correctly.

As far as I remember Waze was never intended to be pedestrian/bike app. Core functions for drivers still require improvements and I would wonder if we will see navigation for bikers/pedestrians in future.

---

<div class="post-metadata">

### Author: ![sindelm](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/s/1BAB50/32.png) [@sindelm](https://www.waze.com/discuss/u/sindelm)
#### Post date: [May 29, 2013, 4:36pm UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/12 "2013-05-29T16:36:13Z")

</div>

I’m also not aware about it so far. But I think it will come one day… And the value lies in the data (maps) not the engine, I think.

---

<div class="post-metadata">

### Author: ![porubcan](https://www.waze.com/discuss/user_avatar/www.waze.com/porubcan/32/78878_2.png) [@porubcan](https://www.waze.com/discuss/u/porubcan)
#### Post date: [May 29, 2013, 4:40pm UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/13 "2013-05-29T16:40:22Z")

</div>

Those few WT will never be enough for the purpose and there are other apps available already. For now we shold focus on getting roads mapped correctly

Sent from my HTC One X using Tapatalk 4 Beta

---

<div class="post-metadata">

### Author: ![sindelm](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/s/1BAB50/32.png) [@sindelm](https://www.waze.com/discuss/u/sindelm)
#### Post date: [May 29, 2013, 4:55pm UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/14 "2013-05-29T16:55:59Z")

</div>

Of course. I agree, there are a lot of things more imopratnt than WT… But in case the WT category is recongized it should be handled properly (by route planner).

---

<div class="post-metadata">

### Author: ![vlado\_s](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/v/FFC400/32.png) [@vlado\_s](https://www.waze.com/discuss/u/vlado_s)
#### Post date: [May 29, 2013, 6:27pm UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/15 "2013-05-29T18:27:45Z")

</div>

> [@foxitrot](#):
>
> … but red arrows between WT and Vilova.

NO! There were green arrows too. I’m sure.

---

<div class="post-metadata">

### Author: ![foxitrot](https://www.waze.com/discuss/user_avatar/www.waze.com/foxitrot/32/25401_2.png) [@foxitrot](https://www.waze.com/discuss/u/foxitrot)
#### Post date: [May 29, 2013, 8:40pm UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/16 "2013-05-29T20:40:32Z")

</div>

> [@vlado\_s](#):
>
> > [@foxitrot](#):
> >
> > … but red arrows between WT and Vilova.
> 
> NO! There were green arrows too. I’m sure.

I admit. I came later here - even the UR/MP was already gone.

BTW, Argus, are you still around? I believe we could continue in our native languages.

---

<div class="post-metadata">

### Author: ![argus-cronos](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/a/963EFF/32.png) [@argus-cronos](https://www.waze.com/discuss/u/argus-cronos)
#### Post date: [May 30, 2013, 5:49am UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/17 "2013-05-30T05:49:29Z")

</div>

Well, of course do your business foxitrot 😉 sorry for hijacking native language :mrgreen:  
But i believe red arrows or even unknown direction is useless, had several tests, as long as it is connected, it is a problem, sometimes depending on alternatives of course. Or roadclosures then it will definitely rout over the wt.

Cu  
Argus

---

<div class="post-metadata">

### Author: ![Romcigan](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/r/FFC400/32.png) [@Romcigan](https://www.waze.com/discuss/u/Romcigan)
#### Post date: [May 30, 2013, 7:37am UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/18 "2013-05-30T07:37:33Z")

</div>

Ok, there are many WT (not only nearby this village). Should I switch all turns in/out WT to red?

---

<div class="post-metadata">

### Author: ![foxitrot](https://www.waze.com/discuss/user_avatar/www.waze.com/foxitrot/32/25401_2.png) [@foxitrot](https://www.waze.com/discuss/u/foxitrot)
#### Post date: [May 30, 2013, 9:06am UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/19 "2013-05-30T09:06:15Z")

</div>

I’d love to convince at least thousands of people to spam the support with all possible cases of through WalkTrail (or even through a red arrow) routing :evil: (better, through any of the segment types, promised to be not routable anymore).

Maybe they would finally find the offending bugs (at least one each week) and finally we would maybe not get any of those regular weird detours anymore.

Otherwise, I’m sharing Romcigan’s approach - there are really attached WT’s and, although there is no practical use for them ATM, Waze promised already ages ago not to supply routes through them (declaring them “unroutables”). And again, I’d draw them and draw them, until they’d fix this yet-another-loose-screw in the machine. :twisted: Remember Ehud’s requests about us please not hacking the map, in order to fix routing? :lol:

---

<div class="post-metadata">

### Author: ![sindelm](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/s/1BAB50/32.png) [@sindelm](https://www.waze.com/discuss/u/sindelm)
#### Post date: [May 30, 2013, 9:30am UTC](https://www.waze.com/discuss/t/wazer-provided-route-x-walking-trail/41688/20 "2013-05-30T09:30:46Z")

</div>

> [@Romcigan](#):
>
> Ok, there are many WT (not only nearby this village). Should I switch all turns in/out WT to red?

Hmm. I’d prefer out-turns according to the reality, in-turns to red… In case of being in a WT (or pedestraing broadwalk) zone it could be useful for geting off there.
