Various miniTraff and mapTraff graphics and screenshots

Back to the main page.

3D Map and Signal display
2D Map and Signal display
Intersection Data panel
Query Data panel
Sample Velocity diagram
Multiple Lane diagram

Below is the 3D map and signal display (CTRL-J).
Each intersection is numbered and intersection #2 (lower right intersection) is in the forefront. The phase numbers 'float' above the signals. The tetrahedrons are the vehicles. The time is shown in the upper left corner of the display. The display is very minimalist to reduce CPU and memory requirements.

The letters show the "turn preference" for each vehicle at the next intersection (L - left, R - Right, S - Straight, N - Not Applicable). The numbers show the lane that the vehicle is currently using. A trailing 'T' means that the vehicle is in a turnout or turn lane.

The map colors can be changed. The red vehicles are stopped. The cyan vehicles are moving. The yellow vehicles have just run the red light at intersection #2 and are fleeing the scene while looking in the rear view mirror. The magenta vehicles have been 'flagged' ('left turn' and 'lane #1' selected on the color dialog). This flag color overrides all other colors.

Below is the 2D map and signal display (CTRL-V).
The actual display is more legible than the JPEG below, but you get the idea. Each intersection is numbered and the signal display is looking at intersection #1 (upper right intersection). The map is tilted back 54 degrees Vertically. The colors are the same as the 3D map (described above) except for the flagged vehicles which are green.

The short street names (bbbbw, ccccs, bbbbe, ccccn) are just what I used for testing. The street name field is free form, but you'll probably want to abbreviate for space considerations on the map.

Below is a screenshot of the data entry panel for intersection and leg creation (CTRL-I).
This panel controls the timing of the lights. The blue numbers are default values from the "citYwide values" (CTRL-Y) panel. The "Mirror Phase" and "Mirror Intersection" will force a phase to light when some other phase is lit (for coordination). You can also change the intersection and phase numbers that appear on the map and signal display (shown above).

These panels are from Fluxbox (Linux) with the font set to "Easy Reading".

Below is a screenshot of query #7 entry panel (CTRL-7).
This query prints the number of cars approaching the light during the last three seconds of green and the whole of yellow. Our example query contains the following elements. (after the word "Query:" at the top of the panel shown below)

L0M0 <= K2 AND L0M1 OR L0M2 print L0M3

For this example L0 (location 0) is either street ccccn and fragment 2, or intersection 1 and phase 8 (which are two ways of specifying the same location) M0 (method 0) is qiIPGreenTime, K2 is 30 (which is 3.0 seconds), M1 is qbIPGreen, M2 is qbIPYellow and M3 is qiSFVehCount.

(qbIP stands for query, boolean, Intersection, Phase)
qbIPGreen needs (I)ntersection and (P)hase location data and returns the (b)oolean true when the light is green and false the rest of the time.
(qiSF stands for query, integer, Street, Fragment)
qiSFVehCount needs (S)treet and (F)ragment data and returns the (i)nteger vehicle count.

Below is a Velocity graph created from Report data.

The actual report consists of lines which look something like this:
       Time 294 ; Vehicle Speed 4.961621 ; Vehicle 0 ; Veh ID 0ccccn@60 ; Street ccccn ; Frag 0 ;
       Time 294 ; Vehicle Speed 5.2101116 ; Vehicle 1 ; Veh ID 0ccccn@160 ; Street ccccn ; Frag 0 ;
       Time 294 ; Vehicle Speed 6.0911074 ; Vehicle 2 ; Veh ID 0ccccn@40 ; Street ccccn ; Frag 0 ;

I used the following filter (under Linux) to create tabular data:
grep 'Vehicle 1' report.txt | cut -d " " -f 2,6 > Vehicle1.txt

And then used "ygraph" (also under Linux) to create the diagram below. You can see that Vehicle 4 passes Vehicle 3 (and therefore becomes Vehicle 3) just before time 1920. It then does the same thing to Vehicles 2 and 1 and goes on to win the race. The discontinuities at the end happen as vehicles leave the street fragment.

Below is the Lane diagram from the help menu.
All lanes are numbered inside to outside (left to right under Left-hand drive) starting from zero. miniTraff can support any number of lanes in any direction. These lanes include left turn, right turn and thru lanes.

For example one leg of an intersection might have five exclusive left turn lanes, one shared left turn lane, seven thru lanes, one shared right turn lane, and six exclusive right turn lanes. You must have at least one full length lane in a fragment. You can have a maximum of one shared left turn lane and one shared right turn lane or a single lane that is shared for both left and right turns.

Every lane has a usage percent associated with it. This is the percent of total vehicles (left + thru + right) that will use this lane. (although, thru vehicles change lanes as needed to pass slower vehicles)

Well, that's all you get here. If you want more, download and run the programs.

miniTraff and mapTraff are licensed under the Open Software License version 1.1. This software is provided under this License on an "AS IS" BASIS and WITHOUT WARRANTY, either express or implied, including, without limitation, the warranties of NON-INFRINGEMENT, MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Return to the miniTraff home page.