Map view

The map view provides a graphical representation of selected objects. The following entity type objects can be rendered by the map view:

Assets
Asset Assignments
Shipments
Shipment Legs
Loads
Stops
Trips
Bookings
Skeleton Routes

The map view is non-modal, so users can keep the map open and still operate on views behind it.

The map view consists of two sections: the graphical map display at the top of the panel, and a list of objects passed into the map view at the bottom of the panel. See Map list.

To open a map view, select one or more rows from a supporting entity view and click Map.

Note: The Map operation will only be available in entity views if the map license is detected (and the operation is active/enabled).

The map view will always open from the right-hand side of the results panel. The zoom level is automatically determined by the objects selected for display.

Note: A maximum of two map views can be open at any time.

To add objects to an open map view, repeat the Map operation from a supporting entity view. The map view supports the simultaneous display of different entity types in the same map view instance, such as shipment legs and loads, loads and bookings, etc.

Note: If a map view is already open and that view is not ‘pinned’, the selection will be added to that view. Otherwise, a second map instance will open.

If a selected load has no attached stops, a route cannot be rendered and an error message will be presented. In this case, no objects are added to the map view.

Shipments, shipment legs, and unassociated asset assignments always render on the map view as two location points (that is, origin and destination locations). Loads, trips, bookings and associated asset assignments are rendered based on associated stops. Route lines are automatically rendered to connect sequenced locations.

Skeleton routes and associated skeleton locations render on the map view similar to loads and stops.

Stops and assets sent to the map will render as stand-alone location points; no route lines will be generated to connect these location points.

In addition, users have the option (via Settings) to render reported location markers for loads, trips, bookings, assets and asset assignments. Reported location markers represent the assigned carrier/asset reported position(s) while executing that object as reflected in event history or stop-level actuals (for loads, trips and bookings), or asset activities (for assets and asset assignments).

Each stop location on the map is represented as a marker. In the event a location point is rendered more than once (i.e., markers overlap), either by the same object or by different objects, the marker appears just once, but information about each instance is collected and presented in that marker’s hover/balloon text.

Each reported location is also represented as a marker, but rendering is separate from stop locations. When reported locations overlap, handling is the same as described above.

The Settings operation in the results panel title bar provides additional options. See Map Settings for more information.

The map view can be moved around the Smartbench frame by dragging from the title bar or by using “move” operations on the title bar. Resizing is accomplished by dragging on window frame borders or using operations on the title bar. A map view can also be ‘pinned’ for possible side-by-side viewing with another map view or properties page instance. For more information about operations on the map view, see Map view operations.

In this section