Ordering of location group and location group stop data #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
dev
before they can be merged tomaster
)Description
The GTFS-lib for efficiency reads one row from a CSV file and writes that directly to the matching table. Unfortunately this prevents parsing/reordering of the data to suit DT. This update (besides creating a new util class for CSV reading) intercepts requests to read location groups or location group stops and reorders the data prior to it being read into the database.
This ultimately allows the database row id to represent the same location group id in location groups and location group stops. Yes, a lot of effort just to order some data, but hey.