summaryrefslogtreecommitdiff
path: root/lib/Travelynx/Model
AgeCommit message (Collapse)AuthorLines
2025-11-16DBRIS: also store raw admin IDsBirte Kristina Friesel-0/+3
cf. https://github.com/derf/Travel-Status-DE-DBRIS/issues/10#issuecomment-3538711349
2025-11-16DBRIS: store operatorsBirte Kristina Friesel-0/+3
Requires DBRIS ≥ 0.17, which just hit CPAN
2025-10-29Incorporate dbdb into travelynxBirte Kristina Friesel-0/+15
2025-10-19generate_missing_stats: also rebuild yearly stats, if neededBirte Kristina Friesel-0/+11
2025-10-19get_travel_distance: abort if stop IDs are not present2.17.12Birte Kristina Friesel-0/+3
2025-10-03edit journey: pass on backend ID for origin/destination changes2.17.8Birte Kristina Friesel-2/+4
Closes #322
2025-09-19InTransit: only set isCancelled when needed; also set isAdditionalBirte Kristina Friesel-41/+66
2025-09-19Journeys->update: add lat/lon annotations2.17.3Birte Kristina Friesel-4/+14
This is another fix related to #313
2025-09-18Stations->get_by_names: backend_id is mandatory these daysBirte Kristina Friesel-12/+22
2025-09-17Journey->update: augment changed route with EVA IDs, if available2.17.2Birte Kristina Friesel-3/+4
Closes #313 Related to #305
2025-09-17Journey->update: Keep route data if it has been shortenedBirte Kristina Friesel-6/+23
Partial fix for #313
2025-08-30Prepare v2.17Birte Kristina Friesel-2/+0
2025-08-22InTransit: correctly estimate trip position if vehicle is currently at a stopBirte Kristina Friesel-0/+6
2025-08-18Invalidate stats cache when setting a journey's polylineBirte Kristina Friesel-0/+5
Closes #293
2025-08-17Support polyline uploadsBirte Kristina Friesel-0/+72
2025-08-16backend selection: show frequently used backends2.16.6Birte Kristina Friesel-0/+30
Closes #288
2025-08-04estimate_trip_position: Handle long stops (use dep, not arr)2.16.4Birte Kristina Friesel-8/+5
2025-07-27Fix polyline view in journey detail view for ring linesBirte Kristina Friesel-6/+8
Partially resolves #268 -- in map views that are not specific to a single journey, the polyline will still be wrong.
2025-07-27another distance calculation fix for ring linesBirte Kristina Friesel-3/+7
Fixes #229
2025-07-27Fix polyline-based distance calculation if stops are present more than onceBirte Kristina Friesel-18/+25
Note that the polyline shown in the journey view may still be wrong Fixes #229 Fixes #261
2025-07-27journey: Fix route highlightingBirte Kristina Friesel-4/+13
Polyline is still wrong
2025-07-27polyline handling is hardBirte Kristina Friesel-1/+7
2025-07-27Journey: use _dt suffix for with_route_datetime keysBirte Kristina Friesel-4/+3
2025-07-27get_travel_distance: explain multi-stop-pass handlingBirte Kristina Friesel-6/+24
2025-07-27... oopsBirte Kristina Friesel-0/+2
2025-07-27Journey#get_travel_distance: Only query (sched|rt)_(arr|dep) if definedBirte Kristina Friesel-4/+10
2025-07-20estimate_trip_position: handle duration between legs == 0Birte Kristina Friesel-0/+5
2025-07-18Add localization support.Birte Kristina Friesel-5/+16
Right now, only two languages are supported, and only a fraction of strings are already translated. There's also quite a bunch of todos left where strings are assembled in the Model, which has no access to localization functions. But that's something for iterative refinement over the next months, and (especially when it comes to adding languages and translation strings to templates) merge requests. Squashed commit of the following: commit 67d756f3bd167003907c8357126630dd7c1a3cfa Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Fri Jul 18 19:53:56 2025 +0200 more translations commit 8cb0d65e70e42180419a5dd7634d332e65488dd4 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Fri Jul 18 18:54:12 2025 +0200 sme more translations commit ff12f010380914f9461966f2ef8ac6b303712ee4 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Fri Jul 18 18:53:31 2025 +0200 Add language selection to account page commit 9bf27132cbf2f87bca5af564914d96a57045ecc1 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Fri Jul 18 16:42:28 2025 +0200 Translate footer components commit 90c2c6505e933848268ed9c5bbe21e0b459cd72a Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Fri Jul 18 16:16:50 2025 +0200 Use Accept-Language header if user has no preferred languages commit 814cb4a4dd4017606829ecc6b6c70822bf52a30e Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Fri Jul 18 16:11:19 2025 +0200 Add list of preferred languages to user settings commit 731b789855914cb94ec091604e32aa68a678404a Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Fri Jul 18 15:33:42 2025 +0200 Localization with Locale::Maketext WiP, no suitable foundation for merge requests yet. Still todo: * override Accept-Language header via account settings * Adjust all the templates and frontend javascript Related to #223
2025-07-11Fix train position calculation on first leg of polyline2.15.14Birte Kristina Friesel-1/+1
2025-07-11estimate_trip_position: Remove dead codeBirte Kristina Friesel-11/+0
2025-07-11InTransit: re-add fallback path to location estimation.Birte Kristina Friesel-11/+20
It makes sense when annotating the position with the user rather than the vehicle.
2025-07-10in transit: show estimated train position and full route (greyed out)2.15.13Birte Kristina Friesel-0/+133
2025-07-03Journey-based checkins: store platforms with route; set arrival platform from it2.15.5Birte Kristina Friesel-0/+24
Closes #269
2025-06-29Journeys->get: type: trim trailing white space (hello, hafas)Birte Kristina Friesel-1/+1
2025-06-29Journeys->get: pre-compute delay dataBirte Kristina Friesel-0/+6
2025-06-25Journeys->add: allow consecutive route stops at the same timestampnetworkException-2/+2
This patch relaxes the route timestamp sanity checking introduced in 9e6728a3e14fbe48b7e7aa1d7c0ae2d4e79f0ece by allowing the same timestamp (usually minute accuracy) to occur multiple times for consecutive stops. This is common for trams, for example.
2025-06-24Journeys->add: a little bit of sanity checking for route timestampsBirte Kristina Friesel-2/+10
2025-06-23update_arrival_motis: store arrival platform, if availablenetworkException-1/+2
See b4879a8a48ccecf1071d1ed76a02fecfb4eba3b6
2025-06-23Journey: show dep/arr stop in table; include platforms if availableBirte Kristina Friesel-1/+3
Also: show checkin timestamp
2025-06-23update_arrival_{dbris,efa,hafas}: store arrival platform, if availableBirte Kristina Friesel-3/+5
2025-06-23InTransit->add: Use existing JSON instanceBirte Kristina Friesel-7/+7
2025-06-23Manual journey entry: support sched arr/dep timestamps of intermediate stopsBirte Kristina Friesel-9/+25
2025-06-21Add bare-bones support for manual checkins (still bound to a specific backend)Birte Kristina Friesel-3/+43
Extension opportunities (maybe, eventually) * provide datetimes of intermediate stops * provide an API for real-time data updates * look up stops that travelynx does not yet know about rather than rejecting them outright
2025-06-18Stations->add_or_update: show user-friendly error if latlon are missing2.14.12Birte Kristina Friesel-0/+3
This can happen with EFA SEV stops
2025-06-17DBF links: support efa and motis backendsBirte Kristina Friesel-1/+1
2025-06-16MOTIS: Store trip operatornetworkException-0/+3
2025-06-15EFA: handle arrival being cancelled after checkinBirte Kristina Friesel-9/+10
2025-06-15InTransit->add: efa: mark cancelled stopsBirte Kristina Friesel-9/+10
2025-06-15EFA: Handle check-ins into cancelled departuresBirte Kristina Friesel-1/+1
Note that this bumps the EFA dependency to 3.10 (which is just being released) Arrival cancellations are still on the to-do list
2025-06-15EFA, HAFAS: Store trip operator(s)2.14.2Birte Kristina Friesel-0/+6
Closes #142
generated by cgit v1.2.3 (git 2.39.1) at 2025-12-10 04:23:48 +0000