-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
interaction for labels #303
Comments
Would really like this. It solves two problems with featuresAt(): picking up labels that aren't really there (https://github.com/mapbox/mapbox-gl-online/issues/675), and not being able to grab labels that ARE there (https://github.com/mapbox/mapbox-gl-online/issues/374) |
@ansis how deep is this issue? Where would a contributor start if they wanted to add labels to the rtree? |
I think it might be sort of deep. The tricky thing is that labels have different sizes and different lengths along a line at different zoom levels.
And then a bunch of work to integrate the new |
Any chance this could move some time in the next couple months? Are there any ways to temporarily hack around the issue? It's a pretty big usability knock for direct selecting -> styling. Users always expect to be able to click on labels. |
for /app, one hack is to call |
fix #303 This increases worker memory usage by around 10% (a couple of MB). 1/3 of the increase comes from retaining the CollisionTile. 2/3 of the increase comes from retaining VectorTileFeatures.
fix #303 This increases worker memory usage by around 10% (a couple of MB). 1/3 of the increase comes from retaining the CollisionTile. 2/3 of the increase comes from retaining VectorTileFeatures.
fix #303 This increases worker memory usage by around 10% (a couple of MB). 1/3 of the increase comes from retaining the CollisionTile. 2/3 of the increase comes from retaining VectorTileFeatures.
fix #303 This increases worker memory usage by around 10% (a couple of MB). 1/3 of the increase comes from retaining the CollisionTile. 2/3 of the increase comes from retaining VectorTileFeatures.
fix #303 This increases worker memory usage by around 10% (a couple of MB). 1/3 of the increase comes from retaining the CollisionTile. 2/3 of the increase comes from retaining VectorTileFeatures.
fix #303 This increases worker memory usage by around 10% (a couple of MB). 1/3 of the increase comes from retaining the CollisionTile. 2/3 of the increase comes from retaining VectorTileFeatures.
fix #303 This increases worker memory usage by around 10% (a couple of MB). 1/3 of the increase comes from retaining the CollisionTile. 2/3 of the increase comes from retaining VectorTileFeatures.
fix #303 This increases worker memory usage by around 10% (a couple of MB). 1/3 of the increase comes from retaining the CollisionTile. 2/3 of the increase comes from retaining VectorTileFeatures.
fix #303 This increases worker memory usage by around 10% (a couple of MB). 1/3 of the increase comes from retaining the CollisionTile. 2/3 of the increase comes from retaining VectorTileFeatures.
map.featuresAt
should include labels. or have a separate call for it.The text was updated successfully, but these errors were encountered: