Latest Contributions by MelindaMorang

Why won't the method described on the other thread work?  Just create multiple points for each park corresponding to each road intersection with the park and use those as the facilities. ... View more

Yes, put the stops and the snapped stops in the same feature class temporarily so you can run Points to Line.  Use the unique ID of the stops for the Line Field parameter (like if you have a stop id value or something).  This makes it so an individual line will be drawn between the stop's original position and its snapped position. ... View more

Hello, Jennifer. For Problem 2: You should be able to set up the field mapping the way you want if you feed your model a default input feature class.  So, go ahead and give it some origins and destinations as input, set up the field mapping the way you want it, but then leave the input origins and destinations as model parameters.  This way, you'll still be able to choose a different feature class as input.  That said, if the input has a field called Name, it will automatically map to the Name property in the Origins and Destinations anyway, so you don't need to set up anything special.  If you're trying to map a different field, then you do need to set up field mapping.  I'm not actually not sure if the tool will error out if the input doesn't have the appropriate fields.  You might need to use python instead of Model Builder if you want validation that complex. For Problem 3: "Add to Display" only works when you run the model from the Model Builder canvas.  It's mostly a debugging tool.  If you want your output to be added to the map when you run the model as a tool, right-click the output and make it a parameter, just as you did for input parameters.  It becomes a derived output and will be added to the map.  I know, it's a little strange. ... View more

That's correct.  GetNAClassNames() just returns the string names of the sublayers.  In your case, you need the layer object, which is what ListLayers gives you.  If you wanted your script to be usable in localized versions of ArcGIS where the layer names might be called something in a different language, then you would want to use GetNAClassNames() to find the sublayer name in that language and pass that value into your code rather than hard-wiring "orders".  But if you're the only one running this script, then hard-wiring "orders" should be fine. ... View more

Your network dataset needs some source feature classes.  For example, you need a feature class of streets.  You need to put that feature class into the feature dataset where you want to create the network.  So your first screenshot above is perfect.  After you do that, copy your streets feature class into the feature dataset.  Then, do what you're doing in your second screenshot. ... View more

Hello, Christopher.  I'm not sure how much experience you have in creating network datasets, so please feel free to ask if you need any clarification on any of the following.  Multimodal networks tend to be pretty complicated. But before I continue, I'll just mention that there is a set of tools you can download to take care of a lot of this automatically if you have GTFS public transit data: http://www.arcgis.com/home/item.html?id=0fa52a75d9ba4abcad6b88bb6285fae1 To answer your question, if you want the bus stops to be incorporated as part of your network, you need to do a couple of things: 1) You need to make sure the geometries are connected.  You can use the Snap geoprocessing tool to snap the transit stops to the street features.  But if you need to maintain the transit stops in their original locations (for instance, because they are connecting the transit lines), then it would be best to create a copy of the stops first and snap the copy.  You can then use the Points to Line geoprocessing tool to generate a connector line between the original stop location and the new stop location.  The Points to Line tool can make use of the stop's ID to generate an individual line between each pair of stops with the same ID (the original and the snapped version). 2) In order for your stops and connector lines to actually be connected in the network dataset, you need to add vertices to the street features at the locations of connection.  You can do this automatically by running the Integrate tool with 0 xy tolerance.  Make a back-up copy of your data first because Integrate can do some scary and non-reversible things. 3) In addition to the above, you need to include the stops, snapped stops, and connector lines into your network dataset as network data sources.  Use a connectivity policy of Override for your snapped stops if you have End Point connectivity for your streets.  This ensures that the connector lines connect to the streets at the vertices you created and don't have to snap to end points. ... View more

Hello Jonathan.  You need to create the feature dataset inside the file geodatabase (kind of like creating a subfolder inside a folder).  Then, move all the feature classes you want to use with your network inside the feature dataset.  You should then be able to create your network inside the feature dataset. ... View more

You would enter the roads in the input features box.  It will create a vertex anywhere that the road features intersect themselves. Make a backup copy of your data first... ... View more

Hello, Robert. First, here is the link to the 10.3 version of the tutorial you were following (it seems like you were using the old 10.0 version): Exercise 1: Creating a network dataset—Help | ArcGIS for Desktop The information is mostly the same, but there are a few changes. Regarding elevation fields, unless your data is already 3D, you probably don't want to use actual Z values for connectivity.  Instead, you will use Z-levels to model bridges, overpasses, and tunnels. Please read this doc page to get a better handle on what network connectivity is and how it works: Understanding connectivity—Help | ArcGIS for Desktop Basically, there are a couple of ways to control whether or not network edges actually connect to one another.  There is a whole section on that page explaining Z-levels. ... View more

Hello, William.  You're on the right track, but your syntax isn't quite right.  You need to use listLayers more like this: layer_object.listLayers(polygons_layer_name)[0] Check out the code sample on this page for something closer to what you're trying to do: Make Service Area Analysis Layer—ArcGIS Pro | ArcGIS for Desktop ... View more

Well...your Service Area analysis did a pretty good job of identifying roads that weren't connected. If you're using Any Vertex connectivity, you can automatically add vertices at locations where roads cross using the Integrate tool with 0 XY tolerance.  Make a backup copy of your data first... If you're using End Point connectivity, you'll have to split features at intersection points, which can be done.  However, if you have fields in your data like address ranges or travel times, keep in mind that these could get messed up if you start splitting features.  You'll need to make sure that your geodatabase domains are set up with the appropriate merge/split policies. ... View more

I see what's happening here.  When you run a Network Analysis, your input points have to "locate" on the network, meaning they snap to the closest network edge and the snapped location is considered to be the start or end point of the analysis. In your image 1, the origin is snapping to the western connector.  Since you have a script evaluator preventing turns from one connector to another, it can't travel from its start location at the end of the western connector to the eastern connector the way you want, so it's forced to used the western connector.  In image 2, it happily travels from the western connector to the eastern connector because there's nothing to prevent it. This problem can be worked around.  You can tell your stops (origins and destinations) not to "locate" on edges but to instead locate on junctions.  If it's located on the junction between the connector lines, I think it should be able to travel down any of them. To set this up, open your NA layer properties, and go to the Network Locations tab.  You should see a box that looks something like the image below.  Uncheck the boxes for your streets or connectors, and check on the Shape box for junctions. ... View more

Hello, Peter.  Yes, you will need to do some extra work to make sure that your two street datasets actually connect properly to one another.  In order for streets to actually be connected in a network dataset (ie, it's possible to drive from one to another), they must have either endpoints or vertices at the locations where they touch, depending on your network's connectivity policy.  If they simply cross over one another without vertices or endpoints, they will not be considered connected in a network.  It will be treated more like an overpass, where no connection is possible.  You can learn more about network dataset connectivity here: Understanding connectivity—Help | ArcGIS for Desktop One of the easiest ways to ensure connectivity is to set your connectivity policy to Any Vertex and to use the Integrate tool with an XY tolerance of 0.  Integrate is sort of a scary tool that edits your input features in unpredictable ways, but the 0 XY tolerance ensures that nothing will actually change shapes.  It will just add vertices at the points of intersection.  It also honors the selection set, so you could first select only the small number of features that you're trying to connect before running the tool. ... View more