[FEA] Update cuspatial notebook to remove 31 polygon limitation workaround

[taureandyernv]

Is your feature request related to a problem? Please describe.
Previously, cuSpatial was limited to processing 31 polygons at a time. according to @thomcom , @trxcllnt and @cwharris did a great job removing this limitation. Now our notebook, https://github.com/rapidsai/cuspatial/blob/branch-0.18/notebooks/nyc_taxi_years_correlation.ipynb, needs to reflect that. The work around used needs to be removed.

Describe the solution you'd like
update notebook

[zhangjianting]

I think the "old" point-in-polygon test API is still useful when the number of polygons is small for two reasons: 1) no need for indexing on points which could be both convenient and efficient. 2) For applications such as Video Analytics in Intelligent Transportation (ITS), the solution is a perfect match, as the number of polygons (Region of Interests) at an intersection is smaller than 32, i.e., sizeof(uint32_t). Point data may come in a stream mode which makes it difficult to index. This actually was the motivation to develop this point-in-polygon test API two years ago.
Instead of removing this API, I would suggest making better documentation and give users a choice.
@taureandyernv @thomcom , @trxcllnt and @cwharris

[thomcom]

@taureandyernv how about we rename the old pip to point_in_polygon_bitmap and the new one to point_in_polygon_quadtree and update the docs, instead of deprecating like we worked on last week?

[taureandyernv]

sure, @thomcom . Shall we put a notice on each of them that tells the user to use pip_bitmap (pip_bm) for small numbers of polygons and pip_qt for larger ones? Thanks for that great explanation @zhangjianting.

[github-actions]

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

[thomcom]

How has this one resolved @taureandyernv ?

[github-actions]

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

[github-actions]

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

[harrism]

To summarize, there are two PIP APIs: the non-indexed one which is limited to 31 polygons, and the indexed (quadtree) spatial join, which is limited only to the size representable using the index integer type.

We could update the notebook to use the latter. however as @zhangjianting points out the former is still useful when the overhead of building an index is not desirable.

[github-actions]

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.