Open nvkelso opened 7 years ago
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?
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.
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 notifications@github.com 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 https://github.com/tangrams/tron-style/issues/125#issuecomment-254856765, or mute the thread https://github.com/notifications/unsubscribe-auth/AABBXZl2HHRshoiviRnYY0v3bKHYozEgks5q1j1sgaJpZM4KadH8 .
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 notifications@github.com 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 notifications@github.com 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 https://github.com/tangrams/tron-style/issues/125#issuecomment-254856765, 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.
Per request from @bcamper.