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
Thanks for creating a placeholder repo @ShashankBice
I think we need to explicitly mention "lidar" in this repo name. My vision here is to have a set of centralized airborne lidar processing workflows to generate standard products. The filtering and other procesing steps are important as well, and we might not actually want to produce grids for some applications, but just process or aggregate point clouds.
But I also think we can centralize some of the satellite lidar processing routines as well. these currently live in multiple repos, including asp_plot and coincident.
I wonder if something like "lidar_proc" or "lidar_gt" (gt = ground truth) would be more descriptive for the larger goals. @scottyhq
The text was updated successfully, but these errors were encountered:
I think we need to explicitly mention "lidar" in this repo name. My vision here is to have a set of centralized airborne lidar processing workflows to generate standard products.... I wonder if something like "lidar_proc" or "lidar_gt" (gt = ground truth) would be more descriptive for the larger goals.
Sounds good. I'd also suggest removing abbreviations. "lidar-processing" already exists. So maybe "lidar-tools",,, or "plydar" since it rolls off the tongue 😂
Thanks for creating a placeholder repo @ShashankBice
I think we need to explicitly mention "lidar" in this repo name. My vision here is to have a set of centralized airborne lidar processing workflows to generate standard products. The filtering and other procesing steps are important as well, and we might not actually want to produce grids for some applications, but just process or aggregate point clouds.
But I also think we can centralize some of the satellite lidar processing routines as well. these currently live in multiple repos, including asp_plot and coincident.
I wonder if something like "lidar_proc" or "lidar_gt" (gt = ground truth) would be more descriptive for the larger goals.
@scottyhq
The text was updated successfully, but these errors were encountered: