This is on purpose for the safety of the map data. If an editor was using an older script that accessed data in a way that was no longer supported by a Waze back end update, they could not do it very long before the script would stop working. Clearly it is easy enough to get around the issue, but by that point the editor is likely to have access to be able to make other changes and also would notice the script is no longer working as intended.SuperDave1426 wrote:It would be nice if this update did not have an artificial, unneccessary expiration date in it....
I don't use the customization features of Validator, but this list looks like something that should be part of the instructions in the Wiki. Did we build a page for it to include these things?sketch wrote:typeRank
15 freeway
14 major highway
13 minor highway
12 ramp
11 primary street
10 street
9 service road
8 dirt road
7 parking lot road
6 private road
5 walking trail
4 pedestrian bdwk
3 stairway
2 railroad
1 runway
type
1 street
2 primary street
3 freeway
4 ramp
5 walking trail
6 major hwy
7 minor hwy
8 dirt
9
10 ped boardwalk
11
12
13
14
15
16 stairway
17 private road
18 railroad
19 runway
20 parking lot road
21 service road
I don't know about the new Ferry type, I haven't tested it yet.
After 3+ years of it being an accepted abbreviation across the US, why did it change to unaccepted?PesachZ wrote:This is for the US, Expwy is our recommended abbreviation for Expresswaywhatnt wrote:v 1.1.10 is flagging "Expy" as an incorrectly abbreviated street name.
PesachZ wrote:The MUTCD lists "Expwy" as the exclusive acceptable abbreviation for expressway.
I believe most BGS where expressway is abbreviated it appears as "Expwy", and not "Expy".
OCD. Highlighted. Duh.PesachZ wrote:I want to add that although Expy is not recommended, it will still work with our current TTS engine, so there is no urgent rush to fix them all immediately. However it should something you fix when you see it.
SF Bay Area done as far as I can see.PesachZ wrote:I want to add that although Expy is not recommended, it will still work with our current TTS engine, so there is no urgent rush to fix them all immediately. However it should be something you fix when you see it.
However, validator shows an error I presume because the new USA version of the new page shows it should be:'E' St, Rio Linda, California
Is the Wiki link from validator for a particular error able to change to different country specific pages? Or do we need to solve the problem on the one Wiki page?E. St, Rio Linda, California
I wasn't sure it could be dynamic with those Wiki links, but that is good news.PesachZ wrote:validator should be updated so that in the US I shows the link to the USA version of the page.
Re: [Script] WME Validator 1.0.2 / 04.07.2014