Surry Hills & Routing Problems

Hi Team,

Just today my feed has been filled with heaps of Routing issues in and around the Surry Hills area. mtbwill has made a comment of the area regarding light rail works. But there are heaps here. Not only that, I seem to be getting a few in other areas too that would not normally pop up.

Permalink

Yes … MP’s, MP’s everywhere … sounds like a meme.
A lot are strange turns being disabled from high-level editors that I see around the forums and I know, know better! Some of the segments were last touched over 12 months ago.
I suspect there’s been a bug in WME at some stage (I know I encounter turn arrows doing strange things after saves) which causes the arrows to look different to what has been saved to the server.
I have been fixing where I can (or posting update requests), then refreshing, checking checking again.

The Surry Hills ones appear to be editors implementing closures for the Sydney Light Rail (either full or one-way) with restrictions, rather than asking for the closure. All without thinking of the implications for side streets! I have been giving the SLR website / constructions zones a read tonight, but they of course never state when a closure will end (or even if a road has opened again!). I’m going in to the city for work tomorrow afternoon, if my meeting finishes up early I’ll go for a walk up Devonshire street and see what’s going on.
Alternatively if you are a local and KNOW what’s going on, post here and save me the hassle of finding a park in Surry Hills!

Perhaps I should have read here first? :slight_smile: Not long ago tonight I put restrictions on parts of Devonshire St based on the presence of those reports, but also reading up on sydneylightrail.transport.nsw.gov.au. The information on there isn’t as complete/detailed as I’d hoped - Will, I hope you do get to do a walkthrough and see what’s happening.

At risk of stating what should be obvious, if my edits tonight don’t reflect the ground truth, then please feel free to fix them.

I did get in there - a little later than I hoped but had a nice coffee to keep the eyelids open for the drive home! I have to listen to my recording and make some notes, but there are a lot of sections that are completely closed.

For parts that are signed as “local residents only” (I.e. Need to prove to a traffic controller that you live there - what’s the accepted approach? Restrict / enact closure and locals know to ignore?

Would converting to a private road address the issue? Are we talking one street or half a suburb?

Just Devonshire street with a bit on Chalmers at the west end. but with Devonshire being closed in parts, it affects side streets (and causes routing issues if all the segments are just “Restricted”).
End game is that Devonshire will have one lane eastbound only.

I’ll go over my notes tonight, come up with a plan, and put it on this thread for peer review before I get all clicky :slight_smile:

At this rate we’ll need our own mini map raid. Everyone meet at mtbwill’s house on Friday, BYO Drinks :slight_smile:

Not going unless there is drinks supplied! :lol:

yeah you should just make it road closure like george st. service/local vehicles will know to use it anyway

I feel like I’m being set up … hardly worthy of a mapraid :stuck_out_tongue: although the information available is about as sparse and as simple to interpret :slight_smile: It might as well be written in Cyrillic … On a side note, I’m sure that could actually be a fun thing to do, would need to find a location with enough space, a decent internet connection, and a working fridge … back on track now.

So - everything I have read and sighted in person shows that Devonshire will be eastbound-only once the works are completed. The light rail tracks are on the right side of the road as you walk eastbound (i.e. what would be the westbound lane).

My plan in a nutshell, then a more longwinded explanation - would love feedback before I start but I’m ready to get cracking straight away.

  • Implement a closure for Chalmers St between Devonshire and Foveaux
  • Change all segments of Devonshire St to be one-way, eastbound
  • Delete westbound segment (AGC) from Devonshire to Elizabeth
  • Join the two northmost segments of Clisdell St to allow it to be used for u-turn
  • Implement a closure for all or most of Devonshire St (L4+ required)
  • allow U-turns at the intersection of Devonshire st for all streets that would otherwise need to turn in to Devonshire but are affected by the closure.
    I expect all this can be done in a couple of hours of editing (getting in before the next tile update is done). All the edits would need to be done before the closure is put in place.

Implement Closure for Chalmers St - L4+ required
This can be done immediately. Chalmers St is closed already. None of the documents gives an end date. Source
Could an L4+ please implement a closure in all directions on these segments (Permalink) effective immediately until 31/12/2018.

Implement Devonshire St as a one-way street, eastbound
All the literature and observation of the road say it will be one-way eastbound once construction is finished. This is pretty straightforward. Some segments are temporarily westbound but all are gated with “local access only” signs and traffic controllers who were stopping & questioning the few cars that entered.

  • Remove all existing restrictions
  • Enforce one-way eastbound on Devonshire along the entire length (Chalmers to Bourke)

Delete westbound segment (AGC) from Devonshire to Elizabeth
With Devonshire being eastbound only, this is redundant.

  • Delete the short segment
  • Delete the now redundant junction nodes on Elizabeth St and Devonshire St

Allow Clisdell St to be used as a u-turn
I’m in two minds about actually undividing Clisdell St. The southbound direction is ~2m higher than the northbound. Undividing would simplify the map, but there haven’t been any reports about it. Are there any adverse effects I’m unaware of?
Option 1 - Undivide Clisdell

  • Undivide Clisdell and implement turn restrictions so you aren’t asked to turn westbound in to the side streets

  • Enable u-turn at the Devonshire St end
    Option 2 - Leave Clisdell divided

  • Join the two northern ends of Clisdell together on the one junction node

  • enable the turn arrows effectively given a u-turn instruction (angles preferred, TTS override if it doesn’t work)

  • delete redundant junction nodes remaining on Devonshire

Implement closure for Devonshire St - L4+ required
Option 1 - Full Closure
My preferred option is to close all of Devonshire St. Even the bits you can drive clearly aren’t for “through traffic” - from signage (“local traffic only”), the traffic controllers, and the awful quality of the road (road plates, potholes, very narrow lane!).

  • Permalink TBA once other map edits have been made. Some segments will likely change ID.

  • Duration unknown - so effective immediately, expire 31/12/2018
    Option 2 - Specific closures
    The other option is to implement specific closures and leave open the segments I mentioned above. I have these written down and can detail them if we want to go this way.

  • Permalink will be provided if we go this option
    I will need an L4+ available at relatively short notice to be able to implement the closures before the map tiles are updated. Who is available and can put their hand up to help out?

Allow u-turns at segments joining Devonshire affected by closures
Allow Waze to help people fix their driving mistakes - enable u-turn at all the side streets joining to Devonshire St. Depending which option we go on the point above (closures) will depend which ones I implement u-turns at.
If we go my preferred option, then it will be all! Otherwise, I have notes.

Thanks ituajr! Glad that I had interpreted correctly.
I’ll follow the guidelines in How to un-divide two one-way roads as best as possible whilst performing this part of the surgery.

I’ll get started on the edits after work tonight.

OK - all done. Just need the closures implemented now.
All from now until maximum (31st August)
I’ll give these to you in the same “zones” that the construction is planned in, so zones can be opened easily in the future.
Would love if somebody could check my work when they have some free time!

Zone 15
Zone 16
Zone 17
Zone 18

Looks great! Interesting, some of the segments that didn’t get a closure only had a minor geometry change, but good to know. Can’t edit after a closure, can’t do a closure until an edit has been processed!
I’ll ping you over the weekend once I see the edits on livemap.

Some nice work there Will. Kudos to you for taking ownership of this and having a go. Well done buddy.

Cheers mate! As an update … these changes are not yet live on the map yet. INTL is still lagging WAY behind with the last update 27th Feb. I’ll keep watching it but I’ve stopped holding my breath and have gone purple …

Aaand they’ve acknowledged the problem!
https://status.waze.com/2018/03/delay-in-map-tiles-release-intl.html

Looks like everything is live in the app and on livemap now. Are you able to try putting all the closures on now? We should probably leave the restrictions in place (just in case it forces another tile update). ituajr - I’ll send you a PM as well.

Here’s the permalinks to the 4 zones again.
Zone 15 - This closure looks fine
Zone 16
Zone 17
Zone 18 - only 1 segment here is currently closed (264382360). Probably easiest to remove and reapply the whole zone?

Looks perfect. Thanks for your help!! I’ve set a reminder for mid-August so I can check in and request the closures be extended if necessary.