We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This could reduce ecosystem name clashes
The text was updated successfully, but these errors were encountered:
That makes sense, let's make sure they are all the same though!
Sorry, something went wrong.
Actually nevermind...we'd have to pirate these lines
https://github.com/rafaqz/Extents.jl/blob/ced3c5fa4c1761e6138e661a74acc6c8a72c5f9f/src/Extents.jl#L142-L146
and we can't depend on GeoInterface in Extents, because it's circular...
So maybe we need a GeometricPredicateFunctionStubs.jl package that just has these function stubs, and then Extents can override them for its own use.
Yeah but maybe we should remove those methods anyway as only GI.extent reliably works on geometries. It all needs a rethink at some point
No branches or pull requests
This could reduce ecosystem name clashes
The text was updated successfully, but these errors were encountered: