Latest Contributions by MelindaMorang

Okay, thanks for the additional details.  That helps me narrow in on the problem. The first problem you mentioned was that intersection junctions were missing in your network.  It sounds like that's the real problem, and any problems with adding a junction feature class to your network are secondary problems with something you're trying to do to correct the first.  Is that right? The most common issue when creating a network with manually digitized roads relates to connectivity.  There are a couple of geometry problems and network dataset settings that can cause roads to be disconnected at intersections where they should connect: Geometry problems - The digitized streets aren't snapped together at intersections.  There are little gaps and dangles, and the streets don't meet up neatly and cleanly at the intersection points.  To correct this, you need to edit the street features. No vertices or end points at intersections - The digitized streets are long lines that cross other lines, but they don't have vertices or end points at the locations where they intersect.  These are treated as underpasses/overpasses instead of intersections.  You can run the Integrate tool to generate vertices at the intersection points (but make a backup copy of your data first because Integrate can mangle it). Incorrect connectivity policy. The streets aren't connected at intersections because you're using End Point connectivity, but the street features don't end at intersections (they just have vertices).  You can fix this by switching to Any Vertex connectivity.  Documentation for connectivity: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/understanding-connectivity.htm When you build the network dataset, vertices should automatically be created at connected intersections.  If no vertex was connected, it means that the geometry and/or network dataset settings do not see that intersection as properly connected. To help you debug the problem, try using the Explore Network tool to click on the street features near the problem area to see how they're connected (or disconnected).  Documentation for Explore Network: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/explore-network.htm  If none of that solves your original problem and you still want to include your own junctions in the network, you should be able to select a point feature class as a source feature class of the network in the Create Network Dataset tool or manually in the network dataset properties.  The point feature class must be in the network's feature dataset. ... View more

Hello.  Are you using a network dataset you created yourself or got from your organization (as opposed to Esri Streetmap Premium or ArcGIS Online service)?  If so, the problem is probably with the network dataset.  Here are some common problems: Incorrect connectivity policy. The streets aren't connected at intersections because you're using End Point connectivity, but the street features don't end at intersections.  You can fix this by switching to Any Vertex connectivity.  Documentation for connectivity: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/understanding-connectivity.htm The cost attribute isn't configured correctly.  It may not be calculating distance correctly, the units may be wrong, etc.  Documentation for cost attributes: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/cost-attributes.htm You could have a restriction attribute preventing travel on that side street where the two disconnected points are located. You could have some kind of turn restriction preventing travel around that corner To help you debug the problem, try using the Explore Network tool to click on the street features near the problem area to see how they're connected (or disconnected), what restrictions are applied, and how the cost attributes are being calculated.  Documentation for Explore Network: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/explore-network.htm  ... View more

I think you're on the right track with your testing so far.  To me, it looks like it's probably some sort of connectivity problem.  It might be a topology issues  (gaps, dangles, poorly connected streets).  Or it might just be something you can fix easily by adjusting the network dataset's connectivity policy from End Point to Any Vertex. If your street features are split at every intersection (they intersect at endpoints of features), then End Point connectivity (the default) is appropriate.  However, if your street features are long and intersect with many other features at junctions instead of endpoints, then you should instead use Any Vertex connectivity. Here's some documentation about connectivity: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/understanding-connectivity.htm If that doesn't fix it, you might gain some insights by working through this set of Tasks intended to help local governments (mostly in the US) create network datasets for their cities using street centerlines: https://www.arcgis.com/home/item.html?id=9e321cf94d2b43b991cc5109189b2c26.  I'm not sure if your input data has all the necessary attributes, but you might still learn something from the Tasks, since the steps guide you through some data quality, validation, and editing workflows. ... View more