All the original post seem to have been deleted, are you able to add new ones?doctorkb wrote:Let me know if you need any original posts updated.
Sent using Tapatalk for Android 4.4.2
All the original post seem to have been deleted, are you able to add new ones?doctorkb wrote:Let me know if you need any original posts updated.
Yes the speed is calculated for the estimated time you'll arrive at the segment, and also for which segment you are going to after that segment. I.e. the same segment will a different speed depending on if you're going straight or making a turn at the end of it.okladriver wrote:I'm sure this is a Waze data issue and not something with the script, but has anyone seen same-segment times change depending on the overall route?
For example, I'm looking at two different routes with the same start and end point. I have one large segment that is common to both.
When I select one route it says the cross time is 64 seconds, when I select the other route it says the same segment is 78 seconds. Not a huge discrepancy, but odd to me.
Edit: Just had a thought. Do Waze calculate when you'll get to a certain segment and pull the data from that calculated time? That would make this behavior understandable if a different route had the driver getting to the common segment later or earlier than the other route.
Is that 33 and 29 in seconds to traverse, or mph? There is a difference in the math, you can choose in settings.taco909 wrote:...
Reason I ask is on a test road (no actual speed data), my transition time on the first segment varies depending on to where I drag the start point.
The counterintuitive issue is when the start point is in the center of the segment, the number is 33. If I drag the pin to the beginning of the segment, that number actually drops to 29.
This is a fairly short PS segment.
The script can only sow the routes out pulls from the server. If the server only returns one route, then that's all the script can show. Sometimes the client also only gives one route.Arnoniem wrote:Great update. Excellent visualisation of the 2way routes, just as I had in mind
Question: I ofter see that the script only gives 1 route, instead of 3 alternatives, while I have this enabled. Can you look into that or tell me what i'm doing wrong?
Thanks
I'm not sure what you mean by "Vector speeds" or where Waze said "they don't have vector speeds". Waze definitely does record a separate speed for each connection through a junction. In you're example the circled segment will have 3 speeds recorded when heading south, 1 for straight, 1 for left, and 1 for right. It also has a general average speed for the segment start to end. And it will have the same data for the other direction as well, traverse speed, and transition speed. This has been confirmed by Waze. And is discussed it the wiki under the title "turn delay". It is how Waze knows if a right is faster than a left, and the source of some.confusing detours.Olestas wrote:Another strange thing..
Waze stated they don't have vector speeds..
But I can not understand, why from the same segment left and right turn speeds differ according to real traffic situation (going right is 10 times faster then going left).
Light2015-04-29 11_59_16-Waze Map Editor.pngLeft2015-04-29 12_00_03-Waze Map Editor.png
There are two different processes, you are mixing the information from one to the other.Olestas wrote:Until now I was under impression, that waze DOES NOT differ directions from junction, but only takes segments average speed, which results in bad impact on complex junctions, where you can drive in different directions with different speeds. I also was informed by one of waze personnel, that traffic jams do not form on segment, if it has slow left turn, but fast straight drive... Even if left turn is totatlly standstill.
Even more, yesterday I lost 5 minutes on left turn, and waze was just sitting silent, while right turn drivers where passing by as wind.
I also learned not to believe wiki too often, as it sometimes is outdated or not 100% correct.
Although, from my screenshots, I see that there is difference, but in that time range, left turn still is much slower...
After opening the route speeds tab, are you selecting two segments simultaneously using multi-select so both segments end up highlighted at the same time?maqifrnswa wrote:Thank you. I select route speeds tab, select segments, and nothing happens. If I type in addresses into the route speeds tab and click "Calculate Route," nothing happens. I've tried every combination of checkboxes and disabled all addons except this one. I also used the firefox JS debugger and don't see any warnings or errors.taco909 wrote:No problems on Firefox here.maqifrnswa wrote:Thanks for this!
I'm having some problems: every time I try to use WME Route Speeds, nothing happens.
Has anyone had any luck with Firefox 38.0 on Ubuntu 15.04?
Please be sure to select the Route Speeds tab before selecting your segments. Once the segments are selected, the Route Speeds "A" and "B" pins will appear and may be dragged anywhere on the screen.
WME validator, URO+, UR comments all work fine
EDIT: same with chrome, it's probably an ubuntu thing... I'll check out the source code and see if there's anything I can fix
I think the script does this automatically if you find have "try more" checked. Can you confirm please?tonestertm wrote:Would be nifty to have a button which ranked the routes in the same order as Livemap. This wouid help a lot while investigating BDP issues.
I meant to say inchecked before. Sorry.tonestertm wrote:Nope. The only thing Try More does is increase the number of routes requested internally to 10 times the number shown in the selector box, then filter the best of the returned results out and display them according to the Route Type setting. I don't think I've ever seen this script do Livemap ranking, except maybe when it was first under development.82 to 5 detour Livemap route ranking.jpg82 to 5 detour Route Speeds Try More.jpg
Is this in Beta, show routes isn't authorized to work in Beta due to cross domain security, so this is the designed workaround.bz2012 wrote: WME show routes doesn't seem to be working as it used to work either. It is only showing a link toshow routes in livemap
Re: [Script] WME Route Speeds (Traffic)