Latest Contributions by ChrisDonohue__GISP

Not sure if you found an answer already, but I'll throw out some ideas in case you haven't: 1.  The most common reason for this to occur is that the street linework is not truly connected from a Network Analyst perspective.  It can look fine visually, but will have tiny disconnects that prevent the passage from one edge to another.  Run Topology with rules to check the linework and then edit the data to resolve this. 2.  Another reason could be that the attributes that Network Analyst checks to determine if a route can be used are set incorrectly.  For example, the "oneway" attribute may be set up incorrectly. Chris Donohue, GISP ... View more

Some questions to help troubleshoot: 1. Which software are you using to do the import process?  For example, are you using a Tool or instead "Add Data" in ArcMap.  Also, what version is the software?  2. What are you importing it into?  Right into ArcMap and viewing it there, still as a .csv?  Into a geodatabase? Or creating some other new file? Chris Donohue, GISP ... View more

What is likely going on is that some of your spatial data have incomplete spatial references.  While ArcMap has the capability to "project on the fly", it can only do so effectively if all the data have full spatial references. For example, you mention that CAD data is being viewed.  It is fairly common for CAD files to have a coordinate system that matches the one commonly used for an area, but to lack a projection.  Because the coordinates are the same as other data, it loosely lines up with the other data that have the same coodinate system.  But because it lacks the projection, it will be off by a bit. I'd suggest checking the spatial reference information for all your data layers and for ArcMap itself.  ArcMap needs to be checked as the Data Frame inherits the spatial information of the first data layer you loaded into it. ArcMap Right-click on the "Layers" heading (Data Frame) in the Table of Contents. Right-click, then choose Properties Then choose the Coordinates tab and see what spatial reference is set. For Data layers loaded into ArcMap Right-click on the layer in the Table of Contents Choose Properties Click on the Source tab Scroll down to see the spatial reference information. It can be OK for their to be different spatial reference information, as long as the layers have complete spatial reference information.  So if you have data in UTM and State Plane, that can be OK. What are Map Projections? ArcGIS Help (10.2, 10.2.1, and 10.2.2) Specifying a Coordinate system IArcGIS Help (10.2, 10.2.1, and 10.2.2) Chris Donohue, GISP ... View more

Some questions to help clarify this: 1.  Is the issue technical - i.e. the analysis bogs down/software crashes due to the large amount of records? 2.  Is the issue that their are many resulting Near records and uncertainty on how to query these results down to get the final answer? Chris Donohue, GISP ... View more

One of these Excel workflows may do the trick: Count unique values among duplicates Chris Donohue, GISP ... View more

An alternative workflow that may work better than doing many selections: 1.  Open the attribute table for your streets 2.  Right-click on the "FULLNAME" field heading and choose "Sort Ascending" 3.  Scroll to street of interest and select it. 4.  Use the "Zoom to Selected" tool. 5.  Return to step 3 to repeat for the next street. Chris Donohue, GISP ... View more

One potential solution for corrupted files is to run the Check Geometry and Repair Geometry tools. Checking and Repairing Geometries ArcGIS Help 10.1 Also, if it turns out your shapefiles are damaged beyond hope, you may be able to restore the files from backup.  For example, if you have Windows 7 you may be able to use the "Previous Versions" function to recover the files. In Windows Explorer, Right-click on folder, Properties, Previous Versions tab, Select, Restore. Warning - make a copy your data to another location before trying this.  Also, realize it will restore everything in the folder and all files and folders coming off that folder, so take this into consideration before attempting this particular process. Chris Donohue, GISP ​ ... View more

I'd start by checking the Data Frames to see if they are in the same Coordinate Systems (so therefore same expected units).  It is possible the Data Frames are in different units, which could account for the unexpected differences.  The differing coordinate systems can come about as the Data Frame inherits the coordinate system of the first layer added to it (and typically inset maps have less layers than the main map), so a different "first" layer may have been added when setting it up. Another check is to look at the Scale Bar Properties themselves and see if the units are correct.  It is quite possible the units were mis-set, so it is good to check this.  For example, the data frame may have a linear unit of feet, but the Scale Bar "Division Units" is set to meters and the "Label" still is set to read "feet". Chris Donohue, GISP ... View more

The link Jake posted is helpful.  One other issue to consider that is not directly mentioned but may be a factor is financial.  If your organization does not currently have an enterprise geodatabase/ArcSDE, there is an additional cost consideration in purchasing it. Also, some time and effort (and therefore often money) will be needed to set it up and maintain it.  Something else to add to the mix as you evaluate your needs.... Chris Donohue, GISP ... View more

One way to do this is to create a Layer File (.lyr), then apply it to both. Chris Donohue, GISP ... View more

Can you post a portion of your data?  That would help in troubleshooting it. Chris Donohue, GISP ... View more

Another suggestion that others have mentioned as a way to quickly check a network dataset in problem areas where there does not seem to be a route found is to use the "Create a Service Area" function in Network Analyst.  When doing so, intentionally put in a very large distance so it will try to create a Service Area for the whole dataset.  Also, be sure to check "on" the option for "Generate Lines". Then run it.  After it is run, first check the overall Service Area to see if it matches the expectation.  Disconnects of the data will result in a road network without a Service Area polygon.  Then zoom in to these spots and use the Generated Lines to see where the "break" is.  Note that the break may be due to either a disconnect and/or a Network-specific Attribute set wrong.  For an example of the latter, "Oneway" set for a one-way street, but in the wrong direction, so the routing cannot happen. Chris Donohue, GISP ... View more