Level3→L2 Unlock: Beerburrum (SR60 - Beerburrum Rd)

[GarvinGray]

My Level: 2
Reason for request:

Permalink
To connect Eaton Rd to Beerburrum Rd.

[GarvinGray]

@ituajr

Unlocked. You could set the speed limit on Beerburrum Rd while you’re there, if you know it.

I have fixed up what I can. I doubt the 60 kph as being accurate that is South of Eaton Rd, but can not find a speed limit sign anywhere for km’s looking in streetview going south back towards Elimbah.

Beerburrum Rd travelling south is 100kph, so I see no reason why the North direction is 60 kph all the way to Eaton Rd.

[Traveling_Gav]

Yes it is a pain when you cant find a sign. However I dont assume and would leave it and wait for a report to confirm.

[GarvinGray]

Permalink

I have found 80 kph and 100 kph signs all the way further South near where Beerburrum Rd passes under the D’Aguilar Hwy. I have clicked on all the segments from this area to Eaton Rd and am now asking for it all to be unlocked so I can correct the speed limits.

I know in the past when I have asked for a large number of segments to be unlocked, waze has not dealt well with the permalink request. So in case the permalinks only unlock a couple of segments, I want travelling North from just North of where Beerburrum Rd goes under D’Aguilar Hwy all the way to Eaton Rd/Beerburrum Rd.

To add further information- in checking for speed signs, I have seen a couple of speed caution signs recommending taking the bend at 80kph, but the unverified speed limit is currently set for 60kph. That tells me that the legal speed limit should be 100 kph.

[glomp]

Other editors are able to provide multiple permalinks for their unlock/update requests.
This way only the required and correct segments are supplied.
As the requesting editor it is your duty to supply the appropriate details for the request.
I don’t know why this is so hard to do.

[GarvinGray]

@ituajr

The permalink only selected 2 segments. Perhaps next time you could try selecting just the first and last segment of the stretch you want unlocked. That saves us the trouble of identifying cross streets, and it should easy for us to select all the segments in between.

Following Glomp’s comment, I tried getting a permalink for the full stretch of road that you described. I found that if I zoomed out enough for all segments to be on the map, I got Permalink, and trying to load that link took over 6 minutes and was still saying “Loading road data…”. I changed the URL to say “zoom=2” instead of “zoom=1” and that also stalled. Finally I used “zoom=3” Permalink and that worked, selecting 15 segments with a total length of 12.35 km. Finally, I zoomed in enough so that just the northern segment mostly filled the screen, and the permalink became Permalink and that didn’t work (got only 3 segments, totalling 3.38 km.

So, it appears that the trick is to zoom out just enough but not too far! Or maybe not try to be too ambitious, and use several permalinks, each with half a dozen segments.

To Glomp, as you can see from ituajr’s analysis, the issue is not as simple as it first appears. Also, if an editor attempts to zoom out to cover the entire section they want to permalink, they are likely to miss some very small segments that need to be unlocked, as these tiny segments are hidden when viewed in zoomed out.

It does appear that the highest probability of success is to break up the permalink into small separate permalinks containing a few segments in each permalink.

[GarvinGray]

Speed limits all along this stretch have now been fixed using streetview.