You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the sample data covers only a subdomain of the frame (say, land), it is sometimes desirable to avoid extending it too much into lakes and oceans. A solution is to add a cutoff distance (in "raster" pixels, like the blur option).
Left: random walk; right: random walk with a cutoff at 9px (and pixelSize: 0.5).
This can be done in user space with custom interpolators, but seems like a simple option to offer in interpolatorNearest (which would deprecate interpolateNearest), and interpolatorRandomWalk. (I haven't looked at interpolatorBarycentric yet.)
Code patch (to be optimized to avoid Math.hypot and skip unless cutoff is specified):
When the sample data covers only a subdomain of the frame (say, land), it is sometimes desirable to avoid extending it too much into lakes and oceans. A solution is to add a cutoff distance (in "raster" pixels, like the blur option).
Left: random walk; right: random walk with a cutoff at 9px (and pixelSize: 0.5).
This can be done in user space with custom interpolators, but seems like a simple option to offer in interpolatorNearest (which would deprecate interpolateNearest), and interpolatorRandomWalk. (I haven't looked at interpolatorBarycentric yet.)
Code patch (to be optimized to avoid Math.hypot and skip unless cutoff is specified):
Feature suggested by @HarryStevens
(Slightly related to a generic “clip” feature #1109 —but here we only have point samples, no geojson.)
The text was updated successfully, but these errors were encountered: