Simply put, it monitors gps data from mobile's beacons from various locations as they pass through these locations. For example, K3QQN-9 beacons his position as he passes westbound through a stretch of I-264 near Brambleton Avenue in Norfolk. He travelling at 58 miles per hour. My station takes his direction of travel and speed and sends a "milepost" object with his information. The text frame would look like this on a home computer:

264W_X11 West Speed 58Mph Time 1800 I-264 west @ Brambleton Ave.
The translation for the above is this:

264W_X11 is the object created for this location. Interstate 264 west near exit 11.
West is the direction of travel.
Time 1800 is self explanatory.
I-264 @ Brambleton Ave is the text description of the object location.

Since I do not have a Kenwood D-700 or D7A, I do not know exactly what it looks like on those screens. If anyone can save a screen and send a pic to me via e-mail it would be appreciated.

Note that there is a one mile stretch of highway beyond a designated point where a mobile can trip the signpost. In the example above, K3QQN-9 can trigger the I-264 west @ Brambleton Avenue signpost anywhere on I-264 between Brambleon Avenue and the Berkley Bridge. Note also that this signpost is set so that only mobiles on I-264 westbound will trigger the signpost. Signpost can be set to trigger at any direction or a specific direction(s). A signpost can be set at a location BEFORE a known highway choke point to monitor speed appraching said choke point. A local example would be before a tunnel. I have signposts set to trigger only when a mobile beacons in the direction of a tunnel. Case in point if a mobile beacons on I-64 westbound in Norfolk @ 4th View St., 3 miles before the Hampton Roads
Bridge-Tunnel, UI-Signpost will send the object and text. However, another mobile beaconing eastbound leaving the tunnel on that same stretch will not trigger the signpost.

Below is a list of locations I've selected to monitor traffic: