Restrictions and the difficulties of documenting

Moderator: Unholy

Re: Restrictions and the difficulties of documenting

Postby kentsmith9 » Sun Sep 29, 2013 4:35 pm

A more current thread on this topic is at http://www.waze.com/forum/viewtopic.php?f=276&t=56393
USA: California (Northern, SF/SJ)

ImageImageImageImageImageImage
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 11104
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 1485 times
Been thanked: 1691 times

Re: Restrictions and the difficulties of documenting

Postby kentsmith9 » Fri Aug 02, 2013 4:50 am

AlanOfTheBerg wrote:So, now we have time-based turn restrictions and need to start documenting. We also have time-based directionality restrictions. We also have vehicle-type restrictions. Each can be full-time, recurring weekly/daily, or for selected date ranges.

The interface is similar, especially the directionality/vehicle types one. The topics are related, in terms of it being a restriction, but what will general users think?

My first thought was single page titled "Restrictions" or something similar, with major sections on "Turn Restrictions", "Time-based Turn Restrictions", "Traffic Restrictions", and "Vehicle Type Restrictions" and then start with our best guesses at redirects for other similar names.

Throw out some ideas.

I think just "restrictions" is too broad. That should lead to a disambiguation page like
Level

Then the "Restrictions" disambiguation page would lead to the relevant topics each in depth for that area.

The current Map Editing quick start on Turn Restrictions should be pulled into the new page covering both standard and time-based turn restrictions (TBTR). They are interlinked and should not be isolated.

We currently have HOV and HOT lanes pages that have related timing for when they are free for all that we can link back to TBTR, but during restricted times we are still missing vehicle occupancy from the client app to completely fix this.

CBenson wrote:First, the closure feature in the app, the coming closure feature in the editor and the Mega Event reporting all all sort of seem like restrictions. This could just be handled with a cross-reference that says for closures see xxxx.

We have part of that now with Road closures and Construction zones, so we just need to add the mega closure (discussion on Wiki update in another thread currently).

As for redirects that is easy enough. In fact every day I look something up in the Wiki if I do not find what I expected with that search term (if is comes up with nothing), I create a redirect to the correct page. This seems to be a life-long endeavor. :lol:
USA: California (Northern, SF/SJ)

ImageImageImageImageImageImage
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 11104
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 1485 times
Been thanked: 1691 times

Re: Restrictions and the difficulties of documenting

Postby jwriddle » Sat Jul 27, 2013 3:29 am

james9becker wrote:Do the Waze masters have more info about the options for setting up traffic restrictions? I am thinking about restrictions based on truck or cargo type. Such as weight or hazardous cargo. The signs with the capital HC in a circle.

Jim
Level 3 Editor


Add Senior Citizens and drivers with three or more bumper stickers.


------------------------
Sent from iPhone 4 via Tapatalk 2
iPhone 4 (VZW) • iOS 6.1.3 • Waze 3.7.3.0
Droid Mini (VZW) • Android 4.2.2 • Waze 3.7.3.0
ImageImage
Jay W. RiddleArea Manager
US | Georgia: North Atlanta
jwriddle
 
Posts: 466
Joined: Sun Mar 11, 2012 3:39 am
Location: Atlanta, GA, USA
Has thanked: 256 times
Been thanked: 21 times

Re: Restrictions and the difficulties of documenting

Postby JimB50 » Sat Jul 27, 2013 3:27 am

Do the Waze masters have more info about the options for setting up traffic restrictions? I am thinking about restrictions based on truck or cargo type. Such as weight or hazardous cargo. The signs with the capital HC in a circle.

Jim
Level 3 Editor
Jim
Level 3 editor
LG VS 930 Android 4.1.2
Cleaning up in my area
JimB50
 
Posts: 206
Joined: Tue Mar 19, 2013 10:17 am
Location: League City, TX, USA
Has thanked: 24 times
Been thanked: 6 times

Re: Restrictions and the difficulties of documenting

Postby JimB50 » Fri Jul 26, 2013 6:32 pm

As a follow up to HavanaDay, the new restriction types seem to cry out for a script to find all of these new restrictions on the visible map. Similar to the Color Highlights script.
One other thing about time restrictions. The HOT (HOV plus tolls) lane has weekend hours with the opposite timing for the beach crowd going to Galveston. I have not seen the details for turn restrictions. Is that possible with the new turn restrictions?

