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 am starting to think about whether or not we should have a specific set of optional specifications for intersection points and their relationships to the "segments" we are describing in the specification. What attributes would be useful here? Would we move the crosswalks to this schema? How do we handle multiple legs?
I started an effort a while ago to map traffic signals and describe movements through an intersection in a format referencing OpenStreetMap objects. Some of those ideas could be relevant. See the doc and the specification
I am starting to think about whether or not we should have a specific set of optional specifications for intersection points and their relationships to the "segments" we are describing in the specification. What attributes would be useful here? Would we move the crosswalks to this schema? How do we handle multiple legs?
@marsxul / @migurski / @louh / @emilyeros
The text was updated successfully, but these errors were encountered: