1

I downloaded 2 1/3 arcsecond DEMs from the national map as .img files. First I ran the Mosaic to New Raster tool in Arcmap. The values of the first DEM are 49.0551 to 1111.13. The values for the second DEM are 274.089 to 3505.05. The output is -78.4316 to 3505.05. I have tried changing some of the options as follows.

Pixel type: 32bit float, 32 bit unsigned (this one gave a low of 0)

Mosaic Operator: All the possible options

So then I tried it in ERDAS with mosaic express. I got the same result.

I looked at the histograms, not just the stretch classification to confirm the values.

I used the pseudocolor option in ERDAS to locatate the negatave pixels of which there are many thousands. They are not located at the seam line, rather it is a big valley that is the lowest area of the DEM.


I downloaded the DEM again, but this time as arcgrid. Now it displays the min of -78 instead of 49 and the max is now 1875 instead of 1111. Not sure why the IMG gave different values. I went to google earth to check if this is an error. Turns out that at the very edge of the DEM it does drop below sea level, so it is correct. I still do not understand why the IMG file did not display the -78 and 1875 in the first place. I would not have been worried if the min and max of the mosaic output was the same as the inputs.

closed as off-topic by PolyGeo Oct 15 '16 at 1:27

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This problem cannot or can no longer be reproduced. Changes to the system or to the asker's circumstances may have rendered the question obsolete, or the question does not include a procedure to enable potential answerers to reproduce the same symptoms. Such questions are off-topic as they are unlikely to help future readers, but editing them to include more details can lead to re-opening." – PolyGeo
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    Overkill. Set extent to mosaic. Use raster calculator to compute A. The same for B. Raster calculator Con(isnull(A), B,A) – FelixIP Oct 14 '16 at 5:09
  • Sorry, I do not understand. – GeographyNerd Oct 14 '16 at 5:18
  • 1
    FYI - If you want people to see your responses you need to ping them with @username. – jbalk Oct 14 '16 at 7:02
  • 2
    Again the question, are there any nodata pixels in the low valley area in one (or both) of the input DEM? I suppose, that the nodata values are ignored in the statistics of the Input DEM, but are not recognized as nodata values by the resampling process. – Saleika Oct 14 '16 at 7:43
  • 2
    @GeographyNerd Please add all additional information as an edit to your question, not in comments – Midavalo Oct 14 '16 at 7:52