Folks:
I have a very general comment on CF Swath related to geolocating pixels in a swath.
Level 1/2 product generation systems that output remotely sensed swath data from polar orbiting systems often have a concern/requirements related to keeping the volume of data to a minimum.
If I am reading the CF swath proposal correctly, it would seem there is an assumption that lat/lon coordinates for each pixel is required to be CF compliant. This adds significantly to the size of a NetCDF-CF product file containing swath data.
Has there been any thought to define some type of a polar orbiting satellite projection that includes requisite time, orbital, and sensing map parameters in addition to explicit lat/lon values in the product file ?
Note that this question is not just limited to swath data coming from polar orbiting satellites.
v/r
randy
> On Apr 30, 2018, at 1:56 PM, Charlie Zender <zender at uci.edu> wrote:
>
> Dear CFers,
>
> We wish to draw your attention to and invite feedback on two proposals
> to extend CF:
>
> CF Swath, for encoding remotely-sensed (a.k.a. swath) data
> https://github.com/Unidata/EC-netCDF-CF/blob/master/swath/swath.adoc
>
> CF2-Group, for files with netCDF4 Groups
> https://github.com/diwg/cf2
>
> Questions/comments may be made as GitHub issues at their respective
> repositories. Suggested changes may be made as GitHub Pull-Requests
> (PRs).
>
> Sincerely,
> Charlie, Daniel, and Aleksandar
> --
> Charlie Zender, Earth System Sci. & Computer Sci.
> University of California, Irvine 949-891-2429 )'(
> _______________________________________________
> CF-metadata mailing list
> CF-metadata at cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
_____________________________________
Randy C Horne (rhorne at excaliburlabs.com)
Principal Engineer, Excalibur Laboratories Inc.
voice & fax: (321) 952.5100
cell: (321) 693.1074
url:
http://www.excaliburlabs.com
Received on Mon May 21 2018 - 10:41:27 BST
