Latest Contributions by Walker_Max

‎08-10-2020

Thanks for the reply Alan. All of the LinkID fields for AltStreets, Streets and Z Levels are long integers. The error shows LinkID for all of the fields except the signs table which shows SRC_LinkID. You are correct that I misspoke in my versioning. I have desktop 10.6.1 and I have version 10.6.0.3 of the tool. I'm willing to bet this is my issue. I'll download 10.6 and try working though the creation process with it. Thanks Max

‎08-10-2020

I am using the Process NAVSTREETS Street Data tool (version 10.6.1) with arcgis 10.6.1. When I add data sources for Streets, AltStreets, Z-levels, Cdms, Rdms and signs, everything looks correct. But as soon as I set the output file geodatabase, I get an error for all of them that the "Field named LINK_ID is not the expected type." (SRC_Linkid for signs). The LinkID field is a Long Integer and is unedited from HERE. What is the expected type that this data processing tool is looking for? And why is it all correct until I set the file geodatabase location? Thanks, Max #StreetsProcessingTools #NAVSTREETS #LINKID #NetworkDataset NetworkAnalyst

‎05-05-2020

How are the KPH. and Minutes fields calculated when you create a network data set? I have a network data set that I've built and I needed to update some intersections. I made my edits and am now trying to figure out how to calculate the KPH and Minutes fields so that when a route uses the newly added road segments, the time calculation is correct. OR is the Miles and Minutes all that are needed? If so, how are the minutes calculated? #CostAnalysis #NetworkAnalyst #NetworkDataset #CostAttribute #Miles #Minutes #KPH

‎04-12-2018

I was able to edit a value in the directions.xml located in the network analyst folder under program files to get the directions to read as I wanted. C:\Program Files (x86)\ArcGIS\Desktop10.2\NetworkAnalyst\Directions  <Recognizer id="ComplexTurn" type="eRTComplex" > <Rule>@Intersection And @TurnAzimuth</Rule> <Param name="DistanceThreshold" value="0.04"/> <Param name="Origin" value="SecondSimpleTurn"/> </Recognizer> I changed the distance threshold value to 0 instead of 0.04.

‎04-03-2018

Our end goal is to have all turns in the route have their own line of direction, instead of the combined example.

‎04-02-2018

I am more so looking for a way to break up lines of directions like " and immediately turn left on". We currently wrap all local road sections of the route with a green band. This shows customers which sections they need to get local permission for. If we do a jurisdiction check on the first part of that string, " Turn left on |EDISON ST (Local-GALLATIN) (Class 0)| and immediately turn left on |IL-13 (State) (Class 2)|", we are assigning that whole stretch of the route local jurisdiction. When in actuality it is only the first .1 miles of the 4 mile section identified by that line of directions. Even if we check the second end of the directions string for "State", we are then assigning the .1 mi of local roadway state jurisdiction. We solve routes and issue permits directly after a route is solved. I am concerned that the first option would add a lot of time to the route solve process and not really solve our issue. The second option would generate an accurate mileage value for State vs Local roadways, but I don't think it will alter the directions or the issue of assigning the green band to local roadway edges. I'll attempt the second option and see if we can figure out a different method of assigning the green band on the local edges. Thanks! Max

‎03-28-2018

I am using the Network Analyst‌ extension to find routes for truck permitting. We recently upgraded our network dataset versions to 10.2 and I noticed some changes in the directions. The change that is causing an issue for me is when there are two turns in close proximity. The directions return something like "Turn left on |EDISON ST (Local-GALLATIN) (Class 0)| and immediately turn left on |IL-13 (State) (Class 2)|". The issue is that it ties two different road segments together under one line of directions. This results in the mileage being combined for those two different road features. For our routing application, we need these two roadways separated for mileage calculation (State vs Local). We also wrap the local roadways with a green band in our application so customers know which local sections of their route they need to get local permits for. This is much more difficult with two different classifications of roadway segments sharing the same line of directions. I have tried changing the Road Class Integer Descriptor to classify State and Local roadways different but the "immediately turn.." still occurred. Does anyone have any ideas on what I can change to get the directions to read each change in street name or direction as its own line? The images attached show how the two different jurisdictions of roadways are combined into one line of directions (which I need broken up). As you can see, the mileage is combined for that line of directions. So even though .1 miles might be local and the other .3 is state, it only results in .4 Mi. Thanks! Max

Online Status	Offline
Date Last Visited	a month ago

My Ideas

Latest Contributions by Walker_Max

Re: Process NAVSTREETS Street Data tool - Field named LINK_ID is not the expected type

Process NAVSTREETS Street Data tool - Field named LINK_ID is not the expected type

Network analyst - Cost attribute calculation

Re: Network Analyst Directions

Re: Network Analyst Directions

Re: Network Analyst Directions

Network Analyst Directions