Latest Contributions by DaleHoneycutt

We have tools for operating on NetCDF data.  See the Multidimension toolbox:  (http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/An_overview_of_the_Multidimension_toolbox/004300000002000000/) There's also a book of topics in the help system about working with NetCDF.  Here's the first topic of the book: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/What_is_netCDF_data/004600000001000000/ ... View more

Use the Select Data tool to select the network analyst sublayer you want to copy.  The network analysis layer would be the input to Select Data.  You then specify the sublayer (stops, facilities, etc) and that sublayer will be output.  You can then operate on this output just like you would any other layer.  You can input it to Copy Features or any other tool that accepts a layer (most tools accept layers) Select Data tool: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Select_Data/004000000009000000/ ... View more

Try the Spatial Join geoprocessing tool.  In the tool dialog box, there's a "field mapping" control.  You can right-click on a field in this control and select "Mean", which will average the values.  See: Spatial Join tool: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Spatial_Join/00080000000q000000/ Using the field map control: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//00210000000s000000.htm Mapping input fields to output fields: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//002z00000014000000.htm ... View more

Use the Copy Features tool.  You can give it a layer as input and it will copy the features to a feature class.  If the input layer has a selection, only the selected features will be copied. ... View more

See this blog post: http://blogs.esri.com/Dev/blogs/geoprocessing/archive/2009/03/06/Tips-and-tricks-_2D00_-accessing-feature-shape-in-Calculate-Field.aspx Since you want selected features to be calculated, just input a layer or table from the table of contents in ArcMap that has a selection -- only selected features/rows will be calculated. ... View more

Chris has the solution, but you could do the same iteration in ModelBuilder using Iterate Feature Selection (http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//00400000000s000000.htm (assumes you have 10.0) ... View more

One approach you can try is to first turn your polygon features into line features using the Feature To Line tool.  Important: the "Output has M values" geoprocessing environment setting should be set to "Enabled" so that your output lines can store M-values. Turn the lines into routes using the Create Routes tool.  The objectId of the lines will be your route id.  Your measure source will be LENGTH.  This will update the M-values on your lines to the length along the line. Now you can place point events along these lines using the Make Route Event Layer tool.  You'll need to create a table of the events.  An event would be a route id and a measure (say 10 meters) along the route. The result is a point exactly 10 meters along the line.  You can offset the point to the left or right of the line (inside or outside the polygon).  The problem with this is that you have to construct the table of events, something like: RouteID,  Measure   1 ,           10   1 ,           20   1 ,           30   2 ,           10   2 ,           20 etc... If all you need is a graphic display, add the output of Create Routes to ArcMap, right-click to get properties, and there's a tab for Routes.  You can place symbols along each route line at defined increments.  I don't know how to export these symbols to features however. There's probably an easier way, but the Feature To Line -> Create Routes will at least get you M values that you can experiment with. ... View more

Does the Feature Vertices to Points tool do the trick? http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Feature_Vertices_To_Points/00170000003p000000/ I've used this tool in the past to get corner points to use as registration tic marks. (Sorry, I just realized I confused this post with another post that wanted the opposite -- given polygons, create points from corner) ... View more

You'll need to make a model parameter of the field name. First, see this topic for a general discussion of how to create model tools: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/A_quick_tour_of_creating_tools_with_ModelBuilder/00150000001t000000/ Secondly, see this topic for information on how to make model variables: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Exposing_tool_parameters_as_variables/002w0000003w000000/ Then you can make a model parameter of the variable: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Creating_model_parameters/002w0000003z000000/ ... View more

Forgot to mention... you're calculating areas.  You can always use the Calculate Field tool to recalculate areas to any units after modifying geometry.  See this blog post for more info ... View more

You have to 'declare' beforehand what fields need to be reapportioned during an overlay operation.  You do this by using the Make Feature Layer tool to create a new layer, then running the overlay operation with this new layer.  The Make Feature Layer tool has a table where you can check  "Use Ratio Policy" for any of the feature class attributes.  In your case, you would want to use ratio policy for your area attribute (as previous response indicated, you wouldn't have to do this for geodatabase). Here's a blurg from the documentation: "Attribute values from the input feature class(es) will be copied to the output feature class. However, if the input is a layer(s) created by the Make Feature Layer tool and a field's "Use Ratio Policy" is checked, then a ratio of the input attribute value is calculated for the output attribute value. When "Use Ratio Policy" is enabled, whenever a feature in an overlay operation is split, the attributes of the resulting features are a ratio of the attribute value of the input feature. The output value is based on the ratio in which the input feature geometry was divided. For example, If the input geometry was divided equally, each new feature's attribute value is assigned one-half of the value of the input feature's attribute value. "Use Ratio Policy" only applies to numeric field types. ... View more

In short: no ... View more

Actually, what's going on is your parameter doesn't yet have a value.  Test that your parameter has a value before describing it.  You can use the altered state as a test as suggested, but the truest test is that it has a value: if self.parameters[0].value: ... View more

The way to do this is with the "Spaghetti and Meatballs" technique.  This technique is in the UC presentation http://resources.arcgis.com/gallery/file/geoprocessing/details?entryID=6D00A1DF-1422-2418-7FB1-4720F8155690.  Spaghetti and Meatballs works like this: Use the Feature To Polygon tool; input your feature class containing the overlapping polygons.  The tool will output a new feature class with non-overlapping polygons.  Essentially, your input is the 'spaghetti', and Feature to Polygon will turn this spaghetti into polygons. Now create the 'meatballs'. Run the output of Feature To Polygon input Feature To Point.  Be sure to check the "Inside" option.  What this does is create a point feature class of polygon centroids.  Each point has the object ID of the input polygons so that you can relate these back to the input polygons. Intersect the meatballs (the centroids) with the original overlapping polygons.  The output will be a new point feature class.  There will be one point in the output feature class for each polygon that overlays the point. Summarize the points output from Intersect.  What you're doing is reducing the multiple points per polygon into one point, summarizing fields as you do.  I can't tell you exactly what to do -- it depends on your attributes. Join the summarized points (the meatballs) back to the non-overlapping polygons. The download has a couple of models that show this technique, and the slides detail it further. I sure hopes this helps... I've been meaning to blog about this, but 10.1 keeps getting in my way! Thanks, Dale ... View more

Can't be done...  yet...  we're looking into this for future releases ... View more