Spatial Landmarks not recognized in NA

[BrandonMcAlister]

Hey everyone I was tasked with creating a local government Network Dataset for our facility. I have fully built the network and it is able to route around our facility with no issue. A restriction we have in our facility are vehicle gates, some with badge access and some that are manual gates. There is a restriction set up to only allow routing through gates with badge access. 

My goal is to have the badge access gates show up in the directions. The gates are a points that are added as a junction to the Network, they are set to connect at any vertex along the edge feature (roads) and the edge feature is set to allow any vertex. However when the Route goes through the gate it does not say the gate name it passes through. The gate junction is set up to support directions and the base name field is filled out. 

From my research it seemed the best course for me to take was to add the Gates as a Spatial landmark so when the route passes by the gate it would input a predetermined text block into the directions. However it does not do that, the shapefile I use for the spatial landmarks is exactly that same as the junctions shape file, so it does intersect with the edge feature (roads). I have not tested it with a shapefile that does not intersect with the edge feature (roads)

I followed pretty much everything outlined in this help page: https://pro.arcgis.com/en/pro-app/3.0/help/analysis/networks/how-to-create-a-usable-network-dataset.... 

Does anyone know what I should do differently to allow the gates name to show up in the directions?

Network Analyst built on ArcGIS PRO 3.0.1, we have since upgraded to 3.1

[JaySandhu]

Can you try the spatial landmarks as feature classes in a geodatabase as opposed to being a shapefile? 

Jay Sandhu

[BrandonMcAlister]

My apologies I wasn't clear, the file I am using for the spatial landmarks is contained in the same feature dataset as the Network Dataset. To my knowledge anything that is added to a Network dataset has to be contained within the same feature dataset. 

So yes, the spatial landmarks "shapefile" is a feature class within a geodatabase. I have tried it on a file geodatabase and on our SQL geodatabases and have not been successful in either. 

[RachelApplebaum]

Are the gates set up as a turn or confirmation landmark? That might be what's going on. If they're set up as Turn landmarks, then if they're at the intersection of 2 edges that constitute a straight "turn" (within a 30 degree azimuth, I believe) then you might not be getting them used in the directions. Also make sure that you have the label field set up for them, so that it's reporting the right info.

To check the type of landmark, look at the Guidance column.

[BrandonMcAlister]

The gates are set as a confirmation landmark, currently the label field is text which is just the gate names. 

[RachelApplebaum]

Are you able to remove the gates as junction sources in the ND? We don't recommend having landmarks as edge or junction sources and it could be causing some issues. 

If that doesn't work, would you be able to post a sample of the data, with a network dataset and a route through a gate, showing that it's not generating the direction?

[BrandonMcAlister]

If I understood you correctly, it is not recommended as have the same "feature class" as both a junction and landmarks. In my case I have two feature classes: Gates_Source_features, which is added as a junction under the source features tab; and Gates_Landmarks, which is added under the spatial landmarks tab. You can see them below.

 

Below is the print out of the route layer in ArcGIS Pro, this route travels through 3 different gates and should have the name of the gate show up between "Bear right on Linberg Exit Ramp/Continue forward on Amelia Earhart Boulevard", there is a gate right after "Turn right on Byrd Highway", and the final gate is between "turn left on Earhart Drive and Continue forward on perimeter road" However as you can see they don't show up in the directions.

 

Attached below is the same route that is run on our Enterprise portal and it has the same issue. 

 

[RachelApplebaum]

Ah, ok. Are the Gates_Source_features and the Gates_Landmarks feature spatially coincident?

[BrandonMcAlister]

Yes, Gates_Landmarks is just a copy of Gates_Source_Features.

[RachelApplebaum]

Ah, ok. Let me do some testing here. I can reproduce that situation fairly easily. Hopefully I can reproduce the results just as easily.