SOW_Attachment_D-UTDF.pdf
PDF 9 KB Posted
- Solicitation number
- 250415
- Issued by
- Orange County, California
About this file
This is a Scope of Work attachment for the California Congestion Management Program (CMP) that establishes technical standards for traffic data collection and submission. The document specifies requirements for the Universal Traffic Data Format (UTDF) files that contractors must provide as part of the 2027 CMP traffic data collection project. Two file types are required: a volume file (VOLUME.CSV) containing 15-minute turning movement count data organized by date, time in military format, intersection ID, and directional turning movements (north, south, east, and west with left, through, and right designations); and a geometry file (LANES.CSV) containing lane group data, including the number of lanes, shared lane configurations, lane widths in feet, turning pocket storage lengths, and storage lane counts for each of the 101 CMP intersections.
The geometry file format utilizes standardized record types including "Lanes" to denote the number of lanes in each direction and turn movement, "Shared" to flag shared lane types using values 0 through 3 to indicate no turn, left turn, right turn, or both turns respectively, "Width" to specify lane widths, "Storage" to document turning pocket lengths, and "StLanes" to identify the number of storage lanes. Both files must be comma-delimited text files that can accommodate data for multiple intersections and time periods. The document provides detailed examples of properly formatted data and explains the coding conventions for recording shared lane configurations, establishing clear technical specifications that bidders must follow to ensure compatibility with Trafficware's CMP analysis system.
View the file
Other files
Show all 17
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment D
UTDF Standards
Two UTDF files are required for the CMP – a volume file and geometry file. Both are text based, and should be comma delineated. The contents of each are listed below.
Volume text file formats
Trafficware recommends the volume files to have the name VOLUME.CSV. This file can contain data for multiple intersections, time periods, and days. The first three lines are headers with information on the data contained in the file. The forth line identifies the different fields including: date, time (military format), intersection ID (should match the CMP intersection ID number), and the turning movement count. A 15-minute turning movement count data file created in UTDF looks like this:
Turning Movement Count Collected By:John Doe 15 Minute Counts
DATE,TIME,INTID,NBL,NBT,NBR,SBL,SBT,SBR,EBL,EBT,EBR,WBL,WBT,WBR
10/30/08,0600,1,5,53,19,14,13,4,55,68,7,51,44,13 10/30/08,0615,1,5,51,22,16,12,6,54,85,8,84,52,11 10/30/08,0630,1,4,25,11,18,19,10,45,78,7,50,34,23 10/30/08,0600,2,5,45,23,22,18,10,66,97,15,64,44,53 10/30/08,0615,2,4,61,25,14,12,6,55,84,7,83,51,44 10/30/08,0630,2,4,55,11,18,19,10,45,78,10,66,34,23
Geometry text file format
Trafficware recommends that geometry files be names LANES.CSV. The standard comma delineated lane file and header created by UTDF looks like this:
Lane Group Data
RECORDNAME,INTID,NBL,NBT,NBR,SBL,SBT,SBR,EBL,EBT,EBR,WBL,WBT,WBR
"Lanes",1,1,2,1,1,2,0,0,1,0,0,1,0 "Shared",1,,2,,,2,,,3,,,3, "Lanes",2,1,2,1,1,2,0,0,1,0,1,1,0 "Shared",2,,0,,,2,,,3,,,1, "Width",1,12,12,12,12,12,12,12,12,12,12,12,12 "Storage",1,150,,,150,,,,,,,, "StLanes",1,1,,,1,,,,,,,, This file can contain multiple intersections as shown above. Different intersections are indicated by different values of “INTID.” The normal columns and fields are shown in the sample file above. The “Lanes” field contains the number of lanes in the lane group.
“Shared” contains a flag describing shared lanes and is further discussed below.
“Width” includes the lane width for each lane group, in feet. “Storage” contains the length of any turning pockets, in feet. If there is no turning pocket, this field is left
Attachment D empty. “StLanes” contains the number of turning pocket (storage) lanes. This can be more or less than the number of turning lanes, but if there is a turning pocket this number must be at least 1.
The shared field uses the following values 0,1,2,3 to indicate lanes shared with no turn, left turn, right turn, and both turns, respectively. It should only be filled-in for the primary lane group for each direction. As an example, to indicate lanes of L, LT, T, R use the following:
RECORDNAME NBL NBT NBR
Lanes 1 2 1 Shared 1
As another example, to indicate lanes of L, T, TR use the following:
RECORDNAME NBL NBT NBR
Lanes 1 2 0 Shared 2
File details come from the government source that posted it. Updated .