Does waze do any route calculations on its own

[CBenson]

@bgodette

@CBenson

@bgodette

This “ramp” might have something to do with it.

What’s wrong with that ramp?

Nothing, other than it being a Ramp in the middle of a desired route when the alternate doesn’t have one.

I can’t imagine why having ramp in the middle of the route would effect the routing. Besides the alternative has a ramp here.

@bgodette

@CBenson

@bgodette

Other than that there’s a whole lot of work, and I do me a lot, that needs to be done along the route from the bridge to Milton. Excessive junctions, IGN damage, reverse connectivity (dunno if that matters), bad turn restriction, two-ways that should be one-way, messed up geometry and junctioning at intersections, intersecting but not junctioned roads, etc etc.

Sure there is much clean up that could be done. But waze will route over those roads. So why won’t it route from Annapolis to Milton over them?

Other than the ramp, I’d guess mostly all the excessive junctions, the two routes from the bridge should have been a big hint. We also have no idea on the relative cost of each road type once the routing server switches to “long route” mode, we only know that Streets have a very high cost in relation of Freeway/Major/Minor/Primary. If it isn’t the excessive junctions then that would seem to imply that Major and Minor also have a higher cost than Freeway, but lower cost than Primary and Street, when doing long routes.

The two routes from the bridge show that its at least 50 minutes and 80 miles longer to go around the bay than over the bridge. Shouldn’t the times given by waze for the alternative routes already take into account the various routing penalties?

[bgodette1]

@CBenson

@bgodette

Other than the ramp, I’d guess mostly all the excessive junctions, the two routes from the bridge should have been a big hint. We also have no idea on the relative cost of each road type once the routing server switches to “long route” mode, we only know that Streets have a very high cost in relation of Freeway/Major/Minor/Primary. If it isn’t the excessive junctions then that would seem to imply that Major and Minor also have a higher cost than Freeway, but lower cost than Primary and Street, when doing long routes.

The two routes from the bridge show that its at least 50 minutes and 80 miles longer to go around the bay than over the bridge. Shouldn’t the times given by waze for the alternative routes already take into account the various routing penalties?

I don’t believe the ETA includes any of the penalty time for junctions, and that it only totals up transit times based on current/historical conditions.

All I can really suggest is to clean up the intended route and see what happens. If it still wants to go the long way round we’ll have a fairly strong indicator that in long route mode road typing really matters and it will strongly prefer to stay on Freeway.

[MikeJones3]

How long to map updates take to come live? I see some red roads on the map right after the bridge and it seems they are roads people fixed but they have not updated?

Also I did a lot of fixes on roads near my home in NJ and am wondering when they will be fixed

[CBenson]

http://status.waze.com/ seems to suggest that tiles should be updated with edits made through November 26. I’m not sure they’re there yet.

[bgodette1]

@CBenson

The current status is that all the segments now show as highway on my phone.

Waze will route over the segments if they are near the end of the route as seen here and here.

Now that I’ve got my 4+ status I’ve gone through that first route cleaning up all the minor issue, removed extraneous junctions, etc, from A to B. I did not work the reverse route, so the split roads in the other direction have only minor work done.

[CBenson]

So you were able to remove junctions across the route to Milton? Great it did need the work. I’m eager to see routing through that area.

[bgodette1]

@CBenson

So you were able to remove junctions across the route to Milton? Great it did need the work. I’m eager to see routing through that area.

Yeah no editing issues along the route to Milton. There were problems but nothing that would have prevented routing from the bridge, obviously since live map gave a route. The question now is if the cleanup makes enough of a difference to make it a preferred or even alternate from Annapolis.

Sent from my Kindle Fire using Tapatalk

[CBenson]

It getting better, waze will now route over the Bay Bridge. But still doesn’t route directly over the hinterlands of the Delmarva peninsula.

[bgodette1]

@CBenson

It getting better, waze will now route over the Bay Bridge. But still doesn’t route directly over the hinterlands of the Delmarva peninsula.
(unavailable attachment: Milton Improve.png)

Interesting, I’ll go over it again in case I missed something.

Sent from my Kindle Fire using Tapatalk

[bgodette1]

I cannot eliminate these junctions:
junction
junction
junction
junction
junction

[CBenson]

I’ve deleted them. I’m thinking about complicating the Chesapeake Bay Bridge though. The problem is that the northern span is three lanes while the southern span is two lanes. Thus, when the traffic is heavy eastbound, one lane of the northern span is used for eastbound traffic. Currently if you travel eastbound on the northern span, waze has problems. I will probably add the crossover roads and make the northern span two way. The crossover roads should likely be parking lot roads or something like that so that waze won’t route eastbound on the northern span, but if you go that way enable waze to route you off the bridge.

[MikeJones3]

@CBenson

I’ve deleted them. I’m thinking about complicating the Chesapeake Bay Bridge though. The problem is that the northern span is three lanes while the southern span is two lanes. Thus, when the traffic is heavy eastbound, one lane of the northern span is used for eastbound traffic. Currently if you travel eastbound on the northern span, waze has problems. I will probably add the crossover roads and make the northern span two way. The crossover roads should likely be parking lot roads or something like that so that waze won’t route eastbound on the northern span, but if you go that way enable waze to route you off the bridge.

really good idea. I totally confused waze when I was on what it thought was the wrong bridge…

[bgodette1]

@CBenson

I’ve deleted them. I’m thinking about complicating the Chesapeake Bay Bridge though. The problem is that the northern span is three lanes while the southern span is two lanes. Thus, when the traffic is heavy eastbound, one lane of the northern span is used for eastbound traffic. Currently if you travel eastbound on the northern span, waze has problems. I will probably add the crossover roads and make the northern span two way. The crossover roads should likely be parking lot roads or something like that so that waze won’t route eastbound on the northern span, but if you go that way enable waze to route you off the bridge.

Local knowledge, and there’s even a UR for it.

[CBenson]

It’s routing straight across now. Thanks, bgodette.

[bgodette1]

@CBenson

It’s routing straight across now. Thanks, bgodette.

Just checked for myself, and yup it seems to be working. This brings up a lot of questions and concerns for me now, since what I did (restricted all turns and re-enabled) seems excessive to make the route work over something that didn’t seem to have any major issues after the first pass through.

Unsurprisingly the reverse route does not work as I didn’t do much on the westbound bits where the roads were split.

[jasonh300]

We have something similar here.

Note the HOV2 Lane, which is set as 2-way. It’s not disconnected at either end, so routing won’t take you on it, but if you go that way, Waze seems to always know which road you’re on.

https://www.waze.com/cartouche/?zoom=5&lat=29.93826&lon=-90.05773&layers=BTFTFTTTTTTFTTTTT