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

Representing Exception User Classes #124

Open
LaurentG-AMD opened this issue Oct 31, 2023 · 2 comments · May be fixed by #136
Open

Representing Exception User Classes #124

LaurentG-AMD opened this issue Oct 31, 2023 · 2 comments · May be fixed by #136
Milestone

Comments

@LaurentG-AMD
Copy link

Is your feature request related to a problem? Please describe.

Similar to issue #117, there is currently no way to define and communicate a policy that excludes User Classes rater than include them, based on our reading of the User Classes spec.

For instance, creating a no-stopping zone except for buses would require overlaping both a no-stopping zone for every type of vehicles and superimposing a stopping for User Classes='bus' with a higher priority, which departs from the way the regulations are written in Montreal and both makes it more complicated to maintain and to correctly comprehend for local users.

Describe the solution you'd like

We would like

  • user_classes_except = true to indicate that a rule does not apply during to the listed user classes

Example : A no stop zone for a bus stop:

{
    'activity': 'no-stopping',
    'user_classes': ['bus'],
    'user_classes_except': true
}

Is this a breaking change

No, not breaking

Impacted Spec

Curbs

Describe alternatives you've considered

As described above it is possible to circumvent the missing exception clause but it requires multiplying the number of policy objects and may make the model harder to maintain and/or comprehend.

Additional context

None

@schnuerle schnuerle added this to the 1.1 milestone Dec 12, 2023
@schnuerle
Copy link
Member

Is this close enough to Issue #117 to put this description as a comment there and close this issue? Or do you think this is a different idea?

@LaurentG-AMD
Copy link
Author

It's definetly the same idea applied to another section of the spec. They should be treated at the same time.

@mplsmitch mplsmitch linked a pull request Aug 14, 2024 that will close this issue
schnuerle added a commit to mplsmitch/curb-data-specification that referenced this issue Nov 19, 2024
@schnuerle schnuerle linked a pull request Nov 19, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants