Unreported road closure in Edmonton

Map Editors Community Canada Alberta
1

The intersection at 118th Avenue NW and 97 Street NW has a bunch of lane closures and a total closure of eastbound traffic on 118th Avenue which aren’t currently showing up on Waze; this has been ongoing for days.

I attempted to suggest an edit for a road closure, but on that tab in the Editor it just says, “To add or edit closures, you need to be a level 4 editor or a Waze for Cities partner with established permissions.”

Is there another way to suggest closures?

Is Waze getting closure/disruption data from the CoE datafeed? FYI, while the ongoing construction and some of the lane restrictions are listed on the City public map, the closure is not listed.

2

Thanks for the heads up. I’ve found records of the construction closure on the Edmonton commuter website (Current Traffic Disruptions | City of Edmonton). As such, i’ve added an eastbound closure to that tiny segment until December 5th at 6am (which is what they claim on the Edmonton site as the end of ‘phase 4’).

As for going forward, you can come hang out with the other local editors on our discord as well: Waze Canada
Build up some edits and learn from other local editors and maybe earn the right to add those real-time closures yourself in future :slight_smile:

Thanks for editing with us. Good to have another Albertan on board!

3

Thanks @pironic for grabbing the segment.

@nlindq, firstly welcome to the forums!

Manually road closures are limited to L3 and special permission (ie. partners) - We do do get Edmonton’s Disruptions feed automatically imported into Waze and for the vast of [segment] closures, they are correctly added as-per defined.

There are some entries though that don’t/cannot get identified as a closure, SB 97 St to EB 118 Ave being one of those as its just listed as a left turn ban - the feed does not (yet) add closures to turns. Between that and language (eg. lane closures), they don’t get automatically added.

As you mentioned all EB 118 Ave was closed, we did add a segment closure instead of relying on the Edmonton alert. If we got it wrong, its an easy fix.

image
image521×329 9.38 KB

We can certainly manually add them - as @pironic mentioned, we have a community discord server you can relay details into.
You can also reach-out via the forum/unlock sub-forum (with “closure” or “road closure” in the headline) and some will definitely get to for you.

There is also in-app/in-car. (in-car + CarPlay, Android Auto , and Android Automotive)
If you’re using in-car, there isn’t a direct report for closures*, but you can just do a general map problem and an editor will follow-up

In-app, there is a closure report, but its recently changed - were as before you had to choose a direction of the closure, its more predictive now to make it safer while driving.

Example, if you have a left turn coming up and its closed, when you Report > Closure, it will apply a closure to that turn/movement, cause you were being routing, and recalculate for you.

*There is also a new auto detection closure now, in-app and in-car that if there are enough users on a high priority road, it will automatically apply a closure - this is still new as of this year, but I have seen the detected closures applied pretty quickly.

Hope this gives you some answers, if you have any questions feel free to reply, DM, what be it - happy to answer more.

4

Fantastic; thanks!

Is there a way to mark restrictions which impede traffic flow? As part of that same utility construction, on the section of road joining the traffic circle on 101 Street eastbound to 118 Ave west of 97 Street they’ve closed both the left and right lanes, leaving just the center lane open for traffic turning left onto 97th street northbound. That’s a real chokepoint at rush hour, so it’d be nice if Waze could route around it when it gets even a little bit busy.