Latest Contributions by MelindaMorang

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

Great!  I'm so glad you found a solution.  The disadvantage of script evaluators is that they increase solve time because they have be calculated at solve time (as opposed to being baked into the network so the values can just be looked up).  But if speed isn't your main concern, this should hopefully work fine for you. ... View more

Hi Russ.  I understand the problem, and it's a tricky one. I have a couple of ideas, none of which are ideal. Idea 1: Use Point Barriers You could make your census block centroids into point barriers to prevent travel across your virtual lines with 0 cost.  However, the problem is dealing with your origin and destination centroids.  If they were to locate directly on top of the point barrier at the same location, then they would not be reachable at all.  If the origin or destination located on one of your virtual connector lines slightly offset from the point barrier, then it would only be able to use that single exit from the centroid to connect to the road network, so that doesn't work either.  However, you might be able to make this work if you calculate routes one at a time and simply remove the point barriers at the origin and destination location for that route and leave the others.  This could be automated, but if you're doing every block to every other block, the calculation might take a really long time compared to just running a single OD Cost Matrix analysis. Idea 2: Don't use centroids The cleanest solution might be to simply not use the centroids but to instead use the intersections with the surrounding streets as your origins and destinations.  By giving your centroid connectors 0 cost, you're effectively doing this anyway.  The disadvantage here is that you will have a bunch of origins and a bunch of destinations associated with each centroid, and you would end up with a bunch of routes instead of just one.  But, if you tracked the census block IDs, with a little post-processing, you could just delete all but the fastest route between unique pairs of blocks. Idea 3: Use a Script Evaluator for default turn behavior I haven't experimented with this idea, but you might be able to come up with a solution that works using a Script Evaluator for the default turn values on your cost attribute.  For the cost attribute you're using for your analysis, you can open up the Evaluators dialog from the network dataset properties.  On the Default Values tab, there's a place where you can set the default behavior for all turns (transitions from one edge to another).  Here, you could use a script evaluator to allow all turns except for transitions from one virtual edge to another. Learn more about script evaluators here: Types of evaluators used by a network—Help | ArcGIS for Desktop As I said, this is a tough problem.  I hope this gives you a few ideas.  If you come up with a good solution, please post it here so others can see! ... View more

That code looks like it should work, in theory.  Is your "PRMT_ID" field a string field?  I'm actually not sure how the field mapping would behave if you mapped a field to Name that was, say, an integer. ... View more

Dan is correct that the Curb Approach settings are the way to control which side of the road a vehicle can stop on.  However, at this time, Curb Approach settings can be configured only for the orders, not for the vehicles. ... View more

Hello, Claudio.  There is a user's guide included in the download of that tool which should provide instructions for how to use it.  You can also access the latest version of the user's guide here: http://transit.melindamorang.com/UsersGuides/DisplayGTFSRouteShapes/DisplayGTFSRouteShapes_UsersGuide.html If that doesn't solve your problem, please provide more details about the trouble you are experiencing. ... View more