Peter Liu

Yup, I'm seeing it again-- seems entirely sporadic. Reopened.

@mtirwin I actually haven't submitted (my bad), but the bug has disappeared for me again. Would you mind submitting, since you are still experiencing this?

@danswick I made something similar at https://www.mapbox.com/bites/00174/ -- feel free to appropriate bits and pieces as needed. is there some way to incorporate the [default geocoder](https://www.mapbox.com/mapbox.js/example/v1.0.0/geocoding-auto/) to get some typeahead...

I have a workflow that involves multiple worker passes to download data and generate the objects to visualize them. In this context, I'd like the workers to be as versatile...

>As mentioned, the only workaround is a complete anti-pattern and abuse of the library - introducing N layers for N styled features. @nickfaughey @eslavnov @dalbani There's actually another way to...

@averas I had the same question a few days back-- turns out we don't support transitions in DDS properties yet. Good feature enhancement down the road, though cc/ @lucaswoj

@carlosrovira right. in my understanding, the challenges of transitioning expression updates are similar to those for DDS updates in this thread so far. But as a user, I've found some...

@mariokam check out the roadmap [here](https://www.mapbox.com/mapbox-gl-js/roadmap/)

Another example, this time without visible holes. [Original:](https://gist.github.com/peterqliu/4e411ef9e562965535b5) `turf.buffer(fc, 0, 'miles')`: