Closed loriabendroth closed 2 years ago
The NAL website offers the following CSVs
Filename | In Database | Available for Download |
---|---|---|
mngt_tillage_data.csv | :heavy_check_mark: | :heavy_check_mark: |
mngt_notes_data.csv | :heavy_check_mark: | :heavy_check_mark: |
mngt_residue_data.csv | :heavy_check_mark: | :heavy_check_mark: |
mngt_fertilizing_data.csv | :heavy_check_mark: | :heavy_check_mark: |
mngt_harvesting_data.csv | :heavy_check_mark: | :heavy_check_mark: |
mngt_planting_data.csv | :heavy_check_mark: | :heavy_check_mark: |
mngt_irrigation_data.csv | :heavy_check_mark: | :heavy_check_mark: |
mngt_dwm_data.csv | :heavy_check_mark: | :heavy_check_mark: |
weather_data.csv | :heavy_check_mark: | :heavy_check_mark: |
soil_properties_data.csv | :heavy_check_mark: | :heavy_check_mark: |
soil_moisture_data.csv | :heavy_check_mark: | :heavy_check_mark: |
agronomic_data_0.csv | :heavy_check_mark: | :heavy_check_mark: |
irrigation_data.csv | :heavy_check_mark: | :heavy_check_mark: |
water_stage_data.csv | :heavy_check_mark: | :heavy_check_mark: |
water_table_data.csv | :heavy_check_mark: | :heavy_check_mark: |
water_quality_data.csv | :heavy_check_mark: | :heavy_check_mark: |
drain_flow_and_N_loads_data_0.csv | :heavy_check_mark: | :heavy_check_mark: |
meta_methods.csv | :heavy_check_mark: | :heavy_check_mark: |
meta_treatment_identifier.csv | :heavy_check_mark: | :heavy_check_mark: |
meta_plot_characteristics.csv | :heavy_check_mark: | :heavy_check_mark: |
meta_site_characteristics_0.csv | :heavy_check_mark: | :heavy_check_mark: |
data_dictionary_5.csv | :heavy_check_mark: | :heavy_check_mark: |
@akrherz , can you bring the missing ones into the drainagedata.org interface? The checklist is very helpful - thanks
@akrherz , for the missing data, put: https://datateam.agron.iastate.edu/td/dl/#tab_data
unrelated, but:
This leaves one file -> irrigation data.
To me, this seems like mngt metadata, but @giorgichi made it research data in how the file is named. To me, it seems like it should go with other irrigation metadata. Gio, how do you recommend we handle this in the interface?
Irrigation data can be treated as daily precipitation data.
The onsite precip data is not part of the data download tab. It is under the weather tab. Are you saying that we should have weather data as export tab within the download function?
For reference the mngt_irrigation_data
table has 771 rows and the irrigation_data
table has 752. Both of which could easily fit in the data export interface. I would prefer to do it there.
@akrherz , yes, go ahead and include the irrigation data with the other farm management records. So this will be included as long as the checkbox is checked for Field Operations Data under Management and Metadata tab.
@loriabendroth so I have done mngt_irrigation_data
with incoming change not yet deployed. Does the other irrigation_data
table need to be done as well as a separate tab?
@akrherz , yes, best to keep as a separate tab because at USDA NAL, they are two different csvs.
@loriabendroth done, I called this tab "Irrigation 2" without any guidance for something more appropriate.
@akrherz , for the data that is "mngt_irrigation_data.csv" - have the tab named "Irrigation_Event-Based" and for the other, name it "Irrigation_Daily"
@loriabendroth , this should be done, but I did not use underscores nor dashes as spaces are no technical issue for this.
@akrherz and @giorgichi , during the meeting, it was discussed that people were not possibly getting the authoritative source of data... or they were confused where to find it.