sketch wrote:Regarding "(Closed)" / "(Construction Zone)" / "CONST ZN":
According to wiki:
When a road is under long-term construction, but is not closed, add "(Construction Zone)"
So I'm not sure if Validator should suppress issues at the "not closed" road
A report for obsolete CONST ZN markers will be added.
sketch wrote:What I was thinking was that I could put in a name (whether "U-Turn" or "* North *" or whatever else), run the report, and get all the streets matching that name in the report.
At the moment all the filters run afterwards the scan. Validator scans and collects all of the issues. Then you click "Show report" and Validator applies the filters and shows the report.
This street match option you suggested would be applied during the scan and once it changed you would need to rescan the area. So this option does not fit well with the existing filter options
berestovskyy wrote:#115 Non-drivable connected to drivable at node B
I would say, don't mark it as an error when:
- the non-driveable is a dead-end road.
- the non-driveable has housenumbers on it.
No problem to exclude dead-ends, but the house numbers are not available. To get the numbers Validator would have to request Waze server, means it would be very slow
Toolbox also has an option to pull the house numbers from Waze server. So it might be twice slower, because Validator and Toolbox would request same house numbers twice...