nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Additional digits added by 'ascii to raster' tool

MarcVis

Hi,

I have a DEM in ascii format which I imported into ArcMap using the 'ascii to raster' tool. All values in the ascii file have 3 digits after the decimal point. However, after importing, the raster values do have many more digits (e.g. 1451.623 became 1451.623047...). Does anyone know where the additional digits come from, aka what is happening behind the scenes of the ascii to raster tool?

Thanks!

Marc

Find more posts tagged with

Accepted answers

All comments

DanPatterson_Retired

ASCII to Raster—Conversion toolbox | ArcGIS Desktop or

DEM to Raster—Conversion toolbox | ArcGIS Desktop

Any extra decimals places were already UNLESS you are confirming that 1451.623 was actually showing in the text file Otherwise it may be floating point representation but the example you give doesn't show this

for example going from float16 to float64 you can see that the decimal representation is different, but none are gained.

z <SPAN class="operator token">=</SPAN> np<SPAN class="punctuation token">.</SPAN>array<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="number token">1451.623</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">,</SPAN> dtype<SPAN class="operator token">=</SPAN>np<SPAN class="punctuation token">.</SPAN>float16<SPAN class="punctuation token">)</SPAN>
<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>z<SPAN class="punctuation token">[</SPAN><SPAN class="number token">0</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="number token">1452.0</SPAN>

z <SPAN class="operator token">=</SPAN> np<SPAN class="punctuation token">.</SPAN>array<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="number token">1451.623</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">,</SPAN> dtype<SPAN class="operator token">=</SPAN>np<SPAN class="punctuation token">.</SPAN>float32<SPAN class="punctuation token">)</SPAN>
<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>z<SPAN class="punctuation token">[</SPAN><SPAN class="number token">0</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="number token">1451.623</SPAN>

z <SPAN class="operator token">=</SPAN> np<SPAN class="punctuation token">.</SPAN>array<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="number token">1451.623</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">,</SPAN> dtype<SPAN class="operator token">=</SPAN>np<SPAN class="punctuation token">.</SPAN>float64<SPAN class="punctuation token">)</SPAN>
<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN>z<SPAN class="punctuation token">[</SPAN><SPAN class="number token">0</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="number token">1451.623</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

So the question might be, what is the final format of your 'raster'…? an esri grid? a geodatabase raster? a *.tif? (recommended). Do the numbers change with the output format?

MarcVis

Thank you for your reply!

Yes, the value 1451.623 is showing in the text file. The output format doesn't affect the results of the import, i.e. esri grid, tif, geodatabase all result in the same output.

I attached the ascii file, so you might be able to reproduce my observations. Also attached are two screen shots, one from the Identify form (showing the pixel value 1451.623047) and one from the Layer Properties (showing 10 decimal places for the minimum and maximum of the raster).

Thanks again!

Marc

I converted your data to a numpy array, it came in as a float32 (32bit floating point values).

I set the array type to float64 and a slice of it looked like this

a[100:300, 100:300]
Out[44]:
array([[1489.567, 1490.179, 1490.441, 1490.702, 1491.003, 1491.728, 1492.366,
        1493.299, 1493.946, 1494.314, ..., 1639.082, 1639.969, 1640.586,
        1641.29 , 1642.091, 1642.714, 1643.287, 1643.971, 1644.556, 1645.272],
       [1490.182, 1490.748, 1491.255, 1491.775, 1492.324, 1492.644, 1493.596,

so I suspect it is just a floating point representation issue. I don't know what they are using behind the scenes.

SteveLynch

Use IEEE-754 Floating Point Converter and you'll soon see that 1451.623 is actually 1451.623046875

The ASCIIToRaster tool produces 32 bit rasters.

DanPatterson_Retired

Steve are the raster tools 32 bit still?

SteveLynch

Dan

Yes, however, some of the conversion tools like Point, Polyline and Polygon ToRaster can create a 64 bit (double) raster. This has been the case for many years, way back in 9.2 or 9.3 I believe. The tool will decide if the output should be 32 or 64 bit. CopyRaster, on the other hand, has a parameter

Esri grid format only supports 32 bit, so you'll rather have to output to fgdb, tif or img.

-Steve

DanPatterson_Retired

I generated the tiff from your ascii file using numpy as....

<SPAN class="keyword token">from</SPAN> arcpy <SPAN class="keyword token">import</SPAN> NumPyArrayToRaster
<SPAN class="keyword token">from</SPAN> arcpy <SPAN class="keyword token">import</SPAN> Point

path <SPAN class="operator token">=</SPAN> r<SPAN class="string token">"C:\Temp\dem.txt"</SPAN>
ncols&nbsp;&nbsp;&nbsp; <SPAN class="operator token">=</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="number token">317</SPAN>
nrows&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="operator token">=</SPAN>&nbsp;&nbsp;&nbsp; <SPAN class="number token">204</SPAN>
xllcorner <SPAN class="operator token">=</SPAN>&nbsp;&nbsp;&nbsp; <SPAN class="number token">2697732</SPAN>
yllcorner <SPAN class="operator token">=</SPAN>&nbsp;&nbsp;&nbsp; <SPAN class="number token">1210264</SPAN>
cellsize&nbsp; <SPAN class="operator token">=</SPAN>&nbsp;&nbsp;&nbsp; <SPAN class="number token">2</SPAN>
NODATA_value <SPAN class="operator token">=</SPAN> <SPAN class="operator token">-</SPAN><SPAN class="number token">9999</SPAN>

a <SPAN class="operator token">=</SPAN> np<SPAN class="punctuation token">.</SPAN>genfromtxt<SPAN class="punctuation token">(</SPAN>path<SPAN class="punctuation token">,</SPAN> np<SPAN class="punctuation token">.</SPAN>float<SPAN class="punctuation token">,</SPAN> delimiter<SPAN class="operator token">=</SPAN><SPAN class="string token">' '</SPAN><SPAN class="punctuation token">,</SPAN> skip_header<SPAN class="operator token">=</SPAN><SPAN class="number token">6</SPAN><SPAN class="punctuation token">)</SPAN>
a0 <SPAN class="operator token">=</SPAN> np<SPAN class="punctuation token">.</SPAN>where<SPAN class="punctuation token">(</SPAN>a<SPAN class="operator token">==</SPAN><SPAN class="operator token">-</SPAN><SPAN class="number token">9999</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">,</SPAN> np<SPAN class="punctuation token">.</SPAN>nan<SPAN class="punctuation token">,</SPAN> a<SPAN class="punctuation token">)</SPAN>

LL <SPAN class="operator token">=</SPAN> Point<SPAN class="punctuation token">(</SPAN>xllcorner<SPAN class="punctuation token">,</SPAN> yllcorner<SPAN class="punctuation token">)</SPAN>
out <SPAN class="operator token">=</SPAN> NumPyArrayToRaster<SPAN class="punctuation token">(</SPAN>a0<SPAN class="punctuation token">,</SPAN> LL<SPAN class="punctuation token">,</SPAN> <SPAN class="number token">2.0</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="number token">2.0</SPAN><SPAN class="punctuation token">,</SPAN> np<SPAN class="punctuation token">.</SPAN>nan<SPAN class="punctuation token">)</SPAN>
out<SPAN class="punctuation token">.</SPAN>save<SPAN class="punctuation token">(</SPAN>r<SPAN class="string token">"C:\Temp\dem_np.tif"</SPAN><SPAN class="punctuation token">)</SPAN>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Statistics yield

So you can get 64 bit if you need it.

dem_np.zip

DanPatterson_Retired

Steve as you were responding, I used NumPyArrayToRaster… which is my usual route, and things are good

Thanks

SteveLynch

you could also skip using ASCIIToRaster and rather use the CopyRaster tool.

Make sure that the ASCII file has a .asc extension and pick PixelType=64 bit

DanPatterson_Retired

True... I just find it easier using the array approach since I can do any last minute resampling/aggregation or reclassification (the empty line 13 ) before saving out.

MarcVis

Dan and Steve, thanks a lot for your replies, that was very helpful! 😄

Best,

Marc

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.