SMS:WAM Map to Raster Utility: Difference between revisions

From XMS Wiki
Jump to navigationJump to search
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
The ''Map to Raster'' utility has been updated to allow for conversions between big endian to little endian. Most machines are little endian and therefore users should just use the utility like they did before. However, if the InOut/Map files were created from a machine that is big endian the user should convert to little endian. To convert: copy the InOut/Map files to a little endian machine. Then from the command line run map_to_rast.exe passing "big_endian" as an argument. It will look something like this: c:\>map_to_rast.exe big_endian. Other command line arguments can also be used outlined below:  
The ''Map to Raster'' utility has been updated to allow for conversions between big endian to little endian. Most machines are little endian, therefore use the utility as before. However, if the InOut/Map files were created from a machine that is big endianconvert to little endian. To convert: copy the InOut/Map files to a little endian machine. Then from the command line run map_to_rast.exe passing "big_endian" as an argument. It will look something like this: c:\>map_to_rast.exe big_endian. Other command line arguments can also be used outlined below:  
*native  
{|class="wikitable"
 
|-
Specifies that unformatted data should not be converted.
|native  
 
|Specifies that unformatted data should not be converted.
*big_endian  
|-
 
|big_endian  
Specifies that the format will be big endian for integer data and big endian IEEE floating-point for real and complex data.
|Specifies that the format will be big endian for integer data and big endian IEEE floating-point for real and complex data.
 
|-
*cray  
|cray  
 
| Specifies that the format will be big endian for integer data and CRAY* floating-point for real and complex data.
Specifies that the format will be big endian for integer data and CRAY* floating-point for real and complex data.
|-
 
|fdx (Linux, Mac OS X)  
*fdx (Linux, Mac OS X)  
|Specifies that the format will be little endian for integer data, and VAX processor floating-point format F_floating, D_floating, and X_floating for real and complex data.
 
|-
Specifies that the format will be little endian for integer data, and VAX processor floating-point format F_floating, D_floating, and X_floating for real and complex data.
|fgx (Linux, Mac OS X)  
 
| Specifies that the format will be little endian for integer data, and VAX processor floating-point format F_floating, G_floating, and X_floating for real and complex data.
*fgx (Linux, Mac OS X)  
|-
 
|ibm  
Specifies that the format will be little endian for integer data, and VAX processor floating-point format F_floating, G_floating, and X_floating for real and complex data.
| Specifies that the format will be big endian for integer data and IBM* System\370 floating-point format for real and complex data.
 
|-
*ibm  
|little_endian  
 
| Specifies that the format will be little endian for integer data and little endian IEEE floating-point for real and complex data.
Specifies that the format will be big endian for integer data and IBM* System\370 floating-point format for real and complex data.
|-
 
|vaxd  
*little_endian  
| Specifies that the format will be little endian for integer data, and VAX* processor floating-point format F_floating, D_floating, and H_floating for real and complex data.
 
|-
Specifies that the format will be little endian for integer data and little endian IEEE floating-point for real and complex data.
|vaxg  
 
| Specifies that the format will be little endian for integer data, and VAX processor floating-point format F_floating, G_floating, and H_floating for real and complex data.
*vaxd  
|}
 
Specifies that the format will be little endian for integer data, and VAX* processor floating-point format F_floating, D_floating, and H_floating for real and complex data.
 
*vaxg  
 
Specifies that the format will be little endian for integer data, and VAX processor floating-point format F_floating, G_floating, and H_floating for real and complex data.


==Related Topics==
==Related Topics==

Latest revision as of 16:59, 17 November 2016

The Map to Raster utility has been updated to allow for conversions between big endian to little endian. Most machines are little endian, therefore use the utility as before. However, if the InOut/Map files were created from a machine that is big endian, convert to little endian. To convert: copy the InOut/Map files to a little endian machine. Then from the command line run map_to_rast.exe passing "big_endian" as an argument. It will look something like this: c:\>map_to_rast.exe big_endian. Other command line arguments can also be used outlined below:

native Specifies that unformatted data should not be converted.
big_endian Specifies that the format will be big endian for integer data and big endian IEEE floating-point for real and complex data.
cray Specifies that the format will be big endian for integer data and CRAY* floating-point for real and complex data.
fdx (Linux, Mac OS X) Specifies that the format will be little endian for integer data, and VAX processor floating-point format F_floating, D_floating, and X_floating for real and complex data.
fgx (Linux, Mac OS X) Specifies that the format will be little endian for integer data, and VAX processor floating-point format F_floating, G_floating, and X_floating for real and complex data.
ibm Specifies that the format will be big endian for integer data and IBM* System\370 floating-point format for real and complex data.
little_endian Specifies that the format will be little endian for integer data and little endian IEEE floating-point for real and complex data.
vaxd Specifies that the format will be little endian for integer data, and VAX* processor floating-point format F_floating, D_floating, and H_floating for real and complex data.
vaxg Specifies that the format will be little endian for integer data, and VAX processor floating-point format F_floating, G_floating, and H_floating for real and complex data.

Related Topics