WME Validator localization for US

[ img ] This is the place to discuss issues that are relevant for locations in the US. For any other discussions, please use the main forums.

Re: WME Validator localization for US

Postby banished » Tue Apr 22, 2014 3:09 am

pumrum wrote:in the case of railroads, I believe -5 was chosen because roadways very rarely need to deviate down 5 levels from ground, and having railroads and road segments intersect is very common - so they chose the elevation least likely to interfere with the drivable roadways.


Railroads are set at -5 and disconnected from any drivable road out of an abundance of caution to mitigate against inadvertent/newbie connections. We all have a healthy concern that even if railroads are not supposed to be navigable, no one wants to take the chance.

Railroads are also (supposed to be) locked at L-5 for the same inadvertent/newbie reason. This has not yet been added to the Road Type wiki.

Best to you,
GC, ARC, Veteran, CISSP, MCP
banished
Waze Global Champs
Waze Global Champs
 
Posts: 837
Joined: Mon Sep 28, 2009 11:03 am
Has thanked: 309 times
Been thanked: 229 times

Re: WME Validator localization for US

Postby berestovskyy » Tue Apr 15, 2014 7:50 pm

Hi!
sketch wrote:I think I had problems with \d when actually building the file. berestovskyy suggested I use [0-9] instead.

When we move a RegExp from the "Custom RegExp" field into the localization pack, we have to escape all backslashes, i.e. use '\\' instead of '\' or use '[0-9]' instead of '\d'.

In other words:
Custom RegExp field: I-\d{1,3}
--> Localization pack "regexp" property: "I-\\d{1,3}"


I suggest to use checks #160-167 to easily mix road types with street names. Simply enable the corresponding check in your localization pack and set the regexp param.


At the moment there are two template variables for road types:
${type} - expands to WME road type number, i.e. 3 for Freeway, 6 for Major, 7 for Minor etc.
${typeRank} - expands to road type "rank", i.e. 1 for Runway ... 15 for Freeway (see Road type drop-down list for the order)
berestovskyy
 
Posts: 897
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 821 times

Re: WME Validator localization for US

Postby berestovskyy » Tue Apr 15, 2014 8:37 pm

sketch wrote:160-167 won't work in the US though — we can't say a Freeway has the wrong name, because although there are plenty freeways named say "I-10 W", there are also plenty freeways named "US-90 W" and "SR-63 N" and "Florida's Tpke S"

Sure, you just list all of those formats in regexp field for #160 and you're done. Here is a working example for BeNeLux:
Code: Select all
"160.enabled": true,
"160.problemLink": "https://wiki.waze.com/wiki/Benelux_Freeway",
"160.params": {
   "solutionEN": "Rename the Freeway segment to a 'Anum' or 'Anum - Enum' or 'Anum ri Dir1 / Dir2'",
   "regexp": "!/^A[0-9]+( - (A|E)[0-9]+)*( ri [^\\/]+( \\/ [^\\/]+)*)?$/",
},


sketch wrote:Since 70 et seq. are programmed as inverse of this, they also won't work.

Just leave #70 disabled.

sketch wrote:Easy enough when you are using a road type affirmatively, but when you're trying to negate it, problems can arise.

Sure, it's a bit complicated, so I suggest to use checks #160-167 instead ;) See the example above.
berestovskyy
 
Posts: 897
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 821 times

Re: WME Validator localization for US

Postby Bigbear3764 » Thu Jun 26, 2014 1:10 pm

krikketdoug wrote:I'll admit this is local to Chicago, IL, but I don't know where else to ask the question, and it may be relavent to other local areas within ths US.

Waze is in the process of including vehicle types, including trucks. Validator has shown the ability to interact with the restrictions layer. For example, I can see expired restrictions.


Don't go setting restrictions for trucks on these roads. Until waze has a setting on your phone to set what type of vehicle you are driving, setting any restriction will restrict all vehicles.


Sent from my iPhone using Tapatalk
Bigbear3764
Country Manager
Country Manager
 
Posts: 2617
Joined: Fri Feb 10, 2012 8:02 pm
Location: Island Lake, IL USA
Has thanked: 220 times
Been thanked: 962 times

Re: WME Validator localization for US

Postby CBenson » Thu Jun 26, 2014 6:33 pm

I frequently come across truck restrictions added to the map. They seem to have no effect at all at this point, as you can't indicate you are truck.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
CBenson
EmeritusChamps
EmeritusChamps
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1055 times
Been thanked: 2353 times

Re: WME Validator localization for US

Postby crazycaveman » Mon Oct 27, 2014 7:05 pm

Wasn't sure if anyone had posted checks for wrong road types on segments yet (searched and didn't see anything), but here's my stab at it (s18slider and I did a good bit of troubleshooting on it):

Code: Select all
// All US Highways should be at least Major Highway (except BUS, SPUR, LOOP)
${typeRank}#${street}@#${altStreet[0]}@#${altStreet[1]}@#${altStreet[2]}@#${altStreet[3]}@#${altStreet[4]}@#${altStreet[5]}@#${altStreet[6]}@#${altStreet[7]}@#${altStreet[8]}@#${altStreet[9]}@
/^[1-9](?![245]).*#(?:US Hwy |US-)\\d+(?: [NSWE]| ALT| BYP| CONN| TRUCK| SCN| Scenic)*@/i

Code: Select all
// All State Highways should be at least Minor Highway type (except BUS, SPUR, LOOP)
${typeRank}#${street}@#${altStreet[0]}@#${altStreet[1]}@#${altStreet[2]}@#${altStreet[3]}@#${altStreet[4]}@#${altStreet[5]}@#${altStreet[6]}@#${altStreet[7]}@#${altStreet[8]}@#${altStreet[9]}@
/^[1-9](?![2-5]).*#(?:(?:State Hwy |SR-|SH-|K-|LA-|M-|MA-|MS-|NC-|SC-)\\d+(?: [NSWE]| ALT| BYP| CONN| TRUCK| SCN| Scenic)*|(?:US Hwy |US-)\\d+(?: [NSWE]| BUS| LOOP| SPUR)+)@/i

Code: Select all
// All State BUS, SPUR, LOOP Highways should be at least Primary Street type
${typeRank}#${street}@#${altStreet[0]}@#${altStreet[1]}@#${altStreet[2]}@#${altStreet[3]}@#${altStreet[4]}@#${altStreet[5]}@#${altStreet[6]}@#${altStreet[7]}@#${altStreet[8]}@#${altStreet[9]}@
/^[1-9](?![1-5]).*#(?:State Hwy |SR-|SH-|K-|LA-|M-|MA-|MS-|NC-|SC-)\\d+(?: [NSWE]| BUS| LOOP| SPUR)+@/i


I believe I have the right state abbreviations in there for all the states. Might also be able to modify that last check to include county highways/routes, too.
[ img ][ img ] [ img ][ img ][ img ]
ARC: South Atlantic Region
crazycaveman
US Waze Champs
US Waze Champs
 
Posts: 832
Joined: Fri Sep 03, 2010 1:48 am
Location: Rock Hill, SC, USA
Has thanked: 352 times
Been thanked: 522 times

Re: WME Validator localization for US

Postby crazycaveman » Tue Oct 28, 2014 12:33 am

Yeah, the limit was raised. I'm trying to put one together specifically for SC, which is where I came up with this. I'm sure there's a way to simplify it, but then again, maybe not.
[ img ][ img ] [ img ][ img ][ img ]
ARC: South Atlantic Region
crazycaveman
US Waze Champs
US Waze Champs
 
Posts: 832
Joined: Fri Sep 03, 2010 1:48 am
Location: Rock Hill, SC, USA
Has thanked: 352 times
Been thanked: 522 times

Re: WME Validator localization for US

Postby crazycaveman » Tue Nov 04, 2014 9:53 pm

