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

use more efficient spatial index #385

Closed
geoHeil opened this issue Sep 14, 2019 · 4 comments
Closed

use more efficient spatial index #385

geoHeil opened this issue Sep 14, 2019 · 4 comments

Comments

@geoHeil
Copy link

geoHeil commented Sep 14, 2019

Currently, geospark is based on the jts.STRTree. prestodb/presto#13079 could be a great enhancement regarding memory pressure, i.e. implementing it using Hilbert Packed RTree (Flatbush)
@kaushikCanada
Copy link

what happenned to this?

@AntonPeniaziev
Copy link
Contributor

@jiayuasu , should it be added to JTSplus?

@AntonPeniaziev
Copy link
Contributor

@geoHeil , could you please elaborate on methods to perform benchmark testing for memory footprint? I still barely understand what are Flatbush pros over the STRTree and which kind of data could show it

@geoHeil
Copy link
Author

geoHeil commented Feb 25, 2020

I think prestodb/presto#13079 has a good introduction. But for myself I am also not the expert here. I just heard of this and thought it could be really useful in geospark as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@geoHeil @jiayuasu @AntonPeniaziev @kaushikCanada