[Script] WME Falcon Eye

Map Editors Community Addons, Extensions, And Scripts
1

I am writing a script, I am checking it twice, it’s gonna find out if doglegs are naughty or nice. Falcon Eye is coming to town

Based on Gil’s guide regarding mapping doglegs for Falcon and further information from the Devs, I made a script that checks that automatically (for performance reasons only on one-way streets, but Waze said that that applies also to two-way roads, fyi).

You can download the script here (Tampermonkey extension is required): https://github.com/bedo2991/wme-falcon-eye/releases/latest/download/wme-falcon-eye.user.js

The script should be rather self-explainatory. If you need more infos, you can find them here.

Nice dogleg:

image
image1437×839 882 KB

Naughty dogleg (for different reasons):

image
image1276×724 636 KB

2

Thanks, Francesco, for this script. Looking forward to using it on all our one way roads in Houston.

3

Will have to see how well this works. Thanks

4

Great work! I have a suggestion: could there be an option to only highlight the “naughty” doglegs? Most of the time I don’t need to see the green highlights.

5

There might be, somewhen, but in that way there would be no way to know if these segments were even recognized at all as dogleg candidates or simply skipped.

6

Version 1.2.2 is out!

  • Improved performance: the WME should not freeze when a lot of segments are checked at once.
  • New feature: in the settings, you can disable displaying the approved doglegs in green. @Harmonious4 request
  • Bug fixes: the settings are now stored correctly for your next session.
8

For everyone interested about the topic, Waze released an advanced course about Falcon here: New Resource for the Community: Advanced Segment Editing Course 🚙

9

Is there anyone in a left hand drive country (i.e. exits on the left) successfully using this script with highlights showing?

10

Works alright for me in Ireland:

image
image344×564 111 KB

11

Thank you :slight_smile:
I’ll have to start looking for the conflict :scream:

12

Excellent script, thank you so much for sharing!

13

Great work Francesco!!!

14

It’s a very good script. Is there a way that an AGCs will be filtered out? The Falcon needs the special geometry only when the exit ramp continues more or less in parallel to the highway, and not when in diverges to a different direction.

15

An excellent job adapting to this new reality. The editor community is grateful.

I would like to ask a question: is there any possibility of expanding this to highway access without using ramps? I tested it here and it only works with ramps. If that’s not possible, no worries, it’s already helping in most cases. But we’ll always find a minority of cases that don’t follow the rules lol

image
image362×268 63 KB

16

you can temporarily change them to ramps even without saving and then it might work (at least the lower one, the upper one probably not as you also have to change the primary to a highway type).

17

Permalink?

But I don’t think so, there will always be false positives.

18

Few examples:
An AGC
Sharp exit
Sharp exit

19

For 2 and 3, I would have mapped them as doglegs (based on the aerials).

In general, now everything is checked what “looks like” a highway exit, based on being one way and based on the road type.

The only think that it would be thinkable is being able to define how the highway road names should look like and to check them while validating.

20

As Rickendude explained in one of the calls, Falcon needs “help” only when the exit road continues more or less in parallel to the highway. The “help” is by editing along the criteria he gave us. Whenever the exit road diverges into a different direction, there is no need to follow the guidelines. At least this what I understood. Of course the prioblem is how to differentiate between the exit types. Maybe someone has an good idea for it.