Moderators: Unholy, bextein, Glodenox, JustinS83
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.
by porubcan » Thu Jan 23, 2014 9:13 am
new check proposal:
check description: street name contains only space / non-breaking space (alt+0160) / blank space (alt+255)
What is the problem: in old Cartouche many editors used non-breaking space or blank space as a street name just to distinguish between newly pawed roads and already finished unnamed roads in unnamed streets layer.
How to fix: use correct street name or check "no street" checkbox instead
Severity: warning
Countries: any country
-
porubcan
- Waze Global Champs

-
- Posts: 6408
- Joined: Mon Jan 02, 2012 9:13 am
- Location: Slovakia
- Has thanked: 800 times
- Been thanked: 1906 times
by promaha » Mon May 25, 2015 8:42 pm
Thank you!!!
My work is more efficient thanks to your app!
-
promaha
-
- Posts: 4
- Joined: Fri May 08, 2015 3:30 pm
- Has thanked: 3 times
- Been thanked: 0 time
by pumrum » Thu Jan 30, 2014 7:01 am
Message #44 is for a segment that doesn't have any output to a drivable road, but the summary says "No connectivity from drivable road". It should say "No connectivity to a drivable road"
Description:
#44 The drivable segment has no single outward turn enabled. Enable at least one outward turn from the segment
-
pumrum
-
- Posts: 669
- Joined: Mon Dec 09, 2013 3:02 am
- Has thanked: 92 times
- Been thanked: 301 times
by pumrum » Fri Jan 31, 2014 1:12 am
berestovskyy wrote:I meant no connectivity from this drivable road. I'm not a native speaker, so if you have a spare time I would appreciate if you looked through the Settings->About->Available checks for any other mistakes.
Absolutely, glad to help! I have downloaded the list and will go through it tomorrow.
-
pumrum
-
- Posts: 669
- Joined: Mon Dec 09, 2013 3:02 am
- Has thanked: 92 times
- Been thanked: 301 times
by pumrum » Sun Feb 02, 2014 6:57 am
I didn't see anything specific in the road naming guide for the US, but the following are being highlighted by #94 "lowercase street name (except country-specific words)":
el
la
de
These show up in some states (CA/AZ/NM) and elsewhere as lowercase on street signs. Should they remain lowercase in WME?
if not, let's add them to the exception list for US
if so, I will correct these in WME to be UPPER whenever I find them
-
pumrum
-
- Posts: 669
- Joined: Mon Dec 09, 2013 3:02 am
- Has thanked: 92 times
- Been thanked: 301 times
by pumrum » Sun Feb 02, 2014 3:58 pm
I stand corrected. I was doing edits in the SJC area and I could
swear I had seen road signs that matched the lower case name in WME, but I have been unable to locate. I was likely mistaken. For now it seems like lower case names would be the exception, and 'la' and 'el' should not be added to the exception list. I think the summary from the other forum thread was "match the case of the road sign"
thanks!
-
pumrum
-
- Posts: 669
- Joined: Mon Dec 09, 2013 3:02 am
- Has thanked: 92 times
- Been thanked: 301 times
by pumrum » Mon Feb 17, 2014 9:11 pm
Feature Suggestion:
Highlight railroad segments that form junctions with non-railroad segments.According to the Wiki:
DO NOT create a junction between the driven road and the railroad.
Source:
https://www.waze.com/wiki/Railroad#RailroadI see this frequently in the northeast US where there are a lot of regional railroads that go through towns and for one reason or another someone formed a junction between a railroad and a driveable segment.
-
pumrum
-
- Posts: 669
- Joined: Mon Dec 09, 2013 3:02 am
- Has thanked: 92 times
- Been thanked: 301 times
by pumrum » Mon Feb 17, 2014 10:21 pm
dbraughlr wrote:A Railroad segment must not be at a junction with another type.
A Runway/taxiway segment must not be at a junction with another type.
There must not be a junction with any drivable type and any non-drivable type.
A ramp must be connected at both ends and the junction at one end must have a freeway/highway/ramp segment.
Good point, perhaps instead my feature request should be:
Highlight Non-drivable segments that form junctions with segments of a different type.This way if a railroad formed a junction with anything but a railroad, it would get highlighted. If a runway formed an intersection with a walking path, it would get highlighted. etc etc
-
pumrum
-
- Posts: 669
- Joined: Mon Dec 09, 2013 3:02 am
- Has thanked: 92 times
- Been thanked: 301 times
by pumrum » Mon Mar 17, 2014 10:44 pm
[post edited to reflect actual update]
I saw in one of the recent updates:
- UPD 'Non-drivable connected to drivable': excluded short dead-end segments and segments with HNs
It seems that it's ignoring non-drivable segments all together. I have found intersections between streets and runways, railroads, and walking trails - none are being flagged by WMV 0.8.3
Example:
https://www.waze.com/editor/?zoom=7&lat ... 78&env=usa
Last edited by
pumrum on Mon Mar 17, 2014 11:01 pm, edited 1 time in total.
-
pumrum
-
- Posts: 669
- Joined: Mon Dec 09, 2013 3:02 am
- Has thanked: 92 times
- Been thanked: 301 times
Return to Addons, Extensions, and Scripts
Who is online
Users browsing this forum: Google Feedfetcher