[Bug] Filter layers by map draw control polygons issues

[leverglowh]

Describe the bug
Filtering layers inside a polygon (or rectangle) drawn with the map draw controls:

• Only one layer is selected: the selected layer is correctly filtered, other layers are affected, but randomly, as in some points are hidden, some are visible with no apparent pattern.
• Two or more layers are selected: the filter is broken on all layers, points disappear from inside the polygon too.

This also affects export data feature with "Filtered data" mode, which seems to just list what we see on map.
We were able to reproduce this on both demo environments, with our own data, and with demo data.

To Reproduce
Steps to reproduce the behavior:

1. Go to nytrips demo https://kepler.gl/demo/nyctrips (this is an example)
2. Draw a polygon on map, make sure it covers both layers (all points)
3. Right click and select filter layers, and select "pickup"
4. Notice that the un-selected layer "dropoff" was affected too
5. Now select "dropoff" too
6. Notice that it's hiding points both outside and inside the polygon

Expected behavior
When filtering one layer, the feature should only filter the selected layer, hiding all its points (or other shapes) outside the polygon and showing those inside the polygon, leaving other layers intact.
When filtering more layers, it should show shapes of the selected layers inside the drawn polygon, and hide those outside, leaving other layers intact.

Screenshots

filter.by.polygon.bug.mov

This is the nyctrips example, I only changed the dropoff color from blue to green.

Notice that when I select "pickup" which are red tiny dots, those are correctly filtered, but green circles somehow are affected as well, disappearing from both outside and inside the polygon, but not all of them.
When I then select both layers, most of the points disappear.

Desktop (please complete the following information):
Seems to be cross, below are what we tried and were able to reproduce in all:

• OS: macOS and Windows
• Browser: chrome, safari, firefox
• Version: at lease since 3.2.0, didn't try lower versions

Additional context
The issue is present also when layers are from different datasets.

[leverglowh]

Hey guys, just wanted to ask if we have an ETA for this

[leverglowh]

Hey guy, I had some time to test more on this bug, and was able to reproduce it in merely 10 rows of data (can do with maybe less but I didn't test further).
In the case of 2 layers of a single dataset, the error is reproducible always.
It also happens on layers of two different datasets but not always, so the root cause is still not clear..
I'll attach the exported json.

10 rows 2 pairs filter bug.json

[igorDykhta]

@leverglowh I'll check. Sorry for the delay.

[leverglowh]

Hey guys, very happy to see a PR on this.
Do we have an ETA on the 3.3 release? Just to have an idea, don't want to push 🙏

[igorDykhta]

I'll try to release the next alpha this week.
The fix above is still marked as "investigation needed", as it probably has side effects.