Jim
Level 3 Editor
Jim
Level 3 editor
LG VS 930 Android 4.1.2
Cleaning up in my area
JimB50
 
Posts: 206
Joined: Tue Mar 19, 2013 10:17 am
Location: League City, TX, USA
Has thanked: 24 times
Been thanked: 6 times

Re: Restrictions and the difficulties of documenting

Postby jemay » Sat Jul 27, 2013 3:33 am

The client does not have that type of identification. So the simple answer is no.

Sent from my DROID RAZR HD using Tapatalk 2
:arrow: PLEASE READ: Wiki Resources: FAQ|Best Practices|Editing issues?
Global Champ | Assistant Regional Coordinator for US South West - CA,NV,UT,AZ,NM,CO,HI | CM for US

Samsung Galaxy S8+ - Android 7.0 - Verizon
jemay
Waze Global Champs
Waze Global Champs
 
Posts: 3884
Joined: Tue Nov 09, 2010 1:26 am
Location: US South West - Lakewood, CA
Has thanked: 628 times
Been thanked: 904 times

Re: Restrictions and the difficulties of documenting

Postby HavanaDay » Fri Jul 26, 2013 3:27 pm

I think that you are correct that restrictions should have it's own page. I also think that every wiki page that mentions editing should have a link in big fat red letters linking to this page. As it is set up now, it is going to be hard to track down wrong driving direction errors without having to hunt and peck for time based restrictions along the routing to see if that is causing the issue. Although this function is sorely needed I believe it has the most potential for things to go awry. It is going to be way to easy to mess something up intentionally or unintentionally by a new editor by messing with this function and a full understanding of it is of the utmost importance.
HavanaDay
Country Manager
Country Manager
 
Posts: 1807
Joined: Fri Sep 03, 2010 6:08 pm
Has thanked: 216 times
Been thanked: 212 times

Re: Restrictions and the difficulties of documenting

Postby CBenson » Fri Jul 26, 2013 2:53 pm

AlanOfTheBerg wrote:My first thought was single page titled "Restrictions" or something similar, with major sections on "Turn Restrictions", "Time-based Turn Restrictions", "Traffic Restrictions", and "Vehicle Type Restrictions" and then start with our best guesses at redirects for other similar names.

Throw out some ideas.

I think this approach makes a lot of sense. I don't have a better suggestion. However, a couple of things do come to mind. First, the closure feature in the app, the coming closure feature in the editor and the Mega Event reporting all all sort of seem like restrictions. This could just be handled with a cross-reference that says for closures see xxxx. Second, I suspect that going forward that most relevant vehicle type restriction for the average commuter (and thus the editors) will be the HOV restrictions. It may not be immediately clear that HOV is a "vehicle type." (i.e. the search will be for HOV, not vehicle type). So that should just be made clear when documenting these features.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
 
Posts: 17857
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2356 times

Re: Restrictions and the difficulties of documenting

Postby AndyPoms » Fri Jul 26, 2013 1:58 am

We also need to figure out HOV now too...
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 14430
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 129 times
Been thanked: 1328 times

Re: Restrictions and the difficulties of documenting

Postby AndyPoms » Fri Jul 26, 2013 1:12 am

We need to figure this part out
AndyPoms wrote:Also, there are two types of Truck Restriction - "No Trucks" and "No Through Trucks". The first prohibits all Trucks no matter what (like on a Parkway) the others are less restrictive - Asking Politely & the more common "No THRU Trucks" - which, in Waze terms, is essentially a private road - a truck can go to a destination on that road (or on another road that connects to it), but really shouldn't go in one side and out the other.

As a truck driver (I hold a Class B Commercial Drivers License) things like this need to be considered while deciding mapping policy.
Based on my experience as a Truck Driver (ok, it wasn't a delivery truck, it was a TV Truck, but it was the same size) - the "No Thru Trucks" restriction should NOT be made in the app unless it behaves similar to a private street (where it won't route through, but will route to a destination in a network of roads marked with the restriction).

Also, at this time they Types are not sticking when adding a restriction (viewtopic.php?f=211&t=56321&start=140#p503819).
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 14430
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 129 times
Been thanked: 1328 times

Next

Return to Wiki Updates and Discussion

Who is online

Users browsing this forum: Google Feedfetcher