I think you should use double lanes for the 38.

I can't see the images, but I've investigated this before.

Routing uses cost analysis. In over simplified terms, each turn has a value assigned to it.

IE:

A connected road going towards the destination might cost 1
A connected road going away from the destination might cost 10.

In Waze's routing algorithms. Non-connected roads are not forbidden, they just have a high cost. This allows for educated guess routing to destinations where the roads have not been seen by other waze users.

To absolutely keep routing from turning at a node where a road comes in, you have to use turn restrictions.

Well thanks for the melodrama. Just like any other piece of GPS software, you as the driver are responsible for actually navigating the vehicle. And especially during the infancy of this project there are going to be things that are wrong so doubly so.

I was just trying to explain what it is doing. So now you know... Connectivity is not gospel. That is why we have street directionality, turn restrictions, and bridging for. If connectivity was the deciding factor, then turn restrictions wouldn't even be needed.

Stormer wrote:

enormekever wrote:I think you should use double lanes for the 38.

why? it's road with only 1 lane for each direction

Because it is a controlled-access road (you need ramps to get on/off), it will make your life easier . Also, number of lanes is not important on whether you'll create a separate road for each direction. What are you going to do when there are 3 lanes in each direction? Create 6 roads?

Stormer wrote:And I have no control feature which will show me what turns can be done.. it's worst

Enable "Highlight connectivity" in the View panel. Once this is done, you can select any segment, and the segments that you can drive to from that segment will be highlighted in green.

Stormer wrote:

sketch wrote:

Stormer wrote:And I have no control feature which will show me what turns can be done.. it's worst

Enable "Highlight connectivity" in the View panel. Once this is done, you can select any segment, and the segments that you can drive to from that segment will be highlighted in green.

lol read first post please this discussion is about Highlight connectivity, that it shows other information that routing uses ) It doesn't show connectivity, but routing algoritm can use it ;P

Oh, ha, sorry! I remember reading this topic before, but I thought this was a different one for some reason! Whoops...

enormekever wrote:I think you should use double lanes for the 38.

why? it's road with only 1 lane for each direction

robin1979 wrote:

Stormer wrote:

enormekever wrote:I think you should use double lanes for the 38.

why? it's road with only 1 lane for each direction

Because it is a controlled-access road (you need ramps to get on/off), it will make your life easier . Also, number of lanes is not important on whether you'll create a separate road for each direction. What are you going to do when there are 3 lanes in each direction? Create 6 roads?

no.. you need use ramps only on small part of the road (2km) inside the city.. part of road is done with 2 lanes on map too, but not the part where are only 2 lanes ...

but this is discussion about something else.. I ask why highlight connectivity show other info then routing uses....

This is really stupid, because when I try to make turn restriction it says that segments must be connected in order of selection... So I must first connect these segments and then make turn restriction.... So it takes 3 steps to make restriction instead of 1 step... I hate this feature

And I have no control feature which will show me what turns can be done.. it's worst