NOTE: The cf-satellite mailing list is no longer active. The list archives are made available for historical reasons.
It's possible I'm not on the same track you are, but band is a term used in shorter-wavelength (optical and NIR) remote sensing to refer to an area of the EM spectrum being measured by the instruement. A lot of these sensors are multi-spectral, in the sense that they measure more than one "band" at a given location. Like optical sensors, microwave sensors are also multi-spectral, but our community doesn't use the term "band". In either case, it is a different (additional) dimension from the line/sample dimensions of the swath array of measured values.
(Somebody please let me know if I'm off-track. Pardon the pun.) Mary Jo On Fri, 15 Jul 2011, Upendra.Dadi@xxxxxxxx wrote:
Date: Fri, 15 Jul 2011 11:44:37 -0400 From: Upendra.Dadi@xxxxxxxx To: Upendra.Dadi@xxxxxxxx Cc: cf-satellite@xxxxxxxxxxxxxxxx Subject: Re: [cf-satellite] Proposal for naming convention for swath dimensions Sorry, I really meant using "band" for representing bands. ----- Original Message ----- From: Upendra.Dadi@xxxxxxxx Date: Friday, July 15, 2011 11:40 am Subject: Re: [cf-satellite] Proposal for naming convention for swath dimensionsCF gives guidelines on constructing standard names: http://cf-pcmdi.llnl.gov/documents/cf-standard-names/guidelines CF standard name table has "latitude", "longitude", "depth" & "time" as standard_names for specifying spatio-temporal coordinates. Why not just use "swath"? Upendra ----- Original Message ----- From: Russ Rew <russ@xxxxxxxxxxxxxxxx> Date: Friday, July 15, 2011 11:25 am Subject: Re: [cf-satellite] Proposal for naming convention for swath dimensionsI suggested in the ESIP Federation CF-Satellite discussionyesterday(July 14, 2011) that the names "line" and "sample" could begoodcandidates for the names of the geometrical dimensions of swathdatavariables. I think that these are more generic than previous suggestions, and accommodate a wider range of data acquisitionschemes.There can be sensors out there for which even these names are "incorrect", but the vast majority of the data is produced as arasterof some sort. This is common terminology in many other arenas (photogrammetry, for example).Actually, the CF Conventions don't standardize any dimension or variablenames, according to the beginning of section 1.3: No variable or dimension names are standardized by this convention. Instead we follow the lead of the NUG [NetCDF Users Guide] and standardize only the names of attributes and some of the values taken by those attributes. So "standard_name" attributes for the associated coordinatevariables> may be what we need. This also has the advantage of permittingmultipleline and sample dimensions and multiple associated coordinate variables in the same file, for multiple instruments or resolutions. The process for getting standard names approved is simpler andfaster> than writing CF Trac proposals for inclusion in the CF Conventionstext. Although "line" and "sample" would be fine for dimension and coordinatevariable names, I think they would be too generic for standard names, which have to be very descriptive. Does anyone else familiarwith theCF idioms and customs for standard names for coordinate variablesand> have more descriptive suggestions?--Russ-- Jim Biard Government Contractor, STG Inc. Remote Sensing and Applications Division (RSAD) National Climatic Data Center 151 Patton Ave. Asheville, NC 28801-5001 jim.biard@xxxxxxxx 828-271-4900 _______________________________________________ cf-satellite mailing list cf-satellite@xxxxxxxxxxxxxxxx For list information or to unsubscribe, visit:http://www.unidata.ucar.edu/ma> iling_lists/ _______________________________________________ cf-satellite mailing list cf-satellite@xxxxxxxxxxxxxxxx For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/_______________________________________________ cf-satellite mailing list cf-satellite@xxxxxxxxxxxxxxxx For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/_______________________________________________ cf-satellite mailing list cf-satellite@xxxxxxxxxxxxxxxx For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Mary Jo Brodzik, Special Projects Lead, 303-492-8263 NSIDC/CIRES, Univ. of Colo. at Boulder, 449 UCB, Boulder, CO 80309-0449 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
cf-satellite archives: