Get a sneak peek at whats next for Permanent Hazards on our April 7th Office Hours!
Post by hmarian
We can discuss with staff at the Meetup.
I think it is an important issue in Canada with many remote/rural area with no cell reception.

HM.
hmarian
Waze Global Champs
Waze Global Champs
Posts: 4597
Answers: 1
Has thanked: 104 times
Been thanked: 1437 times
Send a message

Device: Samsung Galaxy S20+
Waze Version: 4.90.90.901
Country Manager: Canada
Area Manager: Greater Toronto Area, Buffalo (NY), Binyamina (Israel)
Android/WME Beta Tester
-----------------------------------------------------------------------------------------
Editing Manual | Editing Best Practice | @Waze_Canada

Post by Kayos_On_The_Road
The initial un-dividing tasks I did were the result of routing issues where wazers were being given illegal U-Turn instructions and the U-Turn prevention mechanism wasn't working. I would *MUCH* rather spend the time to un-divide than to bowtie a junction. I really dislike several road setups in the Lower Mainland. In some cases they are functional, so not really an issue, but some are just terrible and some give just awful TTS instructions.

In the same vein, I also really hate AGCs, and many of those can also be removed and split roads does tend to increase AGCs. My rule of thumb for AGCs is that the lane separation needs to be greater than 75m for an AGC, the reason being that you get a keep rather than turn instruction, unless the AGC has been set up incorrectly (and there are some) to give a turn rather than keep instruction, which is clearly just straight out wrong.

There are some divided roads and AGCs that give both keep and turn instructions, which in some cases I like, but if the AGC is short, that is too much in terms of instruction.

I agree that many of our divided roads are simply the result of a central median, probably from the base map, and there are *TONS* that should not be divided at all. I also find the divided to un-divided transitions along a length of road or street really irritating and again there is not really a justifiable reason for the divide. As far as loosing data, sure this can happen, but I doubt that for any currently divided road that the segment transition time data is that different in each direction, so ditching one side should be OK. If there are really lots of concerns, we can use the same method to retain street numbers to maintain some of the segment history. It means a lot more work, but it's doable.

EDIT: The current wiki gives information about preservation of house numbers during an un-dividing process, but not about preservation of segment speed data. I found one thread about it, but it was inconclusive as to what the best practice was. It seems that no matter what you do, speed data gets lost. I've also just looked at these segments where WB is 13 seconds and EB is 135 seconds. I think before we start on this we need to set the ground rules on exactly how we are going to perform the un-divide, step by step, to preserve as much data as possible.

However, now that I've done more editing, I also agree with the If it ain't broke... mentality, but if we have editors that want to take the time to tidy things up, I say lets go. Bear in mind that there are some nuances that need to be considered, particularly for access to gas stations and malls where there are no parking lot roads. Divided roads make this manageable and will put wazers on the right side of the road without PLRs, so if a road is un-divided, this needs to be looked at too.

Kayos

Edited for spelling and split to divide language.
Kayos_On_The_Road
Posts: 5449
Has thanked: 386 times
Been thanked: 2069 times
Send a message
Last edited by Kayos_On_The_Road on Wed Sep 23, 2015 9:59 pm, edited 1 time in total.
Samsung Galaxy S7 (7.0 stock), waze version always latest beta.
GC, CM - Vancouver, BC
Waze Beta Leader (Android)
Canada Wazeopedia
https://s.waze.tools/c6.pnghttps://wiki.waze.com/wiki/images/c/c1/ ... Tester.png

Post by Kayos_On_The_Road
Go for it! I really want to get rid of this mess.

Although this is a great candidate, it's not the simplest of intersections with respect to the AGCs, and even though I don't like those either, some are needed here for the reasons you point out, and I like your proposal of both the keep and tun instructions given the length of separations.

The AGC which is going to be odd is SB Gaglardi to continue on Gaglardi, as typically an AGC is used for turns, not BCs. Perhaps this can be a scheduled edit so those that are interested in participating and having input can make arrangements to be available.

Kayos
Kayos_On_The_Road
Posts: 5449
Has thanked: 386 times
Been thanked: 2069 times
Send a message
Samsung Galaxy S7 (7.0 stock), waze version always latest beta.
GC, CM - Vancouver, BC
Waze Beta Leader (Android)
Canada Wazeopedia
https://s.waze.tools/c6.pnghttps://wiki.waze.com/wiki/images/c/c1/ ... Tester.png

Post by Kayos_On_The_Road
This makes sense, but I would join the two segments to a single node at Broadway, otherwise we're going to potentially have a short connector segment. The BC segment can be set to no left onto Broadway.

Kayos
Kayos_On_The_Road
Posts: 5449
Has thanked: 386 times
Been thanked: 2069 times
Send a message
Samsung Galaxy S7 (7.0 stock), waze version always latest beta.
GC, CM - Vancouver, BC
Waze Beta Leader (Android)
Canada Wazeopedia
https://s.waze.tools/c6.pnghttps://wiki.waze.com/wiki/images/c/c1/ ... Tester.png

Post by Kayos_On_The_Road
Keeping the alignment of the AGC and BC segments close together you don't see distinct separation in the client and no taper at the common junction node. Keeping locks to 4 or 5 will also mean it's not going to be messed with.
Kayos_On_The_Road
Posts: 5449
Has thanked: 386 times
Been thanked: 2069 times
Send a message
Samsung Galaxy S7 (7.0 stock), waze version always latest beta.
GC, CM - Vancouver, BC
Waze Beta Leader (Android)
Canada Wazeopedia
https://s.waze.tools/c6.pnghttps://wiki.waze.com/wiki/images/c/c1/ ... Tester.png

Post by Kayos_On_The_Road
hmarian wrote:
Rampage_Rick wrote:I am already Rank 2 (fixed over a hundred roads around Nelson/Castlegar that were unknown direction and all turns restricted)

I have noticed that Waze will tolerate short dead zones (i.e. Merritt to Logan Lake) but seems to give up if it looses connection for more than 30 minutes or so. Was contemplating an attempt to use the Shaw Go Wifi hotspots at Sunshine Valley and Manning Park on my next trip through. Still waiting on a bunch of new cell towers that Telus has applied to build along Hwy 3
When you lose connection your logged information will be stored and when connection is resumed it will be sent to Waze, obviously it depend on the duration of the no connection and how much data have been collected. I remember in pone of our Meetups someone who was travelling a lot in rural area without good cell coverage asked Waze to increase the capacity of the App to store offline data, as it was apparent to him that it wasn't sufficient and affected the routing options. Waze said they will give this a thought, but I don't know if anything is planned for future versions.

Obviously when you don't have network connection the App will rely on cached data that was download prior (when the route was called), and the App will rely on that data that is cached in the device, rather than live data.

HM.
We have lots of areas in BC outside of the main towns and cities with effectively no cell coverage. Traveling highways here I find lots of gaps with what the cache has stored, Hwy 3 being one. Until recently Hwy 5 from Hope to Merritt was also one as was Merritt to Kamloops and the Okanagan connector. Even on Vancouver Island you will get cache time outs where you loose your drive information. Interestingly, at times the drive info seems to be stored, but you still don't get the editing area, although it's been a while since I've looked at that aspect.

As has been said before and in other forum threads, if there are area's which you are familiar with but don't have cell coverage to get the editing rights, you can ask for an AM assignment to complete the updates.

Kayos
Kayos_On_The_Road
Posts: 5449
Has thanked: 386 times
Been thanked: 2069 times
Send a message
Samsung Galaxy S7 (7.0 stock), waze version always latest beta.
GC, CM - Vancouver, BC
Waze Beta Leader (Android)
Canada Wazeopedia
https://s.waze.tools/c6.pnghttps://wiki.waze.com/wiki/images/c/c1/ ... Tester.png

Post by Kayos_On_The_Road
codgerd wrote:A real simple one, stumbled across it while fixing a UR nearby. The road is divided from Lougheed north a few blocks. No reason to have this divided.

https://www.waze.com/editor/?env=usa&lon=-122.93671&lat=49.25636&layers=389&zoom=5&segments=59560789,59423473,59452981,59443720,59461681,59606753,59468193,59468004
You're right, I don't know why this is divided in the first place. Didn't you put a google sheets document together for tracking all of the potential undivides?

Kayos
Kayos_On_The_Road
Posts: 5449
Has thanked: 386 times
Been thanked: 2069 times
Send a message
Samsung Galaxy S7 (7.0 stock), waze version always latest beta.
GC, CM - Vancouver, BC
Waze Beta Leader (Android)
Canada Wazeopedia
https://s.waze.tools/c6.pnghttps://wiki.waze.com/wiki/images/c/c1/ ... Tester.png

Post by Kayos_On_The_Road
Ok. When was the base map import?

Sent from my SGH-I747M using Tapatalk
Kayos_On_The_Road
Posts: 5449
Has thanked: 386 times
Been thanked: 2069 times
Send a message
Samsung Galaxy S7 (7.0 stock), waze version always latest beta.
GC, CM - Vancouver, BC
Waze Beta Leader (Android)
Canada Wazeopedia
https://s.waze.tools/c6.pnghttps://wiki.waze.com/wiki/images/c/c1/ ... Tester.png

Post by Kayos_On_The_Road
Nothing to be done now, but lets post day and time of the speeds, and the total transit time in each direction. There will only be additional data for times if there is more than a week. We may also want to run checks at multiple times, particularly for routes where morning and evening times are very different in each direction.

We just want to make sure we minimize data loss during an un-divide. We will need to decide on a location to try a delete of one direction rather than using the house number preservation method. If there is no real appreciable difference, then we can save editing time by deleting one direction.

Kayos
Kayos_On_The_Road
Posts: 5449
Has thanked: 386 times
Been thanked: 2069 times
Send a message
Samsung Galaxy S7 (7.0 stock), waze version always latest beta.
GC, CM - Vancouver, BC
Waze Beta Leader (Android)
Canada Wazeopedia
https://s.waze.tools/c6.pnghttps://wiki.waze.com/wiki/images/c/c1/ ... Tester.png

Post by Kayos_On_The_Road
Looks pretty straight forward to me. What sort of traffic volume is seen here? We need to decide on an undivide to test a deletion in one direction and it effect on times. I would want to try it on a high volume road so that we get traffic data back quickly if things are lost. By the GPS tracks it looks like there is a reasonable amount of traffic here, but I'm not familiar with the area to really gague it. Some of the other potentials I'm looking at are lengthy and the advantage here is it's relatively short and isolated. What are your thoughts?
Kayos_On_The_Road
Posts: 5449
Has thanked: 386 times
Been thanked: 2069 times
Send a message
Samsung Galaxy S7 (7.0 stock), waze version always latest beta.
GC, CM - Vancouver, BC
Waze Beta Leader (Android)
Canada Wazeopedia
https://s.waze.tools/c6.pnghttps://wiki.waze.com/wiki/images/c/c1/ ... Tester.png