[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.6.3 (BETA) / 12.02.2014

Postby berestovskyy » Wed Feb 12, 2014 10:59 pm

12.02.2014 v0.6.3:
- UPD 'Too short segment': roundabouts are excluded
- ENABLED for Bulgaria #27 'City name on Railroad'
- ENABLED for Chile #59, #86 and #93
- UPD 'Exclude non-editable segments' option for nodes
- Spanish translations thanks to robindlc and
fernandoanguita
- Spanish set as a default for AR, BO, CL, CR, CO, CU,
DO, EC, GQ, GT, HN, MX, NI, PA, PE, PY, SV, UY, VE
- fixed map scan: not all of the segments were reported
- ISO date in report
- other minor fixes

BellHouse wrote:I don't quite understand what 2d) means.

Some checks have exceptions, for instance 'Lowercase street name (except country-specific words)'

gizmouf wrote:Here is another idea ... checking average speed on a segment

Sure, the average speed info is available. The problem is what do we do with those segments :?
berestovskyy
 
Posts: 844
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 711 times

Re: [Script] WME Validator 0.6.2 (BETA) / 07.02.2014

Postby davielde » Tue Feb 11, 2014 3:29 pm

berestovskyy wrote:
davielde wrote:I currently get an indicator that a median u-turn segment is too short when it is actually a one way cross street that intersects with a split road.

Sorry, I would appreciate a permalink. I'm looking into the code and the situation you describe is impossible :?


Now that I think it through, I believe that it was most likely a connectivity issue with the cross street segments that was causing the "u-turn" warning. The issues are reported in separate sections of the Validator report, but I clicked on the u-turn warning and likely fixed the glaring red connectivity issue at the same time. The u-turn problem was what stayed on the brain because it is more unique, whereas I've been fixing tons of connectivity problems recently.

Awesome tool!
davielde
 
Posts: 1219
Joined: Tue Sep 17, 2013 2:01 pm
Location: Michigan, USA
Has thanked: 469 times
Been thanked: 756 times

Re: [Script] WME Validator 0.6.2 (BETA) / 07.02.2014

Postby bedo2991 » Tue Feb 11, 2014 11:33 am

Suggestion: do not warn for "segment too short" on roundabouts' segments:
Example: https://www.waze.com/editor/?zoom=10&la ... =244307615
bedo2991
Waze Global Champs
Waze Global Champs
 
Posts: 1275
Joined: Sat Jan 07, 2012 12:45 pm
Location: Italy, Marche
Has thanked: 266 times
Been thanked: 769 times

Re: [Script] WME Validator 0.6.2 (BETA) / 07.02.2014

Postby ituajr » Tue Feb 11, 2014 1:20 am

Would it be possible to extend the "Exclude non-editable segments" feature to "Exclude non-editable segments AND NODES"? At present the Validator reports problems with nodes that are outside the user's editable area - for example:
WMEV.JPG
(99.96 KiB) Downloaded 1990 times


Permalink for completeness: https://www.waze.com/editor/?zoom=4&lat=-34.6449&lon=139.26868&env=row&layers=813

Rollo
ituajr
Area Manager
Area Manager
 
Posts: 1321
Joined: Wed Oct 26, 2011 11:23 pm
Location: South Australia
Has thanked: 152 times
Been thanked: 662 times

Re: [Script] WME Validator 0.6.2 (BETA) / 07.02.2014

Postby fernandoanguita » Mon Feb 10, 2014 6:57 pm

bedo2991 wrote:
fernandoanguita wrote:Percentage is being calculated with a big error (Reported percentage is 10 times bigger than real)

Look more carefully to the "percentage" sign in your report: https://es.wikipedia.org/wiki/Por_mil
8:635 = x:1000
x = 8 * 1000 / 635 = 12.60


Oops... !!!!!
You are right, I was not careful enough to look it right. :oops:

Or may be I need glasses :D

Thanks for the quick reply !
fernandoanguita
Master Raider
Master Raider
 
Posts: 928
Joined: Mon Oct 01, 2012 2:53 am
Location: Concepción, Chile
Has thanked: 200 times
Been thanked: 477 times

Re: [Script] WME Validator 0.6.2 (BETA) / 07.02.2014

Postby berestovskyy » Mon Feb 10, 2014 6:46 pm

Hi,
‰ means promille (per thousand).

The is a bug introduced in 0.6.1 with "fixed few bugs with new and deleted segments". At the moment Validator reports ~2 times less segments (and hence ~2 times less errors) during the map scan. No problem with the highlighting, i.e. it highlights all of the errors on the map.

The issue will be fixed in the next version. Sorry for the inconveniences.
berestovskyy
 
Posts: 844
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 711 times

Re: [Script] WME Validator 0.6.2 (BETA) / 07.02.2014

Postby bedo2991 » Mon Feb 10, 2014 6:27 pm

fernandoanguita wrote:Percentage is being calculated with a big error (Reported percentage is 10 times bigger than real)

Look more carefully to the "percentage" sign in your report: https://es.wikipedia.org/wiki/Por_mil
8:635 = x:1000
x = 8 * 1000 / 635 = 12.60
bedo2991
Waze Global Champs
Waze Global Champs
 
Posts: 1275
Joined: Sat Jan 07, 2012 12:45 pm
Location: Italy, Marche
Has thanked: 266 times
Been thanked: 769 times

Re: [Script] WME Validator 0.6.2 (BETA) / 07.02.2014

Postby fernandoanguita » Mon Feb 10, 2014 6:19 pm

Dear Berestovskyy,

I have some small issue on the report of the area on the permalink.

At the end of the report says:
Summary
WME Validator has checked 635 segments and reported 2 errors (3‰) and 8 warnings (13‰).

3% of 635 errors is not 2 errors, and
13% of 635 errors is not 8 errors.

Percentage is being calculated with a big error (Reported percentage is 10 times bigger than real)

As you can see Validator has aloud me to reduce significantly the errors of the area (over 200 when started fixing it, I didn´t check percentage before starting).

I hope you can fix this small issue, it is not a bug, is just a small issue and has nothing to do with the proper functionality of the error detection.

Best regards form Concepción, Chile,
fernandoanguita
Master Raider
Master Raider
 
Posts: 928
Joined: Mon Oct 01, 2012 2:53 am
Location: Concepción, Chile
Has thanked: 200 times
Been thanked: 477 times

Re: [Script] WME Validator 0.6.2 (BETA) / 07.02.2014

Postby gizmouf » Mon Feb 10, 2014 11:28 am

Here is another idea to be discussed (or not :) ): checking average speed on a segment (don't know if you can get it like the Color Highlights script do) and highlight those with excessive speed regarding the road.

I have URs that appears with weird detours being proposed and the explanation seems to be one or several segments with illogical speeds registered. The cause of this is segments that have been re-used and modified, sometimes generating a false average speed.

Like 150 km/h on a ramp (with the Freeway attached to it being limited to 90), and Waze tells the driver to exit the Freeway just to re-enter on it the next ramp (without any trafic jam or whatever on the Freeway).

Since you won't be able to know what the correct speed should be for each segment, you could do a general check and mark all the segments with, for example, a speed over 150 km/h. Or 130 km/h but excluding Freeways. Or whatever seems logical in your country regarding a type of road.

The type of warning is to be determined (orange or red since it affects the routing).
gizmouf
Waze Local Champs
Waze Local Champs
 
Posts: 4929
Joined: Sat Jul 13, 2013 2:28 pm
Location: Nantes, France
Has thanked: 56 times
Been thanked: 716 times

Re: [Script] WME Validator 0.6.2 (BETA) / 07.02.2014

Postby BellHouse » Mon Feb 10, 2014 8:05 am

berestovskyy wrote:Further plans
Guys, let me know if you are interested in the following features:

1. User interface internationalization - i.e. translation of buttons, checkboxes, tips etc. on your language. Would it be useful or English is OK?

2. Separating translations from the main script. The main script will be slimmer and faster, while you will be able maintain translations on your own. I suggest to extract the following features:
a) UI translations (optional, see 1)
b) translation of check titles, problem descriptions, howtos and links localization
c) enabling/disabling checks for the country
d) managing exceptions and check parameters

Let me know what you guys think before I start to implement the functionality.
I would also like to hear if the script startup time in v0.6.2 is still an issue for you.

Yes, I think localizations would be helpful, as it would widen the user circle (not every editor is fluent in English). The translations can probably be handled by string lists, which could be fed to you by local persons or groups in each country. In particular, I like the idea of having localized links to wiki/howto references.

About 2c): I suggest to have a default enabled/disabled check list for each country, where each user can then individually edit his list. A reset-to-default functionality should allow fixing screwed-up configurations. ;)

I don't quite understand what 2d) means.
BellHouse
Waze Global Champs
Waze Global Champs
 
Posts: 3472
Joined: Sun May 12, 2013 5:57 pm
Location: Cologne / Germany
Has thanked: 790 times
Been thanked: 2466 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: Baidu [Spider], Bing [Bot], kentsmith9