Latest Contributions by MelindaMorang

‎07-25-2014

Hmm...then I'm not sure what's going on. Are you able to share your data? If so, I could take a look.

‎07-25-2014

Hi Sheldon. From your descriptions, it really sounds like the network edge is restricted. - When you use a small search tolerance, the point can't find a non-restricted network element to locate on, so it shows up as unlocated. - When you increase the search tolerance a lot, it finds another network edge that isn't restricted and locates on that network edge as well. Note that the point always shows up in the location of the original input no matter which network edge it's getting located on. The point doesn't move to show you that it located on a different edge. - When you uncheck Exclude restricted portions of the network, it is now able to locate on the restricted edge that it's right next to, so it still works with the small search tolerance. Try using the Network Identify tool (on the Network Analyst toolbar). Click on that network edge that's causing problems. You should be able to see the restriction values for it for any restrictions in your network. There must be something happening that you didn't expect.

‎07-03-2014

First, is there a compelling reason that the properties (houses) have to be included as feature in the network? Will these houses simply be used as origins, destinations, stops, facilities, etc. in your analyses? If so, you don't need to build them into the network. When you load them as locations into your NA layers (Service Area, Route, etc.), the layer will automatically locate the points on the closest network edge. You can adjust the location settings as needed. The actual points don't need to be part of the network. If you DO need all those properties to be junctions in the network, here's how you can do it (you need the at least the Standard (ArcEditor) license for this method): 1) Create a copy of your 300,000 houses that aren't attached to the network. 2) Use the Snap tool (http://resources.arcgis.com/en/help/main/10.2/index.html#//001v00000007000000) on the copy of the houses to snap them to the closest street feature. 3) Use the Points to Line tool (http://resources.arcgis.com/en/help/main/10.2/index.html#//00170000003s000000) to create a straight line between the original house location and the snapped house location. Make sure to match up the points by ID so you get one line between each pair. 4) Include this line feature class in your network. You can set up your impedance attribute to calculate the travel time based on the line length or whatever else you want. 5) You need to ensure that the street feature class has a vertex or endpoint at the location of the snapped house location or else the network won't connect in that location. The easiest thing to do is to run the Integrate tool (http://resources.arcgis.com/en/help/main/10.2/index.html#//00170000002s000000) to create a vertex on the streets in the location of the snapped houses. This will create vertices in those locations. Then, when setting up your network, make sure you include the snapped houses as junctions, and use Override as the connectivity policy for the snapped houses.

‎07-02-2014

Are you trying to use the same tutorial and tutorial data on both your 9.3 machine and your 10.1 machine? I wouldn't expect that to work. Various improvements to network datasets have been made throughout the years, so the procedures and data used for the 10.1 tutorial might not work in 9.3. The 9.3 version of the tutorial is here: http://webhelp.esri.com/ArcGISdesktop/9.3/index.cfm?TopicName=Tutorials ArcGIS 9.3 is very old software. You should upgrade if possible.

‎07-02-2014

Is there some reason that barriers won't work for this application? Barriers are point, line, or polygon features that can be added to the analysis in order to simulate impassible roads due to accidents, construction, floods, etc. They do not modify the underlying network but simply affect the results of an individual analysis. The barrier features can be edited prior to the analysis. http://resources.arcgis.com/en/help/main/10.2/index.html#/Barriers/004700000056000000/

‎07-01-2014

When you create a network dataset, it automatically creates a point feature class containing system junctions indicating the locations where edges in the network connect. Did you, by any chance, delete the junctions feature class intentionally or by accident? Otherwise, as Joe suggested, it might be some kind of error reading or writing to the geodatabase. Have you tried doing the tutorial more than once, and did you get the same error each time?

‎06-25-2014

You can set up an impedance attribute on your network, and you can calculate that impedance differently for each input feature class (roads, rails, etc.). To do this, you need to understand how network attributes and evaluators work: About network attributes: http://resources.arcgis.com/en/help/main/10.2/index.html#/Understanding_network_attributes/00470000000m000000/ About evaluators: http://resources.arcgis.com/en/help/main/10.2/index.html#//00470000000n000000

‎06-16-2014

The best way to do this is to use the Copy Traversed Source Features tool. It will create a feature class of the network edges that were used to create your closest facility routes, and you can export the names from that.

‎06-16-2014

The best thing for you to do is to start with our Network Analyst tutorials, available here: http://resources.arcgis.com/en/help/main/10.2/index.html#//00470000005r000000

‎06-13-2014

Here are a few ideas: 1) Create a rail-only restriction and a road-only restriction on your network. If you know in advance where your input points are located (on the roads, on the rails, or on both), you can turn on or off the appropriate restrictions before running the analysis. 2) On the features that connect the rail lines with the road lines, invoke a large impedance penalty to discourage transitions between the two. This way, it's very likely that two points on roads will use only roads for the route, two points on rails will use only rails to connect, but a point on the road and another point on the rail will be forced to make a transition somewhere even though it's penalized.

