Skip to content
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

Open
voycey opened this issue Dec 31, 2019 · 8 comments
Open

[FEA] Support WKT? #110

voycey opened this issue Dec 31, 2019 · 8 comments
Labels
feature request New feature or request

Comments

@voycey
Copy link

voycey commented Dec 31, 2019

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

@voycey voycey added Needs Triage Need team to review and classify feature request New feature or request labels Dec 31, 2019
@thomcom
Copy link
Contributor

thomcom commented Jan 2, 2020

Yes! I'm investigating this possibility as one of my next features. Thanks!

@github-actions
Copy link

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.

@github-actions github-actions bot added the stale label Feb 16, 2021
@github-actions
Copy link

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.

@thomcom
Copy link
Contributor

thomcom commented Dec 1, 2022

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 cuspatial.from_geopandas(geopandas_dataframe).

@harrism
Copy link
Member

harrism commented Feb 21, 2023

@voycey is this still of interest? If so, can you provide any information on how large the WKT datasets are?

@voycey
Copy link
Author

voycey commented Feb 22, 2023

Hi Mark,
Whilst I'm not actively working on Geospatial stuff right now I still don't think I would store things any differently nowadays. WKT can be stored directly in PostGIS and BigQuery for example as WKT in a Geometry or Geography field type.
Not having to convert between formats would make CuSpatial a really nice options to work on our data.

Our WKT datasets were 200B point datasets X 140M polygons, upwards of 2TB of data each day

@isVoid
Copy link
Contributor

isVoid commented Feb 22, 2023

@voycey With this scale of data, how often do you run into GeometryCollection data type in your dataset?
https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry

@voycey
Copy link
Author

voycey commented Feb 22, 2023

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!

@jarmak-nv jarmak-nv removed the Needs Triage Need team to review and classify label Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
Status: Todo
Development

No branches or pull requests

5 participants