Home

MODIS REPROJECTION TOOL USER'S MANUAL Release 4.1 April

Contents

1. RESAMPLING TYPE MRT User s Manual OUTPUT PROJECTION NEAREST NE TYPE LA TERS OUTPUT PROJECTION PARAME 2005185215618 2006185181530 2007186022514 2008185201335 2009185224517 PE INPUT LAT LONG 46 0 105 0 43 0 93 0 IGHBOR April 2011 hdf hdt hdt hdt hdf D MRT4 1 input MOD14A2 A2005185 h10v04 005 2008044015307 hdf saved from a GUI run or created as recommended in 37 6370997 0 0 0 0 0 0 0 100 0 45 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 DATUM NoDatum OUTPUT PIXEL SIZE 1000 The parameter file is edited and saved for each of the input files changing the input and output filenames for each file This can be a manually intensive process if large numbers of files are required see below for description of the automated batch processing functions in MRTBatch jar Parameter File List MOD14A2 A2005 prm MOD14A2 A2006 prm MOD14A2 A2007 prm MOD14A2 A2008 prm MOD14A2 A2009 prm Then a batch file is written to encapsulate the repetition of resample execution on each file Batch File sd_fire bat resample p MOD14A2 A2005 prm resample p MOD14A2 A2006 prm resample p MOD14A2 A2007 prm resample p MOD14A2 A2008 prm resample p MOD14A2 A2009 prm And finally the batch file is run from the command prompt window Executing Batch Command C Progr
2. a spatial subset type INPUT_LAT LONG INPUT_LINE SAMPLE OUTPUT_PROJ_COORDS l spatial subset or or U U ery lat ULlong LRlat LRlong line ULsample Rline LRsample lt 0 based gt Lprojx ULprojy LRprojx LRprojy Line Sample must be specified for the highest resolution of all SDSs specified to be processed in the product u UTM zone x pixel size g filename for the log file Usage RESAMPLE h file hdf creates raw binary header file TmpHdr hdr If using an input parameter file recommended the only required command line argument is the arameter file name To run the MRT resample from the command line type p yp resample p lt parameter file gt If a parameter file is not used or if only certain fields require changes command line arguments will set the parameters directly and override parameter file specifications MRT is sensitive to the lower case font used for command line arguments To override any parameter file option or to run resample without a parameter file the following arguments may be typed into the MRT command line interface i input filename Input MODIS level 2G 3 or 4 HDF EOS file o output filename Output filename including extension hdr hdf or tif to set the output file type Output filenames follow a convention to identify the input product and bands used in the operation 0o namegame tif Output Fi
3. Starting with a base parameter file from the GUI and modifying as necessary can help avoid accidental processing errors should the user wish to construct a parameter file for command line use The parameter file format is described fully in Appendix A Below is an example of a parameter file Double quotes may or may not be necessary depending on how the host system handles spaces in directory paths or file names INPUT FILENAME D My RT Inputs MYD09GA A2007113 h24v02 005 2007116092027 hdt SPECTRAL SUBSET 0000000000120110000000 SPATIAL SUBSET TYPE INPUT LAT LONG SPATIAL SUBSET _UL CORNER 65 0 127 0 PATIAL SUBSET LR CORNER 61 0 154 0 n OUTPUT FILENAME D My MRT Output MODO9GA tif RESAMPLING TYPE BILINEAR MRT User s Manual April 2011 28 OUTPUT PROJECTION TYPE Il Q O OUTPUT PROJ 0 0 0 0 0 El CTION PARAMETERS OOO eS o 8 8 o Ovi O O O OO o 8 8 o 001 0 0 OOO o 8 o O OO OO DATUM NoDatum PIXEL SIZE 500 The sample parameter file shown above specifies that the input data file is MYDO9GA A2007113 h24v02 005 2007116092027 hdf Bands 11 13 and 14 surf _ refl b01 surf refl b03 surf refl b04 will be projected to Geographic using bilinear interpolation resampling The output pixel size for all bands is set to 500 to overcome potential inconsis
4. Step 3 Building the applications Once the Makefiles are set up there are a couple ways to build the applications The easiest way is to go to the top level MRT_HOME directory and then issue the following commands e make clean optional e make e make install e make clean optional The make clean command removes any object files and other miscellaneous temporary files The make command builds the executables The make install command moves all the executables to the SMRT_HOME bin directory Otherwise each of the above commands needs to be issued separately in every subfolder which includes all the library and program directories These include the shared_src gctp geolib append meta dumpmeta hdf2rb hdflist mrtmosaic resample sdslist and update tile meta This may be useful if only one or two programs are being worked on 4 Step 4 Build ModisToo1 The ModisTool is written in Java Under the JavaGuiSrc directory is a small script that builds the ModisTool ar file and places it into the MRT_HOME bin directory MRT User s Manual April 2011 26 The script is called compilejava and it works under Cygwin or a shell although it should be fairly easy to modify to run under DOS As of version 4 1 ModisToo1 is built with Java version 1 5 0 with scripts targeting the same The software should build under later releases of Java as well MRT User s Manual April 2011 27 Command Line Interface
5. The format converter will support spectral and spatial subsetting but it will not execute any resampling It is necessary to include values for projection information in the parameter file in order for the reformatter to run but all resampling related inputs will be ignored during format conversion The output projection type output projection parameters output pixel sizes and output data types will be the same as the input Mosaic Tool MRT provides a mosaic tool mrtmosaic for mosaicking tiles together prior to resampling The mosaic tool requires that all input files are of the same product type and they must contain the same band names band dimensions number of lines and samples band projection types and projection information band pixel size etc If the band characteristics for each input tile do not match then the mosaic tool will exit with an error The mosaic tool requires an input parameter file which lists the full path and filename of each input file to be mosaicked The input files can be listed in any order and the mosaic tool will determine how they fit together in the mosaic The mosaic tool also requires an output filename The file type of the output file must match that of the input files Thus if the input files are HDF EOS then the output file extension must be hdf Typing mrtmosaic at the command prompt will display the following usage information The last statement in the usage message will be an alert tha
6. C Program Files MRT Tool data rem Set the PATH environment variable to include the MRT executables set Path C Program Files MRT Tool bin rem Run the Java GUI rem Change the java exe path to reflect the directory structure on host rem Quotes are only necessary to handle blank spaces in the pathnames ECHO is off c Program Files Java jrel 6 0 05 bin java exe jar C Program Files MRT Tool bin ModisTool jar MRT User s Manual April 2011 22 4 To add an icon to the desktop please see the direction following the Automatic Installation section above MRT User s Manual April 2011 23 Building the MRT The MRT application is buildable across other operating systems architectures and different compilers than those mentioned in this manual Those described in this manual are those available at USGS EROS Users may wish to attempt compilation on other systems or make code changes to currently supported platform packages The descriptions in this section refer to a variable called MRT HOME which should point to top level installation directory of the MRT application There is additional information that can be found in the README file 1 Step 1 Build third party libraries Supported systems are described briefly under the Platforms subsection of MODIS Reprojection Tool Capabilities above If the users system is currently supported Step 1 can be skipped If there is a need to buil
7. PATH export PATH Run the MRT Java GUI lt path to java_bin gt java jar SHOME My MRT bin ModisTool jar Manual Installation Instructions for Windows Platforms On Windows platforms note that it is no longer necessary to enter directory pathnames with forward slashes instead of backslashes It is in fact recommended that backslashes are used during Windows installation Neither is it necessary to avoid directories with blank spaces for the MRT install directory the Java directory or the input file directory MRT User s Manual April 2011 20 1 Step one for manual Windows installation is unzipping the MRT software which is a two part process First unzip the MRT software package downloaded from the LP DAAC Tools Web site MRT download Win zip This can be done automatically common tools like WinZip For example right click on the zip select WinZip then Extract to and create a directory for the enclosed files such as C Program Files MRT The MRT download Win zip will inflate to install bat MRT Win zip reg _set exe and unzip exe Second the unzip exe will be used to extract the files needed for installation from C Program Files MRT MRT Win zip From Start Programs Accessories open a Command Prompt screen change to the directory containing the files just extracted C Program Files MRT and type the following command unzip MRT Win zip d MRT directory where MRT directory is the direc
8. compiling on Windows with a native compiler then the above library names may not have a 1ib extension instead of a lib prefix e g 1ibz a would be called z 1ib Once the third party libraries are built copying them into the MRT_HOME 1ib directory will make modifying the Makefile easier Likewise copying all the third party include files into the SMRT_HOME include directory will ease Makefile changes 2 Step 2 Modifying the Makefiles This step may be skipped if building on a supported platform Otherwise note that MRT actually consists of three libraries and many programs each having their own Makefile There is a top level Makefile as well that merely iterates through the library and program directories that 1t then builds using their respective Makefiles Some systems cannot read Makefiles and use their own proprietary method of building Visual Studio for C C on Windows for example and it would probably be best to set up the project manually through the IDE The MRT directory structure can be shown as follows MRT shared src library gctp library geolib library append meta program dumpmeta program hdf2rb program hdflist program mrtmosaic program resample program sdslist program update tile meta program Examine each Makefile to determine what changes to certain flags will be needed to tailor the build for a specific system All progra
9. for format conversion is to process all bands across the entire tile unless otherwise specified Spatial and spectral subsetting are supported in format conversion so those parameters may be input as well Unlike the resampling process Resampling Type Output Projection Type Output Projection Parameters and Output Pixel Size are not used for file format conversion The converter will use output files with specifications identical to the inputs for these parameters ignoring any entries to these fields on the GUI To perform a file conversion simply click the Convert Format button next to the Run button at the bottom right of the GUL or use the Convert Format option under the Action menu on the top banner of the GUI Either will be grayed out unclickable until the information described above is entered Mosaic Tool The MRT will allow the user to specify several input files to be processed The MRT will mosaic the input tiles into one large image then process that image as specified by output parameters entered by the user Processing several tiles is very similar to processing a single tile The only difference is that multiple tiles are selected in the Open Input File process The following example shows the user selecting four tiles for processing The user may select multiple files by using the Shift and Ctr1 keys along with pressing the left mouse button The Shift key will select all files between the previous mouse click and th
10. for processing and wishes to output one of the bands at a different resolution would enter the following command opsz 1000 1200 1000 1000 1000 Otherwise the default is to output to the same resolution as the input for each band which generally is the same for each band This field is optional but given the native pixel resolution of MODIS swath data it may be used to normalize the output pixels e g change 926 6 m input to 1 000 m output If the number of output pixel sizes entered in this field is less than the number of bands processed then the last pixel size entered will be used as the pixel size all bands For example it is not MRT User s Manual April 2011 32 necessary to write out the output resolution for all bands if the same output resolution is desired for all bands Simply entering opsz 1000 will apply the desired output pixel size to all bands selected for processing u UTM zone Output zone number relevant only for UTM projections Valid values are 60 to 60 g log filename This option allows the user to specify the path and name of the log file The default log filename is resample log h HDF filename This creates a raw binary header file from the input HDF EOS file The name of the output header file is TmpHdr hdr f This switch causes resample to implement format conversion The input file format is converted to the specified output file format based on the input and output filename extensions
11. icon on the desktop if one was created or click on ModisTool bat in the MRT bin directory A ModisTool window will pop up on the screen in a few seconds Failure to display the GUI indicates a configuration error most likely in the PATH to the Java executables on the host machine See Manual Installation instructions above to determine how to check and resolve any such errors The ModisTool bat Windows or ModisTool UNIX may need to be edited to identify a valid Java path Another potential reason is that a session restart was not completed after the software installation To run resample from the GUI users need to fill in the various fields and click Run In general complete fields in the order listed working down the left Source side and progressing down the right Destination side For example spectral and spatial subsetting parameters may not be selected until an input file is opened output projection parameters may not be entered until an output projection type is specified etc The contents of any field may be changed at any time prior to running resample Simply click on the field and make the desired changes Along the top left banner on the GUI is a menu bar labeled with File Action Settings and Help The File menu includes options for opening an input file opening a parameter file or exiting the GUI Other options for specifying an output file and saving a parameter file become active on the File menu after Source informa
12. the center of the corner pixel All other corners are expressed using the HDF standard which is the outer extent of the UL and lower right LR corners Both HDF EOS and raw binary MRT output coordinates thus represent the UL corner of the corner pixel Any output corner coordinates specified by the GUI in the status box or by the command line in standard output or to the log file represent the outer extent of the pixel Log File MRT writes logging and status information to a screen display and also to a log file The log file is named resample log and is written into the bin directory e g C MRT bin resample log Details of MRT activity are appended to the log at the completion of every run so the history of every MRT execution is recorded ad infinitum The log is an ASCII text file which users may edit or print with standard text file tools The command line version of the resampler will allow the user to specify the path and name of the resample log file using the g option The options for the resampler are fully described later in the Command Line Interface section Bounding Tiles Bounding tiles have presented some difficulties for the MRT These tiles occur on the outer edge of the Sinusoidal globe as seen in the gridded figure below MRT User s Manual April 2011 10 MODIS Land Sinusoidal Mapping Grid Horizontal Tile Number 00 01 02 03 04 05 06 07 08 09 10 11 12 13 141516 17 1819 20 21 22 23 24 25 26 27 2
13. the software e Update the system variables to include PATH MRT HOME and MRT DATA DIR information for MRT e Edit the GUI script in the MRT bin directory to reflect the system directory structure Below are instructions for manually working through these steps The first section is relevant to UNIX systems and includes specifics for C shell and Bourne shell The second section is relevant to Windows systems and includes specifics for NT ME XP Manual Installation Instructions for UNIX Platforms 1 Step one for manual installation of the MRT to a UNIX based system such as Linux or Macintosh is a two part extraction process to load the necessary files to the user s system First unzip the MRT download _ lt platform gt zip file downloaded from the LP DAAC Tools Web site Use the command unzip or unzip from a UNIX terminal to inflate the download package to a chosen location unzip zipfile d MRTdownload directory where zipfileisMRT download Linux zip 32 bit compilation MRT_ download Linux64 zip 64 bit compilation or MRT download Mactel zip Macintosh MRT User s Manual April 2011 17 compilation and MRTdownload directory is the directory to which the zip contents will be extracted If an error is returned saying unzip command not found try using a preceding as shown below unzip MRT download _Linux zip d SHOME MRT Changing to the MRTdownload_directory in the UNI
14. tile were processed QA and FireMask HDF EOS output would consist of a single sd_ fire 2006 hdf while in GeoTIFF the same output would be delivered as sd_fire 2006 0A tifandsd fire 2006 FireMask tif Output File Type This option is positioned under the Output File window and can be used after a file name is selected to change its format without having to relocate and rename it Select GeoTIFF HDFEOS or RAWBINARY from the Output File Type drop down list to automatically change the extension of the file name entered in the Output File field MRT User s Manual April 2011 49 Resampling Type MRT offers three resampling methods from the Resampling Type drop down list Nearest Neighbor Bilinear or Cubic Convolution Note that when projecting thematic data sets such as a fire mask or any QC band nearest neighbor is required to avoid mixing categorical values For example if 1 snow 2 water and 3 fire resampling methods using averaging will potentially mix 1 and 3 and output a 2 El ModisTool PEE File Action Settings Help Source Destination Input Files DIPROJECTIMRTMaintenance MRTA tinpi Specify Output File Open Input File Output File CTIMRTMaintenance MRT4 1 outputisd_fire_2006 ti 1 View Metadata Output File Type A View Selected Tile s 2 Resampling Type E Input File Info nput Projection Type SIN rojection Parameters 6371007 181 0
15. 0 m is 0 009 degrees If left blank the output pixel size remains the same as the corresponding input pixel size for each selected band If specified on the GUI the output pixel size will be used for all selected bands This helps normalize MODIS pixels which due to their basis in arcseconds are actually 926 6 m pixels instead of 1 000 m The MRT Output Pixel Size function is not recommended as a tool to rescale 1 000 m data to higher resolutions Load or Save Parameter File The MRT offers a method to retain all the Source and Destination parameters just entered through the steps above This is useful if there is more than one file to process to the same specifications if users need to input the same parameters at a later session or if users do not want to enter all the parameter information repeatedly To save all information just entered on the GUL click on Save Parameter File and type in a file name Unlike specifying an image output file it is not necessary to include a file extension with the name and a file with the extension prm is created in the directory of choice see the sample parameter file included in the Batch Processing section An existing file name may be used but the file will be overwritten unless it is modified If the last parameter file used for processing was not saved it is retrievable from the MRT bin directory where the most recently executed parameters are saved in TmpParam prm To restore saved para
16. 0000000000000 otal Number of Bands 2 Data Type UINTS UINTS Pixel size 926 6 926 6 umber of lines 1200 1200 Number of samples 1200 1200 Lat Long of Upper Left Corner 49 999999996 124 457906126 Lat Lona of Unner Right Comer 49 999999996 108 90066786 _ Edit Projection Parameters Output Pixel Size A Output Projection Type The Output Projection Type Geographic UTM etc is selected from a drop down list and its parameters are entered using the Edit Projection Parameters button Resampling Type Output Projection Type MRT User s Manual April 2011 50 Clicking the Edit Projection Parameters button will pop up a dialog box in which users may enter or edit up to 15 gridding parameters Note that the default values appearing in the pop up box are not automatically overwritten when their fields are clicked Users must delete or highlight them for replacement Integer values are automatically be converted to floating point Some parameter fields will be grayed out uneditable when they are not used for a particular output projection These fields are based on the table of projection parameters in Appendix C ES Projection Parameters Sphere disabled disabled 6370997 disabled CentLon CenterLat 100 las FE FN disabled 0 0 foo disabled disabled disabled disabled disabled disabled d F Datum NoDatum y Cancel When
17. 8 29 30 31 32 33 34 w wn Vertical Tile Number iT SL 5ST HT ET ZT TL OT 60 80 0 90 50 0 0 Z0 TO 00 The tiles are labeled from top to bottom and from left to right starting at 00 The horizontal tiles range from h00 to h35 and the vertical tiles range from v00 to v17 The MODIS HDF EOS filename will contains a field specifying the horizontal and vertical location of the tile For example a tile covering the state of Florida USA would be named something like MOD13Q1 A2011042 h10v06 005 20011060132568 hdf where h10v06 indicates its tile location on the Sinusoidal grid Data over the southern tip of Africa might be named MO09A1 A2007177 h19v12 005 200908 123 1246 hdf where h19v12 is its tile location Bounding Tile Issue Bounding tiles are unique in that they contain corner points with projection coordinates which do not map to a valid latitude longitude For example tile h10v02 over Alaska theoretically has corner points along both the far western and far eastern edges of the Sinusoidal globe Bounding tiles wrap around the edges of the Sinusoidal globe which places coordinates in discontinuity space i e in the black space in the figure above This is not unique to MRT or MODIS tiles and impacts any global projection software This discussion will be limited to MRT handling of the MODIS tiles The discontinuity space for the Sinusoidal projection as with many projections occurs at the 180 0 180 0 longit
18. 98333 The following are the longitude latitude corners provided by GCTP inverse mapping UL long lat in degs 179 999999954516 59 999999994612 UR long lat in degs 160 000000050532 59 999999994612 long lat in degs 140 015144391778 49 999999995507 R long lat in degs 155 572382657536 49 999999995507 The UR longitude above 160 has extended beyond the eastern hemisphere past the 180 line and 20 degrees into the western hemisphere The associated forward mappings from the above latitude longitude values likewise indicate the UR corner has wrapped around the 180 line into discontinuity space as shown below UL x y in meters 10007554 677000002936 6671703 117999996990 UR x y in meters 8895604 162390576676 6671703 117999996990 Xx y in meters 10007554 677000001073 5559752 598332998343 LR x y in meters 11119505 196667000651 5559752 598332998343 MRT User s Manual April 2011 12 The forward mapping coordinates above do not match the original squared off upper right corner Bounding Tile Solution The solution for handling the bounding tiles first detects that a latitude longitude pair has wrapped around the Earth by running forward mapping on the inverse mapping to validate the latitude longitude values In the case that the forward mapping projection values are the same as the original projection corners then the latitude longitude values will be used directly In the case that the forwar
19. 99996 4124 457906126 Run EP ROE LR Corner 39 999999996 91 37851024 Exit Metadata Examination The basic metadata displayed in the Input File Info window includes the input projection type Sinusoidal the input projection parameters the total number of bands the data type of each band the pixel size of each band the number of lines and samples in each band and the corner coordinates of the tile Users may examine detailed metadata by highlighting the filename in the Input Files box then clicking on View Metadata below the Open Input File button This will pop up the internal metadata from the input HDF EOS tile including its inventory metadata archive metadata and its grid structure MRT User s Manual April 2011 45 The View Metadata window offers a Find service in the lower left corner into which a case sensitive text string can be typed to parse the internal metadata for terms of interest EB View Metadata OBJECT GRINGPOINTLONGITUDE NUM_VAL 4 CLASS 1 VALUE 104 5201961 1598 124 88536205918 109 0021 43160265 91 1909609510465 END_OBJECT GRINGPOINTLONGITUDE OBJECT GRINGPOINTLATITUDE NUM_VAL 4 CLASS VALUE 39 755681 7203217 49 967693939585 50 1046853303771 39 8554224326714 END_OBJECT GRINGPOINTLATITUDE OBJECT GRINGPOINTSEQUENCENO NUM_VAL 4 CLASS 1 VALUE 1 2 END_OBJECT 3 4 GRINGPOINTSEQUENCENO END_GROUP GRINGPOINT GROUP CLASS O
20. BJECT EXCLUSIONGRINGFLAG NUM_VAL sA CLASS p KI Find LONGITUDE Tile Locator Just beneath the View Metadata window is another button labeled View Selected Tile This feature will bring up a global map on the Sinusoidal grid and highlight the location of the tiles in the Input Files box in light blue El Image Window D MRT User s Manual April 2011 46 Spectral Subsetting Immediately below the Input File Info box are options for spectral subsetting By default all available bands are selected and appear in the box to the right Selected Bands To exclude certain bands from processing click on the desired band and use lt lt to deselect it This will move it to the box on the left Available Bands To move bands from the Available box to the Selected box click on the desired band and use gt gt to select the band for processing Shift Click and Ctrl Click are useful for highlighting multiple bands for selection In the example below derived from an 8 day MODIS Fire tile one of the two available bands has been removed from processing by moving it to the Available Bands box Available Bands 1 Selected Bands Spatial Subsetting Unless otherwise specified MRT will project the entire input file using the Bounding Box coordinates defined in the HDF EOS Archive metadata displayed in the Input File Info window Users have the option to override this default and extract spatial sub
21. FN 26 Interrupt Mollweide Sphere 27 Hammer Sphere CentMer FE FN 28 Wagner IV Sphere CentMer FE FN 29 Wagner VII Sphere CentMer FE FN 30 Oblated Equal Area Sphere Shapem Shapen CentLon CenterLat FE FN 31 Integerized Sinusoid Sphere CentMer FE FN Code amp Projection Id SPS Sees Sas SSS a pase See Ses eSs 9 1101 EENE 121 13 P 1 15 1 0 Geographic LU TM 2 State Plane 3 Albers Equal Area 4 Lambert Conformal C 5 Mercator 6 Polar Stereographic 7 Polyconic MRT User s Manual April 2011 20 21 22 23 24 25 26 27 28 29 30 aL Equid Conic A Equid Conic B Transverse Mercator Stereographic Lambert Azimuthal Azimuthal Gnomonic Orthographic Gen Vert Near Per Sinusoidal Equirectangular iller Cylindrical Van der Grinten Hotin Oblique Merc A Hotin Oblique Merc B Robinson Space Oblique Merc A Space Oblique Merc B Alaska Conformal Interrupted Good Mollweide Interrupt Mollweide Hammer Wagner IV Wagner VII Oblated Equal Area Integerized Sinusoidal MRT User s Manual Zero one Longl Lat1 Long2 Lat2 PSRev LRat PFlag Angle NZone RFlag April 2011 Zero one Zero one 67 Notes Lon Z Longitude of any point in the UTM zone or zero If zero a zone code must be specified Lat Z Latitude of any point in the UTM zo
22. MODIS REPROJECTION TOOL USER S MANUAL Release 4 1 April 2011 Land Processes DAAC USGS Earth Resources Observation and Science EROS Center MRT User s Manual April 2011 1 Table of Contents Ilo orto AA A TE 4 MODIS Reprojection Tool Capabilities ccccecccccscessseesseesseessecseecseecaecesecnsecnseceseeseeeseeeseaeseneeeseeeeeeaeesaes 5 Plat MS 3220 ac nest li a A REE OMA eG RR a a ae Ea 5 A RR 5 Data PLOdUAS 2 A A AR AN A E A Astle RNR ae 3 PIETONI tdt E T E TEE ae O tee Se taa 5 DAA AE E E T AT E E E E hee E A 6 Map Projections cc a Ad al a ato 6 ROMO si 6 Forma CONYE Oea a a ca ren Pe AEA AE E EO 6 Mose FOO aaa ia aa iia 7 AN A O 7 Spectral SUSHI ii E A a A S 8 Spatial SUD iii A A A A E E nate EA ES 8 Output Pixel SiZ caida ni isla ido 9 Parame er Ellos tac tc dcir dato sshd aii he eee 9 Metadata ata dt adds E E O A O ST AE del E T A de eda adalat tee shin des 9 Back orourids Flia ida aa a tr tE EA ba da aii 10 Comer COOLGINALES init dilata Dtos bodes N 10 Los lia TA ashes a aN 10 Bounding Til A vices ch a A aint 10 Bond Td dead 11 Bounding Tle Sol id ita tn a a Ea tido 13 MODIS Reprojection Tool Installati0M oooonnoninnninoninocionncnonononononoconoconoconncnnnrnnno nan ronnnonnnronnronncon nano nacinnos 14 Pre Installation es i a AAE AA T STs hee Nos a Ge Meneses Na he Rao 14 Automatic Installation A aiii ode 15 Adding a Shortcut Icon in Windows cccccesscesscesseeeseesseeeseecscecsaecsaecsaec
23. MRT functionality is based on two primary executables resample and mrtmosaic Both can be run by entering parameter information either through a GUI or a command line interface The GUI is a simple and user friendly guide for input information but is not recommended when processing requirements include large number of files and actions The MRT command line interface is a useful tool for intensive data conversions and includes the flexibility of automation Usage Of resample and mrtmosaic are described separately below following a description of the parameter file MRT needs as input to any processing Parameter Files Regardless of how it is invoked via the GUI or the command line the MRT executables are directed by a parameter file containing all the information necessary to read MODIS data from an input data file transform the data into a specified output projection and write the results to an output file The parameter file contains the file names and file types of the input and output data files spectral and spatial subsetting information output projection type output projection parameters output UTM zone if necessary output resampling type and output pixel size Parameter files are generated automatically through the MRT GUL and can be saved for later use either through the GUI or the command line interface They are distinguished by a prm extension and formatted as ASCII text which may be created and edited in any text editor
24. NLINES rl r2 rn NSAMPLES cl c2 PIXEL SIZE sl s2 MIN VALUE vl v2 MAX VALUE vl v2 BACKGROUND FILL f1 pl t lon t lon lon t lon d2 tn En sn vn vn 2 Header file for MODO9GHK A2000072 h08v05 001 2000084105003 p2 p3 p4 p5 po p7 p8 p9 p10 p11 p12 p13 p14 lat long in decimal degrees for the outer extent of the pixel projection coordinates for the outer extent of the pixel bandn fn DATUM Optional datum value BYTE ORDER little endian or big endian MRT User s Manual April 2011 62 Editing header files Header files may be created and modified by directly editing the header file with an ASCII text editor Running MRT and selecting raw binary file output also creates header files In this case the MRT automatically generates an output header file along with output data files Notes e Fields may occur in any order Each field should begin on a new line but may span more than one line for readability Field values should be separated by white space Otherwise there are no significant restrictions on field formatting e All text following a on a line is considered to be a comment Some comment lines are automatically generated by MRT for reprojection to a raw binary output image for informational purposes only e Field names should be largely self explanatory Lower case items represent numeri
25. Open Input File to the right of the Input File field This will pop up an input file selection dialog box allowing selection of the desired input file by pointing and left clicking with the mouse The default directory is set to the MRT User s Manual April 2011 43 MRT bin so users need to either set a preferred directory using the Settings menu on the GUI s top banner or navigate to the directory containing the input files using the browse tools in the dialog box These include a drop down directory tree search a button to move up one directory a button to return to the user s home directory a button to create a new directory and options to list or show details of the files in the open directory If several adjacent tiles are desired for processing MRT will allow selection of multiple input filenames This is discussed later in the Mosaic Tool section below CO ij xi Lookin C input z a E f Bs D MOD14A2 A2006185 1 10v04 005 2008134150325 hdf C MOD 14A2 A2007 185 h10V04 005 2007 198234014 hdf D MOD14A2 A2008185 h10v04 005 2008195005505 hdf D MOD14A2 A2009185 h10v04 005 2009199012243 hdf File Name MOD14A2 42005185 h10v04 005 2008044015307 haf ya mp Open Cancel An input file is selected either by typing its name into the File Name field at the bottom of the dialog box by double clicking on the file name in the directory list or by highlighting the file name with a singl
26. Tool bat A system restart is advised to ensure the changes made during MRT installation take effect and the tools function as expected C shell csh tesh ModisTool template bin sh KKK KKK KKK KKK KKK KKK KKK KKK KKK KK KKK KKK KKKKKEKK ModisTool C Shell script for running the MRT GUI KKK KKK KKK KKK KKK KKK KKK KKK KK KKK KKK KKK K KKK KKK MRT User s Manual April 2011 19 EA Set the MRT HOME environment variable to the MRT installation directory setenv MRT HOME SHOME My MRT Set the MRT DATA DIR environment variable to the data directory setenv MRT DATA DIR SHOME My MRT data Set the PATH environment variable to include MRT executables set path Spath q SHOME My MRT bin Run the MRT Java GUI lt path to java_bin gt java jar SHOME My MRT bin ModisTool jar Bourne shell sh bash ModisTool template bin sh KKAXKKKXKKKXKKKXKKXAKXKKKKXKKXKXKKXKKKKKKXKKKKXKKXAKkA ModisTool Y Bourne Shell script for running the MRT GUI KKAXKKKXKKKXKKKXXKKXAKKKKKXKKXAKXKKXKKAKKKXKKAKKkAKkA Set the MRT HOME environment variable to the MRT installation directory MRT HOME HOM export MRT HOM My MRT Set the MRT DATA DIR environment variable to the data directory MRT DATA DIR SHOME My MRT data export MRT DATA DIR Set the PATH environment variable to include MRT executables PATH SHOME My MRT bin
27. X terminal the file mrt install should be present along with either MRT Linux zip MRT Linux64 zip orMRT Mactel zip The second part of the extraction process will inflate the MRT software package Use the unzip command to extract the installation software to a chosen location unzip zipfile d MRT directory where zipfile is MRT Linux zip MRT Linux64 zip or MRT Mactel zip and MRT directory is the directory into which MRT will be installed For example to install in a My MRT subdirectory in the home directory on a Linux workstation type the following unzip MRT Linux zip d SHOME My MRT 2 Step two will add MRT information to the startup files for the current shell csh tcsh sh bash Typing echo 0 orecho SHELL at the command prompt will display which shell is being used C shell csh tesh users will need to add or update the path MRT HOME and MRT DATA DIR environment variables to the system login file in the home directory Assuming installation of MRT in a My MRT subdirectory in the home directory the following lines are appended to the login set path path q SHOME My MRT bin setenv MRT DATA DIR SHOME My MRT data setenv MRT HOME SHOME My MRT Bourne shell sh bash users will likewise add or update the path MRT HOME and MRT DATA DIR environment variables to the system profile and bash profile file in the home directory in addition to se
28. al Area ER Equirectangular GEO Geographic IGH Interrupted Goode Homolosine HAM Hammer ISIN Integerized Sinusoidal LA Lambert Azimuthal Equal Area Lcc Lambert Conformal Conic MERCAT Mercator MOL Molleweide Ps Polar Stereographic SIN Sinusoidal TM Transverse Mercator and UTM Universal Transverse Mercator projection parameter list Output projection parameters This quoted floating point list includes up to 15 projection parameters with each value separated by white space p1 p2 p15 If there are fewer than 15 values specified in the list the remaining values will be set to zero Integer values will automatically be converted to floating point 10 See Appendix C for more information about projection parameters or type resample help lt projection gt at the command line MRT User s Manual April 2011 31 s spectral subset list Name of band Science Data Set or SDS to resample This is a quoted binary list with each value separated by white space 1 0 1 0 1 0 0 means do not use this band while 1 means select this band If there are fewer values in the list than input bands the remaining bands will not be selected 1 e will default to 0 Use the index number 0 based after the band name to identify a 2D slice of a 3D band a spatial subset type Type of output spatial subset value Valid options are INPUT LAT LONG lat
29. am Files MRT4 1 MRT bin gt sd_fire bat MRT User s Manual April 2011 38 UNIX Bourne Shell Batch Processing A non windows alternative uses iteration such as the following UNIX Bourne shell for loop rather than a bat but the parameter files need to be generated just the same see below for description of the automated batch processing functions in MRTBatch jar for 1 1n hdt do resample p i prm done Direct Argument Batch Processing MRT processing can be directed by parameter files as used in the Windows and UNIX batch processing descriptions above but it also responds to direct argument input The arguments detailed in the previous Resample Tools section provide the same functionality as and may be used instead of or in addition to the parameter file These optional arguments provide no additional functionality but do make it easier to control the resample executable because it may greatly reduce the number of parameter files needed The optional arguments are designed to override fields in the parameter file Consider a scenario in which there are a number of MODIS input data files to process by performing essentially the same operations on each data set transformation to an output projection spectral subsetting spatial subsetting etc Rather than creating a different parameter file for each input data product a tedious and error prone process at best a single parameter file serves the purpose with overriding in
30. at as input Output file formats include raw binary HDF EOS and GeoTIFF The raw binary file format is specified in Appendix B gt MRTSwath is a no cost download from https Ipdaac usgs gov Ipdaac tools modis_reprojection_tool_swath Summary information on an example of multi dimensional MODIS data is available at https Ipdaac usgs gov Ipdaac products modis_products_table brdf_albedo_model_parameters 16 day 13 global 5 00m mcd43al MRT User s Manual April 2011 5 Data Types MRT supports 8 bit 16 bit and 32 bit integer data both signed and unsigned as well as 32 bit float data The output data type is always the same as the input data type Map Projections MRT uses calls to the General Cartographic Transformation Package GCTP and as such allows projection to the following mapping grids Albers Equal Area Equirectangular Geographic Hammer Integerized Sinusoidal Interrupted Goode Homolosine Lambert Azimuthal Lambert Conformal Conic Mercator Molleweide Polar Stereographic Sinusoidal Transverse Mercator Universal Transverse Mercator The GCTP used by MRT applications has been modified to incorporate the Integerized Sinusoidal Projection originally applied to Version 001 MODIS products Resampling Three resampling methods are available in MRT nearest neighbor NN bilinear BIL and cubic convolution CC Format Conversion MRT provides an option to convert an input file to a different fo
31. c and string values for the various fields Several fields require arrays of n values for imagery containing n bands SDS elements Different bands may have different data types dimensions resolutions etc e The BANDNAMES field is optional by default bands are named according to their SDS name The MIN VALUE MAX VALUE and BACKGROUND FILL fields are also optional by default no background fill value is used in resampling e Only one input projection type is permitted in this file format All 15 projection parameters must be specified e When inputting UTM data types either the UTM ZONE or first two projection parameters may be used to specify the zone Valid UTM ZONE values between 60 and 60 may be entered If both the UTM ZONE and first two projection parameters are specified then the UTM ZONE is used to determine the zone e A DATUM may be specified for input data Valid values are NAD27 NAD83 WGS66 WGS72 WGS84 and NODATUM If not specified then NODATUM will be used and the first two values in the projection parameters must be entered to define the semi major and semi minor axes of the spheroid MRT User s Manual April 2011 63 e The BYTE ORDER parameter specifies the byte ordering used for the raw binary product Valid values are little endian Intel based systems like Windows and big endian Unix based systems like Linux and Macintosh The byte order is requir
32. c projection using GCTP 2 Convert from the input datum to the output datum in the Geographic projection 3 Project from the Geographic projection to the output projection Both steps 2 and 3 are handled by the same call to Geolib If the input data is not in the SIN projection then a single call to Geolib will handle the reprojection and datum conversion Spectral subsetting HDF EOS input files contain several layers of data which are called Science Data Sets SDS The term SDS is used interchangeably in this document with the term band Any subset of the input bands may be selected for reprojection The default is to reproject all input bands Spatial subsetting A spatial subset is defined by entering two corners upper left and lower right of a rectangle These corners are specified either as input latitude and longitude coordinates as input line sample pairs or as output projection coordinates The default is to project the entire input image using the bounding rectangular coordinates from the global attributes metadata MRT User s Manual April 2011 8 Output Pixel Size Because native MODIS spatial resolution is based on arcseconds at the equator input pixel size is not likely to be exactly as advertised For example 250 m products actually contain 231 7 m pixels 500 m products have 463 3 m pixels 1 000 m products have 926 6 m pixels MRT will default its output to the input pixel size unless otherwise s
33. cification shall be described in another document File naming conventions By convention all related files in raw binary file format are given the same base filename Header files are given the hdr extension Data filenames are generated from the basename and the Scientific Data Set SDS name and given the dat extension as follows basename SDS_ name dat For example MOD09GA A2000072 hdr header file MODO9GA A2000072 sur_refl_ b01 1 dat data file band 1 MODO9GA A2000072 sur_refl b02 1 dat data file band 2 etc Because of these naming conventions there is no need to specify raw binary data filenames inside the header file Data filenames are automatically generated by appending the appropriate extension onto the basename of the header file MRT User s Manual April 2011 61 Header file format The header file contains information required by the MODIS Reprojection Tool for processing data in the raw binary file format An ODL like format is used as illustrated by the following PROJECTION TYPE ISIN T PROJECTION PARAMETERS p15 COORDINATE ORIGIN UI CORNER _LATLON la UR_CORNER_LATLON la iL CORNER LATLON lat LR CORNER LATLON la CORNER XY x y UR_CORNER XY x y L CORNER XY x y LR CORNER XY x y NBANDS n BANDNAMES bandl ban DATA TYPE tl t2
34. d MRT applications on a currently unsupported system third party libraries will need to be built first Please note that the following instruction assumes the libraries will be built statically Use of shared or dynamic libraries is not addressed here Also if some of the libraries needed for MRT are already installed the user will need to determine whether to use those existing or to build them for MRT application making sure MRT pointers are directed to the appropriate library The libraries used by the MRT application are listed below with the version numbers used for this release with links that were valid as of this writing Projects Version Libraries Link zlib 1 2 3 libz a http www zlib net szip 2 0 libsz a http www hdfgroup org release4 obtain html jpeg 6b libjpeg a http www hdfgroup org release4 obtain html tiff 3 8 2 libtiff a http remotesensing org libtiff Geotiff 1 2 3 libgeotiff a http trac osgeo org geotiff hdf4 4 211 libdt http www hdfgroup org products hdf4 use the one in the libmfhdfa src patches directory hdf eos 2 14 Libhdfeos a http www hdfeos org software When compiling the tiff and hdf4 libraries make sure to include their respective dependencies to the szip jpeg and zlib libraries The Geotiff library depends on the tiff library and the hdf MRT User s Manual April 2011 24 eos library depends on the ha 4 library If
35. d mapping projection values are not the same the software will constrain the longitude values at 179 900 for the upper or lower left corners or 179 900 for the upper or lower right corners Because the longitudinal values returned by the GCTP fall in the discontinuity space wrap around backwards MRT signs the longitude as opposite of the GCTP value For example a GCTP return of 180 000 will be written as 179 900 by MRT The longitudinal constraint was not set strictly to 180 0 or 180 0 to avoid the risk of running into further discontinuity issues when going to output space Enforcing longitudinal bounds at 179 900 and 179 900 on the example over h27v03 used above the latitude longitude corners provided by the inverse mapping are changed as shown in the table below The Lat fixed and Lon fixed values are finally converted to output space to define a minimum bounding box in which to project the input data Corner Lat pre fix Lon pre fix Lat fixed Lon fixed UL 59 9999999946 12 179 999999954516 59 999999994612 179 999999954516 UR 59 9999999946 12 160 000000050532 59 999999994612 179 900000000000 LL 49 999999995507 140 015144391778 49 999999995507 140 015144391778 LR 49 999999995507 155 572382657536 49 999999995507 155 572382657536 A tolerance value of 5 m was used to determine if the original projection coordinates and the forward mapping projection coo
36. e click and pressing Open When an input file is opened Source information is loaded into the GUI The file name will appear in the Input File field basic metadata will be displayed in the Input File Info window the Selected Bands window will list the science data sets bands available in the input file and the corner coordinates are shown in the Latitude and Longitude fields MRT User s Manual April 2011 44 A ModisTool File Action Settings Help Source Destination Input Files Specify Output File D PROJECT MRTMaintenance MRT4 Vinp Open Input File Output File LE View Metadata Output File Type View Selected Tile 4 gt Resampling Type Input File Info Nearest Neighbor x Input Projection Type SIN Output Projection Type Projection Parameters 6371007 181 00000000000000 otal Number of Bands 2 y Data Type CUINTS UINTS Edit Projection Parameters Pixel size 926 6 926 63 Number of lines 1200 1200 Number of samples 1200 1200 Output Pixel Size LatLong of Upper Left Corner 49 999999996 124 457906126 ona of UnperRiaht Comer 49 999999996 108 90066786 OoOo g Available Bands Selected Bands 2 f QA E Commands Load Parameter File Save Parameter File Spatial Subset Input Lat Long Parameter File Latitude Longitude UL Corner 49 9999
37. e current mouse click The Ctr1 key will simply add the current mouse click to the list of files MRT User s Manual April 2011 54 Look In C testdata cal e co EE O MOD10A41 42001077 h13v04 003 2001192020935 G MOD1201 42000289 h27v03 002 200 1103231505 D MOD1041 42002052 h09v04 003 2002058061223 O MOD12Q1 42001001 h12v04 003 2001193164828 O MOD1142 42002193 h16v01 003 2002217201812 Q MOD1341 42000273 h02v06 002 20003232 13007 O MOD1201 42000289 h24v02 002 2001103225932 Q MOD13A1 42001353 h13v09 003 2002012184903 G MOD1201 42000289 h25402 002 2001103225927 O MOD13Q1 42002257 h11v09 003 200228504 1900 G MOD12Q1 42000289 h26v03 002 200 1103225927 Ly MOD1301 42002257 h11v10 003 2002285043845 File Name 31201 A2000289 h26v03 002 2001 103225927 hdf MOD1 21 A2000289 h27v03 002 200110323151 Files of Type shag he Open Cancel The mosaic tool requires that all input tiles are of the same product type and thus contain the same bands which remain the same size data type projection pixel size etc for all input tiles If the input tiles are not of the same product type the MRT will exit with an error When multiple tiles are mosaicked the output is in HDF format and named TmpMosaic hdf The TmpMosaic hdf is input to subsequent resampling actions The HDF4 libraries currently included in MRT software impose a 2 gigabyte GB limitation on file sizes so it is possible for MRT to reject processing becau
38. e input files and in GUI mode displays basic file specifications including the number of bands available data type numbers of lines and samples and the upper left and lower right corners Output file metadata is written for HDF EOS input files only not for raw binary inputs The output HDF file contains the output metadata followed by the original input file metadata The input structure core and archive metadata information is stored under the HDF attributes OldStructMetadata OldCoreMetadata and OldArchiveMetadata respectively MRT User s Manual April 2011 9 Background Fill If the majority of values that lie under the resampling kernel are background fill values then a background fill value is output Otherwise resampling is performed only from non background fill values and kernel weights are adjusted accordingly MRT reads the FillValue for each input band and uses that value for the output background fill If no FillValue is specified then the default value is 0 NOTE For some MODIS products the fill value is very high i e 65535 rather than a lower value or negative value as some users may be accustomed to For these products the non image data in the resampled image will also be background fill This will result in very bright pixels surrounding the actual image data instead of the dark pixels that may be expected Corner Coordinates The upper left UL corner specified for output in GeoTIFF refers to
39. e the information at the start of the Installation section for hints on how to determine the location of the Java bin directory 3 Step three is using a command line interface to navigate to the directory to which MRT download_ lt platform gt zip was unzipped On Windows systems it will contain the four files mrt install bat MRT lt platform gt zip reg set exe and unzip exe On UNIX systems only two files mrt install and MRT lt platform gt zip will be present MRT User s Manual April 2011 15 4 Step four is to execute the install scripts while within the directory containing the installation files see previous step e For UNIX Linux or Macintosh type mrt_ install such as user server MRT S mrt_install e For Windows type mrt install from the Command Prompt screen invoked from Start Programs Accessories C Program Files MRT gt mrt_install 5 Step five is to carefully follow the instructions appearing in response to the install command The program will prompt the user to enter a preferred location for the install and the information needed to set up path and environment variables correctly Providing full pathnames for all directories is advised because although wildcards and relative pathnames will be accepted they are likely to keep MRT software from setting up correctly Use copy paste functions if possible when entering directory paths Typographical errors will not be recognized during the instal
40. ecified in the output projection parameters field DATUM lt NAD27 NAD83 WGS66 WGS72 WGS84 gt This field is optional and defaults to NODATUM Otherwise a valid datum may be specified for output projections If the NODATUM option is used then the user must specify the spheroid semi major and semi minor axes in the projection parameters See the Datum Conversions section for more information OUTPUT PIXEL SIZE lt value gt The output pixel size may be specified for each band processed in output projection units meters for all projections except Geographic which requires units of decimal degrees For example if five bands are selected for processing and the user wishes for some reason to output one of the bands at a different resolution the line in the parameter file would look like this below OUTPUT PIXEL SIZE 1000 1200 1000 1000 1000 Otherwise the default is to output to the same resolution as the input for each band which is generally the same for each band This field is optional but given the native pixel resolution of MODIS swath data users may utilize it to normalize the output pixels e g change 926 6 m input to 1 000 m output If the number of output pixel sizes entered in this field is less than the number of bands processed then the last pixel size entered is used as the pixel size all bands For example it is not necessary to write out the output resolution for all bands if t
41. ed since it is possible that the input file was processed on a system with a different byte order in which case the image would need to be byte swapped upon ingest As of MRT 4 0 two byte and four byte data types are stored in machine dependent byte order All previous versions output raw binary products as big endian byte order e The COORDINATE ORIGIN is an optional comment field that is not used by the MRT on input but is written on output for information purposes only It specifies the location of the coordinate origin as one of the four corners UL UR LL LR The resampling executable assumes the coordinate origin is UL for raw binary data e There are two sets of corner coordinate fields The CORNER_XY coordinates in projection units are optional comment fields These fields are not used by the MRT on input but are automatically generated on output for informational purposes only The CORNER_LATLON coordinates are required latitude and longitude in decimal degrees e Valid DATA TYPE values are INT8 UINT8 INT16 UINT16 INT32 UINT32 and FLOAT32 MRT User s Manual April 2011 64 Appendix C Projection Parameters Projection Parameters 1 8 Code Projection Id H 2932 22279 SS GE REA RSE e l 1 2 3 4 l 5 l 6 17 8 0 Geographic 1UTM Lon Z Lat Z 2 State Plane 3 Albers Equal A
42. editing the projection parameters an output datum may be specified For all projections the default will be NoDatum The Datum Conversions section of this manual discusses more information on this field but it is important to iterate that either a Datum or the first two projection parameters may be specified but not both If both are specified then the MRT will exit with an error A special note for UTM projections MRT will automatically set the UTM Zone when UTM is set as the Projection Type Although it is an option it is not necessary to enter a UTM Zone value in the Edit Projection Parameters box A special note for Lambert Conformal Conic projections Although the standard parallels and latitude of origin fields are both open for editing enter a value into only one or the other Setting standard parallels effectively does the job of the latitude of origin in LCC projection and having the OriginLat specified as well as the STDPR1 and STDPR2 will place the projected output at inaccurate latitude longitude coordinates MRT User s Manual April 2011 51 Output Pixel Size Right under Edit Projection Parameters is an Output Pixel Size box This can be used to specify a different pixel size for output files than was input to MRT A new pixel size can be entered using decimal degrees for the Geographic projection and meters for all other projections For reference 250 m is 0 00225 degrees 500 m is 0 0045 degrees and 1 00
43. er of the corner parameters see below is specified this field defaults to INPUT_LAT LONG and the entire image will be processed SPATIAL SUBSET UL CORNER lt UL line UL sample UL lat UL lon UL proj x UL proj y gt SPATIAL SUBSET LR CORNER lt LR line LR sample LR lat LR lon LR proj x LR proj y gt These fields are required for spatial subsetting and define the coordinates of the upper left and lower right corners in units appropriate to the selected sPATIAL SUBSET TYPE By default the entire input image will be selected The bounding rectangular coordinates in the input file s metadata are used to determine the image coordinates The parameter field is formatted as follows for each subset type n PATIAL SUBSET TYPE INPUT LAT LONG PATIAL SUBSET UL CORNER 1 969280203 37 840197592 26 054383372 16 574757586 n n PATIAL SUBSET LR CORNER n PATIAL SUBSET TYPE INPUT LINE SAMPLE n PATIAL SUBSET UL CORNER 20 20 n PATIAL SUBSET LR CORNER 1353 2029 MRT User s Manual April 2011 58 SPATIAL SUBSET TYPE OUTPUT_PROJ_COORDS SPATIAL SUBSET UL CORNER 635521 0 1235874 0 137256 0 82544 0 SPATIAL SUBSET LR CORNER In the case of multi resolution data sets the highest resolution of any spectral band is assumed for line sample values MRT expects f
44. erized Sinusoidal ISIN Lambert Azimuthal LA Lambert Conformal Conic LCC Mercator MERCAT Molleweide MOL Polar Stereographic PS Sinusoidal SIN Transverse Mercator TM Universal Transverse Mercator UTM OUTPUT PROJECTION PARAMETER lt pl p2 p3 p4 p5 p15 gt This field is optional but recommended for resampling success The array field contains the 15 output projection parameter values By default all projection parameter values are set to zero with the exception of UTM When the first two UTM projection parameters are zero the projection will default to the scene center Projection parameter values are floating point and any integer values entered are automatically converted to floating point If there are fewer than 15 projection parameter values specified 12 See Appendix C for more information on projection parameters Or type swath2grid help lt projection gt at the command line MRT User s Manual April 2011 59 the remaining values are set to zero If there are more than 15 values specified the extra values will be ignored Coordinate values latitudes and longitudes should be entered in decimal degrees UTM ZONE lt zone number gt This is optional for users selecting uTM output projection type MRT will choose the appropriate zone value by default but one may be otherwise specified Valid values are 60 to 60 If present the UTM Zone overrides values sp
45. etermine the path to the existing Java executable This method will work only if the Java executable is on the current path Typing find name java will also work but this will search all mounted file systems and may take time to complete If necessary ask a system administrator where the Java bin directory is located If the Java executable is on the current path the version of Java installed on the machine can be determined by typing java version which will output something similar to this java version 1 5 0 If the version number is older than 1 5 0 the MRT GUI is not guaranteed to work In this case installing a newer Java version is recommended Automatic Installation 1 Step one for automatically installing the MRT to either Windows or UNIX systems Linux or Macintosh is unzipping the MRT download lt platform gt zip file 2 Step two is to collect the following information to facilitate successful and efficient installation e The complete pathname of the directory in which MRT will be installed full pathnames are recommended over wildcards The default will create a MRT subdirectory in the current directory but users have the option to enter a different directory path if preferred e The pathname of the directory containing the Java executable program java or java exe This pathname is not necessary on UNIX platforms if the Java executable is on the current path in which case it will be found automatically Se
46. ferred directory then selecting an existing file or by typing in a new output file name as shown below Recall that a preferred default directory for all output files may be configured using the Settings menu on the top banner of the GUI MRT User s Manual April 2011 48 MRT will expect a file extension appended to the file name and will not accept a name without it The file extension indicates the file format of the output image Adding haf will tell MRT to output to HDF EOS tif to output to GeoTIFF and hdr to output to raw binary If an existing file is selected without modifying the file name an overwrite warning will pop up E Select xj f q Look In C output y al E f EE y sd_fire_2005 FireMask tif Y sd_fire_2005 QA tif File Name sd_fire_2006 tf Files of Type hdr hdf tif y L if Select Cancel The output file format also determines how many files will be delivered at the end of processing HDF EOS output consists of one file and however many bands were processed are packed as science data sets within the file GeoTIFF and raw binary formats store one band per file so each band selected for processing results in an output file The user does not need to specify a new output GeoTIFF name for each selected band as the band name is automatically appended to the base output file name For example if both bands in a MOD14A2
47. hat the output file must be in haf format mrtmosaic i lt directory input file name list prm gt o lt directory output mosaic hdf gt To run the resample executable on the mosaic such as to reproject reformat or subset create a standard parameter file using output _mosaic haf as the input file Spectral subsetting is allowed in mrtmosaic by using the s command line switch The h switch will provide the user with header information for output mosaic The t switch will output the h v tile information read from the horizontal and vertical tile information embedded in the HDF EOS metadata For raw binary files the tile information must be specified in the filename itself Thus if the user wants to 173 use the t switch with mosaic tool the input filenames must contain h v somewhere in the filename The mosaic tool will exit with an error if the tile information is not available MRT User s Manual April 2011 34 The status information from the mosaic tool will specify the order of the input files in the output mosaic In the following example file 0 refers to the first file listed in the parameter file file 1 refers to the second file and so on When the input files do not provide a rectangular output mosaic then sections of the mosaic are filled with a background value MRT reads the FillValue for each input band and uses that value for the output background fill Ifno FillValue is specified then the defa
48. he same output resolution is desired for all bands Simply entering the following will apply the desired output pixel size to all bands selected for processing OUTPUT PIXEL SIZE 1000 MRT User s Manual April 2011 60 Appendix B MRT Raw Binary File Format This document specifies the format of the header file for the MODIS raw binary file format In this file format raw binary data and metadata are stored in separate files The header file contains information required by the MODIS Reprojection Tool MRT for processing MODIS data in the raw binary file format Header files consist of user editable ASCII text in the format described below Raw binary MODIS data are stored in individual data files with one file per band In this document the term band is used interchangeably with the HDF term Scientific Data Set or SDS Within files bands data are stored in row major order starting at the upper left corner of the image The data type may be 8 bit integer 16 bit integer 32 bit integer or 32 bit float Integer values may be signed or unsigned Two byte and four byte data types are stored in machine dependent byte order NOTE This is new as of version 4 0 All previous versions output raw binary products as big endian byte order A metadata file contains information about a corresponding data file Metadata are stored in the metadata file as user editable ASCII text in ODL format The metadata file format spe
49. he user needs to specify a radius other than that used for Sphere 19 the NODATUM option must be used For Integerized Sinusoidal and Sinusoidal projections users are allowed to specify their own sphere radius values MRT User s Manual April 2011 7 Though a data product may be referenced to a datum it is important that users understand sphere based projections technically have no datum Any sphere based output will not contain any datum information It will instead contain information pertaining to its spheroid It will be up to the user to keep track of the datum to which the data is referenced In addition the GCTP Geolib software prevents datum conversions when an initial datum is not known Thus if a product is output without a datum it can no longer be converted to another datum using the MRT software The datum value will be used as output to HDF EOS GeoTIFF and raw binary data files The datum will be specified in HDF for the HDF EOS files since HDF EOS does not support datums HDF EOS files are assumed to be referenced to WGS84 according to the HDF EOS documentation Once the MRT knows the input and output datums and has verified that the datum projection parameter combinations are valid the reprojection and datum conversion must be handled The following are the steps that will be followed by the MRT to reproject the input SIN data to the specified output projection and datum 1 Project the input data to the Geographi
50. ing nothing but MRT input Za Step two will create a base parameter file using the MRT GUL Open one input file in the GUI and enter the desired parameters see MRT GUI section below Instead of clicking Run at the end Click Save Parameter File to save the resulting prm Then exit the MRT GUI 3 Step 3 invokes the MRTBatch jar to create parameter files prm for each input file in the input data directory It also writes out a batch script that is later used to execute the processing jobs MRTBatch bat From the Command Prompt window navigate to the MRT bin directory This is where the jar file lives Type the following command to initiate parameter file and batch script generation place all fields in one line i e do not break this statement into multiple lines java jar MRTBatch jar d input directory p parameter directory input_parameter_ file o parameter file directory where input file directory is the directory in which all input files are placed e g C Project InputFiles MRT User s Manual April 2011 40 parameter file directory is the directory where the parameter file created using the GUI p was saved and to which the parameter files built by this application will be written o input parameter file is the parameter file was saved from the GUI e g mrtauto_test prm Note that the o parameter file directory is not necessary Users can omit it from the command line
51. installation to Windows platforms Backslashes are in fact now recommended when entering directory paths during installation Otherwise there are a couple of pre install checks that users are encouraged to address to ensure successful installation and execution of MRT software First note that entry of full pathnames during installation is highly recommended for all directories Wildcards and relative pathnames are accepted but the MRT may or may not set up correctly Second in order to run the MRT GUI installation of a current version of J ava is required at least the Java 2 Runtime Environment version 1 5 or the Java 2 SDK version 1 5 or later If the only intent is to use the command line interface Java is not necessary and this requirement can be ignored but GUI operations will not execute without a current Java version 7 MRT users may register as LP DAAC Tools Users by signing up at https Ipdaac usgs gov Ipdaac tools modis_reprojection_ tool Java software for all platforms may be downloaded from the Oracle Web site at http www oracle com technetwork java javase downloads index html MRT User s Manual April 2011 14 The Java directory path is needed during the installation process so have this information available during installation On Windows platforms Start Search can be used to locate the Java directories on the system On UNIX based systems such as Linux and Macintosh type which java to d
52. itude and longitude in decimal degrees INPUT LINE SAMPLE input line and sample and OUTPUT PROJ COORDS output projection x and y The default is LAT LONG and the value specified for this field must match the type of values specified in the spatial subset list l spatial _subset list note lower case L Output UL and LR corner coordinates The entries in this quoted floating point list must correspond with the spatial subset type field For example spatial subset type INPUT LAT LONG then spatial subset list should consist of the UL corner latitude UL corner longitude LR corner latitude LR corner longitude To input coordinates by line and sample a quoted integer list consisting of the start UL corner line start UL corner sample end LR corner line and end LR corner sample may be used The third option is to specify the output projection coordinates of the UL and LR corners Thus it may be a quoted floating point list consisting of the UL projection x UL projection y LR projection x and LR projection y values Values must appear in the specified order separated by white space Latitude longitude and projection x y values should represent the outer extent of the UL and LR corners of the subset x pixel size Output pixel size This may be specified for each band processed in output projection units meters for all projections except Geographic which requires decimal degree units For example a user who selected five bands
53. jection IPS cuidan it a a E E added 50 Quiput Pixel TIE A A E E E 52 Load or Save Parameter Filio a a Aaa sas odds 52 EXCUSA dis 52 Exating the CUL aia 53 Format CONVE id AA A AA a ta lant 54 Mosaic dot e ed nc ed 54 Crd sd da Aia 56 A O AA 56 Appendix A MRT Parameter File Format ccccccccsccssscssseesseeeeeeeecseecseecaeceaecesecssecseeseceeeaeseseseeeenseesaes 57 File naming conventions ii a A a an 57 Editing parameter ld A A EE DA 57 Paramotor ttle To MA AA AA AA A sale E A a AS 57 Appendix B MRT Raw Binary File ForMat oooooononnnicnnoonnoonnnonnnannnnn cono cono ncon nono nono nn con nr nr naar rn ran rnnr rra 61 Fil naming CONVENIOS 1 e 61 Header dle OM a a e Mana dad 62 Editing Acad ls di 63 INOUCS untar A A AE a die bien A RE 63 Appendix C Projection Parameters ieceri iecere E EE EEE EERE TEE KEE ea E 65 Projection Parameters 8 iii iia da iii ii 65 Projection Parameters 9515 ocna oadecte siege sence E E senda E E E dada 66 INOUE Feces lts tt AAA ea tv cane fet nts EE en thea E a nl bos 68 MRT User s Manual April 2011 3 Introduction The Moderate Resolution Imaging Spectroradiometer MODIS was launched into space aboard the National Aeronautics and Spaces Administration NASA Earth Observing System EOS platform Terra in December 1999 A second MODIS sensor was launched on the Aqua platform in May 2002 The objective of MODIS is to provide a comprehensive series of global observations of Earth s land ocean
54. jection i e decimal degrees for Geographic and meters for all other projections The upper right and lower left corners will be computed from the specified UL Corner and LR Corner to create a rectangle in output space defined by the map projection specified later These output corners are mapped back to input space to determine their location in input space The final product after processing should have the same image corner coordinates as specified by the user but note that MRT will adjust the lower right corner based on output pixel size if its location does not fall in an integral number of lines and samples The MRT expects that the upper left and lower right corner point values of any input or output HDF EOS file whether appearing in the Input File Info orentered in Spatial Subset will reflect the outer extents of the image i e upper left of the upper left and lower right of the lower right not to the center of the upper left and lower right pixels Be aware however that GeoTIFF output will be tagged with coordinates from the center of pixel Specify Output File After entering all the necessary Source information the next step is to define the Destination parameters The first is the name of the output file which is user defined through a dialog box invoked by clicking the Specify Output File button on the top of the right pane on the GUI Similar to the dialog for opening files output file naming is done by navigating to a pre
55. lation process and could result in display or execution errors 6 Step six is a recommended system or session restart to ensure the changes made during MRT installation take effect Adding a Shortcut Icon in Windows MRT has an icon file in the Windows distribution package It is located in the MRT bin directory A shortcut icon for the MRT can be created and used on the Windows platforms To create a shortcut icon follow these steps 1 Click the right mouse button on the desktop 2 Select New gt Shortcut 3 Type in the path and name for the ModisTool bat file or use the Browse button to find the ModisTool bat file which should be in the MRT bin directory e g C Program Files MRT41 MRT bin ModisTool bat 4 Select Next 5 Type a name for the shortcut i e ModisTool MRT etc 6 Select Finish MRT User s Manual April 2011 16 10 11 12 13 Right click on the shortcut icon that was just created Select Properties Select the Shortcut tab Press Change Icon Click OK to choose an icon from the list or specify a different file Type in the path and name for the ModisToo1 ICO file or use the Browse button to find the ModisTool ICO file which should be in the MRT bin directory Press OK then OK The MRT icon should now be available on the desktop When the icon is double clicked the MRT GUI should appear Manual Installation Three steps are required for manual installation of the MRT e Unzip
56. lenames namegame surf refl b01 tif See Appendix A for more information about the parameter file MRT User s Manual April 2011 30 namegame surf refl b02 tif namegame 250m _quality tif For multi dimensional products 3rd and 4th dimension slices are names as follows lt SDS name gt lt 3rd dimension name gt lt 4th dimension name gt where is a two digit value representing the data slice for the associated dimension Obviously if the product only has three dimensions the lt 4th dimension name gt will not appear This naming convention is used for the output filenames the output HDF EOS band names and the band names in the GUI The 3 D and 4 D naming convention produces long names when the band name 3rd dimension name and 4th dimension name are all of substantial length themselves Currently the HDF EOS library for the Windows platform will support only 57 characters for band names which produces problems with the MRT naming convention on the Windows platforms For the Windows platforms if the output band name is going to be longer than 57 characters the naming convention is then changed as follows to produce smaller output band names lt SDS name gt 3 4 resampling type Resampling kernel type CUBIC CONVOLUTION NEAREST NEIGHBOR or BILINEAR The default is NEAREST NEIGHBOR output projection type Output projection short name Valid values are AEA Albers Equ
57. loat values containing a decimal point to define input latitude and longitude coordinates and integer values to indicate line sample pairs If any entered value is float then INPUT LAT LONG will be assumed Note that spatial subsetting takes place in the input image space not the output image space OUTPUT FILENAME lt directorypath outputfilename extension gt The output file name is required The name may optionally contain a directory path UNIX users are advised to enclose file names in double quotes A file extension must be included as it is used to automatically determine output file type hdr Raw Binary ndf HDF EOS tif GeoTIFF An invalid or missing extension will generate an error Note that an existing file with the same name as specified in OUTPUT FILENAME will be overwritten by resample RESAMPLING TYPE lt NN BI CC gt This field is optional The default resampling type is NEAREST NEIGHBOR NN unless specified as BILINEAR BI or CUBIC_CONVOLUTION CC OUTPUT PROJECTION TYPE lt AEA ER GEO GOODE HAM ISIN LA LCC MERCAT MOL PS SIN TM UTM gt This field is required for resampling but optional for format conversion The output projection type may be one of the following Albers Equal Area AEA Equirectangular ER Geographic GEO Interrupted Goode Homolosine GOODE Hammer HAM Integ
58. meters simply click Load Parameter File navigate to the desired prm and click Open This will restore all the parameters in the Source and Destination fields on the GUI The fields can be edited any time prior to clicking Run The saved prm can also be used to feed command line processing see Batch Processing section Executing resample Having entered all the desired Source and Destination parameters for projection click Run either on the bottom of the GUI s right pane or under the Action menu on its top left As resample executes a Status window will pop up to display job progress Its contents are simultaneously being appended to a processing log that tracks every MRT session The log is useful for troubleshooting and is found in the MRT User s Manual April 2011 52 MRT bin as resample log The log is an ASCII text file that users may edit or print with standard text file tools IES Status ox pa esample processing band FireMask ie complete 849 rows 0 10 20 30 40 50 60 70 80 90 100 Houtput image extents lat lon UL 49 999999996000 124 457906126000 UR 49 999999996000 91 377093884813 LL 39 994439043821 124 457906126000 LR 39 994439043821 91 377093684813 loutput image extents X Y projection units UL 124 457906126000 49 999999996000 UR 91 377093884813 49 999999996000 LL 124 457906126000 39 994439043821 LR 91 377093684613 39 994439043621 j band type lines smpl
59. ms are written in C so some of the flags are centered on what the C compiler linker and archive are expecting Other flags indicate commands to copy remove and move files The following lists the compile flags used by the Makefiles MRT User s Manual April 2011 25 Flag Description The CC flag indicates the compiler to be used It could be set to gcc cc or xlc for ce example depending on system particularities The CFLAGS flag indicates any switches that need to be passed on to the C compiler CFLAGS For GNU C 03 Wall W Wno switch is used for example Users need to figure out what switches apply to their C compiler The LDFLAGS flag indicates the libraries and switches to be passed on to the linker One LDFLAGS switch that is used for supported platforms to pass to the GNU linker is the s switch which strips the executable of any debug information The libraries needed depends on the application being built The AR flag indicates the archive command that needs to be run to create the static or AR x 61 o 113 29 dynamic library The current setting is set at ar resv CP The CP flag indicates the command to copy files and the current setting is set to cp RM The RM flag indicates the command to remove a file and the current setting is set to rm f MV The MV flag indicates the command to move a file and the current setting is set to mv 3
60. ne or zero If zero a zone code must be specified SMajor Semi major axis of ellipsoid If zero Clarke 1866 in meters is assumed SMinor If zero a spherical form is assumed eccentricity squared of the ellipsoid if less than one or if greater than one the semi minor axis of ellipsoid Sphere Radius of reference sphere If zero 6370997 meters is used STDPAR Latitude of the standard parallel STDPR1 Latitude of the first standard parallel STDPR2 Latitude of the second standard parallel CentMer Longitude of the central meridian OriginLat Latitude of the projection origin FE False easting in the same units as the semi major axis FN False northing in the same units as the semi major axis TrueScale Latitude of true scale LongPol Longitude down below pole of map Factor Scale factor at central meridian Transverse Mercator or center of projection Hotine Oblique Mercator CentLon Longitude of center of projection CenterLat Latitude of center of projection Height Height of perspective point Long1 Longitude of first point on center line Hotine Oblique format A Long2 Longitude of second point on center line Hotine Oblique format A Lat1 Latitude of first point on center line Hotine Oblique format A MRT User s Manual April 2011 68 Lat2 Latitude of second point on center line Hotine Oblique format A AziAng Azimuth angle east of north of center line Hotine Oblique format B AzmthPt Longitude
61. of point on central meridian where azimuth occurs Hotine Oblique Mercator format B IncAng Inclination of orbit at ascending node counter clockwise equator SOM format A AscLong Longitude of ascending orbit at equator SOM format A PSRev Period of satellite revolution in minutes SOM format A LRat Landsat ratio to compensate for confusion at northern end orbit SOM format A use 0 5201613 PFlag End of path flag for Landsat 0 start of path end of path SOM format A Satnum Landsat Satellite Number SOM format B Path Landsat Path Number Use WRS 1 for Landsat 1 2 and 3 and 2 for Landsat 4 5 and 6 SOM format B Shapem Oblated Equal Area oval shape parameter m Shapen Oblated Equal Area oval shape parameter n Angle Oblated Equal Area oval rotation angle NZone Number of equally spaced latitudinal zones rows must be 2 or larger and even RFlag Right justify columns flag is used to indicate what to do with zones with an odd number of columns If it has a value of 0 or 1 it indicates the extra column is on the right zero or left one of the projection y axis If the flag is set to 2 the number of columns are calculated so there are always an even number of column in each zone Array elements 14 and 15 are set to zero All array elements with blank fields are set to zero All angles latitudes longitudes azimuths etc are entered in decimal degrees and the MRT then converts them to packed degree
62. pecified Output pixel size specification must be in meters unless projecting to a Geographic mapping grid in which case decimal degrees must be used The specified output pixel size will be used to process all selected bands through the GUI but command line allows distinction between output pixel sizes per band Parameter Files Whether invoked via the GUI or the command line MRT executables are directed by a parameter file containing all the information necessary to read MODIS data from an input data file transform the data into a specified output projection and write the results to an output file The parameter file contains the file names and file types of the input and output data files spectral and spatial subsetting information output projection type output projection parameters output UTM zone if necessary output resampling type and output pixel size Parameter files are generated automatically through the MRT GUL and can be saved for later use either through the GUI or the command line interface They are distinguished by a prm extension and formatted as ASCII text which may be created and edited in any text editor Starting with a base parameter file from the GUI and modifying as necessary is recommended to avoid accidental processing errors should the user wish to construct a parameter file for command line use The parameter file format is described fully in Appendix A Metadata MRT extracts useful information from th
63. ple file that can be examined for content 1 Tn the command line MRT space around tokens is not required List values may be separated by either white space or commas MRT User s Manual April 2011 57 INPUT FILENAME lt directorypath inputfilename hdf gt The input data file name is a required field that provides requisite processing information Only MODIS HDF EOS file names are accepted The file name may contain a directory path UNIX users are advised to enclose file names in double quotes An invalid file name or non swath product will generate an error SPECTRAL SUBSET bandl band2 bandn This field is optional by default all input image bands will be selected This is an n element array of binary values corresponding to the n bands Scientific Data Set or SDS elements in the input data set In this array a indicates that a band was selected and a 0 indicates that it was not If there are fewer binary values than input image bands the remaining bands will not be selected If there are more binary values than input image bands the extra values will be ignored SPATIAL SUBSET TYPE lt INPUT LAT LONG INPUT LINE SAMPLE OUTPUT PROJ COORDS gt This field is required only if spatial subsetting is desired Spatial subsets may be defined using input latitude and longitude coordinates input lines and samples or output projection X and Y coordinates If neith
64. put and output filename changes addressed via command line arguments Consider the following shell iteration tor 1 an hdt do resample p prmfile prm i i o basename i hdf tif done This example reprojects every HDF EOS file in the current directory using a single parameter file prmfile prm The input and output filenames are changed in the parameter files for each file The output is written to GeoTIFF with the same base filename as the input file Any of the fields listed in the previous Resample Tools section can be modified as direct arguments MRT User s Manual April 2011 39 Automated Batch Processing Since the 2008 release of MRT an automated batch processing package is available that runs MRT from command line with minimal interference from the user It sits with the other MRT software in the bin directory e g C Program Files MRT Tool bin and is called MRTBatch jar This file contains the scripts needed to automate prm and bat builds and to execute the batch processing Its usage is described in the following steps e Gather all input files Create parameters files for each input and write a batch script Execute the batch script The sections above on Batch Processing describe the functions wrapped into MRTBatch jar which automates this otherwise very manual process To use MRTBatch jar follow the steps below 1 Step one is to simply gather all input files in an exclusive directory contain
65. r s Manual April 2011 21 to c Program Files MRT Tool and MRT DATA DIR would be set to c Program Files MRT Tool data It is recommended that any previous values specified for these keys are removed Close the Registry Editor after the keys have been updated 3 In step 3 the ModisTool bat script used to run the MRT GUI is created manually This script will configure the variables PATH MRT_HOMI E and MRT DATA DIR for the GUI The bat can be generated in any text editor such as Notepad and should be saved to the MRT bin directory Below is an example that can be copied as a template for creating this file It assumes the directory structure used in the examples above Make sure to replace all directory information in the template to reflect the structure of the host machine Note that the final statement starting with c Program Files Java is all on one line Do not break this statement into multiple lines Save the file in the bin e g c Program Files MRT Tool bin as ModisTool bat A system restart is advised to ensure the changes made during MRT installation take effect and the tools function as expected echo off rem KKEKKKKKKKKKKKKK KK rem ModisTool bat rem KKKKKKK KK KK KK rem Set the MRT HOME environment variable to the MRT installation directory set MRT HOME C Program Files MRT Tool rem Set the MRT DATA DIR environment variable to the data directory set MRT DATA DIR
66. r 21 11 19 09 2011 April 2011 min max 254 fill 255 36 Batch Processing Options The command line MRT is fully scriptable for batch processing of MODIS data There are a number of ways to use this functionality all of which involve the creation of parameter files for each input and directing the MRT to use them for processing Users may execute specific jobs with parameter files that are simple to automate using either script batch files or iterative commands depending on the host operating system The MRTBatch jar capability is also available to facilitate the set up for running batch processing jobs Windows Batch Processing For example a user may wish to project a time series of fire data to the same mapping grid Any text editor can be used to create a parameter file prm for each file in the series The scenario below is based on only 5 files but applies to any number of inputs Input File List MOD14A2 A2005185 MOD14A2 A2006185 MOD14A2 A2007185 MOD14A2 A2008185 MOD14A2 A2009185 Parameter File MOD14A2 A2005 prm Appendix A INPUT FILENAME SPECTRAL SUBSET h10v04 h10v04 h10v04 h10v04 h10v04 1 1 SPATIAL SUBSET_TY SPATIAL SUBSET_UL SPATIAL SUBSET_LR OUTPUT FILENAME _CORNE _CORNE D MRT4 1 output sd_ fire 2005 tif 0 0 0 0 0 R R 05 05 05 05 05 eo
67. rdinates are the same value This tolerance value should be sufficient for MODIS tiles but if this software is used in the future for data from other higher resolution images then a more appropriate tolerance value will be needed for processing those products MRT User s Manual April 2011 13 MODIS Reprojection Tool Installation To obtain the MRT software users are required to create an account on the LP DAAC Tools Web site a quick process that will enable notifications of software related information such as new releases After successful login users can download the appropriate platform specific MRT zip file from the same site The MRT software is delivered in MRT_download_ lt platform gt zip that needs to be unzipped before installation After the MRT package MRT lt platform gt zip is extracted from the download zip package the software can be installed with either an automatic or a manual installation process The automatic installation process is recommended but instructions for both methods are outlined below Pre Installation Users no longer need to carefully place software or files in directories with no spaces in their path names as required by previous MRT versions As of version 4 1 MRT will install and run in any specified directory This applies to both the MRT and Java directories Further related to directory paths it is also no longer necessary to use forward slashes instead of backslashes during MRT
68. rea SMajor SMinor STDPR1 STDPR2 CentMer OriginLat FE FN 4 Lambert Conformal C SMajor SMinor STDPR1 STDPR2 CentMer OriginLat FE FN 5 Mercator SMajor SMinor CentMer TrueScale FE FN 6 Polar Stereographic SMajor SMinor LongPol TrueScale FE FN 7 Polyconic SMajor SMinor CentMer OriginLat FE FN 8 Equid Conic A SMajor SMinor STDPAR CentMer OriginLat FE FN Equid Conic B SMajor SMinor STDPR1 STDPR2 CentMer OriginLat FE FN 9 Transverse Mercator SMajor SMinor Factor CentMer OriginLat FE FN 10 Stereographic Sphere CentLon CenterLat FE FN 11 Lambert Azimuthal Sphere CentLon CenterLat FE FN 12 Azimuthal Sphere CentLon CenterLat FE FN 13 Gnomonic Sphere CentLon CenterLat FE FN 14 Orthographic Sphere CentLon CenterLat FE FN 15 Gen Vert Near Per Sphere Height CentLon CenterLat FE FN 16 Sinusoidal Sphere CentMer FE FN 17 Equirectangular Sphere CentMer TrueScale FE FN 18 Miller Cylindrical Sphere CentMer FE FN 19 Van der Grinten Sphere CentMer OriginLat FE FN MRT User s Manual April 2011 20 Hotin Oblique Merc A SMajor SMinor Factor OriginLat FE FN Hotin Oblique Merc B SMajor SMinor Factor AziAng AzmthPt OriginLat FE FN 21 Robinson Sphere CentMer FE FN 22 Space Oblique Merc A SMajor SMinor IncAng AscLong FE FN Space Oblique Merc B SMajor SMinor Satnum Path FE FN 23 Alaska Conformal SMajor SMinor FE FN 24 Interrupted Good Sphere 25 Mollweide Sphere CentMer FE
69. ril 2011 4 MODIS Reprojection Tool Capabilities Platforms MRT is highly portable software available for four platforms and has been tested on the following systems Windows NT 32 bit Linux 32 bit Linux 64 bit Macintosh OS X 32 bit Though they were not tested MRT is expected to install and run on other systems such as Windows Vista and Windows 7 Consult the Release Notes for platform specific differences and caveats Interfaces MRT may be invoked either from a user friendly GUI or from a powerful command line interface The GUI allows novices and users with light processing requirements to reproject convert and subset MODIS tiled data The GUI also allows easy inspection of metadata The scriptable command line interface with its variety of command line options is likely to be the method of choice for reprojecting large numbers of files Data Products MRT currently allows reprojection of all gridded levels 2G 3 and 4 MODIS Land data products Support for swath levels 1B and 2 data is available in the MRTSwath application Most MODIS products are 2 Dimensional 2 D but there are some 3 D and 4 D data sets e g the MCD43 BRDF Albedo suite The MRT supports 3 D and 4 D data products and currently outputs them to 2 D data products for raw binary georeferenced tagged image file format GeoTIFF and HDF EOS output formats File Formats MRT accepts raw binary or tiled MODIS Land products in HDF EOS form
70. rmat without reprojecting The possible input and output formats are described in File Formats above The Format Converter will support spectral and spatial subsetting When doing format conversion the resampling process will be skipped The output projection type and output projection parameters are not needed and will be ignored if specified In gt Summary information on the GCTP software is available from http gcmd nasa gov records USGS GCTP html MRT User s Manual April 2011 6 format conversion the output projection type is the same as the input projection type and the output projection parameters are the same as the input projection parameters The output pixel size 1f specified will be ignored remains the same as the input pixel size as does the output data type NOTE A simple command line tool called hdf2rb is used for format conversion from HDF to raw binary It does not rely on geographic information and therefore works well with bounding tiles Mosaic Tool MRT can mosaic several tiles together before reprojecting them Mosaicking is done automatically from the GUI by selecting several filenames for the input filename The input files are mosaicked first and then reprojected Mosaicking can also be done via the command line using the mrtmosaic executable Datum Conversions A limited number of input and output datums are supported by the MRT for datum conversions Supported datums are North American Datum
71. s and atmosphere at higher spatial resolutions 250 meter m 500 m 1 000 m than its predecessor the Advanced Very High Resolution Radiometer AVHRR and more frequently near daily overpass than its orbital neighbor Landsat 7 MODIS observations are critical for studies of climate vegetation pollution global change and many other important economic and environmental issues The MODIS Reprojection Tool MRT was developed to support higher level MODIS Land products which are distributed as Hierarchical Data Format Earth Observing System HDF EOSY files projected to a tile based Sinusoidal grid MRT software facilitates the use of MODIS Land tiles by providing map projection format conversion and spectral and spatial subsetting options and is compiled for use on multiple operating systems MRT functionality is based on the resample and mrtmosaic executables that may be run either from the command line or from a Graphical User Interface GUI The GUI is an easy user friendly way to input data for manipulation and the more powerful command line interface serves users with intensive data processing requirements This User s Manual describes the use of both to run the MRT resample and mrtmosaic programs More information about MODIS is available from http modis gsfc nasa gov More information about HDF and HDF EOS is available from http www hdfgroup org and http hdfeos net respectively MRT User s Manual Ap
72. s minutes seconds DDDMMMSSS SS format for the call to GCTP MRT User s Manual April 2011 69
73. s of 1927 NAD27 and 1983 NAD83 and World Geodetic Systems of 1966 WGs66 1972 WGS72 and 1984 wes84 User specification of the output datum is supported as part of the output parameters for the MRT in both the GUI and command line interfaces The GUI uses a datum drop down box to allow the datum to be specified This drop down box has NODATUM set as the default with options to select available datums If the command line version is being used then the datum should be specified using the DATUM parameter in the parameter file entering either any of the datums listed above or NODATUM If no value is provided for the DATUM in the parameter file NODATUM will be used as the default A datum is a standard definition of the semi major and semi minor axes of a shape If the NODATUM option is selected MRT will expect the user to enter spheroid information in the first two fields of the projection parameters for all the MRT supported projections except UTM and Geographic If the semi major and semi minor axes are not specified while the NODATUM is selected MRT will exit with an error Likewise if semi major and semi minor axes are entered in the projection parameters and a specific datum is selected the MRT will exit with an error Please note that the current GCTP package automatically uses the radius of Sphere 19 6370997 m for any sphere based projections except for Sinusoidal and Integerized Sinusoidal Until this is fixed in GCTP if t
74. s pixsiz min max fill 1 FireMask UINTS 849 2807 0 0118 0 9 0 End Time Tue Mar 22 16 24 56 2011 Finished processing EAAARAARARER AER RARA AREA ERRE RRE RARA AREA RARER AER R ARA AREA RARE REN ARA ARANA NRARAR a i I gi Clear Close When the Run button is clicked the GUI creates a temporary parameter file TmpParam prm in the bin directory and runs resample using that parameter file resample p TmpParam prm This file is overwritten on subsequent runs but not deleted so it can be examined with any ASCII text file viewer editor when processing is complete Exiting the GUI To exit the MRT GUI click the Exit button or click File Exit on the menu bar on the top banner on the GUI The standard operating system commands e g double click on the X in the upper right hand corner of the window in Microsoft Windows MRT User s Manual April 2011 53 Format Conversion The previous section Resampling Tool directed use of the MRT GUI to execute the resample software The MRT also provides a file format converter which allows conversion from input HDF EOS to output GeoTIFF or raw binary without resampling Running the format converter is similar to the resample option please see section above for details on parameters discussed here The Input File information must be specified first then the Output File name and Output File Type As with resampling the default
75. se TmpMosaic hdf file size exceeds this limit This has been observed when numerous tiles are input for mosaicking e g Africa but is dependent on the data type A 250 m product has more volume than a 1 000 m product and so a mosaic of twenty tiles with 1 000 m pixels may be more successful than the same for 250 m pixels MRT User s Manual April 2011 55 Credits The MODIS Reprojection Tool was developed as a collaborative effort between the Land Processes Distributed Active Archive Center at the U S Geological Survey Earth Resources Observation and Science Center and the South Dakota School of Mines amp Technology Contacts LP DAAC is the main user support facility for this tool reports and other comments may be addressed to LP DAAC User Services U S Geological Survey USGS Earth Resources Observation and Science Center EROS 47914 252 Street Sioux Falls SD 57198 0001 Phone 605 594 6116 Toll Free 866 573 3222 Fax 605 594 6963 Email lpdaac usgs gov Web https Ipdaac usgs gov MRT User s Manual April 2011 Download and installation assistance bug 56 Appendix A MRT Parameter File Format Parameter files are user editable ASCII text files that contain information required by the MODIS Reprojection Tool MRT for processing MODIS data Information entered by the user in the MRT Graphical User Interface GUI is stored in a parameter file either for future use or to run the resample e
76. secseceseceseeseeeseeeseaeeeseeeseeeaeeaaes 16 Mandal Inistallats Otis 0 a a aa Oa aa av RASS acid 17 Manual Installation Instructions for UNIX PlatformMS oooonnnoncccconancnoconancnononnononnnanononnnnnnoronnnnnnnonnnnos 17 Manual Installation Instructions for Windows Platforms ooooooccnnnoncconononanononancnnonnnnnnoonannnononannnaronnnnos 20 B lding the MRT dai lA a EA AA A Hs ak AAA A dd olive 24 Command Line erlat eccu a a A A E RRE 28 Parameters Ele A es ees Pa TR least ea tt in datas eee 28 Resample TOG mii eta 29 Mosaic Lola as 33 Batch Processiie Options nicas daa di Obey evened E a as 37 MRT User s Manual April 2011 2 Windows Batch Process A A tias 37 UNIX Bourne Shell Batch Processing cccesccssscesecesscesseeeeceeceeeseceseeeseecseecssecsaecaecuaeenseseeeeseneeneeeaas 39 Direct Argument Batch Processing cccccesccssscessceseceseceeceeeceeceeeseceseeessecseecssecsaecsaeceaeenaeeeeeeseeeeneeesgs 39 Automated Batch Processihg amina a a ii 40 MODIS Reprojection Tool GU Deneire iit did eiii ee va rta bad 42 Resampling Tola dal Ii 42 Opening an Input Fl anta ala toria densa naaa 43 Metadata Ex amination Qi idad ti a AA Leeks 45 Ti LOCO AA E AA E ii eee ta deanna 46 Spectral Subsetting zseni eena aE A larisa betta 47 Spatial SubsettiN girene a be a A A a e a T A A laa hectie 47 Specify Output Fils ts E A te 48 Output FT a E 49 Resampling Py pes mia ad daa nt aE E EE oi be E e AE AAN toads 50 Output Pro
77. sets from any input tile Spatial information is entered in the bottom third of the Source pane Users can define subset corner points either in input or output space by selecting Input Lat Long Input Line Sample or Output Projection X Y from the Spatial Subset drop down Spatial Subset UL Corner Output Projection X Y LR Corner 39 999999996 91 37851024 MRT User s Manual April 2011 47 The UL Corner and LR Corner are populated with the bounding coordinates by default These fields can be edited to specify an area of interest by simply clicking in the box and entering the bounds of the desired subset If the Spatial Subset type is set to Input Lat Long enter corner points in decimal degrees To subset using Input Line Sample specify line sample pairs using a zero based coordinate system assuming the upper left corner is 0 0 MRT will use Input Lat Long or Input Line Sample to automatically compute the other two rectangle corners upper right and lower left in input space All four corner points will be projected into output space using the map projection specified later on the Destination side of the GUI A minimum bounding rectangle is computed in output space that contains the four projected points All points inside this rectangle in output space are mapped back into input space for projection When creating a subset based on Output Projection X Y these coordinates must be specified in the same units used for the pro
78. t no processing parameters were included in the command mrtmosaic Usage mrtmosaic i input filenames file t h o output filename MRT User s Manual April 2011 33 s spectral subset bl b2 bN g filename for the log file where input filenames file is a text file which contains the names of the files to be mosaicked If using the s switch the SDSs should be represented as an array of Os and 1s A 1 specifies to process that SDS 0 specifies to skip that SDS Unspecified SDSs will not be processed If t is specified then the tile locations of the input filenames are output to tile txt o s and h are not needed Raw binary files must specify the tile locations in the filename to be used with the t switch i e mod09ghk h02v16 hdr If h is specified then the mosaicked header information will be output to TmpHdr hdr o s and t are not needed NOTE Only input Sinusoidal and Integerized Sinusoidal projections are supported for mosaicking Example mrtmosaic I TmpMosaic prm s 1 1 0 1 o mosaic hdf This will mosaic the first second and fourth SDSs in each of the specified HDF files in TmpMosaic prm Warning mosaic General Processing Error processing the arguments for the mosaic tool To simply mosaic multiple tiles such as prior to resampling create a parameter file listing the input filenames Then type the following command all on one line Note t
79. tency between the native 463 3 m MODIS pixels and other 500 m data sets The output will be written to the GeoTIFF file MODO9GA tif Since the UL and LR corner points were not specified the bounding coordinates from the input file s global attributes will be used for the output corner points Resample Tool From the command prompt typing resample resampl help or resampl help param in the MRT bin directory results in a brief usage message that lists various command line arguments used to execute MRT These are the fields typically included in a parameter file but via command line any or all of them may be modified Detailed descriptions of each parameter field follow the usage message below MODIS Reprojection Tool v4 1 March 2009 Usage RESAMPLE p parameter file options Options that override parameter file specifications i input_file_name o output file name r resampling type NN BI CC NONE t projection_type AEA ER GEO HAM IGH ISIN LA LCC MERCAT MOL PS SIN TM UTM j projection parameter list pl p2 p15 s spectral subset b1 b2 bN If using the s switch the SDSs should be represented as an array of Os and 1s A 1 specifies to process that SDS 0 specifies to skip that SDS Unspecified SDSs will MRT User s Manual April 2011 29 not be processed be processed If the s switch is not specified then all SDSs will
80. tion the fields on the left side of the pane and Destination information right side have been entered respectively These File options mirror the button functions on the GUI MRT User s Manual April 2011 42 ModisTool of x File Action Settings Help Source Destination Input Files Specify Output File Open Input File Output File po i View Metadata Output File Type View Selected Tile Resampling Type Input File Info Nearest Neighbor v Output Projection Type Edit Projection Parameters Output Pixel Size e Available Bands Selected Bands ae Commands E Load Parameter File Save Parameter File Spatial Subset gt Parameter File Latitude Longitude RUN Cc i a UL Corner Run Convert Format The Action menu includes the Run and Convert functions and is simply an alternative to clicking the Run and Convert Format buttons on the bottom right side ofthe GUL Use the Settings menu to set the default directory locations for input files output files and parameter files This is useful as otherwise MRT will default to its bin directory for everything The Help menu contains About information and will open a popup displaying the version and release date for the installed MRT Opening an Input File Start on the left pane of the GUI where Source information is entered Click
81. tory in which the MRT will be finally installed For example to install the MRT in C Program Files MRT Tool type the command as follows unzip MRT Win zip d c Program Files MRT Tool 2 Step two is to update the system variables to recognize the PATH MRT_HOME and MRT DATA DIR needed to run MRT Windows NT XP users must edit their user keys to add the MRT PATH MRT HOME and MRT DATA DIR to the system variables Invoke a Command Prompt window from Start Programs Accessories and type regedit at the DOS prompt Administrative privileges may be needed to complete this step This will bring up a GUI containing user key information Double click on the HKEY CURRENT_USER key then click on the Environment key The current user key environment variables and their values will be listed on the right hand side of the GUI If the keys MRT DATA DIR MRT HOME and PATH do not exist go to the Registry Editor menu bar at the top of the GUI and click Edit From there select New then String Value to create a new user key The keys for PATH MRT HOME and MRT DATA DIR should be listed in the right pane of the Registry Editor Each can be double clicked to modify their values Continuing with the above example the PATH would be modified to add c Program Files MRT Too1 bin to the end of the current string entering a semi colon to separate directories in the path The MRT HOME would be set MRT Use
82. tting the path to the Java executable The following lines are appended to profile or bash profile files in the home directory MRT User s Manual April 2011 18 bin sh PATH SPATH SHOME My MRT bin MRT DATA DIR SHOME My MRT data MRT HOME SHOME MRT export MRT HOME PATH MRT DATA DIR Note that the final statement starting with lt path_to_java_bin gt java is all on one line Do not break this statement into multiple lines These changes will not take effect without restarting a new login session Also be aware that each new installation will append the environment variable statements to the startup files so it is advisable to remove these lines prior to a new install 3 In step 3 the ModisTool shell script used to run the MRT GUI is created manually This script will configure the variables PATH MRT _HOME and MRT DATA DIR The ModisTool script can be generated in any text editor and should be saved to the MRT bin directory Below is an example that can be copied as a template for creating this file using any text editor It assumes the directory structure used in the examples above Make sure to replace all directory information in the template to reflect the structure of the host machine Note that the final statement indicating the Java path is all on one line Do not break this statement into multiple lines Save the file in the bin e g home user My MRT bin as Modis
83. ude line Along this line data do not cover all 10 x 10 degrees of a tile as they do for interior tiles The blank space is populated with fill data to complete the tile MRT User s Manual April 2011 11 The projection coordinates of one to three corner points in a bounding tile fall in the discontinuity space In this case the MRT will process the tile as usual but issue a warning to the user It will cite that a certain corner point does not have a valid latitude longitude and will be adjusted accordingly When MRT passes bounding tile projection coordinates into the transformation package GCTP provides the output latitude and longitude values Because of their proximity to the 180 0 180 0 line the returned longitude values wrap around it and fall on the other side of the Earth When these GCTP coordinates are further passed to the forward mapping algorithm the output projection coordinates will not match those of the input For example the upper right corner of MODIS bounding tile h27v03 falls in discontinuity space and therefore it longitude will map to the other side of the 180 0 180 0 line The Sinusoidal projection coordinates for this tile are as follows UL x y in meters 10007554 677000 6671703 118000 LR x y in meters 11119505 196667 5559752 598333 Upper right and lower left corners are derived by squaring off the tile UR x y in meters 11119505 196667 6671703 118000 LL x y in meters 10007554 677000 5559752 5
84. ult value is 0 In the Mosaic Array see below fill areas are designated as file 9 MODIS Mosaic Tool v4 1 March 2009 Start Time Mon Mar 21 11 18 58 2011 Input filenames 4 D ModisSave testdata MOD12Q1 A2000289 h24v02 002 2001103225932 hdf D ModisSave testdata MOD12Q1 A2000289 h25v02 002 2001103225927 hdf D ModisSave testdata MOD12Q1 A2000289 h26v03 002 2001103225927 hdf D ModisSave testdata MOD12Q1 A2000289 h27v03 002 2001103231505 hdf Output filename D ModisSave testdata TmpMosaic hdf Mosaic Array file 0 file 1 file 9 file 9 file 9 file 9 file 2 file 3 Mosaic processing band Land Cover Type 1 complete 1200 rows 0 10 20 30 40 50 60 70 80 90 100 complete 1200 rows 0 10 20 30 40 50 60 70 80 90 100 Output mosaic image info output image corners lat lon UL 70 000000000000 120 006250000000 UR 70 000000000000 180 000000000000 50 000000000000 120 006250000000 LR 50 000000000000 180 000000000000 output image corners X Y projection units UL 6671703 118599000387 7783653 638365999795 UR 11119505 197665000334 7783653 638365999795 6671703 118599000387 5559752 598833000287 LR 11119505 197665000334 5559752 598833000287 MRT User s Manual April 2011 35 1 End Time band Land Cover Type 1 Finished mosaicking MRT User s Manual type lines smpls pixsiz UINT8 2400 4800 926 6254 Mon Ma
85. which will result in a prm directory containing the new parameter files being built in the input file directory instead 4 Step four will run the MRTBatch created just above The MRTBatch bat contains a list of commands to run the MRT on every input file according to the parameter files Change directories at the Command Prompt to go to the MRT bin directory Tell MRT what to do by typing the directory path and name of the batch file such as shown below Windows C Program Files MRT Tool bin mrtbatch bat UNIX SHOME My MRT bin mrtbatch The results of the processing job will echo out in log form on the command prompt display and when completed files should be ready in the output directory specified in the original base parameter file MRT User s Manual April 2011 41 MODIS Reprojection Tool GUI Resampling Tool This section of the User s Manual describes how to run resample from the MRT GUI This GUI serves two purposes one it helps a novice user or one with light processing needs to enter all requisite inputs and process those jobs two it helps users with heavier processing requirements to enter all requisite inputs and save them in a parameter file which they may edit and use to run resample from command line Users may also load saved parameter files into the GUI for inspection and or editing To start the GUI type ModisTool from within the MRT bin directory at the command prompt doubleclick on the MRT
86. xecutable In fact the MRT GUI is basically a parameter file editing tool This document specifies the MRT parameter file format which for the most part stores information as field value pairs corresponding to GUI fields and values File naming conventions By convention all related files in a data set should be given the same base filename Different extensions indicate the file type parameter files prm header files hdr metadata files met HDF EOS files ndf and GeoTIFF files t if Editing parameter files Parameter files may be created and modified in two ways by directly editing the parameter file with an ASCII text editor or by using the MRT GUI In the MRT GUI selecting Load Parameter File allows the user to load values from an existing parameter file Selecting Save Parameter File allows the user to save the current parameter values to a specified parameter file Parameter file format The parameter file consists of field value pairs and comments Comments begin with the character and extend to the end of the line Each field must begin on a new line and may span more than one line for convenience and readability Fields may occur in any order All field value tokens must be separated by white space including the equals and parentheses symbols To verify the format of any of the fields below enter the desired information using the GUI then use the Save Parameter File button to generate a sam

Download Pdf Manuals

Related Search

Related Contents

TK-2302/ TK-3302 - [::] Kenwood ASC  Nokia MD-3 Car Speaker User Manual  Ferrari by Logic3 Scuderia R100  OZONE WORLD LIMITED  SEMS User Manual  取扱説明書 - 自転車  DC3 5-Port HUB Installation Guide (DRC 304-A)  Galaxy classic series 8/18/60/128    FlexScan T761/T962 Manuel d`utilisation  

Copyright © All rights reserved. Failed to retrieve file