Latest Contributions by MelindaMorang

Hi John.  I can't tell from your question whether you have your own network dataset or you're using the Esri-provided Streetmap Premium or ArcGIS Online routing service.  The answer to your question depends on which of those you're using. If you have your own network dataset, then getting better results is likely a matter of improving the way turns are modeled in your network.  You can use global turns to penalize, for example, all left turns.  You can use a turn feature class to forbid or penalize specific turns at specific intersections.  Here's some documentation on that: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/turns-in-the-network-dataset.htm (with links to more detailed documentation on turn feature classes and global turns). If you're using Streetmap Premium or the ArcGIS Online routing service, you don't have the ability to configure the network dataset.  If you're seeing unrealistic solutions, please feel free to respond here (or send me a private message) with an example of the input points and the travel mode you're using.  We'd be happy to investigate a couple of cases where the solution is bad, and we can see if it might be a problem with our data. Note that for either your own network dataset or Streetmap Premium / AGOL, you can configure your own travel mode for the analysis.  You can choose which restrictions to use and what U-turn policy to employ.  Some tweaking here may be helpful.  Here's some documentation about using travel modes: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/travel-modes-in-network-analysis-layers.htm  ... View more

There's not enough information here to diagnose the problem.  That "Cannot connect to database" error usually appears when either something is terribly wrong or there's a bug in Pro.  Technically users should never see that!  Are you able to share your data and template (send me a private message if you wish to share privately)?  Also, what version of ArcGIS Pro are you running? ... View more

Yes, unfortunately, this feature does not exist in Pro. The best you can do is run the XY Table To Point tool using the SnapX and SnapY fields from the network analysis layer sublayer you're looking at (like Route Stops).  This will create a separate feature class showing the network locations of each original point. You an also use the Snap To Network option on the Add Locations tool when adding your input locations to the network analysis layer's sublayer.  This will move them from their original location to the network location, with optionally some offset. ... View more

To respond specifically to this question: "I am curious if the Make  a route layer needs to be imported into my enterprise Geodatabase as well then the route can be created. If so, how do you Make a Route Analysis Layer that is within the Enterprise Geodatabase." No, Pro doesn't support creating a route analysis layer whose sublayer data is in an Enterprise geodatabase. The workflow you're using now is the correct workflow, which is why I suspect a problem with the network. ... View more

Your workflow seems fine, and you should be able to create a Route layer using a network in an Enterprise gdb.  I suspect something is wrong with the network.  When you ran Build Network, did you get a warning about build errors?  If so, you should inspect the build errors reported (it's in a text file, and the warning message gives you the filepath for the text file).  My guess is something caused awful problems when building the network, resulting in it having no valid edges. ... View more

Since your trails are in a separate feature class, as mentioned above, you could construct a single cost attribute that calculates the travel time on roads using driving speeds and on trails using walking speeds.  So technically you could get this to work.  You just need to set up the evaluators for your cost attribute correctly. Documentation for cost attributes: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/cost-attributes.htm  Documentation for evaluators: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/types-of-evaluators-used-by-a-network.htm The limitation with this model is that the solver can't track whether or not the traveler currently has their car.  So, you could potentially get a route where the traveler drives to a trailhead, walks on the trail, emerges at a different point, and continues driving, even though they left their car at the other end of the trail.  But if you're just trying to find the best way to get to some point deep in the woods from your headquarters or something like that, it shouldn't be an issue. ... View more

In general, no, that's not possible in the same analysis. If you're creating your own network dataset and you have a separate source feature class for the trails, you could configure a travel time cost attribute to calculate the travel time differently for the streets vs  the trails.  However, this would preclude a traveler from walking on streets (because as soon as they're on streets, the travel time assumes driving).  Maybe that's fine for your purposes. ... View more

I don't think group connectivity is the right way to approach this.  The typical way to handle overpasses and underpasses is to use elevation fields.  You add two fields to your data, like FZLEV and TZLEV, which assign a numerical value (or null) to the two ends of each feature (the from and to ends, in the direction of digitization).  In the locations of overpasses and underpasses, you make sure the FZLEV and TZLEV values match up.  For example, the two endpoints touching in the underpass have a value of 0, and the two endpoints touching in the overpass have a value of 1.  The network will treat the overpass and underpass as disconnected from each other because the elevation fields are different. Documentation: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/understanding-connectivity.htm#GUID-915E20F5-8309-4837-8EF4-8A5DC7A8D2F2 I've seen some of your other posts, and it sounds like you're trying to create a network dataset from street centerlines and having some problems getting it to work.  This downloadable set of Pro Tasks is aimed at helping local governments create network datasets from their street centerlines and might help you get started: https://www.arcgis.com/home/item.html?id=9e321cf94d2b43b991cc5109189b2c26  ... View more

Unfortunately, there's no way to limit the data.  The GTFS To Public Transit Data Model tool will include all data that's in the input GTFS dataset.  The extra data shouldn't really cause any problems for your analysis, though. ... View more

Yes, you could also strategically use stops to force a route to use the new road. If your goal is to see how the new road impacts travel times from origins to destinations, though, it would be better to NOT force the solver to use the new road.  If you want an accurate picture of whether the new road is valuable, you can check the results to see whether it's been chosen as the optimal path from A to B.  If not, then the new road isn't actually improving travel times. ... View more

I think what you're asking is how to force a route analysis to use the new street you added to your network dataset.  Is that correct? The Route solver will always find the least-cost path between points, meaning that it minimizes the cost attribute used by the travel mode.  There's no option to force it to use a particular road.  It will use the road if doing so minimizes the overall travel cost. However, you could add barriers to the route to make other potential routes through the network impossible and thereby force the route to use the new road. ... View more

Unfortunately, this still isn't possible. That post from 2019 was about a prototype tool for ArcMap called Add GTFS To a Network Dataset, which is now deprecated and has been replaced by functionality in core ArcGIS Pro (see tutorial).  However, the same limitations to the Network Analyst solvers apply which prevents us from separately constraining the walk time from the overall travel time. Other users have asked for this functionality, and we're aware of the need for it.  Unfortunately, it's a substantial amount of work that just hasn't been prioritized yet.  If you'd like, you can contact Esri Support to log an official enhancement request for this functionality.  Tell the Support analyst to reference the existing enhancement request number ENH-000154968 ("Allow the Public Transit Evaluator in Network Analyst to limit a traveler's walking time or distance separately from the overall travel time.") and add your case to it.  Adding more cases through this official channel can help us prioritize this work in the future. With all that said, the hacky workaround for Service Area lines from the 2019 post still works, though it might not be quite the output you're looking for. ... View more

Do you see this warning flag when you open the network dataset properties?   If you see that, then you need to first remove from the map the network dataset and any network analysis layers that reference it.  Certain properties of the network aren't editable when the network is open in the map. ... View more

Yes, unfortunately, this makes sense to me.  Enterprise is based on the ArcGIS Pro codebase, and Enterprise 11.1 used the Pro 3.1 codebase (I think).  At any rate, your version of Enterprise is older and doesn't have the fix we made in Pro 3.4.  You would have to update to Enterprise 11.4. ... View more