Skip to main content
Sign In |
  Help (new window)

Blog

Go Search
Home
Dataset Information
Blog
User Support
  

Categories
General Announcements and News
Dataset Changes and Updates
FAQ
Other Blogs
There are no items in this list.
Links
Photos
Archive
Archive (Calendar)
Fluxnet-Synthesis > Blog > Categories

4/20/2009

Finding SWC, H20stor, and Ts in the data cube
If you are accessing the fluxnet data through the data cube, you may notice that you do not see SWC, Ts, and H20stor as datumtypes in the cube.  This is because these three variables have an offset associated with them.  We have defined the offset of (none) to be the default in the cube.  Thus, variables that have an offset will not appear until you either provide offset as a filter or specify offset as one of the dimensions.  In the data cube, for clarity, we have translated the offsets of 1 and 2 into upper and lower respectively. When using the data cube, it is always a good idea to explicitly define each of the dimensions to make sure that you know exactly what you are getting.
Posted at 8:23 AM by Deb Agarwal | Category: FAQ | Permalink | Email this Post | Comments (0)

4/13/2009

Units for wbal_clim and wbal_act in the daily files
From Markus Reichstein: the units for wbal_clim and wbal_act are not converted to mm/day, but remain as average mm/h for that day.
Posted at 10:23 AM by Deb Agarwal | Category: FAQ | Permalink | Email this Post | Comments (0)
Submitted by and submission date explained . . .
For each ancillary data entry submitted, the full history of that entry is kept in the database.  The entry surfaced in the reports and in any of the web interfaces is the latest accepted entry.  With that entry you will see the fields "Submitted By" and "Submission Date". This will tell you who the value was received from and on what date.  The earliest date we received that entry (in the case of successive copies) will be surfaced.  Before the La Thuile workshop and during the La Thuile workshop the ancillary data entries were all kept in Excel spreadsheets with no provenance information.  Data from these original spreadsheets has  the "Submitted By" field set to "La Thuile prep" and the "Submission Date" set to the date we received the spreadsheet. Within the database we also keep the name of the spreadsheet.
 
Each time we output an updated set of ancillary data, all reports will include toward the top a generated date and a date indicating the most recent "Submission Date" for all the data in the report.  This will allow users to quickly recognize whether newer information is contained in the report.  We also publish a report with all ancillary data changes since the last major data release.  The flux/met data only changes at the time of a data release. Reports and the blog postings will indicate the flux/met data that has changed between releases.
 
If you have any questions regarding data changes or history of an ancillary data item please contact fluxdata-support@fluxdata.org.
Posted at 9:08 AM by Deb Agarwal | Category: FAQ | Permalink | Email this Post | Comments (0)

3/16/2009

Individual site ancillary data reports
There are now two types of ancillary data reports for each flux site.  The first contains all the public information and can be accessed from the link in the "Dataset Information" tab. The second report contains the full set of ancillary data for the report and can be reached using the links on the BADMFill report that can be obtained using the "Data Browsing" tab.
Posted at 5:24 PM by Deb Agarwal | Category: FAQ | Permalink | Email this Post | Comments (0)

3/10/2009

Procedure for adding new flux sites to fluxdata.org
Steps for getting a unique identifier assigned for a new site and getting that site listed in FLUXNET.
  1. Send the site name, state, country, latitude, longitude, primary contact, and the name of the appropriate fluxdata curator to fluxdata-curators@fluxdata.org.
  2. Dario Papale (who is on this mailing list) will assign a unique site code and will recommend a curator. He will send this information to fluxdata-curators@fluxdata.org + the requester.
  3. The new site will be added to the fluxdata.org database.
  4. Unless the suggested curator objects, the suggested curator will become the curator.
Posted at 10:16 AM by Deb Agarwal | Category: FAQ | Permalink | Email this Post | Comments (0)

2/17/2009

Redundant Ancillary Variables . . .
If you look at the list of site ancillary variables, you might notice that some seem to be redundant.  This is due to the fact that these variables came to us via different reporting protocols.  Where possible, we are moving to eliminate these redundant variables and are standardizing on the BADM variables.  If you are reporting values for a site and notice multiple variables with the same meaning, please use the variable names and protocol for reporting from the BADM documentation (links to this documentation can be found on the "Dataset Information" page).
Posted at 10:29 AM by Deb Agarwal | Category: FAQ | Permalink | Email this Post | Comments (0)

11/16/2008

Links added to enable direct download of reports . . . .
Under the dataset information and the data browsing tabs on the site, there are now (ftp) links.  Choosing these links will enable direct download of the excel version of the report.
Posted at 9:36 AM by Deb Agarwal | Category: FAQ | Permalink | Email this Post | Comments (0)

10/3/2008

Access to the FLUXNET synthesis dataset and proposal submission instructions . . . .
At the current time, the access to the FLUXNET synthesis dataset is restricted to PIs of sites that have data in the FLUXNET synthesis set and people working on a paper proposal that has been accepted. If you would like to submit a proposal, please see the instructions here.  We are currently looking at adding other tower PIs that do not have data in the dataset to the access list. (As can be seen from the more recent entry above, all site contacts now can obtain logins on the fluxdata site).
Posted at 7:52 AM by Deb Agarwal | Category: FAQ | Permalink | Email this Post | Comments (0)

2/29/2008

FLUXNET Site curators and ancillary curators explained . . .
You will notice on the site that we have a report that lists sites by curator or by country and curator.

Early in the process of collecting the data and ancillary data for the fluxnet synthesis effort we were having the problem that we were getting different data and ancillary data from different people.  The idea of the curator is to specify a single primary point of contact responsible for interacting with the site PI and receiving the site's flux/met data for the fluxnet synthesis effort.  The ancillary curator is the equivalent contact for the ancillary data for the site. Often the curator and ancillary curator are the same person.  There are two key goals with the establishment of the curator and anc curator roles.

1. Provide the site PI with a single point of contact to the fluxnet synthesis effort.
2. Designate a single authority within the group gathering fluxnet synthesis information that is responsible for determining the answers to questions about a site and obtaining information and data for the site.

The curator and ancillary curator are also responsible for  approving any changes made to information and data for a site and propagating this information to the various FLUXNET databases.
Posted at 1:47 PM by Deb Agarwal | Category: FAQ | Permalink | Email this Post | Comments (0)

2/19/2008

Update to VPD units in .mat files . . .
The units reported in the fluxnet hourly .mat files for VPD are incorrect.  The correct units should be hPa and not kPa. We will be updating the files to correct the problem soon.
Posted at 4:12 PM by Deb Agarwal | Category: FAQ | Permalink | Email this Post | Comments (0)
1 - 10 Next