hi,
i try to figure out why the navigation goes by the street insted of the highway in a new area (new roads)
navigation offered by waze
navigation should be
i cannot fin the error for now,
can someone help
thanks
i did swap primary street to street and the service road from primary street to service road
for the road type, its better… but
the navigation use the taxi “private road” to get to the airport “YUL” “Montréal airport”
so for now im waiting for any suggestions
thanks
i did add a no right turn for the taxi lane, it should be solved now, but ill doubble check it tomorrow before adding solved to the report
the actual address of the airport is on the taxi lane in front of the aiport !!
I’m not exactly sure what you’re after… your “supposed to be” link didn’t have a complete route.
the trip planned to the airport “YUL” of Montreal get peopple to the Taxi lane…
here is the trip planned by waze
https://www.waze.com/livemap/?zoom=15&lat=45.5&lon=-73.66153&from_lat=45.50001&from_lon=-73.66154&to_lat=45.45764&to_lon=-73.7497
and the trip should pass by these segments, but the end point is on the taxi lane…
HEY SOMEONE DID DELETE THE NEW EXIT BETWEEN THESE 2 SEGMENTS
and u can see it on the live map
https://www.waze.com/editor/?lon=-73.73992&lat=45.45228&zoom=5&layers=901&env=usa&segments=75992094,75992092
one section of the primary road have been change by WEBS101 to ramp
i did those mods for the navigation issue
I didn’t delete or add any ramps. I think somebody must have seen the unfinished ramp in the satellite shot and deleted it.
We can’t name streets like ramps, though. It confuses the driver when you take a section of Romeo-Vachon and name it Cardinal.
still the exit is cardinal // montreal airport
and the exit b4 is romeo-vachon as the service lane of the kind of “highway” 6 lanes they did build to access the airport and ave Cardinal
and the tracking didnt use them, so i did put “primary street” on that segment so the navigation choose it insted of romeo-vachon that was “primary street” and set it as “street”
to force the navigation, but when u seek for montreal airport, the navigation link u to a point on the taxi lane in front of it insted of arrival or departure…
so its kinda hard of us to settle the right choice of road and to get at the right level
and sorry to accuse u for deleting a ramp, but i saw only your name that did edit it today, and i did made the changes yesturday, so it was a simple “no-brainer” conclusion :roll:
First off, “ramp” vs “primary street” won’t drastically affect navigation / routing. The only two street types that do this with any significant degree are Private Road and Parking Lot Road. Other than that, it’s only a matter of slight preference that is given to higher streets.
There were some weird elevation issues – try to keep joining segments no different in elevation than one or two. I’m not certain it makes a huge difference, but it seems to sometimes cause a bug in the routing engine. That’s the only reason I can see for it to have directed a user off the primary street and onto the taxi lane, for example.
I’ve restored the deleted ramp – but I don’t know its name. Can you advise on that?
I’ve also added restrictions for the taxi and bus lanes (i.e. only taxis and buses are permitted, respectively).
actually the street view is clear
airport // ave Cardinal
and the actual problem here is when u seek the airport like “YUL”
u end up on the taxi lane as destination
so i think its out of commun editor control
Perhaps the taxi lane is the “closest” street to the YUL landmark.
The solution at this point: disconnect the taxi lane from the regular roadways.
HOWEVER, let’s allow the changes I’ve made (including restrictions) to get into the system before we do that – if it’s still routing funny on Saturday, then we can do the disconnection.
i can see 2 address for the airport when u seek “YUL” in your destinations
one is good and one on the taxi lane
Good
Aéroport international Pierre-Elliot-Trudeau (YUL), Dorval, Quebec
https://www.waze.com/livemap/?zoom=15&lat=45.5&lon=-73.66153&from_lat=45.50001&from_lon=-73.66154&to_lat=45.45764&to_lon=-73.7497#
BAD, Taxi lane
Montréal-Pierre Elliott Trudeau International Airport (YUL), Dorval
https://www.waze.com/livemap/?zoom=15&lat=45.5&lon=-73.66153&from_lat=45.50001&from_lon=-73.66154&to_lat=45.45764&to_lon=-73.7497#
have fun to follow the info
so my solution is to delete the english link to the airport and copy the french one to rename it in english.
i dont know how i could do that, but its the solution i see for this issue
That makes some sense – except the english one doesn’t exist at all. 
Let’s leave things as is until Saturday – then re-evaluate.
this is a bit out of the issue, but montreal could benefit of several destinations
arrivals
departure
long term parking
short term parking
yep its a load to add and many public facilities in the world could benefit
That may be an upcoming feature – or at least there may be an upcoming feature that can be exploited for that use. Stay tuned.
as i could see this issue is solved and some new options could be in a new project
thanks for your help
Attention, mon ami. Le street view n’est pas en courant.
In this view, it still has the ramp onto 520, which no longer exists. The sign may have changed. Also, in this view, the sign indicates direction to the airport, but the street remains Côte-de-Liesse. It is not a ramp.
On a related matter, for Doctorkb:
You replaced the missing ramp but misnamed it and it’s locked at level 6: https://www.waze.com/editor/?env=usa&zoom=5&lat=45.45233&lon=-73.74182&layers=1925&segments=78661668
I’m not sure which exit number it should be, but it definitely should say “Sortie” instead of “Exit”. I’ll drive on that ramp on April 11, if not sooner, and check it out.