Page 50 of 237

Re: [Script] WME Validator 0.6.0 (BETA) / 04.02.2014

PostPosted: Tue Feb 04, 2014 3:34 pm
by CBenson
Don't know about the Int'l server, but having two one-ways that connect the same two junctions has caused problems in my area. If the origin or destination is on one of the street waze will occasionally start or stop the route on the other. This has been solved by adding a extra junction on one of the segments.

Re: parallel paths to the same endpoints

PostPosted: Mon Feb 10, 2014 11:49 am
by CBenson
sketch wrote:
dbraughlr wrote:Let's consider first a one-way terminal loop.

What is the known navigation error in this situation?
How do you correct it?

I'm not sure what the problem would be on a one-way terminal loop, if any, but knowing which way to go from a dead-end isn't really a problem.

I've seen numerous reports of problems with one-way terminal loops. The problem is that waze ignores the one-way property of the road, so will appear to route either way around the loop. You correct it by putting two extra junctions in the loop.

Re: junctions with drivable and non-drivable

PostPosted: Mon Feb 17, 2014 10:25 pm
by CBenson
dbraughlr wrote:A ramp must be connected at both ends and the junction at one end must have a freeway/highway/ramp segment.

Must seems strong to me. These segments have been ramps for quite some time and I've never found enough of a reason to change them.

Re: [Script] WME Validator 0.7.0 (BETA) / 19.02.2014

PostPosted: Thu Feb 20, 2014 4:41 pm
by CBenson
berestovskyy wrote:- NEW for ALL: 'More than 55 letters Ramp'

I'm curious as to where the guidance for this check comes from.

Re: [Script] WME Validator 0.7.0 (BETA) / 19.02.2014

PostPosted: Fri Feb 21, 2014 11:39 am
by CBenson
berestovskyy wrote:
CBenson wrote:
berestovskyy wrote:- NEW for ALL: 'More than 55 letters Ramp'

I'm curious as to where the guidance for this check comes from.

It comes from the suggestion in this thread: forum post No objections, so the check is implemented.
Let me know if the check should be disabled for US.

bedo2991 wrote:Edit: another thing that might be useful worldwide could be a warn: "Ramp streetname is too long". (Maybe 65 chars, not to bee too restrictive). We have some editors that take all the possible destination shown in the road signs and put them all in the ramp streetnames...

Hmm, that's exactly what I do - put all the possible destinations shown on the road sign in ramp streetnames. If the check is useful to others that's fine. But I'm not limiting my ramp names to 65 characters.

Re: ramp as non-highway connector

PostPosted: Sat Feb 22, 2014 12:02 pm
by CBenson
dbraughlr wrote:
kentsmith9 wrote:Unless someone can identify the problem

Simply put, there is not Road Type for connectors below the class of highways (freeways, MH, mH).
(I highly favor adding a proper road type for connectors; perhaps this is what "Service road" was originally intended to do.)

For normal classification Streets (primary street, street, and the obsolete service road), any connector is the lower of the two ends.

For Other - drivable (dirt roads, parking lot roads, and so forth) and all Non-drivable types, any connector is just whatever it is.

Ramp is a highway classification in the taxonomy of Road types.
Using Ramp for a street is a misuse of a highway road type for non-highway function.

    Highway
    • Freeway
    • Major highway
    • Minor highway
    • Ramp
    Street
    • Primary street
    • Street
    • Service road

Maybe this discussion should be split from this thread again, but I disagree with this statement. The guidance in the US, as noted above, is that ramps are to be used for grade separated connections. We could discuss changes, but "highway function" is term that we can endlessly debate. Again we should likely have that debate elsewhere.

Re: [Script] WME Validator 0.7.1 (BETA) / 20.02.2014

PostPosted: Sat Feb 22, 2014 5:31 pm
by CBenson
GizmoGuy411 wrote:Would anyone edit this any differently?

I guess I'd be inclined to map it as a walking trail. It seems (though it remains essentially unstated) that this is why waze will route to the end of a walking trail when the address is associated with the trail.

Re: [Script] WME Validator 0.7.1 (BETA) / 20.02.2014

PostPosted: Sat Feb 22, 2014 6:25 pm
by CBenson
Well I wish we could get some further guidance on what the developers intend for us to use walking trails for.

Re: [Script] WME Validator 0.7.3 (BETA) / 24.02.2014

PostPosted: Fri Feb 28, 2014 12:29 pm
by CBenson

Re: [Script] WME Validator 0.7.4 (BETA) / 28.02.2014

PostPosted: Fri Feb 28, 2014 8:05 pm
by CBenson
myriades wrote:In this case, there is no way that Waze failed the routing ;)

I disagree for the reason stated in the split thread.