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.

Sign up for GitHub

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

Jump to bottom

Add a PointCloud subclass of Vector to consistently deal with points? #463

Open
rhugonnet opened this issue Jan 31, 2024 · 0 comments · May be fixed by #492
Open

Add a PointCloud subclass of Vector to consistently deal with points? #463

rhugonnet opened this issue Jan 31, 2024 · 0 comments · May be fixed by #492
Labels
new-feature A new functionality / feature or request priority

Comments

@rhugonnet
Copy link
Contributor

Every type of point data (tuple of lists, list of tuples, array, geodataframe, etc) could be converted consistently into a geodataframe of only points that could fit into a PointCloud() subclass of Vector?

It could be the default input/output of:

  • Raster.to_points(),
  • Raster.interp_points(),
  • Raster.value_at_coords(),
  • etc...

And serve to have an ElevationPointCloud class in xDEM: GlacioHack/xdem#463
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
new-feature A new functionality / feature or request priority
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add PointCloud subclass of Vector rhugonnet/geoutils
1 participant
@rhugonnet