Richard Fairhurst
Richard Fairhurst
Processing a Devon extract with coastline shapefiles (OMT schema) now takes: real 1m10.838s [down from 2m2.193s] user 3m30.221s sys 0m4.077s Without coastline: real 0m25.509s user 0m45.782s sys 0m1.050s The main...
callgrind suggests that, by far, the largest amount of time spent in tile output is in sorting OutputObjects. This is at `TilesAtZoomIterator::RefreshData` https://github.com/systemed/tilemaker/blob/master/src/tile_data.cpp#L114, calling a comparison function at https://github.com/systemed/tilemaker/blob/master/src/output_object.cpp#L140. Without...
LuaJIT is basically a bit weird. It's nice to have for the performance optimisation but causes issues in some circumstances - e.g. segfault when using `--store` on macOS. Unfortunately the...
- [x] Bring OpenMapTiles-compatible config up-to-date (WIP) - [ ] Support transliteration - [ ] Use this to replace current example config.json/process.lua - [ ] Install these somewhere sane under...
It's plausible that the user might not need Lua functions, if they're just making tiles from shapefiles without any OSM data. Currently we bomb out with a kaguya "Type mismatch"...
Mapbox GL renders features in the order they appear in the source tiles (see https://github.com/mapbox/mapbox-gl-js/issues/4361). This is particularly relevant when trying to achieve correct z-index for bridges/tunnels. We should be...
https://github.com/mapbox/mvt-fixtures: "A `require()`able suite of valid and invalid vector tile fixtures for testing Mapbox Vector Tile encoders and decoders"
Same structure as the JSON file. yaml-cpp appears to be the standard: https://github.com/jbeder/yaml-cpp
This is in case anyone else runs into the same issue, really. I was having issues with artefacts at the edges of source images, caused by nodata values. Adding a...
It seems to be a reasonably open secret (by which I mean SOTM bar chat ;) ) that Mapbox is currently putting most of its development efforts behind Valhalla; and...