[Script] WME Junction Node Fixer v0.2.1 2017-08-16

Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.

Moderators: Unholy, bextein

Forum rules
Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.

DO NOT START a new thread unless it is about a new idea. Keep discussion of existing tools within the main thread for that tool.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.

Re: [Script] WME Junction Node Fixer v0.0.8.2 2014-01-29

Postby kentsmith9 » Thu Apr 10, 2014 4:02 pm

bgodette wrote:
CBenson wrote:Why will there be an additional penalty? Waze told us ages ago there was a penalty to pass every junction node, but later told us that if the node only connects two segments the penalty is "null."
We've actually tested that. There's a penalty until drive analysis processes a drive across the new node. After that happens and a tile build happens, the assume transit time does appear to become zero, but until that happens it seems to be the old 5s penalty from the dark ages.

Bgodette, can you check my new entry in the wiki of your note here. I thought it was already in the Wiki, but I couldn't find it.
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 5536
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 1472 times
Been thanked: 1681 times

Re: [Script] WME Junction Node Fixer v0.0.8.2 2014-01-29

Postby rivercitysyn » Thu Apr 10, 2014 3:37 pm

Is there a reason permissions are set so that the extension has access to so much in Chrome?

Would it be possible to restrict them in the next release for peace of mind?
rivercitysyn
 
Posts: 52
Joined: Thu May 27, 2010 8:45 pm
Location: Richmond, Virginia
Has thanked: 17 times
Been thanked: 2 times

Re: [Script] WME Junction Node Fixer v0.0.8.2 2014-01-29

Postby Olestas » Wed Apr 02, 2014 9:44 am

So, any news on when same connection roads splitting appears? :D
Olestas
Coordinators
Coordinators
 
Posts: 5789
Joined: Wed Mar 09, 2011 7:08 pm
Location: Latvia
Has thanked: 2813 times
Been thanked: 2070 times

Re: [Script] WME Junction Node Fixer v0.0.8.2 2014-01-29

Postby doctorkb » Fri Mar 28, 2014 8:38 pm

bgodette wrote:There are no instructions when there are no alternatives. That's in the Wiki btw.


I *know* I have received instructions when the street names are different, even when there's no alternative.

That said, I understand that we're talking about the same street names -- that's not to say that one won't get edited at some point and the other not, resulting in different ones by accident.

I'm still not clear why this is an argument -- if you have a highway that takes a nice gentle curve, and a street that cuts it off, why should we be putting the extra node into the highway?

Nodes *do* reduce the traffic display and reporting (i.e. if you report heavy traffic, it is only for the node you're on... too many nodes and the "heavy traffic" looks to be a very short span, when in fact, it can be long).
doctorkb
Coordinators
Coordinators
 
Posts: 4091
Joined: Wed Nov 04, 2009 9:17 am
Location: Edmonton, Alberta, Canada
Has thanked: 624 times
Been thanked: 1622 times

Re: [Script] WME Junction Node Fixer v0.0.8.2 2014-01-29

Postby bgodette » Fri Mar 28, 2014 4:01 pm

CBenson wrote:While primarily a display issue, I believe there are some minor end-user experience/routing issues that are addressed as well. First, if the route begins or ends on a segment that connects with another segment at both ends, I think that sometimes the route is shown beginning or ending on the other segment. Second, if your route includes a segment that shares end nodes with another segment, if you deviate onto the other segment, it seems that waze does recalculate the route (admittedly not a significant problem as you end up at the same point anyway).
Perhaps. It would explain some of the "proceed to highlighted route" I occasionally get.
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3434
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 114 times
Been thanked: 537 times

Re: [Script] WME Junction Node Fixer v0.0.8.2 2014-01-29

Postby bgodette » Fri Mar 28, 2014 3:56 pm

CBenson wrote:Why will there be an additional penalty? Waze told us ages ago there was a penalty to pass every junction node, but later told us that if the node only connects two segments the penalty is "null."
We've actually tested that. There's a penalty until drive analysis processes a drive across the new node. After that happens and a tile build happens, the assume transit time does appear to become zero, but until that happens it seems to be the old 5s penalty from the dark ages.
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3434
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 114 times
Been thanked: 537 times

Re: [Script] WME Junction Node Fixer v0.0.8.2 2014-01-29

Postby bgodette » Fri Mar 28, 2014 3:53 pm

doctorkb wrote:Ok -- but making the change (i.e. putting that node in there) can introduce a few things:
1. if it's on a corner (a likely place for a geometry node, where the junction would be created), there could suddenly be a "turn left" or "turn right" instruction when before there was none.
There are no instructions when there are no alternatives. That's in the Wiki btw.
doctorkb wrote:2. there will be an additional penalty introduced (at least until the routing engine gets better knowledge of traffic)
5s for 1-2 days from the first time someone transits the node, same as an edit delay.
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3434
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 114 times
Been thanked: 537 times

Re: [Script] WME Junction Node Fixer v0.0.8.2 2014-01-29

Postby CBenson » Fri Mar 28, 2014 3:19 pm

doctorkb wrote:Ok -- but making the change (i.e. putting that node in there) can introduce a few things:
1. if it's on a corner (a likely place for a geometry node, where the junction would be created), there could suddenly be a "turn left" or "turn right" instruction when before there was none.

2. there will be an additional penalty introduced (at least until the routing engine gets better knowledge of traffic)

So does it not make sense to penalize the lower-classed street first?

I have never received a turn instruction at a point like this. Do you have a example of one that does, it would be interesting to determine when the instruction is given and when it is not.

Why will there be an additional penalty? Waze told us ages ago there was a penalty to pass every junction node, but later told us that if the node only connects two segments the penalty is "null."
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2355 times

Re: [Script] WME Junction Node Fixer v0.0.8.2 2014-01-29

Postby CBenson » Fri Mar 28, 2014 3:14 pm

While primarily a display issue, I believe there are some minor end-user experience/routing issues that are addressed as well. First, if the route begins or ends on a segment that connects with another segment at both ends, I think that sometimes the route is shown beginning or ending on the other segment. Second, if your route includes a segment that shares end nodes with another segment, if you deviate onto the other segment, it seems that waze does recalculate the route (admittedly not a significant problem as you end up at the same point anyway).

EDIT: I meant, waze does not recalculate the route.
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2355 times

Re: [Script] WME Junction Node Fixer v0.0.8.2 2014-01-29

Postby doctorkb » Fri Mar 28, 2014 3:08 pm

bgodette wrote:
doctorkb wrote:Can I suggest that lower ranking be split before longer?

If the short segment is a parking lot, it should still be the one to get a penalty over a street...
FYI all this connected to same node fix does is deal with a display problem in WME when drawing the route proposed by Waze. There is no actual issue being fixed by this in terms of end-user experience or routing.


Ok -- but making the change (i.e. putting that node in there) can introduce a few things:
1. if it's on a corner (a likely place for a geometry node, where the junction would be created), there could suddenly be a "turn left" or "turn right" instruction when before there was none.

2. there will be an additional penalty introduced (at least until the routing engine gets better knowledge of traffic)

So does it not make sense to penalize the lower-classed street first?
doctorkb
Coordinators
Coordinators
 
Posts: 4091
Joined: Wed Nov 04, 2009 9:17 am
Location: Edmonton, Alberta, Canada
Has thanked: 624 times
Been thanked: 1622 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: jarkaz