The Bronson Files, Dataset 1, Field 17, 2012
Department of Agriculture
@usgov.usda_gov_the_bronson_files_dataset_1_field_17_2012_0c1e5
Department of Agriculture
@usgov.usda_gov_the_bronson_files_dataset_1_field_17_2012_0c1e5
Dr. Kevin Bronson provides this unique nitrogen and water management in cotton agricultural research dataset for compute, including notation of field events and operations, an intermediate analysis mega-table of correlated and calculated parameters generated during the experimentation, high resolution plot level data intermediate analysis tables, plus SAS process output intermediate tables, as well as the complete raw sensor recorded outputs.
This data was collected during the beginning time period of our USDA Maricopa terrestrial proximal high-throughput plant phenotyping tri-metric method generation, where a 5Hz crop canopy height, temperature and spectral signature are recorded coincident to indicate a plant health status. In this early development period, our Proximal Sensing Cart Mark1 (PSCM1) platform supplants people carrying the CropCircle (CC) sensors, and with an improved view mechanical performance result.
See included README file for operational details and further description of the measured data signals.
Summary: Active optical proximal cotton canopy sensing spatial data and including additional related metrics such as thermal are presented. Agronomic nitrogen and irrigation management related field operations are listed. Unique research experimentation intermediate analysis table is made available, along with raw data. The raw data recordings, and annotated table outputs with calculated VIs are made available. Plot polygon coordinate designations allow a re-intersection spatial analysis. Data was collected in the 2012 season at Maricopa Agricultural Center, Arizona, USA. High throughput proximal plant phenotyping via electronic sampling and data processing method approach is exampled. Acquired data using USDA Maricopa first mobile platforms, such as the Proximal Sensing Cart Mark 1, and via people. SAS and GIS compute processing output tables, including Excel formatted examples are presented, where data tabulation and analysis is available. The weekly proximal sensing data collected include canopy reflectance at six wavelengths, ultrasonic distance sensing of canopy height, and infrared thermometry. Lint and seed yields, first open boll biomass, and nitrogen uptake were also determined. Soil profile nitrate to 1.8 m depth was determined in 30-cm increments, before planting and after harvest. Nitrous oxide emissions were determined 20 or more weeks in the season with 1-L vented chambers (samples taken at 0, 12, and 24 minutes). Nitrous oxide was determined by gas chromatography (electron detection detector).
Organization: Department of Agriculture
Last updated: 2024-03-30T12:21:28.736238
Tags: agroecosystems-environment-weather-and-climate, ars, data-gov, earth-science-agriculture-soils-nitrogen, earth-science-biosphere-vegetation-plant-phenology, field-based-high-throughput-phenotyping, np211, plant-phenotyping
CREATE TABLE cs_gps (
"timestamp" TIMESTAMP,
"record" BIGINT,
"latitude_a" BIGINT,
"latitude_b" DOUBLE,
"longitude_a" BIGINT,
"longitude_b" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"magnetic_variation" DOUBLE,
"fix_quality" BIGINT,
"nmbr_satellites" BIGINT,
"altitude" DOUBLE,
"pps" BIGINT,
"dt_since_gprmc" DOUBLE,
"gps_ready" BIGINT,
"max_clock_change" BIGINT,
"nmbr_clock_change" BIGINT
);CREATE TABLE f17_2012_plot_corner_point_coordinates_0 (
"point_x" DOUBLE,
"point_y" DOUBLE,
"id" BIGINT,
"treat" BIGINT,
"rep" BIGINT,
"treat_name" VARCHAR,
"gas" VARCHAR,
"neutron" VARCHAR,
"n_rate" DOUBLE,
"orig_fid" BIGINT
);CREATE TABLE n_2012_05_18_hs_data (
"longitude" DOUBLE,
"latitude" DOUBLE,
"elevation" DOUBLE,
"fix_type" BIGINT,
"utc_time" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"sensor" BIGINT,
"vi1" DOUBLE,
"vi2" DOUBLE,
"r1" DOUBLE,
"r2" DOUBLE,
"r3" DOUBLE
);CREATE TABLE n_2012_05_29_hs_data (
"longitude" DOUBLE,
"latitude" DOUBLE,
"elevation" DOUBLE,
"fix_type" BIGINT,
"utc_time" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"sensor" BIGINT,
"vi1" DOUBLE,
"vi2" DOUBLE,
"r1" DOUBLE,
"r2" DOUBLE,
"r3" DOUBLE
);CREATE TABLE n_2012_06_04_hs_data (
"longitude" DOUBLE,
"latitude" DOUBLE,
"elevation" DOUBLE,
"fix_type" BIGINT,
"utc_time" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"sensor" BIGINT,
"vi1" DOUBLE,
"vi2" DOUBLE,
"r1" DOUBLE,
"r2" DOUBLE,
"r3" DOUBLE
);CREATE TABLE n_2012_06_12_hs_data (
"longitude" DOUBLE,
"latitude" DOUBLE,
"elevation" DOUBLE,
"fix_type" BIGINT,
"utc_time" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"sensor" BIGINT,
"vi1" DOUBLE,
"vi2" DOUBLE,
"r1" DOUBLE,
"r2" DOUBLE,
"r3" DOUBLE
);CREATE TABLE n_2012_06_13_hs_data (
"longitude" DOUBLE,
"latitude" DOUBLE,
"elevation" DOUBLE,
"fix_type" BIGINT,
"utc_time" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"sensor" BIGINT,
"vi1" VARCHAR,
"vi2" VARCHAR,
"r1" VARCHAR,
"r2" VARCHAR,
"r3" VARCHAR
);CREATE TABLE n_2012_06_19_hs_data (
"longitude" DOUBLE,
"latitude" DOUBLE,
"elevation" DOUBLE,
"fix_type" BIGINT,
"utc_time" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"sensor" BIGINT,
"vi1" VARCHAR,
"vi2" VARCHAR,
"r1" VARCHAR,
"r2" VARCHAR,
"r3" VARCHAR
);CREATE TABLE n_2012_06_22_hs_data (
"longitude" DOUBLE,
"latitude" DOUBLE,
"elevation" DOUBLE,
"fix_type" BIGINT,
"utc_time" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"sensor" BIGINT,
"vi1" DOUBLE,
"vi2" DOUBLE,
"r1" DOUBLE,
"r2" DOUBLE,
"r3" DOUBLE
);CREATE TABLE n_2012_06_25_hs_data (
"longitude" DOUBLE,
"latitude" DOUBLE,
"elevation" DOUBLE,
"fix_type" BIGINT,
"utc_time" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"sensor" BIGINT,
"vi1" DOUBLE,
"vi2" DOUBLE,
"r1" DOUBLE,
"r2" DOUBLE,
"r3" DOUBLE
);CREATE TABLE n_2012_07_02_cs_data (
"timestamp" TIMESTAMP,
"record" BIGINT,
"batt_volt_min" DOUBLE,
"ptemp" DOUBLE,
"airtemp" DOUBLE,
"targtemp_1022" DOUBLE,
"targtemp_1023" DOUBLE,
"targtemp_1052" DOUBLE,
"sbtemp_1022" DOUBLE,
"sbtemp_1023" DOUBLE,
"sbtemp_1052" DOUBLE,
"tmv_1022" DOUBLE,
"tmv_1023" DOUBLE,
"tmv_1052" DOUBLE,
"sonicv" DOUBLE,
"dist_inches" BIGINT
);CREATE TABLE n_2012_07_02_hs_data (
"longitude" DOUBLE,
"latitude" DOUBLE,
"elevation" DOUBLE,
"fix_type" BIGINT,
"utc_time" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"sensor" BIGINT,
"vi1" DOUBLE,
"vi2" DOUBLE,
"r1" DOUBLE,
"r2" DOUBLE,
"r3" DOUBLE
);CREATE TABLE n_2012_07_09_hs_data (
"longitude" DOUBLE,
"latitude" DOUBLE,
"elevation" DOUBLE,
"fix_type" BIGINT,
"utc_time" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"sensor" BIGINT,
"vi1" VARCHAR,
"vi2" VARCHAR,
"r1" VARCHAR,
"r2" VARCHAR,
"r3" VARCHAR
);CREATE TABLE n_2012_07_18_hs_data (
"longitude" DOUBLE,
"latitude" DOUBLE,
"elevation" DOUBLE,
"fix_type" BIGINT,
"utc_time" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"sensor" BIGINT,
"vi1" VARCHAR,
"vi2" VARCHAR,
"r1" VARCHAR,
"r2" VARCHAR,
"r3" VARCHAR
);CREATE TABLE n_2012_07_27_hs_data (
"longitude" DOUBLE,
"latitude" DOUBLE,
"elevation" DOUBLE,
"fix_type" DOUBLE,
"utc_time" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"sensor" DOUBLE,
"vi1" DOUBLE,
"vi2" DOUBLE,
"r1" DOUBLE,
"r2" DOUBLE,
"r3" DOUBLE
);CREATE TABLE n_2012_08_03_cs_data (
"timestamp" TIMESTAMP,
"record" BIGINT,
"batt_volt_min" DOUBLE,
"ptemp" DOUBLE,
"airtemp" DOUBLE,
"targtemp_1022" DOUBLE,
"targtemp_1023" DOUBLE,
"targtemp_1052" DOUBLE,
"sbtemp_1022" DOUBLE,
"sbtemp_1023" DOUBLE,
"sbtemp_1052" DOUBLE,
"tmv_1022" DOUBLE,
"tmv_1023" DOUBLE,
"tmv_1052" DOUBLE,
"sonicv" DOUBLE,
"mad_inches" BIGINT,
"sigtime" DOUBLE,
"parr_inches" BIGINT
);CREATE TABLE n_2012_08_03_cs_gps (
"timestamp" TIMESTAMP,
"record" BIGINT,
"latitude_a" BIGINT,
"latitude_b" DOUBLE,
"longitude_a" BIGINT,
"longitude_b" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"magnetic_variation" DOUBLE,
"fix_quality" BIGINT,
"nmbr_satellites" BIGINT,
"altitude" DOUBLE,
"pps" BIGINT,
"dt_since_gprmc" DOUBLE,
"gps_ready" BIGINT,
"max_clock_change" BIGINT,
"nmbr_clock_change" BIGINT
);CREATE TABLE n_2012_08_03_hs_data (
"longitude" DOUBLE,
"latitude" DOUBLE,
"elevation" DOUBLE,
"fix_type" BIGINT,
"utc_time" DOUBLE,
"speed" DOUBLE,
"course" DOUBLE,
"sensor" BIGINT,
"vi1" DOUBLE,
"vi2" DOUBLE,
"r1" DOUBLE,
"r2" DOUBLE,
"r3" DOUBLE
);CREATE TABLE n_2012_f017_activitieslog (
"bronson_files_volume_1_f017_2012_activities_log_table" VARCHAR -- Bronson Files Volume #1 - F017–2012 Activities Log Table,
"unnamed_1" VARCHAR -- Unnamed: 1,
"unnamed_2" VARCHAR -- Unnamed: 2,
"experimental_and_agronomic_field_operations_are_listed" VARCHAR
);Anyone who has the link will be able to view this.