-
Notifications
You must be signed in to change notification settings - Fork 101
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: Add locations.geojson schema #1750
Labels
enhancement
New feature request or improvement on an existing feature
flex
Rules and rule changes related to GTFS-Flex.
Milestone
Comments
emmambd
added
enhancement
New feature request or improvement on an existing feature
status: Needs triage
Applied to all new issues
labels
May 8, 2024
emmambd
changed the title
Add locations.geojson schema
Flex: Add locations.geojson schema
May 8, 2024
emmambd
added
flex
Rules and rule changes related to GTFS-Flex.
status: Blocked
Can't work on it currently because of an external factor.
and removed
status: Needs triage
Applied to all new issues
labels
May 9, 2024
emmambd
modified the milestones:
Flex: modifying pre-existing rules,
6.0 Validator Release
May 30, 2024
Continues #1758
|
emmambd
removed
the
status: Blocked
Can't work on it currently because of an external factor.
label
Jul 16, 2024
5 tasks
5 tasks
Tasks:
|
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature request or improvement on an existing feature
flex
Rules and rule changes related to GTFS-Flex.
Describe the problem
We want to be able to support Flex as a part of #1721, we need to add a schema for the new file locations.geojson.
Proposed solution
New schema
Modify and test duplicate_key. Test with
duplicate-area-548-locations-geojson.zip. Duplicated area_548 in https://data.trilliumtransit.com/gtfs/islandtransit-wa-us/islandtransit-wa-us--flex-v2-TEST.zip to test this.
Modify and test foreign_key_violation when location_id is defined in stop_times.txt but not in locations.geojson. Test with
foreign_key_violation_area_1137.zip to verify.
Check if there are performance issues locally with the test feeds in the proposal document, to see if there are persistent issues with parsing failing for Flex data based on what was found in foreign_key_violation doesn't catch a missing trip_id #1752
Special considerations given this is a geojson file when we only supported txt files before
Alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: