summaryrefslogtreecommitdiff
path: root/lib/Travelynx/Model
AgeCommit message (Collapse)AuthorLines
2024-08-27get_travel_distance: intermediate: Handle destination renames in sanity check2.8.35Birte Kristina Friesel-1/+6
Also related to #160
2024-08-26map, get_travel_distance: Prefer EVA ID over name for route matches2.8.33Birte Kristina Friesel-2/+6
Station names frequently change, so the EVA ID is more robust Closes #160
2024-08-25get_travel_distance: no need for debug output if there is no polylineBirte Kristina Friesel-2/+4
2024-08-23Suggest backends based on coverage and latest checkout coordinatesBirte Kristina Friesel-0/+26
References #156
2024-08-17get_travel_distance: do not overwrite {to,from}_eva with undefBirte Kristina Friesel-2/+2
2024-08-15stats, map: deal with multiple EVA IDs mapping to the same station nameBirte Kristina Friesel-20/+54
2024-08-14IRIS checkout: do not overwrite HAFAS route with IRIS routeBirte Kristina Friesel-8/+0
The IRIS route may differ from the HAFAS route in case of diversions, causing travelynx to lose real-time data, coordinates, and polyline when the follow-up add_route_timestamps call is not made.
2024-08-14get_travel_distance: always return beeline distance2.8.18Birte Kristina Friesel-9/+6
2024-08-09get_connection_targets: always return a list2.8.13Birte Kristina Friesel-2/+5
Closes #152 Closes #153
2024-08-07dumpstops: provide backend name and type rather than just opaque IDs2.8.10Birte Kristina Friesel-1/+1
2024-08-04journey->add: pass backend_id on to station search for route2.8.9Birte Kristina Friesel-2/+3
Ref: #150
2024-08-04manual journey entry: hardcode DB (HAFAS) for station selection2.8.8Birte Kristina Friesel-2/+4
TODO: Add a dropdown to select different backends Closes #150
2024-07-26Multi-backend supportBirte Kristina Friesel-73/+236
Squashed commit of the following: commit 92518024ba295456358618c0e8180bd8e996fdf1 Author: Birte Kristina Friesel <birte.friesel@uos.de> Date: Fri Jul 26 18:39:46 2024 +0200 add_or_update station: remove superfluos 'new backend id := old backend id' commit df21c20c6e4c86454f8a9ac69121404415217f2a Author: Birte Kristina Friesel <birte.friesel@uos.de> Date: Fri Jul 26 18:35:51 2024 +0200 revert connection targets min_count to 3 commit be335cef07d0b42874f5fc1de4a1d13396e8e807 Author: Birte Kristina Friesel <birte.friesel@uos.de> Date: Fri Jul 26 18:20:05 2024 +0200 mention backend selection in API documentation commit 9f41828fb4f18fd707e0087def3032e8d4c8d7d8 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Thu Jul 25 20:19:23 2024 +0200 use_history: not all backends provide route data in departure monitor commit 09714b4d89684b8331d0e96f564a4c7432318f70 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Thu Jul 25 20:11:44 2024 +0200 disambiguation: pass correct hafas parameter commit 8cdf1120fc32155dc6525be64601b7c10a9c7f52 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Thu Jul 25 20:11:28 2024 +0200 _checked_in: hide Zuglauf link for non-db checkins commit 7455653f541198e0e0a6d11aed421487ffdb6285 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Thu Jul 25 20:01:47 2024 +0200 debug output commit b9cda07f85601a58ea32dbdacdd5399f302db52b Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Thu Jul 25 19:09:07 2024 +0200 fix remaining get_connection_targets / get_connecting_trains_p invocations commit 2759d7258c37c7498905cfe19f6b4c4f6d16bd21 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Wed Jul 24 20:50:12 2024 +0200 support non-DB HAFAS backends (WiP)
2024-07-21Stations: Remove get_latlon_by_name (no longer needed)2.7.9Birte Kristina Friesel-14/+0
2024-07-21Add lat/lon to pre-2.7.8 journeys; add eva where missingBirte Kristina Friesel-9/+8
This speeds up the map significantly and makes coordinates_by_station obsolete
2024-07-21Journey->add: store lat/lon for route at entry time, if availableBirte Kristina Friesel-4/+33
2024-07-08store lat/lon along with route2.7.8Birte Kristina Friesel-2/+6
This increases resilience against EVA ID reuse
2024-06-15InTransit: allow setting data in add callBirte Kristina Friesel-2/+9
2024-06-15remove service / sb_template selection; hardcode DBF with variable hafas flagBirte Kristina Friesel-36/+3
2024-06-15recent journeys: use hafas=DB as wellBirte Kristina Friesel-1/+1
2024-06-15Use hafas=DB rather than hafas=12.6.22Birte Kristina Friesel-1/+4
2024-06-08Store journey backend; do not rely on '|' in ID to distinguish IRIS/HAFASBirte Kristina Friesel-1/+17
This is in preparation for supporting multiple HAFAS backends, and possibly EFA and RIS::Journeys.
2024-06-06... derp2.6.18Birte Kristina Friesel-4/+1
2024-06-06traewelling pull sync requires user_name to be set2.6.17Birte Kristina Friesel-1/+4
2024-05-24check train/trip id when updating associated dataBirte Kristina Friesel-17/+31
this avoid race conditions when a user changes their checkin between the time of request (old trip id) and the time of data update (new trip id). These could lead to funny effects such as buses suddenly having S-Bahn carriage formations.
2024-05-22route_after: handle passing the same stop more than once2.6.10Birte Kristina Friesel-2/+9
2024-05-09InTransit: postprocess: simplify DateTime handling a bitBirte Kristina Friesel-21/+25
2024-04-21refactor polyline insertion into InTransit ModelBirte Kristina Friesel-0/+55
2024-04-16Store HAFAS checkins with type/train/line number at checkin station2.6.7Birte Kristina Friesel-3/+5
2024-04-03store tz_offset in route data if presentBirte Kristina Friesel-1/+7
2024-02-13Journeys: adjust sanity_check for local transit stuff2.5.17Birte Kristina Friesel-7/+7
2024-02-09add dumpstops command2.5.16Birte Kristina Friesel-0/+6
2023-12-27Switch to Travel::Status::DE::HAFAS 5.xBirte Kristina Friesel-28/+29
2023-10-01suggested connections: avoid fetching IRIS trains via HAFASBirte Kristina Friesel-3/+6
2023-10-01store related stations; respect them when looking up connectionsBirte Kristina Friesel-14/+48
2023-09-24intransit: support HAFAS trains that do not have a typeBirte Kristina Friesel-1/+1
2023-09-24add support for HAFAS connection suggestions; drop manual destination listBirte Kristina Friesel-27/+3
Still TODO: handle stations that have several EVAs
2023-09-09indicate whether current journey has realtime dataBirte Kristina Friesel-3/+9
2023-09-07Fix intermediate stop display for journeys without real-time data, e.g. H-BahnBirte Kristina Friesel-4/+8
2023-08-26obtain autocompletion from database2.1.1Birte Kristina Friesel-0/+13
2023-08-22select latest journey based on timestamp, not ID2.0.2Birte Kristina Friesel-1/+1
This avoids manually added past journeys messing with the latest travel target
2023-08-16recent targets: distinguish hafas/irisBirte Kristina Friesel-3/+4
2023-08-13WIP: HAFAS supportBirte Kristina Friesel-21/+198
2023-08-09Store traewelling refresh token in database1.34.3Birte Kristina Friesel-12/+13
2023-08-07Traewelling: replace legacy password login with OAuth2Birte Kristina Friesel-4/+3
This is a breaking change insofar as that traewelling support is no longer provided automatically, but must be enabled by providing a traewelling.de application ID and secret in travelynx.conf. However, as traewelling.de password login is deprecated and wil soon be disabled, travelynx would break either way. So we might or might not see travelynx 2.0.0 in the next days. Automatic token refresh is still todo, but that was the case for password login as well. Closes #64
2023-07-19Users->delete: delete relations as well1.33.6Birte Kristina Friesel-9/+11
2023-07-18followee list: show if accounts are following back1.33.3Birte Kristina Friesel-2/+20
2023-07-16account: add a list of sent follow requestsBirte Kristina Friesel-9/+11
2023-07-16show followee checkins in departure boardBirte Kristina Friesel-1/+1
2023-07-15postprocess timeline; move user-related parts to get_user_statusBirte Kristina Friesel-152/+131