⇐ ⇒

[CF-metadata] how to capture horizontal spatial resolution of imagery in a standard way

From: rhorne at excaliburlabs.com <rhorne>
Date: Wed, 1 May 2013 12:15:23 -0400

Mark:

  

I generally understand what you are suggesting, but a CDL example would be
helpful to me.

  

I like the idea of a general purpose, extensible CF construct.

  

Note that because many earth projections used to display imagery cause
pixels to vary in area they cover even though these images are still
considered to have a fixed horizontal spatial resolution. Usually, the
pixels at the earth projection control point(s) cover the exact area
associated with the image's resolution. In the case of GOES-R ground
system generated images, the pixels have a constant angular horizontal
spatial resolution, but the surface area they cover increases away from the
satellite's nadir (i.e. the projection's control point.)

  

v/r

  

rh

----------------------------------------
 From: "Hedley, Mark" <mark.hedley at metoffice.gov.uk>
Sent: Wednesday, May 01, 2013 11:31 AM
To: "Randy Horne" <rhorne at excaliburlabs.com>, "cf-metadata at cgd.ucar.edu"
<cf-metadata at cgd.ucar.edu>, "cf-satellite at unidata.ucar.edu"
<cf-satellite at unidata.ucar.edu>
Subject: RE: [CF-metadata] how to capture horizontal spatial resolution of
imagery in a standard way

Hello Randy Is the image regular in location and resolution (with respect
to a defined coordinate reference system)? If so, could an approach be to
create a regular coordinate type which can simply encode all of this
information in one place? such a type could be expanded at will to provide
all the points and all the resolutions required mark
________________________________________ From: CF-metadata
[cf-metadata-bounces at cgd.ucar.edu] on behalf of Randy Horne
[rhorne at excaliburlabs.com] Sent: 30 April 2013 19:33 To:
cf-metadata at cgd.ucar.edu; cf-satellite at unidata.ucar.edu Subject:
[CF-metadata] how to capture horizontal spatial resolution of imagery in a
standard way Although it works, using boundary variables to capture the
horizontal spatial resolution of imagery is inefficient. Using cell methods
with the keyword "interval" could be used to capture the horizontal spatial
resolution of imagery, but it implies the data values represent specific
points rather than areas. (I guess a "resolution" keyword could be added
for use with cell methods.) Another option is to establish a standard_name
for horizontal spatial resolution and relate the value to the data variable
using the "ancillary_variables" keyword. Does anyone have any thoughts on
this ? very respectfully, randy
_______________________________________________ CF-metadata mailing list
CF-metadata at cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20130501/b974389c/attachment.html>
Received on Wed May 01 2013 - 10:15:23 BST

This archive was generated by hypermail 2.3.0 : Tue Sep 13 2022 - 23:02:41 BST

⇐ ⇒