Latest Contributions by MelindaMorang

It sounds like the network somehow got corrupted.  If you see it again, please save a copy of the bad network and share it with us.  Maybe we can figure out what caused it to get into that state and fix it! ... View more

No updates from the Esri side.  The other user hasn't shared the network with us, so there's not much we can do.  Can you share your network?  Feel free to private message me with a sharing link or to request that I provide one for you. ... View more

From your description, I highly doubt the Directions geoprocessing tool is going to give you the output you need.  It's not really machine readable, so unless it gives you exactly what you want, it's unlikely to be usable.  You can download some network datasets from our Pro tutorial data here and give the tool a try yourself: https://links.esri.com/NetworkAnalyst/TutorialData/Pro The Directions geoprocessing tool was created a very long time ago and utilizes an earlier way of generating directions that is more or less deprecated, at least internally.  It doesn't use the new directions engine under the hood, which generates the DirectionPoints and DirectionLines feature classes.  Those feature classes (the newer-style directions) are the only directions information we get back from services.  We don't have the older style directions information available to us, so we can't support the Directions tool when solving against a service.  It is extremely unlikely that we would ever make any updates to that tool to support this. It sounds like you have very specific needs for the output text and format for your turn-by-turn directions.  I think coming up with an automated process for post-processing DirectionPoints and DirectionLines will be your best bet.  The calculations you mentioned seemed straightforward enough.  If you can implement them using the Calculate Field tool or something like that, you could run them in a Python script or model. Another option is to use our custom directions functionality in the arcpy.nax module: https://pro.arcgis.com/en/pro-app/latest/arcpy/network-analyst/custom-directions.htm.  This allows you to customize the directions maneuver text as it's being generated, although this only works if you have a local network dataset and not a service.   ... View more

The barriers sublayers are just ordinary feature classes, so to get rid of barriers, you should just delete all the rows.  You can select them all and delete them and then save edits, or you can use the Delete Features geoprocessing tool. ... View more

Unfortunately, while I can definitely help you with problems related to the GTFS To Public Transit Data Model tool and associated ArcGIS functionality, I can't really help you debug your GTFS data.  I did take a quick look at it and spot-checked a few values for the two routes you mentioned, and everything looks okay as far as I can tell. Here are a couple of things to check on the Network Analyst side to rule out a problem there: Make sure the date and time you're using for the analysis is a date and time when transit service is running for the new line. Make sure you don't have a connectivity problem.  Use the Explore Network tool to click on the transit line and its associated StopConnectors features and make sure it's really connected to the streets. Are you using any of the Public Transit evaluator's supported attribute parameters to run scenarios for excluding lines?  Have you inadvertently excluded the new transit lines?  (See https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/public-transit-evaluator.htm#ESRI_SECTION1_9FF9489173C741DD95472F21B5AD8374.  If you have no idea what I'm talking about, you're probably not doing this.) If none of those things bear any fruit, then the problem is likely related to your homemade GTFS files, and you'll need to check those carefully to find where it's falling apart. ... View more

Oh, I think that makes sense.  The route_type field probably got something like 3.1 instead of 3, so it was read as a double instead of an int.  I'll see if I can reproduce that problem and make the error better. ... View more

Interesting.  It sounds like something was corrupted in the network, so starting over is a good idea.  If you still have a copy of the bad network around, I'd be happy to take a look at it.  We can try to see if we can improve the error messaging in case you or someone else runs into this again. ... View more

@RylandLu It seems like you must have found the culprit.  Any chance you can share the bad routes.txt file with me so I can improve the error message on our side? ... View more

Hmm, that's not a very specific error! What version of Pro are you using? Does it matter how you configure the new cost attribute?  If you do something really simple, does it still have the problem? ... View more

OD Cost Matrix is the best tool to use if you want a table showing the driving time of each population centroid to healthcare centers.  Here's a tutorial: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/od-cost-matrix-tutorial.htm Service Area should produce polygons around the provided facilities.  If it's not working or producing the expected output, maybe something is wrong with the settings you chose or the network dataset you're using.  (Did you create your own network dataset?)  Here's a tutorial: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/service-area-tutorial.htm ... View more

You're correct that the Directions tool doesn't work when the network analysis layer uses a service as its network data source.  However, turn-by-turn directions are available.  You can print them from the Directions pane.  Or, if you want to do something more custom with them, you can access the DirectionPoints and DirectionLines feature classes in the feature dataset that stores the network analysis layer's data. To find the feature dataset where the network analysis layer's data is stored: Open the properties of the network analysis layer by right-clicking or double-clicking in the Contents pane. Go to the Source page Go to the Analysis Data Source section Refer to the Database and Feature Dataset rows in the table. You'll find the DirectionPoints and DirectionLines feature classes like this: The schema of those feature classes is documented here (for Route): https://pro.arcgis.com/en/pro-app/latest/arcpy/network-analyst/route-output-data-types.htm#ESRI_SECTION1_D2B51A15DC6D45D6AF1167156492240A  (I know this is the arcpy.nax documentation, but it's the same schema.)  The other solvers that support directions have a nearly identical schema, with some minor differences in the ID fields that refer back to the original inputs. Does this serve your needs?  If not, please let us know specifically which features of the Directions tool you would like to see implemented (which output type, etc.). ... View more

Did the Closest Facility solve generate any warning messages like ‘No "Facilities" found for "Unnamed (ObjectID = 1)" in "Incidents".’? I suspect the facilities may be on parts of the network that are disconnected from the rest of the network due to some sort of connectivity problem.  Check whether the roads they're located on are properly connected to the surrounding roads.  You can use the Explore Network tool to click on roads to see what other roads they're connected to. It could also be a problem with a one-way street being incorrectly configured, or a turn restriction preventing travel through an intersection, if you're modeling turns. ... View more

Hello @tcrammond.  Sorry about this.  Unfortunately many of the arcpy modules don't behave nicely with linters, for a variety of technical reasons.  I will investigate this and see what options we have for improving the experience.  However, regardless of what Pylance is telling you, the module should still work as documented when the code is run. Could you please tell me what version of ArcGIS Pro you're running?  I know we made some improvements to arcpy.nax linting and type hinting in the 3.2 release, but it may have been in a limited area. ... View more