Latest Contributions by ChrisDonohue__GISP

Besides what Dan Patterson  mentioned about checking the geoprocessing logs, one can also check the metadata. Each geoprocessing tool that creates new output data or updates the input data will add metadata about the execution of the geoprocessing tool, which includes the tool name, its location, and the parameters used ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Viewing Tool Execution History.  Scroll down to the section "Geoprocessing History in Metadata" Chris Donohue, GISP ... View more

Here's a similar recent GeoNet post that may may be of help: https://community.esri.com/thread/188140-home-range-tool-or-program  Chris Donohue, GISP ... View more

Another possibility in regards to the geoprocesing history being missing.  If you are using ArcGIS 10.2, there apparently is a bug. NIM096145: When background processing is enabled, geoprocessing..   If this is the case, they do offer a workaround in that one can turn off the background processing and then the geoprocessing history will be retained.  This issue may occur in other versions, though the bug report states it is fixed in 10.5 Chris Donohue, GISP ... View more

To help in troubleshooting, can you post what the Get Field Value tool inputs look like?  I.e. what is filled in here: Chris Donohue, GISP ... View more

As Neil Ayres alluded to, one can create a topology on the whole dataset, then in the Error Inspector window check on the box for Visible Extent only.  Zoom to the extent of what you want to work on and then click the "Search Now" button to see what issues are present in that area.  You can bookmark the locations to make it easier to get to each extent that needs review. Also, a more pragmatic way to accomplish your goal is to export a selection to a new feature class and delete from your main file the same features (make a backup of the full unaltered file first).  Run topology on the exported features and do the corrections.  Then Append the corrected feature class back in to your main file.  It's not an elegant approach, but it is workable.  The distinct area of work created by this method is helpful in ensuring the area that needs to get corrected gets done in full, while at the same time does not lead one into "wandering off" into neighboring areas that are not as high a priority to correct. ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Append (Data Management) Chris Donohue, GISP ... View more

In terms of the issue with their not being results under geoprocessing, is the geoprocessing option checked?  Go to:  Geoprocessing, Geoprocessing Options..., check on "Log geoprocessing options to a log file".  Also, consider lengthening the time interval in section "Results Management" by "Keep results younger than:"  Check this setting, as one of the options is "Never save". Viewing tool execution history—Help | ArcGIS for Desktop  Chris Donohue, GISP ... View more

My first thought it that a Precondition may need to be established.  Otherwise the Calculate Field might run before the Get Field Value.  However, I am not certain that is what is causing the issue.  Might be worth a try, though. ArcGIS Help (10.2, 10.2.1, and 10.2.2) - A Quick Tour of Preconditions ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Setting Preconditions Chris Donohue, GISP ... View more

 I can get it to work by chaining Add Fields together in Modelbuilder.  Can you describe what you have tried and what seems to be going awry?  Are you using an Iterator? Also, any chance the shapefile naming conventions are tripping things up? Also note - Add Field doesn't produce a new shapefile, but adds a field to an existing shapefile.  So if you need the original shapefile maintained without the new fields, make a copy of it first. ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Add Field (Data Managment) ... View more

 What geographic location are you looking for?  Chris Donohue, GISP ... View more

That was my read also, that the Warning was undesirable. If anyone figures out how to suppress it, I'd be curious to hear it as I can see how it can cause confusion. Chris Donohue, GISP ... View more

Also, it looks like the warning you are getting is expected behavior.  Note - I added the underline to the tool help below: Overwriting tool output The Overwrite the outputs of geoprocessing operations check box controls whether tools automatically overwrite any existing output when run. When it is checked, you receive a warning before tool execution that the output exists, but the tool executes and overwrites the output dataset. With this option off, existing outputs are not overwritten, and the tool displays an error, preventing you from executing the tool. Source:  ArcGIS Help (10.2, 10.2.1, and 10.2.2)  - Using geoprocessing options to control tool execution Chris Donohue, GISP ... View more

A question - is the goal to produce a feature class for use beyond just as another input to the existing model?  If so, don't worry about naming the output here; instead add a Copy Features following the Make Feature Layer and name it there.  What I'm thinking is that you are getting the error because the model creates it in temporary workspace whenever the model is run.  So if the model was already run once, it already exists. From the Make Feature Layer Help (ArcGIS Help (10.2, 10.2.1, and 10.2.2) ) Summary Creates a feature layer from an input feature class or layer file. The layer that is created by the tool is temporary and will not persist after the session ends unless the layer is saved to disk or the map document is saved. Usage The temporary feature layer can be saved as a layer file using the Save To Layer File tool or can be saved as a new feature class using the Copy Features tool.   Chris Donohue, GISP ... View more

If you have access to an Advanced license, Step 2 and 3 can be replaced with the following to eliminate most of the manual editing: 2.  Run Feature Vertice to Points with the Point Location (optional) set to Start to create a point layer of the line starting points from the lines generated in step 1. ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Feature Vertice to Points (Data Management) 3.  Add a field to the Points for Distance and populate it with the appropriate value (or Join it from your existing table). 4.  Buffer the Points, using the Distance Field as the criteria.  This will create a polygon layer around each start point. 5.  Intersect the Line layer (from step  1) and the Buffer polygon layer, with the Output Type (optional) set to Point.  This will create points on the line at the distance from the start. 6.  Run Split Line at Point on the Line layer using the Line layer as the input and the points from the Intersect.  This will result in a new line layer split at the points. ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Split Line at Point 7.  Manually delete the unneeded segments.  Or alternately, do Spatial Joins to append the information to each line, then do a query to find the ones not needed and delete them en masse. 8.  Run Feature Vertices to Points again on the lines, with the Point Location (optional) set to End.  The result will be your final points. Caveats:  If there are many points close together and the distances for each are greater than the distance to nearby points, nearby lines will be split multiple times.  This will require careful review after splitting the lines to pick the correct segments to be deleted, and then editing to reconnect the lines back into one segment for each line (representing start point to desired distance). Also, if this process can be automated with Modelbuilder or Python, if you are familiar with either.  This might be worth figuring out if you have many datapoints to do and/or will be repeating this same process often.  I bet there is probably a way to do this whole thing with more finesse with Python; but this will work otherwise. Chris Donohue, GISP ... View more

Another workflow: 1.  Add a new field to your data table called "Line ID".  Give each point pair the same LineID value.  Then use Points to Line with the Line Field (optional) setting set to LineID.  This will generate a new line feature class from your point pairs. ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Points To Line (Data Management)  2.  Go into editing mode.  Select a line, then on the Editor toolbar click Editor, then Split, and manually enter the split distance.  Note - check the line Directionality so the split is occurring in the desired spot.   After the line is split, delete the segment not needed. ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Splitting lines at a specified distance or percentage 3.  Create a new point in Editing Mode by Snapping it to the line end of the newly-edited line file.  EDIT:  Added step 3 to finish the process (didn't have enough caffeine at original time of writing, so left out the obvious ) Chris Donohue, GISP ... View more