Latest Contributions by RobertLindquist

I want to restrict turns at particular intersections if a vehicle is greater than a specified length.  In other words,  any vehicle over 65 feet cannot turn left or right, but driving straight through the intersection is OK.  Further, any vehicle under 65 feet can turn in any direction. My approach is:  In the network dataset, first I created a new feature class (named:  LengthTurnRestrictions).  I have created turn features, snapping them to the edges of the network (see the illustration below).  I added a field to the attribute table named "LengthRestiction" and have coded all of these new features as LengthRestriction = "TRUE".  [ATTACH=CONFIG]17116[/ATTACH] In the Network dataset properties, I have created a turn restriction attribute (named: LengthTurnRestriction).  I've also created a network attribute parameter (named: VehicleLength and set the default value to 0).  Finally, I know that I need to set the attribute evaluator to use that parameter, but I'm not sure exactly what to do.  My thought was to set the evaluator Type be set to VB Script and the value "restricted" using VB script like:  restricted=FALSE Select Case UCase([LengthTurnRestriction])   Case "TRUE":restricted =TRUE End Select This did not work as I'd hoped.  Please comment about my approach, or better yet, let me know just what I need to do to enforce length-based turn restrictions. ... View more

I'm looking for a version of AGSSOM for 10.1  Does anyone know if it has been compiled for the ArcGIS 10.1 release?  If so, can you point me to where I can download it. Thanks. ... View more

I have an application for routing oversize/overweight vehicles on a statewide database built from Navteq data.  In the desktop application, routes are solved relatively quickly; even long routes accross the state (average under 10 seconds).  However, we need to deploy a web application to allow the trucking public to apply fro permits for these vehicles.  I've created a map service from the MXD that I've used in the desktop application.  The web application is using this map service.  The problem is:  it takes significantly longer (up to 10 times longer) to solve the same route in the web application.  It works, but the time to solve is not acceptable.  Does anyone have any suggestions for what I should look at to try to increase route solving speed in the web application? ... View more

I am using the Street Data Processing toolbox (the Process NAVSTREETS Street Data tool) which has worked well for me in the past.  I now have updated Streets data and am trying to run the tool on it.  I include all of the inputs (Z-levels shapefile, CDMS, RDMS, and Signs tables).  It appears to run fine, attached is a screenshot of the report showing that it completed successfully.  It does create a File Geodatabse Feature Dataset, and  creates a Streets feature class in the dataset.  HOWEVER, I am not getting everything in terms of output that I have gotten in the past: now, it does not create and build the network, it does not create the Restricted turns, Signposts, or ND_Junctions.  Any suggestions? ... View more

I have an application for routing oversize vehicles, and at certain intersections I need to restrict only certain turns based on parameters or conditions of the vehicle.  For example, a vehicle over 80 feet long cannot make a left turn but all shorter vehicles can make the left turn.  The 80 foot vehicle can however go straight through the intersection or make a right turn.  Is there a way to place a turn restriction that checks the vehicle parameters? ... View more

When I solve for a route, I am getting the following message: Warning: Gaps have been detected in the cumulative impedance values of the output. This can occur due to the presence of positive-impedance junctions, turns, or additive point barriers along the output edges. Measures have been disabled for output in this case. I have looked in the Help to try to find out exactly what it all means and if it is a serious problem.  I have modified the "minutes" attribute to encourage/discourage travel along some parts of the network.  In the route directions, I am not concerned with travel time, only a workable route (I'm routing oversize vehicles and simply looking for a way to get them from point A to point B).  I don't know if that is what's causing this message or not.  Any further explanation of what the message means and what the ramifications are would be appreciated. ... View more

I have a turns feature class that I use to restrict multi-part U turns.  I'm trying to update some features but after deleting the old feature, adding in a new feature and rebuilding the network dataset, I get the following build error:  "SourceName: MultiPartUTurns, ObjectID: 41, Turn element already exists."  I've tried using the Update by Geometry tool and then re-build the network but the results are the same. ... View more

I have created a turn feature class to prohibit certain multi-part U turns.  It is working just as I'd expect when I solve for routes.  The problem is:  we are using Navteq data as our base for creating the network dataset and Navteq provides quarterly data updates.  I would like to be able to import the turn feature class to the updated data (understanding that it wil only be applicable where Navteq features remain the same -- which is of course the majority of features).  I've tested importing my turn feature class into an older Navteq version and built the network dataset.  The problem is:  even though the majority of road features have not changed, my turn restrictions are not being honored as they were earlier.  I'm looking for a way to retain my turn restrictions when I update the (mostly unchanged) base data. ... View more