Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: describe Curb activities w/ table #69

Draft
wants to merge 3 commits into
base: release-1.0.0
Choose a base branch
from

Conversation

zanebclark
Copy link
Collaborator

Note the question marks emphasizing areas of debatable coverage

@zanebclark zanebclark requested a review from a team as a code owner January 24, 2022 18:55
Comment on lines +378 to +379
| no stopping | not a typical travel lane | ❌ | ❌ | ❌ | ❌ | ✅ |
| travel | represents curbside lanes intended for moving vehicles, like bus lanes, bike lanes, and rush-hour-only travel lanes | ❌ | ❌ | ❌ | ❌ | ✅ |
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@schnuerle , this does a good job of representing my problem w/ no stopping vs travel. In this model, they represent the same thing.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love the table, nice work! For the "?" you could use the Emoji White Question Mark or even Wavy Dash to show it's not clearly defined.

In my mind, these activities that are used for defining rules for curb policy, no stopping and travel are different, beyond what the table currently shows, maybe more about physical build. An example "travel" area by the curb could be a flush curb to the travel lane of a road, while a no stopping rule could apply to a curb cut in an area that is never a normal travel lane. I'm not sure of the policy differences and needs between these rule definitions of 'travel' vs 'no stopping' - maybe you just want to be clear that this zone at this time of day is a travel lane and be clear about that, vs just a no stopping area?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've replaced the question mark w/ the emoji. I think I got the right wavy one. Let me know if I'm off

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

while a no stopping rule could apply to a curb cut in an area that is never a normal travel lane.

If you can't stop there and you can't travel there, I'm not sure what you could do there. I can think of one example of such a situation, but it suggests we ought to have a no travel activity instead of a travel one. It also bends the definition of a curb:

A promenade or large sidewalk-like area could have a no travel activity defined for all non-municipal car-like classes and a no parking policy defined for scooters.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems that temporary uses that block use of the curb, such parklets for outdoor dining, or a construction lay down area could represent an opportunity to use the proposed no travel activity, as only using no stopping could communicate that the curb lane could still be utilized in some fashion as a travel lane.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, local jurisdictions will need to do some translation work to fit local regulatory practices to CDS. As an example, in SF we use no stopping on signage to designate curb space that is temporarily permitted for moving trucks to stop and conduct loading activity.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@schnuerle and @kenyaw , check out the #64 discussion for the continuation on this

@schnuerle schnuerle added Curbs API documentation Improvements or additions to documentation labels Jan 24, 2022
@schnuerle schnuerle changed the base branch from feature-release-work-1 to release-1.0.0 January 25, 2022 15:03
@schnuerle schnuerle added this to the 1.0.0 milestone Feb 8, 2022
@schnuerle schnuerle modified the milestones: 1.0.0, Future Feb 21, 2022
@schnuerle
Copy link
Member

Moving this to a future release to see what activity changes might be needed and how a table can best help clarify.

@schnuerle schnuerle marked this pull request as draft February 21, 2022 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Curbs API documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants