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.

Sign up for GitHub

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

Jump to bottom

Moving transit model into a separate module #6431

Open

8 tasks

leonardehrenfried opened this issue Feb 5, 2025 · 0 comments

Open

8 tasks

Moving transit model into a separate module #6431

leonardehrenfried opened this issue Feb 5, 2025 · 0 comments

Labels

Member

leonardehrenfried commented Feb 5, 2025 •

edited

Loading

Before we can move transit model into its own module, we need to resolve the following issues:

Bad

Timetable depends on GTFS-RT
Transit group priority depends on the RAPTOR API
TripPattern depends on RoutingTripPattern which depends on the RAPTOR API
FrequencyEntry depends on Frequency which is a copy from OBA

Undecided

Lots of model classes depend on framework code: text, i18n, geometry...

Acceptable

transit model depends on JTS
transit model depends on org.geojson for which there is no ready-made lib
transit model depends on the dagger runtime

leonardehrenfried added the Technical Debt label

leonardehrenfried mentioned this issue

Remove dependency from Timetable to GTFS-RT TripUpdate #6432

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment