landuse polygons (traced from landuse/landcover raster datasets)
Producing these is a colossal pain. I did a set of contour vector tiles for cycle.travel and it required lots of messing with GDAL, subdividing to avoid the shapefile size limit, etc. The results are ok but could be better.
We could potentially support raster tracing in tilemaker, where you'd supply rasters in the layer definition and specify how you wanted them traced. tilemaker would then do the tracing, create vector geometries, and write them out with the usual pipeline.
What we'd need:
libgeotiff - DEM and landcover files are usually supplied as GeoTIFFs
gcntr.c produces very good tracing results, and is BSD-licensed. (It was previously used in matplotlib though they've now implemented their own code.)
It would be a boon for the planet-scale case, but also really easy for people producing local maps to just drop in a GeoTIFF they've sourced from SRTM or somewhere.
We might want to make it an optional feature to avoid imposing the libgeotiff dependency on everyone.
(Just spitballing an idea, not necessarily seriously...)
Many maps contain data ultimately sourced from raster datasets:
Producing these is a colossal pain. I did a set of contour vector tiles for cycle.travel and it required lots of messing with GDAL, subdividing to avoid the shapefile size limit, etc. The results are ok but could be better.
We could potentially support raster tracing in tilemaker, where you'd supply rasters in the layer definition and specify how you wanted them traced. tilemaker would then do the tracing, create vector geometries, and write them out with the usual pipeline.
What we'd need:
It would be a boon for the planet-scale case, but also really easy for people producing local maps to just drop in a GeoTIFF they've sourced from SRTM or somewhere.
We might want to make it an optional feature to avoid imposing the libgeotiff dependency on everyone.