Hi HP-
I wrote up
inquiry 2475 for the expanding of the jython methods for VIIRS data interrogation.
I was testing with some DNB files and SVM files with and without the geolocation data combined in the files. I also downloaded 'deaggregated' files from CLASS which have each ~85 second granule as separate files. (I used 1.6 and the latest nightly.)
1. I did not see any differences in the Field Selector field listings among any of the data. All combinations of loading the data would list all the available variables. If you have some sample data files that show this behavior, I could try them here.
2. In the Jython shell I did see the 'incomplete' listing when using listVIIRSFieldsInFile(filename) with files that did not have the geolocation data combined. However, if I specified the individual geolocation file in the method, then I would get the missing variables listed. For example:
listVIIRSFieldsInFile('/Users/jayh/Data/joleen/SVM03_npp_d20140403_t1809429_e1811071_b12604_c20140404004022598570_noaa_ops.h5')
VIIRS-M3-SDR_All/ModeGran
VIIRS-M3-SDR_All/ModeScan
VIIRS-M3-SDR_All/NumberOfBadChecksums
VIIRS-M3-SDR_All/NumberOfDiscardedPkts
VIIRS-M3-SDR_All/NumberOfMissingPkts
VIIRS-M3-SDR_All/NumberOfScans
VIIRS-M3-SDR_All/PadByte1
VIIRS-M3-SDR_All/QF1_VIIRSMBANDSDR
VIIRS-M3-SDR_All/QF2_SCAN_SDR
VIIRS-M3-SDR_All/QF3_SCAN_RDR
VIIRS-M3-SDR_All/QF4_SCAN_SDR
VIIRS-M3-SDR_All/QF5_GRAN_BADDETECTOR
VIIRS-M3-SDR_All/Radiance
VIIRS-M3-SDR_All/Reflectance
VIIRS-M3-SDR_All/ReflectanceFactors
Data_Products/VIIRS-M3-SDR/VIIRS-M3-SDR_Aggr
Data_Products/VIIRS-M3-SDR/VIIRS-M3-SDR_Gran_0
[u'VIIRS-M3-SDR_All/ModeGran', u'VIIRS-M3-SDR_All/ModeScan', u'VIIRS-M3-SDR_All/NumberOfBadChecksums', u'VIIRS-M3-SDR_All/NumberOfDiscardedPkts', u'VIIRS-M3-SDR_All/NumberOfMissingPkts', u'VIIRS-M3-SDR_All/NumberOfScans', u'VIIRS-M3-SDR_All/PadByte1', u'VIIRS-M3-SDR_All/QF1_VIIRSMBANDSDR', u'VIIRS-M3-SDR_All/QF2_SCAN_SDR', u'VIIRS-M3-SDR_All/QF3_SCAN_RDR', u'VIIRS-M3-SDR_All/QF4_SCAN_SDR', u'VIIRS-M3-SDR_All/QF5_GRAN_BADDETECTOR', u'VIIRS-M3-SDR_All/Radiance', u'VIIRS-M3-SDR_All/Reflectance', u'VIIRS-M3-SDR_All/ReflectanceFactors', u'Data_Products/VIIRS-M3-SDR/VIIRS-M3-SDR_Aggr', u'Data_Products/VIIRS-M3-SDR/VIIRS-M3-SDR_Gran_0']
listVIIRSFieldsInFile('/Users/jayh/Data/joleen/GMTCO_npp_d20140403_t1809429_e1811071_b12604_c20140404003429456303_noaa_ops.h5')
VIIRS-MOD-GEO-TC_All/Height
VIIRS-MOD-GEO-TC_All/Latitude
VIIRS-MOD-GEO-TC_All/Longitude
VIIRS-MOD-GEO-TC_All/MidTime
VIIRS-MOD-GEO-TC_All/ModeGran
VIIRS-MOD-GEO-TC_All/ModeScan
VIIRS-MOD-GEO-TC_All/NumberOfScans
VIIRS-MOD-GEO-TC_All/PadByte1
VIIRS-MOD-GEO-TC_All/QF1_SCAN_VIIRSSDRGEO
VIIRS-MOD-GEO-TC_All/QF2_SCAN_VIIRSSDRGEO
VIIRS-MOD-GEO-TC_All/QF2_VIIRSSDRGEO
VIIRS-MOD-GEO-TC_All/SCAttitude
VIIRS-MOD-GEO-TC_All/SCPosition
VIIRS-MOD-GEO-TC_All/SCSolarAzimuthAngle
VIIRS-MOD-GEO-TC_All/SCSolarZenithAngle
VIIRS-MOD-GEO-TC_All/SCVelocity
VIIRS-MOD-GEO-TC_All/SatelliteAzimuthAngle
VIIRS-MOD-GEO-TC_All/SatelliteRange
VIIRS-MOD-GEO-TC_All/SatelliteZenithAngle
VIIRS-MOD-GEO-TC_All/SolarAzimuthAngle
VIIRS-MOD-GEO-TC_All/SolarZenithAngle
VIIRS-MOD-GEO-TC_All/StartTime
Data_Products/VIIRS-MOD-GEO-TC/VIIRS-MOD-GEO-TC_Aggr
Data_Products/VIIRS-MOD-GEO-TC/VIIRS-MOD-GEO-TC_Gran_0
[u'VIIRS-MOD-GEO-TC_All/Height', u'VIIRS-MOD-GEO-TC_All/Latitude', u'VIIRS-MOD-GEO-TC_All/Longitude', u'VIIRS-MOD-GEO-TC_All/MidTime', u'VIIRS-MOD-GEO-TC_All/ModeGran', u'VIIRS-MOD-GEO-TC_All/ModeScan', u'VIIRS-MOD-GEO-TC_All/NumberOfScans', u'VIIRS-MOD-GEO-TC_All/PadByte1', u'VIIRS-MOD-GEO-TC_All/QF1_SCAN_VIIRSSDRGEO', u'VIIRS-MOD-GEO-TC_All/QF2_SCAN_VIIRSSDRGEO', u'VIIRS-MOD-GEO-TC_All/QF2_VIIRSSDRGEO', u'VIIRS-MOD-GEO-TC_All/SCAttitude', u'VIIRS-MOD-GEO-TC_All/SCPosition', u'VIIRS-MOD-GEO-TC_All/SCSolarAzimuthAngle', u'VIIRS-MOD-GEO-TC_All/SCSolarZenithAngle', u'VIIRS-MOD-GEO-TC_All/SCVelocity', u'VIIRS-MOD-GEO-TC_All/SatelliteAzimuthAngle', u'VIIRS-MOD-GEO-TC_All/SatelliteRange', u'VIIRS-MOD-GEO-TC_All/SatelliteZenithAngle', u'VIIRS-MOD-GEO-TC_All/SolarAzimuthAngle', u'VIIRS-MOD-GEO-TC_All/SolarZenithAngle', u'VIIRS-MOD-GEO-TC_All/StartTime', u'Data_Products/VIIRS-MOD-GEO-TC/VIIRS-MOD-GEO-TC_Aggr', u'Data_Products/VIIRS-MOD-GEO-TC/VIIRS-MOD-GEO-TC_Gran_0']
I'm not sure if the geolocation variables can be accessed through scripting unless they are in a combined file. The programmers will have to take a look at that as well.
If you have any other questions or comments, just let us know.
Thanks, Jay