Latest Contributions by MelindaMorang

Hi again.  I saw your escalation request for this BUG.  I wanted to acknowledge that we are looking into it and update you on what we know so far. The Base Name property of the directions field mappings is set to an invalid field name that doesn't exist in the Pathways source feature class. When you changes certain other network dataset properties, it's triggering some sort of refresh, deleting this invalid property, and causing unexpected changes to the walking directions text.  You can't actually see the invalid field name in the UI because the UI knows that it's invalid and conceals it (something we hope to improve). We definitely want to improve the behavior of the network dataset for this scenario. However, it seems like the root of the problem is an invalid setting, possibly related to the network dataset template used to create the network.  But, we still don't fully understand the problem, since setting a valid value for that Base Name field mapping property doesn't fix the network. ... View more

Did you actually manage to get it working?  I'm sorry this has proven so frustrating!  At this point, if it's still not working, I suggest you call Esri Support so one of the analysts can work through it with you and try to pin down the source of the problem.  It doesn't seem like the type of problem we can solve here on the forums. ... View more

Until a developer can debug the problem, we don't know what's causing it, and I can't offer a very good workaround. My only idea is this: Use the Create Template From Network Dataset tool to create an xml template file with your network dataset schema. Open the xml file and edit the Confirmation or Turn Landmarks tolerance  (you'll have to dig through the xml to find where that property is). Delete your network dataset Use the Create Network Dataset From Template tool to re-create the network using your updated xml template. Run Build Network I'm pretty sure this will work for the Confirmation and Turn Landmarks case because it should be a simple update to the template xml.  But for some of the other items you mentioned, like adding a hierarchy attribute, I suspect the changes to the xml template would be too difficult. ... View more

Okay, I was able to reproduce the problem in Pro 3.3 (the latest release).  I logged an issue, and our developers will take a look.  You can track the issue as BUG-000169839 through Esri Support if desired. For what it's worth, Pro 3.0 is in Mature Support, and it would be a good idea to update your software to the latest version.  I guess you could wait until we fix this bug, though, if you want. ... View more

Also, what version of ArcGIS Pro are you using? ... View more

Just to make sure I fully understand the problem: Before making the changes described above, was the network in a built state?  (In other words, you ran Build Network at some point and haven't made any edits to the source features or the network dataset properties since then.) Did you re-build the network dataset after making any of the changes you listed above? Assuming you re-built the network, were there any build errors? Did you re-solve the route before checking the directions? After changing the network dataset properties and committing the changes (clicking OK on the properties dialog), check the network dataset properties Directions configuration.  Is it still configured correctly for the Level fields?  Network Dataset Properties -> Directions -> Field Mappings -> Auxiliary Properties -> Level (From) and Level (To) ... View more

Can you please post a screenshot of the network dataset property you're altering? I see the problem you're describing in the directions text, but I don't understand from your description of "Situation 2" which property you're changing. ... View more

Okay, those build errors are minimal and don't really look like a problem, so they're probably safe to ignore. Here is some documentation explaining network dataset connectivity policies: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/understanding-connectivity.htm The "Create an use a network dataset with public transit data" tutorial has some specific information explaining when you might need to use Any Vertex instead of End Point connectivity for your streets.  Take a look at the "Examine the street data" section (particularly step 7) and the "Examine the network dataset's properties" section (particularly step 3). ... View more

The problem is more likely in your network dataset.  Maybe the streets aren't properly connected to each other.  I see from your Geoprocessing history that the Build Network tool succeeded with warnings. Did you examine the build error text file and check each one?  Did you make sure the connectivity policy was correct for the way your street data was constructed?  (In other words, do you need to use Any Vertex instead of Endpoint?) ... View more

This definitely looks strange. Your code looks fine to me. What I can't determine from your screenshot is whether there are edges in your network underneath that zig-zaggy purple line.  Are there?  Or is the line just completely different from the underlying features in the network?  In other words, is the purple route following SOME kind of streets, or is it just generating a wacky geometry that has nothing to do with the underlying network? Since I really have no idea what might be causing this, here are some questions and things to check that might lead somewhere: Does your travel mode (any of the ones you've used) have a simplification tolerance set, and what is it? Is your network dataset built?  Have you edited the geometry or settings since the last time you built it?  (The General page on the network dataset properties will tell you if it's built.) Are you 100% sure that the route you created using the Pro UI was using the same network that your script is using?  Did you accidentally use ArcGIS Online as the network data source for the layer in the UI? If you call export() in your script to export the output route to a feature class, does it still look strange?  Maybe the problem is in the insertCursor. This definitely seems like a strange issue, and if none of these questions lead anywhere, you might be best served by calling Esri Support or Support for the distributor in your country.  They can look at your workflow in detail and try to identify the problem. ... View more

Yes, if you were able to successfully create and build a network with your edited template, then this should be sufficient to resolve the problem. ... View more

By the way, this was an extremely strange issue!  I'm sorry you encountered it, but it's certainly not something we had ever thought to test.  You found a very interesting challenge for our team. ... View more