Volodymyr Agafonkin
Volodymyr Agafonkin
Sorry for the late response — this PR is on our mind and we'll look at it closer after we're done with the current v3.3 release. 🙏
Yeah, that looks bad... Might be something in the way we handle geometry, but might be good to confirm whether it's related to Draco or not by reencoding the model...
Ah, I see you've already tried it with #13106. Will investigate what's going on there...
This is likely a browser bug. `mapboxgl.clearStorage()` simply deletes the app cache, but doing so through DevTools would do the same. Not sure if there's anything we can do on...
There's no way to make a "line heatmap" the same way the point heatmap works at the moment. What you could try to get a similar look is overlaying all...
This was fixed on the geojson-vt side, but now ids [don't survive the transfer](https://github.com/mapbox/mapbox-gl-js/pull/2888#issuecomment-233482084) through `vt-pbf`. We'll probably want to switch to something like Geobuf.
@lucaswoj we could do this, but this feels kinda hacky and fragile to me (e.g. what if the data has both `id` and a property `$id`?). It might be good...
@anandthakker thanks! I was referring to the vector-tile-spec limitation of having ids as uints which John pointed out in the PR, so the original issue would still be present as...
@danzel is it only reproducible on Chrome, and not on other browsers like Firefox, Safari, IE?
OK, if we don't figure this out, lets just sacrifice having the dragging hand cursor outside of the map view, and set the dragging class on map container. I think...