Found an error in my above regular expressions. Here are the correct ones:

Code: Select all
// All US Highways should be at least Major Highway (except BUS, SPUR, LOOP)
${typeRank}#${street}@#${altStreet[0]}@#${altStreet[1]}@#${altStreet[2]}@#${altStreet[3]}@#${altStreet[4]}@#${altStreet[5]}@#${altStreet[6]}@#${altStreet[7]}@#${altStreet[8]}@#${altStreet[9]}@
/^[1-9](?![245]).*#(?:US Hwy |US-)[0-9]+(?: ALT| BYP| CONN| TRUCK| SCN| Scenic| [NSWE])*@/i

Code: Select all
// All State Highways should be at least Minor Highway type (except BUS, SPUR, LOOP)
${typeRank}#${street}@#${altStreet[0]}@#${altStreet[1]}@#${altStreet[2]}@#${altStreet[3]}@#${altStreet[4]}@#${altStreet[5]}@#${altStreet[6]}@#${altStreet[7]}@#${altStreet[8]}@#${altStreet[9]}@
/^[1-9](?![2-5]).*#(?:(?:State Hwy |SR-|SH-|K-|LA-|M-|MA-|MS-|NC-|SC-)[0-9]+(?:| ALT| BYP| CONN| TRUCK| SCN| Scenic| [NSWE])*|(?:US Hwy |US-)[0-9]+(?: BUS| LOOP| SPUR)+(?: [NSWE])?)@/i

Code: Select all
// All State BUS, SPUR, LOOP Highways should be at least Primary Street type
${typeRank}#${street}@#${altStreet[0]}@#${altStreet[1]}@#${altStreet[2]}@#${altStreet[3]}@#${altStreet[4]}@#${altStreet[5]}@#${altStreet[6]}@#${altStreet[7]}@#${altStreet[8]}@#${altStreet[9]}@
/^[1-9](?![1-5]).*#(?:State Hwy |SR-|SH-|K-|LA-|M-|MA-|MS-|NC-|SC-)[0-9]+(?: BUS| LOOP| SPUR)+(?: [NSWE])?@/i


My previous checks would catch the cardinals when checking for BUS/SPUR/LOOP, so if a street or primary street was named US-99 N it would get flagged twice. This should fix that
[ img ][ img ] [ img ][ img ][ img ]
ARC: South Atlantic Region
crazycaveman
US Waze Champs
US Waze Champs
 
Posts: 832
Joined: Fri Sep 03, 2010 1:48 am
Location: Rock Hill, SC, USA
Has thanked: 352 times
Been thanked: 522 times

Re: runways

Postby dbraughlr » Wed Apr 16, 2014 9:36 pm

pumrum wrote:Railroads not level -5 or at least rank 3:

I recommend extending this to runways as well.
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

Re: WME Validator localization for US

Postby DwarfLord » Thu Jul 24, 2014 1:56 am

sketch wrote:Since "St" is now pronounced "Street" regardless of location in the phrase, we have a lot of work to do to change all abbreviations of "Saint" as "St" to "St."

A fellow editor tells me that lots of users are still running a version of the Waze client that doesn't reliably pronounce "St." as "Saint" (I'm told this capability only arrived in June).

Based on this understanding and the sensible desire for backward compatibility he has been changing some recent "St." edits to spell out the "Saint".

What is the consensus on maintaining backward compatibility here? Clearly we want to stamp out use of "St" for "Saint", but should we be actively removing "St." abbreviations as well, and replacing them all with the spelled-out version so that older clients work?

Or should we switch to "St." wherever we find the opportunity and abandon backward compatibility in this case?
DwarfLord
Wiki Master
Wiki Master
 
Posts: 2500
Joined: Sat Dec 07, 2013 4:01 pm
Location: Santa Cruz Mountains, California USA
Has thanked: 1088 times
Been thanked: 1475 times

Next

Return to United States

Who is online

Users browsing this forum: No registered users