Wavetronix Command Translator (CMD-DT) - User Guide Manuel d'utilisateur Page 131

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 156
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 130
130 CHAPTER 11 TASKBUILDER SUB-WINDOWS
In Trip Time mappings, ALL destination columns must have a mapping from a source
column before the mapping can be accepted. e sub-window will notify you if one or
more destination columns do not have a mapping. e only necessary columns for a
trip-time calculation are the Sensor ID and Speed columns. Others can be removed by
editing the template if no mapping currently exists.
Creating a Mapping
Aer source columns are added, mappings from source to destination can be created by
one of two methods:
Select the desired name from both column lists and click the Add button.
OR
Select the desired source column then drag the cursor from the source column to the
desired destination column. A blue guideline will appear to show the mapping line as
it goes across the screen.
Aer a mapping is made, the source and destination columns will be highlighted and the
mapping line will be drawn between the two. e mapping will also be listed in the Map-
ping Pairs tree at the bottom of the screen.
Trip Time Template Sub-window
e Trip Time Template sub-window, shown in Figure 11.5, is designed to increase com-
patibility with any number of source datasets. You can decide whether to dene trip-time
routes using only sensor IDs, or a lane or approach subdivision of some kind. e template
can also be set to SmartSensor mode, and a Collector will obtain trip-time information
from Wavetronix SmartSensors. Additional names can be created that more appropriately
dene a sensor so it can be identied when creating a trip-time route.
Trip Time Template Sub-window Elements
e Trip Time Template sub-window contains the following elements:
Key Detector ID – e devices used in your collection network determine how the trip-
time routes are dened. If your device and/or data sources are Sensor Only, TaskBuilder
allows one or more sensor IDs to be assigned to a route element, and mapping is done
manually. If your device and/or data sources are Sensor + Lane/Approach, TaskBuilder
allows only one sensor to a route element, but multiple lanes or approaches to be as-
signed within that sensor. Mapping is done manually. If trac data is obtained from
a Collector appliance handling Wavetronix SmartSensors, the template can be set to
Wavetronix SmartSensor mode. e Wavetronix SmartSensor mode will automatically
congure both the template and the mappings to handle SmartSensors.
Vue de la page 130
1 2 ... 126 127 128 129 130 131 132 133 134 135 136 ... 155 156

Commentaires sur ces manuels

Pas de commentaire