Re: [cf-satellite] cf-satellite Digest, Vol 28, Issue 10

NOTE: The cf-satellite mailing list is no longer active. The list archives are made available for historical reasons.

Hi,



As mentioned in my Email 2 weeks ago, I attended the annual GSICS joint meeting 
attended by EUMETSAT, NOAA, NASA, CMA, JMA, and KMA; note our work here is 
visible to the WMO and CGMS.  We discussed the process for submitting CF 
satellite standard name proposals and the already submitted proposed satellite 
CF standard names by NOAA and EUMETSAT, and here is what I can report.



Based on our experience, the submission of satellite CF standard name proposals 
is a long, difficult and frustrating process.  Feedback is often received that 
leave the proposed CF updates in limbo as questions, opinions and taste are 
presented that do not have an answer or solution without further discussion.



In addition to this, the concept of providing a satellite vocabulary in the 
standard names guidelines would help with defining and clarifying the proposed 
satellite standard names.



Therefore I suggest the following:



1. Feedback to proposals shall provide comments/opinions AND possible solutions 
to the issues raised in these comments/opinions to allow the submissions to be 
promptly reworked.  Feedback leading to limbo state can be ignored (I’m sorry 
for the bluntness of this suggestion but we have to be efficient and pragmatic 
in how to use our time).



