Floating Lidar extension

[stephenholleran]

Purpose:
There are many competing floating lidar solutions on the market, each with their own metadata file format. Utilizing the WRA Data Model to standardize the floating lidar metadata that is used for wind resource assessments would be advantageous to all stakeholders involved. This meeting is to explore the possibilities of using the WRA Data Model to transfer metadata from floating lidar devices to consumers of the data.

Attendance:
SH (Brightwind), JF (NREL), VN (Fugro), GK (RWE), NS (RWE), AM (Eolos), DC (NRG Systems), AM (PNNL), RK (PNNL), CS (PNNL), MM (PNNL)

Agenda:

1. Intros
2. Quick intro to the data model
3. RWE's perspective - why it would be good for them
4. Open chat:
   1. VN: do have their own format. Customers haven't really requested specific formats. Met Ocean format is requested sometimes. Sending data from device to shore needs small packets for satellite transfer. ZPH is good for this. They get the data from the device and then package it up to send to the customer.
   2. MA: do have their own format, they have been asked for specific formats to fit into customers SCADA, have also provided JSON in the past.
   3. AM: the request to PNNL is usually about the maintenance events, reports, etc.
   4. MA: Wave, current, salinity, sea temp, biological activity, ........
   5. VA: Long trail of documentation throughout the whole process. Calibrations, through to validation process and then to installation. Setup would include QC filters.
   6. DC: get the history of the measurement point, not just the initial setup.
   7. AM: not all floating lidars are the same and all have their own differences. We would not want to leave out any floating lidar OEM.
   8. SH: we can include sensor other than just wind speed measurement.
   9. VN: Climate and Forecasting (CF) conventions. https://cfconventions.org/ This might align with this already.
   10. VN: a good endeavor, close the scope. Focus on what is important for wind resource assessment.
   11. MA: there is a lot of data, be flexible, difficult to take everything into account, future proof it.
   12. Everyone is in agreement that we should continue the conversation to determine what the scope could be.

Action:

• Send invite for 3 or 4 weeks time.

[stephenholleran]

Purpose:
There are many competing floating lidar solutions on the market, each with their own metadata file format. Utilizing the WRA Data Model to standardize the floating lidar metadata that is used for wind resource assessments would be advantageous to all stakeholders involved. This meeting is to explore the possibilities of using the WRA Data Model to transfer metadata from floating lidar devices to consumers of the data.

Objective of todays call:
Define a minimum scope that captures everything for a wind resource assessment.

Attendance:
SH (Brightwind), FK (Fugro), GK (RWE), NS (RWE), AM (Eolos), DC (NRG Systems), AM (PNNL), RK (PNNL), CS (PNNL), NS (Shell), JU (Shell)

Agenda:

1. Intros
2. Quick intro to the WRA Data Model
3. Open chat:
   1. CS POD data standards. (CS to provide more info) https://www.arm.gov/publications/programdocs/doe-sc-arm-15-004.pdf
   2. Instead of thinking what is needed for a wind resource assessment, use what is required in the classification process i.e. the environmental parameters that show some sensitivity on the measurements.
   3. What are the measurements from a floating lidar that are required for a wind resource assessment? This question changed to simply listing out everything that a floating lidar measures and then narrowing it down for the scope.

Scope:

1. Measurements that are captured:
   1. Wind speed from lidar
   2. Wind direction from lidar
   3. Vertical wind speed from lidar
   4. Wind speed from anemometer/sonic
   5. Wind direction from wind vane/3d-sonic
   6. Wave direction
   7. Wave height
   8. Wave spectra
   9. Wave period
   10. Current direction at various depths
   11. Current speed at various depths
   12. Sea level height (if height is the correct term?)
   13. Water temperature at various depths
   14. Sea surface air temperature
   15. Sea surface air pressure
   16. Sea surface relative humidity
   17. Precipitation
   18. Solar irradiation
   19. Sea bed water pressure (i.e. water column height)
   20. Salinity
   21. GPS (differential GPS)
   22. Compass
   23. IMU (Inertia Motion Unit) - roll, pitch, yaw, +more (heave, (may not be needed for wind resource assessment)

Action:

• CS: to provide sample file and link to of the Atmospheric Radiation Measurement [ARM] (https://www.arm.gov/data/work-with-arm-data/) standards.
• SH: send out new invite for 2 weeks time.

[stephenholleran]

From NS (Shell)

A few comments on the list of measurement parameters we complied last week.

• For air temperature, air pressure and relative don’t specify sea surface measurements (ie list “air temperature” not “sea surface air pressure”). I would not be surprised if some buoys start measuring temp/pressure/RH at multiple heights and the exact measurement height can be specified in the meta data (that’s the beauty of the data model)
• The current speed and current direction work will work very similar to lidar wind speed and direction, multiple heights with the specific heights driven by measurement need
• ‘Water level’ is the term I’ve read for sea bed water pressure/water column height

[stephenholleran]

Call on the 2022-03-03

Objective of todays call:
Define a minimum scope that captures everything for a wind resource assessment.

Attendance:
SH (Brightwind), GWM (Fraunhofer IWES), VN (Fugro), GK (RWE), AM (Eolos), AM (PNNL), NS (Shell), ST (EDF)

Agenda:

1. Quick intros
2. Review the list of measurements that a floating lidar captures.
3. Which ones are only used for wind resource assessments?
   1. Wave can impact on floating turbines in terms of which direction they face.
   2. Wave is used by wind resource teams in calculating O&M availability.
   3. In the below list everything up to and including 'waves'.
   4. The other measurements from the floating lidar are used in other departments such as loads and so we should try and capture as much as possible in the data model.
4. Do we include more in the scope? Yes, but we can split the work load.
5. What do we include? Work down through the list as it is ordered below.
6. Think about producing a matrix of use cases (for wind resource assessment or quality) and what measurements would be used for that use case.
7. Maybe think about what the minimum standard that should be provided by a floating lidar. This would be dependent on the use case and so it pretty much includes the whole list.

Scope:

1. Measurements that are captured:
   1. Wind speed from lidar (uncorrected, 10-min data from the lidar device. For the process of motion correcting, the raw lidar data is used.)
   2. Wind direction from lidar
   3. Motion corrected wind speed
   4. Motion corrected wind direction
   5. Vertical wind speed from lidar
   6. Lidar CNR
   7. Lidar Doppler Spectral Broadening
   8. Lidar Quality/
   9. Wind speed from anemometer/sonic
   10. Wind direction from wind vane/ 3d- sonic
   11. Sea level height (if height is the correct term? what is the reference?)
   12. Sea surface Air temperature (a height of 0 m would indicate at the sea surface)
   13. Sea surface Air pressure
   14. Sea surface Relative humidity
   15. GPS (differential GPS)
   16. Compass
   17. Precipitation
   18. Solar irradiation
   19. Wave direction
   20. Wave height
   21. Wave spectra
   22. Wave period
   23. IMU (Inertia Motion Unit) - roll, pitch, yaw, +more (heave, (may not be needed for wind resource assessment)
   24. Sea/ocean/water ? current direction at various depths (In CF conventions everything is "sea_water" and then "from_direction")
   25. Current speed at various depths
   26. Water temperature at various depths
   27. Sea bed water pressure (i.e. water column height) (Is "water level" more appropriate?)
   28. Water quality (pH, chlorophyll, dissolved O2, etc)
   29. Salinity
   30. Battery voltage/current
   31. Fuel levels
   32. Presence of X (animal identification / tagging)
   33. Radio telemetry
   34. Sound from a hydrophone/microphone

Action:

• SH to work through some of the new measurement types putting them into the data model for review in the next call.

[stephenholleran]

From AB:
Is motion corrected wind speed dependent on how the motion was corrected for?

[stephenholleran]

Call on the 2022-03-31

Objective of todays call:
Continue detailed discussions on how to implement measurements from a floating lidar into the WRA Data Model.

Attendance:
SH (Brightwind), GWM (Fraunhofer IWES), GK (RWE), DC (NRG), NS (Shell), CS (PNNL), JF (NREL), NS (RWE), AB (Altosphere)

Notes:

1. I have created a new issue [SCHEMA] expand for floating lidar #159 to track the implementation of floating lidar into the data model.
2. Reviewed the motion corrected variables:
   1. This pull request shows the motion corrected measurement types added. (The pull request will get updated as more commits are added.) Iss #159 implement floating lidar #160
   2. Added motion corrected vertical wind speed. It is not widely used but can be, so it should be available.
   3. The height reference for the datum plane should be from 'sea_level' and not 'mean_sea_level'. This 'sea_level' needs to be added to the 'height_reference'. Some people may still use mean sea level but the option should be there.
3. ZX has some extra data columns that should be captured. Such as quality "points in fit at 79m" for the 'M' version and 'back scatter'. Investigate what exactly these could be.
4. 'Sea Level' is mostly known as 'Water Level'. Usually measured with a pressure sensor which measure the water column above the sea bed. Can also be measured using an ADCP. Rename 'Sea level' to 'Water level'.
5. Differential GPS is a hardware technique to improve the GPS measurements.
6. 'Wave' values, significant wave height. Measured by an inertial device (optical) to measure the heave and inertia to then calculate the wave height and period. This is calculated in post-processing. We will need to add a new sensor type to cover this. TO BE CONTINUED..........

Scope:

1. Measurements that are captured:
   1. Wind speed from lidar (uncorrected, 10-min data from the lidar device. For the process of motion correcting, the raw lidar data is used.)
   2. Wind direction from lidar
   3. Vertical wind speed from lidar
   4. Motion corrected wind speed
   5. Motion corrected wind direction
   6. Motion corrected vertical wind speed
   7. Lidar CNR
   8. Lidar Doppler Spectral Broadening
   9. Lidar Quality
   10. Wind speed from anemometer/sonic
   11. Wind direction from wind vane/sonic
   12. Sea Water level height (measured from the sea bed)
   13. Air temperature (a height of 0 m would indicate at the sea surface)
   14. Air pressure
   15. Relative humidity
   16. GPS (differential GPS)
   17. Compass (usually measured using a GPS compass, can also be measured via a magnetic compass.)
   18. Precipitation
   19. Solar irradiation
   20. Wave direction
   21. Wave height
   22. Wave spectra
   23. Wave period
   24. IMU (Inertial Measurement Unit) - roll, pitch, yaw, +more (heave, (may not be needed for wind resource assessment)
   25. Sea/ocean/water ? current direction at various depths (In CF conventions everything is "sea_water" and then "from_direction")
   26. Current speed at various depths
   27. Water temperature at various depths
   28. Sea bed water pressure (i.e. water column height) (Is "water level" more appropriate?)
   29. Water quality (pH, chlorophyll, dissolved O2, etc)
   30. Salinity
   31. Battery voltage/current
   32. Fuel levels
   33. Presence of X (animal identification / tagging)
   34. Radio telemetry
   35. Sound from a hydrophone/microphone

Action:

• SH to continue to work through some of the new measurement types putting them into the data model for review in the next call.
• SH to add 'sea_level' to 'height_reference'.
• SH to add 'inertial_measurement_unit' to the sensor types.
• GVM to ask ZX about the different quality columns that come from the 'M' version.

[stephenholleran]

Call on the 2022-04-14

Attendance:
SH (Brightwind), NS (Shell), GK (RWE), ST (EDF), TG (Orsted)

Notes:

1. Issue [SCHEMA] expand for floating lidar #159 to help track the implementation of floating lidar into the data model.
2. Pull request Iss #159 implement floating lidar #160 to also help track the changes.
3. SH added 'sea_level' to 'height_reference'.
4. SH added 'inertial_measurement_unit' to the sensor types.
   1. What are the measurement types and units that come from an IMU? Is the raw IMU measurements or are processed measurements (e.g. wave height) provided. Lacking the expertise on the call to continue with this discussion.
5. Continuing from previous meeting regarding wave measurements:
   1. Previously.... 'Wave' values, significant wave height. Measured by an inertial device (optical) to measure the heave and inertia to then calculate the wave height and period. This is calculated in post-processing. We will need to add a new sensor type to cover this. TO BE CONTINUED..........
   2. From https://cdip.ucsd.edu/m/documents/wave_measurement.html There are two main types of sensors used to measure sea surface elevation, pressure sensors mounted on the sea bed and accelerometers in a buoy. To measure wave direction directional buoys are used which measure pitch and roll in addition to vertical heave.
   3. ADCPs (https://en.wikipedia.org/wiki/Acoustic_Doppler_current_profiler) can measure wave heights and direction but are they used in the wind industry for this? Lacking the expertise on the call to continue with this discussion.
   4. Should waves be called sea_surface_wave as in the CF Conventions? Yes, we should use what exists. Clarify with metocean people first though. Some floating lidar providers already do use these when supplying data.
   5. Significant wave height is provided for the 10-min period.
6. Skipping the rest of 'wave' and 'current' discussions as no floating lidar provider is on the call. Water temperature at various depths. Measured with thermometers that are either mounted on the mooring chain or a probe protruding from the bottom of the buoy. Can also be measured by an ADCP either mounted on the buoy or sea bed.
   1. From what reference is the temperature measured, a depth from sea level, mean sea level or a height from the sea bed?
   2. Should we define the reference height or allow the customer or floating lidar provider to use which ever they wish?

Scope:

1. Measurements that are captured:
   1. Wind speed from lidar (uncorrected, 10-min data from the lidar device. For the process of motion correcting, the raw lidar data is used.)
   2. Wind direction from lidar
   3. Vertical wind speed from lidar
   4. Motion corrected wind speed
   5. Motion corrected wind direction
   6. Motion corrected vertical wind speed
   7. Lidar CNR
   8. Lidar Doppler Spectral Broadening
   9. Lidar Quality
   10. Wind speed from anemometer/sonic
   11. Wind direction from wind vane/sonic
   12. Water level height (measured from the sea bed)
   13. Air temperature (a height of 0 m would indicate at the sea surface)
   14. Air pressure
   15. Relative humidity
   16. GPS
   17. Compass (usually measured using a GPS compass, can also be measured via a magnetic compass.)
   18. Precipitation
   19. Solar irradiation
   20. Wave direction
   21. Wave height
   22. Wave spectra
   23. Wave period
   24. IMU (Inertial Measurement Unit) - roll, pitch, yaw, +more (heave, (may not be needed for wind resource assessment)
   25. Sea/ocean/water ? current direction at various depths (In CF conventions everything is "sea_water" and then "from_direction")
   26. Current speed at various depths
   27. Water temperature at various depths
   28. Sea bed water pressure (i.e. water column height) (Is "water level" more appropriate?)
   29. Water quality (pH, chlorophyll, dissolved O2, etc)
   30. Salinity
   31. Battery voltage/current
   32. Fuel levels
   33. Presence of X (animal identification / tagging)
   34. Radio telemetry
   35. Sound from a hydrophone/microphone

Actions:

• SH to continue to work through some of the new measurement types putting them into the data model for review in the next call.
• SH Clean up the email list.
• ALL ask floating lidar providers to attend as we are really missing their expertise. GK to draft a letter from wind farm developers to floating lidar providers to outline that we are now working on wave data. Their expertise on IMUs, ADCPs, metocean data that we are missing and would appreciate their participation. Also what is the height reference for measuring sea temperature at various depths? Fugro, Eolos, Axys, RPS, Akrocean, Fraunhofer IWES, at least.
• GWM to ask ZX about the different quality columns that come from the 'M' version.

[stephenholleran]

Call on the 2022-04-28

Attendance:
SH (Brightwind), GK (RWE), GWM (Fraunhofer IWES), FK (Fugro), AG (brightwind), NS (RWE), ST (EDF)
Notes:

1. Issue [SCHEMA] expand for floating lidar #159 to help track the implementation of floating lidar into the data model.
2. Pull request Iss #159 implement floating lidar #160 to also help track the changes.
3. From last meeting; What are the measurement types and units that come from an IMU? Is the raw IMU measurements or are processed measurements (e.g. wave height) provided. Lacking the expertise on the call to continue with this discussion.
   1. From a conversation with JU (Shell) the IMU can measure 2 Hz however this is not transmitted and so not delivered to the client. It takes a minimum of 17 minutes of data to do the spectral analysis to work out wave info, so the wave info is usually provided as a 30-min rolling calculation provided every 10-min. As a first draft of this I think we should just account for the wave info and not the raw IMU data? In a similar vane that we don't deal with the raw lidar data. The 17 minutes is not an industry standard. The high resolution data is usually not provided, but is becoming more relevant especially in the context of the Crown Estate validation process. There may be 10-min IMU statistics that may be required by some clients. Maybe leave these out for now and come back with an enhancement. Stick with the wave info for now.
   2. wave_height: CF Conventions call it sea_surface_wave_significant_height, do we want to follow? We can chop the first part down to just 'wave'. Significant wave height (the mean value of the upper third) is the most common but also maximum. wave_significant_height, wave_maximum_height
   3. wave_direction: CF Convention sea_surface_wave_from_direction, do we want to follow? CF Conv have both 'from' and 'to'. From JU (Shell) from is used for waves. wave_direction can be used on it's own so long as it is clearly defined in the data model and linked to the definition in the CF Convention.
   4. wave_spectra: not provided in the 10-min data on a daily basis so we can drop this. Similar to the raw IMU and lidar data.
   5. wave_period: peak is the most commonly used (the period that contains most of the energy (needs clarifying)), there are lots more statistics for this but most just want the peak. Not in CF Conventions, suggesting to call it wave_peak_period.
4. Water temperature at various depths can be accounted for already. We just need to add sea_floor as another height reference? CF Conventions use 'sea_floor' and not 'sea_bed'. sea_floor is better as sea_bed as sea bed can mean deep in the sea bed whereas sea floor is more specific.
   1. The CF conventions call this sea_water_temperature. Do we want to use this and keep the sea part? No, drop the 'sea' part and just use water_temperature. Floating lidars could be deployed in the Great Lakes for example.

Scope:

1. Measurements that are captured:
   1. Wind speed from lidar (uncorrected, 10-min data from the lidar device. For the process of motion correcting, the raw lidar data is used.)
   2. Wind direction from lidar
   3. Vertical wind speed from lidar
   4. Motion corrected wind speed
   5. Motion corrected wind direction
   6. Motion corrected vertical wind speed
   7. Lidar CNR
   8. Lidar Doppler Spectral Broadening
   9. Lidar Quality
   10. Wind speed from anemometer/sonic
   11. Wind direction from wind vane/sonic
   12. Water level height (measured from the sea floor)
   13. Air temperature (a height of 0 m would indicate at the sea surface)
   14. Air pressure
   15. Relative humidity
   16. GPS
   17. Compass (usually measured using a GPS compass, can also be measured via a magnetic compass.)
   18. Precipitation
   19. Solar irradiation
   20. Wave direction
   21. Wave height
   22. Wave spectra (not provided in the 10-min data on a daily basis so drop this.)
   23. Wave period
   24. IMU (Inertial Measurement Unit) - roll, pitch, yaw, +more (heave, (may not be needed for wind resource assessment)
   25. Sea/ocean/water ? current direction at various depths (In CF conventions everything is "sea_water" and then "from_direction")
   26. Current speed at various depths
   27. Water temperature at various depths
   28. Sea bed water pressure (i.e. water column height) (Is "water level" more appropriate?)
   29. Water quality (pH, chlorophyll, dissolved O2, etc)
   30. Salinity
   31. Battery voltage/current
   32. Fuel levels
   33. Presence of X (animal identification / tagging)
   34. Radio telemetry
   35. Sound from a hydrophone/microphone

Actions:

• SH to continue to work through some of the new measurement types putting them into the data model for review in the next call.
• SH Clean up the email list.
• ALL ask floating lidar providers to attend as we are really missing their expertise. GK to draft a letter from wind farm developers to floating lidar providers to outline that we are now working on wave data. Their expertise on IMUs, ADCPs, metocean data that we are missing and would appreciate their participation. Also what is the height reference for measuring sea temperature at various depths? Fugro, Eolos, Axys, RPS, Akrocean, Fraunhofer IWES, at least. Email sent for feedback on the letter.
• GWM to ask ZX about the different quality columns that come from the 'M' version. Sent email, awaiting response.

[stephenholleran]

Call on the 2022-07-07

Attendance:
SH (Brightwind), GWM (Fraunhofer IWES), AG (Brightwind), PW (Vestas), JU (Shell), JF (NREL), MP (NRG Sys), ST (EDF)

Notes:

1. Issue [SCHEMA] expand for floating lidar #159 to help track the implementation of floating lidar into the data model.
2. Pull request Iss #159 implement floating lidar #160 to also help track the changes.
3. Update on open letter to floating lidar manufacturers from wind farm developers:
   1. Awaiting Taylor Greer's (Orsted) company name and address.
   2. Jason can invite instrument people from Orsted.
4. SH added water_temperature as discussed in the last meeting.
5. SH added the measurement unit for meter (m) so we can use it in wave heights.
6. SH in the process of adding wave_significant_height however, what is the height reference for this? We have to have something so options are:
   1. 'mean_sea_level'
   2. 'sea_level' Go with this. We can explain in a tutorial that it can be ignored for wave heights.
   3. 'lowest_astronomical_tide'
   4. other? E.g. 'wave_trough'
7. Would our wave_peak_period be the same as CF's sea_surface_wave_period_at_variance_spectral_density_maximum? Yes. Reference this in the description.
8. water_level would be the more appropriate name to call the column of water above the sea floor as it is independent of how it is measured.

Scope:

1. Measurements that are captured:
   1. Wind speed from lidar (uncorrected, 10-min data from the lidar device. For the process of motion correcting, the raw lidar data is used.)
   2. Wind direction from lidar
   3. Vertical wind speed from lidar
   4. Motion corrected wind speed
   5. Motion corrected wind direction
   6. Motion corrected vertical wind speed
   7. Lidar CNR
   8. Lidar Doppler Spectral Broadening
   9. Lidar Quality
   10. Wind speed from anemometer/sonic
   11. Wind direction from wind vane/sonic
   12. Water level height (measured from the sea floor)
   13. Air temperature (a height of 0 m would indicate at the sea surface)
   14. Air pressure
   15. Relative humidity
   16. GPS
   17. Compass (usually measured using a GPS compass, can also be measured via a magnetic compass.)
   18. Precipitation
   19. Solar irradiation
   20. Wave direction
   21. Wave height
   22. Wave period
   23. IMU (Inertial Measurement Unit) - roll, pitch, yaw, heave, +more, (leaving out for now, we can come back with an enhancement)
   24. Water current direction at various depths
   25. Current speed at various depths
   26. Water temperature at various depths
   27. Sea bed water pressure (i.e. water column height) (Is "water level" more appropriate?)
   28. Water quality (pH, chlorophyll, dissolved O2, etc)
   29. Salinity
   30. Battery voltage/current
   31. Fuel levels
   32. Presence of X (animal identification / tagging)
   33. Radio telemetry
   34. Sound from a hydrophone/microphone

Actions:

• SH to add 'sea_floor' to the height references.
• SH to add 'water_level'.
• SH to add 'wave_maximum_height'.
• SH to add 'wave_direction'.
• SH to add 'wave_peak_period'.
• SH Clean up the email list.
• ALL ask floating lidar providers to attend as we are really missing their expertise. GK to draft a letter from wind farm developers to floating lidar providers to outline that we are now working on wave data. Their expertise on IMUs, ADCPs, metocean data that we are missing and would appreciate their participation. Also what is the height reference for measuring sea temperature at various depths? Fugro, Eolos, Axys, RPS, Akrocean, Fraunhofer IWES, at least. Email sent for feedback on the letter. Awaiting Taylor Greer's info.
• GWM to ask ZX about the different quality columns that come from the 'M' version. Sent email, awaiting response. No additional quality flags from Scott (ZX).

[stephenholleran]

Call on the 2022-09-01

Reboot

Attendance:
SH (Brightwind), FK (Fugro), MW (BP), SW (ZX), WW (Fraunhofer IWES), RKC (Axys), JM (ZX), MBe (Akrocean), GK (RWE), JU (Shell), MBo (Axys), AB (Vaisala), AG (Brightwind). (13)

Agenda:

1. Welcome, "quick" intros.
2. Problem - many providers all with a different data format. Difficult for consumers of the data to deal with.
3. What is the WRA Data Model? https://github.com/IEA-Task-43/digital_wra_data_standard/wiki/Task-43-WRA-Data-Model---An-introduction
4. What we have done so far.
   1. Current active participants: RWE, Shell, Orsted, Atlantic Shores, Vattenfall, Fraunhofer IWES, Fugro, Eolos, NRG Systems, Vestas, NREL, PNNL, Altosphere, Brightwind.
   2. Completed(?) lidar specific measurements (e.g. motion corrected), wave measurements and water level, water temperature. Next up would be currents. See list below.
5. Objective: to get an agreement to develop this and adopt it.
   1. 9 of the participants (2 dropped off early) typed that they agree to contribute to this development.
   2. Bi-weekly calls were preferred.
   3. The commitment is to turn up and contribute within that 1 hour, no homework involved.

Notes:

1. Issue [SCHEMA] expand for floating lidar #159 to help track the implementation of floating lidar into the data model.
2. Pull request Iss #159 implement floating lidar #160 to also help track the changes.

Scope of variables to include:

1. Measurements that are captured:
   1. Wind speed from lidar (uncorrected, 10-min data from the lidar device. For the process of motion correcting, the raw lidar data is used.)
   2. Wind direction from lidar
   3. Vertical wind speed from lidar
   4. Motion corrected wind speed
   5. Motion corrected wind direction
   6. Motion corrected vertical wind speed
   7. Lidar CNR
   8. Lidar Doppler Spectral Broadening
   9. Lidar Quality
   10. Wind speed from anemometer/sonic
   11. Wind direction from wind vane/sonic
   12. Water level (height measured from the sea floor)
   13. Air temperature (a height of 0 m would indicate at the sea surface)
   14. Air pressure
   15. Relative humidity
   16. GPS
   17. Compass (usually measured using a GPS compass, can also be measured via a magnetic compass.)
   18. Precipitation
   19. Solar irradiation
   20. Wave direction
   21. Wave maximum height
   22. Wave peak period
   23. IMU (Inertial Measurement Unit) - roll, pitch, yaw, heave, +more, (leaving out for now, we can come back with an enhancement)
   24. Water current direction at various depths
   25. Current speed at various depths
   26. Water temperature at various depths
   27. Sea bed water pressure (i.e. water column height) (Is "water level" more appropriate?)) See above water level.
   28. Water quality (pH, chlorophyll, dissolved O2, etc)
   29. Salinity
   30. Battery voltage/current
   31. Fuel levels
   32. Presence of X (animal identification / tagging)
   33. Radio telemetry
   34. Sound from a hydrophone/microphone

Actions:

• [ ]

[stephenholleran]

Call on the 2022-09-15

Attendance:
SH (Brightwind), MS (ZX), SY (Vaisala), AG (Brightwind), SL (Axys), DS (Axys), JP (Axys), AC (Vaisala), FK (Fugro), JF (NREL), JM (ZX), GK (RWE), AB (Altosphere), PP (WISE Group)

Agenda:

1. Recap on last meeting.
2. Revisit the structure of the data model (if needed?) Recording of presentation from Feb about the structure.
3. Go back over what we have done so far. Any changes?
   1. No suggested changes.
   2. Added 'wave spreading' to the list.
   3. Explained a lot about the structure of the data model and how different use cases would work with the data model.
   4. Everyone seems happy with what we have completed so far. Next meeting (29th) can look at 'wave spreading' and 'currents'.
4. Currents next. Didn't get to this.
   1. Searching 'current' in the CF Conventions only had 1 hit.

Notes:

1. Issue [SCHEMA] expand for floating lidar #159 to help track the implementation of floating lidar into the data model.
2. Pull request Iss #159 implement floating lidar #160 to also help track the changes.

Scope of variables to include:

1. Measurements that are captured:
   1. Wind speed from lidar (uncorrected, 10-min data from the lidar device. For the process of motion correcting, the raw lidar data is used.)
   2. Wind direction from lidar
   3. Vertical wind speed from lidar
   4. Motion corrected wind speed
   5. Motion corrected wind direction
   6. Motion corrected vertical wind speed
   7. Lidar CNR
   8. Lidar Doppler Spectral Broadening
   9. Lidar Quality
   10. Wind speed from anemometer/sonic
   11. Wind direction from wind vane/sonic
   12. Water level (height measured from the sea floor)
   13. Air temperature (a height of 0 m would indicate at the sea surface)
   14. Air pressure
   15. Relative humidity
   16. GPS
   17. Compass (usually measured using a GPS compass, can also be measured via a magnetic compass.)
   18. Precipitation
   19. Solar irradiation
   20. Wave direction
   21. Wave maximum height
   22. Wave peak period
   23. Wave spreading
   24. IMU (Inertial Measurement Unit) - roll, pitch, yaw, heave, +more, (leaving out for now, we can come back with an enhancement)
   25. Water current direction at various depths
   26. Current speed at various depths
   27. Water temperature at various depths
   28. Sea bed water pressure (i.e. water column height) (Is "water level" more appropriate?)) See above water level.
   29. Water quality (pH, chlorophyll, dissolved O2, etc)
   30. Salinity
   31. Battery voltage/current
   32. Fuel levels
   33. Presence of X (animal identification / tagging)
   34. Radio telemetry
   35. Sound from a hydrophone/microphone

Actions:

• [ ]

[stephenholleran]

Call on the 2022-09-29

Attendance:
SH (Brightwind), DS (Axys), FK (Fugro), GWM (Fraunhofer IWES), AM (Eolos), SY (Vaisala), DC (NRG Sys)

Sticky Notes:

1. Intro to the structure of the data model, a recording of a presentation from Feb-2022.
2. Issue [SCHEMA] expand for floating lidar #159 to help track the implementation of floating lidar into the data model.
3. Pull request Iss #159 implement floating lidar #160 to also help track the changes.

Agenda:

1. Recap on last meeting.
2. 'Wave Spreading': This is the standard deviation of all the wave directions measured.
   1. In CF Conventions this is sea_surface_wave_directional_spread
   2. How is it measured? IMU
   3. What are the units? Degrees.
   4. Term to use is wave_directional_spread, similar to what we did with wave_direction in dropping the sea_surface.
   5. Should not generally exceed 90 degrees as it implies there is more than one sea state component.
   6. Keep the definition a bit generic as different providers calculate it slightly differently.
3. Currents next.
   1. Searching current in the CF Conventions only had 1 hit.
   2. They use sea_water and then either velocity, speed, direction, e.g. sea_water_velocity_from_direction. This is similar to sea_surface_wave_from_direction where we use wave_direction.
   3. Term? sea_water_speed, current_speed, water_speed? Decided on water_speed as current can be mixed up with electrical. In the definition state that it can also be known as current_speed.
      4. Units m/s.
   4. For direction the term would therefore be water_direction.
   5. Anything else to consider for water currents? No thoughts at this time.
4. Sensor used to measure water speed and direction is an ADCP.
   1. Usually mounted on the buoy, but could also be sea floor mounted.
   2. There could be motion corrected values.
   3. There can be mounting offsets to be applied i.e. the ADCP is mounted at a certain depth below the sea surface.
   4. The reference height can be mean sea level.
   5. Treat it as a sensor or similar to a lidar i.e. a logger?

Scope of variables to include:

1. Measurements that are captured:
   1. Wind speed from lidar (uncorrected, 10-min data from the lidar device. For the process of motion correcting, the raw lidar data is used.)
   2. Wind direction from lidar
   3. Vertical wind speed from lidar
   4. Motion corrected wind speed
   5. Motion corrected wind direction
   6. Motion corrected vertical wind speed
   7. Lidar CNR
   8. Lidar Doppler Spectral Broadening
   9. Lidar Quality
   10. Wind speed from anemometer/sonic
   11. Wind direction from wind vane/sonic
   12. Water level (height measured from the sea floor)
   13. Air temperature (a height of 0 m would indicate at the sea surface)
   14. Air pressure
   15. Relative humidity
   16. GPS
   17. Compass (usually measured using a GPS compass, can also be measured via a magnetic compass.)
   18. Precipitation
   19. Solar irradiation
   20. Wave direction
   21. Wave maximum height
   22. Wave peak period
   23. Wave spreading
   24. IMU (Inertial Measurement Unit) - roll, pitch, yaw, heave, +more, (leaving out for now, we can come back with an enhancement)
   25. Water current direction at various depths
   26. Current speed at various depths
   27. Water temperature at various depths
   28. Sea bed water pressure (i.e. water column height) (Is "water level" more appropriate?)) See above water level.
   29. Water quality (pH, chlorophyll, dissolved O2, etc)
   30. Salinity
   31. Battery voltage/current
   32. Fuel levels
   33. Presence of X (animal identification / tagging)
   34. Radio telemetry
   35. Sound from a hydrophone/microphone

Actions:

• SH: Add in wave_directional_spread. Review at the next meeting.
• SH: Add in water_speed. Review at the next meeting.
• SH: Add in water_direction. Review at the next meeting.
• SH: Prepared for ADCPs.

[stephenholleran]

Call on the 2022-10-13

Attendance:
SH (Brightwind), AG (Brightwind), MS (ZX), SW (Greenrebel), GWM (Fraunhofer IWES), SL (Axys), FK (Fugro), JU (Shell), AM (Eolos), SY (Vaisala), RKC (Axys), PW (Vestas), GK (RWE).

Sticky Notes:

1. Intro to the structure of the data model, a recording of a presentation from Feb-2022.
2. Issue [SCHEMA] expand for floating lidar #159 to help track the implementation of floating lidar into the data model.
3. Pull request Iss #159 implement floating lidar #160 to also help track the changes.

Agenda:

1. Recap on last meeting.
2. Review new additions.
   1. No changes.
3. ADCPs.
   1. From previous meeting:
      1. Usually mounted on the buoy, but could also be sea floor mounted.
      2. There could be motion corrected values.
      3. There can be mounting offsets to be applied i.e. the ADCP is mounted at a certain depth below the sea surface.
      4. The reference height can be mean sea level.
      5. Treat it as a sensor or similar to a lidar i.e. a logger? No conclusion.
   2. Treat it as a sensor or similar to a lidar i.e. a logger?
      1. Allow the flexibility by allowing it to be a logger.
      2. Is it pointing up or down, facing the sea_floor or sea_level. 'vertical_orientation' with 'upward' or 'downward'. 'is_orientated_to_sea_floor' true/false. 'vertical_orientation' works.
      3. Assumed speed of sound setting. It does have an impact. Is it a setting that a user can change? Bring back up in the next meeting.
   3. Vertical water speed? I believe if there is a central beam on the ADCP it can measure the vertical speed.
      1. We should include it.
      2. The term should be 'vertical_water_speed'.
   4. Echo intensity? It can be used to judge quality. It can also be used for turbidity (the amount of suspended sediment in the water column.) This might be useful to include therefore we should include it. Term to use 'echo_intensity'.
   5. Signal to noise ratio is a measure of quality. More unlikely to be used in design. Term to use: 'signal_to_noise_ratio'.

Scope of variables to include:

1. Measurements that are captured:
   1. Wind speed from lidar (uncorrected, 10-min data from the lidar device. For the process of motion correcting, the raw lidar data is used.)
   2. Wind direction from lidar
   3. Vertical wind speed from lidar
   4. Motion corrected wind speed
   5. Motion corrected wind direction
   6. Motion corrected vertical wind speed
   7. Lidar CNR
   8. Lidar Doppler Spectral Broadening
   9. Lidar Quality
   10. Wind speed from anemometer/sonic
   11. Wind direction from wind vane/sonic
   12. Water level (height measured from the sea floor)
   13. Air temperature (a height of 0 m would indicate at the sea surface)
   14. Air pressure
   15. Relative humidity
   16. GPS
   17. Compass (usually measured using a GPS compass, can also be measured via a magnetic compass.)
   18. Precipitation
   19. Solar irradiation
   20. Wave direction
   21. Wave maximum height
   22. Wave peak period
   23. Wave directional spreading
   24. IMU (Inertial Measurement Unit) - roll, pitch, yaw, heave, +more, (leaving out for now, we can come back with an enhancement)
   25. Water direction at various depths
   26. Water speed at various depths
   27. Vertical water speed
   28. Water temperature at various depths
   29. Sea bed water pressure (i.e. water column height) (Is "water level" more appropriate?)) See above water level.
   30. Water quality (pH, chlorophyll, dissolved O2, etc)
   31. Salinity
   32. Battery voltage/current
   33. Fuel levels
   34. Presence of X (animal identification / tagging)
   35. Radio telemetry
   36. Sound from a hydrophone/microphone

Actions:

• SH: For an ADCP add 'vertical_orientation' to the vertical profiler properties.
• ALL: To consider if speed of sound should be included if it is a setting.
• SH: Add 'vertical_water_speed' measurement type.
• SH: Add 'echo_intensity' measurement type.
• SH: Add 'signal_to_noise_ratio' measurement type.

[stephenholleran]

Call on the 2022-10-27

Attendance:
SH (Brightwind), JP (Axys), LR (Akrocean), NS (Shell), MB (Akrocean), AG (Brightwind), SL (Axys), FK (Fugro), BM (Akrocean), AB (Altosphere).

Sticky Notes:

1. Intro to the structure of the data model, a recording of a presentation from Feb-2022.
2. Issue [SCHEMA] expand for floating lidar #159 to help track the implementation of floating lidar into the data model.
3. Pull request Iss #159 implement floating lidar #160 to also help track the changes.

Agenda:

1. Quick intros.
2. Recap on last meeting.
3. Review new additions.
   1. List of ADCP OEMs? Nortek, Teledyne RDI, AANDERAA
   2. Additional from last week's actions is to add ADCP to the list of sensor_types.
   3. Units of echo intensity? Need to look up.
4. Should speed of sound be included? Leave out for now. It will be easy to add in the future if it is needed.
5. Water quality - is not standard. Leave out for now.
6. Salinity - relevant for foundation design. We should include. Can be at different depths. Most likely a measurement of conductivity of the water. Units are ppt (parts per thousand). CF conventions: 'sea_water_salinity', go with 'water_salinity'. CF conventions also have sea_water_practical_salinity. Action is to implement and clarify the difference.

Scope of variables to include:

1. Measurements that are captured:
   1. Wind speed from lidar (uncorrected, 10-min data from the lidar device. For the process of motion correcting, the raw lidar data is used.)
   2. Wind direction from lidar
   3. Vertical wind speed from lidar
   4. Motion corrected wind speed
   5. Motion corrected wind direction
   6. Motion corrected vertical wind speed
   7. Lidar CNR
   8. Lidar Doppler Spectral Broadening
   9. Lidar Quality
   10. Wind speed from anemometer/sonic
   11. Wind direction from wind vane/sonic
   12. Water level (height measured from the sea floor)
   13. Air temperature (a height of 0 m would indicate at the sea surface)
   14. Air pressure
   15. Relative humidity
   16. GPS
   17. Compass (usually measured using a GPS compass, can also be measured via a magnetic compass.)
   18. Precipitation
   19. Solar irradiation
   20. Wave direction
   21. Wave maximum height
   22. Wave peak period
   23. Wave directional spreading
   24. IMU (Inertial Measurement Unit) - roll, pitch, yaw, heave, +more, (leaving out for now, we can come back with an enhancement)
   25. Water direction at various depths
   26. Water speed at various depths
   27. Vertical water speed
   28. Water temperature at various depths
   29. Sea bed water pressure (i.e. water column height) (Is "water level" more appropriate?)) See above water level.
   30. Echo Intensity
   31. Signal to Noise Ratio
   32. Water quality (pH, chlorophyll, dissolved O2, etc) (not standard so leave it for an enhancement)
   33. Salinity
   34. Battery voltage/current
   35. Fuel levels
   36. Presence of X (animal identification / tagging)
   37. Radio telemetry
   38. Sound from a hydrophone/microphone

Actions:

• SH: Add CF convention of [upward_sea_water_velocity] to vertical water speed.
• SH: Update example to use the Signaure250 ADCP.
• SH: Add ADCP OEMs to list.
• SH: Add salinity to the measurement types. May also need a new sensor.
• ALL: Come back confirming that echo intensity units are decibels.

[stephenholleran]

Call on the 2022-11-10

Attendance:
SH (Brightwind), JP (Axys), LR (Akrocean), FK (Fugro), AG (Brightwind), MM (RWE), SL (Axys).

Sticky Notes:

1. Intro to the structure of the data model, a recording of a presentation from Feb-2022.
2. Issue [SCHEMA] expand for floating lidar #159 to help track the implementation of floating lidar into the data model.
3. Pull request Iss #159 implement floating lidar #160 to also help track the changes.

Agenda:

1. Quick intros.
2. Recap on last meeting.
3. Review new additions.
   1. Salinity is commonly known as the salt content of water. Other mediums prequalify the word salinity e.g. "soil salinity". Therefore I think it is ok to simply use the word "salinity" on it's own for our use as we are always referring to water. Is this ok? Yes.
      1. Practical Salinity Units (PSU) is just one scale to measure salinity and it depends on the method of measurement (conductivity, compared to the conductance of a standard potassium chloride solution). These are dimensionless. Even though it is formally incorrect and discouraged to add PSU as a unit after the value, if floating lidar providers add PSU after the value then we should add it? Ok to add PSU after the value.
      2. Other units to measure salinity are grams of salt per liter of water (g/L) or grams of salt per kilogram of water (g/kg) which is dimensionless and is otherwise know as parts per thousand (ppt).
      3. "Reference composition salinity scale" is more of an absolute salinity measurement using Thermodynamic Equation Of Seawater 2010 (TEOS-10) where it's units are g/kg or ppt.
   2. Conductivity Temperature Depth (Pressure) (CTD) sensor.
      1. Conductivity, units Siemens per meter (S/m).
      2. Pressure, units dbar.
4. Battery voltage and current already covered. Not really useful for the client.
5. Fuel levels? Some providers rely on liquid fuels. No real use case for the attendees but it was agreed that adding the unit Liter (L) would be useful. Not sure if fuel level would be measured by any other metric.
6. Environmental monitoring can be left out for now and added to future releases as required. This would include 'Presence of X (animal identification / tagging)', 'Radio telemetry' and 'Sound from a hydrophone/microphone' from the list below.

Scope of variables to include:

1. Measurements that are captured:
   1. Wind speed from lidar (uncorrected, 10-min data from the lidar device. For the process of motion correcting, the raw lidar data is used.)
   2. Wind direction from lidar
   3. Vertical wind speed from lidar
   4. Motion corrected wind speed
   5. Motion corrected wind direction
   6. Motion corrected vertical wind speed
   7. Lidar CNR
   8. Lidar Doppler Spectral Broadening
   9. Lidar Quality
   10. Wind speed from anemometer/sonic
   11. Wind direction from wind vane/sonic
   12. Water level (height measured from the sea floor)
   13. Air temperature (a height of 0 m would indicate at the sea surface)
   14. Air pressure
   15. Relative humidity
   16. GPS
   17. Compass (usually measured using a GPS compass, can also be measured via a magnetic compass.)
   18. Precipitation
   19. Solar irradiation
   20. Wave direction
   21. Wave maximum height
   22. Wave peak period
   23. Wave directional spreading
   24. IMU (Inertial Measurement Unit) - roll, pitch, yaw, heave, +more, (leaving out for now, we can come back with an enhancement)
   25. Water direction at various depths
   26. Water speed at various depths
   27. Vertical water speed
   28. Water temperature at various depths
   29. Sea bed water pressure (i.e. water column height) (Is "water level" more appropriate?)) See above water level.
   30. Echo Intensity
   31. Signal to Noise Ratio
   32. Water quality (pH, chlorophyll, dissolved O2, etc) (not standard so leave it for an enhancement)
   33. Salinity
   34. Battery voltage/current
   35. Fuel levels
   36. Presence of X (animal identification / tagging)
   37. Radio telemetry
   38. Sound from a hydrophone/microphone

Actions:

• SH: Add PSU as a unit.
• SH: Add measurement unit L.
• SH: Clean up the last bits, send email asking to review and inform everyone we will reviewing it on the next call.

[stephenholleran]

Call on the 2022-12-08

Attendance:
SH (Brightwind), LR (Akrocean), AG (Brightwind), SY (Vaisala), AM (Eolos), JF (NREL), AB (Altosphere).

Sticky Notes:

1. Intro to the structure of the data model, a recording of a presentation from Feb-2022.
2. Issue [SCHEMA] expand for floating lidar #159 to help track the implementation of floating lidar into the data model.
3. Pull request Iss #159 implement floating lidar #160 to also help track the changes.

Agenda:

1. Quick intros.
2. Recap on last meeting.
3. Review new additions.
   1. Added 'PSU' as a unit for Salinity.
   2. Added Pressure measurement type.
   3. Added 'L' as a unit.
   4. Added 'height' and 'depth' as measurement types.
   5. Cleaned up the example implementation.
4. Final review:
   1. AM's comment on the pull request; should we have more generic wave parameters 'wave_height' and 'wave_period' in addition to 'wave_significant_height' and 'wave_peak_period'? Yes, we think this is a good thing to do.
   2. Step through example json.
   3. Approve? Unanimous approval to release subject to generic 'wave_height' and 'wave_period' added.
5. Next steps?
   1. Do a new release along with other changes to the Task 43 WRA Data Model. Version 1.2.
   2. Dissemination. LinkedIn post.
   3. Take an open public dataset and create a data model for it. NYSERDA dataset could be a good one to use. E05 and E06. E06 had lidar replacement. https://oswbuoysny.resourcepanorama.dnvgl.com/download/f67d14ad-07ab-4652-16d2-08d71f257da1 Create an issue to work on this. AB to lead. Other possible datasets might be listed here https://groups.io/g/wrag/wiki/13236

Actions:

• SH: Update ChangeLog.
• SH: Add in generic 'wave_height' and 'wave_period'.
• AB: To lead on implementing for NYSERDA E06.

[stephenholleran]

Call on the 2023-02-02

Attendance:
SH (Brightwind), NS (Shell), AM (Eolos), SY (Vaisala), CB (Vaisala), JF (NREL), AB (Altosphere), AG (Brightwind)

Sticky Notes:

1. Intro to the structure of the data model, a recording of a presentation from Feb-2022.

Agenda:

1. Quick intros.
2. Recap on last meeting.
3. Update on producing an example implemented WRA Data Model formatted file for an open dataset.
   1. AB creating a blog to show NYSERDA or other dataset as an example in the WRA Data Model format and hoping to show some sort of a visualization of the configuration.
   2. Aiming for end of Feb.
   3. AM offers to help.
4. Adoption?
   1. Are you going to adopt it and how might you adopt it? Produce converters to convert the metadata contained in a daily data file into a WRA Data Model formatted file?
      1. AM going to provide the file as part of the installation and any maintenance events.
      2. Supply chain workshop, draft contract language, upstream processes, tooling. Workshop with stakeholders to explain, demonstrate (NYSERDA data), case studies, understand user needs, how to get help or report an issue. Focus would be on offshore mostly.
      3. We think it is a good thing to do.
      4. Training material was highlighted previously as a need. These can be major part of a workshop content.
      5. Don't need to tag onto an in-person event but we should submit abstracts.
      6. Event options are WESC (Glasgow, 23-26 May), WindEurope Tech Workshop (Lyon, 1-2 June), American Clean Power WRA (Austin, 14-15 Nov). Also in June 12-16th, the wider Task 43 group get together in Colorado where we could have a session.
   2. Find out if any contract language exists from developers.
5. Next call?
   1. Keep the call in 2 weeks to discuss AB blog.

Actions:

• SH: Ask around if any contract language exists that could be used.
• AB: Have a skeletal blog post ready for the next call to get feedback from the group.

[stephenholleran]

Call on the 2023-02-16

Attendance:
SH (Brightwind), FK (Fugro), CB (Vaisala), SY (Akrocean), LR (Akrocean), SW (GreenRebel), AG (Brightwind), JU (Shell), AB (Altosphere)

Sticky Notes:

1. Intro to the structure of the data model, a recording of a presentation from Feb-2022.

Agenda:

1. Quick intros.
2. Recap on last meeting.
3. AB update on blog using NYSERDA data.
   1. Amit explained the background for the blog.
   2. What use cases could be used to demonstrate the data model for floating lidar?
      1. A device swap would be the most likely.
      2. A change in orientation or heading is a config change.
      3. The window height can be changed.
      4. For offshore a heading source could change e.g. GPS compass fails there are alternatives that can be used to adjust the wind direction data. Can be captured in 'notes'.
      5. Mooring failures and the buoy drifting off station.
   3. The NYSERDA data has a device swap out. It uses the ZX lidar. It would be good if we were able to have examples for both WindCube as well as ZX. CB shared 2 links to possible open options.
   4. SY suggested another use case is to show the time saved from not having to sift through loads of pdf to get the config changes.
4. Possible workshop update.
   1. As this floating lidar group and the main group are both focusing on dissemination, it makes sense to amalgamate.
   2. Yes. There was no reason not to do this. It would bring some new motivation to the main group.
   3. Keep this Thursday. Cancel both meetings and create a new one.

Actions:

• SH: create new meeting invite.

[stephenholleran]

This meeting has now ended as the main work for expanding the WRA Data Model to accommodate floating lidar has been completed. Further meeting notes will be captured in the General meeting notes. #129