DOC: add a guide on spatial indexing #3498
Conversation
There was a problem hiding this comment.
Thanks for working on this @martinfleis ; overall this looks great. I added some text suggestions to consider.
Is there a way to avoid the Out[33]: <Axes: > in the rendered code outputs? (looking at readthedocs output here)
I spent some time playing with it while writing this with no solution. The only one we could opt for is switching RST for ipynb and let nbsphinx parse it. Then it will consider the whole cell as one |
| Note that for many operations where a spatial index provides significant | ||
| performance benefits, GeoPandas already uses it automatically (like :meth:`~GeoDataFrame.sjoin`, | ||
| :meth:`~GeoDataFrame.overlay`, or :meth:`~GeoDataFrame.clip`). However, more advanced use cases may require | ||
| a direct interaction with the index. |
There was a problem hiding this comment.
Maybe we could mention the many-to-many case up front as an example of a situation where direct interaction makes sense?
There was a problem hiding this comment.
Not sure I follow what you meant...
What the title says. Adding it to Advanced guide as basic stuff can be done without interacting with the sindex ever via sjoin and friends.