# Waze avoiding FM road?
**URL:** https://www.waze.com/discuss/t/waze-avoiding-fm-road/296739
**Category:** Texas
**Created:** [July 12, 2015, 6:43pm UTC](https://www.waze.com/discuss/t/waze-avoiding-fm-road/296739 "2015-07-12T18:43:59Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@ctpoole](https://www.waze.com/discuss/u/ctpoole)
#### Post date: [July 12, 2015, 6:43pm UTC](https://www.waze.com/discuss/t/waze-avoiding-fm-road/296739/1 "2015-07-12T18:43:59Z")
I have a weird one. Try routing from this point [https://www.waze.com/editor/?env=usa&lon=-98.33909&lat=30.44026&layers=2021&zoom=5&nodes=38885915](https://www.waze.com/editor/?env=usa&lon=-98.33909&lat=30.44026&layers=2021&zoom=5&nodes=38885915) to 25404 Hamilton Pool Road. If you get the results I and a reporter are getting, then the fastest route by almost 30 minutes is selected as #2 not as #1 route.
It appears that Waze is avoiding FM 952 if it can. Any ideas since I am stumped.
The one idea I do have is that this is a u-turn issue, but I don’t think so.
---
### Author:  [@txemt](https://www.waze.com/discuss/u/txemt)
#### Post date: [July 13, 2015, 9:28pm UTC](https://www.waze.com/discuss/t/waze-avoiding-fm-road/296739/2 "2015-07-13T21:28:20Z")
I got it to route fine using livemap.
---
### Author:  [@ctpoole](https://www.waze.com/discuss/u/ctpoole)
#### Post date: [July 14, 2015, 12:46am UTC](https://www.waze.com/discuss/t/waze-avoiding-fm-road/296739/3 "2015-07-14T00:46:23Z")
Txemt, did you try more than one time of day?
Sent from my iPad using Tapatalk
---
### Author:  [@txemt](https://www.waze.com/discuss/u/txemt)
#### Post date: [July 14, 2015, 6:56am UTC](https://www.waze.com/discuss/t/waze-avoiding-fm-road/296739/4 "2015-07-14T06:56:54Z")
Not really. I got sidetracked with a million other things. 🙂
I’ll test it more, but I can see one issue. That FM isn’t FCd right.
---
### Author:  [@JeffS97](https://www.waze.com/discuss/u/JeffS97)
#### Post date: [July 14, 2015, 8:25pm UTC](https://www.waze.com/discuss/t/waze-avoiding-fm-road/296739/5 "2015-07-14T20:25:07Z")
That is weird. Both the Android app and the Live Map find multiple routes, but the shortest and fastest route is listed as the second choice. This image sums up the issue:
[http://imgur.com/0EcIVD1](http://imgur.com/0EcIVD1)
---
### Author:  [@txemt](https://www.waze.com/discuss/u/txemt)
#### Post date: [July 14, 2015, 8:40pm UTC](https://www.waze.com/discuss/t/waze-avoiding-fm-road/296739/6 "2015-07-14T20:40:23Z")
Ok…I’ve changed RM to a PS. We’ll see if that helps.
---
### Author:  [@ctpoole](https://www.waze.com/discuss/u/ctpoole)
#### Post date: [July 22, 2015, 9:45pm UTC](https://www.waze.com/discuss/t/waze-avoiding-fm-road/296739/7 "2015-07-22T21:45:58Z")
It appears that your change did the trick. From this can I make the assumption that Waze will favor road segments that are at or above the “importance” of the road where the route starts and that is why it avoided the FM? Changing the importance of the FM fixed the issue or is there something else going on with the routing engine?
---
### Author:  [@txemt](https://www.waze.com/discuss/u/txemt)
#### Post date: [July 22, 2015, 10:14pm UTC](https://www.waze.com/discuss/t/waze-avoiding-fm-road/296739/8 "2015-07-22T22:14:27Z")
Now you see the importance of FC. Waze maximizes FC as long as it’s set properly. When we first looked at this area, the road was two way the whole way, but also had various degrees of road. It wasn’t consistent enough for Waze to route down it, so it took the FC route, which was longer.
I sent you a PM about the rest of the area.
---
### Author:  [@PvilleT](https://www.waze.com/discuss/u/PvilleT)
#### Post date: [August 3, 2015, 2:27pm UTC](https://www.waze.com/discuss/t/waze-avoiding-fm-road/296739/9 "2015-08-03T14:27:16Z")
LOL. It’s a case of role reversal. What a difference 18 months makes.
