Latest Contributions by DaleHoneycutt

‎04-26-2013

(I was hoping Melita would answer you! Thanks Melita) David: Also take a look at this help topic: Coordinate system considerations for geoprocessing services. Even though this topic is about geoprocessing services, it has information useful for geoprocessing in general. A few points to look for in this topic: It links to a web application that shows how calculating length/area (using Cartesian math) is affected by the projection. It's a cool little app and shows just how awful Web Mercator is. It discusses the geoprocessing Output Coordinate System environment setting It specifically discusses the Near and Generate Near Table tools, two geoprocessing tools that compute distances using Cartesian math. It links to other help topics of interest

‎04-26-2013

Mike: I suspect this is just a refresh issue with the ArcToolbox window. There is definitely only one item description that you edit using the item description editor, available in ArcCatalog or the Catalog tree in ArcMap. After editing the Item Description in Catalog, exit the application (ArcMap/ArcCatalog). Open the application, show the ArcToolbox window, and see if your item description has been refreshed. If that doesn't work, try removing and adding your tool to the ArcToolbox window. If neither of these work, I'll do some more investigating. What version you running? Obviously, it has to be 10.x since Item Description was introduced at 10.0, but what specific version you on?

‎04-22-2013

Take a look at this blog article More adventures in overlay: counting overlapping polygons with spaghetti and meatballs. The first thing you'll need to do is to combine your 11 layers into one feature class. Use the Merge tool for this. Then you can follow the pattern outlined in the blog post: Create (spaghetti) polygons from the merged buffers above using the Feature to Polygon tool Create (meatball) centroid points using the Feature to Point tool Use Spatial Join to count the number of overlapping polygons

‎04-04-2013

See "Example 3" in this help topic: Examples of inline model variable substitution. There are other useful examples in this topic as well.

‎04-03-2013

If the input is a Feature Layer (and probably a Table View as well), you can determine whether it has selected records using the FIDSet property of the describe object. Here is some tests I made in the Python Window on a layer named "VennDiagram_1"). Note--for a dataset, the FIDSet property is not supported... you can only use this method with layers. >>> # no selected records >>> d = arcpy.Describe("VennDiagram_1") >>> print d.FIDSet >>> print len(d.FIDSet) 0 >>> # I select two features >>> print d.FIDSet 7; 9 >>> # I clear the selection >>> print d.FIDSet >>> # I select all records (note that this is the same as selecting none... in ArcMap/geoprocessing, >>> # nothing selected means to process all features. ) >>> print d.FIDSet 4; 6; 7; 8; 9; 12 >>>

‎04-02-2013

If I understand the problem, it's really easy to solve. See attached. Basically, you create two string variables (Year and Type). Both these variables would be model parameters. You could set a value list filter on these two parameters. You then use Calculate Value with the expression "%Year%%Type%" with the output type set to String. [ATTACH=CONFIG]23152[/ATTACH]

‎04-02-2013

See this blog post on concatenating field values. This is if you're concatenating field values. If you want to concatenate two string data elements in ModelBuilder, in-line variable substitution may be what you want.

‎04-02-2013

I agree that the Spatial Join tool is probably the way to go, but take a look at the Identity or Intersect tools. Both these tools create new features by overlaying the input features, which may be something you want to do. This blog about overlay, and subsequent blogs may also be helpful.

‎04-01-2013

Short answer: You need to make the output variable of your model (the new layer) a Model Parameter. Right-click the variable and choose "Model Parameter". See Creating Model Parameters in the help.

‎03-28-2013

I don't have an answer about the cursor problem, but in looking at your task, it seems that you don't need cursors at all -- you could overlay the buffers and the parcel features using Spatial Join, Intersect, or Identity. Spatial Join might be the most direct way -- it will give you a Join_Count attribute which would be the number of buffers that intersect a parcel. And it would be lighting fast compared to select by location for each individual parcel. For an example to get started, see this blog post and scroll down to the section on Spatial Join. Target features = parcels Join features = buffers Join operation = JOIN_ONE_TO_MANY Match Option = (you have a choice here) [INDENT]If you want buffers that just touch the boundary of a parcel to count, use INTERSECT[/INDENT] [INDENT]If the buffer has to cross into a parcel, use WITHIN_A_DISTANCE with a small distance. The blog explains this.[/INDENT]

‎03-27-2013

Curtis: PYTHON_9.3 is the way to go. The "9.3" python processor returns lists instead of enumerators, and numerous other benefits over the 9.2 processor (I'll ask around and see if I can get a list of these 'other' benefits, but we are going to have to step into the way-back machine and rummage around thru the muck). I don't have any performance numbers, but the 9.3 parser will be faster. Personally, I wish that the PYTHON_9.3 was the default parser for Calculate Field and Calculate Value, but deeply knotted technical issues prevented us from doing that at 10.0 (I think it might be possible now).

‎03-12-2013

Have a look at this blog post about spaghetti and meatballs. I *think* that your methodology is going to involve creating spaghetti and meatballs as discussed in the blog.

‎02-26-2013

Graeme: Good suggestion. I added a note to the doc.

‎02-26-2013

You could also use the Spatial Join tool. The Target Features and the Join Features would be the same layer (your point layer). The Join Operation is JOIN_ONE_TO_ONE, the Match Option is WITHIN_A_DISTANCE and your Search Radius is 300 meters. This will give you a new output point feature class where TARGET_FID is the object ID of the input point and Join_Count is the number of points within 300 meters. Also, for most proximity (distance) calculations, I agree that projecting your data to a projected coordinate system such as UTM is usually a good idea.

‎02-25-2013

For 'finding' features, start with Select Layer By Attribute For addresses, start with Geocode Addresses For Linear Referencing, start with Make Route Event Layer

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

My Ideas

Latest Contributions by DaleHoneycutt

Re: Projections effect on GIS computations? Area and distance measurements in the GIS

Re: Toolbox Metadata. How does this work?

Re: Heat map from Buffered Layers

Re: Arcgis 10.1 modelbuilder - defining a field name in a expression to be a paramete

Re: ArcTool: simulating 'Use selected features' option

Re: String Concatenation

Re: String Concatenation

Re: Transfering Attributes between Overlapping Polygon Layers ??

Re: Displaying Geoprocessing Results

Re: Update Cursor Tool Returing Error

Re: Which Calculate Field expression_type should be used?

Re: Overlapping polygons, multiply shapfiles, and attribute tables. Oh my!

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

Re: Point buffer overlap

Re: How do I use the "Find" tool in Modelbuilder

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