1. 21 Apr, 2020 2 commits
  2. 20 Apr, 2020 2 commits
  3. 19 Apr, 2020 3 commits
  4. 18 Apr, 2020 6 commits
    • Volker Krause's avatar
      Handle more station types, and prioritize them · 30a73505
      Volker Krause authored
      This fixes the DEN and DUS tests, and makes some progress on PDX/HKG/PVG.
      30a73505
    • Volker Krause's avatar
      Look for stations slightly outside of terminal bounds as well · 412cfbea
      Volker Krause authored
      This fixes HAM, and should fix GDN/FRA/LIS too eventually, once the issues
      exposed there now get addressed.
      412cfbea
    • Volker Krause's avatar
      Also consider stations inside terminal buildings outside the airport bounds · b4911486
      Volker Krause authored
      This can happen when terminal buildings overlap the airport bounds. Fixes
      CPH for example.
      b4911486
    • Volker Krause's avatar
      Check the precise boundary for including terminals, not just the bbox · 91b4705e
      Volker Krause authored
      This removes terminal buildings from adjacent facilities from the
      consideration, such as the Airbus site next to TLS, or the government
      terminal next to TXL.
      91b4705e
    • Volker Krause's avatar
      Add a bunch of tests for optimized airport coordinates · 6479a49c
      Volker Krause authored
      This should help evaluate tweaks to the coordinate picking logic. With the
      current raw coordinates from Wikidata most of this fails (MUC being the
      exception), with the new OSM-based coordinate selection two thirds yield
      good results already.
      6479a49c
    • Volker Krause's avatar
      Initial experiments to improve airport coordinates based on OSM data · 4b5489d0
      Volker Krause authored
      So far the coordinates we use for navigating to/from airports come from
      Wikidata, and are typically somewhere on the center of the whole airport
      area, typically a runway. That's far from ideal for navigation, as that's
      neither a location you want to or event can get to, and in extreme cases
      this even leads to navigation "snapping" to the opposite side of the
      airport entirely.
      
      Instead we want a coordinate around somewhere around the entrance. So far
      there's three types of information from OSM we consider here:
      * terminal buildings (or rather the center point of their bounding box)
      * entrance nodes on terminal building polygons (unfortunately not reliably
      available in the input data).
      * railway stations on the premise of the airport.
      
      This improves the result for many smaller or mid-sized airports
      considerably already. What this cannot improve is the situation
      at large airports with widely spread terminals (LHR, CDG, MXP, etc).
      Those however cannot meaningfully represented by a single coordinate
      anyway.
      
      Code isn't hooked up yet, this is just for local experiments at this
      point.
      4b5489d0
  5. 17 Apr, 2020 1 commit
  6. 15 Apr, 2020 2 commits
  7. 14 Apr, 2020 2 commits
  8. 01 Apr, 2020 1 commit
    • Volker Krause's avatar
      Add lookup table for VR (Finish railway) station codes · d337aced
      Volker Krause authored
      This doesn't cover codes containing 'Ä' or 'Ö' yet, which appear in the
      official list, but for which we have no idea how they are encoded in the
      corresponding barcode yet. As that's only a dozen or so in total, that's
      not a big problem though.
      d337aced
  9. 30 Mar, 2020 2 commits
  10. 29 Mar, 2020 1 commit
  11. 28 Mar, 2020 10 commits
  12. 27 Mar, 2020 1 commit
  13. 26 Mar, 2020 4 commits
  14. 25 Mar, 2020 3 commits