Code Monkey home page Code Monkey logo

ess-dive-community / essdive-hydrologic-monitoring Goto Github PK

View Code? Open in Web Editor NEW
0.0 0.0 2.0 6.38 MB

READY TO USE. A reporting format intended for water level, temperature, electrical conductivity, specific conductance, dissolved oxygen, and pH measured in situ using sensors deployed in water bodies.

Home Page: https://ess-dive.gitbook.io/hydrologic-monitoring-data-and-metadata/

License: Creative Commons Attribution 4.0 International

data-standard hydrologic-monitoring reporting-format sensor water-level water-quality

essdive-hydrologic-monitoring's People

Contributors

aegoldman avatar

Watchers

 avatar  avatar  avatar  avatar

essdive-hydrologic-monitoring's Issues

Adding section to README file

I suggest the following changes:

I suggest that we add a new section to the README file which aligns with what some of the recently published RFs have on their page. It's a section that informs readers what updates were made between (for example) v1.0.0 and v1.0.1. For now, we can just have a placeholder like the one below. This can go below the 'getting started' section.


Updates in v1.0.0

This is the first release of the Hydrologic Monitoring Reporting Format reporting format.

Clarification: Depth and Elevation terms

  • Documentation reference (URL): https://github.com/ess-dive-community/essdive-hydrologic-monitoring/blob/main/HydroRF_Term_Guide.md#depth
  • Submitter: Danielle Christianson (LBNL)
  • Justification (why is this change necessary?): It takes some effort to figure out how the terms "Depth" and "Elevation" might work together and relate to the recommended vocabulary "Sensor_Depth" and "Sensor_Elevation". I'm assuming the following.
    • Per the definition of the term Elevation, it is the elevation of the sensor, not the elevation of a physical feature (e.g., ground surface).
    • Depth and/or Elevation should be used for permanently installed sensors that do not vary during the observation period, unless moved by the researcher or unforeseen events.
    • Sensor_Depth and Sensor_Elevation should be used when sensor vertical position is an observation, i.e., they are expected to vary during the observation period.

I suggest the following changes:

  • Give an example of reporting Depth and Elevation together. For example: assuming I understand the RF correct: if Depth = 1, Depth_Reference = meters below ground surface, Elevation = 1000, Elevation_Reference = meters above mean sea level (NAVD88), then the elevation of the ground surface = 1001 meters above mean sea level. A simple figure would be helpful to quickly communicate these relationships. There may be other examples relevant to hydrological observations that are also common / better suited.
  • Add guidance on when to use Depth v. Sensor_Depth and Elevation v. Sensor_Elevation.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.