L2→L1 Unlock: Templeogue (R137)

[shane_meagher]

Hi,

Can the following segments be unlocked (L2 -> L1):
https://waze.com/editor?env=row&lat=53.29997&lon=-6.30514&s=1125901093281271&zoomLevel=16&segments=101843756,367940354,405398361,405398362,282034503,401531199,401531200,247960670,247960671

The eastbound lane of the R137 between Cypress Grove and Templeville Road is closed until the 4th April for ESB Networks to undertake works:
SDCC Closure Notice

Thanks, Shane

[davidg666]

@shane_meagher

Can the following segments be unlocked (L2 -> L1):
https://waze.com/editor?env=row&lat=53.29997&lon=-6.30514&s=1125901093281271&zoomLevel=16&segments=101843756,367940354,405398361,405398362,282034503,401531199,401531200,247960670,247960671

The eastbound lane of the R137 between Cypress Grove and Templeville Road is closed until the 4th April for ESB Networks to undertake works:
SDCC Closure Notice

Hi Shane,

Did you want the unlock because of the road closure?

If you were planning to place a restriction on these segments, we can put a closure on it instead; this takes effect immediately and shows on the app in bright colours.

I’ve created a closure (and a related map comment in WME) for you, but do you still need the unlock for any other changes? I can do that, although it’s not possible to edit segments that have a closure on them.

++David \ davidg666

[shane_meagher]

Thanks David,

It was just for the closures so no need for the unlock.

Shane

[davidg666]

@shane_meagher

It was just for the closures so no need for the unlock.

Hi again Shane,

Grand so - thanks for raising this though - we would have missed the closure completely if you hadn’t come across it yourself. We do have an automatic feed of closures on the #closure_notices on Slack, but this one didn’t show up there.

++David