Switch to full style
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.

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.
Post a reply

Re: [Script] WME Validator 1.1.16 / 29.01.2016

Tue Feb 23, 2016 2:50 am

Don't know if this has been addressed, but Validator is flagging roads as a bad name with the Expressway abbreviation Expy.

Re: [Script] WME Validator 1.1.16 / 29.01.2016

Tue Feb 23, 2016 3:11 am

I'll go find it again and check. Strange, the text to speech was able to read Expy as Expressway.

Re: [Script] WME Validator 1.1.16 / 29.01.2016

Tue Feb 23, 2016 3:18 am

Expy is how they use it in ND.
Attachments
Expy name.jpeg
(178.96 KiB) Downloaded 915 times

Re: [Script] WME Validator 2020.04.12 (PLACES BETA)

Thu Jul 16, 2020 1:34 pm

I have a suggestion for Validator. I think it would be useful to have an indicator on the Validator tab when Validator has too many issues. I sometimes pan around the map with Validator on and if I don't click a segment, I may not realize it's no longer highlighting segments because there are too many issues. Having a visual indicator without clicking on the segment would be useful for that use case.

Re: [Script] WME Validator 1.1.20 / 03.11.2016

Sun Nov 20, 2016 8:38 pm

Validator has stopped working for both Chrome and Firefox for me. What's Wrong?

Re: [Script] WME Validator 0.5.7 (BETA) / 29.01.2014

Fri Jan 31, 2014 11:32 am

Optimisation: you do not have to check the geometry if the boundingrectangles of segments do not overlap. But I guess you realized that one yourself. ;-)

Re: [Script] WME Validator 0.7.1 (BETA) / 20.02.2014

Sat Feb 22, 2014 1:15 pm

Segments WITH HN (driveable or not) are different from segments WITHOUT HN in that they are a legit navigationtarget. Often walkingtrails are used to connect houses to the correct street, disconnecting these trails would send the wazers to the wrong side of the block...

You wouldn't need the complete list of HN, just the confirmation that a segment has HN. Is that a separate/faster query?

[Script] WME Validator 0.7.1 (BETA) / 20.02.2014

Sat Feb 22, 2014 9:17 pm

berestovskyy wrote:
But still we have plenty of options for 'Non-drivable connected to drivable' check:
1. We can exclude dead-ends up to 300 m long.
2. Or we can enable check #115 just for some countries by request.
3. Or we can report just railroads connected to drivable roads.


I would go for #1; but the summum would be a recursive dead-end-check ;-)

Railroads are ALWAYS to be reported if connected to something drivable. As there are a number of countries that have substituted railroads by walking trail (with a distinctive name like "spoorlijn" or "railroad") those should be treated equivalent to RR.

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

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!

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

Fri Feb 28, 2014 12:06 am

Some dev READS this thread, maybe? Hello! Welcome!
Post a reply