I'll hope to get some screenshots up soon, this can be really helpful working with and diagnosing BDP.
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
I tried using the expression editor to modify an existing expression with this text in the editor:
It then pasted this as the expression for selection:
Notice the end of the expression is not what I was asking for.
Then I tried to highlight using it and got this error:
----
Rsel v1.14
Rsel Highlights v0.6.9
Rsel editor v0.2.7
EDIT: Further debug reveals I had the speed limit field in the Rsel editor panel filled with 22, though I would expect what I type in the expression editor to override that. When I cleared the Rsel SL field, the expression editor and highlighter worked properly without any warnings issued.
Code: Select all
(Road Type = "Freeway" OR Road Type = "Major Highway" OR Road Type = mH OR Road Type = PS OR Road Type = St) AND (Has NOT speed limit OR Has unverified speed limit)
Code: Select all
(Road Type = "Freeway" OR Road Type = "Major Highway" OR Road Type = "Minor Highway" OR Road Type = "Primary Street" OR Road Type = "Street") AND (! Has speed limit 22 mph in any direction OR Has unverified speed limit 22 mph)
Then I tried to highlight using it and got this error:
So I'm reporting itRSel Highlights was unable to parse the saved expression text to exactly match the original expression.
Your original selection will be used for highlighting, but it cannot be edited – only deleted. Please make a bug report here.
----
Rsel v1.14
Rsel Highlights v0.6.9
Rsel editor v0.2.7
EDIT: Further debug reveals I had the speed limit field in the Rsel editor panel filled with 22, though I would expect what I type in the expression editor to override that. When I cleared the Rsel SL field, the expression editor and highlighter worked properly without any warnings issued.
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Congrats and awesome, it's a big help using the whole package (Rsel, Rsel Highlights, Rsel Expression Editor, and Context menu) when working with SLs.
P.S. some of those pics and rules look a bit familiar
Sent from Android using Tapatalk
P.S. some of those pics and rules look a bit familiar
Sent from Android using Tapatalk
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
What version of Rsel are you using?voludu2 wrote:I started from a saved road selector expression:I hit the highlights button and got an error message:On Screen AND Road Type = "Street" AND (Has unverified speed limit OR Has NOT speed limit OR Has speed limit in only one direction)I had the same difficulty withRSel Highlights was unable to parse the saved expression text to exactly match the original expression.
Your original selection will be used for highlighting, but it cannot be edited – only deleted. Please make a bug report here.On Screen AND (! (Has speed limit in both directions) OR Has unverified speed limit)
Sent from Android using Tapatalk
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
I'm sorry I meant to ask what version of the highlighting where are you using? It has to be at least 0.7.8.x and then of course reload WME after the upgradevoludu2 wrote:I'm using road selector 1.14
Sent from Android using Tapatalk
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
You can even place the entire PL as the string and it will highlight any of those included segments.
ID = "www.waze.com/editor.....&segments=74958 ... 55,6493939"
Sent from Android using Tapatalk
ID = "www.waze.com/editor.....&segments=74958 ... 55,6493939"
Sent from Android using Tapatalk
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
There is some problem with non ASCII characters in names.
I think you will soon completely replace my script but you did a good job.
I think you will soon completely replace my script but you did a good job.
I did nothing. It just works because the strings are in Unicode.TheLastTaterTot wrote:How did you get it to transfer correctly for RSel?
I don't know if it helps you but I use the RegExp object as the parameter of the String search() method an it works fine.TheLastTaterTot wrote:ah okay. I think maybe the regex testing and searching might be affecting it. I'll look into this matter -- unless you already have an answer?
I guess, you question is in wrong topic .jasonh300 wrote:Is this a bug or is there something I should do different in the expression?
I'm using this expression:
(State = "Louisiana" AND Road Type = "Major Highway" AND Has NOT speed limit) OR (State = "Louisiana" AND Road Type = "Major Highway" AND Has unverified speed limit)
And it highlights these segments:
https://www.waze.com/editor/?env=usa&lo ... ,502449400
The speed limit is set, however, this was split recently, and seems to have unverified speed limits on the opposite direction, which should be inconsequential. I cleared it from one of the segments by making it two-way and removing the speed limit and then switching it back to one-way. But this is the only place in the entire state that I've found this problem. I assume it's because it's the only thing that's been split since the speed limit import and didn't have the speed limits verified before it was split.
Is there something I can do differently in my expression that will prevent this from happening? WMECH does not detect this as not having a verified speed limit.
Thanks!
The selection is made by WME Road Selector script but I will reply here.
The condition Has unverified speed limit checks both directions and if one of them has an unverified speed limit the condition is true. It is by design.
You could exclude the segments with the hidden speed with the ! Has speed limit in hidden direction condition. But it is probably not what you want.
I could add some condition like "visible unverified" but I think this is very exceptional case because when you once verify the speed it cannot be set as unverified therefore it is faster to correct these few segments than to add a condition which nobody else will need.
Re: [Script] WME Road Selector Highlights