POST
|
Thanks for the suggestions. It turned out that the cause was something else, which appears to be a bug in the tool, and so is worth documenting here for future users. The input zone layer to the Zonal Histogram was a layer created from a selection from a source layer. That is, Layer2 (the input defining the zones for the Zonal Histogram tool) was created in a map by selecting 250 features from Layer1 (a complete set of US ZIP code polygons), then doing right click/Selection/Create layer from selected features. However, even though Layer2 has only 250 features that display on the map or show up in its attribute table, the Zonal Histogram tool went a grabbed all the layers from Layer1 to use as the zones! So instead of the expected 251 fields in the histogram table, there were about 30,000, and that is why no DBF or MDB table could be created. The upshot: when using a map layer defined as a subset of a source layer, Zonal Histogram will use the source layer instead to define the zones. p.s. my ultimate resolution to extract the data as required was to run the histogram, save output to a file GDB in the default format, write a python script that reversed the rows and columns of that huge zonal histogram, and write the table to a CSV file, which I could then manipulate in Excel. While a table with 30000 columns is almost impossible to do anything with, a table with 30000 rows is no problem.
... View more
05-07-2012
09:29 AM
|
0
|
0
|
995
|
POST
|
Hi James, ... Also, the tool might fail with some formats (including dbf and info table) if a graph was being specified. So could you please first try to see what happens if you specify a graph name? Just to make sure I understand the point about the graph name--I was not requesting a graph, just the table. Do you mean that specifying a graph name and having the tool calculate and save it might help? Or just that if I were requesting a graph, then there would be naming issues. Thanks, Jim
... View more
05-04-2012
01:29 PM
|
0
|
0
|
995
|
POST
|
When running the Zonal Histogram tool, the Results window say the tool executes successfully after 4.5 hours, but the output table is not created. Right clicking on the output table in the Results window gives the options "add to display" and "copy location"; the first does nothing and the second has the right path and filename but the file doesn't exist. Here's the really puzzling part: There are no error messages. Has anyone run into this before? I've tried Zonal Histogram many different ways for this task, and nothing works well. Outputting to a table in a file gdb worked once, but then ArcMap and ArcCatalog choke trying to export the output table to DBF. Details: ArcGIS 10 sp4 Input zones: a layer that is a subset of polygons from a polygon shapefile Input raster: a large (16 GB) IMG raster desired output table: DBF file stored to a directory (not a geodatabase). Table should have 251 fields (yes, carefully chosen to respect the 255 field limit for dbf).
... View more
05-04-2012
09:03 AM
|
0
|
7
|
4375
|
POST
|
I've been trying for hours to get the code in "Merge example 2 (stand-alone script)" on the "Merge (Data Management)" help file page(http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//001700000055000000) to run, and finally realized that there appears to be an error in this ESRI-provided script. In the line: fieldMappings.RemoveFieldMap(fieldMappings.FindFieldMapIndex(field.name)) The words "Remove" and "Find" should not be capitalized. That is, the correct method names are "removeFieldMap" and "findFieldMapIndex", so the correct line is: fieldMappings.removeFieldMap(fieldMappings.findFieldMapIndex(field.name)) Can someone from ESRI confirm/correct the help file? (or let me know why I'm wrong) This is for ArcGIS 10. Thanks.
... View more
04-28-2012
07:30 AM
|
0
|
1
|
442
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|