You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for pointing out.
But the mentioned method with the hard coded layer names is just a left over that should have been removed already, it never gets called.
Nevertheless, I'm using a shortcut by extracting the layer names from the style - for speed.
Didn't want to check all +160.000 tiles for which layers they actually contain.
When checking layers already, one could also check the fields they contain and provide a real proper tile.json.
But then again, since the vt spec allows every feature to have different properties I didn't want to go into checking that for consistency as well.
I think we both know that the layer and attribute names in the vtpk tiles are an absolute mess, changing between zoom levels for the same content (what should be the same layer).
Also, if all vtpk metadata would be properly read and output as provided, it wouldn't match the actual vtpk tiles.
This project is truly limited to the basemap.at vector tiles since you embed all(?) layer names into
OutputMbtiles.cs
.To make
vtpk2mbtiles
beneficial for others you need to read the layer names from the tiles.The text was updated successfully, but these errors were encountered: