topic Re: Extract Multi Values to Points NOT WORKING! in ArcGIS Spatial Analyst Questions

Extract Multi Values to Points NOT WORKING!

KevinWiley — Mon, 30 Apr 2012 00:16:31 GMT

I am trying to use this tool, but it isn't working correctly. I'm trying to extract values from multiple rasters to a set of points. I run the tool, and it always creates the new fields in the point attribute table; however, it never populates those fields with all the values. Sometimes, it's no values at all. Sometimes, it's one out of five raster fields. Sometimes, it's three out of seven. But so far, I've never had all the new fields properly populated with values. Also, if I use the Extract Values to Points tool, and go one raster at a time, that tool works fine. But the multi tool would be far more convenient, if only I could get it to work. Is this tool just buggy, or do I need to do something differently? Please help!

Re: Extract Multi Values to Points NOT WORKING!

GayathriAlallasundaram — Mon, 30 Apr 2012 13:42:32 GMT

Hi,

There was bug NIM062706(Getting incorrect results when running Extract Multi Values to Points in ArcGIS.) associated to Extract Multi Values to Points, however, it has been fixed in version 10SP4. Please click the link below and install install 10 SP4 if you have not done it already,

http://resources.arcgis.com/content/patches-and-service-packs?fa=viewPatch&PID=66&MetaID=1840

Thank You,
Gayathri A.

Re: Extract Multi Values to Points NOT WORKING!

TimHoward1 — Fri, 04 May 2012 12:55:42 GMT

I have upgraded to SP4 and, unfortunately, this tool is still not working for me either. Behavior varies from: 1. attributing columns in the points layer with zero, very large, or very small numbers -- all the same for all rows within each column, 2: creating the columns but then leaving all values null, 3: crashing arcmap outright.

Conceptually, this tool is an excellent addition to the toolbox and it really would be great if we could depend on it to do the job correctly.
Tim

Re: Extract Multi Values to Points NOT WORKING!

PavanYadav — Mon, 07 May 2012 20:53:21 GMT

Greetings,

I would like to investigate this issue and am wondering if you could help me. What I would like to get from you is your sample data. If you are able to do so, I will send you instructions to upload your data on our FTP site. Here is my email, please send me an email so that I can send you ftp instructions.

Thank you for your help in advance.

Regards,
Pavan

Re: Extract Multi Values to Points NOT WORKING!

zheminxuan — Fri, 13 Jul 2012 19:59:02 GMT

Hi,

I'm also trying to extract values from multiple rasters to a set of points. After running the tool, attributing columns in the points layer are all shown with zero
What can I do for this issue? Please help!

Re: Extract Multi Values to Points NOT WORKING!

JessieAbbate — Tue, 20 Nov 2012 15:13:42 GMT

did anyone ever get data to you? i'm having the same issue!
-jessie

Greetings,

I would like to investigate this issue and am wondering if you could help me. What I would like to get from you is your sample data. If you are able to do so, I will send you instructions to upload your data on our FTP site. Here is my   email, please send me an email so that I can send you ftp instructions.

Thank you for your help in advance.

Regards,
Pavan

Re: Extract Multi Values to Points NOT WORKING!

PavanYadav — Wed, 21 Nov 2012 15:43:11 GMT

did anyone ever get data to you? i'm having the same issue!
-jessie

Hi Jessie,
We received test data only from one user, and we were able to reproduce the issue. It's a data specific issue that was reproducible at v10 Service Pack 5 and v10.1. Bug ID for the issue is NIM082931. This bug has been fixed at 10.1 SP1. I was wondering if you could try on 10.1 SP1 and see what happens. If you still get an unexpected result please contact support, here you can find contact information. If you are not current on maintenance, please send me an email at pyadav AT esri DOT com.

ArcGIS 10.1 Service Pack 1 for (Desktop, Engine, Server) download link.

Regards,
Pavan

Re: Extract Multi Values to Points NOT WORKING!

steveSuperczynski — Tue, 22 Jan 2013 19:54:10 GMT

What about in ArcGIS 10.0? I am running the latest service pack (5) and this tool is giving me trouble too.

-Steve

Re: Extract Multi Values to Points NOT WORKING!

GeoRevelation — Sat, 09 Feb 2013 19:02:11 GMT

I am using 10.1 SP1 and I am getting unexpected results. I am using a simple RGB .img where the values are only 0 or 255 but never 0,0,0 or 255,255,255 (like yellow, cyan, etc) but the tool only returns values that are 0,0,0 or 255,255,255.

It would be great if this worked.

Thanks

Re: Extract Multi Values to Points NOT WORKING!

curtvprice — Wed, 13 Feb 2013 19:57:57 GMT

I am using 10.1 SP1 and I am getting unexpected results. I am using a simple RGB .img where the values are only 0 or 255 but never 0,0,0 or 255,255,255 (like yellow, cyan, etc) but the tool only returns values that are 0,0,0 or 255,255,255.

It would be great if this worked.

Thanks

Whenever a raster tool does not work I try to see if it works with the Esri grid format. Convert your .img to a grid stack (copy raster with the output set an output raster name with no extension, starting with a letter, less than 11 chars), and see if EMVTP will work on that.

Please open an incident with Esri if you can -- we need this tool to work more consistently!

Re: Extract Multi Values to Points NOT WORKING!

StephenBan — Sun, 17 Mar 2013 20:55:17 GMT

I just came across this bug in 10.0 SP5; as described above, it seems they did fix it in 10.1 SP1.

The order in which I added raster layers was important; if I added a layer that had NODATA values, all subsequent layers would also show NODATA values for those locations. If the same layers were added before the NODATA layers, the values would be fine.

Running the multivalue tool one layer at a time also seems to work (of course, this defeats the purpose of the multi-value tool).

Re: Extract Multi Values to Points NOT WORKING!

ChrisSimpson — Thu, 25 Jul 2013 11:42:15 GMT

Try switching off Background Processing in Geoprocessing Options.

Re: Extract Multi Values to Points NOT WORKING!

ScottLamon1 — Mon, 03 Mar 2014 16:37:07 GMT

I just came across this bug in 10.0 SP5; as described above, it seems they did fix it in 10.1 SP1.

The order in which I added raster layers was important; if I added a layer that had NODATA values, all subsequent layers would also show NODATA values for those locations. If the same layers were added before the NODATA layers, the values would be fine.

Running the multivalue tool one layer at a time also seems to work (of course, this defeats the purpose of the multi-value tool).

I don't think they fixed this in 10.1. I have a user who is having the tool crash on him if he adds the rasters in the wrong order.

Re: Extract Multi Values to Points NOT WORKING!

ThomasStanley — Sun, 12 Dec 2021 03:55:40 GMT

I find that ArcMap 10.2 crashes to desktop if I load this tool up with many layers. However, it functions quite reliably one layer at a time. The python console makes this very easy to use:

layers =

band-select layers, drag and drop into console, hit enter,

for layer in layers:
  arcpy.sa.ExtractMultiValuesToPoints('RandomPoints', layer, 'NONE')

hit enter

Has been much easier and more foolproof than other methods.

Re: Extract Multi Values to Points NOT WORKING!

ChrisParker — Tue, 28 Mar 2017 12:15:12 GMT

Is anyone else still having problems with this? I'm running ArcGIS Version 10.4.0.5524 (Advanced License) and over the past few months I have been experiencing issues with the ‘Extract multi value to points’ tool that I did not have before. The problems are:

The first time I run the tool it assigns incorrect values for the newly created field (but if I re-run the tool it does assign the correct values from the raster to the newly created field)
Whenever I run the tool the ‘OBJECTID’ fields for each point change from their original values – so the points are re-ordered.

Re: Extract Multi Values to Points NOT WORKING!

curtvprice — Thu, 20 Apr 2017 04:46:24 GMT

I don't know about the first issue. But it is generally true that OBJECTID is internally maintained by the database (ie it can be changed by the database software where the data is stored) and is not persistent. You should use some other identifer besides OBJECTID to keep track of things if you need it to remain unchanged through edits and modifications to the dataset (including adding fields).

What format is the point dataset in? You may want to try a different format and see if the tool behaves better.

Re: Extract Multi Values to Points NOT WORKING!

ChrisParker — Thu, 20 Apr 2017 10:24:58 GMT

Hi Curtis,

Thanks - I've been directed to some text in the tool description that does warn that this can happen:

Whilst I can work round the issue it seems strange to me that:

1. This issue has been introduced relatively recently (I have been using this tool without this issue for several years)

2. The ObjectID can be modified. I thought the whole point of an object identifier was that it is a unique and constant reference to an object? I can't see any user benefits of allowing the ObjectID to be modified but would like to think that it is more than just lazy coding?

I've tried working from both shapefiles and feature classes within a geodatabase and the issue occurs regardless. Or did you mean something else when referring to different formats?

Cheers,

Chris

Re: Extract Multi Values to Points NOT WORKING!

curtvprice — Thu, 20 Apr 2017 21:42:15 GMT

I thought the whole point of an object identifier was that it is a unique and constant reference to an object? I can't see any user benefits of allowing the ObjectID to be modified but would like to think that it is more than just lazy coding?

Unique, yes. Persistent, definitely not. This has to do with how data are stored in the RDBMS world - objectIDs are used internally by the software for its own purposes, for example in some RDBMS's when an object is edited, instead of deleting it, a new feature is created and added to the end of the table, and the existing object is flagged for deletion ( this is what "Compact geodatabase" is all about.) Supporting this means that OID should not be messed with, and is only useful for relates right after an operation (for example an Intersect operation). Of the inputs of the intersect are edited, OID's may change and the joins back to the inputs may no longer work. How persistent the OIDs are depends on the data format (RDBMS [various formats], coverage, shapefile, gdb) and which operations you do.

Clearly they mess with this tool in some way that alters the input, I'm guessiong for robustness and performance reasons. I wonder why this basic tool has been so buggy for so long? There are probably issues 'under the hood' we don't know about.

Extract Multi-Values To Points and Sample are very similar tools and often I use one when the other won't work on a given dataset (on a given day!!!) Sample is a Spatial Analyst tool and honors the raster environment settings well, so it is sometimes more useful than the other.

Re: Extract Multi Values to Points NOT WORKING!

maheshrao — Tue, 18 Jul 2017 15:19:36 GMT

Extract Multi-Values to points is a very useful tool, and I use it often.

Make sure the raster datasets and the feature shp file conform to the same coordinate sys. The points might display correctly on the rasters in the DataFrame due to the on-the-fly projection, but it is important that the coordinate sys is consistent across the stack and match to that of the point feature layer.

Re: Extract Multi Values to Points NOT WORKING!

AlfredWagtendonk — Thu, 26 Oct 2017 15:33:02 GMT

I remember having issues with the use of this tool a few years ago. Using it again now caused me Python to crash each time. Almost giving up (thinking this tool was still not improved by ESRI) I read the comment by Mahesh Rao and indeed I had forgotten to check if my layers had the same coordinate systems. After reprojecting the feature layer to the projection of the raster layer, the issue was solved. Thanks! So, make sure to check the coordinate systems of your input layers...