Latest Contributions by DaleHoneycutt

‎02-25-2013

Is this a 1:M join? That is, your table has more than one record per county. Sounds like that's what you've got. I'd go with the Make Query Table tool. There's an example of using Make Query Table in this help topic -- it's the 2nd example.

‎02-25-2013

In deciding whether to enable the Always run in foreground checkbox, we scan the model and examine the properties of each tool the model uses. If one of those tools has Always run in foreground checked (the default state), then the parent model's checkbox is disabled; you can't run a model in the background if one of the tools it is using is set to run in the foreground. So, I'm thinking that your custom models are calling other custom models or tools that you've built and you first have to enable those to run in the background. Be sure to look at this topic about background: Running custom (model or script) tools in the background. It discusses the above behavior as well as the importance of setting all layer variables to be parameters.

‎02-25-2013

See this blog post More adventures in overlay: counting overlapping polygons with spaghetti and meatballs. It's not exactly what you're looking for, but the section titled "Point in polygon overlay" should be very helpful.

‎02-22-2013

ArcGIS Geoprocessing services will overwrite existing data by default. If you are on 10.1, I would suggest that you use %scratchfolder% instead of %scratchworkspace% since you're writing a .dbf. But if you're creating geoprocessing services with 10.1, you don't have to use any scratch workspace or folder -- the service publishing process figures out that you're writing a .dbf file and will 'automagically' write it to the scratch folder.

‎02-21-2013

Seems like you just need to run the Intersect tool (or Spatial Join). The output will be a point feature class with all the attributes of the lighting strikes and the attributes of the fire polygons they fall within. You could then run attribute queries on this output. If a fire polygon doesn't have a lighting strike within it, then the output feature class from Intersect won't contain any features that have that polygon's OBJECTID or attributes. You could then select these "no strikes within" polygons and run Generate Near Table to find the closest strike.

‎02-11-2013

Ah... that geometric mean! Not that I know of. I'll have to do some checking. For sure Dissolve doesn't have the option.

‎02-11-2013

Feature class and table names within a geodatabase must be unique, even if they reside in a feature dataset. This is unlike folders on the file system. I just did a test and arcpy.Exists does return true whether or not the feature class resides in a feature dataset. (I like using the python window to quickly test how something works). Here's what I did. In my geodatabase "Test.gdb", I created a Feature Dataset named "TestFD". Within TestFD, I created a feature class named "Fred". In python: >>> print arcpy.Exists(r'E:\StreetIntersectionList\ToolData\Test.gdb\Fred') True >>>

‎02-11-2013

You can input a Weight Field to the Mean Center tool -- is this what you mean? For more information, take a look at the "how it works" doc.

‎02-11-2013

Try the Mean Center tool

‎02-04-2013

Start with the Quick Tour of developing tools in Python. This help topic is the overview topic that explains how to create a script tool that you can use in ModelBuilder. As far as the Python code itself, you want to execute your IDL code from w/in Python, reading and writing to standard input/output or to files. I don't have any experience with IDL so I don't know what it's capable of. And I kinda forget the Python calls for executing external programs (did it many years ago), but there's lots of examples on the web; just do a search -- I found some threads on stackoverflow.com You should visit our Python resource center, as well as our Python recipe site. There is also a Python forum.

‎02-02-2013

See attached image. The help topic Using layers and table views may help explain more.

‎01-03-2013

arcpy.AddError() is currently a no-op in Calculate Value. You can, however, raise an error, as in: raise arcpy.ExecuteError("This input argument is weak") However, this generates a whole call stack of errors -- it isn't very pretty, but it works... the model will stop execution and the last message will be "This input argument is weak" ... your user should be able to locate the message easily. The best solution is to create a little script tool. Here's the code for a script tool that takes two args, message and severity. I can post this tool to the script tool gallery later today. Anyway, if you're up to coding a script tool: import arcpy message = arcpy.GetParameterAsText(0) severity = arcpy.GetParameterAsText(1) arcpy.SetParameter(2, True) # Output parameter set to false on error if severity.upper() == "ERROR": arcpy.SetParameter(2, False) # error, don't continue arcpy.AddError(message) if severity.upper() == "WARNING": arcpy.AddWarning(message) if severity.upper() == "INFORM": arcpy.AddMessage(message)

‎12-21-2012

There might be a problem with the netCDF to Layer tool running in background. Have you tried running in foreground? See the topic Foreground and Background Processing for more info on how to change to foreground.

‎12-21-2012

Can you provide some of the data that I can test? The only explanation I can think of is that in fact one of the inputs does have overlapping polygons.

‎12-19-2012

Just a shot in the dark here: take a look at this topic A quick tour of publishing a geoprocessing service and scroll down until you find the section titled "Small output datasets". It explains how output data is copied to the server in order to support map services. This may or may not by your situation.

Online Status	Offline
Date Last Visited	‎11-11-2020 02:22 AM

My Ideas

Latest Contributions by DaleHoneycutt

Re: Many Table Values to One Polygon

Re: Why is "Always run in foreground" grayed out?

Re: Point buffer overlap

Re: Scratchworkspace file already exists

Re: Lightning Data Analysis

Re: Calculate Geometric Mean

Re: Having trouble in book "Getting to Know ArcGIS ModelBuilder"

Re: Calculate Geometric Mean

Re: Calculate Geometric Mean

Re: How to nest IDL code into Python script for use as a tool in ArcGIS ModelBuilder

Re: Using Selection Tools and "Make Feature Layer" Effectively and Efficiently

Re: Print messages from Calculate Value tool?

Re: netCDF to feature/raster problems

Re: Overlapping polygons appear after intersection

Re: Published GP Service keeps copying data to server

Re: Copy feature layer while keeping the objectid

Re: Which Calculate Field expression_type should b...

Re: Filling gaps in polygons

Re: Find maximum value across a row

Re: Null Values in Excel Spreadsheet Import