1. 31 Aug, 2020 6 commits
  2. 28 Aug, 2020 1 commit
  3. 15 Aug, 2020 6 commits
  4. 05 Aug, 2020 2 commits
  5. 02 Aug, 2020 15 commits
  6. 01 Aug, 2020 2 commits
    • Johnny Jazeix's avatar
      Fix Windows build. · 952eac8b
      Johnny Jazeix authored
      QT_STRICT_ITERATORS do not work on vs compilers.
      Missing ZLib includes for osm runner plugin.
      952eac8b
    • Johnny Jazeix's avatar
      Fix Windows build. · 3aa9cb26
      Johnny Jazeix authored
      QT_STRICT_ITERATORS do not work on vs compilers.
      Missing ZLib includes for osm runner plugin.
      3aa9cb26
  7. 30 Jul, 2020 4 commits
  8. 27 Jul, 2020 1 commit
    • Volker Krause's avatar
      Enable TileDirectory to load input data from an OSMX file · b19fd67f
      Volker Krause authored
      This is considerably more efficient to read and to update compared to the
      manually maintained o5m pyramid used so far, at the cost of a lot of disk
      space.
      
      The OSMX usage is extremely primitive so far, relying solely on its command
      line tool. We could gain a bit more performance still by using OSMX API
      directly and avoiding the PBF file indirection, but that is in the ~1%
      range, and technically not entirely straightforward due to how OSMX is
      built and its bundled dependencies.
      
      This code will be used by the upcoming Tirex backend for on-demand tile
      generation, existing code is only touched for removing a small bit of
      dead code.
      b19fd67f
  9. 21 Jul, 2020 1 commit
  10. 17 Jul, 2020 1 commit
  11. 14 Jul, 2020 1 commit
    • Volker Krause's avatar
      Remove broken caching of area computation results · d202b912
      Volker Krause authored
      The problem here is that this code uses the address of the argument as
      cache key. The argument can however be a temporary, meaning we can get
      cache key collisions and thus wrong results. This shows in tiles
      occasionally missing a random subset of polygons, typically in the zoom
      range 11-15, where we apply area size filters.
      
      The solution is fortunately easy: Remove the caching of the area
      computation result entirely. We can do this as this neither contributes
      to the overall cost in a measurable way, nor do we seem to compute the
      area of the same polygon multiple times anyway.
      d202b912