EXPORT_ELEVATION
The EXPORT_ELEVATION command exports all currently loaded elevation data to a file. The following parameters are supported by the command.
- FILENAME - full path to file to save the data to
- EXPORT_LAYER - filename or description of layer(s) to export. By default all compatible and exportable layers are exported. You can include multiple EXPORT_LAYER parameters if you have multiple masks to search. Wildcards (* and ?) are supported. Hidden layers are not considered. To export just the layer(s) selected in the Control Center, use EXPORT_LAYER="SELECTED LAYERS".
-
TYPE
- type of elevation file we're exporting to:
- FIRST_LOADED - export to the same type as the first loaded file
- LAST_LOADED - export to the same type as the last loaded file
- ARCASCIIGRID - export an Arc ASCII Grid format file.
- BIL - export to a BIL format file (simple binary format with header).
- BIP- export to a BIP format file.
- BLUE_MARBLE_GRID - export grid shift file for Geographic Calculator.
- BSQ - export to BSQ format file.
- BT - export to a BT (Binary Terrain) format grid file.
- COG - exports a cloud-optimized GeoTIFF. This is a GeoTIFF with overview layers added and a tiled layout.
- DTED - export to DTED format grid files.
- DXF_3DFACE - export a DXF 3D face format file.
- DXF_MESH - export a 3D DXF mesh format file.
- DXF_POINT - export a 3D DXF point format file.
- ERDAS - export to an Erdas Imagine IMG format file.
- ERM_GRID - export ERMapper grid file.
- FLOATGRID - export a Float/Grid format file.
- GEOSOFT_GRID - export to a Geosoft grid format file.
- GEOTIFF - export to a GeoTIFF format file.
- GLOBAL_MAPPER_GRID - export to a Global Mapper Grid format file.
- GRAVSOFT_GRID - export to a Gravsoft Grid format file.
- GWS - export to Windsim GWS.
- HF2 - export to a HF2/HFZ format file.
- INM_3TX - export FAA INM 3TX format grid.
- IDRISI_RASTER - export to an Idrisi elevation format file.
- LANDXML - export elevation data to a Land/XML format file.
- LEVELLER_HF - export to a Leveller heightfield file.
- LIDAR_LAS - export to a Lidar LAS/LAZ file. Use .laz in filename to get LasZip.
- MAPMAKERTERRAIN - export to a MapMaker Terrain format file.
- NITF - NITF format terrain file
- OPTIMI_GRID - export optimi terrain grid.
- PLS_CADD - PLS-CADD terrain file
- ROCKWORKS_GRID - export to a RockWorks Grid format file.
- SRTM - exports SRTM HGT 1x1 degree tiles. See SRTM_LEVEL in Other Format Specific fields to set the level.
- STL - export to a STL format file
- SURFERGRID - export to a Surfer Grid format file. The FORMAT parameter specifies whether it is an ASCII or binary format Surfer Grid file.
- TERRAGEN - export to a Terragen terrain file.
- UCD - export AVS UCD file.
- USGS_DEM - export to a native format USGS DEM file.
- VRML - export to a VRML file.
- VULCAN_3D - export to a Vulcan3D triangulation file.
- VMAPPER_GRID - export to a Vertical Mapper Grid file.
- XYZ_GRID - export to a XYZ Grid file.
- ZMAP_PLUS - export to ZMap+ grid format.
- ELEV_UNITS - specify elevation units to use in export
- FEET - export in US feet
- DECIFEET - export in 10ths of US feet
- METERS - export in meters
- DECIMETERS - export in 10ths of meters
- CENTIMETERS - export in centimeters
- SPATIAL_RES - specifies spatial resolution. Defaults to the minimum spatial resolution of the two layers if not specified. Should be formatted as x_resolution,y_resolution. The units are the units of the current global projection. For example, if UTM was the current global projection and you wanted to export at 30 meter spacing, the parameter/value pair would look like SPATIAL_RES=30.0,30.0. You can also specify as a percentage of the default resolution by adding a percent. For example to get half the detail your double the spatial resolution value, so you would use SPATIAL_RES="200%,200%".
- SPATIAL_RES_METERS - specifies spatial resolution to use in meters. The value in meters will automatically be converted to the curent view/export projection units. For example, to do an export at 2.0 meter spacing (or as close as you can get to that in the current units), use SPATIAL_RES_METERS=2.0, or to do an export at 1.0 meters in X by 1.5 meters in Y, use SPATIAL_RES_METERS="1.0,1.5".
- FORCE_SQUARE_PIXELS - if this value is set to YES, the spatial resolution of the resultant elevation file will be set so that the x and y pixel size are the same, with the minimum default size being used for both.
- SAMPLING_METHOD (elevation and raster only) - specifies the sampling method to use when resampling this layer. The following values are supported:
- DEFAULT - Use either automatic resampling based on export or layer resampling, depending on setting of global flag about whether to resample on export
- AUTO - Automatically select a resampling method based on how the export resolution and bounds compare to the original layout for a layer. For example if you export to a lower resolution a box averager of appropriate size may be used automatically
- LAYER - Use the sampling method set for each layer
- The list of SAMPLING_METHOD values for the IMPORT command can also be specified to use a particular sampling method for all layers being exported.
- Shared IMPORT SAMPLING_METHOD valuesThe following values are supported
- NEAREST_NEIGHBOR - use the nearest neighbor sampling method
- BILINEAR - use bilinear interpolation
- BICUBIC - use bicubic interpolation
- BOX_2X2 - use a 2x2 box average
- BOX_3X3 - use a 3x3 box average
- BOX_4X4 - use a 4x4 box average
- BOX_5X5 - use a 5x5 box average
- BOX_6X6 - use a 6x6 box average
- BOX_7X7 - use a 7x7 box average
- BOX_8X8 - use a 8x8 box average
- BOX_9X9 - use a 9x9 box average
- MAX_2X2 - use maximum value found in 2x2 box (for image layers, use brightest color)
- MAX_3X3 - use maximum value found in 3x3 box (for image layers, use brightest color)
- MAX_4X4 - use maximum value found in 4x4 box (for image layers, use brightest color)
- MAX_5X5 - use maximum value found in 5x5 box (for image layers, use brightest color)
- MAX_6X6 - use maximum value found in 6x6 box (for image layers, use brightest color)
- MAX_7X7 - use maximum value found in 7x7 box (for image layers, use brightest color)
- MAX_8X8 - use maximum value found in 8x8 box (for image layers, use brightest color)
- MAX_9X9 - use maximum value found in 9x9 box(for image layers, use brightest color)
- MED_2X2 - use median value found in 2x2 box
- MED_3X3 - use median value found in 3x3 box
- MED_4X4 - use median value found in 4x4 box
- MED_5X5 - use median value found in 5x5 box
- MED_6X6 - use median value found in 6x6 box
- MED_7X7 - use median value found in 7x7 box
- MED_8X8 - use median value found in 8x8 box
- MED_9X9 - use median value found in 9x9 box
- MIN_2X2 - use minimum value found in 2x2 box (for image layers, use darkest color)
- MIN_3X3 - use minimum value found in 3x3 box (for image layers, use darkest color)
- MIN_4X4 - use minimum value found in 4x4 box (for image layers, use darkest color)
- MIN_5X5 - use minimum value found in 5x5 box (for image layers, use darkest color)
- MIN_6X6 - use minimum value found in 6x6 box (for image layers, use darkest color)
- MIN_7X7 - use minimum value found in 7x7 box (for image layers, use darkest color)
- MIN_8X8 - use minimum value found in 8x8 box (for image layers, use darkest color)
- MIN_9X9 - use minimum value found in 9x9 box (for image layers, use darkest color)
- BLUR_3X3 - perform a Gaussian Blur using 3x3 kernel
- BLUR_5X5 - perform a Gaussian Blur using 5x5 kernel
- BLUR_7X7 - perform a Gaussian Blur using 7x7 kernel
- GEN_WORLD_FILE - specifies that a world file (TFW for TIF, JGW for JPG, etc.) should be generated in addition to the grid file. Use GEN_WORLD_FILE=YES to turn on.
- GEN_TAB_FILE - specifies that a MapInfo TAB file should be generated in addition to the grid file. Use GEN_TAB_FILE=YES to turn on.
- GEN_PRJ_FILE - specifies that a projection (PRJ) file should be generated in addition to the data file. Use GEN_PRJ_FILE=YES to turn on.
- GEN_AUX_XML_FILE - specifies that an ESRI .aux.xml projection file should be generated in addition to the data file. Use GEN_AUX_XML_FILE=YES to turn on.
- OVERWRITE_EXISTING - specifies that existing files should be overwritten. The default is OVERWRITE_EXISTING=YES, so use OVERWRITE_EXISTING=NO to skip exporting files that already exist.
- FILL_GAPS - specifies that small gaps in between and within the data sets being exported will be filled in by interpolating the surrounding data to come up with an elevation for the point in question. This option is on by default, specify FILL_GAPS=NO to turn off.
- SAMPLE_TYPE - specifies what type of samples will be exported for formats that support different data types. If provided, this parameter will take precedence over the BYTES_PER_SAMPLE and USE_UNSIGNED parameters. For example, use SAMPLE_TYPE="F32" to specify 32-bit single precision floating point samples. Here is a list of the valid values and the associated types:
- U8 - unsigned 8-bit integer
- S8 - signed 8-bit integer
- U16 - unsigned 16-bit integer
- S16 - signed 16-bit integer
- U32 - unsigned 32-bit integer
- S32 - signed 32-bit integer
- F32 - 32-bit single precision floating point
- F64 - 64-bit double precision floating point
- BYTES_PER_SAMPLE (DEPRECATED use SAMPLE_TYPE instead) - specifies how many bytes to use per elevation sample in the BIL file. Valid values are 1 byte (8 bit), 2 bytes (16-bits) and 4 bytes (32-bits). If this value isn't specified, 2 bytes are used.
- USE_UNSIGNED (DEPRECATED use SAMPLE_TYPE instead)- if exporting to 1 or 2 byte integer samples, add USE_UNSIGNED=YES to the command to get unsigned 8-bit or 16-bit values rather than the default signed values.
- USE_BIG_ENDIAN - specifies that elevation values written to BIL files should use big endian (Motorola byte order) rather than the default little endian (Intel byte order).
- USE_ESRI_HDR - specifies that the ESRI .hdr format should be used for the export. Use USE_ESRI_HDR=YES to enable.
- COORD_DELIM - specifies the delimeter between coordinates
- COMMA - coordinates are separated by commas
- FIXED_WIDTH - coordinates are stored in fixed width columns
- SEMICOLON - coordinates are separated by semicolons
- SPACE - coordinates are separated by space characters
- TAB - coordinates are separated by tab characters
- EXPORT_COLORS - specifies that RGB color values should be exported for each coordinate that is saved.
- EXPORT_ECEF - specifies that the export should use ECEF (earth-centered earth-fixed, or geocentric) coordinates.
- EXPORT_ROW_MAJOR - specifies that the XYZ values should be exported in row-major order. Use EXPORT_ROW_MAJOR=YES to enable this.
- REVERSE_ROWS - specifies that the values should be exported from bottom-to-top rather than top-to-bottom
- REVERSE_COLS - specifies that the values should be exported from right-to-left rather than left-to-right
- THIN_GRID_MAX_DELTA - specifies that the output points should be thinned in areas with elevation values that change less than the specified valu. The units are whatever units are specifed in the ELEV_UNITS parameter. By default if this value is provided the data will be divided in to grids of a max size 64x64. If all values in that grid are within THIN_GRID_MAX_DELTA of each other, only a single point will be exported. If not, 4 smaller grids of size 32x32 are examined, and so on until a single point is reached. Use THIN_GRID_PIX_SIZE to specify a different maximum subgrid size other than 64x64.
- THIN_GRID_PIX_SIZE - specifies the maximum number of samples on each side of the sub-grids examined with THIN_GRID_MAX_DELTA is specified.
- COORD_DELIM - specifies the delimeter between coordinates
- COMMA - coordinates are separated by commas
- FIXED_WIDTH - coordinates are stored in fixed width columns
- SEMICOLON - coordinates are separated by semicolons
- SPACE - coordinates are separated by space characters
- TAB - coordinates are separated by tab characters
- EXPORT_COLORS - specifies that RGB color values should be exported for each coordinate that is saved.
- EXPORT_ECEF - specifies that the export should use ECEF (earth-centered earth-fixed, or geocentric) coordinates.
- EXPORT_ROW_MAJOR - specifies that the XYZ values should be exported in row-major order. Use EXPORT_ROW_MAJOR=YES to enable this.
- REVERSE_ROWS - specifies that the values should be exported from bottom-to-top rather than top-to-bottom
- REVERSE_COLS - specifies that the values should be exported from right-to-left rather than left-to-right
- THIN_GRID_MAX_DELTA - specifies that the output points should be thinned in areas with elevation values that change less than the specified valu. The units are whatever units are specifed in the ELEV_UNITS parameter. By default if this value is provided the data will be divided in to grids of a max size 64x64. If all values in that grid are within THIN_GRID_MAX_DELTA of each other, only a single point will be exported. If not, 4 smaller grids of size 32x32 are examined, and so on until a single point is reached. Use THIN_GRID_PIX_SIZE to specify a different maximum subgrid size other than 64x64.
- THIN_GRID_PIX_SIZE - specifies the maximum number of samples on each side of the sub-grids examined with THIN_GRID_MAX_DELTA is specified.
- COORD_OFFSET (XYZ_GRID only) - specifies the offset to apply to any coordinates written to the file. This offset will be added to each coordinate written to the file. The offset should be specified as a comma-delimited list of the X, Y, and Z offsets, such as COORD_OFFSET=100000.0,200000.0,0.0
- COORD_SCALE (XYZ_GRID only) - specifies the scale factors to apply to any coordinates written to the file. Each coordinate will be multiplied by these scale factor before being written to the file. The scale factors should be specified as a comma-delimited list of the X, Y, and Z scale factors, such as COORD_SCALE=0.1,0.1,1.0
- BYTES_PER_SAMPLE - specifies how many bytes to use per elevation sample in the IMG file. Valid values are 2 bytes (16-bits) and 4 bytes (32-bits). If this value isn't specified, 2 bytes are used.
- ADD_OVERVIEW_LAYERS - specifies that overview (pyramid) layers should be generated for the export. Use ADD_OVERVIEW_LAYERS=YES to enable.
- BLOCK_SIZE - specifies the block size to use for the export. The default is BLOCK_SIZE=64.
- COMPRESS_OUTPUT - specifies whether or not the exported file should be compress. The default is COMPRESS_OUTPUT=YES.
- BYTES_PER_SAMPLE - specifies how many bytes to use per elevation sample in the IMG file. Valid values are 2 bytes (16-bits) and 4 bytes (32-bits). If this value isn't specified, 2 bytes are used.
- ADD_OVERVIEW_LAYERS - specifies that overview (pyramid) layers should be generated for the export. Use ADD_OVERVIEW_LAYERS=YES to enable.
- BLOCK_SIZE - specifies the block size to use for the export. The default is BLOCK_SIZE=64.
- COMPRESS_OUTPUT - specifies whether or not the exported file should be compress. The default is COMPRESS_OUTPUT=YES.
- VOID_ELEV - pixel value to use for noData pixels.
- SAMPLE_TYPE - specifies what type of samples will be exported for formats that support different data types. If provided, this parameter will take precedence over the BYTES_PER_SAMPLE and USE_UNSIGNED parameters. For example, use SAMPLE_TYPE="F32" to specify 32-bit single precision floating point samples. Here is a list of the valid values and the associated types:
- U8 - unsigned 8-bit integer
- S8 - signed 8-bit integer
- U16 - unsigned 16-bit integer
- S16 - signed 16-bit integer
- U32 - unsigned 32-bit integer
- S32 - signed 32-bit integer
- F32 - 32-bit single precision floating point
- F64 - 64-bit double precision floating point
- BYTES_PER_SAMPLE (DEPRECATED use SAMPLE_TYPE instead)- specifies how many bytes to use per elevation sample in the vertical GeoTIFF file. Valid values are 2 bytes (16-bits) and 4 bytes (32-bits). If this value isn't specified, 2 bytes are used.
- USE_UNSIGNED (DEPRECATED use SAMPLE_TYPE instead)- if exporting 2 byte integer samples, add USE_UNSIGNED=YES to the command to get unsigned 16-bit values rather than the default signed values.
- ADD_OVERVIEW_LAYERS - creates overview layers when exporting the file to help with rendering of larger data areas
- TILE_SIZE - specifies that the GeoTIFF file should be exported with a tiled organization and use the specified tile size. This tile size should be between 8 and 2048. Typical values are 64, 128, and 256.
- DISABLE_BIGTIFF - use to disable the automatic creation of BigTIFF-format files for very large exports. Use DISABLE_BIGTIFF=YES to disable the automatic BigTIFF support.
- TIFF_COPYRIGHT - specify text to store in TIFFTAG_COPYRIGHT tag.
- TIFF_DATETIME - specify text to store in TIFFTAG_DATETIME tag.
- TIFF_DOC_NAME - specify text to store in TIFFTAG_DOCUMENTNAME tag.
- TIFF_GT_CITATION - specify text to store in GeoTIFF GTCitationGeoKey GeoTIFF tag.
- TIFF_IMAGE_DESC - specify text to store in TIFFTAG_IMAGEDESCRIPTION tag.
- TIFF_PCS_CITATION - specify text to store in GeoTIFF PCSCitationGeoKey GeoTIFF tag.
- TIFF_NO_GTIFF_HEADER - don't embed a GeoTIFF header in the file. Use TIFF_NO_GTIFF_HEADER=YES to disable write of header.
- COMPRESSION (GeoTIFF only)- specifies the type of compression to use for the generated TIFF file. If you do not provide a compression value then no compression will be used.
- NONE - Do not compress the output.
- LZW - Use LZW (lossless) compression on the output.
- DEFLATE - Use Deflate/ZIP (lossless) compression on the output.
- VERT_CITATION - specifies the text description to store in the GeoTIFF file for the vertical coordinate system for the elevations. If nothing is supplied the default one (if any) for the supplied VERT_CS_CODE will be used.
- VERT_CS_CODE - specifies the vertical coordinate system (i.e. vertical datum) to store in the GeoTIFF file to specify what the elevations are referenced to. Use the EPSG code, like 5103 for NAVD88. If you don't specify a value and you specify a VERT_CITATION field that matches a known name, the associated VERT_CS_CODE for that name will be used. For example, VERT_CITATION="NAVD88" will provide VERT_CS_CODE=5103 by default. If neither of these are present and the source files used all use the same known system, that will be used. Note that no vertical datum conversion is done, this is just to supply metadata.
-
- VOID_ELEV - pixel value to use for noData pixels.
- EXPORT_SLOPE - use to specify that slope values should be exported rather than elevation values. Use EXPORT_SLOPE=YES to enable.
- EXPORT_SLOPE_DIR - use to specify that slope direction values should be exported rather than elevation values. Use EXPORT_SLOPE_DIR=YES to enable.
- EXPORT_SLOPE_PERCENT - use to specify that slope values should be exported as percent slope rather than degrees. Use EXPORT_SLOPE_PERCENT=YES to enable and also make sure to add EXPORT_SLOPE=YES to the command line.
- DTED_LEVEL - specifies which DTED level to export to. The values must be between 0 and 5 (with 0, 1, and 2) being the only levels supported by most applications.
- DTED_PRODUCER_CODE - specifies a producer code to store in the DTED file header. This should be in the form CCAAABBB where the first 2 characters are the country code.
- DTED_SECURITY_CLASS - specifies the security classification character to store in the DTED file header. The default is 'U' for unclassified. Other valid values are 'C' (confidential), 'S' (secret), and 'R' Restricted.
- SPLIT_INTO_FOLDERS - write each column out to separate folders by longitude. Use SPLIT_INTO_FOLDERS=YES to enable this behavior.
- SAVE_HEIGHTS_ABOVE_GROUND - specifies whether the exported LAS/LAZ file should contain raw elevations or a calculated 'height above ground'. Use SAVE_HEIGHTS_ABOVE_GROUND=YES to enable saving heights above ground. Note this requires a Global Mapper Pro license.
- LAS_VERSION - specifies what version of LAS file to write out. This would be 1.1, 1.2, 1.3, or 1.4. If you don't specify a version, the lowest version that will support all of the provided options will be used (typically 1.1 or 1.2).
- VERT_CS_CODE - specifies the vertical coordinate system (i.e. vertical datum) to store in the LAS file to specify what the elevations are referenced to. Use the EPSG code, like 5103 for NAVD88. If you don't specify a value and the source files used all use the same known system, that will be used. Note that no vertical datum conversion is done, this is just to supply metadata.
- VERT_CITATION - specifies the text description to store in the Lidar LAS file for the vertical coordinate system for the elevations. If nothing is supplied the default one (if any) for the supplied VERT_CS_CODE will be used.
- FILE_SOURCE_ID - specifies a File Source ID numeric value to store in the exported LAS file header. If not specified and one of the input files is a LAS file with this value specified it will be used.
- GLOBAL_ENCODING - specifies a Global Encoding numeric value to store in the exported LAS file header. If not specified and one of the input files is a LAS file with this value specified it will be used.
- SYSTEM_ID - specifies a System ID value to store in the exported LAS file header. If not specified and one of the input files is a LAS file with this value specified it will be used.
- GEN_SOFTWARE - specifies a Generating Software value to store in the exported LAS file header. If not specified and one of the input files is a LAS file with this value specified it will be used. Otherwise 'Global Mapper' will be used.
- FLIGHT_DATE - specifies the flight date to store in the exported LAS file header. This can be either the day of the current year (value 1 to 366) or a common date format, including month, day, and year. If not specified the current date will be used.
- GUID - specifies the GUID to store in the LAS header. The format should be like GUID="{21EC2020-3AEA-4069-A2DD-08002B30309D}".
- USE_8BIT_CLASSES - specifies that full 8-bit values should be used to store the point classification, allowing values up to 255, even in LAS 1.1/1.2 files that only support classes up to 31 per the standard. Use with care as the files created using USE_8BIT_CLASSES=YES will not comply with the LAS standards if any classes over 31 are present.
- SAVE_HEIGHTS_ABOVE_GROUND - specifies whether the exported LAS/LAZ file should contain raw elevations or a calculated 'height above ground'. Use SAVE_HEIGHTS_ABOVE_GROUND=YES to enable saving heights above ground. Note this requires a Global Mapper Pro license.
- LAS_VERSION - specifies what version of LAS file to write out. This would be 1.1, 1.2, 1.3, or 1.4. If you don't specify a version, the lowest version that will support all of the provided options will be used (typically 1.1 or 1.2).
- VERT_CS_CODE - specifies the vertical coordinate system (i.e. vertical datum) to store in the LAS file to specify what the elevations are referenced to. Use the EPSG code, like 5103 for NAVD88. If you don't specify a value and the source files used all use the same known system, that will be used. Note that no vertical datum conversion is done, this is just to supply metadata.
- VERT_CITATION - specifies the text description to store in the Lidar LAS file for the vertical coordinate system for the elevations. If nothing is supplied the default one (if any) for the supplied VERT_CS_CODE will be used.
- FILE_SOURCE_ID - specifies a File Source ID numeric value to store in the exported LAS file header. If not specified and one of the input files is a LAS file with this value specified it will be used.
- GLOBAL_ENCODING - specifies a Global Encoding numeric value to store in the exported LAS file header. If not specified and one of the input files is a LAS file with this value specified it will be used.
- SYSTEM_ID - specifies a System ID value to store in the exported LAS file header. If not specified and one of the input files is a LAS file with this value specified it will be used.
- GEN_SOFTWARE - specifies a Generating Software value to store in the exported LAS file header. If not specified and one of the input files is a LAS file with this value specified it will be used. Otherwise 'Global Mapper' will be used.
- FLIGHT_DATE - specifies the flight date to store in the exported LAS file header. This can be either the day of the current year (value 1 to 366) or a common date format, including month, day, and year. If not specified the current date will be used.
- GUID - specifies the GUID to store in the LAS header. The format should be like GUID="{21EC2020-3AEA-4069-A2DD-08002B30309D}".
- USE_8BIT_CLASSES - specifies that full 8-bit values should be used to store the point classification, allowing values up to 255, even in LAS 1.1/1.2 files that only support classes up to 31 per the standard. Use with care as the files created using USE_8BIT_CLASSES=YES will not comply with the LAS standards if any classes over 31 are present.
- VOID_ELEV - specifies the string to use for no data values. The default is -9999.0.
- PRECISION - specifies the number of digits of precision to include after the decimal. The default is an automatic determination based on the actual value. If you want to instead use just one digit after the decimal always, use PRECISION=1.
- USE_CENTER_COORDS - specifies that center coordinates rather than corner coordinates should be written to the Arc ASCII Grid header. Use USE_CENTER_COORDS=YES to enable.
- ELEV_LAYER - filename or description of elevation layer(s) to export for Windsim GWS export. By default all compatible and exportable layers are exported. You can include multiple ELEV_LAYER parameters if you have multiple masks to search. Wildcards (* and ?) are supported. Hidden layers are not considered.
- ROUGHNESS_LAYER - filename or description of roughness grid layer(s) to export for Windsim GWS export. By default all compatible and exportable layers are exported. You can include multiple ROUGHNESS_LAYER parameters if you have multiple masks to search. Wildcards (* and ?) are supported. Hidden layers are not considered.
- QUAD_NAME (USGS_DEM only) - specifies the quad name to place in the header of the USGS DEM file.
- VERT_EXAG (VRML only) - specifies the vertical exaggeration to use when creating the VRML file. Larger values result in a rougher terrain being generated while smaller values result in a smoother terrain. A value of 1.0 results in no vertical exaggeration at all (i.e. a nearly true to life representation). If you don't specify a value the currently selected vertical exaggeration value on the Vertical Options tab of the Configuation dialog will be used.
- ALLOW_LOSSY (GLOBAL_MAPPER_GRID only) - specifies whether or not a slight loss in precision is allowable in order to achieve better compression ratios. The default is YES, so turn only use lossless compression you need to specify a value of ALLOW_LOSSY=NO.
- FORMAT (SURFERGRID only) - determines if Surfer Grid export format is ASCII, BINARY_V6, or BINARY_V7. The default is ASCII if no format is specified.
- EXPORT_ECEF (DXF_3DFACE only) - specifies that the export should use ECEF (earth-centered earth-fixed, or geocentric) coordinates.
- CREATE_BINARY (STL only) - specifies that the STL file that is created will be a binary STL file rather than a (much larger) ASCII text STL file.
- Z_UP (STL only) - specifies that the STL file that is created will use a "Z-Up" orientation; that is, Y values in exported coordinates will represent elevations and Z values will represent latitudes.
- NITF_USE_DECIMAL (NITF only) - specifies that is a NITF file is exported with lat/lon coordinates that the ICORDS is set to D for decimal coordinates rather than G for DMS.
-
SRTM_LEVEL (SRTM only)- specifies what SRTM level to use for SRTM HGT export. The values are 1 (1-arc-second resolution) and 3 (3-arc-second resolution). If not provided, a default of level 3 is used.
-
Specify Bounding Box for Operation
See also Specify Bounds for Operation
- GLOBAL_BOUNDS - specifies the combine bounds in units of the current global projection. There should be 4 values in a comma-delimited list following the parameter name. The values should be in order of minimum x, minimum y, maximum x, maximum y.
- GLOBAL_BOUNDS_SIZE - specifies the combine bounds in units of the current global projection. There should be 4 values in a comma-delimited list following the parameter name. The values should be in order of minimum x, minimum y, width in x, width in y.
- LAT_LON_BOUNDS - specifies the combine bounds in latitude/longitude degrees. There should be 4 values in a comma-delimited list following the parameter name. The values should be in order of west-most longitude, southern-most latitude, eastern-most longitude, northern-most latitude.
- LAYER_BOUNDS - specifies that the operation should use the bounds of the loaded layer(s) with the given filename. For example, to export to the bounds of the file "c:\test.tif", you would use LAYER_BOUNDS="c:\test.tif". Keep in mind that the file must be currently loaded.
- LAYER_BOUNDS_EXPAND - specifies that the operation should expand the used LAYER_BOUNDS bounding box by some amount. The amount to expand the bounding rectangle by should be specified in the current global projection. For example, if you have a UTM/meters projection active and want to expand the bounds retrieved from the LAYER_BOUNDS parameter by 100 meters on the left and right, and 50 meters on the top and bottom, you could use LAYER_BOUNDS_EXPAND="100.0,50.0". You can also specify a single value to apply to all 4 sides, or supply 4 separate values in the order left,top,right,bottom.
- SNAP_BOUNDS_TO_MULTIPLE - specifies that the top-left corner of the bounding box for the operation should be snapped to a multiple of the given value. For example, using SNAP_BOUNDS_TO_MULTIPLE=1 will snap the top-left corner to the nearest whole number. The values will always go smaller for X/easting/longitude and larger to Y/northing/latitude so you always get at least what is requested.
- SNAP_BOUNDS_TO_SPACING - specifies that the top-left corner of the bounding box for the operation should be snapped to a multiple of the resolution of the operation. For example, if you are exporting at 5 meter spacing, the top left corner will be snapped to the nearest multiple of 5. Use SNAP_BOUNDS_TO_SPACING=YES to enable or SNAP_BOUNDS_TO_SPACING=NO to disable. If not provided, the global setting for snapping exports to the nearest sample spacing boundary from the Advanced section of the General tab of the Configuration dialog will be used.
- USE_EXACT_BOUNDS - specifies that the exact bounds that were defined in the command should be used. Generally, when the bounds specified in a command are not the same as the data bounds, the command uses the intersection between the two. When USE_EXACT_BOUNDS=YES is specified, the command will use the bounds as specified, instead of the intersection.
-
Cropping to Polygons/Areas
See also Cropping Operations to Polygons/Areas
- POLYGON_CROP_FILE - specifies the full path and filename or loaded layer description of a vector file/loaded layer containing one or more polygon features to which the operation should be cropped. If multiple polygons are found in the specified file the polygon which has the largest intersection with the data to be combined will be used as the crop polygon (see POLYGON_CROP_USE_ALL or POLYGON_CROP_USE_EACH for exceptions).
- POLYGON_CROP_FILE_PROJ - specifies the projection to use for the POLYGON_CROP_FILE. Use if the file doesn't have an associated projection file. See special Projection Specification for instructions.
- POLYGON_CROP_NAME - specifies the name of a polygon shape previously defined using the DEFINE_SHAPE command to which the export should be cropped. The coordinates in the shape need to have been provided in whatever projection the new terrain layer will be in (i.e. the current projection). If you want to crop to any area features that are selected with the Digitizer Tool in the user interface rather than a defined polygon, use POLYGON_CROP_NAME="SELECTED".
- POLYGON_CROP_USE_ALL - specifies that if a POLYGON_CROP_FILE is specified that contains multiple polygons, the operation will be cropped to all polygons in that file rather than just the best-fit polygon.
- POLYGON_CROP_USE_EACH - specifies that if a POLYGON_CROP_FILE is specified that contains multiple polygons, the operation will generate a separate export for each polygons in that file rather than just the best-fit polygon. See the POLYGON_CROP_BBOX_ONLY and POLYGON_CROP_NAME_ATTR options for naming and other options when using this parameter. Use POLYGON_CROP_USE_EACH=YES to enable. This parameter also works with FEATHER_BLEND_EDGES. Use POLYGON_CROP_USE_EACH=YES with FEATHER_BLEND_POLY_FILE or FEATHER_BLEND_POLY to feather the edges of multiple polygons.
- POLYGON_CROP_EXCLUDE - specifies that the crop areas are actually regions to exclude from the export rather than include. If you add POLYGON_CROP_EXCLUDE=YES to the command the results will contain everything outside the crop areas but within the full export bounds.
- POLYGON_CROP_COMBINE_DUPS - specifies that if a POLYGON_CROP_FILE is specified that contains multiple polygons and POLYGON_CROP_USE_EACH is set, whether or not polygons with duplicate values for the attribute used for filenaming will be combined into a single export or split into separate exports. The default is POLYGON_CROP_COMBINE_DUPS=YES.
- POLYGON_CROP_BBOX_ONLY - specifies that if the POLYGON_CROP_USE_EACH parameter is specified that each export should just be cropped to the bounding box of each polygon rather than the actual boundary of the polygon. Use POLYGON_CROP_BBOX_ONLY=YES to enable only cropping to the bounding box.
- POLYGON_CROP_GRID_ONLY - specifies that any crop polygon(s) are used only to determine which tile/grid cells will be exported. For each tile/grid cell that intersects a crop polygon, the full tile/grid cell will be exported. Use POLYGON_CROP_GRID_ONLY=YES to enable.
- POLYGON_CROP_INT_DATA_BOUNDS - control how the bounding box for the export is determined if a crop polygon is specified. If this option is disabled, the export bounds will be the bounds of the crop area(s), even if they extend outside the data bounds, unless you explicitly specified a bounding box in the other parameters (i.e. LAYER_BOUNDS, GLOBAL_BOUNDS, etc.). If the option is enabled, the export bounds will be the intersection of the crop area bounds and the non-cropped bounding box (i.e. full data bounds or specified bounds in other parameter). This parameter is enabled by default, use POLYGON_CROP_INT_DATA_BOUNDS=NO to disable.
- POLYGON_CROP_NAME_ATTR - used to control the filenames generated when cropping to multiple polygons using the POLYGON_CROP_USE_EACH parameter. See special Attribute Name parameter details. This value will be appended to any filename specified in the EXPORT FILENAME parameter. If no value is provided, the exported files will be sequentially numbered.
- POLYGON_CROP_FOLDER_ATTR - used to control the filenames generated when cropping to multiple polygons using the POLYGON_CROP_USE_EACH parameter. See special Attribute Name parameter details.
- POLYGON_CROP_FILENAME_SUFFIX - specifies the text to insert in the output filename just before the file extension when cropping to polygons. For example, if you add POLYGON_CROP_FILENAME_SUFFIX="_out", the original FILENAME was "my_file_.dem" and the value from the polygon was "A1", you would get an output filename of "my_file_A1_out.dem".
- POLYGON_CROP_COMPARE_STR - specifies a compare string to use to filter out the areas in the polygon crop file. See the COMPARE_STR parameter for the EDIT_VECTOR script command for details.
-
Tiling / Gridding Parameters
See also Tiling/Gridding Export into Smaller Chunks
- GRID_TYPE_CELL_SIZE - specifies that the export should be gridded into multiple tiles with each tile having the given size in the export projection. The value should be specified as cell width,cell height. For example, if you are exporting in a metric projection and want to tile the export into cells that are 10,000 meters wide by 5,000 meters tall, you would use GRID_TYPE_CELL_SIZE="10000.0,5000.0".
- GRID_TYPE_PIXEL_SIZE - specifies that the export should be gridded into multiple tiles with each tile having the given size in pixels/samples. The value should be specified as cell pixel width,cell pixel height. For example, if you want to tile the export into cells that are 800 pixels wide by 600 pixels tall, you would use GRID_TYPE_PIXEL_SIZE="800,600".
- GRID_TYPE_PIXEL_SIZE_MAX - specifies that the export should be gridded into multiple tiles with each tile having the given maximum size in pixels/samples. This works by calculating the number of rows and columns needed to hold cells of the given pixel dimensions, then shrinking those pixel dimensions down so that the tiles exactly cover the exported bounds. The value should be specified as cell pixel width,cell pixel height. For example, if you want to tile the export into cells that are at most 800 pixels wide by 600 pixels tall, you would use GRID_TYPE_PIXEL_SIZE_MAX="800,600".
- GRID_TYPE_ROWS_COLS - specifies that the export should be gridded into multiple tiles with a given number of rows and columns of tiles. The value should be specified as number of rows,number of columns. For example, if you want to tile the export into a grid of 8 rows each 4 tiles across, you would use GRID_TYPE_ROWS_COLS="8,4".
- GRID_OVERLAP - specifies how much to overlap tiles when gridding an export into multiple tiles. This is a percentage value from 0 to 100 and only applies when on of the GRID_TYPE_* parameters is used. For example, to make your grid tiles overlap by 5% of the grid tile size, use GRID_OVERLAP="5.0". The default value is 0.0, meaning that the tiles do not overlap.
- GRID_OVERLAP_NUM_PIXELS - indicates whether or not the value specified in GRID_OVERLAP should be interpreted as a number of pixels instead of a percentage. Use GRID_OVERLAP_NUM_PIXELS=YES to specify that the value specified in the GRID_OVERLAP parameter should be interpreted as a number of pixels. Use GRID_OVERLAP_NUM_PIXELS=NO or omit this parameter to specify that the value is a percentage.
- GRID_KEEP_CELL_SIZE - specifies that the size of the grid cells should be maintained over sample spacing. This means that if you specify a grid of 4 rows and 5 columns, each grid cell will be exactly 25% of the total export height and 20% of the total export width. The sample spacing may be slightly smaller than what is specified in order to achieve this. By default, the sample spacing is exactly maintained and each grid cell may be slightly larger than specified to maintain an integer number of exported cells. Use GRID_KEEP_CELL_SIZE=YES to enable.
- GRID_NAMING - specifies how to name tiles when gridding an export into multiple tiles. The value should be SEQUENTIAL for sequential numeric naming starting at 1, SEPARATE for separate prefix appending by row and column, or SEPARATE_COLS_FIRST for separate prefix appending by columns and rows. For the SEPARATE options, use the GRID_NAMING_COLS and GRID_NAMING_ROWS parameters to specify the details of how to name the rows and columns. The value will be appended to FILENAME specified in the EXPORT command. If no GRID_NAMING parameter is supplied, the last selected grid naming options selected in the user interface will be used.
- GRID_NAMING_COLS - specifies how to name the column portion of grid cell names when using the GRID_NAMING=SEPARATE or GRID_NAMING=SEPARATE_COLS_FIRST parameter. The value of this field is a comma-delimited list with the following field values:
- Naming type. Can have the following values:
- NUM - name using numbers in ascending order
- NUM_REVERSE - name using numbers in descending order
- ALPHA - name using letters in ascending order
- ALPHA_REVERSE - name using letters in descending order
- Starting value for numbering or lettering (i.e. '1', or 'A'). If the naming type is numeric you can also specify %left% or %right% as the starting value to use the left or right coordinate of the cell bounding box. For row naming you can use %top% or %bottom%.
- Prefix string to use before the numeric or alphabetic value.
- Step value for numeric naming (default is '1')
You can leave values blank if they don't apply or you want to use the default. As an example, to do numeric naming starting at the number 100, increasing by 10 each time with a prefix of DEM, you would use GRID_NAMING_COLS="NUM,100,DEM,10".
- Naming type. Can have the following values:
- GRID_NAMING_ROWS - specifies how to name the row portion of grid cell names when using the GRID_NAMING=SEPARATE parameter. See the documentation for the GRID_NAMING_COLS parameter above for details on the format.
- GRID_NAMING_PREPEND_ZEROES - specifies whether or not to prepend zeroes to the start of grid column/row names. Use GRID_NAMING_PREPEND_ZEROES=NO to disable the prepending of zeroes.
- GRID_NAMING_SEPARATOR - specifies the separator string to use between pieces of a grid name. The default is an underscore (_).
- GRID_CREATE_FOLDERS - specifies that a separate folder should be generated for each row (or column if GRID_NAMING=SEPARATE_COLS_FIRST is specified) of the export rather than placing every output file in the same folder.
- Tiling to Polygons/Areas - If you would like to tile your export to a series of polygons/areas, use the POLYGON_CROP_FILE and POLYGON_CROP_USE_EACH parameters. Click the link for details.
SAMPLES
Here is an example script showing 2 GWS exports:
GLOBAL_MAPPER_SCRIPT VERSION=1.00
// Do export with elev/roughness layers separately specified
EXPORT_ELEVATION TYPE="GWS" FILENAME="output.gws" \
ELEV_LAYER="*blue_springs*.dem*" ROUGHNESS_LAYER="Roughness *"
// Do export with automatic layer selection
EXPORT_ELEVATION TYPE="GWS" FILENAME="output_auto.gws"