return visibility in featuresAt()

[edenh]

map.featuresAt() currently returns all layers for that point, even if they are not visible because of collisions. We should either not return hidden layers for those points or return with a visible: false key.

@ansis @jfirebaugh @mourner

[jfirebaugh]

Agreed. I think the default should be to omit hidden features, with an option to include them. Having the visibility available as a property on the resulting features is also a good idea.

[mcwhittemore]

Hidden features might be a thing people are using currently (intentionally or not) so providing the hidden attribute is the safest bet.

[steinbachr]

+1

[peterqliu]

+1 to a configurable option. having a featuresAt that matches visibility is useful when building interactivity with map elements. but when you're using the map as an interface to access the underlying dataset, retrieving the full data is useful

[musicformellons]

+1

[ansis]

featuresAt is replaced by queryRenderedFeatures and querySourceFeatures. queryRenderedFeatures only returns visible features. Symbols hidden because of collisions are not returned. querySourceFeatures can be used to get features independent of styling. I don't think we need an option for including hidden features right now.