-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPU Aggregation (8/8): Remove legacy aggregator #9100
Conversation
54f40a2
to
9829760
Compare
3471468
to
11cee24
Compare
11cee24
to
91be89f
Compare
If GPUGridLayer has never worked in the v9.x lifecycle then perhaps that isn't needed? But keeping CPUGridLayer as an alias of GridLayer would be a nice backward-compatibility approach I think. |
I also think removing it seems reasonable. Probably not the most common layer, and easy enough for affected users to update. |
I think it is reasonable to remove the old layers, it is straightforward for users to rename the layer |
For #7457
For discussion: there is no more CPUGridLayer/GPUGridLayer, simply
GridLayer
. Should we keep the old layer exports with thegpuAggregation
flag preset?This affects the carto module @donmccurdy @felixpalmer
Change List
AggregationLayer
into the heatmap-layer directory.HeatmapLayer
is the only remaining layer using it, and we are planning a rewrite.