BADM Group Overview
BADM variables in this group are organized as shown below. The overview highlights what variables are required per group. It also indicates which variables cannot be specified together ( OR ) in the same group entry. See BADM Basics for more details.
Multiple entries of this BADM group can be reported per site. However, combinations of Ⓒ variables must be unique. Read more:
| Required | Optional | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Instrument Pairing Information |
BADM variables: Definitions, Units, Requirements
See Overview tab or BADM Basics for explanation of Required and Optional variables.
Multiple entries of this BADM group can be reported per site. However, combinations of Ⓒ variables must be unique. Read more:
| Variable Requirements | Units | Description |
|---|---|---|
| INSTPAIR_MODEL_1Required | LIST(INST_MODEL) Show | Manufacturer and/or model, or type of instrument Select from the LIST INST_MODEL the most precise definition of the sensor used. If it is not available in the list, please contact the regional network for support and evaluate the addition of a new code. |
| INSTPAIR_SN_1Ⓒ Required | free text | Serial number or other unique text string used to identify this instrument Report the serial number of the sensor in order to identify it in the future and relate it to the measured and submitted variable. If the sensor doesn't have a serial number, a number can be assigned by the PI and kept linked univocally to the sensor. A PI assigned S/N should start with either the site code or an acronym related to the institution (e.g. LBNL12345). It must be unique across the entire network. |
| INSTPAIR_MODEL_2Required | LIST(INST_MODEL) Show | Manufacturer and/or model, or type of instrument Select from the LIST INST_MODEL the most precise definition of the sensor used. If it is not available in the list, please contact the regional network for support and evaluate the addition of a new code. |
| INSTPAIR_SN_2Ⓒ Required | free text | Serial number or other unique text string used to identify this instrument Report the serial number of the sensor in order to identify it in the future and relate it to the measured and submitted variable. If the sensor doesn't have a serial number, a number can be assigned by the PI and kept linked univocally to the sensor. A PI assigned S/N should start with either the site code or an acronym related to the institution (e.g. LBNL12345). It must be unique across the entire network. |
| INSTPAIR_DATEⒸ Required | YYYYMMDDHHMM | Instrument pair date |
| INSTPAIR_DATE_UNCOptional | days | Uncertainty in the Instrument pair date |
| INSTPAIR_COMMENTOptional | free text | Instrument pair comments |
| INSTPAIR_HEIGHT_SEPRequired | m | The vertical separation between the instrument pair (negative values: instrument 2 is above instrument 1) Report the vertical separation between a pair of instruments used together to produce a variable. For example, report vertical separation between a sonic anemometer and gas analyzer used to produce the variable FC (CO2 flux). |
| INSTPAIR_EASTWARD_SEPRequired | m | The E-W separation between the instrument pair (negative values: instrument 2 is west of instrument 1) Report the east-west distance between a pair of instruments used together to produce a variable as measured via GPS, tape and compass, or other method. Use magnetic north as a reference. For example, report E-W separation between a sonic anemometer and gas analyzer used to produce the variable FC (CO2 flux). |
| INSTPAIR_NORTHWARD_SEPRequired | m | The N-S separation between the instrument pair (negative values: instrument 2 is south of instrument 1) Report the north-south distance between a pair of instruments used together to produce a variable as measured via GPS, tape and compass, or other method. Use magnetic north as a reference. For example, report N-S separation between a sonic anemometer and gas analyzer used to produce the variable FC (CO2 flux). |
BADM Examples
Choose a variable marked with to show examples of how to submit and interpret these BADM. See BADM Basics for more details.
Combinations of Ⓒ variables must be unique. Read more: .
| Instrument Pairing Information |
DATE and DATE_UNC
DATE
Many groups require DATE to describe the time period that the metadata or ancillary data represents.
Dates should be entered at the precision known and most suitable to the observation. Supported precision include year, month, day, and minute in ISO formats: YYYY, YYYYMM, YYYYMMDD, YYYYMMDDHHMM.
Typical resolutions used for DATE are year, month, or day: YYYY, YYYYMM, YYYYMMDD.
DATE_UNC
Uncertainty in the DATE is an optional variable that can also be reported.
Report a date uncertainty that is commensurate with the DATE reported. For example if a day is reported for the DATE, date uncertainty should be on the order of days rather than months or years. If a year is reported for the DATE, date uncertainty should be greater than a year.
Customize and Download CSV for BADM Submission
After selecting your desired variables, download the customized CSV file for submission of BADM. For additional submission details, see BADM Submission Instructions. See BADM Basics for general BADM details.
Multiple entries of this BADM group can be reported per site. However, combinations of Ⓒ variables must be unique. Read more: . See BADM Basics for more details.
| Required | Optional | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
Submit completed CSV file at Upload Data using the BADM option (login required).