• TIFIMG: TIFF-IMG format conversion

Direct access to online help: TIFIMG

Access the application from the menu:
"File | Import | Rasters | TIFF, GeoTIFF -> IMG"
"File | Export | IMG -> TIFF, GeoTIFF"

Presentation and options

This application allows bidirectional transformation of TIFF and IMG files. In addition to its general purpose, it also allows multiband import (radiometric bands, quality, etc.) of USGS Landsat data collections 1 and 2. In the case of collection 2, both Level 1 and Level 2 processing data can be imported.

Application options:

The order in which the options are presented in this previous explanation, in the application dialog box and in the syntax corresponds to their conceptual grouping, by type of transformation (information, transformations from TIFF to the several types of IMG and from IMG to the various types of TIFF). However, the numbering of the options is correlative according to the order in which they have been programmed over the years.

Information TIFF (option 0): This option shows the header information of the TIFF file.

TIFF to IMG (b/n 1 bit) (option 1): This option transforms TIFF files b/n (1 bit) to IMG files (1bit).

TIFF to IMG (gray 8 bits) (option 2): This option transforms gray TIFF files or DTM (any number of bits, integers or reals) to IMG files of the same type.

TIFF to IMG (palette, 8 or 16 bits) (option 3): This option transforms TIFF files with palette (8 or 16 bits, integer) to an IMG file of the same type and palette.

TIFF to IMG RGB (option 4): This option transforms multiband TIFF (RGB) files to 3 IMG file (one per band), of the types of the TIFF bands, typically byte; the 3 IMG files are related to a multiband REL. In order to facilitate the visualization of the RGB composition in IMG format, a MiraMon Map file (.mmm) is also generated, which allows this composition to be opened directly.

TIFF to IMG multiband (option 4): This option transforms multiband TIFF files to one IMG file per band, of the types of TIFF bands.

TIFF to IMG Landsat multiband (option 9): This option transforms Landsat multiband TIFF files to one IMG file per band, of the TIFF band types, except if they are from the Landsat series Collection 2, which are generated in real values already converted to reflectances on the ground.

IMG a TIFF (b/n 1 bit) (option 5): This option transforms IMG files (1bit) to a TIFF file b/n (1 bit).

IMG to TIFF (gray 8 bits) (option 6): This option transforms IMG files (gray scale) to a TIFF file without palette, of the types of IMG bands.

IMG to TIFF (palette, 8 or 16 bits) (option 7): This option transforms IMG files to a TIFF file with palette, of the type of IMG bands, typically byte or 16-bit integers type.

IMG to TIFF (RGB) (option 8): This option transforms IMG (RGB) files into a 24-bit color TIFF file.

In imports of TIFF to IMG the presence of both a World file (* .TFW or * .TIFW) as of the GeoTiff format. In case of contradiction, the georeference of the World file prevails.
In IMG exports to TIFF, a GeoTiff format and a TFW.

Both the World file and the GeoTiff format allow georeference a TIFF file by assigning a pixel side and some extreme coordinates (bounding box).

In case that a TIFF file contains control points for its georeferencing, these are stored in a table with the same name than the output IMG but adding the "_GCP" suffix.

Other richest possibility in metadata is to use the DIMAP format. In In this case, the metadata is distributed in a file in XML format (from extension .dim). A file of the same name as the TIFF is supported but of extension .dim or directly a file Metadata.dim such com is distributed in a DIMAP product folder (then the TIFF file is called Imagery.tif). SPOT images are distributed this way.
More information about the DIMAP format: https://www.intelligence-airbusds.com/en/8722-the-dimap-format

General notes:

• The TIFF and IMG extensions are assumed in each case.
• There are two ways to determine the names of the IMG files resulting from converting a multiband TIFF: fixing a specific file name for each band, when the total number of bands is known; specifying a destination directory for the resulting files, and the application will automatically generate numbered file names for each band (in this case it is recommended to specify a common prefix for the names to avoid conflicts with results from other runs).
• For RGB conversions it is assumed that the file names are given in the order "Red" "Green" "Blue".
• For conversions with palette, the PAL extension must be added in order to obtain the scaled palette with 64 intensity levels per color channel, the P25 extension if the scaled palette with 256 intensity levels is desired, and the P65 extension if the scaled palette with 65536 intensity levels is choosed. It is also possible to define the DBF extension. The DBF format is the MiraMon standard for palettes and symbolization tables. (The P25 format was the standard in version 3 or lower).

Specific notes:

• Landsat images may have undergone NLAPS or LPGS processing:
• NLAPS: Landsat images processed by NLAPS (National Land Archive Production System), typically with WO.txt (Work Order) metadata file extension. According to USGS documentation, NLAPS processing was discontinued in 1999 and LPGS processing should be selected for later processed images.
• LPGS: Landsat images processed by LPGS (Landsat Product Generation System), typically with MTL.txt (Metadata Text File) metadata file extension.

More information about NLAPS and LPGS can be found through the following link, as well as in the article:

Cristóbal, J., Pons, X., Serra, P. (2004) Sobre el uso operativo de Landsat-7 ETM+ en Europa. Revista de Teledetección, 21:55-59. http://www.aet.org.es/revistas/revista21/AET21-11.pdf


• To understand some of the concepts discussed below it may be convenient to read the following article on Collection 2 of the Landsat series:
Pons, X., Cea, C., González-Guerrero, O., Cristóbal, J. (2025) Landsat Collection 2: Key Information and Recommendations for Data Users and Product Developers. Revista de Teledetección, 66, e23510. https://doi.org/10.4995/raet.2025.23510


• Importing data from Collection 2, (for each MSS, TM, ETM+ and OLI/TIRS sensor) generates the layers specified in the following files:
  MSS: https://d9-wret.s3.us-west-2.amazonaws.com/assets/palladium/production/s3fs-public/atoms/files/LSDS-1416_LandsatMSS-C2-L1-DFCB-v3.pdf
  TM: https://d9-wret.s3.us-west-2.amazonaws.com/assets/palladium/production/atoms/files/LSDS-1415_Landsat4-5-TM-C2-L1-DFCB-v3.pdf
  ETM+: https://d9-wret.s3.us-west-2.amazonaws.com/assets/palladium/production/atoms/files/LSDS-1414_Landsat7ETM-C2-L1-DFCB-v3.pdf
  OLI/TIRS: https://d9-wret.s3.us-west-2.amazonaws.com/assets/palladium/production/atoms/files/LSDS-1822_Landsat8-9-OLI-TIRS-C2-L1-DFCB-v6.pdf
• In the application window it is possible to activate the generation of file names (and descriptors) in the MiraMon language if this does not match the language of the images. Otherwise, as is the case with Landsat images imported into the MiraMon english language version, the option is disabled by default.


