Airways Solar Radiation (DSI-3281)
Entry ID:
gov.noaa.ncdc.C00044
|
[
Update this Record
]
|
Updating this record requires registration.
|
Summary
Abstract:
Airways Solar Radiation is historical digital data set DSI-3281, archived at the National Climatic Data Center (NCDC). This is meteorological and solar radiation data. The meteorological data is a small historical subset of the larger, ongoing NCDC data set, US Global Surface Airways Hourly Observations (DSI-3280) (C00215). DSI-3281 contains meteorological data from only 31 of the many DSI-3280 ... stations, and only from the years 1988-95. These 31 stations also reported direct and global solar radiation data, which is found in DSI-3281 but not DSI-3280. The 31 stations included in this historical data set are located in the US and Guam. The stations are: Albuquerque, NM; Lander, WY; Bismarck, ND; Las Vegas, NV; Boise, ID; Long Beach, CA; Boulder, CO; Madison, WI; Brownsville, TX; Midland, TX; Burlington, VT; Montgomery, AL; Caribou, ME; Nashville, TN; Columbia, MO; Omaha, NE; Dodge City, KS; Phoenix, AZ; El Paso, TX; Pittsburgh, PA; Ely, NV; Raleigh, NC; Fresno, CA; Salt Lake City, UT; Grand Junction, CO; Seattle, WA; Great Falls MT; Sterling, VA; Guam, PI; Tallahassee, FL; and Lake Charles, LA. This data set contains hourly or 3-hourly surface weather observations that are taken primarily at major airports and military bases. Observations are made by trained personnel, or by automated equipment that has been tested by the controlling agency. Stations are usually fully instrumented and therefore record a complete range of meteorological parameters. Observations are generally recorded for the 24-hour period midnight to midnight. Basically, the major parameters are clouds, visibility, winds, air temperature, sky cover, relative humidity, air pressure, direct and global radiation and present weather. However, there have been several historical changes in the way observations have been recorded, including the advent of the Automated Surface Observing System (ASOS) in 1992. The detailed parameters, allowing for such changes, are: sky condition in tenths and height per layer; sky condition in eighths and height per layer; altimeter setting; sky condition in tenths and cloud coverage by layer; sky condition in eighths and cloud coverage by layer; ceiling height; cloud type and height by layer; total amount of sky cover by the first two cloud layers and by the first three cloud layers; dew point temperature in tenths Celsius; dew point temperature in Fahrenheit; horizontal visibility; station pressure; direct and global radiation; present weather code; present weather between 5 and 10 statute miles in vicinity; relative humidity; sea level pressure; air temperature in tenths Celsius; air temperature in Fahrenheit; wet bulb temperature in tenths Fahrenheit; total sky cover in eighths; total sky cover and total opaque sky cover measured in tenths; wind direction and speed to 16 points; wind direction and speed; and wind direction and speed from ASOS. All parameters are not reported by all stations. 
Purpose:
To make a wide range of climatic data available to researchers and the public.
SUPPLEMENTAL INFORMATION: data set
CURRENTNESS REFERENCE: Ground Condition
Related URL
|
Description:
View Source Metadata document from the Metadata Manager and Repository (NMMR).
|
Geographic Coverage
(Click for Interactive Map)
Spatial coordinates
| |
N: 49.0
|
|
S: 10.0
|
|
E: -65.0
|
|
W: 140.0
|
Data Set Citation
Dataset Originator/Creator:
National Climatic Data Center, NESDIS, NOAA, U.S. Department of Commerce
Dataset Title:
Airways Solar Radiation (DSI-3281)
Dataset Release Date:
Unknown
Data Presentation Form:
tabular digital data
Online Resource:
http://www.ncdc.noaa.gov
Temporal Coverage
Start Date:
1988-01-01
Stop Date:
1995-12-31
Quality
ATTRIBUTE ACCURACY REPORT: Anomalous/Suspect Data January 2004 Beginning Jan. 29-30 BP values fell between 960-970 mb, these data values should be considered suspect and were left in the data set. Reason is unknown. February 2004 On 02/03/2004 ice and snow were observed on the screen of the rain gauge. The plug was checked and the ice and snow were dumped into the funnel to test the heater. The ... heater was working. The cold may have overwhelmed the heater causing melting and re-freezing on the screen. Daily precipitation totals may be incorrect due to gradual melting of any snow and/or ice that accumulated in the funnel or on the screen. However, cumulative totals between these dates are correct. There was no precipitation on 02/03/04, but to preserve the cumulative total for the month, all data were left in. March 2004 No data anomalies April 2004 No data anomalies May 2004 The following 15-min precipitation totals were identified as outliers. Severe thunderstorms and torrential rains occurred on these dates. The anomalous data are most likely due to these events. The following data were left in: STNCODE SMPLDATE SMPLTIME CLASS TotPrcp hudfsmet 05/24/2004 20:30 15 05.8 hudfsmet 05/24/2004 20:45 15 05.3 hudfsmet 05/26/2004 21:45 15 13.0 hudfsmet 05/26/2004 22:00 15 07.4 hudfsmet 05/26/2004 22:15 15 05.1 The following 15-min and 60-min relative humidity readings were identified as outliers. The data appear consistent, and the cause of the anomalous readings was likely previously occurring heavy rains. The following data were left in: STNCODE SMPLDATE SMPLTIME CLASS RH hudfsmet 05/25/2004 05:15 – 07:45 15 101 hudfsmet 05/25/2004 06:00 – 08:00 60 101 hudfsmet 05/27/2004 02:15 – 07:45 15 101 hudfsmet 05/27/2004 03:00 - 08:00 60 101 June 2004 The following 15-min and 60-min relative humidity readings were identified as outliers. The data appear consistent and the causes of the anomalous readings were likely concurrent precipitation events. The following data were left in: STNCODE SMPLDATE SMPLTIME CLASS RH hudfsmet 06/03/2004 07:15 15 101 hudfsmet 06/03/2004 07:30 15 101 hudfsmet 06/26/2004 07:00 – 09:00 60 101 hudfsmet 06/26/2004 06:45 – 08:45 15 101 July 2004 The following 15-min and 60-min relative humidity readings were identified as outliers. The data appear consistent and the causes of the anomalous readings were likely concurrent precipitation events. The following data were left in: STNCODE SMPLDATE SMPLTIME CLASS RH hudfsmet 07/02/2004 06:00 – 08:00 15 101 hudfsmet 07/06/2004 00:45 – 09:00 15 101 hudfsmet 07/06/2004 01:00 – 09:00 60 101 hudfsmet 07/19/2004 01:45 – 04:30 15 101 hudfsmet 07/19/2004 02:00 – 04:00 60 101 hudfsmet 07/27/2004 18:00 – 24:00 15 101 hudfsmet 07/27/2004 19:00 – 24:00 60 101 hudfsmet 07/28/2004 00:15 – 10:15 15 101 hudfsmet 07/28/2004 00:15 – 10:00 60 101 hudfsmet 07/29/2004 03:00 – 08:00 15 101 hudfsmet 07/29/2004 04:00 – 08:00 60 101 The following 15-min precipitation totals were identified as outliers. The anomalous data are most likely due to heavy rain events. The following data were left in: STNCODE SMPLDATE SMPLTIME CLASS TotPrcp hudfsmet 07/05/2004 19:15 15 10.2 hudfsmet 07/23/2004 13:45 15 12.4 August 2004 The following 15-min and 60-min relative humidity readings were identified as outliers. The data appear consistent and the causes of the anomalous readings were likely concurrent precipitation events. The following data were left in: STNCODE SMPLDATE SMPLTIME CLASS RH hudfsmet 08/02/2004 02:45 – 08:30 15 101 hudfsmet 08/02/2004 04:00 – 08:00 60 101 hudfsmet 08/05/2004 01:00 - 08:30 15 101 hudfsmet 08/05/2004 02:00 – 08:00 60 101 hudfsmet 08/09/2004 01:30- 08:00 15 101 hudfsmet 08/09/2004 02:00 – 08:00 60 101 hudfsmet 08/12/2004 20:45 – 24:00 15 101 hudfsmet 08/12/2004 21:00 – 24:00 15 101 hudfsmet 08/13/2004 00:15- 09:45 15 101 hudfsmet 08/13/2004 00:15 - 09:00 60 101 hudfsmet 08/13/2004 23:15 – 24:00 15 101 hudfsmet 08/14/2004 0015 – 09:00 15 101 hudfsmet 08/14/2004 00:15– 09:00 60 101 hudfsmet 08/16/2004 05:00 – 10:45 15 101 hudfsmet 08/16/2004 06:00 – 11:00 60 101 hudfsmet 08/16/2004 20:45 – 24:00 15 101 hudfsmet 08/16/2004 21:00 – 24:00 60 101 hudfsmet 08/17/2004 00:15 - 08:45 15 101 hudfsmet 08/17/2004 00:15 - 09:00 60 101 hudfsmet 08/18/2004 06:15 15 101 hudfsmet 08/18/2004 06:30 15 101 hudfsmet 08/21/2004 02:15 – 05:30 15 101 hudfsmet 08/21/2004 03:00 – 06:00 60 101 hudfsmet 08/21/2004 13:30 15 101 hudfsmet 08/21/2004 13:45 15 101 hudfsmet 08/22/2004 04:15 – 08:00 15 101 hudfsmet 08/22/2004 05:00 – 08:00 60 101 hudfsmet 08/30/2004 20:15 – 24:00 15 101 hudfsmet 08/30/2004 21:00 – 24:00 60 101 hudfsmet 08/31/2004 00:15 - 08:30 15 101 hudfsmet 08/31/2004 00:15 - 08:00 60 101 The following 15-min precipitation totals were identified as outliers. The anomalous data are most likely due to heavy rain events. The following data were left in: STNCODE SMPLDATE SMPLTIME CLASS TotPrcp hudfsmet 08/01/2004 19:30 15 09.9 hudfsmet 08/30/2004 18:45 15 14.0 September 2004 The following 15-min precipitation totals were identified as outliers. The anomalous data are most likely due to heavy rain events. The following data were left in: STNCODE SMPLDATE SMPLTIME CLASS TotPrcp hudfsmet 09/17/2004 22:30 15 05.1 The following 15-min PAR totals were identified as outliers. The readings are within sensor specifications and occurred at night. Also, it was raining at the time. The following data were left in: STNCODE SMPLDATE SMPLTIME CLASS TotPAR hudfsmet 09/18/2004 02:00 15 -0001.6 hudfsmet 09/18/2004 02:15 15 -0001.8 hudfsmet 09/18/2004 02:30 15 -0001.8 hudfsmet 09/18/2004 02:45 15 -0001.8 hudfsmet 09/18/2004 03:00 15 -0001.7 hudfsmet 09/18/2004 03:15 15 -0001.4 hudfsmet 09/18/2004 03:30 15 -0001.3 hudfsmet 09/18/2004 03:45 15 -0001.1 hudfsmet 09/18/2004 04:15 15 -0001.1 hudfsmet 09/18/2004 04:30 15 -0001.3 hudfsmet 09/18/2004 04:45 15 -0001.4 hudfsmet 09/18/2004 05:00 15 -0001.5 hudfsmet 09/18/2004 05:15 15 -0001.5 hudfsmet 09/18/2004 05:30 15 -0001.3 The following 15-min and 60-min relative humidity readings were identified as outliers. The data appear consistent and the causes of the anomalous readings were likely due to concurrent precipitation events or early morning humidity . The following data were left in: STNCODE SMPLDATE SMPLTIME CLASS RH hudfsmet 09/08/2004 18:00 – 24:00 15 101 hudfsmet 09/08/2004 19:00 – 24:00 60 101 hudfsmet 09/09/2004 00:15 – 10:15 15 101 hudfsmet 09/09/2004 00:15 – 10:00 60 101 hudfsmet 09/11/2004 06:30 15 101 hudfsmet 09/13/2004 06:15 – 07:30 15 101 hudfsmet 09/13/2004 07:00 60 101 The aforementioned rain event on 09/17/2004 also appears to have affected the temperature readings. Erratic readings occurred beginning at 15:15 on 10/01/2004 (see Section 12). Temperature data from 23:30 on 09/17/2004 to 15:15 on 10/01/2004 were left in, but are considered suspect due to the onset of problems with the RH portion of the sensor. October –November 2004 The temperature/RH probe was replaced on 10/07/2004 and data collection began at 08:15 on 10/08/2004. The replacement probe was a spare that had not been calibrated since 2003. Therefore, all temperature/RH data from 08:15 on 10/08/2004 until 10:00 on 11/17/2004, when a new probe was installed, are suspect. November 2004 The following 15-min precipitation totals were identified as outliers. The anomalous data are most likely due to heavy rain events. The following data were left in: STNCODE SMPLDATE SMPLTIME CLASS TotPrcp hudfsmet 11/25/2004 10:30 15 07.1 hudfsmet 11/28/2004 11:30 15 06.1 December 2004 The PAR sensor began recording extremely high readings on 12/22/2004. These readings were followed by readings of –99999 on 12/23/2004. This pattern reoccurred on 12/29/2004 and 12/30/2004 and again on 12/31/2004 and 01/01/05. The problem was likely due to miscommunication between the PAR sensor and the CR10X caused by corrosion on the wires. Data that were obviously abnormal or –99999 were deleted (see Section 12). The following data appear reasonable, but were recorded during the time period that the PAR sensor appeared to be miscommunicating with the CR10X. The data were left in, but are suspect. STNCODE SMPLDATE SMPLTIME SMPLDATE SMPLTIME CLASS hudfsmet 12/22/2004 18:15 - 12/23/2004 11:15 15 and 60 hudfsmet 12/24/2004 23:15 – 24:00 15 hudfsmet 12/24/2004 00:15 - 12/29/2004 11:15 15 and 60 hudfsmet 12/30/2004 01:15 – 09:30 15 and 60 hudfsmet 12/30/2004 20:15 – 24:00 15 and 60 hudfsmet 12/31/2004 00:15 – 10:30 15 and 60 hudfsmet 12/31/2004 14:15 – 24:00 15 and 60 hudfsmet 12/25/2004 00:15 - 12/29/2004 00:00 144 On 02/07/2005 it was discovered that the circuit breaker on the outlet for the rain gauge heater had been tripped. It is unknown how long the heater had been inactive. The temperature did not fall below freezing for an extended period of time before 12/14/2004. There was a significant rain event on 12/23/2004. Therefore, if the heater was not working, daily precipitation totals between 12/14/2004 and 12/23/2004 and daily precipitation totals between 12/24/2004 and 01/01/2005 may be incorrect due to gradual melting of any snow and/or ice that accumulated in the funnel or on the screen. However, cumulative totals between these dates are correct. All data were left in. LOGICAL CONSISTENCY REPORT: NACOMPLETENESS REPORT: Data collection period Weather data have been collected at the Field Station at Tivoli Bays since July 1999. Weather data were collected for the entire year in 2004. Deleted Data March 2004 At 10:50 on 03/10/04 an updated program was loaded onto the CR10X (see Section 14). Hourly averages and max/min data (Array 60) at 11:00 on 03/10/04 and daily averages and max/min data (Array 144) at 24:00 on 3/10/04 were deleted due to loss of 5-second data used to calculate these averages. May 2004 The weather station was shut down for maintenance at 07:43 on 05/11/2004 (see Section 13) and after power was restored, data collection resumed at 10:45 on 05/11/2004. Therefore, hourly averages (Array 60) and max/min data (Array 15, 60) at 11:00 on 05/11/2004 were deleted due to loss of 5-second data used to calculate these numbers. Data collection was restored at 10:45 on 05/11/2004, but the newly calibrated barometric pressure sensor was not installed correctly. The problem was discovered and fixed at 12:15 on 05/11/2004. All barometric pressure data were deleted from 10:45 through 12:15 on 05/11/2004. Hourly average and max/min barometric pressure data (Array 60) at 13:00 on 05/11/2004 were deleted due to loss of 5-second data used to calculate these numbers. Data collection was restored at 10:45 on 05/11/2004, but the multiplier for the LI-COR sensor was not changed until an updated program (see Section 14) was loaded onto the CR10X at 11:30 on 05/11/2004. Therefore, all PAR data were deleted from 10:45 through 11:30 on 05/11/2004. The updated program (see Section 14) was loaded onto the CR10X at 11:30 on 05/11/2004. Therefore, hourly averages and max/min data (Array 60) at 12:00 on 05/11/2004 were deleted due to loss of 5-second data used to calculate these numbers. Daily averages and max/min data (Array 144) at 24:00 on 05/11/2004 were deleted (all parameters) due to the loss of 5-second data used to calculate these averages, which occurred after the updated program was loaded onto the CR10X. September – October 2004 On 9/17/2004 at 23:30 the RH reading was –99999. Erratic readings and readings of –99999 continued until the problem was discovered at 14:00 on 10/07/2004. The RH probe appears to have failed as a result of an extremely heavy rain event on 09/17/2004. All RH data were deleted from 21:15 on 09/17/2004 to 14:00 on 10/07/2004. Temperature readings became erratic on 10/01/2004, random temperature readings of 30-40oC began to occur at 15:15. The spikes became more frequent between 10/01/2004 and 10/07/2004, when the problem was discovered, and ranged from 50oC to 90oC. All temperature data were deleted from 15:15 on 10/01/2004 to 14:00 on 10/07/2004. The temperature/RH probe was replaced with a spare on 10/07/2004 and data collection began at 08:30 on 10/08/2004. Hourly averages and max/min data (Array 60) at 09:00 on 10/08/2004 and daily averages and max/min data (Array 144) at 24:00 on 10/08/2004 were deleted (all parameters) due to loss of 5-second data prior to 08:15 on 10/08/2004. Due to a possible programming or operator error (cause unknown) Battery Voltage (avgvolt) data was not recorded from 10/08/2004 at 08:30 until 12/09/2004 at 11:15. November 2004 The temperature/RH probe was replaced with a new probe on 11/17/2004. All temperature and RH data were deleted while the replacement was occurring from 10:30-11:00 on 11/17/2004. Daily averages and max/min temperature and RH data (Array 144) at 24:00 on 11/17/2004 were deleted due to the probe replacement. December 2004 The PAR sensor began recording extremely high readings on 12/22/2004. These readings were followed by readings of –99999 on 12/23/2004. This pattern reoccurred on 12/29/2004 and 12/30/2004 and again on 12/31/2004 and 01/01/05. The problem was likely due to miscommunication between the PAR sensor and the CR10X caused by corrosion on the wires. The following data were deleted: STNCODE SMPLDATE SMPLTIME CLASS hudfsmet 12/22/2004 15:00 – 18:00 15 and 60 hudfsmet 12/22/2004 24:00 144 hudfsmet 12/23/2004 11:30 – 23:00 15 and 60 hudfsmet 12/23/2004 24:00 144 hudfsmet 12/29/2004 11:30 – 23:45 15 and 60 hudfsmet 12/29/2004 24:00 144 hudfsmet 12/30/2004 00:15 - 01:00 15 and 60 hudfsmet 12/30/2004 09:45 – 20:00 15 and 60 hudfsmet 12/30/2004 24:00 144 hudfsmet 12/31/2005 10:45 – 14:00 15 and 60 hudfsmet 12/31/2004 24:00 144 Missing Data May 2004 The weather station was shut down at 07:43 on 05/11/2004 in order to replace the existing sensors with newly calibrated sensors. Data (all parameters) are missing from 07:45 through 10:30 on 05/11/2004. Data collection resumed at 10:45 on 05/11/2004. An updated program (see Section 14) was loaded onto the CR10X at 11:30 on 05/11/2004. Therefore, data (all parameters) were not collected at 11:30 on 05/11/2004. October 2004 The weather station was shut down at 14:10 on 10/07/04 in order to replace the temperature/RH probe. This cleared the program from the CR10X. The program was reloaded at 08:30 on 10/08/04. Therefore data (all parameters) are missing from 14:15 on 10/07/04 until 08:30 on 10/08/04. LINEAGE/PROCESS STEP: PROCESS DESCRIPTION: Additional Description: Entry verification The Centralized Data Management Office converted all SWMP weather data collected with CR10X program versions prior to version 4.0 which was distributed in October 2003. This was necessary in order to merge the old data format (12 array output) with the new data format found in version 4.0 (3 array output). The new format produces averages, maximums and minimums every fifteen minutes (array 15), every hour (array 60) and every day (array 144) for any sensors hooked up to the CR10X. Specifically, the 150 and 151 fifteen minute data were converted to the new 15 array; the hourly 101, 102, 105 and 106 data were converted to the new 60 array; and the daily 241, 242, 243, 244, 245 and 246 data were converted to the new 144 array. With the new format, the use of 55555's to code for deleted data and 11111's to code for missing data has been abandoned. Hence, all 55555's or 11111's contained in the SWMP weather data collected prior to Version 4.0 of the CR10X program were removed and left blank. The 15-minute, 1-hour average, and 24-hour data were downloaded from each instrument on the weather station to a Campbell Scientific CR10X datalogger. The CDMO Datalogger Program (NERR_4_1.CSI) was loaded into the CR10X, which controls the sensors and the data collection schedule (see Section 3). For data storage, the CR10X stored the data, via cable, on a Campbell Scientific SM4M storage module. The storage module was manually retrieved on a monthly basis. Using the PC208W software supplied by Campbell Scientific, the data were uploaded from the storage module and stored on a computer in comma-delimited format (.DAT). These raw data files were archived at the CDMO and at the reserve on CD-ROM. Raw data files were then opened in Microsoft Excel and pre-processed using the EQWin Format Macro developed by the CDMO. This macro reformats the header columns, inserts station codes, inserts a date column, corrects the time column format, and reformats the data to an appropriate number of decimal places. The Excel file was then copied into EQWin and the data were QA/QC checked using criteria defined in Section 3 and archived in a database. Queries, reports and graphs were used to discover outliers and large changes in the data. Data that were collected and retained but considered suspect are documented in Section 11. Data that were collected but deleted are documented in Section 12. Missing data are documented in Section 13. The Research Assistant is responsible for data entry verification. PROCESS DATE: 20060222
Access Constraints
Data collected in conjunction with the National Estuarine Research Reserve System's (NERRS) System-wide Monitoring Program (SWMP) is considered public information. Please see site for further information: http://cdmo.baruch.sc.edu/aboutdata.htm
DISTRIBUTION LIABILITY: Distribution According to the Ocean and Coastal Resource Management Data Dissemination Policy for the ... NERRS System-wide Monitoring Program, NOAA/ERD retains the right to analyze, synthesize and publish summaries of the NERRS System-wide Monitoring Program data. The PI retains the right to be fully credited for having collected and processed the data. Following academic courtesy standards, the PI and NERR site where the data were collected will be contacted and fully acknowledged in any subsequent publications in which any part of the data are used. Manuscripts resulting from the NOAA/OCRM supported research that are produced for publication in open literature, including refereed scientific journals, will acknowledge that the research was conducted under an award from the Estuarine Reserves Division, Office of Ocean and Coastal Resource Management, National Ocean Service, National Oceanic and Atmospheric Administration. The data set enclosed within this package/transmission is only as good as the quality assurance/quality control procedures outlined by the enclosed metadata reporting statement. The user bears all responsibility for its subsequent use/misuse in any further analyses or comparisons. The Federal government does not assume liability to the Recipient or third persons, nor will the Federal government reimburse or indemnify the Recipient for its liability due to any losses resulting in any way from the use of this data. NERR weather data and metadata can be obtained from the Research Coordinator at the individual NERR site (please see Section 1 Principal investigators and contact persons), from the Data Manager at the Centralized Data Management Office (please see personnel directory under the general information link on the CDMO home page) and online at the CDMO home page http://cdmo.baruch.sc.edu/. Data are available in text format and as Access data tables.
Use Constraints
The principal investigator (PI) listed in the enclosed metadata retains the right to be fully credited for having collected and processed the data. Please see the site for further information: http://cdmo.baruch.sc.edu/aboutdata.htm
Data Set Progress
COMPLETE
Distribution
Distribution Format:
Ascii File, Formatted For Text Attributes, Declared Format (ASCII)NA
Fees:
Data is available at no charge.
Personnel
Role:
TECHNICAL CONTACT
Role:
DIF AUTHOR
Contact Address:
New York State Department of Environmental Conservation
City:
Annandale
Province or State:
NY
Postal Code:
12504
Country:
USA
Creation and Review Dates
DIF Creation Date:
2008-08-01
Last DIF Revision Date:
2008-10-10
|
[
Update this Record
]
|
Updating this record requires registration.
|
|
