Brett Camper

deck.gl uses a similar approach ([docs](https://github.com/visgl/deck.gl/blob/master/docs/developer-guide/custom-layers/picking.md)), and you can also see some ideas for applying it to multiple objects that they developed here: https://github.com/visgl/deck.gl/blob/master/dev-docs/RFCs/v5.3/picking-overlapping-objects-rfc.md. As @matteblair said, not straightforward, but...

Sorry for the delay. Unfortunately, there is no built-in way to do this right now. You get nice text handling for anchoring, collision, etc. by attaching/nesting a `text` block underneath...

Keeping this open to log as an enhancement request.

If I understand what you are getting at -- I could see providing hints in the scene YAML, in the data source definition, that specifies which properties (by layer) are...

Actually, can you say a bit more about the motivation / expected savings for ES here? Is it to improve initial feature parse time from the data source, or reduce...

This is a very interesting idea and I am curious to test something similar on Tangram JS. Given a lot of the operations being saved here are native to the...

Is it intended to be an MBTiles-datasource-only feature?

New landcover layer would be vectorized (from raster)? On Wed, May 1, 2019 at 2:45 PM Nathaniel V. KELSO wrote: > This would be a breaking 2.0 change, where we'd...

Just wanted to note that TileJSON endpoints are now available for the Mapzen Vector Tile service (http://mapzen.com/vector). See https://github.com/mapzen/vector-datasource/issues/73.

Sorry for the delay -- will get you some representative scene data we use for Tangram shortly. Good to see the project picking back up :)