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

Refactor IO to use laspy #15

Open
rmsare opened this issue Oct 4, 2019 · 0 comments
Open

Refactor IO to use laspy #15

rmsare opened this issue Oct 4, 2019 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@rmsare
Copy link
Collaborator

rmsare commented Oct 4, 2019

Right now, write_pdal and write_las use temporary files to save a numpy array as a LAS file. This is bad because

  • The temp file may be huge, and take a long time to write
  • This doesn't keep any spatial reference information

Instead, write_las should use laspy's File object,to write points and copy a header. This means that read_las should also use laspy, and return a header to copy.

@rmsare rmsare added enhancement New feature or request presubmission labels Oct 4, 2019
@rmsare rmsare self-assigned this Oct 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant