Latest Contributions by DaleHoneycutt

Huh... I thought that would have worked as well.  I'll try to dig into it and what gives. ... View more

Seems like the Generate Near Table tool would be the place to start. You would set the Maximum number of closest matches parameter to 2.  This will yield a table with two records for each building.  It won't have the road width on the table, but you could use something like the Join Field tool to add this information to the table. The next step is to pivot the table.  That is, you don't want two records per building, you want one record with fields like: BuildingID Road1ID (closest road ID) Road1Width Road1Distance Road2ID (second closest road) Road2Width Road2Distance Off the top of my head, I'd look at the Pivot Table tool to do this, but I'm not sure if it will do exactly what you need.  I'll have to think more about it over lunch . ... View more

If you have 10.2 Advanced license, then you should use the Conflation tools.  If, by chance, your pipelines have a linear reference system, you could use those tools to migrate attributes.  What you're attempting to do is non-trivial. Editing your data so that it spatially matches, then using Intersect, may be the only sure way to do what you want (unless you can access the Conflation tools). ... View more

Dissolve should do exactly what you want.  Perhaps you need to uncheck Create Multipart Features? ... View more

The Points To Line tool doesn't honor the output coordinate system environment setting (see the bottom of the tool doc page where environments are listed; output coordinate system isn't listed, meaning it isn't used by the tool).  I'm guessing that the output line features are in the same coordinate system as the input points.  That means you'll have to use the Project tool to project the output to the coordinate system you want. ... View more

Is history logging enabled?  See Viewing tool execution history Here's a snippet from that doc: [INDENT]Enabling history logging To enable the writing of history log files, do the following:     From the Standard toolbar, click Geoprocessing > Geoprocessing Options.     Enable (check) the Log geoprocessing operations to a log file check box. [/INDENT] ... View more

Most likely, the data frame coordinate system and the coordinate system of the features are different. But all this can be avoided if you've got 10.1 -- you can instruct the buffer tool to do geodesic buffering by setting the Output Coordinate System environment to use a geographic coordinate system rather than a projected coordinate system.  Have a good look at the tool documentation. Here's the 10.1 doc for Buffer. If you don't have 10.1, then double check that the coordinate systems of the data frame (used by the measure tool) and the coordinate system of the feature class (used by the buffer tool) are exactly the same. ... View more

FYI: This was such a good thread that I mined it for a blog article:   More adventures in overlay: point in polygon ... View more

Seems to me that you could do this using Intersect rather than a bunch of Select Layer By Location and iterators.  If you run Intersect with the lines and polygons as input you'll get a line feature class with the attribute of the polygon that overlays it.  Each line will be split by the polygon that overlays it, forming new lines, but you'll have the parent information (the original objectID).  This seems to be enough information to do what you want -- use  Summary Statistics to find lines that have more than one record.  Not sure what the final objective is, but it seems that this'll give you all the info you need. ... View more

Here is a thread about this : http://forums.arcgis.com/threads/96992-Creating-polygons-based-on-values-of-other-polygons. Your problem is similar, but you have the additional constraint of compactness (is this for voter redistricting? If so, see http://www.esri.com/software/redistricting/. ... View more

Did you put quotes around your string in the tool input?  That is: "%value%_something.shp" If you did that and it still doesn't work, use Calculate Value.  The expression is "%value%_something.shp", there is no code block, but the output Data Type would be Feature Class.  Use the output of Calculate Value as input to your tool.  What you're doing is "casting" (in programmer terms) the string to a feature class.  But you shouldn't have to do this -- the quoted string should just work. ... View more

Maybe you could have just validated the model instead of re-inserting table to table? ... View more

There is no straight-forward way to do this.  You'll have to use Python. Build a custom script tool where: Your input spatial reference is a string parameter The parameter has Value List filter of the known projection names Inside your code, you do a look-up of the input projection name string and convert it to a spatial reference object. Call Make XY Event Layer passing in the spatial reference object you created. Any listeners out there have an existing script tool that does this? ... View more

Still confused... Attached [ATTACH=CONFIG]29536[/ATTACH]is the Make XY Event Layer dialog.  Click the icon next to Spatial Reference and you can choose the spatial reference. Are you saying that you don't want to use the Spatial Reference dialog?  That you want to provide a fixed list of spatial references (say, 4 or 5 "standard" spatial references) that the user can pick from rather than using the Spatial Reference dialog? ... View more