-
Notifications
You must be signed in to change notification settings - Fork 13
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
Updates to standardize LAS format / metadata #257
Comments
@solmazhajmohammadi we can follow up about this - we should be able to implement this to existing extractor. |
@solmazhajmohammadi - please provide an update/next steps |
Bounding box depends on Issue 44 |
What about the other metadata? Have you looked into the OGC specifications?
…On Tue, Apr 4, 2017 at 1:51 PM Solmaz Hajmohammadi ***@***.***> wrote:
Bounding box representation depends on Issue 44
<terraref/reference-data#44>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#257 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAcX527Gq1erniJ97XwSieQ6h9_qeJa8ks5rspEegaJpZM4L3qvD>
.
|
@solmazhajmohammadi can this be closed? |
@solmazhajmohammadi - @max-zilla needs to know if anything needs to be changed with extractor before the code freeze on Aug 15 |
The LAS files are in standard format as long as we are using the PDAL version >1.3 |
LAS files should follow OGC las 1.4 standard
Goal is for (raster, point cloud) files to differ where it is useful, but have similar interfaces where applicable.
Are all x,y,z units in m relative to the gantry origin?
Description
Completion Criteria
The text was updated successfully, but these errors were encountered: