Open bwitham opened 5 years ago
Going to take a shot at this only for the sake of possibly speeding up the conflate run for roads from #3530. If nothing comes out of some short time spent on this, then will shelve it to backlog for the time being since doing this for all tree instances will take a significant amount of time.
The bottleneck in #3530 doesn't have to do with this indexing, so shelving.
Actually it might...
Going to take a look at this, since it is a bottleneck in some conflate scenarios. Not sure if tuning will help or not yet.
I believe alll the
HilbertRTree
indexing values have been based on a single trial run against a single dataset. Doing some more intensive testing and against a handful of datasets may end up helping overall runtime performance. Look for refs to this issue in code. For very large datasets, I've noticed for various conflation types where pulling surrounding features from the geospatial index is a performance bottleneck.