topic Re: Using raster attribute other than 'value' in map algebra in ArcGIS Spatial Analyst Questions

Using raster attribute other than 'value' in map algebra

PeterHarrel — Fri, 05 Nov 2010 14:35:26 GMT

In the old Single Output Map Algebra statement, I could specify which raster attribute I wished the operation to be performed on by listing attribute name in the following format: raster.attribute.

For example, a habitat raster with multiple attributes in addition to 'value' could be multiplied by a mask raster in SOMA by typing:
mask * habitat.type
where 'type' was a different attribute.

This does not seem to be possible in the ArcGIS 10 Raster Calculator. Is there another option?

Re: Using raster attribute other than 'value' in map algebra

EricRice — Fri, 05 Nov 2010 14:46:12 GMT

Hi there,

Dot notation is not currently possible in the new map algebra framework. However, you can make a call to the Lookup tool within the map algebra expression. This tool is designed to make a raster from an attribute of the input raster. Once the you have the Lookup result you can multiply it by your mask.

Regards,
Eric

Re: Using raster attribute other than 'value' in map algebra

MelissaHart — Fri, 05 Nov 2010 18:33:04 GMT

Eric,

It appears that the Lookup tool treats 0 in the value field as NODATA, even when you're calling another attribute.

This is problematic when 0 is a valid entry. Any suggestions?

Thank you!

Re: Using raster attribute other than 'value' in map algebra

SebastianGatscha — Mon, 08 Nov 2010 14:16:55 GMT

I have the same problem. I want to make a SetNull calculation using the "Count" of a raster and not Value.
There must be an easier way of doing that, then using the Lookup function.

No Suggestions???

Re: Using raster attribute other than 'value' in map algebra

EricRice — Wed, 10 Nov 2010 14:58:08 GMT

I have the same problem. I want to make a SetNull calculation using the "Count" of a raster and not Value.
There must be an easier way of doing that, then using the Lookup function.

No Suggestions???

SetNull has a parameter for the Where Clause. You can use the Count field there.

Re: Using raster attribute other than 'value' in map algebra

EricRice — Wed, 10 Nov 2010 15:16:00 GMT

Eric,

It appears that the Lookup tool treats 0 in the value field as NODATA, even when you're calling another attribute.

This is problematic when 0 is a valid entry. Any suggestions?

Thank you!

Melissa,

I can't reproduce that issue. Can you please log an incident with Esri Support so we can get the data and try to replicate?

Eric

Re: Using raster attribute other than 'value' in map algebra

MelissaHart — Fri, 12 Nov 2010 18:11:29 GMT

Melissa,

I can't reproduce that issue. Can you please log an incident with Esri Support so we can get the data and try to replicate?

Eric

We will do that, Eric -- thanks!

Re: Using raster attribute other than 'value' in map algebra

WaylonDaniels — Fri, 17 Jun 2011 13:13:30 GMT

It is now June 2011. Has this problem been resolved?

"Dot notation is not currently possible in the new map algebra framework."

How are we to use raster attribute values in Map Algebra or the SA Math functions in ArcGIS10?

Thanks,
Dwain

Re: Using raster attribute other than 'value' in map algebra

JeffreySwain — Mon, 20 Jun 2011 11:07:28 GMT

The lookup tool will create a raster that has the value that you are looking for. This concept of dot notation does not exist in python processing used in the Python Window, so you will have to create a new raster with the value desired and the processing can be done.

There is an enhancement request that exists to return that functionality. Please log a support incident to add to that enhancement request.

Re: Using raster attribute other than 'value' in map algebra

ChrisSnyder — Mon, 20 Jun 2011 15:15:09 GMT

#START SHORT RANT

Why is it that ESRI chooses to not port certain existing functionality from earlier version of their software to newer versions?

Spatial Analyst/Grid Examples:
--------------------------------------
1. dot notation
2. docell
3. ability to run concurrent SA processes

Why not, as a first priority, port all the existing functionality, concentrate on making it better/faster, and then come up with new additional tools/functionality as a second priority???

From a user's point of view, it is very frustrating having to submit an "enhancement request" for functionality that had existed for decades, but then mysteriously disappears... Yarr!

#END SHORT RANT

Re: Using raster attribute other than 'value' in map algebra

Diego_FabianPajarito_Grajales — Sun, 06 May 2012 02:56:41 GMT

#START SHORT RANT

Why is it that ESRI chooses to not port certain existing functionality from earlier version of their software to newer versions?

Spatial Analyst/Grid Examples:
--------------------------------------
1. dot notation
2. docell
3. ability to run concurrent SA processes

Why not, as a first priority, port all the existing functionality, concentrate on making it better/faster, and then come up with new additional tools/functionality as a second priority???

From a user's point of view, it is very frustrating having to submit an "enhancement request" for functionality that had existed for decades, but then mysteriously disappears... Yarr!

#END SHORT RANT

This is all but new, Esri always do the same, so do not expect to have all your 9.x or 10.x scripts ready to work with the future 11.x or 12.x arcGis Versions.

It had happened at every version update with every product just try to imagine people working on the JAVA Framework in ArcGIS Server 9.2, I was one of those it was a mess.

I'm just going to look for another option for sure I will share with you my solution.

Diego P

Re: Using raster attribute other than 'value' in map algebra

Diego_FabianPajarito_Grajales — Sun, 06 May 2012 04:10:11 GMT

#START SHORT RANT

Why is it that ESRI chooses to not port certain existing functionality from earlier version of their software to newer versions?

Spatial Analyst/Grid Examples:
--------------------------------------
1. dot notation
2. docell
3. ability to run concurrent SA processes

Why not, as a first priority, port all the existing functionality, concentrate on making it better/faster, and then come up with new additional tools/functionality as a second priority???

From a user's point of view, it is very frustrating having to submit an "enhancement request" for functionality that had existed for decades, but then mysteriously disappears... Yarr!

#END SHORT RANT

I cannot understand why the Lookup function does not work in arcpy and give me some 01006 and 010327 errors.
I know this is not a real solution but I just had 6 raster files, so I decided to use the Lookup from ArcToolBox and get the new raster manually, It did not work.

If some of you get the point with that function let me know

Diego Pajarito

Re: Using raster attribute other than 'value' in map algebra

JeffreySwain — Mon, 07 May 2012 10:26:44 GMT

The Lookup tool should work in model builder. I think that you are getting 010006 errors or insufficient arguments, which is prompting the unable to set the spatial extent error, 010327. Both point to the issue that the model does not appear to be recognizing your raster. I would be sure that the syntax is correct or since it is a model, the process that is creating the raster you are trying to use in the Lookup tool has been created, before the next action takes place.

Re: Using raster attribute other than 'value' in map algebra

boonejardot — Mon, 07 May 2012 21:14:24 GMT

Im currently trying to figure out the exact same thing. Let you know If I figure it out.

Re: Using raster attribute other than 'value' in map algebra

boonejardot — Tue, 08 May 2012 01:28:33 GMT

Yes it works with Lookup. Used the function Created a new raster that had the value set to the attribute that I prefered. Works... At first it didnt, but I had to change the folder/database it went into for some reason, then it worked. Good luck.

Re: Using raster attribute other than 'value' in map algebra

curtvprice — Fri, 18 May 2012 13:42:07 GMT

I had to change the folder/database it went into for some reason, then it worked.

Did the output workspace path that didn't work include spaces or unusual characters?