Latest Contributions by JaySandhu

When you use the Dissolve Tool, rather than using Min/Max statistics, try First and Last as follows: Perhaps this will give you the expected results. Jay Sandhu ... View more

Have you done a full rebuild? Try adding a new cost attribute to the network dataset, save the changes and then remove it. Rebuild the network and it should be a full rebuild. If the problem still persists, I suggest that you contact Esri Tech Support and share your data so that they can help figure out what could be going on. Jay Sandhu ... View more

This data does not seem to have any problems. It is likely that packaging the data caused a rebuild of the network and the connectivity has been fixed. Perhaps you can re-build your network and see if that clears it up.  Jay Sandhu ... View more

I guess I do not understand your issue. Where are you seeing the split multiple segments. How are they being generated. What do you need to accomplish? Perhaps some more details may help.  Jay Sandhu ... View more

You run the dissolve tool on the output of the solve. Not on the input network dataset. Where do you see the multiple SourceOIDs that make up the route? It is in the routeedges feature class in the data you uploaded. So that is what you dissolve. Jay Sandhu ... View more

Are there any Z Levels defined? That is, on the Network Dataset property page for Source Settings, there is a Vertical Connectivity tab and it may have some elevation fields defined. If not, can you share the data or part of the data where you see this problem? You can zoom to the area you want share and then use the Share ribbon option of Mobile Map and then on the pane make sure to write to a local file and make sure the current display extent is checked on. This will create a small MMPK you can upload. Jay Sandhu ... View more

There can be many reasons why you could get this situation. The first thing to check is if the source line features are polyline Z and could it be the three edges meeting at that X,Y location have different Z coordinates. I am not sure when you say elevation is 0 if it was for the 3d coordinate or for the Z Levels that can also cause this. Or there can be a connectivity group policy in place. You can add the network dataset to Pro and use the Explore Network tool (on the network dataset/data layer ribbon) and examine those edges to see if there is some you can figure out causing the two junctions. Jay Sandhu ... View more

The source features when made into a network dataset may get split into many features based on the connectivity policy to deal with other crossing roads. The route solve will return a single line for the route and then the Copy Traversed Source Features tool can return back the underlying edges. And in this case it will return back all the pieces of an original feature with the from/to positions. That is the expected result as that is what is contained in the network dataset. You could run the Dissolve tool on the RouteEdges, dissolving on the SourceOID to return back one edge per SourceOID. You will probably want to uncheck the Return Multipart and check on the Unsplit Lines options when you use this tool. Jay Sandhu ... View more

You probably first need to add a new cost attribute called TravelTime and have it load from the FT and TF_Minutes field. Then you can add this cost attribute to a travel mode. And make sure to build the network dataset after you add a new cost attribute. I suggest you look at the steps in the Add Cost section of this tutorial: Create a network dataset—ArcGIS Pro | Documentation Jay Sandhu  ... View more

Looks like you need a linear referencing solution and NOT a routing solution. You need to turn your Route95 line features into linearly referenced routes with appropriate calibrations. Then your point features with the start and end measures are really an Event table with linear events based on these linearly referenced routes. For example, the first point, has a route name: R-VA IS00095NB and From Measure: 89.618 and To Measure 91.943 To return back a line feature between these two measure values for multiple records, you can use the Locate Feature Along Route tool. But for that to work, you need to provide the Route95 set up as linearly referenced routes with that measure units so positions like 89.618 to 91.943 can be figured out. Locate Features Along Routes (Linear Referencing)—ArcGIS Pro | Documentation You can use the Create Routes tool to turn the Route95 lines into appropriate routes. But I am not sure what measure values to use to calibrate them for your measure values. Tool info: Create Routes (Linear Referencing)—ArcGIS Pro | Documentation Jay Sandhu ... View more

If you have your own road line features, you can create a network dataset on them. Then you can create a Route analysis layer, add your start and end points as Stops and solve a shortest path route. This will return you back a line feature of the shortest path. If that is all you need then you are done. If you need the individual original street features that make up that route then you run the GP tool Copy Traversed Source Features. Output from Copy Traversed Source Features—ArcGIS Pro | Documentation If this is the work flow you want to follow, I would suggest going through couple of the Network Analyst tutorials to get you started.  Especially: Create a network dataset—ArcGIS Pro | Documentation and Find the shortest path and generate directions with Route—ArcGIS Pro | Documentation Regards, Jay Sandhu ... View more

It is hard to say what may be going on. But let's start with looking at the properties of your network dataset in the Catalog pane. On the traffic attributes you should be able to see if you have travel modes like so:   If you do see your expected travel modes then I suggest starting a new project in Pro, adding your network dataset and then creating the OD Cost Matrix layer. Does the ribbon at this point show you your travel modes? If yes, then you can continue with loading your locations. If not, then we have to diagnose it more on what could be going on. Regards, Jay Sandhu ... View more