GeometryOps and Rasters mean different things by `touches`

[asinghvi17]

GeometryOps touches means only boundary, Rasters Touches means GeometryOps intersects

[evetion]

Ops is correct here, although I'm not 100% what touches mean in terms of raster interaction? That's not in DE-9IM.

[rafaqz]

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.

[evetion]

But there's no exported function touches in Rasters right? Just a kwarg.

:boundary: for polygons, include pixels where the :center is inside the polygon, where the polygon :touches the pixel, or that are completely :inside the polygon. The default is :center.

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)?

[asinghvi17]

There's a Touches selector, which is the main concern

[asinghvi17]

This will be resolved eventually by DD switching to use DE9IM.jl