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

Repo name discussion #2

Open
dshean opened this issue Jan 16, 2025 · 2 comments
Open

Repo name discussion #2

dshean opened this issue Jan 16, 2025 · 2 comments

Comments

@dshean
Copy link
Member

dshean commented Jan 16, 2025

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

@scottyhq
Copy link
Member

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 😂

@ShashankBice
Copy link
Member

Like both lidar-tools and plydar. I thought of using lidar_proc as well 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants