[Script] WME Validator 1.1.8 / 07.05.2015

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.

Moderator: Unholy

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.1 (BETA) / 05.02.2014

Postby ditchi56 » Wed Feb 05, 2014 11:08 pm

Here's another example. What we have here is a road with a locked gate in the middle, to which only the residents have a key. Each end of the road is accessible to everybody, but only key holders can pass through.

If the central section isn't on the map, and any of the residents start driving through the gate with Waze running, Map Problems will result. OK, they can be deleted, but better to avoid them in the first place - besides an editor not knowing the situation might react to the Map Problem by creating an unrestricted link.

With the central section in but restricted, non-residents never get routed along the road past the gate. Neither do residents, which isn't ideal, but at least they know the area and can make their own decision to ignore the Waze route when they want.

So in my view, Validator should be detecting that the restrictions are different each side of the node, and not flagging it for removal.
ditchi56
Country Manager
Country Manager
 
Posts: 2324
Joined: Tue May 29, 2012 12:35 pm
Has thanked: 347 times
Been thanked: 859 times

Re: [Script] WME Validator 0.6.1 (BETA) / 05.02.2014

Postby ditchi56 » Thu Feb 06, 2014 12:34 am

On this occasion, the "private road" penalty is not (or has not been at some time in the past) sufficient to stop through routing - passing through the gate saves a good ten minutes on some journeys, which is of course why the residents are so keen to keep their gate locked.
ditchi56
Country Manager
Country Manager
 
Posts: 2324
Joined: Tue May 29, 2012 12:35 pm
Has thanked: 347 times
Been thanked: 859 times

Re: [Script] WME Validator 0.6.1 (BETA) / 05.02.2014

Postby ditchi56 » Thu Feb 06, 2014 6:47 am

OK, here here is yet another example of where Validator is incorrectly saying "remove a node" because it isn't recognising restrictions. The northern part of Church St is a pedestrian precinct during the day only. Time restriction closes it 10:00-16:30. There is no junction at the change, just a gate which is closed 10:00-16:30, open at other times.

Now as it happens, Church St also goes 1-way at this point, so Validator wasn't complaining. But I've temporarily made it 2-way, and immediately Validator says get rid of the node, which would incorrectly apply the time restriction to the whole road.
ditchi56
Country Manager
Country Manager
 
Posts: 2324
Joined: Tue May 29, 2012 12:35 pm
Has thanked: 347 times
Been thanked: 859 times

Re: [Script] WME Validator 0.6.3 (BETA) / 12.02.2014

Postby ditchi56 » Thu Feb 13, 2014 12:31 pm

Suggestion: could it warn of

1) landmark too small to show on app? At least petrol (gas) station landmarks if not other types?

2) roundabouts too small to show on app?
ditchi56
Country Manager
Country Manager
 
Posts: 2324
Joined: Tue May 29, 2012 12:35 pm
Has thanked: 347 times
Been thanked: 859 times

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

Postby ditchi56 » Fri Feb 28, 2014 8:09 am

I think the detection of "overlapping segments at node x" is fantastic.

Can you extend it to pick up cases like these, where the road loops round and ends on itself (a hangover from take-on from the base map)? https://www.waze.com/editor/?zoom=6&lat=51.12759&lon=-0.75347&env=row&layers=997&segments=121553822,121553824 Waze doesn't navigate them properly at all, not surprisingly since the apparent junction isn't really a junction on the map.
ditchi56
Country Manager
Country Manager
 
Posts: 2324
Joined: Tue May 29, 2012 12:35 pm
Has thanked: 347 times
Been thanked: 859 times

Re: [Script] WME Validator 0.7.4 (BETA) / 28.02.2014

Postby ditchi56 » Tue Mar 04, 2014 12:52 pm

berestovskyy wrote:Validator reports up to 300 segments per issue to save memory. So if you pan around the map for some time and there are more than 300 segments with 'Soft turns' for instance, Validator will stop highlighting soft turns, but will continue to highlight other issues.

Would it be possible to have a function in Validator settings to control the maximum number of items reported? My poor old computer runs out of memory for handling the report,which takes ages to load, and even to scroll a page. I think I'm asking for a limit on the total number of items reported, rather than a limit on items for a particular issue.
ditchi56
Country Manager
Country Manager
 
Posts: 2324
Joined: Tue May 29, 2012 12:35 pm
Has thanked: 347 times
Been thanked: 859 times

Re: [Script] WME Validator 0.7.4 (BETA) / 28.02.2014

Postby ditchi56 » Tue Mar 04, 2014 5:17 pm

berestovskyy wrote:
ditchi56 wrote:Would it be possible to have a function in Validator settings to control the maximum number of items reported?

Could you please give me a permalink to an area where your browser is out of memory? I'll have a look how many segments/issues are there...

This part of suburban London produced a large report and I wasn't even zoomed right out. When I eventually managed to get to the summary page, it said "WME Validator has checked 11653 segments and reported 12 errors (1‰), 277 warnings (24‰) and 261 notes"

Now of course I can zoom in further and try again, but it would be nice not to have to remember which areas are fairly clear (so I can run Validator zoomed out) and which still have lots of problems. If I could set a limit of, say, 100 in the Validator settings I could then just forget about it - and I probably wouldn't want to fix more than 100 problems in one session anyway.
ditchi56
Country Manager
Country Manager
 
Posts: 2324
Joined: Tue May 29, 2012 12:35 pm
Has thanked: 347 times
Been thanked: 859 times

Re: [Script] WME Validator 0.7.4 (BETA) / 28.02.2014

Postby ditchi56 » Tue Mar 04, 2014 11:00 pm

berestovskyy wrote:
ditchi56 wrote:it said "WME Validator has checked 11653 segments and reported 12 errors (1‰), 277 warnings (24‰) and 261 notes"

It means there are just 12+277+261 issues :? Even if I lower the limit to a 100 of segments per check, I guess it will change nothing for such a low amount of the issues.

Maybe the problem is not related to Validator itself? You might opened too many WME windows or something?

I believe the problem (apart from a machine running low on storage) is the size of the "data" web page generated for the report. So the limit would need to be on the number of items reported, not the number of segments checked (although obviously it would make sense to stop checking once the limit on items to report was reached).
ditchi56
Country Manager
Country Manager
 
Posts: 2324
Joined: Tue May 29, 2012 12:35 pm
Has thanked: 347 times
Been thanked: 859 times

Re: [Script] WME Validator 0.7.4 (BETA) / 28.02.2014

Postby ditchi56 » Thu Mar 06, 2014 11:17 am

berestovskyy wrote:
ditchi56 wrote:I believe the problem (apart from a machine running low on storage) is the size of the "data" web page generated for the report.

I just measured the size of "data" document for the area you send me (12+277+261 issues). It is less than 100KB (Save page as->HTML Only).

I tried few versions back to generate the report in a bit different way, but this "data" method was the most reliable and worked both in Chrome and Firefox. I guess I have to try again...

I've tried creating a "large" report that Firefox has real trouble scrolling around on my overloaded machine. Then I saved it, and reopened it from the saved file. Firefox now had no trouble. So it looks like there's something in Firefox that doesn't handle "data" pages very well.

No need now for you to change anything, except perhaps documentation. Now I know, I'll just save and reopen the report and everything seems to be fine.
ditchi56
Country Manager
Country Manager
 
Posts: 2324
Joined: Tue May 29, 2012 12:35 pm
Has thanked: 347 times
Been thanked: 859 times

Re: [Script] WME Validator 0.7.4 (BETA) / 28.02.2014

Postby ditchi56 » Thu Mar 06, 2014 11:10 pm

Minor problem: the script is reporting time restrictions as expired on the last day for while they apply. It should wait one more day before flagging them as expired.
ditchi56
Country Manager
Country Manager
 
Posts: 2324
Joined: Tue May 29, 2012 12:35 pm
Has thanked: 347 times
Been thanked: 859 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: No registered users