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

Deployment metadata #7

Open
AndyClifton opened this issue Nov 19, 2020 · 1 comment
Open

Deployment metadata #7

AndyClifton opened this issue Nov 19, 2020 · 1 comment

Comments

@AndyClifton
Copy link
Member

We need to include the language used to describe a lidar deployment in the glossary.

This may be captured partly in the e-WindLidar approaches or the Campaign Planning Tool.

This would help us align with IEA Wind Task 43's efforts to generate a metadata schema (see e.g. IEA-Task-43/digital_wra_data_standard#36)

@kersting
Copy link

@AndyClifton As the IEA task 43 data schema becomes more mature and some organizations are moving towards implementation, we realized that the terms height above ground level and height above datum plane may be abstract for installers even though they may be clear to analysts. I tried to look for some images in the internet that would help installers to understand the difference and I didn’t find anything that clearly showed the difference. Given that this is a problem that affects the entire industry, I wanted to bring to your attention and brainstorm a solution perhaps on this subtask. I think that a visual aid of an image, animation, or video on YouTube could help because installers see the world with different eyes of those processing the metadata. Many of the lidar installation errors are related to the fact that platform or trailers have not been taken into account before setting up the lidar heights. Please let me know your thoughts and we can think of some ideas to achieve that.

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

2 participants