You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our team is working on a large-scale project that involves capturing and managing trillions of LiDAR data points from urban scans worldwide. Currently, we use .LAZ files to store this data in Earth-Centered, Earth-Fixed (ECEF) coordinates, with each point having attributes such as return number, intensity, classification, etc. We are exploring GeoWave as a solution for distributed storage and efficient querying of this data.
From the documentation, it seems a custom data adapter is necessary for 3D data handling, but I have a few key questions:
Achieving Millimeter Precision
For our detailed urban models, global millimeter precision is essential. In .LAZ files, ECEF coordinates provide this precision seamlessly. Would GeoWave support this precision effectively if we stay with ECEF, or would lat/lon/alt coordinates be preferable? If lat/lon/alt, we would require a significant number of decimal places for 1mm global precision.
Unified Dataset Structure
We aim to manage all LiDAR data as a single dataset for analytical tasks, not as separate GeoWave datasets per .LAZ file. Could you provide guidance on configuring GeoWave and choosing an optimal data store to handle this?
Creating a Custom Data Adapter
Could you provide advice or point to resources on building a custom adapter for 3D data, especially with high precision and additional attributes?
Thank you for your help and any recommendations you can provide to us!
The text was updated successfully, but these errors were encountered:
Hello GeoWave Team,
Our team is working on a large-scale project that involves capturing and managing trillions of LiDAR data points from urban scans worldwide. Currently, we use .LAZ files to store this data in Earth-Centered, Earth-Fixed (ECEF) coordinates, with each point having attributes such as return number, intensity, classification, etc. We are exploring GeoWave as a solution for distributed storage and efficient querying of this data.
From the documentation, it seems a custom data adapter is necessary for 3D data handling, but I have a few key questions:
For our detailed urban models, global millimeter precision is essential. In .LAZ files, ECEF coordinates provide this precision seamlessly. Would GeoWave support this precision effectively if we stay with ECEF, or would lat/lon/alt coordinates be preferable? If lat/lon/alt, we would require a significant number of decimal places for 1mm global precision.
We aim to manage all LiDAR data as a single dataset for analytical tasks, not as separate GeoWave datasets per .LAZ file. Could you provide guidance on configuring GeoWave and choosing an optimal data store to handle this?
Could you provide advice or point to resources on building a custom adapter for 3D data, especially with high precision and additional attributes?
Thank you for your help and any recommendations you can provide to us!
The text was updated successfully, but these errors were encountered: