Encoding of Swath Data in CF

Size: px

Start display at page:

Download "Encoding of Swath Data in CF"

Gyles Miller
5 years ago
Views:

1 Encoding of Swath Data in CF 2017 EarthCube netcdf-cf Workshop Aleksandar Jelenak, The HDF Group Daid Santek, Uniersity of Wisconsin/SSEC Kent Yang, The HDF Group Robert Carp, Uniersity of Wisconsin/SSEC

2 What We Call Swath Data? 2 Electromagnetic radiation collected from a specific direction into a solid angle and then measured at a number of interals of the electromagnetic spectrum Data collected by instruments on satellites, airplanes, and unmanned aerial systems Original instrument iewing geometry

3 Current Status 3 Second draft finished last month Undergoing community reiew Community: NASA ESDS Dataset Interoperability Working Group CF Satellite Personal contacts

4 Next Steps 4 Complete community reiew of the second draft Announce on the CF mailing list Engage the CF goerning body on the best approach to make this proposal part of the official conention

5 Resources 5 Document s home: CF/blob/master/swath/swath.adoc Pretty print ersion: Comments/suggestions/corrections: (Label issues with Ext-Swath)

6 Resources: Sample Files 6 Skinny examples: Real swath examples:

7 Swath Data Encodings 7

8 Disambiguation: Field-of-View (FOV) s. Field-of-Regard (FOR) 8 FOV CrIS footprint for the FOR 1 to 30 typical of one scan. From Han, Y. et al. (2013), doi: /2013jd020344

9 Proposed Encodings 9 Swath Encoding Radiometric Domain Geophysical Domain Multiband Multiband Image Swath Profile FOR * Profile Image Profile * field-of-regard Image Swath Multiband Profile

10 Time Coordinate 10 The rank of time coordinate can range from one to the rank of its swath ariable The slowest arying dimension must represent along-track platform moement International Atomic Time (TAI) not supported by CF but used in some swath data files

11 Spectral Coordinate 11 Describes the spectrum interals at which electromagnetic radiation is measured Must be present in radiometric swath data Type: radiometric physical property or alphanumeric The data can be either monotonic or non-monotonic

12 Spectral Coordinate 12 Monotonic alues Non-monotonic alues dimensions: band = 5 ; dimensions: num_band = 5 ; float band(band) ; band:standard_name = "sensor_band_..." ; band:units = "μm" ; float band(num_band) ; band:standard_name = "sensor_band_..." ; band:units = "cm-1" ; Standard names to use: sensor_band_central_radiation_waelength, sensor_band_central_radiation_waenumber, sensor_band_central_radiation_frequency, radiation_frequency, radiation_waelength.

13 Alphanumeric Spectral Coordinate 13 netcdf Enhanced Model netcdf Classic Model dimensions: num_band = 5 ; dimensions: num_band = 5 ; band_strlen = 10 ; string band(num_band) ; band:standard_name = "sensor_band_identifier" ; char band(num_band, band_strlen) ; band:standard_name = "sensor_band_identifier" ;

14 Geospatial Coordinates 14 Horizontal component required, ertical component optional Vertical component: Any CF-supported type Horizontal component: latitude-longitude, map projection Latitude and longitude coordinates: Rank at least two The slowest arying dimension represents along-track platform moement

15 Radiometric Encoding: Multiband 15 dimensions: time = 120 ; scan = 512 ; band = 8 ; float band(band) ; float lat(time, scan) ; float lon(time, scan) ; double time(time) ; float swath_data(time, scan, band) ; swath_data:coordinates = "lon lat" ;

16 Radiometric Encoding: Multiband Image 16 dimensions: time = 1 ; nrows = 2048 ; ncols = 2048 ; band = 10 ; float band(band) ; float lat(time, nrows, ncols) ; float lon(time, nrows, ncols) ; double time(time) ; float swath_data(time, nrows, ncols, band) ; swath_data:coordinates = "lon lat" ;

17 Geophysical Encoding: Swath 17 dimensions: time = 512 ; scan = 1024 ; double time(time) ; float lat(time, scan) ; float lon(time, scan) ; float swath_data(time, scan) ; swath_data:coordinates = "lon lat" ;

18 Geophysical Encoding: Image Swath 18 dimensions: time = 1 ; nrows = 1024 ; ncols = 3600 ; float lat(time, nrows, ncols) ; float lon(time, nrows, ncols) ; double time(time) ; float swath_data(time, nrows, ncols) ; swath_data:coordinates = "lon lat" ;

19 Geophysical Encoding: Profile 19 dimensions: time = UNLIMITED ; scan = 512 ; press = 15 ; float press(press) ; float lat(time, scan) ; float lon(time, scan) ; double time(time) ; float swath_data(time, scan, press) ; swath_data:coordinates = "lon lat" ;

20 Geophysical Encoding: Multiband Profile 20 dimensions: time = UNLIMITED ; scan = 512 ; band = 5 ; press = 15 ; float band(band) ; float press(press) ; float lat(time, scan) ; float lon(time, scan) ; double time(time) ; float swath_data(time, scan, press, band) ; swath_data:coordinates = "lon lat" ;

21 Geophysical Encoding: Image Profile 21 dimensions: time = 1 ; FOR = 1024 ; FOV = 3600 ; press = 100 ; float press(press) ; float lat(time, FOR, FOV) ; float lon(time, FOR, FOV) ; double time(time) ; float swath_data(time, FOR, FOV, press) ; swath_data:coordinates = "lon lat" ;

22 Geophysical Encoding: Field-of-Regard Profile 1 22 dimensions: time = 10 ; FOR = 30 ; press = 15 ; FOV_atrack = 3 ; FOV_xtrack = 3 ; float press(press) ; float lat(time, FOR, FOV_atrack, FOV_xtrack) ; float lon(time, FOR, FOV_atrack, FOV_xtrack) ; double time(time) ; float swath_data(time, FOR, FOV_atrack, FOV_xtrack, press) ; swath_data:coordinates = "lon lat" ;

23 Geophysical Encoding: Field-of-Regard Profile 2 23 dimensions: time = 10 ; FOR = 30 ; press = 15 ; FOV_atrack = 3 ; FOV_xtrack = 3 ; short FOV_atrack(FOV_atrack): short FOV_xtrack(FOV_xtrack): float press(press) ; float lat(time, FOR) ; float lon(time, FOR) ; double time(time) ; float swath_data(time, FOR, FOV_atrack, FOV_xtrack, press) ; swath_data:coordinates = "lon lat" ;

24 Encoding Field-of-View Geospatial Extent 24

25 Field-of-View Geospatial Extent 25 Field-of-View (FOV) is typically represented as a point Points hae no geospatial extent but real FOVs do Current CF supports describing FOV geospatial extent if: One geopolygon without any holes Same number of ertices for all FOVs

Example with FOV Geospatial Extents 26 dimensions: atrack = 512 ; xtrack = 1024 ;

float lat(atrack, xtrack) ; lat:bounds = "lat_ertex" ; lon float lon(atrack,

float lon_ertex(atrack, xtrack, ertices) ; float swath_data(atrack, xtrack) ;

26 Example with FOV Geospatial Extents 26 dimensions: atrack = 512 ; xtrack = 1024 ; ertices = 4 ; double time(atrack) ; (atrack, xtrack, 2) (atrack, xtrack, 1) lat float lat(atrack, xtrack) ; lat:bounds = "lat_ertex" ; lon float lon(atrack, xtrack) ; lon:bounds = "lon_ertex" ; float lat_ertex(atrack, xtrack, ertices) ; float lon_ertex(atrack, xtrack, ertices) ; float swath_data(atrack, xtrack) ; swath_data:coordinates = "time lon lat" ; (atrack, xtrack) (atrack, xtrack, 3) (atrack, xtrack, 0)

27 Group Hierarchies 27

28 Swath Files and Groups 28 A feature of the NetCDF Enhanced Data Model Widely used in swath files Not supported by the current CF conention

29 Simple Rules for Groups in Swath Files 29 Store swath data ariables, their coordinates, or any other related ariable in any group Keep ariable attributes with their swath ariables Use full ariable names whereer they need to be referenced Full ariable name: A name that represents the complete hierarchy of a ariable starting from the top group

30 Example with Groups 30 dimensions: ertex = 4 ; time = 392 ; band = 4 ; xtrack = 35 ; group: science { float science_data(time, xtrack) ; :coordinates = "/time /geolocation/lat /geolocation/lon" ; :ancillary_ariables = "/ancillary/quality" ; double time(time) ; float band(band) ; } group: ancillary { float quality(time, xtrack, band) ; :coordinates = "/time /geolocation/lat /geolocation/lon /band" ; } group: geolocation { float lat_ertex(time, xtrack, ertex) ; float lon_ertex(time, xtrack, ertex) ; float lat(time, xtrack) ; :bounds = "/geolocation/lat_ertex" ; float radiance(time, xtrack, band) ; :coordinates = "/time /geolocation/lat /geolocation/lon /band" ; :ancillary_ariables = "/ancillary/quality" ; } float lon(time, xtrack) ; :bounds = "/geolocation/lon_ertex" ;

31 31 THANK YOU! Questions or Comments?

Dataset Interoperability Working Group

Dataset Interoperability Working Group Co-Chairs: Charlie Zender and Peter Leonard Ed Armstrong, Mary Jo Brodzik, Joe Glassy, Aleksander Jelenak, Siri Jodha Khalsa, Wenli Yang; Steve Berrick, Chris Lynnes,