-
Notifications
You must be signed in to change notification settings - Fork 157
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.
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
[FEA] Support WKT? #110
Comments
Yes! I'm investigating this possibility as one of my next features. Thanks! |
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. |
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. |
This wasn't followed up on when we released it, but currently you can use GeoPandas for WKT input, then convert that directly to cuspatial with |
@voycey is this still of interest? If so, can you provide any information on how large the WKT datasets are? |
Hi Mark, Our WKT datasets were 200B point datasets X 140M polygons, upwards of 2TB of data each day |
@voycey With this scale of data, how often do you run into |
Very rarely, the majority of our work was simple polygons and points, it was rare that we had multiple polygons for a single item, I think its possible that others would use them but I also think its equally possible that many dont! |
All of our data is stored inside a data warehouse as text format WKT strings. This is very efficient for us as it means that we can directly process spatial data on both clusters and items like BigQuery, likewise it gives us agility in moving between different file formats (ORC, Parquet, CSV etc)
It would be great if we could directly read WKT strings into cuSpatial without having to convert to shapefiles as our data changes so often and the workflow to convert is cumbersome
The text was updated successfully, but these errors were encountered: