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

Technical Support for is_architectural_change #96

Closed
Polly-Okunieff opened this issue Jun 2, 2020 · 2 comments
Closed

Technical Support for is_architectural_change #96

Polly-Okunieff opened this issue Jun 2, 2020 · 2 comments
Labels
Needs discussion This issue needs clarification/additional discussion or is inactive Technical Assistance This issue/PR is related to the Technical Assistance Subgroup

Comments

@Polly-Okunieff
Copy link

In the current version, a feed issuer can submit more than one work type. So one work type may designate an architecture change to a work type, while the other may not. This may be true, but there will be confusion. Also, is maintenance ever an architectural change? by definition, it is just fixing or preserving existing infrastructure. This may require guidance and best practices discussion.

@j-d-b
Copy link
Collaborator

j-d-b commented Jun 2, 2020

This likely ties into #78. That is, a change in work type could be one of the fields that necessitates breaking the work area into multiple road events. If this is the case we'd allow just one type_of_work and is_architectural_change per event. This may be the clearest method, if there is never a case where two distinct types of work are occurring at the same time on the same piece of roadway.

@j-d-b j-d-b changed the title Technical Support for is_architecture_change Technical Support for is_architectural_change Jun 19, 2020
@mark-mockett mark-mockett added the Technical Assistance This issue/PR is related to the Technical Assistance Subgroup label Jul 23, 2021
@j-d-b j-d-b added Needs discussion This issue needs clarification/additional discussion or is inactive and removed Provide feedback labels Jan 20, 2022
@j-d-b
Copy link
Collaborator

j-d-b commented Mar 22, 2022

Closing due to stale discussion and lack of recent interest.

@j-d-b j-d-b closed this as completed Mar 22, 2022
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 Technical Assistance This issue/PR is related to the Technical Assistance Subgroup
Projects
None yet
Development

No branches or pull requests

3 participants