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

Flex: forbidden_pickup_type #1822

Open
emmambd opened this issue Sep 9, 2024 · 1 comment · May be fixed by #1936
Open

Flex: forbidden_pickup_type #1822

emmambd opened this issue Sep 9, 2024 · 1 comment · May be fixed by #1936
Assignees
Labels
flex Rules and rule changes related to GTFS-Flex. new rule New rule to be added status: Needs triage Applied to all new issues

Comments

@emmambd
Copy link
Contributor

emmambd commented Sep 9, 2024

Describe the problem

See below

Describe the new validation rule

forbidden_pickup_type as defined in the table here

Sample GTFS datasets

No response

Severity

Error

Additional context

No response

@emmambd emmambd added status: Needs triage Applied to all new issues new rule New rule to be added labels Sep 9, 2024
@emmambd emmambd added this to the 7.0 Validator Release milestone Sep 9, 2024
@emmambd emmambd added the flex Rules and rule changes related to GTFS-Flex. label Dec 2, 2024
@cka-y cka-y assigned cka-y and unassigned cka-y Dec 24, 2024
@qcdyx qcdyx self-assigned this Jan 6, 2025
@qcdyx
Copy link
Contributor

qcdyx commented Jan 6, 2025

Hello @emmambd could you indicate the description of ForbiddenPickupTypeNotice? I put "Forbidden pickup type 0 or 3 when pickup/drop-off window is defined." for now.

@qcdyx qcdyx linked a pull request Jan 7, 2025 that will close this issue
5 tasks
@qcdyx qcdyx linked a pull request Jan 7, 2025 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flex Rules and rule changes related to GTFS-Flex. new rule New rule to be added status: Needs triage Applied to all new issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants