Timeline for Using Spatial Analyst Sample tool
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2014 at 23:52 | comment | added | Jeffrey Evans | A 10 character field name limitation for shapefiles. Legacy of the dbf format. ESRI file geodatabase field name lengths can be 64 characters, see: resources.arcgis.com/en/help/main/10.2/index.html#//… | |
| Jun 16, 2014 at 23:15 | comment | added | Oliver Burdekin | 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. | |
| Jun 16, 2014 at 23:08 | comment | added | Michael Stimson | 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. | |
| Jun 16, 2014 at 23:04 | comment | added | Jeffrey Evans | 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. | |
| Jun 16, 2014 at 23:01 | comment | added | Michael Stimson | 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? | |
| Jun 16, 2014 at 22:57 | history | answered | Jeffrey Evans | CC BY-SA 3.0 |