[Script] WME Validator 1.1.20 / 03.11.2016

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 Validator 0.7.3 (BETA) / 24.02.2014

Postby AlanOfTheBerg » Thu Feb 27, 2014 11:57 pm

berestovskyy wrote:
fvwazing wrote:So you DO check HN, though slow?

Yes I do and no it is not that slow. Last Sunday many people noticed that fwd/revCrossSpeed attributes have disappeared from WME, but there was a new handy attribute hasHNs, so the check was implemented ;)

Just FYI, hasHNs has been around for ... well almost since house numbers were added to WME. (Non-public link.)

Maybe now it is finally getting populated.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23613
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1126 times
Been thanked: 4791 times

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

Postby berestovskyy » Thu Feb 27, 2014 11:42 pm

fvwazing wrote:So you DO check HN, though slow?

Yes I do and no it is not that slow. Last Sunday many people noticed that fwd/revCrossSpeed attributes have disappeared from WME, but there was a new handy attribute hasHNs, so the check was implemented ;)

The check is marked as slow because we have to analyze adjacent segments, but it does not send any requests to the Waze server.
berestovskyy
 
Posts: 844
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 711 times

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

Postby fvwazing » Thu Feb 27, 2014 11:15 pm

berestovskyy wrote:
bgarch wrote:Enable "report railroads connected to drivable roads" for any country.

Force update the script, it's done few versions back:
24.02.2014 v0.7.2:
- UPD 'Non-drivable connected to drivable':
excluded short dead-end segments and segments with house numbers

19.02.2014 v0.7.0:
- NEW for ALL: 'Non-drivable connected to drivable'


Wow! So you DO check HN, though slow? Great!
fvwazing
 
Posts: 3589
Joined: Sat Nov 14, 2009 2:48 pm
Has thanked: 415 times
Been thanked: 385 times

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

Postby berestovskyy » Thu Feb 27, 2014 10:19 pm

kentsmith9 wrote:I did not see the official list linked to what letters are supposed to be allowed in each country. I assume there is some table?

For US it's just "to". Let me know if you need any other info.

But before you create the wiki page, please have a look at this forum post about Validator "country packs". I plan to extract translations and all country-specific data into separated scripts, so local communities could maintain the lists of exceptions, translations and enable/disable checks on their own.

AlanOfTheBerg wrote:At least OpenLayers has a function for you (Geometry.segmentsIntersect).

Sure, but we disagree on how many times we need to call this function :lol:
berestovskyy
 
Posts: 844
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 711 times

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

Postby qwaletee » Thu Feb 27, 2014 10:03 pm

irowiki wrote:
qwaletee wrote:Been wondering... what are the SLOW indicators for. They don't seem to be special errors or warnings, what information does this impart?


According to the script, it takes longer to process the stuff marked with SLOW.


So, basically a hint, if activity is slow for you, consider flipping off the SLOW switch. Which you'll probably never remember to turn back on, but hey, half a validator is better than no validator due to a frustrating user experience.
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2908
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 231 times
Been thanked: 1119 times

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

Postby AlanOfTheBerg » Thu Feb 27, 2014 4:48 pm

berestovskyy wrote:The search for overpasses is very expensive operation and would be extremely slow. If there are 500 segments on the map it will take ~125000 comparisons to check if a segment crosses another one.

It could be quite cumbersome, yes. At least OpenLayers has a function for you (Geometry.segmentsIntersect). :) But, I'm not sure if that function works with a single segment like we think of it, or if it requires each lineString which a single segment has a lineString between each geometry node.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23613
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1126 times
Been thanked: 4791 times

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

Postby glomp » Thu Feb 27, 2014 8:57 am

berestovskyy wrote:DISABLED for US 'More than 55 letters Ramp name'


Can we get this disabled for Australia?

With the work we have done for the addition of road shields, the format used for them can add an extra 7-10 characters to the name of a highway/freeway name. This makes the average length of a highway/freeway name about 25 characters.

With the addition of wording such as "entry to:/exit" and a couple of city destinations, it quickly makes the ramp names quite long.
glomp
Waze Global Champs
Waze Global Champs
 
Posts: 1799
Joined: Thu Aug 16, 2012 3:49 pm
Location: Western Australia
Has thanked: 418 times
Been thanked: 879 times

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

Postby berestovskyy » Thu Feb 27, 2014 6:49 am

irowiki wrote:I meant, search for segments that aren't set to ground level currently

Validator highlights issues not features. If you're looking for simple highlighting of non-ground segments, you should look somewhere else.

There are might be two issues with elevations:
1. Two segments intersect at the same elevation (it was discussed in this thread before).
2. A segment has non-ground elevation and no intersections (your request).

In both cases to check if a segment intersects with another, we have to compare it with every other segment on the map = very slow. Sorry, it won't be implemented unless we found another solution :(

JoniX3000 wrote:using the Swedish language on WME makes Validator use Spanish instead of Enligsh.

Thanks, will be fixed.
berestovskyy
 
Posts: 844
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 711 times

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

Postby JoniX3000 » Wed Feb 26, 2014 11:57 pm

I have not read the thread, so this maybe already have been reported, but if not, I've found a bug: using the Swedish language on WME makes Validator use Spanish instead of Enligsh.
JoniX3000
 
Posts: 60
Joined: Sun Jun 10, 2012 6:16 pm
Location: Söderhamn, Sweden
Has thanked: 5 times
Been thanked: 1 time

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

Postby irowiki » Wed Feb 26, 2014 10:25 pm

I meant, search for segments that aren't set to ground level currently, but that would probably be another script!
irowiki
 
Posts: 250
Joined: Tue Feb 11, 2014 3:05 pm
Has thanked: 68 times
Been thanked: 40 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: rmeatc_2