Anshul Singhvi
Anshul Singhvi
I forgot where the issue was, but this is also a point towards the transform_func being able to intercept and transform things at the geometry level.
@rafaqz is this ready to merge into the geometry lookup branch from your end?
Yea that works too
> At gets the centroid/representative point, and Contains or whatever checks if the point is in the area. I don't know about that....it seems pretty useless, the representative point must...
> DE19MPredicates.jl That would be nice...but would conflict with GeometryOps operations when we add those. Plus Rasters has Touches which is not DE9IM touches...
> Haha then we can select with geometries omg We already can ;) > are there types in GO No but there will be. And they have to subtype `GOCore.Operation`....
The problem there is again the names will clash But I don't mind putting func defs there that we specify can only be overloaded by types that the defining package...
> But like, with all the predicates even on a regular raster what does that mean? If I say Intersects(geom), then it can only give me either the bbox or...
I think we're thinking of two different objects. I'm thinking of the GO Operations interface, i.e. ```julia abstract type GeometricPredicate
Is it printing in a compressed way or not really?