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
Originally posted by Charlie-Henry July 11, 2024
Looks like the only place to supply sidewalk closures in in the lanesdetails. We are wondering if it is possible to report a sidewalk closure without knowing the order of lanes (which breaks business rule 2). Making the cross section of every road (including sidewalks/bike lanes/parking) a requirement is a pretty impractical for a City DOT. vehicle_impact is also pretty car-centric and doesn't help this use case.
Proposed solution
Enhance the Vehicle Impact Enumerated Type to support indicating that a sidewalk is closed so that feed producers who want to provide sidewalk impact do not have to have lane-level information.
The text was updated successfully, but these errors were encountered:
j-d-b
changed the title
Allow for Closed Sidewalks without Lane order
Allow indicating a sidewalk closure without providing lane-level information
Jul 12, 2024
Our specific use case comes from our permitting system where we are able to track work zones at the street-segment level. It tracks closures to the general purpose lanes, parking lanes, and sidewalks. Any combination of those can be closed.
So, it's possible we could have one general purpose lane closed + a sidewalk. We do not have the actual lane cross-section to provide that level of detail needed in business rule 2. I'm not sure if adding a "closed sidewalk" to vehicle_impact would solve this, because we may want to show some_lanes_closed at the same time? Unfortunately the sidewalk and roadway share the same street segment & geometry.
Discussed in #372
Originally posted by Charlie-Henry July 11, 2024
Looks like the only place to supply sidewalk closures in in the
lanes
details. We are wondering if it is possible to report a sidewalk closure without knowing the order of lanes (which breaks business rule 2). Making the cross section of every road (including sidewalks/bike lanes/parking) a requirement is a pretty impractical for a City DOT. vehicle_impact is also pretty car-centric and doesn't help this use case.Proposed solution
Enhance the Vehicle Impact Enumerated Type to support indicating that a sidewalk is closed so that feed producers who want to provide sidewalk impact do not have to have lane-level information.
The text was updated successfully, but these errors were encountered: