Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Cancel
- Home
- :
- About ThomasDilts
ThomasDilts
Frequent Contributor
since
07-04-2014
05-19-2026
158
Posts created
103
Kudos given
1
Solutions
190
Kudos received
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
My Ideas
(22 Idea Submissions)Latest Contributions by ThomasDilts
|
POST
|
Hi Duncan. Thanks for the heads up. I ended up dropping the Cell Statistics altogether replacing it with the Plus tool, but to no avail. I'm thinking that the next step might be to try exporting the model out to python, re-do the coding for the looping, and then see where that takes me. The good news is that it works in edit mode for what I want it to do.
... View more
11-16-2018
08:54 AM
|
0
|
0
|
753
|
|
POST
|
ArcCatalog didn't work any better. It just crashed instead of getting hung up. The freeze/crash always happens on the first time the feedback variable is used in the second iteration.
... View more
11-15-2018
03:02 PM
|
0
|
0
|
3540
|
|
POST
|
Hi Curtis. I tried your suggestion. It was a really good suggestion, but it still didn't work. What I did was change the model parameters to string variables and then use those to name the output file with the feedback. Then I just removed that variable from "add to display" in ModelBuilder. At the same time I also made a few other changes. I changed the Cell Statistics tool to the Plus tool and set pyramids and raster statistics to not run by default. I suspect that the problem has to do with the iteration itself, but I still don't understand why it doesn't run in "tool mode" but does fine in "edit mode". One thing that I will try next is try to run it in ArcCatalog since there is no map display there. Another thought is that I should just convert the entire thing to a python script. I'd appreciate any more thoughts, comments, ideas, or feedback that folks might have.
... View more
11-15-2018
02:16 PM
|
0
|
4
|
3540
|
|
POST
|
Hi Curtis. Let me try that when I get to the office. That is a great suggestion. I've got a couple of ideas on how that problem might be remedied.
... View more
11-15-2018
07:12 AM
|
0
|
0
|
3540
|
|
POST
|
I've got a model with iteration that runs fine from within ModelBuilder. In fact, I'd say that it is downright zippy taking about a minute for every 5 rows in a raster attribute table. When I run that same model as a tool using the same datasets it grinds to a halt getting hung up on iteration 3 or 4. Specifically it is the Cell Statistics tool and I'm using feedback to save the results from one iteration and then add the results from the next iteration and so on. I'm wondering if anyone has any idea what would be different enough between ModelBuilder and "tool mode" to account for such a large difference in performance. I'd hate to have to share a tool with others with the caveat that it can only be run from ModelBuilder especially when it is working so well otherwise. Thanks -Tom Dilts
... View more
11-13-2018
01:24 PM
|
0
|
11
|
4559
|
|
IDEA
|
Currently the watershed tool in Spatial Analyst will default the extent to the intersection of inputs, which is almost always the pour point layer. That results in watersheds are truncated because of the spatial extent of the output raster. It should almost always default the other way around, to the flow direction raster or use union of inputs so that watersheds don't get chopped off. I propose that for this tool that the defaults are set to override the normal defaults.
... View more
09-21-2018
04:30 PM
|
0
|
0
|
998
|
|
IDEA
|
It would be great if there were a version of the eliminate tool that could deal with polygons connected to other polygons only by one vertex. Currently the eliminate tool connects to polygons connected by two or more vertices. When converting rasters to polygons it is really common to get polygons that are diagonal to one another (see the image below).
... View more
10-10-2017
11:08 AM
|
1
|
2
|
1268
|
|
IDEA
|
This is my list, but I think that it would be great if the user community could weigh in. Fill - default to CUBIC or BILINEAR All the tools in the Interpolation toolset - default to CUBIC or BILINEAR Most of the tools in the Local and Neighborhood toolsets - should be based on the input (if one layer is floating point then the output should use CUBIC or BILINEAR) Map Algebra/Raster Calculator - should be based on the input (if one layer is floating point then the output should use CUBIC or BILINEAR) All of the tools in the Math toolset - should be based on the input (if one layer is floating point then the output should use CUBIC or BILINEAR) All of the tools in the Multivariate - default to CUBIC or BILINEAR Mosaic/Mosaic to New Raster - should be based on the input (if one layer is floating point then the output should use CUBIC or BILINEAR) All the tools in the Density toolset - default to CUBIC or BILINEAR All the tools in the Distance toolset - should be based on the input (if one layer is floating point then the output should use CUBIC or BILINEAR) Flow direction, watershed - default to NEAREST
... View more
09-19-2017
10:58 AM
|
0
|
0
|
2639
|
|
IDEA
|
Good to know. That means that I've already got it on some tools.
... View more
08-11-2017
02:43 PM
|
0
|
1
|
2639
|
|
IDEA
|
Steve, This is great to hear. Also, it is a good nudge to get me going in the direction of upgrading to Pro.
... View more
08-11-2017
02:25 PM
|
0
|
1
|
2639
|
|
IDEA
|
Improper use of the raster resampling environment settings can lead to problems with rasters. If the default option NEAREST is selected for continuous data then it can result in artifacts that appear as horizontal and vertical striping. The striping is especially problematic for DEMs, hillshades, slope rasters, and flow direction rasters and can even affect watershed delineation. Often these problems can be hard to identify and deal with at a later date. I'd suggest that ArcGIS should be re-designed to be smart enough to detect the proper resampling technique. If the data are integer then NEAREST could be the default, but if the data are floating point then BILINEAR or CUBIC could be the default.
... View more
08-09-2017
03:49 PM
|
2
|
7
|
2933
|
|
IDEA
|
In general I think that having options to view or simulate colors for both color blindness and grayscale would be valuable tools. Right now I find myself designing maps, then exporting them as jpg, png, etc., and finally having to simulate color blindness with VisCheck or some other simulator, then going back to ArcMap to make changes, ... Wouldn't it be great to have a button to 'simulate grayscale' or 'simulate colorblindness' built within ArcMap?
... View more
12-12-2016
11:12 AM
|
6
|
0
|
5180
|
|
IDEA
|
-->
Having two catalog windows that support multiple file selections would be useful because it would make moving files really simple. No longer would the user have to select the files and then navigate to the new folder locations and paste the files, but rather they could simply drag from one folder to another in side-by-side views.
... View more
03-01-2016
01:00 PM
|
5
|
1
|
821
|