Latest Contributions by ChrisDonohue__GISP

I can't answer directly for Melinda, but one way to evaluate the network is to run topology rules on the linework used to create the network.  For example, running the rule "Must not have dangles' will help find gaps in the linework. Small gaps in the linework can be surprisingly common, as many line datasets were not set up to snap the lines together.  The resulting gaps are often very small, to the point where they are not visibly noticeable.  So everything looks great when viewing the linework, but from a Network perspective they are disconnected. One caveat - checking the topology results will take some reviewing, as some dangles are real, so are not really errors.  For examples, all the dead-end streets will be flagged as dangles. Topology rules ArcGIS Help (10.2, 10.2.1, and 10.2.2) Chris Donohue, GISP ... View more

I'm not exactly sure what is causing the issue, but this is a good starting point. Here's ESRI's explanation for the error: 35151 - 000732: Dataset does not exist or is not supported If you haven't tried them, look into their suggestions - maybe that will clear things up? Chris Donohue, GISP ... View more

Rebecca makes a good point on the reverse-ability of transformations. Here's what the ESRI help states: Datum transformations work in either direction. For example, the transformation listed as NAD_1927_to_NAD_1983_NADCON transforms from NAD 1983 to NAD 1927, as well as from NAD 1927 to NAD 1983. 21327 - Select the correct geographic (datum) transformation when projecting between datums Chris Donohue, GISP ... View more

Another setting to check, on the off chance that it is causing the issue: Selection, Selection Options: Make sure the Tolerance value is not a large number, or it may cause selection far beyond the intended extent. Chris Donohue, GISP ... View more

Not sure if this is what is causing the specific issue you mention, but I will bring this up for others who have Selection issues and read this post.  It may be that the Interactive Selection Options are set differently than expected.  I've gotten tripped up by this at times when instead of the default "Create New Selection" the selection gets changed to a different method.  Chris Donohue, GISP ... View more

I'll second Joe's recommendation - Representations are probably the way to go.  Network Analyst won't help you here - this does not appear to be a Network Analyst solution and Network Analyst does not have much in the way of display capabilities. Representations ArcGIS Help (10.2, 10.2.1, and 10.2.2) There are some caveats on Representations, though.  Representations take a while to figure out, so plan to spend some time learning about them.  They are not something learned in a few minutes.  Some of their setup is non-intuitive, and they don't always behave as expected when creating and editing.  They can be very useful, but you will need to dig into them a bit before you can get rolling. As a result, Representations are great if you plan on re-using them over and over for several maps, but usually not worth it for one-time maps that need to be done quickly. Chris Donohue, GISP ... View more

I'll addMelinda Morang (ESRI Network Analyst Expert) here on the off chance the automated forwarding of Network Analyst questions didn't trigger.  She is very helpful in figuring out Network Analyst issues. Chris Donohue, GISP ... View more

Some bits and pieces that may help: The Tool help offers the following: Input/Output fields of incidents - Status field Element not traversable (3)—The network element that the network location is on is not traversable. This can occur when the network element is restricted by a restriction attribute. ArcGIS Help (10.2, 10.2.1, and 10.2.2) Here's the Restrictions available: ArcGIS Help (10.2, 10.2.1, and 10.2.2) This restriction looks like it would be best for the non-vehicular portions: Prohibit network elements The most common use of a restriction is to prohibit traversal. For example, one-way streets can be modeled with a restriction attribute so they can only be traversed from one end to another, but not in the reverse direction. Similarly, a restriction attribute on walkways can completely prohibit traversal so that the network elements identified as walkways are excluded from any route that is generated for a motorized vehicle. Chris Donohue, GISP ... View more

I don't know the exact answer, but something I noticed from the tool help may be worth checking on the chance it is what is triggering the error: TINs used for surface modeling should be constructed using projected coordinate systems. Geographic coordinate systems are not recommended because Delaunay triangulation cannot be guaranteed when the XY coordinates are expressed in angular units, and distance-based calculations, such as slope, volume, and line-of-sight, can produce misleading or incorrect results. ArcGIS Help 10.1 Chris Donohue, GISP ... View more

To tag onto what Darren mentioned, if part of your goal requires identifying the rock outcrops from the imagery, there are some things to look out for. First, keep an eye out what imagery was used by others for this sort of analysis and what bands they used.  Often there are certain band combinations that have been found to work well for specific identification tasks.  Particularly important is finding out what interferences are out there that can cause misclassification. Second, plan to do a few iterations before coming up with the final result.  I'll offer an example that is relevant given your topic - I used Landsat data from Eastern Washington State in the mid 1990's in grad school for a Remote Sensing class project to evaluate land cover.  Using Supervised Classification, I came up with a seemingly good classification system, but when I ground-truthed the results afterwards, it turned out water and basalt outcrops were both being classified as water.  And there were many basalt outcrops in my project areas....Ooops.  Ultimately, this led to using a different band combination to differentiate the two, with much better results in the long run, but it sure added to my workload in the short run to fix that unexpected outcome. So keep an eye out for what combinations people use for outcrop identification and how they avoid interferences.  Additionally, when you do run the classification, be sure to include time for several iterations, with ground-truthing the results as part of each iteration if possible so you can refine your results. Chris Donohue, GISP ... View more

A general suggestion - maybe try loading all your shapefiles into a File Geodatabase, then work against that.  I suggest this as you may be running up against a naming limit having to do with not just the filename but the path.  For example, if the combination of the filename and the path gets close to 255 characters, it can bomb out (even though the specs say it should work fine). General information on Shapefiles Geoprocessing considerations for shapefile output Chris Donohue, GISP ... View more

A possibility - this site apparently has a font-recognition process. WhatTheFont WhatTheFont! « MyFonts WhatTheFont: Recognize the Font from any Image Chris Donohue, GISP ... View more

Glad you found a solution.  It's an interesting challenge. For others reading this, here's a link that describes the limitations of displaying data from Modelbuilder: Note:  Add To Display has no effect outside ModelBuilder. When running a model tool from its dialog box or the Python window, the Add To Display setting will not be honored. To add model data variables to the display when running the model from its dialog box or the Python window, make the data variable a model parameter, then enable the Add results of geoprocessing operations to the display option from  the Standard toolbar: Geoprocessing > Geoprocessing Options > Add results of geoprocessing operations to the display. Displaying Model Data ArcGIS Help (10.2, 10.2.1, and 10.2.2) Chris Donohue, GISP ... View more