Examples of output files from a Landsat 8 Collection 2 and processing level 1, imported into MiraMon and generating file names in the MiraMon language.
In English or by default	In Catalan	In Spanish
LC08_L1TP_20210116_B1-CA_RT.img	LC08_L1TP_20210116_B1-LA_RT.img	LC08_L1TP_20210116_B1-LA_RT.img
LC08_L1TP_20210116_B2-B_RT.img	LC08_L1TP_20210116_B2-B_RT.img	LC08_L1TP_20210116_B2-A_RT.img
LC08_L1TP_20210116_B3-G_RT.img	LC08_L1TP_20210116_B3-V_RT.img	LC08_L1TP_20210116_B3-V_RT.img
LC08_L1TP_20210116_B4-R_RT.img	LC08_L1TP_20210116_B4-R_RT.img	LC08_L1TP_20210116_B4-R_RT.img
LC08_L1TP_20210116_B5-NIR_RT.img	LC08_L1TP_20210116_B5-IRp_RT.img	LC08_L1TP_20210116_B5-IRp_RT.img
LC08_L1TP_20210116_B6-SWIR1_RT.img	LC08_L1TP_20210116_B6-IRoc1_RT.img	LC08_L1TP_20210116_B6-IRoc1_RT.img
LC08_L1TP_20210116_B7-SWIR2_RT.img	LC08_L1TP_20210116_B7-IRoc2_RT.img	LC08_L1TP_20210116_B7-IRoc2_RT.img
LC08_L1TP_20210116_B8-PAN_RT.img	LC08_L1TP_20210116_B8-PAN_RT.img	LC08_L1TP_20210116_B8-PAN_RT.img
LC08_L1TP_20210116_B9-Ci_RT.img	LC08_L1TP_20210116_B9-Ci_RT.img	LC08_L1TP_20210116_B9-Ci_RT.img
LC08_L1TP_20210116_B10-LWIR1_RT.img	LC08_L1TP_20210116_B10-IRol1_RT.img	LC08_L1TP_20210116_B10-IRol1_RT.img
LC08_L1TP_20210116_B11-LWIR2_RT.img	LC08_L1TP_20210116_B11-IRol2_RT.img	LC08_L1TP_20210116_B11-IRol2_RT.img
LC08_L1TP_20210116_BQA-DesignatedFill_RT.img	LC08_L1TP_20210116_BQA-ForaDEscena_RT.img	LC08_L1TP_20210116_BQA-FueraDeEscena_RT.img
LC08_L1TP_20210116_BQA-DilatedCloud_RT.img	LC08_L1TP_20210116_BQA-NuvolDilatat_RT.img	LC08_L1TP_20210116_BQA-NubeDilatada_RT.img
LC08_L1TP_20210116_BQA-Cirrus_RT.img	LC08_L1TP_20210116_BQA-Cirrus_RT.img	LC08_L1TP_20210116_BQA-Cirrus_RT.img
LC08_L1TP_20210116_BQA-Cloud_RT.img	LC08_L1TP_20210116_BQA-Nuvol_RT.img	LC08_L1TP_20210116_BQA-Nube_RT.img
LC08_L1TP_20210116_BQA-CloudShadow_RT.img	LC08_L1TP_20210116_BQA-OmbraNuvol_RT.img	LC08_L1TP_20210116_BQA-SombraNube_RT.img
LC08_L1TP_20210116_BQA-Snow_RT.img	LC08_L1TP_20210116_BQA-Neu_RT.img	LC08_L1TP_20210116_BQA-Nieve_RT.img
LC08_L1TP_20210116_BQA-ClearSky_RT.img	LC08_L1TP_20210116_BQA-CelClar_RT.img	LC08_L1TP_20210116_BQA-CieloClaro_RT.img
LC08_L1TP_20210116_BQA-Water_RT.img	LC08_L1TP_20210116_BQA-Aigua_RT.img	LC08_L1TP_20210116_BQA-Agua_RT.img
LC08_L1TP_20210116_BQA-CloudConfidence_RT.img	LC08_L1TP_20210116_BQA-ConfiancaNuvol_RT.img	LC08_L1TP_20210116_BQA-ConfianzaNube_RT.img
LC08_L1TP_20210116_BQA-CloudShadowConfidence_RT.img	LC08_L1TP_20210116_BQA-ConfiancaOmbra_RT.img	LC08_L1TP_20210116_BQA-ConfianzaSombra_RT.img
LC08_L1TP_20210116_BQA-SnowIceConfidence_RT.img	LC08_L1TP_20210116_BQA-ConfiancaNeuGel_RT.img	LC08_L1TP_20210116_BQA-ConfianzaNieveHielo_RT.img
LC08_L1TP_20210116_BQA-CirrusConfidence_RT.img	LC08_L1TP_20210116_BQA-ConfiancaCirrus_RT.img	LC08_L1TP_20210116_BQA-ConfianzaCirrus_RT.img
LC08_L1TP_20210116_BQA-B6-SWIR1-RS_RT.img	LC08_L1TP_20210116_BQA-B6-IRoc1-RS_RT.img	LC08_L1TP_20210116_BQA-B6-IRoc1-RS_RT.img
LC08_L1TP_20210116_BQA-B7-SWIR2-RS_RT.img	LC08_L1TP_20210116_BQA-B7-IRoc2-RS_RT.img	LC08_L1TP_20210116_BQA-B7-IRoc2-RS_RT.img
LC08_L1TP_20210116_BQA-Radiometric-TerrainOcclusion_RT.img	LC08_L1TP_20210116_BQA-OcultatPelTerreny_Radiometric_RT.img	LC08_L1TP_20210116_BQA-OcultadoPorElTerreno_Radiometrico_RT.img
LC08_L1TP_20210116_4-SAA_RT.img	LC08_L1TP_20210116_4-AIA_RT.img	LC08_L1TP_20210116_4-AAS_RT.img
LC08_L1TP_20210116_4-SZA_RT.img	LC08_L1TP_20210116_4-AIZ_RT.img	LC08_L1TP_20210116_4-AAV_RT.img
LC08_L1TP_20210116_4-VAA_RT.img	LC08_L1TP_20210116_4-AVA_RT.img	LC08_L1TP_20210116_4-ACS_RT.img
LC08_L1TP_20210116_4-VZA_RT.img	LC08_L1TP_20210116_4-AVZ_RT.img	LC08_L1TP_20210116_4-ACV_RT.img
LC08_L1TP_20210116_I.rel	LC08_L1TP_20210116_I.rel	LC08_L1TP_20210116_I.rel

• Changes applied to the values read from some bands: All angle bands originally have a value of 0 in the "outer" part of the image, but this value can be confused with the value of the angle 0, which may be plausible in the azimuth bands at mid-latitudes, and also in the zenith angles at latitudes where the Sun may be in this position (perhaps never at the time of Landsat passage, but possible in certain areas of the Earth), so the 0s in the area that in the QA-DesignatedFill image is 1 are changed to -32768 and it is documented that this is the value of the NoData of these 4 angle bands.
  The same argument applies to the other quality bands, where for example the 0 that means "no" to what the band reports, becomes a "no" outside the scene, which is again a problematic value; since these bands are not bits but bytes, a value of 255 has been given and values outside the scene have been marked as NoData.
• Reading and storing specific keys from the Landsat product metadata file, MTL:
  • The key "LANDSAT_PRODUCT_ID" is assigned to the alternative title.
  • The key "DIGITAL_OBJECT_IDENTIFIER" is assigned to the unique identifier of the data.

  The horizontal reference system quality parameters corresponding to the following keys are stored in the metadata:

  • GROUND_CONTROL_POINTS_MODEL
  • GEOMETRIC_RMSE_MODEL
  • GEOMETRIC_RMSE_MODEL_Y
  • GEOMETRIC_RMSE_MODEL_X
  • GROUND_CONTROL_POINTS_VERIFY
  • GEOMETRIC_RMSE_VERIFY

  Thermal constants are added to the comments section.

  GROUP = LEVEL1_THERMAL_CONSTANTS

  • K1_CONSTANT_BAND_10
  • K2_CONSTANT_BAND_10
  • K1_CONSTANT_BAND_11
  • K2_CONSTANT_BAND_11

  Other parameters incorporated into comments are the following:

  • COLLECTION_NUMER
  • COLLECTION_CATEGORY
  • PROCESSING_LEVEL
  • PROCESSING_SOFTWARE_VERSION (Processing Software)
  • DATE_PRODUCT_GENERATED
  • NADIR_OFFNADIR
  • CLOUD_COVER
  • CLOUD_COVER_LAND
  • IMAGE_QUALITY_OLI
  • IMAGE_QUALITY_TIRS
  • TIRS_SSM_MODEL
  • TIRS_SSM_POSITION_STATUS
  • DATA_SOURCE_TIRS_STRAY_LIGHT_CORRECTION
  • ROLL_ANGLE
  • SUN_AZIMUTH
  • SUN_ELEVATION
  • EARTH_SUN_DISTANCE
  • TRUNCATION_OLI
  • REFLECTANCE_MAXIMUM_BAND_X
  • REFLECTANCE_MINIMUM_BAND_X
  • RESAMPLING_OPTION
  

• Thesaurus generation: they are generated only if the pixel in the band takes three or more values. If it takes only two, the description itself contains the meaning of these values. The program generates a "Thesaurus" folder in the output directory itself with the necessary thesaurus.

• In the radiometry section, the consistency between the keys RADIANCE_MINIMUM_BAND_# and RADIANCE_MAXIMUM_BAND_#, where # is the band number, and the keys QUANTIZE_CAL_MIN_BAND_# and QUANTIZE_CAL_MAX_BAND_#, and the keys RADIANCE_MULT_BAND_# and RADIANCE_ADD_BAND_# is checked. If an inconsistency is detected, an error message is issued. These data are interdependent and, therefore, everything is checked to be accurate and consistent. It is ensured that if any of the data is missing in an MTL, the corresponding calculation can be made, or the converters can be assumed in the case of the last two (RADIANCE_MULT_BAND_# and RADIANCE_ADD_BAND_#) if the first 4 do not exist.

In old versions, in which there was sometimes indeterminacy in whether 0 acted as a NoData or not, uncertain situations could occur that could generate a small inaccuracy in the calculations of the transformation slope if the assumption was incorrect. These inaccuracies, if they existed, were small (clearly smaller than the inaccuracy in the absolute calibration offered by the sensor), but control has also been strengthened in this aspect.

Below is an example with the MTL values and those added in the Radiometry section.

• RADIANCE_MAXIMUM_BAND_4 = 225.200
• RADIANCE_MINIMUM_BAND_4 = -17.600
• QUANTIZE_CAL_MAX_BAND_4 = 255
• QUANTIZE_CAL_MIN_BAND_4 = 1
• RADIANCE_MULT_BAND_4 = 9.5591E-01
• RADIANCE_ADD_BAND_4 = -18.55591


When importing Landsat data with processing level 2, the parameter groups that allow estimating the values of "terrain reflectances" or BOA reflectances are read, and the fields related to Radiance Calibration (or Spectral Radiances) in the radiometry section are left blank.

GROUP = LEVEL2_SURFACE_REFLECTANCE_PARAMETERS
• REFLECTANCE_MULT_BAND_# = 2.75e-05
• REFLECTANCE_ADD_BAND_# = -0.2

The estimated values of "ground reflectances" are calculated in percentages (%), and therefore differ from the units in DN (in fact, Qcal) provided by data with processing level 1. In each case these units are saved in the corresponding section of the metadata.

If this transformation in the processing level 2 data is not desired, but the .img data in the same byte or unsigned integer values (depending on the Landsat series sensor) within the TIF is wanted, it is possible to use TIFIMG in mode 2 (not 9) for specific bands, or GDALMM (which will import, however, less metadata), or once the TIF is open in MiraMon, select everything with the "Select all" button from the object selection box (right mouse button) and save the selection as .img. It should be noted, however, that this "manipulated" level 2 product is of little use without the conversion to % Reflectances for which it has been pre-calculated, and that is why the default TIFIMG import completes this pre-calculation.

An example is shown below with the values that are added in the Radiometry section for the case of Landsat data with level 2 processing.


• Two distributors (NASA-USGS and MiraMon) are added to the distribution tab, as well as two formats (the MTL extract and the extra-compressed IMG RLE itself).


• In the application window there is an option to compress the output IMG files.


By default, "Compress extracompressed indexed RLE" is enabled. If this option is disabled, /NO_COMPRESS appears on the command line.



---

Dialog box of the application

TIFIMG dialog box



---

Examples

TIFIMG 3 SCAN256 IMA256 IMA256.P25
TIFIMG 4 RGB BANDA_1 BANDA_2 BANDA_3
TIFIMG 4 MULTIBAN C:\RESULTADOS /PREFIX=BANDA_
TIFIMG 8 MOAG_7 MOAG_4 MOAG_3 D:\IMATGES\MOAG_FC 250000



---

Syntax

Syntax:

• TIFIMG 0 InputTIFFfFile [/TFW] [/DOC] /stdout
• TIFIMG 1 InputTIFFfFile ResultIMGFile [/TFW] [/DOC] [/NO_COMPRIMIR] [/IDIOMA]
• TIFIMG 2 InputTIFFfFile ResultIMGFile [/TFW] [/DOC] [/NO_COMPRIMIR] [/IDIOMA]
• TIFIMG 3 InputTIFFfFile ResultIMGFile PALFile [/TFW] [/DOC] [/NO_COMPRIMIR] [/IDIOMA]
• TIFIMG 4 InputTIFFfFile IMG_RFile IMG_GFile IMG_BFile [/TFW] [/DOC] [/NO_COMPRIMIR] [/IDIOMA]
• TIFIMG 4 InputTIFFfFile ResultsDirectory [/PREFIX] [/BANDES] [/TFW] [/DOC] [/NO_COMPRIMIR] [/IDIOMA]
• TIFIMG 9 ListFile ResultsDirectory Processing Radiometry [/META] [/MD] [/IDIOMATIC] [/NO_COMPRIMIR] [/IDIOMA]
• TIFIMG 5 OriIMGFile TIFFfile [Scale]
• TIFIMG 6 OriIMGFile TIFFfile [Scale]
• TIFIMG 7 OriIMGFile PALFile TIFFfile [Scale]
• TIFIMG 8 RedFile GreenFile BlueFile TIFFfile [Scale]

Options:

• 0: Header information of a TIFF file.
• 1: Transformation to IMG bit.
• 2: IMG byte transformation.
• 3: IMG transformation with palette.
• 4: Transformation to IMG multiband (whether 3 RGB bands or any number of bands)
• 9: Transformation to IMG Landsat multiband
• 5: Transformation to TIFF bit
• 6: Transformation to TIFF without palette.
• 7: Transformation to TIFF with palette.
• 8: Transformation to TIFF 24 bits

