HEG 2.10 Offical release

[kyang]

I post this for Abe. Kent
---------------------------

Greetings,

The stand-alone HDF-EOS to GeoTIFF Conversion Tool (HEG) version 2.10 is officially released. The release contains tar files for the supported platforms SUN, LINUX, MAC OSX and WINDOWS (32-bit XP and VISTA).

The following tar files have been placed on the EDHS ftp site (ftp to edhs1.gsfc.nasa.gov) in the directory as identified:

/HEG_Tool:

hegWINv2.10.zip
hegLNXv2.10.tar.gz
hegSUNv2.10.tar.gz
hegMACv2.10.tar.gz
HEG_UsersGuide_V2.10.doc
HEG_UsersGuide_V2.10.pdf

These files are accessible from our ftp site by the normally-used password (send a message to: mailto:Landover_PGSTLKIT@raytheon.com if you need the password). You may also download the files from ftp://edhs1.gsfc.nasa.gov/edhs/HEG_Tool/ without the need for the password. Please follow the HEG_README_v2.10 and/or README_INSTALL_Win_v2.10 files for installation, and visit our HEG web site http://newsroom.gsfc.nasa.gov/sdptoo...G/HEGHome.html for HEG related information.

For Toolkit, HDF-EOS and other related software please visit our web sites http://newsroom.gsfc.nasa.gov/sdptoolkit/toolkit.html
http://newsroom.gsfc.nasa.gov/sdptoo...os_plugin.html

[fperks]

Hi, there is some problems i think i should mention about this new version, i've been using it for a few days (we are trying to upgrade from 2.5?):

1. When you attempt to run swtif on two or more files, it errors out on the last run because it states the file already exists, e.g.:

NUM_RUNS = 3

BEGIN
INPUT_FILENAME = C:\Raw\modis\luotest\MOD02HKM.P2009350.2235.hdf
OBJECT_NAME = MODIS_SWATH_Type_L1B
FIELD_NAME = EV_250_Aggr500_RefSB|
BAND_NUMBER = 1
OUTPUT_PIXEL_SIZE_X = 0.011157
OUTPUT_PIXEL_SIZE_Y = 0.004528
SPATIAL_SUBSET_UL_CORNER = ( 76.655533 -179.999954 )
SPATIAL_SUBSET_LR_CORNER = ( 53.356102 179.99968 )
RESAMPLING_TYPE = NN
OUTPUT_PROJECTION_TYPE = GEO
ELLIPSOID_CODE = WGS84
OUTPUT_PROJECTION_PARAMETERS = ( 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 )
OUTPUT_FILENAME = C:\Raw\modis\luotest\MOD02HKM.P2009350.2235_MODIS_ SWATH_Type_L1Bb1.tif
OUTPUT_TYPE = GEO
END


BEGIN
INPUT_FILENAME = C:\Raw\modis\luotest\MOD02HKM.P2009350.2235.hdf
OBJECT_NAME = MODIS_SWATH_Type_L1B
FIELD_NAME = EV_500_RefSB|
BAND_NUMBER = 2
OUTPUT_PIXEL_SIZE_X = 0.011157
OUTPUT_PIXEL_SIZE_Y = 0.004528
SPATIAL_SUBSET_UL_CORNER = ( 76.655533 -179.999954 )
SPATIAL_SUBSET_LR_CORNER = ( 53.356102 179.99968 )
RESAMPLING_TYPE = NN
OUTPUT_PROJECTION_TYPE = GEO
ELLIPSOID_CODE = WGS84
OUTPUT_PROJECTION_PARAMETERS = ( 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 )
OUTPUT_FILENAME = C:\Raw\modis\luotest\MOD02HKM.P2009350.2235_MODIS_ SWATH_Type_L1Bb2.tif
OUTPUT_TYPE = GEO
END


BEGIN
INPUT_FILENAME = C:\Raw\modis\luotest\MOD02HKM.P2009350.2235.hdf
OBJECT_NAME = MODIS_SWATH_Type_L1B
FIELD_NAME = EV_500_RefSB|
BAND_NUMBER = 1
OUTPUT_PIXEL_SIZE_X = 0.011157
OUTPUT_PIXEL_SIZE_Y = 0.004528
SPATIAL_SUBSET_UL_CORNER = ( 76.655533 -179.999954 )
SPATIAL_SUBSET_LR_CORNER = ( 53.356102 179.99968 )
RESAMPLING_TYPE = NN
OUTPUT_PROJECTION_TYPE = GEO
ELLIPSOID_CODE = WGS84
OUTPUT_PROJECTION_PARAMETERS = ( 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 )
OUTPUT_FILENAME = C:\Raw\modis\luotest\MOD02HKM.P2009350.2235_MODIS_ SWATH_Type_L1Bb3.tif
OUTPUT_TYPE = GEO
END

This will error out on the third run, and say "C:\Raw\modis\luotest\MOD02HKM.P2009350.2235_MODIS _SWATH_Type_L1Bb2.tif" already exists on the system. So for what ever reason it is not taking the proper output file name for the final run.

2. When i select multiband geotiff, and attempt to run it. It simply does a non multiband geotiff. It just tries to write out each of the bands individually. And gets the error, that output file 2 already exists.

3. When are you guys going to fix LCC/Polar Projections not having their projection parameters defined properly? Right now if i project using LCC, the latitude of origin is not defined properly(it puts 0). Its kind of irritating since ESRI's Arc doesnt like redefining Lambert_Conformal_Conic twice, even if the parameters are different.

4. Certain MODIS Terra datasets lead to 3 GB single band geotiffs, this is probably because of the huge swaths of no data being created. Attempting to manually set the corners, as according to the HDF file, just leads to the program throwing an error that the UL or LR are out of bounds.

Thanks.

[Abe Taaheri]

I will look into these problems. We made a change in this version so that EOS Datapool, that uses the same HEG executables as the standalone HEG uses, be able to put as much as possible data fields in one output hdfeos file rather than in many files (as it was doing in version 2.9). I believe somehow this has effected the geotiff outputs, though it shouldn't have. I will find out where the problem is and try to get a patch out if I can. Thanks for reporting the problems.