Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change source to MVT (from TopoJSON) #125

Open
nvkelso opened this issue Oct 19, 2016 · 4 comments
Open

Change source to MVT (from TopoJSON) #125

nvkelso opened this issue Oct 19, 2016 · 4 comments
Milestone

Comments

@nvkelso
Copy link
Member

nvkelso commented Oct 19, 2016

Per request from @bcamper.

@nvkelso nvkelso added this to the 2.1 milestone Oct 19, 2016
@nvkelso
Copy link
Member Author

nvkelso commented Oct 19, 2016

It's not clear if all Mapzen house styles should default to MVT, or only if they get included in a native app. Since all end up getting included in native apps, is it the native app's responsibility to modify this?

@matteblair
Copy link
Member

Is there a downside to using MVT everywhere? I seem to remember that MVT is about 30% faster for parsing natively and I think it's roughly the same as TopoJSON on the web.

@bcamper
Copy link
Member

bcamper commented Oct 19, 2016

It's worth doing some benchmarks, but I've never noticed any significant
difference on the web, so I would be cool to use MVT everywhere for
simplicity.

On Wed, Oct 19, 2016 at 11:55 AM, Matt Blair [email protected]
wrote:

Is there a downside to using MVT everywhere? I seem to remember that MVT
is about 30% faster for parsing natively and I think it's roughly the same
as TopoJSON on the web.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#125 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABBXZl2HHRshoiviRnYY0v3bKHYozEgks5q1j1sgaJpZM4KadH8
.

@nvkelso
Copy link
Member Author

nvkelso commented Oct 19, 2016

For debug GUI in the HTML/JS rig we'd keep that link out to TopoJSON for human legibility, but change the Tangram YAML source to MVT.

On Oct 19, 2016, at 10:39, Brett Camper [email protected] wrote:

It's worth doing some benchmarks, but I've never noticed any significant
difference on the web, so I would be cool to use MVT everywhere for
simplicity.

On Wed, Oct 19, 2016 at 11:55 AM, Matt Blair [email protected]
wrote:

Is there a downside to using MVT everywhere? I seem to remember that MVT
is about 30% faster for parsing natively and I think it's roughly the same
as TopoJSON on the web.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#125 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABBXZl2HHRshoiviRnYY0v3bKHYozEgks5q1j1sgaJpZM4KadH8
.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants