Latest Contributions by MelindaMorang

Thanks a lot for your help, it works. ... View more

Hmm, using the transit-enabled network for walking only with restrictions like you're using or other ways to prevent using the transit lines is generally okay.  For a route or OD cost matrix, it would work fine and produce the right results.  However, for Service Area specifically, I think polygons it will generate will be kind of nonsensical. The Service Area solver runs an algorithm to generate the polygon geometry, and this algorithm has a lot of rules around when to cover or not cover edges in the network.  Let's say you have an ordinary city block, and all streets surrounding that block were reachable within the travel time limit.  Then the entire area of that city block will be covered by the polygon.  Let's say only three of the four sides were reachable.  The polygon generation algorithm does some math and covers only part of the interior of that block.  Let's say all four sides were reachable, but a small dead end going into the center of that block is NOT reachable or is restricted.  More math happens, and the polygon geometry will have a hole in it to account for the unreachable street. The problem is if you have a bunch of transit lines criss-crossing your network that are restricted or effectively unreachable in the analysis, the Service Area polygon generation algorithm will go to heroic lengths to avoid covering them, sometimes producing really weird and complicated geometries that really aren't what you want. For your case, I think it would be better to create a separate network.  You can make a copy of your current network and remove the LineVariantElements, StopConnectors, Stops, and StopsOnStreets (and then delete the feature classes and all the associated transit tables).  Or you could start over from scratch with your OSM streets. Here is a tutorial about how to create a network dataset (non-transit): https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/how-to-create-a-usable-network-dataset.htm   ... View more

Thank you again for your help. The Service Area Analysis with lines is exactly what I did and what helped me a lot to discover the connection issues in the first place. I will have a look into those post process tools though.  And now I found the root of the problem. I used a script to extract the line vertices and use them as points to snap on to (using the Near_analysis tool). However, this particular code did not work correctly (I suspect a roundingn error somewhere). I used QGIS for the vertice-extraction instead and this solved the connection issues! Regarding the Licensing: as a lowly intern creeping about I sadly have little leverage to push the company I'm at to double their expenses. Might change however in the future... ... View more

You have a couple of options. Depending on what you're trying to do,  you might be able to model this using an added cost point barrier in your analysis.  Here is some documentation about barriers: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/barriers.htm If that isn't sufficient, and if you have a Streetmap Premium license (I'm assuming that's the Esri proprietary data you're referring to), you can talk to your Esri representative about getting the Custom Roads version of Streetmap Premium, which is editable.  You could then edit in one or more turn features at the intersection you're modeling to add additional travel time when turning left, going straight, etc. ... View more

This Idea has been implemented in ArcGIS Pro 3.2. Please see the What's New documentation for more new features in Pro 3.2 and the Your Ideas in Pro 3.2 blog to learn about other new Ideas that were implemented. ... View more

This Idea has been implemented in ArcGIS Pro 3.2. Please see the What's New documentation for more new features in Pro 3.2 and the Your Ideas in Pro 3.2 blog to learn about other new Ideas that were implemented. ... View more

Melinda, i want to provide an update.  After upgrading to ArcGIS Pro 3.2, this issue is no longer happening! ... View more

Your network configuration looks correct.  The null attribute parameters are also correct.  You can read about the supported parameters for the Public Transit evaluator here: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/public-transit-evaluator.htm#ESRI_SECTION1_9FF9489173C741DD95472F21B5AD8374 My guess is you still have some connectivity problem.  Try using the Explore Network tool to click on one of the LineVariantElements features.  The map will show which other network features are connected to it.  Check to see whether the StopConnectors are correctly connected.  Also click on a StopConnectors feature and make sure it connects to the street. If that still doesn't work, either contact Support or post your data here and I can take a look.  (You can also send me a private message if you want to share the data privately, but be sure to leave a comment here since Esri Community's private message system doesn't give me an e-mail notification.) ... View more

I mean that the 'impedance' option is not directly in the ribbon. It's important for it to be there because it indicates the basis on which the entire analysis is performed   ... View more

Many thanks for the input     ... View more

I have tried it with and without setting the “population” a s a weight, the result is as shown in the screenshots below   ... View more

Also, we have a virtual computer lab that many students use where the screen resolution/scaling is not modifiable. The Network Analyst window doesn't fit on the screen, even at its minimum size. I am not sure why it's necessary for the window to be so large, especially in conditions like below, where it's mostly blank space.   ... View more

A couple of other questions: I can't see from your code snippet where you save the resulting Service Area polygons.  Are you using the export() method?  This might be a dumb question, but are you sure you're saving the result of each iteration to a separate feature class and looking at the right one in the map?  What happens if you run the script with just one travel mode (the one for bus that you're having trouble with)? Are you sure the points you're using as inputs are locating in the desired place on the network?  Are you using some network location settings in Pro that you're not using in your script? Are you sure it's really working as intended within the Pro UI?  Can you paste a screenshot of your layer's analysis settings and your network dataset configuration (connectivity policies, travel mode and attribute configuration)? ... View more