2. The following terms shall be included in the Guidelines for Construction of 
CF Standard Names

   (see: http://cf-pcmdi.llnl.gov/documents/cf-standard-names/guidelines). I 
suggest a new section under Chemical Species called “Satellite Names and 
Phrases”
Satellite Names and Phrases
The following names are used to identify data acquired from satellites in the 
CF satellite standard names conventions.
Name

Alternative Name

Comment

satellite

platform

The object on which the instruments/sensors are attached.

instrument

sensor

The observing device, mounted on the satellite/platform.

detector

The element of the instrument observing a specific band.

band

channel

The spectral region covered by the observation.
Channel may be used as a subset within a band.


Phrase

Meaning – Please provide a better definition if you can.

satellite_point

The absolute latitude and longitude of the satellite/platform.

measurement_point

The geo-referenced latitude and longitude onto a standard coordinate system 
where the measurement is taken.

toa

top of atmosphere – see Surface in the Qualifications section for more 
information.

  Other suggestions are welcome.
For the proposed names submitted by EUMETSAT, the re-worked versions are to 
split them into 3 separate submissions to allow easier acceptance and these are 
as follows:
Submission 1 (Satellite / Platform related):

azimuth_angle

  * degrees

  * Azimuth angle is the angle measured towards the east, from north, along the 
astronomical horizon to the intersection of the great circle passing through 
the point and the astronomical zenith with the astronomical horizon.



platform_measurement_latitude

  * degrees_north

  * Latitude of the data acquired at the measurement point – coordinate system 
shall be defined in the variable comment attribute.



platform_measurement_longitude

  * degrees_east

  * Longitude of the data acquired at the measurement point – coordinate system 
shall be defined in the variable comment attribute.



platform_measurement_altitude

  * m

  * Altitude of the platform above mean sea level.
Submission 2 (Band related):

band_spectral_width

  * cm-1

  * Bandwidth of the spectral channel taken by the detector
Submission 3 (Top of Atmosphere related):

toa_spectral_irradiance

  * mW m-2 (cm-1)-1

  * Irradiance which is relevant for any sensor measuring in the UV-VIS and 
NIR. This parameter is reported by integrating over the whole sphere.



toa_spectral_reflectance

  * 1 (dimensionless)

  * Ratio of radiance to irradiance I/I0, reflection from a thick layer where 
the layer, here the atmosphere, is part of the reflection's property.



toa_outgoing_inband_radiance

  * mW m-2 sr-1

  * "outgoing" means emitted toward outer space; the radiance is integrated 
over a discrete band.



toa_reflectance

  * 1

  * Reflectance is the ratio of the energy of the reflected to the incident 
radiation at the top of atmosphere. A coordinate variable of 
radiation_wavelength or radiation_frequency can be used to specify the 
wavelength or frequency respectively, of the radiation.





If no major issues (note issues should come with suggested solutions) on the 
proposals have been received within two weeks, I will assume we as a community 
think the proposals would benefit users and developers of satellite data, and I 
shall submit them for official acceptance.



Regards,



Peter Miu

Data Services Operations Engineer



EUMETSAT

EUMETSAT Allee 1

64295 Darmstadt

Germany



Tel: +49 6151 807 3290

Fax: +49 6151 807 7410

Email: peter.miu@xxxxxxxxxxxx<mailto:peter.miu@xxxxxxxxxxxx>



Web: http://www.eumetsat.int

Follow EUMETSAT on Twitter https://twitter.com/@eumetsat_users

Ordering Data from EUMETSAT https://eoportal.eumetsat.int/



-----Original Message-----
From: cf-satellite-bounces@xxxxxxxxxxxxxxxx 
[mailto:cf-satellite-bounces@xxxxxxxxxxxxxxxx] On Behalf Of 
cf-satellite-request@xxxxxxxxxxxxxxxx
Sent: Wednesday, February 27, 2013 8:00 PM
To: cf-satellite@xxxxxxxxxxxxxxxx
Subject: cf-satellite Digest, Vol 28, Issue 10



Send cf-satellite mailing list submissions to

      cf-satellite@xxxxxxxxxxxxxxxx<mailto:cf-satellite@xxxxxxxxxxxxxxxx>



To subscribe or unsubscribe via the World Wide Web, visit

      http://mailman.unidata.ucar.edu/mailman/listinfo/cf-satellite

or, via email, send a message with subject or body 'help' to

      
cf-satellite-request@xxxxxxxxxxxxxxxx<mailto:cf-satellite-request@xxxxxxxxxxxxxxxx>



You can reach the person managing the list at

      
cf-satellite-owner@xxxxxxxxxxxxxxxx<mailto:cf-satellite-owner@xxxxxxxxxxxxxxxx>



When replying, please edit your Subject line so it is more specific than "Re: 
Contents of cf-satellite digest..."





Today's Topics:



   1. Re: cf-satellite Digest, Vol 28, Issue 9 (Peter Miu)





----------------------------------------------------------------------



Message: 1

Date: Wed, 27 Feb 2013 09:55:22 +0100

From: Peter Miu <Peter.Miu@xxxxxxxxxxxx<mailto:Peter.Miu@xxxxxxxxxxxx>>

To: "'cf-satellite@xxxxxxxxxxxxxxxx'" 
<cf-satellite@xxxxxxxxxxxxxxxx<mailto:cf-satellite@xxxxxxxxxxxxxxxx>>

Subject: Re: [cf-satellite] cf-satellite Digest, Vol 28, Issue 9

Message-ID:

      
<354F36C3E59AE94285336EF9BD449F6F452B8A24@xxxxxxxxxxxxxxxxxxxxxxxxxxx<mailto:354F36C3E59AE94285336EF9BD449F6F452B8A24@xxxxxxxxxxxxxxxxxxxxxxxxxxx>>

Content-Type: text/plain; charset="Windows-1252"



Hi all,



Just to provide you with an update.



I have received inputs on the proposed CF standard names and units from:



- Mike Grant.

- Jim Biard.

- Randy Horne.



I am attending the GSICS joint meeting next week and I shall discuss the 
proposals and these inputs with the GSICS Data working group members (NOAA, 
NASA, JMA, CMA, KMA, etc.).  I will then compile updates, discuss these with 
our EUMETSAT WMO representative and present it on this list again before 
submission to the CF TRAC (expected due date is mid - end of March).



Regards,

Peter Miu.



-----Original Message-----

From: 
cf-satellite-bounces@xxxxxxxxxxxxxxxx<mailto:cf-satellite-bounces@xxxxxxxxxxxxxxxx>
 [mailto:cf-satellite-bounces@xxxxxxxxxxxxxxxx] On Behalf Of 
cf-satellite-request@xxxxxxxxxxxxxxxx<mailto:cf-satellite-request@xxxxxxxxxxxxxxxx>

Sent: Saturday, February 23, 2013 8:00 PM

To: cf-satellite@xxxxxxxxxxxxxxxx<mailto:cf-satellite@xxxxxxxxxxxxxxxx>

Subject: cf-satellite Digest, Vol 28, Issue 9



Send cf-satellite mailing list submissions to

      cf-satellite@xxxxxxxxxxxxxxxx<mailto:cf-satellite@xxxxxxxxxxxxxxxx>



To subscribe or unsubscribe via the World Wide Web, visit

      http://mailman.unidata.ucar.edu/mailman/listinfo/cf-satellite

or, via email, send a message with subject or body 'help' to

      
cf-satellite-request@xxxxxxxxxxxxxxxx<mailto:cf-satellite-request@xxxxxxxxxxxxxxxx>



You can reach the person managing the list at

      
cf-satellite-owner@xxxxxxxxxxxxxxxx<mailto:cf-satellite-owner@xxxxxxxxxxxxxxxx>



When replying, please edit your Subject line so it is more specific than "Re: 
Contents of cf-satellite digest..."





Today's Topics:



   1. Re: cf-satellite Digest, Vol 28, Issue 5 (Mike Grant)





----------------------------------------------------------------------



Message: 1

Date: Fri, 22 Feb 2013 19:20:38 +0000

From: Mike Grant <mggr@xxxxxxxxx<mailto:mggr@xxxxxxxxx>>

To: Jim Biard <jim.biard@xxxxxxxx<mailto:jim.biard@xxxxxxxx>>

Cc: "cf-satellite@xxxxxxxxxxxxxxxx<mailto:cf-satellite@xxxxxxxxxxxxxxxx>" 
<cf-satellite@xxxxxxxxxxxxxxxx<mailto:cf-satellite@xxxxxxxxxxxxxxxx>>

Subject: Re: [cf-satellite] cf-satellite Digest, Vol 28, Issue 5

Message-ID: <5127C506.3070107@xxxxxxxxx<mailto:5127C506.3070107@xxxxxxxxx>>

Content-Type: text/plain; charset="ISO-8859-1"



On 20/02/13 17:52, Jim Biard wrote:

> This issue with altitude is exactly why it is critical to include the

> geographic coordinate system used - both the horizontal and vertical

> datum.  That's where the issue lies.  It's not with the concept of

> altitude, per se.



This is the key point, but I think it's perhaps one that's a general issue for 
the CF guys to sort out rather than something we need to deal with when 
proposing a standard name.  One could include a short snippet in the 
description along the lines of "For this variable to be meaningful, it must be 
associated with a {horizontal|vertical} datum.".



Again, one should approach this point carefully as it's likely to cause a 
torrent of discussion and bog that name down in a swamp of difficulties.  At 
the least, try to isolate it from others or, if the discussion starts, try your 
hardest to separate the datum issue into another thread separate from the name 
proposal!



> This can be quite a mess to navigate through, and I appreciate you and

> Aleksandar's (and others!) efforts to develop these standard names!



Hear hear!



Cheers,



Mike.

--

PGP: 0xD4925D35 (5A17 756C 3F78 27DB C641 F50C 05EC 4F23 D492 5D35)





Latest news: www.pml.ac.uk<http://www.pml.ac.uk> and @PlymouthMarine



Plymouth Marine Laboratory (PML) is a company limited by guarantee registered 
in England & Wales, company number 4178503. Registered Charity No. 1091222. 
Registered Office: Prospect Place, The Hoe, Plymouth  PL1 3DH, UK.



This message is private and confidential. If you have received this message in 
error, please notify the sender and remove it from your system. You are 
reminded that e-mail communications are not secure and may contain viruses; PML 
accepts no liability for any loss or damage which may be caused by viruses.







------------------------------



_______________________________________________

cf-satellite mailing list

cf-satellite@xxxxxxxxxxxxxxxx<mailto:cf-satellite@xxxxxxxxxxxxxxxx>

For list information or to unsubscribe,  visit: 
http://www.unidata.ucar.edu/mailing_lists/





End of cf-satellite Digest, Vol 28, Issue 9

*******************************************







------------------------------



_______________________________________________

cf-satellite mailing list

cf-satellite@xxxxxxxxxxxxxxxx<mailto:cf-satellite@xxxxxxxxxxxxxxxx>

For list information or to unsubscribe,  visit: 
http://www.unidata.ucar.edu/mailing_lists/





End of cf-satellite Digest, Vol 28, Issue 10

********************************************
  • 2013 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the cf-satellite archives: