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
I have a large amount of nodes where the question “Was ist die Durchfahrtshöhe hier?“ is repeated endless (personal raw translation: “What is the max height for driving through here?“)
I counterchecked that nodes in Vespucci. They already have attributes like:
highway=service
surface=wood
tunnel=building_passage maxheight=4
maxheight:sign = no
In my opinion that data is already fine, correct and complete. SC shouldn't ask here at all.
If I delete both of the maxheight related attributes, I am asked only one question and it's done. Looks like combining both of them triggers the issue.
This is the case since the latest release, and I saw it was worked on some (max_)height-related features.
How to Reproduce
See node 340404170 (August-Kirch-Str. 17, Hamburg, Germany) as an example, but basically my “hood“ is plastered with a lot examples. See attached screenshot showing 53.567066 , 9.905047
Expected Behavior
I'd expect to not being asked that at all, because data looks already fine.
Versions affected
SC v.54.1
The text was updated successfully, but these errors were encountered:
joergRossdeutscher
changed the title
Question for max_height is asked over and over again
Question for maxheight is asked over and over again
Oct 4, 2023
I have a large amount of nodes where the question “Was ist die Durchfahrtshöhe hier?“ is repeated endless (personal raw translation: “What is the max height for driving through here?“)
I counterchecked that nodes in Vespucci. They already have attributes like:
highway=service
surface=wood
tunnel=building_passage
maxheight=4
maxheight:sign = no
In my opinion that data is already fine, correct and complete. SC shouldn't ask here at all.
If I delete both of the maxheight related attributes, I am asked only one question and it's done. Looks like combining both of them triggers the issue.
This is the case since the latest release, and I saw it was worked on some (max_)height-related features.
How to Reproduce
See node 340404170 (August-Kirch-Str. 17, Hamburg, Germany) as an example, but basically my “hood“ is plastered with a lot examples. See attached screenshot showing 53.567066 , 9.905047
Expected Behavior
I'd expect to not being asked that at all, because data looks already fine.
Versions affected
SC v.54.1
The text was updated successfully, but these errors were encountered: