NOTE: The cf-satellite mailing list is no longer active. The list archives are made available for historical reasons.
>While I have bands at three different resolutions namely 1 Km, 4 Km and 8 >Km. >What could be the best way to get the things in place? >Will I have to create lat/lon arrays for three different resolutions. >That will occupy of extra space. >From a user's perspective, I'd recommend creating coordinates for each >resolution. To alleviate the space issues, use compression. -Corey On Fri, 27 Apr 2012 08:11:24 +0530 ghansham sangar <ghanshamsangar@xxxxxxxxx> wrote: >R/Sir >Thanks a lot Sir for a very helpful mail and a very quick reply....... > >The other thing is how to correlate bands of different resolutions with >coordinate variables. >My Navigation is in the form of lat/lon disks which is at 4 km resolution. >While I have bands at three different resolutions namely 1 Km, 4 Km and 8 >Km. >What could be the best way to get the things in place? >Will I have to create lat/lon arrays for three different resolutions. >That will occupy of extra space. Are there any cell methods to correlate >the bands of different resolution >with same set of navigation information. > > >regards >Ghansham >On Fri, Apr 27, 2012 at 12:59 AM, Martin Raspaud <martin.raspaud@xxxxxxx>wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 26/04/12 04:41, ghansham sangar wrote: >> > R/Sir >> > >> > Are there any sample CF complaint satellite L1B (swath) >> > multi-spectral datasets that demonstrate the way we put the band >> > information along with their wavelengths and calibration >> > information. There can be more than one calibration attached to a >> > single band (like radiance and brightness temperature attached to >> > IR channels). >> >> Hi Ghansham, >> >> I don't have any such data, but I guess we could do something like: >> >> >> short ImageData(band, x, y); >> ImageData:coordinates = "band lat lon time wavelength"; >> ImageData:valid_min = 1s; >> ImageData:_FillValue = 0s; >> ImageData:missing_value = 0s; >> ImageData:add_offset = 34.02f, 35.02f, 36.02f; >> ImageData:scale_factor = 1.54f, 1.64f, 1.74f; >> ImageData:radiance_formula = "ImageData * radiance_factor + >> radiance_offset"; >> ImageData:radiance_factor = 2.08f, 2.09f, 2.10f; >> ImageData:radiance_offset = 0.3f, 0.6f, 0.9f; >> ImageData:brightness_temperature_formula = "bt_offset + radiance * >> bt_coef1 + radiance^2 * bt_coef2"; >> ImageData:bt_offset = 1.0f, 1.5f, 1.8f; >> ImageData:bt_coef1 = 2.0f, 2.5f, 2.8f; >> ImageData:bt_coef2 = 3.0f, 3.5f, 3.8f; >> >> Maybe we should add something like formula_terms also ? Or is there >> something more general to describe formulas ? >> >> Best regards, >> Martin >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.14 (GNU/Linux) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >> >> iQEcBAEBAgAGBQJPmaIUAAoJEBdvyODiyJI4krAIAL9pqt5Rs5JqyumUVliNKXqX >> cceRvzCi9p5KK0trp1tFJaYZzSQS74M++ntMlzKZJpXDRSnlO61eRbT+NNNia/fI >> sYgErE/msr3oQO3NDZ/p8i1l8sIrOaM1lkxeOxRaCXFlB4spXDllsNMefNv5lKoW >> 5NWhBzeRIKCAakxJZ8PZaYYB1sRJlx25BelwkxgAowpo6mow/Ci1jEVIUyFQesPx >> x7dJx8qtPuOFgnmBEolxcY7svuk7zN3D/1p2E+i04fvh1pnCz3d++zl+WujNfimm >> suyfgp2J/z4Z9RPNJFxWKIW9nK1k73udddWzj5gBNdtrckL42NlX9yjxDDCydQE= >> =s+37 >> -----END PGP SIGNATURE----- >> >> _______________________________________________ >> cf-satellite mailing list >> cf-satellite@xxxxxxxxxxxxxxxx >> For list information or to unsubscribe, visit: >> http://www.unidata.ucar.edu/mailing_lists/ >> >>
cf-satellite archives: