Tue Jan 21, 2014 12:32 am
SuperDave1426 wrote:I see what you're saying in the rest of the message; however, given the ratio of two-way to one-way streets (and the fact that WME runs opposite of that, requiring you to have to remember to go change the direction after you draw a road), I'm not sure that's a problem.
Someone who's used to it will click on it, see the direction is already two-way, and move on after wondering about it for a minute or two.
I admit that I certainly don't know about where you live, but here on the west coast the vast majority of roads are two-way, not one-way. It seems to me to make a lot more sense to have the editor default to "two-way." (I'm constantly having to deal with roads that should have been two-way, but the person who created them didn't bother to change the direction from the default "one-way" setting.) Failing that, having it be a feature of an extension is nice.
People have their preferences, though. I wouldn't mind it being a clickable option, so long as it's one of the options that will "stick" so that you don't have to keep going back to change it to what you want, if you happen to want the opposite of the default setting.
Tue Jan 21, 2014 12:54 am
Tue Jan 21, 2014 8:12 pm
AlanOfTheBerg wrote:gizmouf wrote:[b]Street name starting without upper case
There was a US discussion in the last couple of months about whether there are proper places to not have first letter upper case on real streets. I don't remember the thread or the outcome at this time, but this needs examination. Ramps starting with "to" should definitely be an exception for this check, at least in the US.
Thu Jan 23, 2014 4:57 pm
Fri Jan 24, 2014 6:09 pm
berestovskyy wrote:sketch wrote:Perhaps directional words should be excluded from the city name check...
Please have a look at Might be incorrect city name explained (forum post). This i case #10 Add/remove word. It has a limit: 10 segments. If you would have more than 10 'West Memphis' segments, they would completely disappear from the report.
I'm not sure if we shall add directional words in all languages. I'd rather to lower the limit mentioned above...
Sat Feb 01, 2014 8:01 pm
Maybe a minor enhancement could be done.
When you select multiple segments, you got something like that.
Maybe you can disable the report when multiple select is performed or at least grouping errors by #type?
Mon Feb 03, 2014 5:38 pm
SuperDave1426 wrote:berestovskyy wrote:If this one-way Ramp has a turn enabled to another one-way Ramp. Here is an example: permalink
I fail to see why that is an "unneeded name," given the length of the ramp. I've seen lots of named segments of that nature out here, and have been doing it that way all along, since it helps to provide guidance to drivers making their way to the freeway.
Mon Feb 03, 2014 5:44 pm
SuperDave1426 wrote:berestovskyy wrote:03.02.2014 v0.5.10:
- NEW for ALL 'Too short segment' (less than 2m long)
Just a "point of curiosity" question, but how does a segment less than 2 meters in length (which is a bit over 6 feet) cause a problem? I agree, it's kinda pointless to put in a segment that's that short, but I'm wondering why there's a check for it (not opposed; just curious).
Mon Feb 03, 2014 5:57 pm
dbraughlr wrote:Why is it wrong for walking trails, boardwalks, and runways to be elevation -5?
I hadn't heard that -5 means railroad. -5 is just a convention that mean do not connect to roadway.
I don't see why a walking trail with elevation -5 is an error. What else should it be?
"Rails to trails" are very popular. Many trails follow old RR rights-of-way.
A useful check is a non-drivable type junctioned with a drivable type.
SuperDave1426 wrote:Ok, I see what you're saying there.sketch wrote:(ramp stuff)
Although there are still times where naming individual segments apply (as you mentioned further in your message), so it seems that a check of that type is probably still not a good idea. Both in the case that we're talking about and which you acknowledge, but also times when the name changes to provide directional information.
I.E., an offramp that splits; the split segments have information about what they're taking you to beyond simply the road name that they're connecting you to.
dbraughlr wrote:sketch wrote:So, this check should probably be adjusted to alert for any segment under [X] m long
... for any drivable segment except a terminal (dead-end) segment under [X] m long ...
Mon Feb 03, 2014 6:19 pm
dbraughlr wrote:sketch wrote:there's no reason* to have the extraneous name taking up space in the Waze database. It's just streamlining.
Whether the name takes up space is the database is a matter of how the database is designed. It doesn't affect routing. Regardless, it should not be the rationale driving this change.
dbraughlr wrote:sketch wrote:Remember that a lot of the checks in Validator are not necessarily wrong, they're just things that might need a look.
I'll reiterate the point I made, that many of these are just checks. Not everything needs action.
In practice, you are mistaken. There are many editors that expect the Validator to give their area a clean bill of health. Come to chat and talk to them. Editors have been deleting the loops flagged with "Same endpoints drivable segments" error. I recommended installing the updated Validator instead.
Any arbitrary "rules" like this should be turned off by default, clearly marked as informational when turned on, and marked with green or some color never used for errors.