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
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
Hi,
I read that vector tiles would be much more space efficient than raster tiles. But comparing what your HTML or iOS demo apps are downloading it doesn't look like so.
Was in the process of answering this and found that @flippmoke had already answered it (in much better detail than I ever could): mapbox/vector-tile-spec#53
Regarding one of @flippmoke’s points, Mapbox GL JS supports inspecting feature attributes in the layer via the featuresAt() and featuresIn() APIs. We’re working to port that to the iOS SDK in #3172.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I read that vector tiles would be much more space efficient than raster tiles. But comparing what your HTML or iOS demo apps are downloading it doesn't look like so.
For example:
http://a.tiles.mapbox.com/v4/mapbox.mapbox-streets-v6/14/4823/6160.vector.pbf?access_token={token}
https://api.mapbox.com/v4/mapbox.streets/14/4823/6160.png?access_token={token}
Results in downloading 16.725 bytes PNG versus 35.206 bytes PBF file.
How is it possible?
The text was updated successfully, but these errors were encountered: