rapidsai / cuspatial

CUDA-accelerated GIS and spatiotemporal algorithms
https://docs.rapids.ai/api/cuspatial/stable/
Apache License 2.0
612 stars 154 forks source link

[DOC] geometry formats #241

Closed achapkowski closed 2 years ago

achapkowski commented 4 years ago

Report needed documentation A clear and concise description of what documentation you believe it is needed and why.

Where can I find documentation on the geometry format?

Describe the documentation you'd like A clear and concise description of what you want to happen.

If it doesn’t exist, provide samples of how geometries must be formatted for product interop.

Steps taken to search for needed documentation List any steps you have taken:

trxcllnt commented 4 years ago

Hi @achapkowski, this docstring includes an example of the format (and here's a visual).

The layout is roughly equivalent to a List of Lists of points:

If the polygons are not closed (as in the example), the start point is assumed to be the closing end point.

achapkowski commented 4 years ago

How do you handle holes?

zhangjianting commented 4 years ago

How do you handle holes?

https://www.esri.com/library/whitepapers/pdfs/shapefile.pdf

github-actions[bot] commented 3 years ago

This issue has been marked rotten due to no recent activity in the past 90d. 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.

github-actions[bot] commented 3 years ago

This issue has been marked stale due to no recent activity in the past 30d. 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 marked rotten if there is no activity in the next 60d.

harrism commented 2 years ago

we should improve the documentation of geometry formats.

achapkowski commented 2 years ago

Thank you, I would appreciate that.

github-actions[bot] commented 2 years ago

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.

harrism commented 2 years ago

@thomcom @isVoid is this covered by the recently merged Python doc PRs?

isVoid commented 2 years ago

Recent refactoring and documentation has made it clear that cuSpatial will adapt to GeoArrow format. This should be covered.