Hi,
I am starting a starting to draft a update to the Road types page to include the new Not Paved check box and the Off Road Not Maintained road type.
Here is the draft proposal: Unpaved, will post a new update when ready for people to look at.
Posted this so we don’t duplicate efforts unknowingly.
Ok,
I am done, have at it and let me know what to wordsmith to improve.
Thanks in advance for your help.
I like it.
Good to know that the ‘brown’ road type now has a huge penalty while the check box is the old ‘dirt road’ penalty.
On another note - has WME or any of the scripts been updated to show the check box is on without clicking a segment? It’s something to look for when the app is avoiding a logical part of a route - saw it in NJ recently on a MH!
Confidence is the feeling you have before you fully understand the situation.
(Sent via mobile.)
Look good. Thanks for taking the time to do this.
Currently the app has settings for Dirt Roads (allow, don’t allow, avoid long ones), but there are no settings for Unpaved roads. I realize that the settings for Dirt Roads really applies to Unpaved, but until the app wording is corrected, this could be confusing. Maybe this should be noted in your draft.
I added a note to the draft about the client settings.
The change in routing to respect the Unpaved box was very recent I will bring it up with the client devs to get that wording in the client updated asap.
I like the draft as well, if I may say so myself. If there are no objections I’d like to see it published in a weeks’ time (giving everyone enough time to notice here and comment).
Sounds good.
With PZs wording change, I like it.
Agree … good work.
By the way, reason this is so good is because PesachZ provided a ton of advice prior to my posting… Thanks, PZ!
Looks great subs and PZ. I’d like to suggest a small change to “Allow through routing that ignores unpaved roads (avoiding the segments with unpaved attribute checked)” and think it should instead say “Allow through routing that ignores whether roads have the unpaved attribute checked”. That would be a little clearer at least to me. When I first read that bullet point I thought it might be ambiguous
Sent from my LG-H811 using Tapatalk
No objection to the proposal content. However, I was wondering about the proposed organization.
The current organization reads like this:
2 Public roads
2.1 Highways
...
2.2 Streets
...
2.3 Quick reference chart
3 Other drivable roads
3.1 Off-road / Not maintained Road
3.2 Parking Lot Road
3.3 Private Road
If the intent is to end up with:
2 Public roads
2.1 Highways
...
2.2 Streets
...
3 Drivable roads
3.1 Unpaved check box
4 Other drivable roads
4.1 Off-road / Not maintained Road
4.2 Parking Lot Road
4.3 Private Road
Having Public v. Drivable v. Other Drivable roads as categories could be a little nebulous/confusing.
I’d like to put out there the option of either inserting the “Unpaved check box” section as section 3.2 under Public roads or placing it and “Off-road / Not maintained Road” sections under a common “Road Paving” (or somethting similar) section. I have a thing for sections with only a single sub-section. Just a thought.
My understanding was that the draft page was simply for content not location. I agree teh unpaved should be at top of public roads.
To try to keep the parallel construction with the writing of the first two bullets, would
“Allow through routing that could include unpaved road(s) (ignores whether roads have the unpaved attribute checked)”
Reading over i didn’t see anything about unpaved attribute on Off road / Not Maintained road type. I feel this would be important to let editors know that having the road segments as Off road / Not Maintained is a high enough penalty and we would not have to put unpaved unpaved attribute to this road type. Or would you actually want this in a certain case? I really dont see why you would want those.
The unpaved attribute is for drivable roads. Currently Off road / Not Maintained is not driveable so it is not applicable.
You can still check unpaved on a Off road / Not Maintained road. Shouldn’t we make this clear that unpaved attribute is not for Off road / Not Maintained?
While you can check it for off road, just as you can check it for stairway and boardwalk/pedestrian non-routable, it is irrelevant and will not effect routing. The server already knows off road is obviously not paved.
And that would make sense and be logical, not that a lot of stuff here is logical.
The change looks mostly good. I have one suggestion in the 3rd paragraph of the Unpaved Checkbox area:
I would suggest being more explicit in that the settings options are within the Waze client. You mention the Waze client in the 4th paragraph, but for clarity it should be used up here too. Thanks subs and PZ for the draft!