You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I try to use the "Tag this crossing as 'lines'" suggestion to fix a way with two crossings on it then it does not make the change that I asked it to make. (See steps to reproduce for details)
Screenshots
Before fixing the intersection:
After clicking on "Tag this crossing as 'lines'"
Version
2.2.3
What browser are you seeing the problem on? What version are you running?
Crossing line and point tags conflict
Tag this crossing as 'marked'
Tag this crossing as 'lines'
Remove all crossing tags
Ignore this issue
I then click on the "Tag this crossing as 'lines'" and instead of the way being changed to crossing:marking=lines it changes the nodes to crossing:marking=yes.
If I remove one of the crossing nodes (and the way that it is on) then it behaves correctly so I think this is specific to having two crossing nodes on the crossing way.
The browser URL at the time you encountered the bug
Whoa good catch @atiannicelli - this was a caused by an unfortunate typo that only occured if that part of code was visited more than once. Easy fix though, I'll get a patch out soon.
Description
If I try to use the "Tag this crossing as 'lines'" suggestion to fix a way with two crossings on it then it does not make the change that I asked it to make. (See steps to reproduce for details)
Screenshots
Before fixing the intersection:
![Screenshot 2024-01-11 at 10 03 01 AM](https://private-user-images.githubusercontent.com/5851115/295956855-c7c5a3f9-ae36-48cc-b815-b10460fa6653.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjExOTA2ODYsIm5iZiI6MTcyMTE5MDM4NiwicGF0aCI6Ii81ODUxMTE1LzI5NTk1Njg1NS1jN2M1YTNmOS1hZTM2LTQ4Y2MtYjgxNS1iMTA0NjBmYTY2NTMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcxNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MTdUMDQyNjI2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MDMxOTUyNGQ4YWZmYTNiMjc3MTE5MmNlN2I0NGYwNTgzMDg3N2MyODJhOGVmMGMzYzZhY2I2N2VkZmNmM2Q3NCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.ZfWJ_XvFSb1m6ehEXA21R0fGEEd5oOX2JbrDbygj9lI)
After clicking on "Tag this crossing as 'lines'"
![Screenshot 2024-01-11 at 10 03 25 AM](https://private-user-images.githubusercontent.com/5851115/295956982-78cf723f-bd71-470b-ae60-49ac9b1a73ac.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjExOTA2ODYsIm5iZiI6MTcyMTE5MDM4NiwicGF0aCI6Ii81ODUxMTE1LzI5NTk1Njk4Mi03OGNmNzIzZi1iZDcxLTQ3MGItYWU2MC00OWFjOWIxYTczYWMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcxNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MTdUMDQyNjI2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9OWNmOGJhMDE1YjBmYWVhNjAxYTUzMzAyZDU2NTliYjRkOTc1ZWUxZjVlNDg4MjA4NGZjZTc5ZTY5Nzk5NjhkYiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.Cv3P45sruZz_jp5wodmhgkgvk5lvUVNw_nMfHk3xy3k)
Version
2.2.3
What browser are you seeing the problem on? What version are you running?
Chrome v120.0
The OS you're using
mac
Steps to reproduce
I have a way with the following tags
and TWO nodes on that way that have the following tags:
When I click on the way it gives me this warning:
I then click on the "Tag this crossing as 'lines'" and instead of the way being changed to crossing:marking=lines it changes the nodes to crossing:marking=yes.
If I remove one of the crossing nodes (and the way that it is on) then it behaves correctly so I think this is specific to having two crossing nodes on the crossing way.
The browser URL at the time you encountered the bug
https://rapideditor.org/edit#background=Bing&datasets=fbRoads,msBuildings&disable_features=boundaries&id=w706113826&map=20.00/42.34726/-88.13017
The auto-detected useragent string for your browser (leave blank if you're manually filling this form out)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
The text was updated successfully, but these errors were encountered: