Hi! Often the width of the road does not correspond to reality. Example a four-lane road looks narrower than it should be. Make possible to specify the number of lanes on the road for cars (in cartouche web interface), and depending on the width of the draw of the road. This would also avoid the appearance of parallel roads on the broad highways.
I think the width of the road is determined by the “type” selected - roads, streets, primary street, major highway, freeway, parking lot road, etc.
Rob
Perhaps refer to the labeling and naming of roads in the Support | Wiki Section
Well, wide highways that look like parallel roads are parallel roads. No map sizes roads based on the number of lanes. Google, Bing, TomTom, Garmin, they all have set road types, and the line size follows those. Waze is the same way.
I like the idea of showing number of lanes for a road. Much better for the map to show what you see in the real world.
Also motorways/highways aren’t always 3 lanes. They may split off into 2 lanes.
Yes, but the number of lanes has little to no correlation with the speed you can expect to travel on a road. You’ll probably be going the same speed on Magazine (one lane each way, not divided) that you’ll go on Veterans (three lanes on either side of a canal).
Line thickness should correlate to relative speed of travel, not to road thickness. Speed of travel is more important information.
Yeah I agree. Doesn’t mean you need to have a 3 lane road appear the same as motorway. It would be nice to have lane guidance, same as you find on tomtoms. You can’t have that without some information on how many lanes a road has.
Well, maybe. If TomTom’s lane guidance is the same as it is on my One 3rd Edition, I think it merely makes assumptions. I have heard “Stay on the right lane” for one-lane-each-way roads, for instance.
Yeah it can be a sketchy at times. On motorways though it’s always been pretty accurate for me.
Yeah, motorways are always going to be multi-lane, so “Stay on the left lane” is always going to be a valid instruction for left exits. I doubt TomTom knows exactly which lanes go where or how many lanes there are.
Actually yes it does. The information isn’t always complete but I’ve had instructions such as stay in the left 2 lanes. On roundabouts it will also tell you what lane you need to be.
Like I said the information isn’t always there but when it is it works great. I saw a big improvement in the amount of this information in the last couple of map updates.
I have a bit of a problem with how wide the roads are displayed in the Waze client. Highways and freeways are shown very wide for example. In the web Live Map, things look much better.
For example, I am trying to edit a part of the map where I have a freeway and 2 parallel overpasses.
The problem is that the freeway is divided in 4 carriageways that receive and feed right and left ramps to both overpasses. The only way, to correct represent all the ramp connections is to represent each freeway carriageway as a separate road in Waze. All looks feasible in the Live Map, but in the client, the freeway roads are so thick and wide that one cannot tell them apart and the whole think becomes a big fat mess.
Is it necessary to have a “thick” representation of freeways and highways in the client? Couldn’t it follow the standard of the Live Map or Cartouche where the width differences are less pronounced and colour is the important descriptor?
I agree with coconha. The new colour schemes are great, but the roads are still thicker than they have to be.
What would be better is if there were more road/street/freeway options.
My suggestion is that under “Edit Road Details”, in the first drop-down box that designates a street type, the street types should include number of lanes, and then if the “direction” is set to “one-way”, the number of lanes is automatically halved.
With the inclusion of lanes, road width will be easier to manage depending on number of lanes and street type. It would also make mapping much easier and make the client map much easier to navigate rather then having to add a few “Primary Street” in each direction or multiple “Freeway” beside each other to manage lanes for on and off ramps. There will also need to be a way to then join an on/off ramp to a specific lane.
ie.
Highways
Freeway - 12 lanes
Freeway - 10 lanes
Freeway - 8 lanes
Freeway - 6 lanes
Freeway - 4 lanes
Major Highway - 8 lanes
Major Highway - 6 lanes
Major Highway - 4 lanes
Major Highway - 2 lanes
Minor Highway - 6 lanes
Minor Highway - 4 lanes
Minor Highway - 2 lanes
Ramps - 4 lanes
Ramps - 2 lanes
Streets
Primary Street - 6 lanes
Primary Street - 4 lanes
Primary Street - 2 lanes
Street - 4 lanes
Street - 2 lanes
Service Road - 4 lanes
Service Road - 2 lanes
Then, for example, if “Primary Street - 4 Lanes” is selected as well as the direction “one-way ->”, it will change the mapped street to a one-way, 2 lane, primary street.
Freeways should be split into two one-way halves. This would be making things unnecessarily complicated.
I have no problems snapping to a twelve-lane interstate every day on the way to and from work. Other GPS makers get by just fine without number-of-lane data. What needs to be changed is Waze’s snapping behaviour, not the lane-awareness.
They may not have lanes assigned, but their maps have much more accurate road widths, so it is easier for a client to snap to the correct area of the road they are driving on.
ie. If I use my Navman GPS and drive on an 8 lane freeway in the most outside lane, the Navman almost always places the car location on the edge the freeway displayed on the screen. Same with 4 lane etc - it does this all the way to a single lane.
If that is due to “snapping”, then yes, please improve that 
One other thing to mention though, on my iphone, the GPS tracking/performance seems to be very poor when using Waze, compared to other GPS apps (like Maps, PD Maps, CityMaps2Go, Stagger Home etc) - the car never seems to “snap” to any lane as often as it should, and instead it starts steamrolling a new road.
If you turn off the steamroller, it wil snap a lot easier, and you are no longer making roads that have to be removed afterward. It is better to turn it on only when driving at roads which have not been driven before.
I agree that the snapping function should be improved. I’d like to see an “intelligent” snap, where it will only snap you to roads that are connected to the roads you came from. So if you are on the interstate, and due to GPS wandering it puts you on a side street or service road, it’ll know better.
+1… However, with the amount of roads (here in the UK anyway) not yet mapped/incomplete, this might cause more problems than it solves, at least until our data is more complete.
Agreed. Perhaps at first this should be only enabled in the US, or it should have a toggle in the menu.
Also, it might work okay, anyway. This would–if it works like it should–mostly only affect interstates, service roads, and exit ramps.