Latest Contributions by ChrisDonohue__GISP

Some possibilities: One could do a Spatial Join: Spatial Join—Help | ArcGIS for Desktop  Another possibility is to do an Identity.  Note, however, that an Advanced license is needed for Identity. Identity—Help | ArcGIS for Desktop  Note that if your linework is not coincident, there could be some issues with using either of these.  In that case, you may need to run Integrate first.  One caution - Integrate modifies the source data (instead of creating a new output), so make copies of your data first and run Integrate on the copies. Integrate—Help | ArcGIS for Desktop  Chris Donohue, GISP ... View more

Just hire this guy to do it for you!  jborgion  Chris Donohue, GISP ... View more

If you have ArcGIS Desktop, access to the Spatial Analyst extension, and access to elevation data, the general workflow would be to create the initial elevation surface, derive the ridgelines, subtract 100 feet from the ridgelines layer to make a new surface, then use that new surface to intersect the original surface, then convert the resulting intersect to vector.  The particulars of each step will depend, however, on what you have access to. Chris Donohue, GISP ... View more

For starters in providing a solution, can you provide the following: 1.  Which software package are you using?  ArcGIS Desktop?  ArcGIS Pro?  Another? 2.  What version is the software? 3.  If it is ArcGIS Desktop or ArcGIS Pro, do you have access to the Spatial Analyst or 3D Analyst Extensions? 4.  Is vertical elevation data available for your planning area?  What format?  Elevation points, a raster surface? 5.  Are the ridgelines already derived or will part of the task be to derive them to then use in the analysis? Chris Donohue, GISP ... View more

In noticed when looking at the posted screenshot that several of the paths used appear to contain restricted characters.  Specifically, there seems to be periods in folder names.  If that is the case, try renaming them to underscores or otherwise eliminate them, as restricted characters will often trip many types of raster processing.  Also, it is recommended if possible, keep the path as short as feasible and avoid long file and folder names.  Even though in theory one could have long paths, in reality raster processes can choke or throw errors if long paths are used.  Yet the same process will work without issues if the path is shortened.  For example, put the data in something really short like C:\Test\Water. Chris Donohue, GISP ... View more

May be of help - I don't know if you saw it, but there is a recent GeoNet thread along these lines: https://community.esri.com/thread/192069-initial-gis-implementation  Chris Donohue, GISP ... View more

Installed the new tool and ran it. Some tools ran fine, others had issues.  Some of this may be due to the older version of ArcGIS used. Here's the results on test data in a File Geodatabase using ArcGIS Desktop 10.2.1: Check for Overlaps function: - overlap_polys output correctly identified polygon overlaps in a parcel test dataset. - overlap_Topology output also found the issues correctly. - OverlapErrors_point and OverlapErros_line outputs had no results (they showed up in the Table of Contents, but I'm not sure if they are used as part of the "Check for Overlaps" function. Check for Gaps function: - GapErrors_poly output was empty/did not find the gaps in a parcel test dataset. - gap_Topology output did find the gaps correctly. - GapErrors_point output was an empty table/did not find gaps. - GapErrors_line found all the gap issues and output them as lines. Check Line Segment Dangle function: - YourDangleErrors output correctly found dangles at distances of 0.1 foot and 1 foot in street centerline test dataset.  Did not 4 other Dangles present (35'+). Check Line Segments Overlap function: - intersect_Topology output correctly showed overlapping lines when run on a test street dataset. - IntersectErrors_point output was an empty table/did not find overlap. - IntersectErrors_line output did find the overlaps.  - IntersectionErrors_poly output was an empty table/did not find overlaps.  Also, I'm curious as to how this output would be used? Scratch Workspace function: - Works.  I was able to switch the folder location for  the Scratch workspace and the other functions then output the results there. Chris Donohue, GISP   mmmm, yummie street data...... ... View more

OK, I'll give it a try. Chris Donohue, GISP ... View more

I'm not a lawyer, so can't say with absolute certainty, but my guess would be that if you make your own symbology in ArcGIS that is similar to what others have used, it is probably OK unless you made it exactly as someone else did.  For example, I would stay away from using any very distinctive elements that were used in the original. I don't know if we have someone familiar with the finer points of this issue on GeoNet - if so I'd be curious also to hear what the specifics are on this issue. Chris Donohue, GISP ... View more

There are several ways to do this.  Here's one workflow: 1.  Put the Lat Longs into an Excel spreadsheet. 2.  Convert the Lat Longs to decimal degrees.  Decimal Degrees = Degrees + (Minutes/60) + (Seconds/3600). 3.  Add a new field and then number the Lat Long coordinate pairs in the sequence they need to be connected.  For example, fieldname "SortOrder", then number each 1, 2, 3, etc in the order that they should be connected. 4.  Follow this process (Add XY Data) to add the data to ArcGIS.  This will create a point for each coordinate pair. Adding x,y coordinate data as a layer—Help | ArcGIS for Desktop  5.  The added data will be in what is called an Event layer in ArcGIS.  Note that this is a temporary layer.  Right-click and Data, Export Data to save off a permanent copy of the points. 6.  Run the Points To Line geoprocessing tool on the point features, being sure to specify for the Sort Field (optional) the field name that has the order of the points so the lines are drawn in the correct order (which was created in step 3 above).  For example, I called the field "SortOrder". Points To Line—Help | ArcGIS for Desktop  Note - places where things go awry commonly happen at step 4, as formatting in Excel can be a culprit.  If that happens, post here what went awry and we can troubleshoot it. Also - an overview article of the same process: Adding Excel Lat Long Coordinates into ArcGIS - GIS Geography  Chris Donohue, GISP ... View more

You may have already considered this, but just wanted to suggest using Topology as a way to find the gaps instead of manual viewing, as Topology will rapidly find the issues.   I would suggest using the Topology Line Rule "Must Not Have Dangles (scroll down in the link to see line rules): Geodatabase topology rules and topology error fixes—Help | ArcGIS Desktop  Also, when one zooms in to around 1:1 when looking for gaps manually there can be visual artifacts that can make it appear that there is an gap when there is not, which makes reviewing difficult.  This is a known limitation of the software.  ESRI Customer support did say last year that future versions of ArcGIS might end up with a built-in limit to how far in one could zoom so people wouldn't go past the limit for the software.  I don't know if this might be where they put that limit into place? Chris Donohue, GISP ... View more

No problem.  Thanks for sharing the tool and being willing to adapt it.  That said, if it turns out rearranging it to make it work for older versions is a total pain, don't worry about modifying it.  Most folks seem to be on newer versions.  I suspect it took a ton of time to get this to where it is at now, so no need to rebuild the world to make it match the limitations of older software. Keep up the good work, Chris Donohue, GISP ... View more

Got some results this time.  When run, the tools chug away and the classic "Not Responding" shows up, but then it finishes out after several seconds.  Tool runs: Check for Overlaps - worked when run on parcels with an intentional overlap.  Looks good. Check for Gaps - no results for output feature class GapErrors_poly when run on parcels with gaps, but did get the parcels gaps correctly depicted as lines in GapErrors_line output (purple lines below). Check Line Segments - DangleErrors output correctly found two dangles that were close to other lines, but missed dangles that were far from other lines.  Could be a just be a tolerance setting, though. Unfortunately, no results for OverlapErrors_line output despite the intentional addition of line overlaps to the street test data. Note - I made some assumptions when running these, which may influence the results: 1.  The tools ran without being in Editing Mode for the selected feature class, which I assume is OK.  If instead it is assumed that the user is in Editing Mode for the feature class being checked, let us know. 2.  I didn't worry about whether the layers selected to run a tool on were set as specifically Selectable. 3.  Ran the tools on test feature classes in a File Geodatabase.  Did not try them on Versioned data. Also, the bane of all software development, a feature request   Is there a way to change the default location the output feature classes get written to?  At the moment the seem to be going to a new geodatabase added to the C: drive.  Not a critical request, but it would be nice to be able to save it to a few levels further out in the C: drive. Looking good, Chris Donohue, GISP ... View more

I'll give that a try. Chris Donohue, GISP ... View more

The AddIn came in easily and looks good, but unfortunately no luck on getting it to work.  I tried some test data in a File Geodatabase which was purposefully altered to have gaps and overlaps, but didn't get any results from running the AddIn tool.  There was not any errors or other feedback, just no results. I suspect it may be the ArcGIS version differences of 10.3.1 vs 10.2.1, i.e. the Python version associated with each version of ArcGIS has some critical difference (I'm still in the stone ages (10.2.1)).   I guess for now add that as a potential limitation for users. Chris Donohue, GISP ... View more