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; } } }

Minus - A tale of 2 rasters - looking for troubleshooting ideas

AwesomeEvan

I'm getting a strange clipped output and I cant figure out why.

I have a DSM and DTM from the same lidar

I'm doing a very simple "Minus" GP tool... and the output is not as expected

The only portion that comes back is the top left?!

Everything about the 2 input rasters is similar: projection, cell size, etc etc...

The results are perfect, i just cant get it to process the whole area. I'm using a very powerful computer.

This is ~20 sq km in total

Furthermore, I used just the DSM and a constant of 1, and the same area gets processed?

Any ideas why this may be happening?

Cheers

gp output

Find more posts tagged with

Accepted answers

AwesomeEvan

Thanks all for the suggestions...

I tried all of them (except "snap raster" environment setting... not sure what that is) but I got the same results, only half being processed...

The suggestions did inspire me to try an alt route to my destination... and I did get there...

I used the Moasic to New Raster, to create 2 singular tifs, then used the minus on them and the results came out as expected.

thanks all

All comments

AwesomeEvan

Thanks all for the suggestions...

I tried all of them (except "snap raster" environment setting... not sure what that is) but I got the same results, only half being processed...

The suggestions did inspire me to try an alt route to my destination... and I did get there...

I used the Moasic to New Raster, to create 2 singular tifs, then used the minus on them and the results came out as expected.

thanks all

XanderBakker

It is strange that Minus or any other tool would only process a part of the data. To rule out any erroneous environment setting I would:

Set the workspace to a valid fgdb (just as Chris Donohue, GISP suggested)
Set the output coordinate system to the input SDE raster
Set the extent to the input SDE raster
Set the snap raster to the input SDE raster
Set the cell size to the input SDE raster

You could try to run the calculation it in the Raster Calculator to see if the changes anything.

DanPatterson_Retired

Minus... is ringing a bell, but it supports all the Environment parameters, assuming that you set them within the Environments tab on the bottom right of the tool dialog (not just the general ones... I trust those less to behave nicely)

On a lark to rule out Minus issues, try Plus... and if that goes well, Times one of the rasters by -1 then plus that result with the other

ChrisDonohue__GISP

I'd use a workspace besides the Default C:\Usename\Documents\ArcGIS\Default.gdb one. Instead, make your own File Geodatabase and store it on a short file path. Don't ask me why, but for whatever reason using the Default geodatabase seems to lead to issues at times when working with raster data.

As for places where Minus may go awry, let me tag one of the raster experts:

Dan_Patterson

Chris Donohue, GISP

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.