-
Notifications
You must be signed in to change notification settings - Fork 0
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
GeometryOps and Rasters mean different things by touches
#6
Comments
Ops is correct here, although I'm not 100% what touches mean in terms of raster interaction? That's not in DE-9IM. |
It comes from gdal and R use in rasterize etc where it means to include the pixels that touch the boundary as well as the other pixels, not exclusive of them. |
But there's no exported function touches in Rasters right? Just a kwarg.
I don't see this as a problem, but if you do, we could deprecate the kwargs for better names used in Ops? :touches becomes :intersects, and :inside becomes :within? :center could be :centroid if we're changing names anyway. PS. You could change this behavior depending on whether a pixel is a point (:center) or area (:touches or :inside)? |
There's a |
GeometryOps touches means only boundary, Rasters Touches means GeometryOps intersects
The text was updated successfully, but these errors were encountered: