1 - AON-CADIS Arctic Observing N

Document Sample
1 - AON-CADIS Arctic Observing N Powered By Docstoc
					1. Andrey Proshutinsky (WHOI)
2. Douglas Kane (UAF)
3. Gaius Shaver (MBL WHOI)
4. Hajo Eicken (UAF)
5. Ignatius G. Rigor (UWash)
6. Jacqueline Richter Menge (CRREL)
7. James Moore (NCAR/EOL)
8. James Morison (UWash)
9. John Toole (WHOI)
10. Jack Kruse (UAlaska)
11. Mary-Louise Timmermans (WHOI)
12. Matthew Shupe and Von Walden (U Colo/U Idaho)
13. Patricia Matrai (Bigelow)
14. Rebecca Woodgate Ron Lindsay Tom Weingartner Terry Whitledge (UWash/UAF)
15. Richard Collins (UAF)
16. Robert Hollister (GVSU)
17. Shari Gearheard (CIRES)
18. Steven F Oberbauer (FIU)
19. Tim Stanton (NPS)
20. Vladimir E. Romanovsky (UAF)
21. Craig M. Lee (UWash)
22. Marion S. Bret-Harte
23. Marion S. Bret-Harte (addendum)
                                   PROJECT NAME

1. 1. IPY: Towards an Arctic Observing Network: An array of Ice-Tethered Profilers to
sample the upper ocean water properties during the International Polar Year
   2. The Beaufort Gyre System: Flywheel of the Arctic Climate?

2. Long-term Measurements and Observations for the International Arctic Research
Community on the Kuparuk River Basin, Alaska

3. IPY: Collaborative Research on Carbon, Water, and Energy Balance of the Arctic
at Flagship Observatories and in a PanArctic Network

4. IPY: Collaborative Research on the State of the Arctic Sea Ice Cover:
An Integrated Seasonal Ice Zone Observing Network (SIZONET)

5. Coordination, Data Management and Enhancement of the International Arctic Buoy

6. Ice mass balance buoy network: Coordination with DAMOCLES

7. Cooperative Arctic Data and Information System (CADIS)

8. North Pole Environmental Observatory

9. Ice-Tethered Profilers (ITPs)

10. IPY Collaborative Research: Is the Arctic Human Environment Moving to a New

11. Observing the dynamics of the deepest waters in the Arctic Ocean

12. Collaborative Research: IPY: Cloud properties across the Arctic Basin from surface
and satellite measurements - an existing Arctic Observing Network

13. The Collaborative O-Buoy Project: Deployment of a Network of Arctic Ocean
Chemical Sensors for the IPY and beyond

14. IPY: COLLABORATIVE RESEARCH: The Pacific Gateway to the Arctic-Quantifying
and Understanding Bering Strait Oceanic Fluxes

15. IPY: Pan-Arctic Studies of the Coupled Tropospheric, Stratospheric and
Mesospheric Circulation.

16. Study of arctic ecosystem changes in the IPY using the Interantional Tundra

17. ELOKA: Exchange for Local Observations and Knowledge of the Arctic

18. Collaborative Research: Study of Arctic ecosystem changes in the IPY using the
International Tundra Experiment.
19. Toward developing an Arctic Observing Network: An array of surface buoys to
sample turbulent ocean heat and salt fluxes during the IPY

20. Development of a Network of Permafrost Observatories in North America and
Russia: The US Contribution to the International Polar Year

21. An Innovative Observational Network for Critical Arctic Gateways: Understanding
Exchanges through Davis Strait

22. IPY: Collaborative Research on Carbon, Water, and Energy Balance of the Arctic
Landscape at Flagship Observatories and in a pan-Arctic Network

23. No response.
Deployment Site(s)

1. For project 1: these sites are lagrangian buoys which move with sea ice. Their
coordinates and data are available in real time at
For project 2: T, S, chemistry are available at ~ 30 hydrographic stations and 4 moorings
in the beaufort sea region limited by 72-78N and 140-150W

2. 69.41 149.74

3. Toolik Lake, Alaska (68.63N, 149.6W)
Cherskii, Siberia (69N, 161E)

4. Barrow mass balance site: 71.367N 156.517W
End of thickness transect Barrow: 73.567N 156.717W
Wales site: 65.600N 168.083W
Other sites operated by international collaborators, details in text sent separately

5. Drifting buoys on that Arctic Ocean

6. Unknown at this time. Ten drifting buoys will be deployed on the sea ice in the Arctic

7. N/A -- Archive data and metadata site

8. 85-90N, all longitudes

9. Drifting array of more than 12 ITPs throughout the Arctic Ocean.

10. pan-Arctic using existing data: see definition @
We will not be "deployed" in the sense you are asking. We will be visiting data archive
sites in the US, Canada, Greenland, Norway, and Russia.

11. 75 N, 150 W
74N, 140W

12. Barrow, AK, USA: 71.323 N, 156.616 W
Eureka, Canada: 80.0 N, 85.81 W
Arctic Ocean (SHEBA): drifting location
North Pole (ASCOS): 90 N, 0 W
Tiksi, Russia: 71.6975 N, 128.9028 E

13. Test site = Barrow, Alaska

14. Bering Strait
ca 59-68N, 165-175 W CTD
with moorings at ~ 66N, 168W

15. Andoya, Norway (69°N, 16°E), Chatanika, Alaska (65°N, 147°W), Eureka, Nunavut
(80°N, 86°W), and Kangarlussuaq, Greenland (67°N, 51°W).
16. 71.18N 156.40W
70.27N 157.24W

17. N/A

18. Thule, Greenland 76.53 N, 68.81 W
Barrow, AK, USA 71.30 N, 156.67 W
Atqasuk, AK, USA 70.45 N, 157.40 W
Toolik Lake, AK, USA 68.63, 149.56 W
Tibetan Plateau, China 37.48 N, 101.2 E
Niwot Ridge, CO, USA 40.05 N, 105.6 W
Additional collaborator sites:
2 sites in Norway
3 sites in Canada, including Alexandra Fiord
One site in Svalbard
One site in Iceland
One site in the Faro Islands
One site in Southern Australia

19. Each year buoys will be deployed at the location of the North Pole Environmental
Observatory camp near the North Pole and at locations in the Beaufort Sea. In the first
year of the project, one buoy will be deployed in the Laptev Sea.

20. The exact locations of the following sites will be available (I will send them as a
separate file).
Alaska: more than 60 sites; Russia: Bolsjezemelskaya thundra, Bolvansky cape (4
Pechora riv., Polar Ural (25);
Nadym area (9);
Mara Sale, Yamal peninsula (6);
Vaskiny Dachi station, Center of Yamal peninsula (2);
Yamburg gas filed area, Western Siberia (3);
Western and Southern Yakutia (.gt.100);
Central Yakutia (2);
Tiksi (5);
Yana-Indigirka lowland (3);
Kolyma lowland (3);
Baikal region (3);
Klyuchevskaya volcanoes group, Kamchatka peninsula (3)

21. Inside box bounded by 62 N, 63 W and 70 N, 51 W
Intensive moored measurements along line from roughly 66.75 N,61.5 W to 67.25 N, 54

22. Toolik Field Station/Imnavait Creek in Northern Alaska (68o 38'N, 149o 36' W)
NE Science Station, Cherskii, Russia (69o N, 161o E)
Collaborating data from Abisko, Sweden; Zackenberg, Greenland, and sites in Canada

23. no response.
                                 Period of Deployment:

1. 1. 2004-present
    2. 2003-present

2. Present to April, 2009

3. 2007-20010

4. 2007-2010
Ice measurements during ice season (typically November-June)
Some observations yearround

5. 1979 – present

6. 2007 – 2008

7. 2007-2009

8. 2000 onward, intense observtions in annually in April

9. 2004-2008 and beyond.

10. Over the course of the project (two years).

11. Aug. 2007 to Aug. 2008

12. Barrow, AK, USA: 3/98 - present
Eureka, Canada: 8/05 - present
Arctic Ocean (SHEBA): 10/97 - 10/98
North Pole (ASCOS): 7/08 - 9/08
Tiksi, Russia: unknown

13. july 2008- may 2009

14. 2007-2009

15. Campaigns during IPY winter-spring 2007-2008 and 2008-2009.

16. 2006-2009

17. N/A

18. May 2007-Dec 2008

19. Nine Buoys will be deployed from 2007-2009. Each buoy will record data for 1-2

20. 2007 - 2009 and beyond

21. September 2004 through October 2010
22. 4 years (at least initially)

23. no response
What data will you provide to an archive?:

1. T,S, chemistry, currents, bottom pressure, and sea ice thickness from 4 ULSs.

2. Meteorological and hydrological data

3. CO2, CH4, DOC, DIC, water, and energy flux from terrestrial landscapes, and
associated climate data

4. ice mass balance data, ice core data, ice buoy data, ice thickness profiles, ice optics
data, web cam images, radar images, satellite images (details in document sent

5. Drifting Buoy Data

6. From each buoy we will provide a time series of position, barometric pressure, air
temperature, snow depth, ice thickness, ice growth, ice surface ablation, ice bottom
ablation, and profiles of temperature through the ice.

7. N/A

8. Ocean properties, ice thickness and mass balance, asurface atmospheric data

9. Profiles of seawater temperature and salinity down to 750 m depth, some with
dissolved oxygen, and ice drift from GPS locations.

10. see table of initial variable identification by project component at:

11. temperature, salinity, velocity

12. Time-height cloud properties data sets above Arctic atmospheric observatories

13. date, time, O3 concentration, BrO concentration, CO2 concentration

14. Mooring time-series data
CTD data

15. Temperature profiles of the stratosphere and mesosphere.
Maps and movies of vortex position over Arctic, based on satellite observations,
radiosondes and meteorological analyses.

16. Data and meta-data

17. Traditional knowledge; environmental observations of Arctic residents; community-
based monitoring data: all shared as approved by contributing community/project

18. plant phenology data, plot point-quadrat vegetation data, plot reflectance spectra,
plot NDVI images, leaf and litter nutrient content and stable isotope ratios, leaf lignin and
tannin contents, soil solution nutrient concentrations, and soil and soil respiratory
radiocarbon data (age)
19. Near-ocean-surface, point-measurement time series of temperature, salinity, water
velocity and the vertical turbulent fluxes of heat, salt, and momentum. Time-series of
vertical profiles of water velocity made by a acoustic doppler current profiler.

20. Ground (permafrost) temperatures at multiple depths recorded with various time

21. Hydrographic profiles: temperature, salinity, dissolved oxygen, chlorophyll
fluorescence, light transmission, selected tracers concentrations TBD.
Shipboard ADCP profiles
Shipboard underway data, including meteorology, SST and SSS.
Moored timeseries of velocity, temperature, salinity, ice draft, ice velocity, acoustics
Glider-based repeat sections (profiles of temperature, salinity and dissolved oxygen)

22. Fluxes of CO2, methane, and water vapor. Micrometeorological data, including
temperature, wind speed, radiation (short and long wave). Data on soil temperatures,
soil moisture. Data on vegetation composition and production in the footprints of the
eddy flux towers. Data on stream chemistry (DOC, etc.) from Imnavait Creek and
possibly from Cherskii.

23. Phenology of appearances of animals and plants. Phenology of ice appearance and
disappearance. Photographic patterns of snow cover appearance and disappearance.
Climatic data from the Toolik main weather station. The collection of environmental data
at the station is expanding, so more types of data will be available in future years. This
will include borehole temperatures, likely instrumented by Vlad Romanovsky.
              Do you provide an archive site for accessing data now?


2. all
past data current conditions

This is the Arctic LTER site, containing hundresds of data sets on lake, stream, and
terrestrial ecosystems near Toolik Lake


5. Yes,



8. NSIDC for archive, near-term data at


10. - we will initially use a passworded section of the site to
collaborate in database development.

11. No response.

12. Some related data is available at:

13. no response.


15. Lidar temperature data is currently housed at host institutions. Data records extend
back to mid-1990's. Maps are also housed at host institutions.

16. no, not directly, data have been archived through JOSS in the past under a former PI

17. ELOKA is developing its own archive. ELOKA proposes to provide data
management and user support to facilitate the collection, preservation, exchange, and
use of local observations and knowledge of the Arctic.
18. National Snow and Ice Data Center,

19. Work underway to establish

20. No. However, some of the Alaskan data are stored at the NSIDC in Boulder, CO

21. We are working to provide data through:
However, this is not yet operational.

22. Data will be archived through the Arctic LTER database,

23. Climatic data is still at the Arctic LTER site (specified in
previous submission), but will probably migrate to UAF in the future.
Would you prefer a central AON archive site to house your data?:

1. does not matter

2. No, we have neen contributing data for several years (before AON)

3. Our current arrangements work well for our own needs; the main new need is to
ensure seamless collaboration with other AON/IPY projects. To achieve this a central
archive is less important than clear and simple metadata protocols

4. Yes, along with mirrored data availability at sites listed above

5. No preference. I would not mind having the data available from multiple sites. E.g. we
also archive at NSIDC.

6. Its less important that the data physically reside in an AON archive than that there be
strong and lasting links between web sites.

7. N/A

8. OK but not solely.

9. Not necessarily.

10. No, but we want to be sure that we can share data with other projects.

11. yes

12. yes

13. yes

14. Having a central AON site is essential.
We would still maintain our own archive in addition.

15. We would like to discuss this during the workshop.

16. yes

17. No

18. It would somewhat helpful but I do not believe it is absolutely necessary. For
maximizing value though, it probably should be at least all be linked to a single portal.

19. We will consider this option.

20. Yes

21. It might be easier for us to correct processing mistakes on our own site. However, a
central site that logged users, and could thus send out notifications of changes, could be
very useful. Ultimately, we will probably always serve from our own site, even if in
parallel with the AON site.

22. Not necessary, but it might be helpful for back up

23. Would be nice, but is not necessary.
What is the data type and/or parameters to be included?

1. all

2. air temperature, relative humidity, wind speed and direction, soil temperature,
barometric pressure, atmospheric longwave radiation, emitted longwave radiation,
incident shortwave radiation, reflected shortwave radiation, net radiation, precipitation,
stream discharge

3. CO2 flux, energy balance parameters, water vapor flux,climate and microclimate
variables, vegetation cover and composition, soil properties, surface reflectance spectra
including NDVI

4. A listing with more detailed information will be sent separately

5. SLP, SAT, Ice Motion, Snow depth, Ice Thickness, Ice Temperatures, etc.

6. Data from each buoy includes: position, air temperature, barometric pressure, snow
depth, ice thickness, vertical profiles of ice temperature.

7. We will archive data and metadata from AON projects. Data will be varied in type and

8. Ocean temp salinity, oxygen, velocities, diffusivities, bottom pressure, ice thickness,
temperature profile, atmospheric pressure, atmospheric temperature, solar radiation

9. P,T,S,and ice drift.

10. We anticipate integrating our project with Arctic-RIMS using the National Snow and
Ice Data Center called EASE-Grid. See:
Variables will be coded at the grid level (25km), national, subnational (e.g. province),
and administrative subdivision (e.g. borough, municipality). We also anticipate producing
point data at the community-level.

11. ascii column format: pressure, temperature, salinity, velocity

12. time-height and timeseries of observables from a given site. The data files will
include cloud water content, particle size, and extinction for both liquid and ice phases.
In addition, some information will be included on cloud water paths, optical depths,
vertical locations, presence, phase classification, vertical velocities, and radiative forcing.

13. atmospheric concentrations of BrO, O3 and CO2

14. Mooring data - currents, TS, biooptic data, some ice tracking and rough ice thickness

CTD data - standard CTD measurements, nutrient bottle samples

15. Data is temperature profiles with error in altitude. Maps are images. We are currently
refining how the two data sets will be integrated, and anticipate using the AON workshop
as a basis for defining the final data types with our international IPY partners.
16. Plant growth, Plant phenology, plant cover, soil/air temperatures

17. Transcripts; audio recordings; video recordings; photographs; maps; artwork;
scientific measurements. Parameters vary between communities and projects but
include environmental parameters such as snow, sea ice, water levels, vegetation,
animal populations, etc.

18. Data will all be manual at regular intervals or for single events at peak season.
Regular intervals: weekly-plant phenology (bud/leaf/flower/fruit status), plot reflectance
spectra (2 nm intervals from 310-1100 nm), NDVI images (jpeg format, 3.1 Mpixels); one
time measurements at peak season (leaf nutrients CNP%, leaf isotopes (13C,18O per
mil), litter nutrients (CNP%), soil solution nutrients (NP m or micromolar), radiocarbon of
respiratory CO2 and soil fractions, point quadrat (species identity and height of top and
bottom hit in a 10 x 10 grid lain over 1 m2.

19. See reply to first question. The interval of the time-series will be 3-4 hrs.

20. Ground (permafrost) temperatures at multiple depths recorded with various time

21. Please see above. Metadata, full time and geolocation stamps will be included.
Although we are willing to share our engineering data, we do not plan to serve it
publically due to the specialized nature, limited audience and large effort that would be

22. Sorry, I don't understand what you are asking for here.

23. No response.
What is/are the data format(s)?:


2. ascii comma separated

3. Raw data in various formats; all coverted to Excel for present purposes; many data
files archived in ASCII

4. mass balance site, buoy, core and thickness data: comma-separated variable ASCII
satellite data and radar imagery: plan is to comply with AON standard currently under
discussion (e.g., NetCDF, preferably GeoTIFF)

5. ASCII, but we can make NetCDF or any other formats if required.


7. Many types

8. Typically ascii or matlab


10. Variables will range from interval (e.g. income) to categorical (e.g. type of
management institution) scaling.

11. ascii column

12. netCDF

13. no response.

14. Ascii

15. Data formats to date are ASCII.

16. spread sheets (Excel)

17. Transcripts; audio recordings; video recordings; photographs; maps; artwork;
scientific measurements.

18. MS-Excel or ascii text, jpeg images

19. Prefer .mat (matlab data file) or flat ascii files

20. Real numbers with to digits after decimal point.

21. NETCDF (preferred) and MATLAB binary.
22. Most likely ASCII files. We could convert to another format if help is available to do
this and it is desired.

23. ASCII files
 What metadata (format and content) do you provide or plan to provide with your

1. whatever is needed

2. site layout and instrumentation specifications

3. Most data are now available using LTER Network Metadata standards (EML)

4. FDGC and ISO compliant metadata files (html and ASCII txt)

5. Metadata for the buoys are currently provided by the manufacturers to JCOMMOPS,
but we can collect these and provide them to the AON.

6. Our data will be presented in a web format with metadata prominently displayed.

7. N/A

8. location, time measurement technique, etc, see

9. see web page.

10. Variable definition, scaling, geographic level, time periods, quality assessment.

11. latitude, longitude, platform, Date, Time

12. netCDF header information detailing the fields that are present in each file. We will
also provide metadata that contains both this netCDF header type information, some
expansion on that information, and additional information on the dataset as a whole.

13. no response

14. Standard as per current archive. (honestly, what did you expect us to
say here?? there are examples on our current archive site)

15. No, data is currently available by request from host institutions. For the IPY
campaigns we would release a daily summary of the meteorological conditions showing
the evolution of the weather in the troposphere, stratosphere and mesosphere.

16. text description

17. Unknown. ELOKA will work this out with project partners.

18. Joss data set guidelines

19. Lat, long, time and data format readme files (in ascii)

20. We have a special form for metadata, which was approved and used by GTN-P
21. Embedded in NETCDF, with additional information in text files as necessary.
22. We will provide metadata in the LTER formats, since our data will be archived in the
LTER database.

23. We are still developing metadata, and are open to suggestion.
What is the time (and space, if you have more than one site) resolution of the

1. 1. 2004-present
    2. 2003-present

2. We report hourly data

3. Resolution varies with the variable of interest. Spatial scale from 1 m2 to square
kilometers. Temporal scale from less than 1 second to half-hourly or hourly averages

4. point-based mass-balance measurements: sampling rate 0.5/hr
ice sampling: 1-2 times per site per year
ice thickness profiling: once per year, spatial resolution .lt.10 m along 100-200 km
satellite data: depends on sensor (details see separate document)

5. We get about 60 hits from each buoy per day, and currently have about 50 buoys
drifting across the Arctic Ocean.

6. We will have 10 autonomous ice mass balance buoys at drifting locations.
Measurements will typically be made every 4 hours.

7. N/A

8. question is really to braoad for a questionaire. These varie from every 15 minutes to
every 3 years and 10 cm vertical resolution to 500 km horizontal scale.

9. Depending on ITP, 1 to 4 profiles per day.

10. 1980-present annual data with some variables potentially coded by month.

11. depth profiles every 4 hours

12. Time resolution: 1-60 min.
Vertical resolution: ~50 m
Space: 4-5 locations across the Arctic

13. Early spring, hourly
Rest- daily
No summer data

14. Mooring data - likely 15min or 1 hr resolution for 2 years
CTD data – casts

15. Lidar temperature data is acquired under clear skies on consecutive nights. Profiles
are hourly over several hours. Radiosonde data is available as two profiles twice a day.
Satellite data is available continually on an hourly basis. Meteorological analyses are
available once daily.

16. summer only at 4 sites (2 at barrow and 2 at atqasuk)
17. To be determined.

18. We will have weekly data for sites at Toolik, Barrow, and Atqasuk, and peak season
data (see question data type above) from either 2007 or 2008 for Niwot Ridge, Thule
Greenland, Tibetan plateau. We have agreements with international investigators for
peak season data for Finse Norway, Abisko Sweden, Faro Islands, Iceland, Alex Fiord
Canada, Svalbard, and White Mountains Australia.

19. The interval of the time-series will be 3-4 hrs. At typical ice drift speeds, this
corresponds to a spatial resolution of 0-5 km

20. Time: from ones/year to ones/day time resolution
Space: point measurements

21. Varies by platform.

22. Flux data will be corrected to 0.5 hour averages

23. Environmental data collection by TFS began in October 2006, but climatic data is
available back to 1988 through the Arctic LTER. Data is collected in the vicinity of TFS.
Please describe any data quality control that you apply to the data:

1. LEVEL 1 RAW DATA is received from each ITP several times per day (after each
profile) and made available within a few hours at ITP data. The locations are unfiltered
and the scientific and operating data are extracted from the binary profiler file and saved
in MATLAB format files, but no other processing, cleaning or smoothing is performed.

LEVEL 2 REAL TIME DATA with preliminary processing is updated multiple times per
day. The location data are filtered and interpolated, while the scientific and operating
data are averaged in 2 m bins and plotted.

Level 2 data from the ITPs deployed in the Beaufort Gyre are available:

2004 - ITP2

2005 - ITP1 - ITP3

2006 - ITP4 - ITP5 - ITP6

LEVEL 3 ARCHIVE DATA includes all de-spiking, filtering, and corrections and will be
updated several times per year at ITP data.

A full description of the ITP data processing procedure will be provided here at a later

2. Before it is sent to NSIDC we do a quality control check.

3. Data are scanned for outliers, filtered, calibrations checked regularly. Integrated
values over half-hourly and longer time intervals calculated during post-processing.

4. With the exception of near-realtime data (see below), all data sets will be subjected to
QA/QC consisting of calibration (where necessary), removal of erroneous data points
(equipment malfunction, data loss), and flagging of suspect data (potential calibration
errors, etc.)

5. Real-time data are QC'ed as part of the buoy-qc efforts of the operational
communities of the DBCP and JCOMMOPS. Research data are QC'ed at the Polar
Science Center.

6. We have two layers of quality control. The first is a computer program that removes
incorrect or incomplete data. The second is a human check of the data for more subtle

7. N/A

8. We work hard to ensure the data we archive is usable by third parties.

9. Filtering and averaging.
10. Maintain original links to data sources; record all procedures use to reformat/recode
data to fit project requirements; obtain qualitative assessment of quality from source
experts; record observations of data anomolies.

11. standard processing, de-spiking

12. The original data sets are produced by other programs (DOE ARM, NOAA, etc.) who
perform their own data quality including data continuity, instrument health, and
measurement quality. Quality control on our derived data sets is based on manual
review of data images and on comparison of results with independent measurements
such as those from aircraft in situ campaigns.

13. no response

14. Pre and post mooring calibration
Pre and post CTD calibration
In house processing and quality control.

15. The retrieval of temperature profiles includes error analysis. error files are computed
with temperature files. Satellite data are provided with levels of quality control.

16. look through it to make sure it appears correct and do preliminary analysis to look for

17. To be determined.

18. Data are double checked upon entry, max, mins, and distributions visualized for
outliers. Outliers are checked against original data sheets. Nutrient analyses are run
twice. Point frame data are entered using MS-Access with restricted entry so only
correct species can be entered with heights restricted to realistic range. Spectra are
referenced against standard and visually inspected for problems.

19. Data will be fully quality-controlled before release. Subsets of more robust data will
be available in near-real time from our website.

20. Temperature sensors are normally tested in the ice bath for 0C. Other types of
quality control also have been used

21. We would prefer to fully process the data before release. However, this precludes
near-realtime release of glider data, and delays dissemination. We could release
uncontrolled preliminary products, if there is a real need for this.

22. Eddy flux data will be checked and bad data (because of instrument failure or strong
winds, etc.) will be removed. Data interpolation and Kalman filtering to deal with data
gaps will be carried out at the MBL. Other types of data (temperature, etc.) will be
summarized and checked for outliers, etc. Data on vegetation will be checked for
transcription errors and outliers, and will be summarized.

23. Data are checked for outliers and entry errors (for phenology data). Photographs of
snow cover are rectified by the TFS GIS department.
                     Will you be collecting data in non real-time?

1. both in real and non real time depending om project

2. Generally no.

3. Mostly not real-time although wireless communication to data loggers will be used to
check for instrument malfunctions, and for coarse estimates of fluxes and climate
parameters; most data require significant post-processing.

4. Ice thickness surveys and ice sampling/optics data will be limited to individual
sampling campaigns with subsequent data processing.

5. No

6. No.

7. N/A

8. Yes, once per year at our mooring and bottom pressue recorders. We pick up these
data once per year.

9. No.

10. This project is focused on existing data. We also will identify near-real time data
streams that closely match existing data streams (e.g. sea ice conditions).

11. Yes, one year of data from each of two moorings will be collected in August 2008.
No data will be available before this.

12. No response.

13. Early spring period will be real-time data
All other times will be weekly transmission
No summer data collected

14. Moorings - as described above

15. No

16. data collected during the summer and to be archived in the late fall to early winter

17. To be determined.

18. All data will be non-realtime. It will all be manual at regular intervals or for single
events at peak season. Regular intervals: weekly-plant phenology (bud/leaf/flower/fruit
status), plot reflectance spectra (2 nm intervals from 310-1100 nm), NDVI images (jpeg
format); one time measurements at peak season (leaf nutrients%, leaf isotopes (per mil),
litter nutrients (%), soil solution nutrients (mmolar), radiocarbon of respiratory CO2 and
soil fractions, point quadrat (species identity and height of top and bottom hit in a 10 x 10
grid lain over 1 m2.
19. Our data are transmitted back from the buoys in near-real time (twice a day)

20. Yes. Typically once per year data collection

21. Yes. Moorings serviced in autumn of each year. Data processing requires several
months following recovery.

22. Yes. Vegetation data will be non-real-time, with collection and summarization
occurring once per year. Stream chemistry data will also not be collected in real-time.
Eddy flux data will be collected in real-time. Flux data at Cherskii may not be able to
leave Russia in real-time, we hope to do much of the processing in Cherskii, and send
out the corrected data.

23. All data are non-real-time. The cameras are connected to dataloggers and
downloaded periodically. Phenology data are collected by observers.
What data will be collected in real-time?:

1. T,S

2. Most data is collected in near real time (within 1 hour) via radio network however data
transmission success depends on the weather.

3. Weather and microclimate, coarse flux estimates

4. ice-mass balance data (incl. drifting buoy), satellite imagery, web cam and radar

5. Yes

6. All buoy data are collected in near real-time. They will be transmitted several times
per day.

7. We will eventually collect many AON datasets, or provide direct web links to them

8. autmated drifting station data= surface met and some ocean data

9. All.

10. None.

11. no

12. All measurements are collected in real-time by the responsible programs (DOE,
NOAA). Our analysis will be done in post-processing.

13. date, time, O3 concentration, BrO concentration, CO2 concentration

14. no response

15. Laser radar, radiosonde and satellite measurements of temperature profiles.

16. maybe climate data depending on costs

17. Unknown.

18. no data will be real-time

19. All of it

20. Non

21. All data collected in real-time. Only glider and shipboard data can be accessed in
real-time, the rest are recovered on an annual basis.

22. CO2 flux, Water vapor flux, methane flux, micrometeorological data
23. none
Please describe any real-time quality control process that you do:

1. Same as earlier QC question.

2. Although we make the data available there is no immediate quality control of this data

3. None in real-time

4. on ice mass balance data bad data points due to equipment malfunction (as
identifiable through exceedance of pre-set thresholds) are automatically edited out; for
all time series a data set subjected to QA/QC as described above is produced and
released after field season

5. Data are part of the buoy-qc monitoring efforts of the DBCP and JCOMMOPS.

6. Computer program filters for incomplete or erroneous data.

7. N/A

8. same as above

9. Filtering and averaging.

10. No response.

11. No response.

12. Responsible programs perform real-time quality control on their measurements

13. no response

14. no response

15. Analysis routines determine temperature and associated errors.

16. not sure at the moment

17. no response

18. no response

19. Will not put near real time data into the AON database, but could provide a link to our

20. N/A

21. Limited automatic processing. Enough for a quick look, not enough to support robust

22. All of our quality control is not real-time right now.
23. no response
Where is the data sent?:


2. NSIDC and we also archive it.

3. Site not available yet; current weather and other data available at

4. drifting buoy data sent to CRREL, Hanover
coastal site data sent to UAF
satellite data received and processed at UAF

5. The data are posted to the Global Telecommunications System.

6. To ARGOS, then to CRREL

7. N/A

8. to us, and some is on GTS

9. To WHOI.

10. No response.

11. No response.

12. For Barrow, data are sent to the DOE ARM archive.
For SHEBA, Eureka, and ASCOS, the data are (will be) sent to the NOAA archive.


14. no response

15. Data is currently archived at host institutions. In our IPY proposal we stated that we
would host a central web-based archive and virtual observatory and provide data to
databases at several programs (e.g., CEDAR, CAWSES, SPARC).

16. have not worked it out

17. no response

18. no response

19. The data is sent via Iridium modem from the buoy to a linux workstation in our lab

20. N/A

21. Collected aborad ship or, in the case of gliders, telemetered directly to our laboratory.
22. The data will be sent to the University of Alaska Fairbanks for post-processing (or
processed in Cherskii), then will be sent to the Marine Biological Laboratory for Kalman
filtering and archiving at the Arctic LTER database

23. All data goes to UAF
Can it be accessed on-line?

1. yes

2. Yes, see above.



5. telnet, and


7. (Please note that site does not exist yet.



10. No response.

11. No response.

12. Barrow:

13. no response

14. no response

15. Samples of data are available on-line, but currently access is by request to host

16. no

17. no response

18. no response

19. Work underway

20. N/A

22. The Arctic LTER database can be accessed on-line at We do not currently plan to make data available before it
gets to the Arctic LTER database, but this could be modified if need be.

23. Toolik web site,
     Are you interested in receiving real-time data delivery of AON data at you

1. yes, all ocean and sea ice data

2. Not at this time.

3. Perhaps--don't know what is available

4. tbd

5. Maybe. We already get the data once per day from Argos, but when we have tried
going to more frequent updates, we get inundated with redundant or repeating data.

6. We are more interested in accessing AON from web sites.

7. N/A

8. not a burning issue

9. We would like to have access to all seawater data in the Arctic, and possibly some
meteorological and ice data as well.

10. No response.

11. No response.

12. no

13. yes, met data, ice cover, SST

14. no response

15. Not sure.

16. no

17. Yes, particularly local scale parameters of concern to Arctic communities - sea ice,
snow, lake ice.

18. no response

19. Shop for full q-c data releases.

20. Yes. Climate data and climate reanalysis data (if available)

21. No response.

22. I'd rather have access to the corrected data, not the raw data. I'm not sure that this is
necessary, though perhaps it will turn out to be more useful than I see right now.
23. no response
Will you be collecting data that require "special handling"

1. no

2. No

3. None

4. We are working with local observers in coastal villages who will record ice
observations and related activities. This data will be collected according to federally
mandated procedures and under guidance review of Institutional Review Board; archival
and dissemination of the data will occur in collaboration with SIKU IPY Project (Dr. I.
Krupnik) and ELOKA AON Project (Dr. Shari Gearheard)

5. No

6. No.

7. N/A CADIS will be equipped to handle such data should the AON investigators need

8. No.

9. No.

10. No. Although data will include human dimensions, it will be aggregate data.

11. no

12. no

13. no

14. no response

15. Not at this stage. We will be dealing with meteorological data sets.

16. no

17. Yes

18. No

19. no

20. No

21. Possibly (marine mammal acoustics- Stafford and Simon)

22. Vegetation data is in a very different format from the flux data, but probably doesn't
require special handling or security.
23. no response
  Do you require other complementary data in order to complete your research?

1. no

2. Usually not, but we do work with several other groups.

3. Yes; satellite data

4. no

5. No

6. Yes, we will be integrating our observations with other surface-based and satellite

7. N/A

8. remote sensing. extensive ice daa, atmospheric data, other bottom pressure
measurements are especially useful

9. In addition to the ocean data, we use meteorological, ice, and satellite data in our

10. We don't require complementary data to realize the goals of the project, but the
project will be greatly enhanced if we can access data from other projects.

11. not necessarily

12. Most data used in our analyses can be considered "complementary" in that they are
produced by other programs.

13. routine surface observations, met data, SST, satellite data of BrO, ice cover

14. Yes

15. Satellite data and meteorological analyses.

16. data from collaborators

17. Some remote sensing data might be interesting to overlay with local observations.
This is a future activity though.

18. Weekly MODIS EVI data would be helpful for Barrow, Atqasuk, and Toolik. Weather
data from those three sites also will be helpful (Toolik is available from LTER).

19. Our buoy will typically deployed with WHOI ice-tethered temperature and
conductivity profilers, PMEL met stations, and CRREL ice mass buoys. All of these data
are complimentary to one another.

20. Yes
21. Atmospheric data, remote sensing, oceanographic data from the surrounding regions
would all be useful as we try to understand this region.

22. We require data from our collaborators in Abisko, Zackenberg, and Canada to truly
complete our pan-arctic network of flux data. Their data will be available, but possibly not
on exactly the same time frame or in the same format as our data. It would be helpful to
get access to data from complementary AON projects such as the permafrost project
and the snow project.

23. no response
Please provide your perception of the top priority data management tasks that
would make AON most useful/successful to the broader community:

1. The system has to be simple with a minimum bureaucracy linking all data sets via
internet rather via managers and middlemen
Only raw data or minimum processed data should be collected. This will significantly
reduce cost of this system.

2. No response.

3. We need a clear definition of how these data are to be used--what are the research
questions to which they will be applied?

4. Having an accessible, well-organized archival and dissemination site and ensuring
that in addition to dissemination within scientific community, thought be given to how to
process and disseminate data in stakeholder-friendly fashion.

5. Easy access.

6. Rapid and easy access to data.

7. Easy data and metadata access

8. our problems are just having toime to qc and finish the basic processing. The external
problem is slowness of archiving

9. Simple standardized datasets of all paramters in near-real time.

10. retrieval of data streams at varying spatial and time scales.

11. a centralized data center on the web

12. A user-friendly, web-based interface for serving AON-related data to the scientific

13. no response.

14. Collation of AON data at one, easily accessible site.

Maintaining an overview of programs and data.

Permanent archiving of the data.

Easy data submission process (to aid getting the data collated quickly).

QC of the data to be done by PIs.

Easy search by region, date, measurement
subsetting by region, date, or measurement
Prompt collation of data once collected.
Clear graphical representations of data availability by maps and timeliness.

(These comments are collated from all PIs.)

15. We are particularily interested in how our data can be presented as part of an
integrated AON. We are intererested in discussing if AON will present a single
integreated virtual observatory.

16. 1 providing a temporary secured ftp space for PIs in collaborative projects to
exchange data with collaborators
2 providing easy access to data
3 providing agreed upon citation format for acquired data
4 tracking data downloaders for proper citation

17. no response

18. Linking the data into a system such as the trial Ameriflux "data cube" model for ease
of retrieval and visualization.

19. Centralized archiving and/or linkning to full q-c historical data sets, all Arctic.

20. Easy access and convenient and easy to use search engines

21. no response

22. Make it easy to share data among the AON projects, make it simple and easy to
contribute data, help with the data management and generation of metadata, if you want
them in a different format than what we are currently prepared to provide.

23. no response
Do you have other special data support requirements or comments?:

1. No

2. No response.

3. None

4. Not at this time.

5. No.

6. No.

7. CADIS will develop to be a major access point for AON data. Our success will rely on
the cooperation of the AON investigators.

8. Not at this time

9. No.

10. We think that the Arctic-RIMS database contains many of the desired features to
support inter-disciplinary research within AON.

11. No response.

12. no

13. no response

14. One thing I would stress and stress again .. (you are good at it, I think, but others are
not) .. when we talk about data bases and archives, can we make sure there is an ASCII
version of the data - not just matlab, not just excel .. but something everyone everywhere
can read. (I've just been through a round with someone who sent me a matlab file which
I am unable to open. 100 years from now, we need the data still to be readable. If the
files are small enough to be ascii, let's do it .. if not, then let's pick an easily readable
standard, and not expect someone to buy some commercial software. I know even the
Europeans don't often buy Matlab .. and I fear we are excluding the less developed
countries too.)

15. Not that we are aware of at this time.

16. I am concerned about other researchers using my data without including me as an
author, proper citation, or improperly using the data (bad conclusions that may be biased
due to how data was collected etc)

17. no response

18. no response.

19. no response
20. No

21. no response

22. Not at this time. Sorry for the delay in responding. This is a collaborative project with
Gus Shaver, and he has responded to this questionnaire also. Hopefully we are not
contradicting each other!

23. This is an addendum to the original questionnaire that I filled out. We would like to
include at least a link to the baseline environmental data collected by TFS within CADIS,
because we regard these data as being complementary to, and part of, our AON effort.

Shared By: