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

Allow specifying lane width via an optional width property on the Lane object #156

Closed
j-d-b opened this issue Jan 27, 2021 · 2 comments
Closed
Labels
Needs discussion This issue needs clarification/additional discussion or is inactive

Comments

@j-d-b
Copy link
Collaborator

j-d-b commented Jan 27, 2021

I'm not sure if producers have this data or if there is value, but allowing specifying the width of a lane has been thrown around in several subgroup discussions throughout the past year, so I wanted to ensure it was recorded on GitHub for discussion.

@j-d-b j-d-b added Needs discussion This issue needs clarification/additional discussion or is inactive Data-content labels Jan 27, 2021
@vchandranNTAM
Copy link

While Lane width seems like a valuable add, characteristics of the lane belongs in the Asset layer. Tying this to the WorkZone events may muddy the waters.

The WZDx discussion should focus on on what work is going on which roadway and which segment of it, where are the closures and whats going on now.

Having said that WZDx efforts most definitely would fall into an extended TAMS strategy for DOTs and local agencies that own and manage transportation assets.

@j-d-b
Copy link
Collaborator Author

j-d-b commented Jun 24, 2021

I agree with @vchandranNTAM and based on co-chairs discussion, all contributors are in agreement that properties like width, which apply to the base details of the area the road event occurs on rather than the changes due to the work zone, should not be covered by WZDx.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs discussion This issue needs clarification/additional discussion or is inactive
Projects
None yet
Development

No branches or pull requests

2 participants