Open jschleuss opened 5 years ago
Zero idea why, but this issue disappears when the tiles are fetched as GeoJSON:
nextzen:
type: GeoJSON
url: https://{s}.tiles.nextzen.org/tilezen/vector/v1/256/all/{z}/{x}/{y}.json
url_params:
api_key: global.sdk_mapzen_api_key
url_subdomains: [a,b,c,d]
rasters: [normals]
max_zoom: 16
Any disadvantage of handling this way?
The above solution actually results in a new bald spot above Chico between zooms 8 and 9. What I ended up doing was adding a GeoJSON layer ONLY for the earth tiles and including a MVT layer on top. That seems to cover all tiles.
It's a bit slower to download both file types, but it's filled in and and exports well.
That's really weird. I think it must have to be an error in the YAML style file.
There's a missing terrain tile in the East Bay at zoom level 8
Issue does not show up in live interactive Nextzen maps that we've pubbed