3 ms·

This is really sweet, awesome work. I really love onthegomap too. I maintain an openmaptiles pipeline, and we've got our planet runtimes down to about ~4 days

This is really sweet, awesome work. I really love onthegomap too. I maintain an openmaptiles pipeline, and we've got our planet runtimes down to about ~4 days on AWS. Would be excited to see if we could use this tool, but we really heavily depend on PostGIS data manipulation to ensure that the data we want ends up in our output tiles. How difficult do you think migrating this SQL to your tool would be? It seems like you can support modifying the data fairly heavily, both before and after MBtile creation.

zylepe 5y ago
Flatmap calls into user-defined profiles in 2 places: first when processing each input element to map it to a vector tile feature, then a second time right before emitting all vector features in a layer. That second call lets you manipulate vector features on each tile using JTS geometry utilities (i.e. merge nearby polygons or lines with the same tags). PostGIS uses GEOS which is ported from JTS so you have access to pretty much the same geometry utilities - often with the same name. It's definitely not as flexible as a PostGIS based solution - especially if you join faraway features that don't appear on the same tile, but in practice it was enough to port the entire OpenMapTiles schema. See the basemap layers package: https://github.com/onthegomap/flatmap/tree/main/flatmap-basemap/src/main/java/com/onthegomap/flatmap/basemap/layers https://github.com/onthegomap/flatmap/tree/main/flatmap-base... for example see the landcover layer https://github.com/onthegomap/flatmap/blob/main/flatmap-basemap/src/main/java/com/onthegomap/flatmap/basemap/layers/Landcover.java#L63 https://github.com/onthegomap/flatmap/blob/main/flatmap-base... which was ported from the SQL contained in https://github.com/openmaptiles/openmaptiles/tree/master/layers/landcover https://github.com/openmaptiles/openmaptiles/tree/master/lay... Also, this OpenMapTiles PR might help improve your existing pipeline after it gets merged: https://github.com/openmaptiles/openmaptiles-tools/pull/383 https://github.com/openmaptiles/openmaptiles-tools/pull/383 Edit: formatting

zylepe 5y ago

Flatmap calls into user-defined profiles in 2 places: first when processing each input element to map it to a vector tile feature, then a second time right before emitting all vector features in a layer. That second call lets you manipulate vector features on each tile using JTS geometry utilities (i.e. merge nearby polygons or lines with the same tags). PostGIS uses GEOS which is ported from JTS so you have access to pretty much the same geometry utilities - often with the same name. It's definitely not as flexible as a PostGIS based solution - especially if you join faraway features that don't appear on the same tile, but in practice it was enough to port the entire OpenMapTiles schema. See the basemap layers package: https://github.com/onthegomap/flatmap/tree/main/flatmap-basemap/src/main/java/com/onthegomap/flatmap/basemap/layers https://github.com/onthegomap/flatmap/tree/main/flatmap-base... for example see the landcover layer https://github.com/onthegomap/flatmap/blob/main/flatmap-basemap/src/main/java/com/onthegomap/flatmap/basemap/layers/Landcover.java#L63 https://github.com/onthegomap/flatmap/blob/main/flatmap-base... which was ported from the SQL contained in https://github.com/openmaptiles/openmaptiles/tree/master/layers/landcover https://github.com/openmaptiles/openmaptiles/tree/master/lay... Also, this OpenMapTiles PR might help improve your existing pipeline after it gets merged: https://github.com/openmaptiles/openmaptiles-tools/pull/383 https://github.com/openmaptiles/openmaptiles-tools/pull/383 Edit: formatting