Possible bug with intersections with parking lot roads

[zCougar]

Hi,

I have found already three routes where navigation gives me very long route instead of direct one and only common thing is that in all cases routing avoids street intersection with parking lot road. Is this something intentional. I hope not.

For instance look at http://world.waze.com/cartouche/?zoom=4 ... FFFFFFTTTT

There is small one way parking road loop and if you select street between it you can see that everyting is well connected:


When asking direction from server from one side of parking lot road to another side, you get such route:


I can easily show more examples but this one should be already very clear. There are no problems with segment direction, allowed turns or recorded speeds. It is clearly visible that route from Waze is absolutely wrong one.

I found this issue because I always use navigation with shortest route option when driving any other roads than my daily one and only after I know that shortest is ok (all junctions and turns and everythig fixed), then I switch to fastest route (there is no enough speed data available anyway at the beginning).

Basically all gas stations are connected with streets using parking lot roads and there are others. Also small roads between flats which are not allowed to pass but can be used to reach these locations are also marked ad parking lot roads right now. Is it a wrong type of road?

Any ideas? I have also sent one similar issue to Waze email but then I didn't understand it. I haven't got any answer but now I found this common thing and maybe somebody else has the same problems

--
Cougar

[zCougar]

Strange. Is here any place where pictures should be uploaded. I put them on my own server which is accessible from everywhere usually..

This is not a case here. This is one street with junction(s) between where parking lot roads are connected. The case you describe is exactly what I understand how it should work. And this is the reason I use parking lot roads for roads that should not be used between navigation but only in case destination is there.

In my case parking lot road is connected with totally straight street and I never get route over this junction. If I choose origin and destination both on different side of this junction then route will give a long direction using all other roads (and actually looking very good route) instead of just going from one segment to another connected segment.

--
Cougar

[zCougar]

I haven't did any changes for this and last edits of most segments were moths ago. Only one is changed 3 weeks ago. I have another place similar where I did changes around week ago, waited as long it went to live map and tested. Result is the same.Only workaround I know right now is to put small street segment before starting with parking lot road but I don't think it is a solution. Just additional and unnecessary data for server and clients.

If direction is asked between two junctions where parking lot roads are connected and there are no other connections (one single segment for example), then route line will look like this:

----*----1=====2====*---- (- is road, * is junction, 1 and 2 are origin and destination and = is blue route)

It is hard to try via web because parking lot roads are not visible even with the greatest zoom level but if you look Cartouche map first and then switch to live map then you can estimate such locations.

There is definitely some issue with junctions where parking lot road is connected..

--
Cougar

[zCougar]

Yes, if I look connectivity of Ehitajate tee north and south segments these these are ok. Connectivity is also ok if I select parking lot road. If I select Ehitajate tee segment between parking lot roads then indeed it shows where I can go but it does not show that I can come from parking lot too.

What I did' is that I disconnected parking lot loop from street, removed these junctions, then crossed parking lot road to the street and added junctions again. And this gave exactly the same result when looking connectivity.

Also there happened strange things when I removed junctions. When I removed junction in north then this middle segment itself also disappeared. Then I moved south segment up and just connected roads by order of selection (don't remember order) and if it usually connects segments to one without needing junction then in this case it also connected but when looking connectivity it shows it like two roads and one way connectivity even missing. And there was no junction where to enable all turns..

Anyway, after that everything was still the same. Then I just added additional junction to parking lot road and all connections went okay.

Could it be a problem of "loop"? I actually remember that in one webinar it was mentioned that to connect two segments to parallel it needed additional junction.

This wasn't edited by me and I didn't look it carefully enough. But there are other locations where such loops does not exist and just normal two-way parking lot road is connected to main street. I'll wait for next live map update and if these problems still exist then I'll show them here too. In one case all segments are two-way and connectivity looks okay for all segments but waze answered that this is fixed now (don't know what they did). Another one is much more complex where many turn restrictions exist and one was even missing so I just changed it and now need to wait.

Does routing calculation always use the data from the same moment that live map does?

--
Cougar

[zCougar]

Should I add new junction top of existing? So far i have feeling that then there will be two junctions very close to each other and hard to remove one. I have fixed several map errors like that before where only solution was to disconnect all segments an then remove junctions too.

Your observation regarding connecting one way roads could be true. This is exactly what I feel too. Most of streets here are built from one way tracks. Sometimes junctions already exist and I just remove all turn restrictions, sometimes there is no junction and segments need to extended over other streets to add junctions. Yes, "enable all turns" is always enabled and also when I change segment direction I always select junctions on both ends and remove all turn restrictions (would be cool if more than one junction can be selected and then do the same operation for all of them in one turn).

I'm not 100% sure I refreshed Cartouche but I know this limitation. I guess it was related with these one way roads converted to two-way later but can't be sure. It wasn't waze webinar but another video "Waze editing #2 - loops and more intersection connections" (http://www.youtube.com/watch?v=D1vc9CZGTrY)where remark was made that add additional junction when two segments are connected to the same junctions but this based on old version of Cartouche.

--
Cougar

[zCougar]

I have seen also junctions so close that even with 5m/10ft zoom it is not possible to select them separately but you always get only one selected. Then I usually just change one segment geometry so that I can get another junction out of this. Don't remember the map problem number but it had its own code even AFAIK.

--
Cougar

[zCougar]

Yes, this one is fixed and it was related with "loop" problem. After adding additional junction all turns went okay.

Still I have the same intersection problems where I checked all segments and there are all turns allowed. No one way roads or any other tricky things:

http://world.waze.com/livemap/?zoom=8&l ... =100720700

And one more I know:

http://world.waze.com/livemap/?zoom=9&l ... g=98419881

This is more complicated as there are actual turn restrictions also.

--
Cougar