Skip to content
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.

Sign up for GitHub

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

Jump to bottom

unsafe_applyreduce using GI.getpoint or GI.gethole #89

Open
asinghvi17 opened this issue Apr 1, 2024 · 0 comments
Open

unsafe_applyreduce using GI.getpoint or GI.gethole #89

asinghvi17 opened this issue Apr 1, 2024 · 0 comments
Labels
enhancement New feature or request low priority Low priority issue, someone can get to it whenever they feel like it!

Comments

@asinghvi17
Copy link
Member

@rafaqz mentioned that GI.getpoint or GI.gethole on any geometry can be substantially faster in some cases (Shapefile.jl comes to mind). One can implement an unsafe_applyreduce, which does not guarantee any ordering, but still gives you the points or rings to operate on.

This would operate only on LinearRing, LineString, Point traits.
@asinghvi17 asinghvi17 added enhancement New feature or request low priority Low priority issue, someone can get to it whenever they feel like it! labels Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request low priority Low priority issue, someone can get to it whenever they feel like it!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@asinghvi17