Latest Contributions by MelindaMorang

Network Analyst has no particular requirements for spatial reference.  You can use anything you like. ... View more

For anyone looking at this issue in the future: The ArcGIS Pro documentation now includes a guide for troubleshooting unexpected network analysis results and problems with user-created network datasets: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/troubleshoot-network-analysis-problems.htm. ... View more

For anyone looking at this issue in the future: The ArcGIS Pro documentation now includes a guide for troubleshooting unexpected network analysis results and problems with user-created network datasets: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/troubleshoot-network-analysis-problems.htm. ... View more

For anyone looking at this issue in the future: The ArcGIS Pro documentation now includes a guide for troubleshooting unexpected network analysis results and problems with user-created network datasets: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/troubleshoot-network-analysis-problems.htm. ... View more

For anyone looking at this issue in the future: The ArcGIS Pro documentation now includes a guide for troubleshooting unexpected network analysis results: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/troubleshoot-network-analysis-problems.htm. ... View more

Thanks for reporting that.  Can you share your network dataset with me?  You can send me a private message through this platform or e-mail me at mmorang@esri.com.  If you need a secure data upload link, I can provide one. ... View more

The Network Analyst locating process doesn't have any knowledge of external features like your canals, so it will always locate points on the closest non-restricted network edge, even if it's on the wrong side of the canal. How did you generate the points in the first place?  If you geocoded them from addresses using the World Geocoding Service or a locator that includes the routing location in addition to the rooftop location, try geocoding them again using the routing location.  That should move the points closer to the correct street or the driveway location for the property rather than the rooftop center, which may be closer to a different street. Alternatively, you could try using a search query when running Add Locations or Calculate Locations to more accurately match the point to the correct street.  Unfortunately, you can only use a single query for the entire dataset, so this might only work on a case-by-case basis. ... View more

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