sublimese wrote:Why do I need to drive route A? Isn't the entire point of Waze that we are crowd-sourcing traffic? If route A is currently full of waze users, does waze really need me to also drive down route A so that it can tell me that that route A is bad?
chrysrobyn wrote:(I wish Waze had a helpful way of permalinking a route, including waypoints.)
sublimese wrote:When I tell it to show me the optional routes, it shows 3 additional routes, all of which are variations on Route A. All of which show best-case commute times, not current actuals or historical times.
The data on 70, 470, 25, 285 (Hampden) and 85 (Santa Fe) will be fine, and like I said Waze is consistent in +/- 2 minutes for my daily which is SE Aurora to Downtown. All site visits have been +/- 2 minutes to where my "driven" area covers pretty much all of the metro. Based on the description of Route B it might be running into a traveled vs straight line as all parts of B other than Kipling north of I-70 and Happy Canyon (Primary) and the actual destination are Minor or higher.AlanOfTheBerg wrote:sublimese wrote:Why do I need to drive route A? Isn't the entire point of Waze that we are crowd-sourcing traffic? If route A is currently full of waze users, does waze really need me to also drive down route A so that it can tell me that that route A is bad?
Not necessarily, no. If you can see that Route A is "full" of Wazers, I would think it would have valid data. I didn't see that you mentioned this about the other route earlier, hence my suggestion, but now that I think about it, with A being I-25 in Denver, I'd think the data is fine.
I know there are several editors in the Denver area, so that road should be just fine, as should route 'B' in general. Route length is something which can affect the road type which Waze will prefer to use which we have no influence over. At certain distances (I cannot recall specifics at this time), Waze will try to not route on anything less than primary street except to get you to one, and off of one near the destination. Longer distances and even Primary Street isn't preferred over highway/freeway. Your list of streets looks like highway or greater for the middle sections, which, again, should be fine for routing even for longer routes.
What is the total distance for your route B? Chatting with bgodette about it may be of use too, as he should be pretty familiar with the area.
No, not even close.chrysrobyn wrote:My money is on the routing server not agreeing that 285 / Alameda Ave is a valid cross-town route.
That would do nothing. Type only comes into play if there's a lack of historical data, which there isn't, or the route is very long (>200 miles before Major vs Minor starts to matter), which it isn't, and even then the distance tiers only increase the likelihood of the route getting pruned, it doesn't outright exclude Types.chrysrobyn wrote:I think you'd have to upgrade it to a Major Highway in order to overcome that barrier
Yes and no. We've managed to get Waze to increase the ratio at which is drops a route. In at least one distance tier it seems to be about 6:1.chrysrobyn wrote:If that's the case, is there a next course of action for the user or for his AMs?
Users browsing this forum: Google Feedfetcher, williehughes79