‎06-13-2014

Notice in the Network Analyst window under Stops how one of your stops has a red symbol next to it. That means it didn't get located on the network. So, when you dropped the stop on the map, it wasn't able to snap to one of the streets on your network dataset. Consequently, you can't solve a Route that goes to that point, because the network doesn't know where the point is. There are a few reasons why your stop might not locate properly on the network: - The stop isn't close enough to a network edge - You altered your network location settings in such a way that the point couldn't locate on that type of network edge I recommend you take a look at these pages in our documentation: - http://resources.arcgis.com/en/help/main/10.2/index.html#//00470000003p000000 - http://resources.arcgis.com/en/help/main/10.2/index.html#//00470000003n000000#GUID-9722833A-C61D-4E66-87CD-796A8A7231A1 - http://resources.arcgis.com/en/help/main/10.2/index.html#//004700000045000000

‎06-11-2014

Hi! If you have an MXD with several layer files saved in it already, you can access those layer files and put them into a list as follows: #Get a list of all the layers in the map document mxd = arcpy.mapping.MapDocument(mxd_path) lyrs = arcpy.mapping.ListLayers(mxd) #Filter the list to obtain only the network analyst layers na_layers = [lyr for lyr in lyrs if lyr.isNetworkAnalystLayer] You can then iterate through this list when generating directions. If you're doing this from the python window in ArcMap instead of a standalone script, replace mxd_path in the script above with "CURRENT".

‎06-06-2014

Can you post a screenshot of the evaluators for your cost attribute? It sounds like you've either converted units incorrectly, or else some of your network edges have 0 impedance.

‎06-05-2014

Hi Fiona. Can you give us more details? What type of network analysis are you doing (Route, Service Area, etc)? Did you create the network dataset yourself? Is it a file geodatabase network, shapefile, SDE, etc? Can you post a screenshot of the error message? All of these things will help us figure it out.

‎06-04-2014

Yes, you can do this! After you create your Route layer, open the layer properties, go to the Analysis Settings tab, and check true the Reorder Stops to Find Optimal Route option. By default, the Route uses the input order of the stops as the order, but by checking this option true, you can have it rearrange the order to find the most efficient route, which sounds like what you want. See http://resources.arcgis.com/en/help/main/10.2/index.html#//004700000045000000 for more information.

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by MelindaMorang

Re: Inconsistent behavior in Network Analyst when adding origins

Re: Inconsistent behavior in Network Analyst when adding origins

Re: Connecting House Points to City Street Network

Re: A Problem in creating a new network dataset

Re: Adding impediments dynamically to a Network Dataset

Re: A Problem in creating a new network dataset

Re: multimodal transport switches

Re: Export Route with Street names

Re: multimodal transport switches

Re: multimodal transport switches

Re: Network Analyst won't Solve Shortest Route

Re: Directions using arcpy

Re: speed problem in OD-Matrix

Re: Error: Cannot read from network table.

Re: Routing Monthly Service Points

Re: TransitNetwork for multimodal analysis?

Re: Network analyst public transit tool Prepare ti...

Re: Network analyst public transit tool Prepare ti...

Re: How do I fill in the blank areas where streets...

Re: Route Solver - Add Locations - Convert Model B...