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 tryed to split a road to include a bridge but could not do it because ID requires to have all elements of the road (trunk) downloaded. How all elements of a road relation could be downloaded if they cover dozens of kilometers?
This have NOT SENSE AT ALL. Who invented this Limitation?
Screenshot(s) or anything else?
Refer to the links above
Which deployed environments do you see the issue in?
No response
What version numbers does this issue effect?
2.30.2
Which browsers are you seeing this problem on?
Microsoft Edge
The text was updated successfully, but these errors were encountered:
Draw a waterway, e.g. ditch, underneath the point on the road you want to split.
A warning about waterway/road crossing appears. Select the solution to create a bridge on the highway.
Drag one end of the bridge over the other, eliminating the bridge.
Now, delete that ditch...
Yeah, that's borderline crazy. Note that iD can create a bridge for itself without downloading the whole relation. So why it's forcing you to do a mere split? Splitting is a simple operation which can be easily performed without downloading the whole relation, just the adjacent ways.
URL
https://www.openstreetmap.org/edit?node=12187466479#map=19/-17.606368/-65.670977
How to reproduce the issue?
I tryed to split a road to include a bridge but could not do it because ID requires to have all elements of the road (trunk) downloaded. How all elements of a road relation could be downloaded if they cover dozens of kilometers?
This have NOT SENSE AT ALL. Who invented this Limitation?
Screenshot(s) or anything else?
Refer to the links above
Which deployed environments do you see the issue in?
No response
What version numbers does this issue effect?
2.30.2
Which browsers are you seeing this problem on?
Microsoft Edge
The text was updated successfully, but these errors were encountered: