Global Mapper script files allow the user to create custom batch processes that make use of the functionality built in to Global Mapper. From a script, one can import data in any of the numerous formats supported by the software, reproject that data if desired, and export it to a new file.
Global Mapper script files consist of a series of command lines. Each command line begins with a command. A series of parameter/value pairs should follow the command. These pairs should be written as parameter=value. No spaces should exist before or after the equal sign. Individual parameter/value pairs should be separated by spaces. If a pair requires spaces internal to the value, quotes may be used around the entire value. For example, for a filename with spaces, the pair could look like FILENAME="c:\\my documents\\test.tif". Parameters that expect a value of YES or NO to enable or disable functionality can (starting with v13.1) be enabled with just the parameter name. So rather than saying FLAG_PARAM_NAME=YES, you can just say FLAG_PARAM_NAME to get the same behavior as specifying yes.
Command lines typically consist of one line
each. To extend a command to another line, use the backslash character
(\) at the end of the line. There are a few exceptions to this, including
the DEFINE_PROJ and DEFINE_SHAPE commands and the looping functionality
provided by the DIR_LOOP_START and DIR_LOOP_END commands.
To access a list of commands regularly
updated by Global Mapper developers, please check the Global
Mapper Script Commands online.