Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

Vector vs Raster tiles required space #3363

Closed
jzarzuela opened this issue Dec 20, 2015 · 2 comments
Closed

Vector vs Raster tiles required space #3363

jzarzuela opened this issue Dec 20, 2015 · 2 comments

Comments

@jzarzuela
Copy link

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?

@friedbunny
Copy link
Contributor

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

@1ec5
Copy link
Contributor

1ec5 commented Dec 21, 2015

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants