Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a bunch of rasters and a point file. I need the information from ll the raster files to be added to my points.

My usual workflow is to use the Spatial Analyst sample tool. It works fine and I can do a spatial join to get the information added to the point file. However, furstratingly the sample tool never seems to offer useful field headings and with a lot of rasters it can become confusing as to which value relates to which raster. Does anyone know of a script or workaround that can produce a table with field headings?

share|improve this question
up vote 2 down vote accepted

If you are doing this in a model or script you can add a field, calculate the field with the grid_code (or whatever field it creates) and then delete the grid_code field. That way everything goes into a properly named field and the default name field is gone!

share|improve this answer

The ArcToolbox > Spatial Analyst Tools > Extraction > Extract Multi Values to Points tool assigns multiple rasters values to a point feature class and assigns the raster name as the column name(s).

share|improve this answer
That's a neater solution to this problem. I like it. No flexibility though, if you've got multiple rasters called the same thing what happens there? – Michael Miles-Stimson Jun 16 '14 at 23:01
How would you otherwise account for an identical raster naming convention? I guess you could use a counter in a script to add an increment value to a filename but this seems like a poor way to manage data and an outlier occurrence. I have never tried it but I imagine that ESRI added an error handling routine that creates a new name if it already exist in the point attribute table. – Jeffrey Evans Jun 16 '14 at 23:04
I reckon give the rasters sensible names first. An ounce of preparation... Grid rasters by file limitations have short names and can be identical but of different times/scenes which would cause this situation to occur. Shapefiles have a limit on attribute name lengths. With this in mind give the rasters sensible names first and then there's no problem to fix is there. – Michael Miles-Stimson Jun 16 '14 at 23:08
It's worth remembering that you're limited to 13 (or 15, I forget) characters for field headings if your table is going into a geodatabase. – Oliver Burdekin Jun 16 '14 at 23:15
A 10 character field name limitation for shapefiles. Legacy of the dbf format. ESRI file geodatabase field name lengths can be 64 characters, see:… – Jeffrey Evans Jun 16 '14 at 23:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.