In some cases, the calling application may want to provide its own data at run-time. We already have the setDataSource() method for adding non-tiled data sources at run-time. However, this has a couple limitations:

• Does not work for non-tiled data sources (the data value is treated as a sin

The documentation for tangram-es 0.12.0 for all methods of MapChangeListener mentions that it is called on the UI thread. However, this is not always true.

✔️ It is incidentally called on the UI thread when the listener is called due to user interactions with the map, because the TouchInput responders are called on the UI thread by the Android system. It is not documented by Android to be c

• What did you see?

In tile 13/4146/2816:

In tile 14/8293/5633:

Note that the highlighted building ha

The src:geom_alt property values should always include all sources used to store alt geometries.
Crawl the repo to make sure all sources are catalogued and that the property contains no duplicate values.

We should reduce the number of simple but annoying translations that devs have to do when interacting with MapzenSearch/MapzenRouter/MapzenMap components

heya,

the demo link at the top of the github repo is pointing to an old URL:

I think the correct URL is https://generalpiston.github.io/react-autosuggest-geocoder/ ?

Right now, all commit messages for work done in Boundary Issues are something like:

Boundary Issues: saved [wof:name] - www-data

A useful feature would be the ability to add a commit message when saving a specific commit message to describe the edit that was completed.

File under polish... Turns out "all" the country features are translated to English, huzzah!

But looking at that page returns an error saying it doesn't know about the country placetype, when it's that there aren't any bad data matches to display.

https://whosonfirst.dev.mapzen.com/spelunker/placetypes/country/?&translations=!eng

While looking at a result like Spanish that is missing tr