treasure valley road dust study: final report - ResearchGate
treasure valley road dust study: final report - ResearchGate
treasure valley road dust study: final report - ResearchGate
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Table 4-1. (cont) GIS coverages used in TRAKER data analysis<br />
Coverage/Fields used<br />
Coverage: 2000 TDM<br />
Filename: 2000.shp<br />
Source: COMPASS<br />
Coverage/Field Description<br />
Coverage Description: Year 2000 Traffic Demand Model analysis results. The<br />
TDM uses optimization algorithms to determine how traffic flows between Traffic<br />
Analysis Zones (TAZ). Major <strong>road</strong>ways are included as individual links in the TDM<br />
coverage. Residential areas are represented by a single TAZ, with one or more links<br />
that access the larger network. i.e individual residential streets are not represented.<br />
This coverage is used to associate TRAKER data to the major streets in the traffic<br />
demand network.<br />
Data Fields Used<br />
Field Description<br />
A, B The A and B fields correspond to node ID numbers within the network. Specifying<br />
A and B uniquely specifies a link in the TDM. Note that individual links only<br />
support traffic flow in one direction. Thus, it is possible to have two links between<br />
any two nodes, one per direction of travel.<br />
Speed (mph)<br />
Specifies the vehicle speed in miles per hour on a particular link.<br />
FTYPE A number between 1 and 20 that assigns a <strong>road</strong>way type to the link: 1-2 ?<br />
Interstate; 3-6 ? Principal Arterial; 7-10 ? Minor Arterial; 11-14 ? Collector; 15-<br />
18 ? Local; 19 ? Interstate Ramp; 20 ? Centroid Connector. A centroid connector<br />
does not necessarily correspond to an actual <strong>road</strong>, but rather is used as a surrogate<br />
for all traffic flow coming out of a TAZ.<br />
THRULANE<br />
COUNTY<br />
ADJCNT<br />
V1_1<br />
Coverage: 2010 TDM<br />
Filename: 2010.shp<br />
Source: COMPASS<br />
The number of travel lanes on the link.<br />
Specifies the County that the link is located in : 1 for Ada, 2 for Canyon.<br />
Adjusted Traffic Volume on a vehicles per average weekday basis. This field isonly<br />
active if actual traffic counts have been obtained for the link. Note that the total<br />
number of vehicles traversing a link is <strong>report</strong>ed. Thus, to obtain the traffic volume<br />
on a per lane basis, you must divide ADJCNT by the THRULANE field.<br />
Traffic Volume in average vehicles per weekday obtained from TDM analysis<br />
results. The total number of vehicles traversing a link is <strong>report</strong>ed. Thus, to obtain<br />
the traffic volume per lane, you must divide V1_1 by the THRULANE field.<br />
Coverage Description: Year 2010 Traffic Demand Model projected analysis<br />
results. The format for this data file is the same as for the 2000 TDM coverage<br />
except that the ADJCNT field is not used.<br />
4-4