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
The latter way is missing the lanes attribute (presumably this slips through because it does not affect rendering style).
Such missing attributes are replaced by the default values and can create significant bottlenecks which invalidate a simulation.
It would be useful to identify ways that form a sequence (by topology and common street name?) and to infer the values of missing attributes from present attributes of surrounding ways.
As alternative, one could annotate objects so that the end use can easier find objects with guessed attributes and correct them manually (#16094)
The text was updated successfully, but these errors were encountered:
In some networks, roads that are split into multiple ways lack important attributes on some of these ways.
https://www.openstreetmap.org/way/1101061677 vs
https://www.openstreetmap.org/way/76402292
The latter way is missing the lanes attribute (presumably this slips through because it does not affect rendering style).
Such missing attributes are replaced by the default values and can create significant bottlenecks which invalidate a simulation.
It would be useful to identify ways that form a sequence (by topology and common street name?) and to infer the values of missing attributes from present attributes of surrounding ways.
As alternative, one could annotate objects so that the end use can easier find objects with guessed attributes and correct them manually (#16094)
The text was updated successfully, but these errors were encountered: