Well I think we have much less active L4+ editors here than you have

I put the the link to data location on this https://docs.google.com/spreadsheets/d/ ... edit#gid=0 spreadsheet as asked in original thread, checked version history, I put it there 21.4

jm6087 wrote:

BatmanandRobbins wrote:I am following; trying to get the railroad crossing disabled!
Seriously what is the purpose of this notification? There are already signs on the road and railroad tracks on the display. Having the big popup is annoying and useless!

I hope you have been able to disable the alert.

You may find it useless and don't feel you need an alert to tell you about a railroad crossing, but every year many people either ignore or don't see railroad crossings and get hit by trains. There are also many cases where people turn on to a railroad track by mistake because it is dark. The alert is designed to alert drivers to these dangers. This is also why the alert is there, it is trying to save lives. And I believe that getting hit by a train is probably more dangerous than the alert designed to prevent it.

Hopefully this "useless" feature will save some lives which makes it worth while.

My childhood home is 50 meters from railroad crossing so I've lived very near one for most of my life. And seen some accidents there too, happened both to locals and non-locals. Some with the worst result...

Many think that locals should know better but no, when something is ordinary you very easily slip into "there has never been a train at this hour" mentality and some day might end up hit by one. So I'm totally supporting this, if it prevents even one death/serious injury it has made desired impact.

I personally want to use it since it "awakens" me to be more cautious when approaching one, even if it's the one I know very, very well. And anyway, if it irritates someone so much the alert for those can be easily turned off from app itself.

How is an alert useful unless you are not watching for signals or signs, or blind? The app sorely needs a railroad crossing function, but it would be used for avoiding railroad crossings, not alerting the driver about them. The alerts are unnecessary clutter. The lack of a feature to avoid railroad almost made me miss my plane. A 5 mile long train stopped in the middle of Fort Lauderdale making it impossible to cross the tracks to reach the airport. Efforts to reroute were fruitless, as it kept taking me to other railroad crossings instead of an underpass or overpass. I wasted an hour driving in circles with no result. Does Waze developer seriously not understand why the driver NEEDS a railroad avoidance feature for? I don’t need an app that dings and talks continuously but offers no rerouting capability to avoid a stopped
train!
 

It appears that RRCs are again disabled for L4 editors. It shows in the Roads menu, but is greyed out.

It seems good to leave them one on top of the other, but the warning point would be different not on the railway.

When it will be visible in app?
You anonsed it in public forum, editors start use it but users will see cameras and will send UReports.
As I understand, users US see more 100.000 dummy cameras

Some railroad crossings have been added near my house, but they are not road crossings (pedestrian only). Yet, they show up on the map during drives. Who can help me remove them? (they are blanked out when I try to remove them in the editor)

turbomkt wrote:

sebgoulettva wrote:Some railroad crossings have been added near my house, but they are not road crossings (pedestrian only). Yet, they show up on the map during drives. Who can help me remove them? (they are blanked out when I try to remove them in the editor)

Is this in Canada?

Yes. Boucherville, QC

How do I turn this ANNOYING feature off???

Take a page from your driving style and cool your jets before posting online, too, maybe.

This feature will not be opt-in because it is primarily intended as a safety feature. You can whine all you want about it, that will not change.

The feature reactivating yourself on your phone, however, is a bug. App bugs should be posted in the official feedback thread for the appropriate version in the Waze App forum.