# Suggestion: Separate unpaved road setting

**URL:** <https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610>\
**Category:** WME Feature Requests\
**Created:** [May 31, 2013, 9:42pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610 "2013-05-31T21:42:40Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![bart99gt](https://www.waze.com/discuss/user_avatar/www.waze.com/bart99gt/32/7621_2.png) [@bart99gt](https://www.waze.com/discuss/u/bart99gt)\
**Post date:** [May 31, 2013, 9:42pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/1 "2013-05-31T21:42:40Z")

</div>

I know there is currently a 4x4/Dirt road selection in the editor, however, I think this is a bit limiting and implies that the road, while vehicle accessible, is a completely unimproved and impassible by some vehicles.

In many areas, you still have some roads that are still gravel/dirt, but are well graded, and are maintained on a semi-regular basis making them wholly passable by most vehicles. Right now, I suspect most of these are probably being classified as regular streets, while being more accurate than the 4x4 road description, still may lead a user down a road they’d like to avoid, or if it were labeled as a dirt/4x4 road may needlessly send someone on a much longer route to avoid one mile of good gravel road.

My suggestion is to add a category for a semi-improved street to better distinguish between the two.

---

<div class="post-metadata">

**Author:** ![AlanOfTheBerg](https://www.waze.com/discuss/user_avatar/www.waze.com/alanoftheberg/32/16350_2.png) [@AlanOfTheBerg](https://www.waze.com/discuss/u/AlanOfTheBerg)\
**Post date:** [May 31, 2013, 9:49pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/2 "2013-05-31T21:49:01Z")

</div>

Already on the list / planned. Please see the 2013 meetup thread in the United States forum. There may be more discussion in that thread too, or search for “unpaved.” I know there’s been a thread or two about it already.

---

<div class="post-metadata">

**Author:** ![DaJoNel](https://www.waze.com/discuss/user_avatar/www.waze.com/dajonel/32/5138_2.png) [@DaJoNel](https://www.waze.com/discuss/u/DaJoNel)\
**Post date:** [April 2, 2014, 2:19pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/3 "2014-04-02T14:19:09Z")

</div>

Any update on when we may see this feature? This will help immeasurably in my local area.

---

<div class="post-metadata">

**Author:** ![AlanOfTheBerg](https://www.waze.com/discuss/user_avatar/www.waze.com/alanoftheberg/32/16350_2.png) [@AlanOfTheBerg](https://www.waze.com/discuss/u/AlanOfTheBerg)\
**Post date:** [April 2, 2014, 3:44pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/4 "2014-04-02T15:44:40Z")

</div>

Nope. Sorry.

---

<div class="post-metadata">

**Author:** ![umopapisdn](https://www.waze.com/discuss/user_avatar/www.waze.com/umopapisdn/32/86215_2.png) [@umopapisdn](https://www.waze.com/discuss/u/umopapisdn)\
**Post date:** [June 20, 2014, 11:32pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/5 "2014-06-20T23:32:45Z")

</div>

I have a suggestion regarding this now that we’re using functional classification maps to govern our editing:

in many locations it’s not uncommon for unpaved roads to be classified for very different purposes, making the “Dirt road / 4x4 Trail” road type more or less obsolete. The need still exists for drivers to be made aware of the type of driving conditions they may encounter.

So, why not make it a checkbox?

Just like toll roads, you could classify anything from a major highway to private road as a dirt road. the user can opt out exactly the same as if they had checked “avoid toll roads.” the framework for this already exists, so why wouldn’t this be the next logical step?

---

<div class="post-metadata">

**Author:** ![Jay91150](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/j/1BAB50/32.png) [@Jay91150](https://www.waze.com/discuss/u/Jay91150)\
**Post date:** [June 29, 2014, 11:04pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/6 "2014-06-29T23:04:32Z")

</div>

+1 for umopapisdn’s suggestion. Alberta has many, many numbered (major) highways which are gravel without a yard of asphalt to be seen. They’re the same width and construction/design of a paved highway, but just happen to have gravel as a surface rather than tarmac.

---

<div class="post-metadata">

**Author:** ![Robert04101](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/r/963EFF/32.png) [@Robert04101](https://www.waze.com/discuss/u/Robert04101)\
**Post date:** [June 8, 2015, 8:50pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/7 "2015-06-08T20:50:00Z")

</div>

I wanted to resurrect this thread and see if any progress is in sight. Ideally we have a separate “Surface type” field, distinct from “Road Type”. “Surface type” would default to “Paved” with at least two grades below that, e.g. “Graded gravel” “Rutted dirt” to provide some measure of degree of drivability.

A lot of secondary roads here in Maine are paved near the main roads but change over to graded gravel after a mile or two. Some drivers might prefer to a longer, fully paved route avoiding the shorter, graveled route. (Example [PERMALINK](https://www.waze.com/editor/?env=usa&lon=-69.52771&lat=43.95440&layers=1921&zoom=4&segments=21581146,67797040,67797042)). Unpaved segments that have little or no driving history in Waze should also have a speed penalty in routing.

---

<div class="post-metadata">

**Author:** ![KC-Guardrail](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/k/FD804B/32.png) [@KC-Guardrail](https://www.waze.com/discuss/u/KC-Guardrail)\
**Post date:** [July 15, 2015, 6:41am UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/8 "2015-07-15T06:41:58Z")

</div>

Same with many county roads in rural Missouri. Many are FC as primary collectors but are gravel.

---

<div class="post-metadata">

**Author:** ![michelesharik](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/m/FD804B/32.png) [@michelesharik](https://www.waze.com/discuss/u/michelesharik)\
**Post date:** [August 1, 2015, 6:14pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/9 "2015-08-01T18:14:19Z")

</div>

I agree that further granularity is needed in the “dirt road” category. I live in an area with dirt roads, some of which are graded by the County and thus easy to drive on, and some which are not and so are … not. :-/ It would be nice to be able to distinguish between these types of roads when following Waze navigation. Thanks!

---

<div class="post-metadata">

**Author:** ![PTaylor\_US](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/p/FFC400/32.png) [@PTaylor\_US](https://www.waze.com/discuss/u/PTaylor_US)\
**Post date:** [April 15, 2016, 5:09pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/10 "2016-04-15T17:09:53Z")

</div>

This really needs to be resolved by Waze. This has been a source of frustration for a good long time. Some map editors have resorted to things like adding [DIRT] at the end of the road name. I suggest greater granularity for road types (it seems the current “dirt” road type is more of an “off road”) like the addition of gravel/unpaved. Also, add a slider in the waze app to add a “weight” for routing on gravel roads.

---

<div class="post-metadata">

**Author:** ![Robert04101](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/r/963EFF/32.png) [@Robert04101](https://www.waze.com/discuss/u/Robert04101)\
**Post date:** [May 10, 2016, 12:45am UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/11 "2016-05-10T00:45:46Z")

</div>

> [@michelesharik](#):
>
> I agree that further granularity is needed in the “dirt road” category. I live in an area with dirt roads, some of which are graded by the County and thus easy to drive on, and some which are not and so are … not. :-/ It would be nice to be able to distinguish between these types of roads when following Waze navigation. Thanks!

There’s something in Beta that’s moving in the right direction.

---

<div class="post-metadata">

**Author:** ![tbk0](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/90959C/32.png) [@tbk0](https://www.waze.com/discuss/u/tbk0)\
**Post date:** [May 24, 2016, 6:05am UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/12 "2016-05-24T06:05:18Z")

</div>

I see the new checkbox “Dirt Road / 4x4 Trail”, do you have informations on that ?

In Iceland there are many thousands km of unpaved roads and they are the only roads to connect large areas of the country, but there are also many hundreds km of 4x4 roads where is necessary to wade rivers and these can only be used from 4x4

Would be very useful indicate on the streets / primary / minor and major segments, the sections paved / unpaved , and fantastic if the routing algorithm will use these informations.

---

<div class="post-metadata">

**Author:** ![abright52](https://www.waze.com/discuss/user_avatar/www.waze.com/abright52/32/16862_2.png) [@abright52](https://www.waze.com/discuss/u/abright52)\
**Post date:** [May 25, 2016, 1:58am UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/13 "2016-05-25T01:58:42Z")

</div>

We really need to either change it to Paved / Unpaved or have three categories:  
-Paved  
-Unpaved - Maintained  
-Unpaved - Not Maintained

Most people (myself included) only want to drive on paved roads. Unless the final destination is gravel, I never want to be routed on gravel. Rock chips are expensive.

User will select the minimum road quality that they want to be routed on. I would select “Paved”, in my case, and the other two road qualities will be ignored unless routing to a location on that road. In that case, it would route to the shortest distance on the low quality road.

I can’t imagine that the number of people that want to be routed on dirt roads exceeds the number of people that want to only be routed on pavement. But that is just my experience in the US…could be completely different in ROW.

NOTES:  
I have been routed on gravel through Waze in the past…I turned around until I found a route with no gravel…this just added time and frustration.  
Some people think there is a natural speed penalty on gravel. That is not always the case, I know several people who regularly drive on gravel and they drive similar speeds as on pavement. It’s all in what you are used to.

---

<div class="post-metadata">

**Author:** ![AlanOfTheBerg](https://www.waze.com/discuss/user_avatar/www.waze.com/alanoftheberg/32/16350_2.png) [@AlanOfTheBerg](https://www.waze.com/discuss/u/AlanOfTheBerg)\
**Post date:** [June 5, 2016, 5:41pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/14 "2016-06-05T17:41:14Z")

</div>

The current checkbox was a product team decision. Problem is is that in 2013, Waze told us they were going to implement it as “unpaved.” The global champ community has made it very clear to Waze that pretty much every disagrees with the implementation of this checkbox, named as it is. and also based on what we’ve been told about the functionality of this checkbox when it comes to the app. Hopefully, they will come around and change what we have today.

---

<div class="post-metadata">

**Author:** ![tbk0](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/90959C/32.png) [@tbk0](https://www.waze.com/discuss/u/tbk0)\
**Post date:** [June 5, 2016, 6:49pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/15 "2016-06-05T18:49:57Z")

</div>

Can we start to use the checkbox for unpaved roads or is better to wait ?

I have just 8000km of public unpaved roads in Iceland and I don’t want to waste time.

---

<div class="post-metadata">

**Author:** ![id35](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/FD804B/32.png) [@id35](https://www.waze.com/discuss/u/id35)\
**Post date:** [June 7, 2016, 11:39am UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/16 "2016-06-07T11:39:54Z")

</div>

Something new about this new checkbox in WME?  
I think it should be named “Unpaved” to avoid misunderstanding.  
And have a penalty in Waze app for those who check “Avoid long dirt road”

---

<div class="post-metadata">

**Author:** ![Robert04101](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/r/963EFF/32.png) [@Robert04101](https://www.waze.com/discuss/u/Robert04101)\
**Post date:** [June 8, 2016, 12:20pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/17 "2016-06-08T12:20:38Z")

</div>

> [@abright52](#):
>
> We really need to either change it to Paved / Unpaved or have three categories:  
> -Paved  
> -Unpaved - Maintained  
> -Unpaved - Not Maintained

Ageed, and I think the current set of options, in principle, allows this:  
-Paved = Street (or PS, …)  
-Unpaved (Maintained) = Street + checked “Dirt” box  
-Unpaved (Not Maintained) = Dirt/4x4 road type

This arrangement is only useful, however, if there’s some implementation in the app.

It would be far better if Waze followed Google Map’s lead and had “paving type” be defined list, rather than a simple either/or flag.

---

<div class="post-metadata">

**Author:** ![tbk0](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/90959C/32.png) [@tbk0](https://www.waze.com/discuss/u/tbk0)\
**Post date:** [June 9, 2016, 4:51am UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/18 "2016-06-09T04:51:15Z")

</div>

A checkbox flag for unpaved is correct, because we need to select also for primary, minor and major segments. Of course it is necessary some implementation in the APP and also visibility of unpaved segments on the APP and on livemap.

---

<div class="post-metadata">

**Author:** ![Robert04101](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/r/963EFF/32.png) [@Robert04101](https://www.waze.com/discuss/u/Robert04101)\
**Post date:** [June 9, 2016, 2:13pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/19 "2016-06-09T14:13:17Z")

</div>

> [@tbk0](#):
>
> A checkbox flag for unpaved is correct, because we need to select also for primary, minor and major segments. Of course it is necessary some implementation in the APP and also visibility of unpaved segments on the APP and on livemap.

Sorry, I wasn’t clear. I want two distinct controls:

1. Road Type (same as now)
2. Road Surface (menu box: Paved, Graded Gravel, Loose Gravel, Dirt, …)

There’s a big difference in road quality between a municipally-maintained packed gravel road and a rutted track down to a lake, but we don’t have a clear way of communicating that to the app users.

---

<div class="post-metadata">

**Author:** ![tbk0](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/90959C/32.png) [@tbk0](https://www.waze.com/discuss/u/tbk0)\
**Post date:** [June 9, 2016, 6:44pm UTC](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610/20 "2016-06-09T18:44:16Z")

</div>

Thx, now is clear and this is a perfect solution.

[Next page](https://www.waze.com/discuss/t/suggestion-separate-unpaved-road-setting/47610.md?page=2)
