- 20 Oct, 2016 2 commits
-
-
Dennis Nienhüser authored
(cherry picked from commit 19c19e20)
-
Dennis Nienhüser authored
Spatially adjacent regions (e.g. neighboring states) share borders such that in rectangular tiles data from both appears. These need to be handled individually in order to have data from both (or more) input files appear in the final tile. (cherry picked from commit f6618ae6)
-
- 04 Oct, 2016 1 commit
-
-
Dennis Nienhüser authored
-
- 03 Oct, 2016 3 commits
-
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
Same approach as in GeoGraphicsScene. Placemarks are assigned a tile level that fully contains them once. When clipping to some boundary box, only those placemarks on the path towards the top of the pyramid can intersect them. Note that this is only a heuristic; checking the actual bounding box intersection again afterwards still rules out a lot of placemarks that don't actually intersect. Rough speed comparison for different approaches: A) Slow: clip all placemarks directly B) Medium: clip all placemarks based on tile pyramid C) Fast: clip all placemarks that intersect with the bounding box D) Very fast: clip all placemarks based on tile pyramid that also intersect with the bounding box C) is the old implementation, B) something I tested locally and C) the new implementation.
-
- 02 Oct, 2016 3 commits
-
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
Creating vector tiles locally is now as easy as running marble-vectorosm-tilecreator http://download.geofabrik.de/europe/germany/baden-wuerttemberg/bremen-latest.osm.pbf Local files can be passed as well. See --help for additional options.
-
Dennis Nienhüser authored
-
- 01 Oct, 2016 7 commits
-
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
Input map files are usually the largest files and traversing them instead of output tiles ensures they have to be loaded into memory just once
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
- 27 Sep, 2016 2 commits
-
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
- 26 Sep, 2016 3 commits
-
-
Dennis Nienhüser authored
Typical usage: marble-vectorosm-tilecreator -o <dir> -z 11,13,15 -m landmass/7 map.o5m Where landmass/7 is a directory created before using e.g. marble-vectorosm-tilecreator -o landmass -z 7 -k landmass.shp (note -o landmass and -z 7 resulting in landmass/7/... tiles)
-
Dennis Nienhüser authored
To avoid reading in a large landmass file for the whole world, they should be preprocessed into tiles instead. Typical usage: marble-vectorosm-tilecreator -o <dir> -z 7 -k landmass.shp
-
Dennis Nienhüser authored
-
- 25 Sep, 2016 2 commits
-
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
- 24 Sep, 2016 4 commits
-
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
- 21 Sep, 2016 1 commit
-
-
Friedrich W. H. Kossebau authored
-
- 20 Sep, 2016 2 commits
-
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
- 19 Sep, 2016 1 commit
-
-
Dennis Nienhüser authored
Since we display tile level n up to zoom level n+1, reduce nodes for level n+1, not n.
-
- 11 Sep, 2016 9 commits
-
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-
Dennis Nienhüser authored
-