Skip to content

Don't apply a default band filter to new layer frames#314

Open
annehaley wants to merge 1 commit intomasterfrom
no-default-source-filters
Open

Don't apply a default band filter to new layer frames#314
annehaley wants to merge 1 commit intomasterfrom
no-default-source-filters

Conversation

@annehaley
Copy link
Collaborator

When I ran a "create road network" task, I realized that the results were not visualizing properly. The layer would get added to the map, tile requests were sent and recieved correct responses, but nothing appeared on the map. I was able to hunt this down and discover that this was because the source_filters field on that LayerFrame had a value of {"band": 1}.

The "create road network" task does not use the dataset conversion process to create layers and frames. It creates all necessary objects within the task itself. When the LayerFrame object is created, no value is specified for source_filters. Rather than changing the task to specify that field on the frame, a more robust solution would be to change the model definition.

The LayerFrame model file defines a function default_source_filters which is called to populate the source_filters field when no value is specified. We shouldn't be returning this band filter by default, since that would only ever apply to multiband raster data. This PR changes that default value to an empty dictionary, such that no filters are applied by default.

@annehaley annehaley requested a review from BryonLewis March 5, 2026 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant