Moving Assets Along the Road Network

This document covers how to move assets along the TIGER road network during runtime.  There's also a method to command the movement of assets along the TIGER database roads, but frankly it's so trivial that it won't be covered in detail here.

The Terrestrial Initiative in Global Environmental Research (TIGER) database is National Environment Research Council (NERC) community research program. JFORCES uses this database for roads and key buildings (hospitals, apartment buildings, and so forth).  Without this information being provided and associated with the scenario during Mission Planning the asset can not use the road movement option.  The data must be linked to the scenario in the Mission Planner, as described in the above "Tiger Features" discussion.

IMPORTANT NOTE: Tiger-data related interfaces will ONLY retrieve data on the components of the TIGER database loaded into the currently running scenario. This means that there are two levels of missing data possible. First, the TIGER database must be associated with the scenario in the Mission Planner. The path to accomplish this is in the Mission Planner is Scenario Defn->Scenario Configuration->Ground Fighting Specifications->Road Network Specifications. Verify the road network is turned on and the appropriate database is user. The second reason that data might be missing is the runtime TIGER database must be populated for the region run. Working notes on how to do this are available here; please read these if interested in the TIGER data.

When the user selects the "Move Along Road Network" option this GUI will appear:

Ground Router GUIItems of interest:

1.      The top part of this interface is a standard JFORCES runtime asset selection widget, described here.

2.      The location with Map Pick option provides the destination.  Note that this interface is NOT limited to road movement; it will automatically employ off-road motion whenever road data is not found or the point is not close enough to a road point.

3.      The "Emergency" button tells the system whether or not the vehicle should use speeds commiserate with those defined for emergency vehicles (otherwise speed limits will be observed).

4.      The "Draw" option indicates that the user wants to see a dynamic rendering of the route planning with an afterimage of the selected route.  When the user first selects this option he'll see a "spider web" of road options grow with the principle route indicated in green (sample).  After the best route is found the residual will remain in cyan, as shown here.

5.      Execute - The simulation will ONLY execute the selected route if this option is selected.  IMPORTANT- by default the route is NOT executed; click this button if you what the vehicle to proceed along the selected route.

6.      The filters (Acceptable min speed, acceptable min road flow, etc) are used to limit the roads used by the algorithm.  This data is consistent with the road data interactively retrievable, as described here.

7.      Issue Command - Nothing will happen until this is pushed.