1. 26 Jan, 2021 1 commit
  2. 24 Dec, 2020 1 commit
  3. 03 Sep, 2020 1 commit
    • Volker Krause's avatar
      Allow to specify supported rental vehicle networks in OTP configuration · 1ab862a0
      Volker Krause authored
      Unfortunately this cannot be queried online, but needs to be dug out of
      server-side config files.
      
      This enables a number of things though:
      - filter static dummy networks that e.g. stadtnavi uses to provide
      locations for taxis or car sharing.
      - translate the internally used identifiers to human readable names.
      - provide vehicle type default values for single-type networks, so we can
      show appropriate icons etc.
      - map identifiers to GBFS feeds where we have those available as well, to
      support result merging.
      
      We also still need to add this data to the other OTP instances supporting
      rental vehicles (eg. those in Finland).
      1ab862a0
  4. 31 Aug, 2020 1 commit
  5. 20 Aug, 2020 1 commit
  6. 10 Aug, 2020 1 commit
    • Volker Krause's avatar
      Expand the rental vehicle data types · 46101085
      Volker Krause authored
      Vaguely following the MDS/GBFS model (but still vastly simplified for now).
      While initially motivated by better support bike sharing in OTP backends,
      it's seems likely we can actually build a generic GBFS-based client as
      well.
      46101085
  7. 26 Apr, 2020 1 commit
    • Volker Krause's avatar
      Rename Departure to Stopover · 5858c90c
      Volker Krause authored
      Departure was always a poor name, given it is also used for arrivals.
      Things got worse with this now also being used for intermediate stops,
      which are both arrivals and departures at the same time. Finding a good
      alternative name is tricky though, as many candidates are ambiguous
      regarding stop locations ("stop", "halt", etc). Digitransit uses the
      words "call" and "quay" to distinguish this, but while clear those are
      rather niche terms. FPTF uses "stopover" for this, which seems like a
      decent compromise.
      
      This is only the first step in adjusting the entire API accordingly,
      more classes will follow, while trying to keep source compatibility.
      5858c90c
  8. 24 Jan, 2020 1 commit
  9. 23 Jan, 2020 1 commit
  10. 20 Jan, 2020 1 commit
  11. 19 Jan, 2020 2 commits
  12. 11 Jan, 2020 3 commits
  13. 09 Jan, 2020 3 commits
  14. 03 Jan, 2020 1 commit
  15. 21 Dec, 2019 1 commit
    • Volker Krause's avatar
      Add basic infrastructure for vehicle layout queries · 9c62130b
      Volker Krause authored
      That is, query coach layouts of a train, as well as where they will stop
      on a platform. This information is available at varying degree of detail
      at least for German and Indian long distance railways it seems.
      
      Nothing actually working yet, just the empty shell.
      9c62130b
  16. 28 Sep, 2019 1 commit
    • Volker Krause's avatar
      Keep qGetPtrHelper internal · 4cedb0da
      Volker Krause authored
      It's actually only needed in the implementation, and not for each usage of
      Q_DECLARE_PUBLIC. This avoids conflicting with other libraries having a
      similar helper function.
      4cedb0da
  17. 17 Jul, 2019 1 commit
  18. 12 Jul, 2019 1 commit
  19. 07 Jul, 2019 1 commit
  20. 26 Feb, 2019 4 commits