Skip to content

Conversation

@kylebarron
Copy link
Member

@kylebarron kylebarron commented Oct 26, 2025

The existing code was no longer working after #912 because we're passing Arrow Vectors into the accessor props instead of arrow.Data objects.

This PR fixes that by selecting a specific record batch of data to pass into each layer.

In geoarrow/deck.gl-layers#164 upstream, it should be easier to catch errors like this.

Closes #955

Copy link
Collaborator

@ATL2001 ATL2001 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

YES👏 I didn't pull this branch down but I did a copy/paste to get the relevant parts into my branch (which I'll discard so as to not cause commit issues) and it's all working again!

I figured it must have had something to do with the switch from the arrow table to the recordbatches, and now that I see what you're doing here, it makes a lot of sense why I wasn't able to find anywhere in deckgl-layers to do something like this.

@kylebarron kylebarron changed the title wip: Fix data filter extension with arrow prop fix: Restore DataFilterExtension functionality with vectorized accessor input Oct 27, 2025
@github-actions github-actions bot added the fix label Oct 27, 2025
@kylebarron kylebarron merged commit c0ae426 into main Oct 27, 2025
8 of 9 checks passed
@kylebarron kylebarron deleted the kyle/fix-filter-maybe branch October 27, 2025 03:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DataFilterExtension seems to be broken on main (may be on my end though...)

3 participants