KTrip issueshttps://invent.kde.org/utilities/ktrip/-/issues2023-09-27T16:27:13Zhttps://invent.kde.org/utilities/ktrip/-/issues/43feature. privacy. Document external data sources used2023-09-27T16:27:13Zgcbfeature. privacy. Document external data sources usedplease document data sources that are fetched on application or at least source's README.
from application alone it is not clear if data is fetched from provider or third party. or how much data is shared. etc.please document data sources that are fetched on application or at least source's README.
from application alone it is not clear if data is fetched from provider or third party. or how much data is shared. etc.https://invent.kde.org/utilities/ktrip/-/issues/42Make QQC2DesktopStyle as recommended2023-04-18T18:22:21ZRinigus SaarMake QQC2DesktopStyle as recommendedOn mobile platforms, it doesn't make sense to have QQC2DesktopStyle. Please make this requirement optional or at least possible to disable during configuration.On mobile platforms, it doesn't make sense to have QQC2DesktopStyle. Please make this requirement optional or at least possible to disable during configuration.https://invent.kde.org/utilities/ktrip/-/issues/41list of details of possible connection is too slow2022-12-05T12:15:07ZVasiliy Sergeevlist of details of possible connection is too slowthe list of connections works good, but when entering into view of detail of some connection, the list then reacts very slowthe list of connections works good, but when entering into view of detail of some connection, the list then reacts very slowhttps://invent.kde.org/utilities/ktrip/-/issues/40Time Format only 12 h2023-07-18T10:37:23ZVasiliy SergeevTime Format only 12 hThe time format doesnt respect the system format. No way to change to 24h time formatThe time format doesnt respect the system format. No way to change to 24h time formathttps://invent.kde.org/utilities/ktrip/-/issues/38Time picker in dark mode on x86-64 hard to read2022-06-27T12:14:08Zraguse raguseTime picker in dark mode on x86-64 hard to readHi,
the time picker in ktrip installed on a x86-64 system is hard to read on a dark mode/ dark theme.
I used standard breeze dark theme on 5.25 KDE Plasma, Ktrip 22.04, kirigami-addons 0.2.
Presumably it's likely an adjustment to ki...Hi,
the time picker in ktrip installed on a x86-64 system is hard to read on a dark mode/ dark theme.
I used standard breeze dark theme on 5.25 KDE Plasma, Ktrip 22.04, kirigami-addons 0.2.
Presumably it's likely an adjustment to kirigami-addons, but not sure.
Please see attached.
Should this go to bugs.kde.org?
Thanks.
![ktrip_timepicker_dark](/uploads/96aa1a8e66f08a5d9e5a99f9496c5cd8/ktrip_timepicker_dark.png)https://invent.kde.org/utilities/ktrip/-/issues/37ktrip crashes when searching for stations2022-06-19T21:27:19ZMatthias Geigerktrip crashes when searching for stationsI built a debian package for ktrip. It works fine, but searching for stations leads to a segfault. I attached both gdb logs below. One seems to be related to kpublictransport.
[gdb.log](/uploads/cdf1ffd5a4b124fc10cf0a39d3e56dbe/gdb.log)...I built a debian package for ktrip. It works fine, but searching for stations leads to a segfault. I attached both gdb logs below. One seems to be related to kpublictransport.
[gdb.log](/uploads/cdf1ffd5a4b124fc10cf0a39d3e56dbe/gdb.log)
[gdb2.log](/uploads/5c99adbba3c49ffb1ed7f0f31772e265/gdb2.log)https://invent.kde.org/utilities/ktrip/-/issues/36Add manpage/docbook2022-06-15T23:05:28ZMatthias GeigerAdd manpage/docbookA manpage/docbook file to ship with ktrip would be an improvement imho.
Right now, I still get the following warning when I'm packaging for debian:
`W: ktrip: no-manual-page usr/bin/ktrip`A manpage/docbook file to ship with ktrip would be an improvement imho.
Right now, I still get the following warning when I'm packaging for debian:
`W: ktrip: no-manual-page usr/bin/ktrip`https://invent.kde.org/utilities/ktrip/-/issues/33Design improvement proposal (for reading)2022-04-29T18:23:46Zprog amateurDesign improvement proposal (for reading)
Hello, I love your app. Really. The only things I think shall be improved is :
1. currently, color font is black everywhere. So when there is a lot of information to read (ex: stops + traffic info), I have difficulties to distinguish b...
Hello, I love your app. Really. The only things I think shall be improved is :
1. currently, color font is black everywhere. So when there is a lot of information to read (ex: stops + traffic info), I have difficulties to distinguish between trip and news. So I suggest to keep black color font for trip, and dark grey for the news.
2. maybe we can collapse those news (like you do for the stops) in case it takes a lot of space and / or add a _"i"_ icon (for "information"), what do you think about it ?
Thank you very much !!!
![image](/uploads/0cf16e9fb6045e12794d386370f1ae42/image.png)https://invent.kde.org/utilities/ktrip/-/issues/29KTrip Flatpak not starting on mobile2023-10-13T10:00:14ZKai HillerKTrip Flatpak not starting on mobileStarting the KTrip Flatpak from Flathub prints the following error message a few times, then quits:
```
Unknown backend setting: "supportedOutputFormats"
```
My environment is phosh on a Librem5 running PureOS. The problem could be repl...Starting the KTrip Flatpak from Flathub prints the following error message a few times, then quits:
```
Unknown backend setting: "supportedOutputFormats"
```
My environment is phosh on a Librem5 running PureOS. The problem could be replicated by others with the same configuration.https://invent.kde.org/utilities/ktrip/-/issues/27Add connection to calendar2021-10-14T12:00:20ZNicolas FellaAdd connection to calendarCould be useful for trip planning.
This could use the new calendar abstraction infrastructure once that is in a usable state. Or just create and open an ical file?Could be useful for trip planning.
This could use the new calendar abstraction infrastructure once that is in a usable state. Or just create and open an ical file?https://invent.kde.org/utilities/ktrip/-/issues/26Query by arrival time2021-10-14T11:58:07ZNicolas FellaQuery by arrival timeCurrently we only allow querying by departure time, but doing it by arrival time could also be usefulCurrently we only allow querying by departure time, but doing it by arrival time could also be usefulhttps://invent.kde.org/utilities/ktrip/-/issues/25Use system's native maps application2021-10-14T15:11:02ZNicolas FellaUse system's native maps applicationCurrently we open all maps in openstreetmap.org, but it would be nicer to open the sytems native maps application insteadCurrently we open all maps in openstreetmap.org, but it would be nicer to open the sytems native maps application insteadhttps://invent.kde.org/utilities/ktrip/-/issues/23Insecure redirect error with Nederlandse Spoorwegen (NS)2021-05-16T13:21:32ZArjan VlekInsecure redirect error with Nederlandse Spoorwegen (NS)When planning any trip in Netherlands it will show a message "Insecure redirect" and no result is shown.
I assume "insecure redirect" means a networking issue, not an impossible-to-make-on-time transfer within the trip (as this trip sho...When planning any trip in Netherlands it will show a message "Insecure redirect" and no result is shown.
I assume "insecure redirect" means a networking issue, not an impossible-to-make-on-time transfer within the trip (as this trip should be a direct one from station A to B)
I can't find any setting to ignore these errors, so this effectively makes the app useless in my country.
Strangely enough, this app can get the departures for both stations of this trip just fine. Albeit the details are very limited
### Details i've entered:
#### Providers
Nederlandse Spoorwegen (NS) only. All others are turned off.
#### Departure station
Zoetermeer
#### Arrival station
DEN HAAG (which is in fact Den Haag CS)
#### Departure date and time
Today and as soon as possible, but any combination of departure date and time gives the same error
Screenshots:
### Journey Zoetermeer -> Den Haag
![Screenshot_20210516_150729](/uploads/433f6be6068b947af52ba86feb2ba1ea/Screenshot_20210516_150729.png)
![Screenshot_20210516_150421](/uploads/55eaad4eb82368b91539ca738c919de0/Screenshot_20210516_150421.png)
### Departures Zoetermeer
![Screenshot_20210516_150803](/uploads/5e6001c411b121db9336a8c5d7f02cbe/Screenshot_20210516_150803.png)
### Departures Den Haag
![Screenshot_20210516_150838](/uploads/2d1add4720c359df496c7c2c580922d0/Screenshot_20210516_150838.png)https://invent.kde.org/utilities/ktrip/-/issues/21Select active backends by drawing the shape of the trip on a map2019-12-31T18:34:35ZRobin SeidelSelect active backends by drawing the shape of the trip on a map[Original issue at kitinerary](https://invent.kde.org/kde/itinerary/issues/10). Automatically choose providers that intersect with the trip shape.[Original issue at kitinerary](https://invent.kde.org/kde/itinerary/issues/10). Automatically choose providers that intersect with the trip shape.https://invent.kde.org/utilities/ktrip/-/issues/20Allow removal of previously chosen stations2019-12-30T06:54:56ZRobin SeidelAllow removal of previously chosen stationsThe list of previously chosen stations quickly fills up. Especially if one has once in a lifetime trips, it would be beneficial to be able to remove these stations afterwards to unclutter the homescreen. Maybe as a general concept a 'cre...The list of previously chosen stations quickly fills up. Especially if one has once in a lifetime trips, it would be beneficial to be able to remove these stations afterwards to unclutter the homescreen. Maybe as a general concept a 'create new trip bundle' might be interesting, where before the trip starts one can give the bundle a name and all stations are stored under the bundle's name. This can then later be chosen, expanded or deleted.https://invent.kde.org/utilities/ktrip/-/issues/19Deutsche Bahn alternative connection not shown, even if it is the fastest2019-12-30T06:48:19ZRobin SeidelDeutsche Bahn alternative connection not shown, even if it is the fastestDeutsche Bahn usually displays an alternative if the original connection isn't possible anymore. This isn't shown in ktrip. It is also not shown in transportr, so itt may be a navitia issue.![Screenshot_20191229-092213](/uploads/7cd6a4b9...Deutsche Bahn usually displays an alternative if the original connection isn't possible anymore. This isn't shown in ktrip. It is also not shown in transportr, so itt may be a navitia issue.![Screenshot_20191229-092213](/uploads/7cd6a4b9de2e4e17969195783e5fa64a/Screenshot_20191229-092213.png)![Screenshot_20191229-092131](/uploads/5bc5626da577703d3e51d1046b1c81e5/Screenshot_20191229-092131.png)![Screenshot_20191229-092237](/uploads/4ed79e0f2614fbd9ad9bd298c781af2c/Screenshot_20191229-092237.png)https://invent.kde.org/utilities/ktrip/-/issues/18Save "favorite" or "common" journeys2019-12-22T19:49:57ZBart RibbersSave "favorite" or "common" journeysI'm guessing a lot of people will travel the same journey often, for example to go to work or relatives. It would be nice to be able to mark these journeys as "favorite" so you can easily select them from a list and only have to choose t...I'm guessing a lot of people will travel the same journey often, for example to go to work or relatives. It would be nice to be able to mark these journeys as "favorite" so you can easily select them from a list and only have to choose the departure/arrival time rather than having to enter the "from" and "to" location every time.
Maybe even give an option to use such a journey in reverse (e.g. coming back from work).https://invent.kde.org/utilities/ktrip/-/issues/17Bus stops can not be found (NL)2019-12-20T10:28:40ZBart RibbersBus stops can not be found (NL)I guess the only provider in NL (NS) doesn't return this information? It's currently impossible for me to plan a trip from my house to my parents, as the final part of the trip has to be done by bus but KTrip can not find the bus stop.I guess the only provider in NL (NS) doesn't return this information? It's currently impossible for me to plan a trip from my house to my parents, as the final part of the trip has to be done by bus but KTrip can not find the bus stop.https://invent.kde.org/utilities/ktrip/-/issues/16Fixing finding departure and destination locations2019-10-10T20:09:12ZJohan OuwerkerkFixing finding departure and destination locationsCurrently it is effectively impossible to locate "Wilhelminaplein" or "Rotterdam Wilhelminaplein" metro or tram stations. In fact, KTrip will return absolute "garbage" results such as "Amsterdam Sloterdijk" which is a completely differen...Currently it is effectively impossible to locate "Wilhelminaplein" or "Rotterdam Wilhelminaplein" metro or tram stations. In fact, KTrip will return absolute "garbage" results such as "Amsterdam Sloterdijk" which is a completely different city as well as numerous locations in Germany. This is because anything with a "rotter", "rotterdam", "wilhelm" prefixes or suffixes will match, not to mention any "dam" you care to mention. For possibly the absolute worst case consider anything with "Euro" in its name in Europe...
KTrip should probably prioritise based on whole word matches, and could also be a bit smarter: if it can detect city or town in the name, it could further constrain any matches to within that city/town and perhaps the same could also apply similarly to country/state/province/region names.
Additionally when querying by city name it may be worth biasing towards "Main" stations. E.g for "Amsterdam" return "Amsterdam Centraal" before considering "Amsterdam Sloterdijk" or "Amsterdam Holendrecht". On the one hand this is probably a fairly straightforward heuristic with almost no penalty for getting it wrong (the user just continues typing to refine the search and the search will eventually zero in on the actual target), on the other hand this could also be a bit context/locale specific.
In fact it could be quite locale/location specific. For instance in the Netherlands there is probably a clear bias towards assuming city = its main railway station, so for "Amsterdam" sort as follows: "Amsterdam Centraal" before trying "Amsterdam" before trying "Amsterdam anything else". This is because if the "Centraal" is present it indicates a certain class of station and quality of service/connection associated with this, otherwise any suffix indicates a "region"/location within the city with the main station being unadorned by any classifier/suffix. E.g. for Eindhoven there is no "Eindhoven Centraal" but there is both "Eindhoven" (the main station) and also "Eindhoven Beukenlaan". As it happens this also partially generalises: the "Centraal" suffix is also available under its English alias "Central". I.e. "Amsterdam Centraal" == "Amsterdam Central", at least as far as railway stations in the Netherlands go.https://invent.kde.org/utilities/ktrip/-/issues/15Heuristics based on the notion of a home country2019-10-10T19:46:11ZJohan OuwerkerkHeuristics based on the notion of a home countryCurrently KTrip has no notion of a home country and does not distinguish between "national" or "international" trips. As a consequence if wish to plan a trip ending or starting at some random busstop in Utrecht, the Netherlands there is ...Currently KTrip has no notion of a home country and does not distinguish between "national" or "international" trips. As a consequence if wish to plan a trip ending or starting at some random busstop in Utrecht, the Netherlands there is more than 50/50 chance I will be offered random places in rural France I never even suspected the existence of. This is unlikely to be a desirable feature for simple domestic travels (e.g. commute). The same applies to those unfortunate French people who cannot find their favourite rural busstop but keep getting offered such Dutch gems as "Viaduct, Utrecht".
However it is probably possible for KTrip to do better based on heuristics. This may also require some support in the public transport backend/frameworks but KTrip could pave the way for it by offering the ability to constrain trip planning to either:
* A home country/region
* The country/region in which you are currently located
* International trips
In the first instance this is mainly about sorting possible inputs: e.g. prefer Dutch busstops over French ones if my preferences/location indicate I am in the Netherlands.
Secondly, this information could also be used to constrain offers returned by public transport backend/framework code. E.g. when planning a domestic trip in the Netherlands the application should effectively ignore the many redundant and possibly mangled/reformatted results returned by "foreign" providers. For example when planning railway trips to Cuijk, the Netherlands there is a good chance KTtrip will display connections to "Cuijk Bhf". The "Bhf" is a German convention, indicating this data was (probably) returned by Deutsche Bahn, and it does not match with reality in the Netherlands: i.e. Cuijk station is simply referred to as "Cuijk" in Dutch.
Moreover when it comes to actual trip information such as delays and unplanned cancellations, foreign provides may well be worse than useless. There is significant additional latency in the data exchange between providers, meaning foreign providers do not stand a chance of having accurate up-to-date information on the timeliness and therefore feasibility of catching a particular connection. At least the foreign providers will always lag the domestic providers for that information, because the domestic provider is the first party and not the third party to that information.
Finally, building on a pattern, the heuristics can probably be further refined:
1. Large countries like India might similarly have duplicate names for stations/stops within the country, and possibly even within a (sufficiently large) region/state/province
2. It may be useful to have a bias towards "same class" of transport. E.g.:
* A user may have a city transport pass, or a railway pass but not both. Switching modes of transport to/from railway may not be preferable even if it winds up marginally shorter. In general it may be preferable to limit the number of transport types and associated complexity of transfers
* If the departure is at a railway station, and the destination could be interpreted as either a railway, tram, metro or bus stop it may be worth assuming "railway".
* On domestic travels it may be better to favour domestic services rather than international ones and in particular to disfavour options that require customs checks (e.g. Eurostar) unless deliberately set to travel/plan internationally.