Thank you to all who joined us yesterday, and to our special guests Ruben and Ofer!
We had a blast answering your marathon of questions, and hope you’re just as excited as we are about how Road Width will make navigation even more accurate.
If you missed the discussion live, don’t worry! You can always watch it on Youtube here.
Tune in for our next episode on October 17th. More details to come…
See you next month!
Brett, on behalf of the Waze Communities Team
Thank you again for joining, looking at your input in the feedback i would like to address some of your concerns.
As said also during the office i would like to explain why we cannot use the information of the lane guidance for number of lanes in road width.
In many cases the number of lanes at the exit of the segment (the “turn” segments) is different than the number of lanes at the entrance. Roads tend to have a few extra lanes at junctions so a 2 lanes road will become 3 or 4 lanes at the junction. Unfortunately there is no way to use this number for road width, although we really wish there was.
We were left with 2 options:
Use just the number of lanes from the LG feature but as the editors to split the segment every time the segment changes number of lanes. This would have been much simpler on the product and development side but would create a huge burden on the community and will pollute the map with tons of new segments.
Implement “Segments data interval”. This is a brand new approach that, when completed would allow the community to add features (road width, speed limits, etc…) without splitting the segment.
This is our first bite into the feature with an initial dataset of road width (road width at the beginning of the segment).