Parameters:

• InputTIFFfFile (Input TIFF file - Input parameter): TIFF file name from which you want to obtain the header information or to transform to IMG file.
• ResultIMGFile (Result IMG file - Output parameter): It is the name of the IMG file transformation result.
• PALFile (Palette file - Output parameter): It is the name of the palette file
• IMG_RFile (IMG red file - Output parameter): It is the name of the result IMG file of the red band.
• IMG_GFile (IMG green file - Output parameter): s the name of the result IMG file of the green band.
• IMG_BFile (IMG blue file - Output parameter): Is the name of the result IMG file of the blue band.
• ResultsDirectory (Results directory - Output parameter): Is the results directory where the files will be stored.
• ListFile (TIFF list file - Input parameter): The name of the file list of TIFF layers.
• Processing (Processing - Input parameter):
  • 1 LPGS
  • 0 NLAPS
• Radiometry (Radiometry - Input parameter):
  • 0 Metadata.
  • 1 Chander.
• OriIMGFile (Origin IMG file - Input parameter): Is the name of the IMG file that will be transformed to TIFF file.
• TIFFfile (TIFF file - Output parameter): Is the name of the output TIFF file.
• Scale (Scale - Input parameter): It is the denominator of the scale in which the TIFF files will be represented. Only used in the conversion from IMG to TIFF. Default value is 100000.
• RedFile (Red file - Input parameter): Is the name of the IMG file of the red band.
• GreenFile (Green file - Input parameter): Is the name of the IMG file of the green band.
• BlueFile (Blue file - Input parameter): Is the name of the IMG file of the blue band.

Modifiers:

/PREFIX= (PREFIX) Is the prefix of the result File. (Input parameter)
/BANDES= (BANDS) In order not to convert all bands, the band indices (integer numbers, using 1 for the first band of the TIF) to convert must be indicated, separated by commas (for example: 1,4,5,7). (Input parameter)
/TFW= (TFW directory) It allows to indicate the directory where to look for the World file (*.Tfw or *.TIFW) to be applied for georeferencing during TIFF to IMG imports. If not indicated, the World file is searched in the TIFF directory. (Input parameter)
/DOC= (File pattern to document) It allows to indicate a raster file of reference of what Inherit the documentation. Never inherit the number of rows or of columns or the range of values. In case of presence of file World or GeoTiff format its value prevails over of this file. (Input parameter)
/META= (META file) Allows you to indicate the auxiliary metadata file (* .META) for Landsat images (TM, ETM + and MSS) (* .TIF) for images processed using LPGS. This file will allow documenting the capture time of the image that is in some metadata files (* .TXT). this file It should only be included in conjunction with the file metadata for Landsat. (Input parameter)
/MD= (Metadata file) Allows you to indicate the metadata file (* .TXT) for images Landsat (TM, ETM + and MSS) (* .TIF) for both images processed by NLAPS or by LPGS. This file will allow you to document the REL associated with the image. It is important not to rename these files, which should have the WO and MTL termination depending on whether it is processed NLAPS or LPGS respectively. (Input parameter)
/IDIOMATIC (Generate filenames in the MiraMon language) In the case of multiband importing from Landsat satellites the output file names can be generated in the MiraMon language as well as the field descriptors. (Input parameter)
/NO_COMPRIMIR (Generate IMG files without compression) To obtain imported IMG files without compression, this modifier parameter must be settled. By default, all TIFIMG imports are compressed in the 'RLE extra-compressed indexed' format. (Input parameter)
/IDIOMA= (Generate file names and descriptors in the desired language; ENG, CAT, SPA) If, for example, the default language of MiraMon is Catalan but /IDIOMA=SPA /IDIOMATIC is indicated on the command line (note that the /IDIOMATIC modifier is being added), both the metadata and the file names and their descriptors will be generated in Spanish. In the same situation with the default language in Catalan, but indicating /IDIOMA=SPA and without adding the /IDIOMATIC modifier, the metadata will be generated in Spanish but the file names and their descriptors in English (Landsat default names). Finally, and still in the same situation with the default language in Catalan, but adding the /IDIOMATIC modifier, both the metadata and the file names and their descriptors will be generated in Catalan. (Input parameter)