queryRenderedFeatures and layer visibility

[ansis]

Does queryRenderedFeatures return features if their layer's visibility is none?
Should it return features if that's the case?

[mourner]

Maybe make this an option of queryRenderedFeatures? hidden: true, turned off by default, which would also include features with 0 opacity, and otherwise exclude.

[jfirebaugh]

Non-visible layers are, by definition, not rendered. Therefore they shouldn't be returned by queryRenderedFeatures.

[mourner]

The main use case would probably be something like #2400. If we never return hidden features, there's just no workaround for this.

[mcwhittemore]

queryRenderedFeatures reminds me a lot of ray-picking and would thus not return things that don't make up what is seen by the user. It sounds like 'querySourceFeatures' should have a geospatial param.

We talked about this a bit on #2106

[roelvanhintum]

I ran into this same problem, as a workaround i've set circle-opacity to 0.01. It's enough to make it invisible. This works for now, but a nicer solution would be welcome.

[jordandudley]

Should the interactive property of layers have any effect on the results of queryRenderedFeatures? I apologize if this is considered too far off topic.

[jfirebaugh]

Closing per #2402 (comment).

@jordandudley The introduction of queryRenderedFeatures obsoleted the interactive property. The code no longer uses it in any way.