Closed dlebauer closed 7 years ago
@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 I will work on the rest of the steps and update here
What about the other metadata? Have you looked into the OGC specifications? On Tue, Apr 4, 2017 at 1:51 PM Solmaz Hajmohammadi notifications@github.com wrote:
Bounding box representation depends on Issue 44 https://github.com/terraref/reference-data/issues/44
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/terraref/computing-pipeline/issues/257#issuecomment-291596805, 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 double checked with Max, we are using version 1.5 However, the ply files are still in pointcloud origin. I have updated the issue 44, in order to do the transformation. This would georeference the LAS files.
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