[[http://jforces.com/forces_doc/UserManual/images/snapshot95.jpg Map Controls]]

This list of interfaces controls the Map. There are three distinct sets of controls depending on the system status. These controls are:

  1. Core - These options are always available. The Runtime and Mission Planner Options are Added to this core on the interface.

  2. Runtime - These options are added to the Map Controls after the system has successfully connected to a simulation.

  3. Mission Planner - These options are added to the Map Controls when the System is in the Mission Planner Mode.

Map Controls - Core Options

Map Settings File:

This permits users to save key components of the map view to a file for later reuse and/or restore the map view from a previously saved view. These settings include the maps' user viewpoint and scale. Other parameters are in the process of being added to this file and new capabilities are expected to be incorporated over time.

Post Images

This option permits the user to display one or more background images in the map. These images are entirely user-defined, so no exhaustive list is provided here. The user can alter this list by changing the input file. This input file is $MAP_DIR/mapInfo.dat and my be edited in any standard (non-formating) editor. An example of how to edit this would be to type the following in a terminal window:

gedit $MAP_DIR/mapInfo.dat

This file consists of a lines of image definitions. Each line defines one image. The fields are:

    1. A unique ID.

    2. The image filename. Currently only .gif and .jpg formats are supported. This file must be in the $MAP_DIR directory.

    3. The northern extent of the image (decimal latitude, negative for Southern Hemisphere)

    4. The western extent of the image (decimal longitude, negative for Western Hemisphere)

    5. The Southern extent of the image (decimal latitude, negative for Southern Hemisphere)

    6. The Eastern extent of the image (decimal longitude, negative for Western Hemisphere)

    7. The map type. Always use "1"

    8. The map description.

    9. The map category. Basically, you want only a few categories and unique descriptions for every map because the interface will generate a hierarchical structure based on category->description.

    10. (Optional) A set name for the map(s). A set consists of one or more maps all within the same category. When the set name is specified the individual maps constituting the set will not be individually displayed. Instead a single checkbutton will be created for the entire set and when this button is changed the display for all maps in the set will changed simultaneously.

Grids

This option enables the user to put a reference grid on the map. There are currently two options.

      1. Constant area grid. These are square grids with constants x and y separation between the lines.  ([[http://jforces.com/forces_doc/UserManual/images/Grid_constantarea_GUI.jpg GUI sample]]) ([[http://jforces.com/forces_doc/UserManual/images/Grid_Constantarea_map.jpg Map Sample]])

      2. Range grid. These are concentric circles radiating out from a given point.  ( [[http://jforces.com/forces_doc/UserManual/images/Grid_Range_GUI.jpg GUI Sample]]) ( [[http://jforces.com/forces_doc/UserManual/images/Grid_Range_Map.jpg Map Sample]])

      3. Lat/Long grid. These are grids set up according to latitudes and longitudes. As such they are similar to the constant area grids except the "vertical" lines converge inwards at north and south extents. ( [[http://jforces.com/forces_doc/UserManual/images/Grid_LL_GUI.jpg GUI Sample]]) ( [[http://jforces.com/forces_doc/UserManual/images/Grid_ll_Map.jpg Map Sample]])

Multiple instance of any of these grid types may be displayed simultaneously, each with their own center points, area specifications, colors, and so forth. Each of these can also include multiple altitude bands. When multiple altitude bands are selected the grid will be repeated at each level.  

Data Driven Overlays

This interface ( [[http://jforces.com/forces_doc/UserManual/images/snapshot97.jpg" example]] ) lists the overlays currently available for use. Like the "Post Images" option described above, the options under this interface are entirely user defined and therefore are not described in detail here. More important is to know the location of the definition files and how to add, delete or modify them.

The files are contained in the $GRAPHICS_DATA_DIR directory and have two forms. The first form defines the line overlays (e.g. Control lines), and the second defines sets of icons. Files defining line outlines can be found in this directory and are always named overlay_###, where ### represents a number between 1 and 999. IMPORTANT: This number must be unique NOT ONLY relative to files named overlay_### but also overlayicon_### found in this directory. While a specification for the file contents can be found here, There is a graphical tool to specify these line overlays easily under "Start Line Overlay Editor" option on this interface. This interface ( [[http://jforces.com/forces_doc/UserManual/images/line_editor1.jpg reference image]]) permits the user to create, delete or edit any of the line overlays. In [[http://jforces.com/forces_doc/UserManual/images/line_editor2.jpg this image]] a pre-existing line overlay has been loaded (through the "Load Existing Overlay" button on this interface). Points of interest:

Unfortunately, currently there's no similar GUI for laying down icon overlays. Instead the user must create these overlays manually (e.g. Through a non-formating editor like gedit). The format of these files can be found here.

Map Reference Aids:

Convert Coordinates

On the [[http://jforces.com/forces_doc/UserManual/images/6bCoordinateConversion.jpg Coordinate Conversion Form]] the user may enter coordinates by either lat/long or UTM and get the alternate form. In addition, users can enter the decimal latitude (or longitude) and get the deg/min, deg/min/sec, and UTM equivalents. He can also enter the deg/min OR deg/min/sec and get the decimal location and the UTM. BUT remember to hit the "Enter" button whenever a valid input is made to any field.

Basically, this system works by recognizing the row in which the user hit the "Enter" button, and then generating the equivalent values in the other 3 forms of the location. So hitting the "Enter" button often is good advice.

There is also the capability for the user to Get Location From Map and the above data is entered into the form in all four formats

Calculate Range & Heading

The [[http://jforces.com/forces_doc/UserManual/images/6cRangeHeadingUtility.jpg Range/Heading Utility Form]] aids the user in determining the range and heading between two points. This interface is kept because it permits the user to input tabular data, but for map picks generally it is more convenient to use the equivalent range/heading utility built into the maps (see the compass icon on the lower-left section of the maps). After this compass icon is picked just pick two points on the map. The map interface also permits the user to select icons and then gives a continuous readout of the range and bearing between the icon (or a map icon, like an aircraft, and a fixed map point)

Within the menu (non-map) interface the Starting Point may be designated by the user by typing the Latitude, Longitude, Northing, Easting and Zone.  The Ending Point may also be designated by the user by typing the Latitude, Longitude, Northing, Easting and Zone .  Either Point may be picked from the map.  The lower portion of this form presents Range (NM); Range (M); and Heading once the points are defined.

Range Indicator

The [[http://jforces.com/forces_doc/UserManual/images/snapshot96.jpg Range Indicator Form]] allows the user to select to insert a range indicator by first choosing the length of the indicator from 1 NM to 500 NM and then selecting the center of the indicator by choosing the Select Center from Map bar and then clicking on the location on the map.  The Lat/Long of the selection then appears on the form.  Selecting the Update with Displayed Settings bar sends this command to the simulation and causes the range indicator icon to appear on the map. The range indicator icon may be removed by clicking on the Remove Range Indicator bar.

Note that this capability is a subset of the much more powerful "Grid" options, described above.

Terrain LOS Corona

The Create LOS Corona Form allows the user to create more or more Line of Sight coronas for arbitrary location. These coronas provide terrain analysis, which can permit users to quickly identify optimal sensor deployments. The coronas can be color coded. The Lat and Long may be typed or the location picked from the map (Map Pick ). Altitude, Range of interests (NM) and Granularity may be entered.

Terrain Profile

The [[http://jforces.com/forces_doc/UserManual/images/terrain_profile.jpg Terrain Profile]] interface provides a horizontal visualization of the terrain between two points. Points of interest:

Terrain Contour Map

[[http://jforces.com/forces_doc/UserManual/images/contour_map_interface.jpg This interface]] permits the user to generate contour and surface maps of a location. It also optionally permits him to insert the map into the map display background. [[http://jforces.com/forces_doc/UserManual/images/sample_contour_map.jpg Here]] is a sample contour map generated by this interface of the Fort Hood region. This is a pretty typical contour format, though labels might make be valuable. The interface also permits the user to create surface maps. [[http://jforces.com/forces_doc/UserManual/images/sample_surface_map.jpg Here]] is a surface map of the same area as the contour map. This surface map uses white for the high spots and black for the low spots, though this default color scheme can be altered through this interface by modifying the high and low colors. Points of interest:

Get Elevation

An interface is provided to get the elevation (in meters) of a location. The location can either be specified via text or a map pick can be used.

Predict Chemical Fallout

This permits a user to specify the area of a chemical emission, the agent, the direction and velocity of the wind, and the time after the emission and provides a first-level estimate of the affected area. This is a very preliminary tool and there is no reason to consider it as having any validity.

Additional Runtime Map Controls

Sensor Displays

This option provides display options to review sensor coverage, tasking, detections and cuing graphically. It is important to remember that the employment (or lack thereof) of any of these options DOES NOT change the operation or success of any of these elements. It simply changes the information displayed on the local screen.

Turn All Detections Off (or On)

This is an interface to request that the simulation should notify this GUI of sensor detections for the force represented by this GUI (i.e. Blue or Red force, as defined in perception). As said above, this DOES NOT stop the sensor from detecting enemies and recording the success (or failure) for analysis, it simply stops (or starts) the reporting of successful detections by this GUI. This option is used to limit communications between the simulation and the GUI when the communications backbone is overloaded.

When OFF is selected, the current detections will continue to be displayed until timed-out of the system as too old.  When ON is selected, new detections will appear as they occur (and time out in accordance with the sensor's definition, usually timing out after 6 sensor scans).  Nothing will be reported while the simulation is in "Pause" mode.

Modify Specific Sensor Reporting

This will turn on or off the sensor reporting for a specific site. Again, this will have no effect on the scenario execution, only on whether the detections from the selected sensors are displayed on the local GUI.   If the umpire wants to shut down the sensor for all terminals he should go to the force controls (Red or Blue, as appropriate), then go to Status->Subsystem Status. From here he can pick the sensor and turn off the sensor subsystem. Or he can kill the sensor asset through the Umpire Controls if preferred.

Sensor Coverage Display

[[http://jforces.com/forces_doc/UserManual/images/sensor_selection_interface.jpg This option]] provides a rapid review of the region covered by selected sensor(s). As seen in the example the the sensors can be picked individually (on the left), by class (on the upper right) or by a blanket selection. Again, the selection (or non-selection) of this option does not change the sensor performance; this option is simply provided to indicate one or more sensors' fields of regard. [[http://jforces.com/forces_doc/UserManual/images/sensor_coverage.jpg Click here]] for an example map display. [[http://jforces.com/forces_doc/UserManual/images/341SensorCoverages.jpg Or here]] for a space-oriented display. Additional options are:

Modify Sensor Tasking Displays

This interface permits the user to display sensor tasking for specific sensors, classes of sensors, or all sensors. The interface is similar t that used for modifying the sensor coverage displays. Again, note that this interface has no effect on sensor tasking, just on whether the tasking will be displayed. Also note that tasking will not be displayed for sensors that are constantly on and gathering data on their entire field of regard (e.g. Air surveillance sensors). In these cases all detections will occur in the expected manner but without any special tasking displays.  

Only sensor tasking for sensors specifically tasked in Mission Planning will appear; this is not a coverage display but a tasking display. To create tailored tasking for sensor go into the Mission Planner mode and go to "Scenario Defn->Assets By Type". Then click on the type of the sensor platform and the tail number. The "Asset Defn" interface will appear. Go to "Operational Tasks" and then select "Add New Operational Task". Select "Sensor Tasking" and fill in the parameters.

Notes:

  1. The tasking display will only be shown when running in perceived information for the side the sensor is reporting to.

  2. The tasking display will only update while the simulation is running; nothing will happen during a pause.

Modify Sensor Detailed Detection Display

When selected, this option draws lines between the sensor and target whenever a detection occurs. [[http://jforces.com/forces_doc/UserManual/images/detailed_detection_monitoring.jpg This interface]] is similar to most of the sensor display controls, permitting display control for specific sensors, classes of sensors, or all sensors at the user's discretion. Functionally, this capability is basically a quick interface to determine detection success (with information on who was detected, by who) during runtime and provides an overview on the detection details available for post-processing analysis. By zooming around on the map interface and clicking on the sensor a target icon it's easy to determine who's detecting what at a given time.  IMPORTANT NOTE: The detection lines are only drawn if the target is specified for detailed monitoring in the detailed_monitoring table. This table is used as a filter for this capability to limit drawing; before this filter was added the detection lines overwhelmed the screen and this capability was useless. 

This interface is intended for use by the Umpire, so it works best in the "Truth" mode, not perception mode. Also, note that detection are only reported in this mode on targets listed in the detailed_monitoring database table. Currently there is no GUI for filling in this table.

Modify Sensor Cuing Displays

When selected, this option will draw indications (usually translucent cones) from a sensor to the area is is tasked to observe through the sensor cross-cuing algorithm. This the algorithm fired off by the sensor_cuing database table, which specifies which sensors (or classes of sensors) should automatically by cued to confirm detections by another sensor (or class of sensors). Again, the display interface permits the user to select whether the cuing information should be displayed for specific sensors, classes of sensors, or all sensors.

Show Detailed SBIRS Focal Plan Image

This option permits the user to display the emulated focal plan of a Space-Based Infra-Red sensor. This option is only available for sensors defined as "SB IR" sensors in database prototyping. It is also only available if the software configuration for this run specified the "Detailed MW SBIR Model" should be employed. This is because only these sensors (running in the detailed mode) have adequate data to drive the algorithm.

[[http://jforces.com/forces_doc/UserManual/images/SBIRS_focal_plane_interface.jpg This interface]] permits the user to select a display of one or more SBIR focal planes. When a display is selected it will come up blank (except for a note that the image is awaiting data). It will stay this way until the sensor begins it's sweep (basically, until it has a chance to see something). After the sensor becomes active a cloud background will appear ( [[http://jforces.com/forces_doc/UserManual/images/SBIR_focal_plane.jpg see example]]) . This background is divided into pixels as per the sensor resolution specification. On top of this resolution are the hotspots that have been identified via low and high pass filtering. As time progresses (i.e. the tracker has a chance to try to correlate these hotspots into 2D tracks) those hotspots correlated to tracks will be outlined with yellow boxes. One has to watch carefully because the 2D tracks show persistence in azimuth and elevation, but the sensor's pointing angle will change regularly and the whole viewpoint will change accordingly at these points.

It should be mentioned that originally the Space Based IR model worked against a piped-in cloud scene. But now that this interface is unavailable it works off a limited static cloud background found in $INPUT_DIR/background.pgm. There should be little work required to re-implement the piped-in clouds should the data become available again. There are other items of interest in this display that can be reviewed by selecting the "Help" option on the top of the display.

Also note that the display (or non-display) of the background scene with hotspots will not change the internal simulation operations. The same detection algorithms are used regardless. The displays are provided only to aid users in understanding the situation.

Wide Strobe

This option determines whether noise jamming reports should be shown as a single strobe radiating from the reporting sensor to the center of each area of interference or should be rendered as a wedge radiating from the sensor and displaying the extend of each region affected.

MTI Filter

This will limit the display of tracks according to the input speed. Note that this only a display option and will not affect the sensor performance. Therefore, if the scenario includes a AMTI radar with a lower threshold of 80 Kts changing this value to 20 Kts WILL NOT alter the capability of this sensor to detect targets closing at 60 Kts. This filter is intended to aid the user in rapidly identifying "fast movers" by filtering out slower returns.

Evaluate Area Access

[[http://jforces.com/forces_doc/UserManual/images/eval_area_access.jpg This interface]] predicts when satellites will have access to an area of interest over the next 24 hours. [[http://jforces.com/forces_doc/UserManual/images/area_access_example.jpg Example here.]] Basically this gives the user a runtime interface to a portion of the data available in the Mission Planner's Space Vignette that was found useful for force planning and intel operations.

TIGER Features

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). These features can be displayed and reviewed via map interaction. A sample interface displaying a list of categorical data available in one scenario is displayed [[http://jforces.com/forces_doc/UserManual/images/TIGER_features_sample.jpg here]]. Specifics on any of the particular elements in this database can be retrieved through the "Review Feature Via Map Click" option. A similar interface ( [[http://jforces.com/forces_doc/UserManual/images/TIGER_road_interface.jpg presented here]]) is available for displaying and/or querying roads.

IMPORTANT NOTE: These 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.

TIGER Roads

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.  FYI - without this information 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.

There are two options to support road display from this datasource:

This information comes from the TIGER database (augmented in the case of carrying capability and clearance/weight information) and for the most part this information is self-explanatory.  But this is an interactive interface with the option that the Umpire can set to reflect road damage or traffic delays.  These include:

Display Options

Current display options that can be toggled on or off during runtime include:

Scenario Targets- This option displays (or undisplays) all targets known to the current scenario. This list is comprised of the targets specified in this scenario during Mission Planning under "Scenario Configuration". If there were no targets identified during Mission Planning nothing will be displayed

Scenario Intel Reports - This includes both the pre-scripted intelligence message and any intelligence messages generated during runtime by sensors configured to create these reports. These intel reports appear as yellow triangles. Associated information (e.g. Target detection speed, alt, and amplifying free-form text) can be reviewed through the Umpire or Blue node controls.

Indicate Detected Objects - This will cause a white cross to be displayed on any asset detected by a scenario sensor. This is useful as a "quick and dirty" indication of surveillance success.

Ground Engagement Areas - This indicates the areas where the mass ground engagement module is currently prosecuting "piston-style" ground engagements. Note that because this module tries to engage everybody in mass mayhem, these area will often overlap.

Terrain Sticks - This will draw a line down from an asset to the underlying terrain. It will use DTED to determine the elevation of the local terrain. This can place a high load on the map displays. For this reason (and because the underlying terrain is rendered in 2D so these lines might appear to stop in mid-space), it is generally recommended to display altitude sticks instead.

Altitude Sticks - Lines from air- and space-borne assets to the ground. Unlike the related "terrain stick" option the lines descend to the maps at 0 MSL instead of stopping at the local DTED elevation.

Speed/Heading Indicators- This will draw vectors from moving platforms with a direction and size appropriate for the platform. Note that these will only be drawn for platforms (or groups) where the "range/heading" flag is turned on for the related icon in database prototyping. That is, the initial indication that a speed/heading vector should be drawn overrides this runtime switch. Naturally, this vector will only be drawn for moving elements. Moreover, for most ground assets this vector is so small as to require the user to zoom way in to see the vector.

Air Defense Overlay - This overlay draws lines from either an aircraft or a SAM site to an airborne target. The colors indicate the engagement status. Current colors are:

[[http://jforces.com/forces_doc/UserManual/images/snapshot98.jpg Comm Connectivity]]

This option permits the user to draw many different communications connectivity and success overlays that aid the user in understanding the communications architecture and related performance. [[http://jforces.com/forces_doc/UserManual/UserManualCommLinkDisplays.pdf Click here for details.]]

Alter Local Display Color

This option permits the user to alter the display color of one or more assets on the local GUI. This has prove useful in tracking a asset of importance in a busy scenario.

Modify Detection Report Scale

This option permits the user to alter the scale for detection reports (e.g. Raw radar detections). Selection causes a small form to appears with a sliding scale bar 0.0 to 3.0 to adjust the Drawing Scale for the Detection Report.

Additional Mission Planning Map Controls

The following Map Control Options are added when entering Mission Planning.

TIGER Features

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). These features can be displayed and reviewed via map interaction. A sample interface displaying a list of categorical data available in one scenario is displayed [[http://jforces.com/forces_doc/UserManual/images/TIGER_features_sample.jpg here]]. Specifics on any of the particular elements in this database can be retrieved through the "Review Feature Via Map Click" option. A similar interface ( [[http://jforces.com/forces_doc/UserManual/images/TIGER_road_interface.jpg presented here]]) is available for displaying and/or querying roads.

IMPORTANT NOTE: These 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 second 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.

Additional Information - Sometimes the TIGER database information is not automatically updated when a new (or alternate) TIGER database is invoked through the Mission Planner (FYI - the route to set this is Scenario Defn->Scenario Configuration->Ground Fighting Specifications->Road Network Specifications). Should that be the case it is advisable to restart the Mission Planner.

Set Unit Display Level

This interface allows the user to turn off the display of assets and/or groups according to their hierarchical level. Generally this is not required, but sometimes the scenario displays overwhelm the systems drawing capabilities. This interface permits the user to tailor the displayed information to the system's drawing capabilities.

Modify SAM Coverage Displays

This interface aids the user in determining scenario SAM coverage. The user is presented the option to turn on (or off) the SAM engagement and / or target acquisition ranges independently. The ranges are based on maximum missile kinematic ranges for engagement, or the processing for avionics acquisition. In both cases the data is as defined for the SAM subsystem in database prototyping. The displays are also not adjusted for terrain. The displays can either be hollow circles or translucent disks. The translucent disks put more demand on the graphics card, so hollow circles are advisable for busy scenarios.

Modify Sensor Coverage Displays

This interface provides a simple tool to render sensor displays during presimulation. The coverages can be displayed either as hollow circles or translucent disks. Again, this is a simple rendering of sensor coverage based on the maximum range specified for the subsystem in database prototyping. A better evaluation of coverage including terrain obscuration is available in Mission Planning under Scenario Defn->Scenario Evaluation->Evaluate Coverages.

Display Building Footprints

This interface displays the footprints of buildings defined in the building_squares and buildings database tables.