Instructions to convert a MAP file to other formats

Convert to FITS

• Use the AltWG toolset to get the proper format

Maplet2FITS --configFile fitsConfig_orex_spc.ini RAD201.MAP RAD201-fullv1.fits

• An example ini file can be found here fitsConfig_spc.ini.

• Notes from Ray Espiritu on 5 May 2020 about the ini file "It may look familiar as it has the same format as the nft config files you send me for generating MLNs. Format is KEYWORD#value. Notice that “//” denotes comment lines. This does not allow you to add custom keywords; the keyword has to exactly match a keyword that is normally populated in the fits header."

• There will still be some header information you will want to change. For this use ChangeFitsHeader, also part of the AltWG distribution toolset.

• More notes from Ray Espiritu on 5 May 2020 for "This tool allows you to add,delete, or modify keywords in the header. Run “ChangeFitsHeader –examples” to see examples for each operation (add, delete, modify, change). There is a limitation inherent in the fits format in that the new fits header cannot have a size difference of more than 2880 bytes from the old fits header. You shouldn’t encounter that if you are adding or deleting a handful of keywords."

Convert to GeoTIFF

• First, convert to FITS format (and update headers as necessary).
• Use GDAL to convert from FITS to GeoTIFF

gdal_translate -a_srs RAD201-v5.prj -a_ullr -8510 8510 8510 -8510 RAD201-fullv1.fits RAD201-fullv1.tif

• An example of the prj file can be found here.