ࡱ> VXU'` Hbjbj .J!    Tt<('''''''$E)h+'Qqqq'I(_$_$_$qX'_$q'_$_$&&' aѻg*  z&'_(0(&,[,C#[,&'[,&'_$t''U$ (qqqq$D AmeriFlux Data Product File Naming and Versioning Conventions Level 2 products: AMF_AAaaa_BBBB_L2_CC_V###.extension AMF = AmeriFlux Network Code AAaaa = FLUXNET Site ID AA = Country Code BR=Brazil CA=Canada CR=Costa Rica MX=Mexico US=United States aaa = Site code BBBB = Year (e.g., 1999) L2 = AmeriFlux Product Level CC = Data Continuity Indicator WG = time series contains record gaps GF = time series has been gap-filled for continuity HY = time series contains some gap-filled variables and some records with gaps V### = Version number (v001, v002, v003, ... v999) Extension = csv for comma-separated value files nc for netCDF files Example: AMF_USMe2_2006_L2_GF_v001.csv Level 3 products: Data files AMF_AAaaa_BBBB_L3_CC_V###.extension AMF = AmeriFlux Network Code AAaaa = FLUXNET Site ID AA = Country Code BR=Brazil CA=Canada CR=Costa Rica MX=Mexico US=United States aaa = Site code BBBB = Year L3 = AmeriFlux Product Level CC = Data Continuity Indicator WG = time series contains record gaps GF = time series has been gap-filled for continuity HY = time series contains some gap-filled variables and some records with gaps (i.e., hybrid) V### = Version number (v001, v002, v003, .... v999) Extension = csv for comma-separated value files mat for Matlab files nc for netCDF files Example: AMF_USMe2_2006_L3_HY_v001.csv Level 3 products: (continued) Graphics files AMF_AAaaa_BBBB_L3_CC_ddd_V###.png AMF = AmeriFlux Network Code AAaaa = FLUXNET Site ID AA = Country Code BR=Brazil CA=Canada CR=Costa Rica MX=Mexico US=United States aaa = Site code BBBB = Year L3 = AmeriFlux Product Level CC = Data Continuity Indicator WG = time series contains record gaps GF = time series has been gap-filled for continuity HY = time series contains some gap-filled variables and some records with gaps (i.e., hybrid) ddd = Data Type met = Meteorological data flx = Flux data V### = Version Number (v001, v002, v003, ....v999) Example: AMF_USMe2_2006_L3_GF_flx_v001.png Level 4 products: Data files AMF_AAaaa_BBBB_L4_T_V###.extension AMF_AAaaa_BBBB_L4_V###.extension AMF = AmeriFlux Network Code AAaaa = FLUXNET Site ID AA = Country Code BR=Brazil CA=Canada CR=Costa Rica MX=Mexico US=United States aaa = Site code BBBB = Year L4 = AmeriFlux Product Level T = Temporal Aggregation (h, d, w, or m) V### = Version Number (v01, v02, v03, .....v999) Extension = txt for files with fixed format ASCII characters mat for Matlab files nc for netCDF files Example: AMF_USMe2_2006_L4_d_v001.csv Level 4 products: continued Graphics files AMF_AAaaa_BBBB_L4_CCC_pp_VVV.png AMF_AAaaa_BBBB_L4_CCCCC_VVV.png AMF = AmeriFlux Network Code AAAAA = FLUXNET Site ID BBBB = Year L4 = AmeriFlux Product Level CCC= Data type (met or flx) pp= Processing technique (st or or; st = standardized processing; or = original data submitted by PI; for example the storage term calculated in a standardized discrete approach versus storage terms provided by the PI) CCCCC = cumul or ustar VVV = Version number (v01, v02, v03) Examples: AMF_USMe2_2006_L4_flx_or_v01.png AMF_USMe2_2006_L4_cumul_v01.png Basic Rules for Versioning %Version numbers are assigned at the site level and not at the network level. Site  data sets may be comprised of data groups with different version numbers due to differences in the frequency of data submission (e.g., infrequently submitted biological/ecological estimates versus micrometeorological data submitted regularly). All flux and meteorological files comprising the site data set will have the same version number. Biological files or BADM templates may have version numbers that differ from those assigned to the flux and meteorological files. % Version numbers are consistent across product levels so users will know what lower level products were used to produce higher level products (e.g., v003 L3 and L4 files were derived from v003 L2 files). % The version number changes when the content of the data set, biological files, or BADM template changes in any way. The version number of individual files may change even though the content of the individual file remains the same. For example, the version number assigned to a site data set changes from v001 to v002 when the site submits another year of data even though no changes have been made to previous years. The primary reason for adopting this protocol is to enable users to refer to distinct data sets rather than have to cite a sites data collection by individual files (i.e., v003 rather than v003 for the 1999 data, v003 for the 2000 data, .... v001 for the 2008 data) Sample Scenarios First scenario AmeriFlux Principal Investigator Jane Doe submits re-processed data for 2002-2007 for site WWW. The initial submission for site WWW was labeled version 1 (v001). Each yearly data file for the level 2, 3, and 4 products based on the re-processed data is assigned a new version number (i.e., v002). Next year Jane Doe submits the 2008 data for site WWW with no changes to the re-processed 2002-2007 data. All corresponding 2002-2008 data files for L2-L4 data products are now assigned v003. Second scenario Version 1 files for site YYY already exist. AmeriFlux Principal Investigator John Doe submits new Level 1 files with changes only to the soil heat fluxes. The new corresponding L2 files are assigned a new version number (v002) since the content of these files changed, even though only for Fg. Even though Fg is not used presently in any of the processing for the L3 or L4 files, the L3 and L4 files for site YYY are also designated as v002 for consistency across data product levels and since the new v002 L2 files would yield the already posted L3 and L4 files. Third scenario Version 2 files exist for site ZZZ and cover the period 2001-2008. Changes are made to the ustar threshold determination procedures used by CarboEurope resulting in new L3 and L4 files for the site. Not only would the L=>@RSW\elwx  ) ܿ}n_SH@5heUh,CJ$aJ$h,CJ$aJ$h,h,CJ$aJ$h,CJ$aJ$mH sH h,h,CJ$aJ$mH sH h,h,CJ$aJ$mHsHh,heUCJ$aJ$mHsHheUCJ$aJ$mHsHh"CJ$aJ$mHsHh"heUCJ$aJ$mHsHh,CJ$aJ$mHsHh"h"CJ$aJ$mHsHheUheU6CJ$]aJ$heUheUCJ$aJ$heUhR5CJ$\aJ$h 5CJ$\aJ$>?@RSwx ) F e  E ^gdI`gdI ^`gd,gd,H) , E F d     + , 1 2 7 8 9 C D Q R 巬吅vjh,CJ$aJ$mHsHh"h"CJ$aJ$mHsHheUh^CJ$aJ$h^h^6CJ$]aJ$heUheU6CJ$]aJ$heU6CJ$]aJ$hI6CJ$]aJ$hh#CJ$aJ$heUh"CJ$aJ$h"CJ$aJ$hICJ$aJ$heUCJ$aJ$heUheUCJ$aJ$h^CJ$aJ$)E v  . A M W e o ^`gd,gd" &d P  ^`gdeU ^`gdh#gdeU    - . C W e o ʻ|qff^V^K^K^K^heUhICJ$aJ$h2-CJ$aJ$hICJ$aJ$heUheUCJ$aJ$heUh,CJ$aJ$h,CJ$aJ$mH sH h,h,CJ$aJ$mH sH heUCJ$aJ$h^CJ$aJ$h,CJ$aJ$h"CJ$aJ$mHsHh"h"CJ$aJ$mHsHh"heUCJ$aJ$mHsHh2-CJ$aJ$mHsHhICJ$aJ$mHsHh"h^CJ$aJ$mHsH 5 `  % & M N m n } ~ gd,gd"gd^gd)| ^`gdI ^`gdeU^gdI`gdIgdIgdeU   % & / 3 ? @ A D F G M N n v } ~ ºկՋxih,h,CJ$aJ$mH sH h,h"CJ$aJ$h,CJ$aJ$heUh^CJ$aJ$h^h^6CJ$]aJ$h^6CJ$]aJ$hh#6CJ$]aJ$h"CJ$aJ$h)| h)| CJ$aJ$h)| CJ$aJ$h^CJ$aJ$heUCJ$aJ$hh#CJ$aJ$hICJ$aJ$heUhICJ$aJ$& (9Eb>Oiy &d P gd^^gdh#`gdh#gdh#gd^ ^`gd,gd, 89DEGab-=}λᨻÂwiheUh^6CJ$]aJ$h^6CJ$]aJ$hI6CJ$]aJ$h"CJ$aJ$h)| h)| CJ$aJ$h)| CJ$aJ$heUhh#CJ$aJ$h2-CJ$aJ$hh#CJ$aJ$heUh^CJ$aJ$h^CJ$aJ$heUh,CJ$aJ$h,CJ$aJ$h,h,CJ$aJ$h,CJ$aJ$mH sH )>?@]u+\ ^`gd ^`gdgdgd"gd gd^ ./5?@]ǸvvkcTH=ch,hCJ$aJ$hCJ$aJ$mH sH h,hCJ$aJ$mH sH hCJ$aJ$hh"CJ$aJ$hhc(h CJ$aJ$mHsHh CJ$aJ$mHsHh^CJ$aJ$mHsHh2-CJ$aJ$mHsHhhc(hhc(CJ$aJ$mHsHhhc(h^CJ$aJ$mHsHhCJ$aJ$mHsHh"CJ$aJ$mHsHheUh^CJ$aJ$h^h^6CJ$]aJ$h^CJ$aJ$*+;OZ[i  #023;?D[\巯巜ʯݯxhPh)| CJ$aJ$h^hhc(6CJ$]aJ$h2-6CJ$]aJ$hhc(6CJ$]aJ$h)| CJ$aJ$h"CJ$aJ$h)| h)| CJ$aJ$h CJ$aJ$heUhhc(CJ$aJ$hPCJ$aJ$hhc(CJ$aJ$h2-CJ$aJ$h^CJ$aJ$heUh^CJ$aJ$*  ;[\y Cz`gdI,gd"gdhc(gd)| ^`gd2- ^`gd^\xy~ "08@HʺҲں}nbhZ CJ$aJ$mH sH h"h)| CJ$aJ$mH sH h"h"CJ$aJ$mH sH h"CJ$aJ$h)| h)| CJ$aJ$heUCJ$aJ$heUh)| CJ$aJ$h)| CJ$aJ$hPCJ$aJ$hI,CJ$aJ$h CJ$aJ$hhc(CJ$aJ$heUhhc(CJ$aJ$h"h"CJ$aJ$mHsHh"CJ$aJ$mHsH$@ HHgdZ gd> ^`gd)| gdhc(z|31:Jm$* 01DFu;ûӻóóۻۣˣ˳۳h}CJ$aJ$h([h 5CJ$\aJ$h([hTJ5CJ$\aJ$h CJ$aJ$honCJ$aJ$hTJCJ$aJ$h([CJ$aJ$h2-CJ$aJ$hi CJ$aJ$hI,CJ$aJ$hl6CJ$aJ$hZ h>CJ$aJ$mH sH honh>5CJ$\aJ$2 -FG ,Zf- . > K !!8!!!HzHHHHHh)| h>CJ$aJ$UhZ CJ$aJ$h*7CJ$aJ$h.~CJ$aJ$h}CJ$aJ$hTJCJ$aJ$h([CJ$aJ$h CJ$aJ$83 and L4 files be assigned a new version number (v003) but so would the L2 files used to generate the new L3 and L4 files in order to maintain the same version number across product levels. ,1h/ =!"#$% @@@ "NormalCJ_HaJmH sH tH DA@D Default Paragraph FontRi@R  Table Normal4 l4a (k@(No List!J>?@RSwx)FeEv.AMWeo5`%&MNmn}~ (9Eb>Oiy>?@]u + \   ; [ \ y C z @ A ] ^ ]&''(rs #000000000@0@0@0@0@0@0@00000000000000000000000000000000000@00000000000000000@0@0@0@0@0@0@0000@0@0@00000000000000000000@0@0@0@0@0@0000000000000000000000000000000000000000000000000&MEb+ \   ; [ \ #Z00 pZ00Z00Z00Z00 ſZ00 Z00Z00Z0 0 lѿZ0 0 Z0 0Z00Z00Z00pZ00Z00Z00Z00Z00Z00Z00Z000MZ00Z00Z00) \H!"E H Hnl$_ol$4`pl$ܴql$rl$sl$tl$ ul$vl$twl$xl$<yl$zl${l$rr#     ''# 9*urn:schemas-microsoft-com:office:smarttagsplaceB *urn:schemas-microsoft-com:office:smarttagscountry-region       S\]lmwx.7RUvx}CLMVWden  ),JS>Ail&'./>FO]b \ x 1 2 @ 8Agp^`oq#Svx5>vxCLMVWden`i ),>AORil=L V \ x   D K { ? _b^`#33333333333333333333333333333@Rx)Ev-/@W9Eby \ B ^ &##[# X z^`zo() ^`hH. pLp^p`LhH. @ @ ^@ `hH. ^`hH. L^`LhH. ^`hH. ^`hH. PLP^P`LhH.[#$B$(        %$i Z )| .~hc(I,-[`-l6*7VATJ([jon[oVpeU sP R^h#~x2-$INI},>"@ BBL a!`@``,@``4@`@UnknownGz Times New Roman5Symbol3& z Arial"qh&&F + +!242QHX)?eU2<Proposed file naming conventions for AmeriFlux data productstabtab Oh+'0 ( 4@ ` l x @Proposed file naming conventions for AmeriFlux data productstabNormaltab2Microsoft Office Word@@tT@g*@g*՜.+,0( hp  ORNL+ ' =Proposed file naming conventions for AmeriFlux data products Title  !"#$%'()*+,-/0123456789:;<=>?@ABCDFGHIJKLNOPQRSTWRoot Entry FЫӻg*YData &1Table.k,WordDocument.JSummaryInformation(EDocumentSummaryInformation8MCompObjq  FMicrosoft Office Word Document MSWordDocWord.Document.89q