Page 1 of 11

Re: Construction (and other scheduled) Closures

PostPosted: Mon Aug 25, 2014 10:17 am
by bz2012
The form is a good start and a great idea.
I would like to suggest a few minor tweaks to improve the process of filling out the form.

Requiring a precise figure when none is available is a common problem with forms.
In this case, often the start and end times for a closure are unknown.
Currently we need to 'make up something' (lie) to complete the form.

How about using 'radio buttons' to select among alternatives?
Something like this:

Scheduled start of closure:
() date [ ] time [ ]
() NOW CLOSED

and

scheduled to re-open:
() date [ ] time [ ]
() UNKNOWN (short term, less than a week)
() UNKNOWN (long term, longer than a week)

The error checking for the form should only require one of the alternatives to be filled in, so if 'NOW CLOSED' is selected, the date and time fields should be blank.

alternatively, if the form software is not that flexible, the directions should note that
we are to to enter
00:00:00 of 1900 as the start when now closed and time of closure is unknown.
23:59:59 of 2222 as the end time when indeterminate or unknown.

Or you can pick some other uniform but arbitrary dates and times that would be a 'flag' so everyone would know that there is no need to lie.

Re: Construction (and other scheduled) Closures

PostPosted: Tue Feb 24, 2015 11:43 pm
by bz2012
manoeuvre wrote:
We should still post a UR at the location. This will allow for better communication with editors regarding updates to the closure. Whether it's getting extended, ending earlier, changed to a week-day closure?


I would also STRONGLY suggest that IF a closure gets extended, The original '[CLOSURE] UR' be REPLACED with a new one, with the new ending time in it.
I find it annoying and time consuming to need to open one that, by the original text, has expired, only to find that it has been extended.

Re: Construction (and other scheduled) Closures

PostPosted: Tue Sep 16, 2014 1:22 am
by cptnformat
Hi All.

I like this system.

What would cause the Waze client to ignore one of these road closures?

Please see the UR - https://www.waze.com/editor/?zoom=5&lat=43.663354&lon=-79.390505&mapUpdateRequest=3785983&env=usa

Based on the directions provided, the client looks like it tried to route onto a (documented) road closure.

Wellesley street is closed westbound from Yonge to Hart House Circle (just past Queens Park)

I can also see this in the August tab (sheet?) of the Google Docs file, row 744

Thanks.

Re: Construction (and other scheduled) Closures

PostPosted: Mon Jun 04, 2018 11:21 am
by Crewbert
doctorkb wrote:Hi Ryan - it sounds like you're looking for the Waze CCP program.

We'll pass your request on to the staff contact so someone can be in touch.

In the meantime, please check out https://www.waze.com/ccp


Thanks for replying. I did previously look at the CCP program, however that seems a little bit more than what I'm looking for right now. Also, when I tried to look more into it a few months ago, I was asked to agree to a bunch of legal jargon on behalf of my organization. I'm not authorized to do that, and as a bureaucratic organization, it would not be an easy process. I'm just looking to do one thing, edit construction zones.

Hopefully someone can get in touch about that possibility.

Thanks

Construction (and other scheduled) Closures

PostPosted: Thu Aug 07, 2014 3:47 pm
by doctorkb
Construction (and other scheduled) closures can now be reported with this form:
https://docs.google.com/forms/d/1qseeTL ... =send_form

At the moment, Canadian Champs have access to the responses to approve closures. This access may be extended to Rank 4s or AMs at a later date.

To view the current list of closures, you can go here:
https://docs.google.com/spreadsheets/d/ ... sp=sharing

This form allows for complete (or directional, i.e. A->B only) closures to be reported. Partial closures (i.e. one of two lanes in a direction) should not be reported.

The closure will be visible in the app (see attachment) and on the livemap, in addition to avoiding routing through the segment.

This method is preferred over adding restrictions -- it is nearly immediate (processed several times per day by Waze staff), and does not rely on a tile rebuild. It also provides the visual closure information.

Re: Construction (and other scheduled) Closures

PostPosted: Fri Aug 08, 2014 9:36 pm
by doctorkb
It doesn't need to be.

The best bet would be to report the UR as mentioned in the form instructions using [ROADWORKS] tag. This will help identify the issue.

I'm trying to figure out how I can share it out, but right now, the owner appears to have restricted that. :(

Re: Construction (and other scheduled) Closures

PostPosted: Tue Aug 12, 2014 2:14 am
by doctorkb
Please use this form.

Mega Events are for much larger things. I will update the documentation to make that more clear.

Thanks!

Re: Construction (and other scheduled) Closures

PostPosted: Wed Aug 13, 2014 4:01 pm
by doctorkb
The nodes is for when you have one-direction-only closures.

If you have a situation like you describe, include the segments adjacent to the closed street in the same permalink. There's no need for separate entries.

Re: Construction (and other scheduled) Closures

PostPosted: Thu Aug 14, 2014 2:34 am
by doctorkb
Sure, or you can put a comment on the sheet.

Re: Construction (and other scheduled) Closures

PostPosted: Thu Aug 14, 2014 5:40 pm
by doctorkb
I think the UR can come off as soon as two things happen:
1. the closure has expired, and this has been verified on livemap
2. the segment lock (if applied) has been restored to the previous setting, or "automatic"

Then the UR can be marked as resolved.