summaryrefslogtreecommitdiff
path: root/templates/journey.html.ep
AgeCommit message (Collapse)AuthorLines
2025-08-22journey: polylines can be downloaded if polylines or route data is availableBirte Kristina Friesel-34/+32
polylines _cannot_ be uploaded if proper route data is unavailable (i.e., route stops do not have ID / lat,lon data)
2025-08-17Support polyline uploadsBirte Kristina Friesel-29/+48
2025-08-17Journey: Add JSON and GPX export of polylinesBirte Kristina Friesel-35/+44
2025-07-27journey: Fix route highlightingBirte Kristina Friesel-2/+4
Polyline is still wrong
2025-07-27Journey: use _dt suffix for with_route_datetime keysBirte Kristina Friesel-2/+2
2025-07-27Allows journeys to be exported (downloaded) as raw JSONBirte Kristina Friesel-0/+10
Closes #279
2025-07-23journey: share: timestamps are always intBirte Kristina Friesel-1/+1
2025-07-23Translate LuftlinieBirte Kristina Friesel-2/+2
2025-07-21Localize journeys.html.ep and translate it to en-GBBirte Kristina Friesel-21/+22
2025-06-30journey: only show delay if it's at least one minuteBirte Kristina Friesel-8/+18
2025-06-23Journey: show dep/arr stop in table; include platforms if availableBirte Kristina Friesel-22/+34
Also: show checkin timestamp
2025-06-15Journey: Expose timestamps with second resolution, if available2.14.4Birte Kristina Friesel-6/+6
2025-06-15EFA, HAFAS: Store trip operator(s)2.14.2Birte Kristina Friesel-0/+8
Closes #142
2025-05-17dbris: persist backend messages and show them in journey view2.11.27Birte Kristina Friesel-0/+10
2025-03-25Consistently use 'train' for DB (IRIS, bahn.de) and 'directions' for HAFASBirte Kristina Friesel-1/+1
2024-08-26Also fix #160 in /journey/ stop list2.8.34Birte Kristina Friesel-3/+3
2024-08-25journey: show ID next to backend info2.8.30Birte Kristina Friesel-2/+2
2024-08-14journey: show beeline if route is unavailable2.8.19Birte Kristina Friesel-0/+6
2024-06-08Store journey backend; do not rely on '|' in ID to distinguish IRIS/HAFASBirte Kristina Friesel-0/+7
This is in preparation for supporting multiple HAFAS backends, and possibly EFA and RIS::Journeys.
2023-09-16journey: show distances below 10km with 100m resolution (and <1km with 1m)Birte Kristina Friesel-2/+2
2023-08-14hafas preparations: Zug → FahrtBirte Kristina Friesel-2/+2
2023-05-01journey: shorten headers; remove realtime from journeyDerf Null-4/+4
2023-05-01journey: show times of intermediate stops, if availableDerf Null-1/+23
2023-03-24only show passenger rights link on own journeys1.30.8Derf Null-1/+1
2023-03-03token: do not expose full checkin timestampDaniel Friesel-1/+1
2023-03-01oops.Daniel Friesel-2/+2
2023-03-01journey template: $journey_visibility may be unsetDaniel Friesel-6/+6
2023-02-28journey: add token to share link if non-publicDaniel Friesel-1/+6
2023-02-27set visibility per journey (wip)Daniel Friesel-0/+10
some odds and ends left to polish, but ready for testing
2023-02-15journey: add share buttonDaniel Friesel-0/+14
2020-09-03add public profile page and public journey detailsDaniel Friesel-0/+3
2020-02-23journey details: show route on map if available1.15.1Daniel Friesel-26/+29
2020-02-19allow showing past journeys on shared status pageDaniel Friesel-38/+40
2020-02-01allow checkin and checkout station to be editedDaniel Friesel-0/+6
2020-01-28Add aria labels where needed, commit 1 of many (#37)Daniel Friesel-3/+3
2019-12-19move wagon group display to sub-template1.11.6Daniel Friesel-11/+1
2019-12-19save all the wagon orders we can getDaniel Friesel-1/+19
2019-12-14improve wagon output in journey detailsDaniel Friesel-4/+4
2019-12-13preliminary wagon viewDaniel Friesel-0/+18
2019-12-08allow a journey's cancellation status to be edited1.11.1Daniel Friesel-2/+6
Closes #27
2019-11-19allow route input when adding journeys manually (#26)Daniel Friesel-0/+6
2019-09-12Explicitly set passenger rights form filename1.9.1Daniel Friesel-1/+2
2019-09-12add auto-generated passenger rights forms1.9.0Daniel Friesel-0/+12
2019-08-23Allow comments to be editedDaniel Friesel-9/+9
2019-08-23Add proper journey comment supportDaniel Friesel-4/+2
2019-05-26Use JSON for messages and route storage, prepare for extended route dataDaniel Friesel-4/+4
2019-05-16Further color improvementsmarudor-1/+1
2019-05-03do not mange journey edit link on small devices1.1.5Daniel Friesel-3/+23
2019-04-26Add manual journey entryDaniel Friesel-9/+22
Closes #3
2019-04-23Use one row per journey instead of split checkin/checkout entriesDaniel Friesel-1/+1
Whether a user is in transit or not is now determined by an entry in the in_transit table instead of a dangling checkin. All completed journeys are stored in the "journeys" table. This does most of the work needed for automatic checkout. However, note that the corresponding worker process is not implemented yet.
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-05 12:32:28 +0000