Traffic Monitoring Guide

Chapter 4. TRAFFIC MONITORING DATA FORMATS

4.1 INTRODUCTION

This chapter provides coding instructions and detailed record formats for the traffic data to be reported to FHWA as part of each State's traffic monitoring program. ASCII text files are used for both the historical fixed-width column format and the new pipe-delimited format.

Data formats are provided for two types of data:

Motorized data include station description, traffic volume, vehicle speed, vehicle classification, weight, and Individual Vehicle Record (IVR) data.
Micromobility data include count station description and count data.

With the exception of motorized station data, traffic monitoring data can be submitted to FHWA's Travel Monitoring Analysis System (TMAS) using the historical fixed-width column formats. Motorized station data must be submitted using the new pipe-delimited format.

Starting with the release of this version of the Traffic Monitoring Guide, State and local agencies will also have the option to submit all traffic data using a pipe-delimited format by following the new specifications outlined in this chapter. For the pipe-delimited format, TMAS uses the pipe "|" character. State highway agencies can submit the traffic data using the fixed-width or pipe-delimited format but not both in one file.

Fields for the fixed-width column format include instructions to "blank fill" or "zero fill" those fields. This means that either leading blanks or zeros, starting at the left of the field, are to be used when the value in the field is shorter than the fixed width of that field. For example, if a field is five characters wide, and the data value is 250, then a blank-filled representation for this field is _ _ 250 and a zero-filled representation for this field is 00250.

Blank Fill or Zero Fill is not required for fields in the pipe-delimited format.

Each data record type includes many data elements. These data elements are classified as Required, Optional, or Required/Optional. A designation of Required means that a record cannot be processed by the TMAS software without these fields being supplied. An Optional designation indicates that the data are not required for the record to be processed by TMAS. Fields designated as Required/Optional could be either Required or Optional based on values used for other related fields. Also, note that data reporting requirements described in the TMG are in English units (e.g., pounds for weight, tenths of feet for distance, tenths of miles per hour for speed, and degrees Fahrenheit for temperature), not SI (i.e., metric) units.

4.1.1 Data Submission Frequency

Table 4-1 provides the recommended data submittal frequency to FHWA. This frequency applies regardless of whether files being submitted are fixed-width or pipe-delimited formats.

**Table 4-1. Data Submission Frequency**
Data Type	Submittal Frequency
Station Description Data	Annually, or when a change occurs
Traffic Volume Data	Monthly, by 25 days after close of the month for which the data were collected
Vehicle Speed Data	Monthly, by 25 days after close of the month for which the data were collected
Vehicle Classification Data	Monthly, by 25 days after close of the month for which the data were collected
Weight Data	Minimum quarterly by the 25^th of the month after the end of the quarter or, with recommended monthly submissions 25 days after the close of the month for which the data were collected
IVR Data	Data type submissions follow the above timelines
Micromobility Data	Minimum quarterly by the 25th of the month after the end of the quarter

States should submit all data files to FHWA through TMAS via the User Profile and Access Control System (UPACS). States should contact their State FHWA Division Offices for further instructions regarding UPACS.

All data should be in the record formats described in this chapter and quality controlled to ensure it truly represents travel at the given location for that time period. If the files are large, it is preferable that a file compression program be used to condense them. For further information, contact the FHWA Office of Highway Policy Information Travel Monitoring and Surveys Division (https://www.fhwa.dot.gov/policyinformation/).

4.1.2 File Naming Recommendations

An example file naming convention for traffic monitoring data is the following:

ssabcxyzmmyyyy.TYP

Where:

ss = State FIPS code

abcxyz = traffic counting station ID (may be omitted if file contains more than one site's data) mm = month of year

yyyy = year of data

TYP = type of data using the following three-character names:

Motorized Data
STA = station description data
VOL = traffic volume data
SPD = speed data
CLA = axle classification data
LEN = length classification data
WGT = weight data
IVR = Individual Vehicle Record data
Micromobility d Data
SNM = count station data
VNM = count data

FHWA recommends the use of consistent file naming conventions as this helps identify files, helps States and local public agencies perform quality assurance testing of the data they are utilizing, and provides an easy mechanism for identifying the content of files when transferring data to users. However, States are not required to use this example file naming convention. Including the TMG format information in the filename is also recommended (e.g., including "FMT2022" for data in the TMG 2022 format).

4.2 STATION DESCRIPTION DATA FORMAT (PIPE DELIMITED ONLY)

Prior to the 2022 version of the TMG, the traffic monitoring station format used a fixed-width field format where the length of each data field was a predetermined number of characters. From the 2022 version (this edition) forward, the traffic monitoring station data format requires variable-length fields using a pipe-delimited format with the pipe, also known as the vertical bar symbol (|), as the delimiter.

The TMG will continue to support both fixed-width and pipe-delimited records for most record types. The exception is the Station Description record for motorized data, which must be a pipe-delimited record. Other record types can be either fixed width or pipe delimited.

The Station Description record format is needed for reporting all motorized data. If a Station Description record is omitted, no other motorized data will be processed by TMAS. The Station Description TMAS table contains one record per traffic monitoring station, per direction, per lane (unless lanes are combined by the data collection device), per year. However, updated station records can be submitted at any time during the year.

The TMAS software retains all approved station records as of December 31^st of each year. FHWA recommends that a yearly review of all station record fields be conducted to ensure the records are current and reflect which stations are being used to collect data.

4.2.1 File Naming Recommendation

It is recommended that the file extension .STA be used for all Station Description data files. The filename should be descriptive to facilitate the deciphering of the file and its contents.

An example file naming convention for the Station Description record is:

ssabcxyzmmyyyy.STA

4.2.2 Station Description — Pipe-Delimited Format

Table 4-2 summarizes the Station Description record using the pipe-delimited format.

**Table 4-2. Station Description Record**
Field	Width	Description	Type	Importance
1	1	Record Type (RT)	Alphanumeric	Required
2	2	State FIPS Code (SFIPS)	Alphanumeric	Required
3	20	Station ID (ID)	Alphanumeric	Required
4	1	Direction of Travel (DIR)	Integer	Required
5	1	Lane of Travel (LN)	Integer	Required
6	4	Year of Data (YR)	Integer	Required
7	2	Functional Classification (FC)	Alphanumeric	Required
8	1	Number of Lanes in Direction Indicated (NL)	Integer	Required
9	2	Vehicle Classification Groupings (VCG)	Integer	Req./Opt.
10	1	Calibration of Weighing System (CWS)	Alphanumeric	Req./Opt.
11	1	Type of Sensor (TS1)	Alphanumeric	Required
12	1	Second Type of Sensor (TS2)	Alphanumeric	Optional
13	11	Latitude (LAT)	Decimal	Required
14	11	Longitude (LONG)	Decimal	Required
15	20	Previous Station ID (PREVID)	Alphanumeric	Optional
16	4	Year Station Established (YREST)	Integer	Required
17	4	Year Station Discontinued (YRDIS)	Integer	Optional
18	3	County FIPS Code (CFIPS)	Alphanumeric	Required
19	1	National Highway System (NHS)	Alphanumeric	Required
20	2	Posted Route Signing (PRS)	Integer	Required
21	8	Posted Route Sign Number (PRSN)	Alphanumeric	Required
22	50	Station Location Description (STALOC)	Alphanumeric	Required

Note: Fields designated as Required must be reported.

Fields designated as Optional are not required to be reported.

Fields designated as Required/Optional could be either required or optional based on values used for other related fields.

The fields for the Station Description record are:

Record Type – Required
S = station description record (Code the letter "S" in the first column.)

State FIPS Codes – Required

Table 4-3 lists the codes for each lane.

**Table 4-3. FIPS State Codes**
State	Code	State	Code	State	Code
Alabama	1	Maine	23	Pennsylvania	42
Alaska	2	Maryland	24	Rhode Island	44
Arizona	4	Massachusetts	25	South Carolina	45
Arkansas	5	Michigan	26	South Dakota	46
California	6	Minnesota	27	Tennessee	47
Colorado	8	Mississippi	28	Texas	48
Connecticut	9	Missouri	29	Utah	49
Delaware	10	Montana	30	Vermont	50
D.C.	11	Nebraska	31	Virginia	51
Florida	12	Nevada	32	Washington	53
Georgia	13	New Hampshire	33	West Virginia	54
Hawaii	15	New Jersey	34	Wisconsin	55
Idaho	16	New Mexico	35	Wyoming	56
Illinois	17	New York	36	Puerto Rico	72
Indiana	18	North Carolina	37	American Samoa	60
Iowa	19	North Dakota	38	Guam	66
Kansas	20	Ohio	39	Northern Mariana Islands	69
Kentucky	21	Oklahoma	40	Virgin Islands of the U.S.	78
Louisiana	22	Oregon	41

Canadian Provinces may use TMAS with the following codes (based on the LTPP):

Province	Code	Province	Code	Province	Code
Alberta	81	Nova Scotia	86	Yukon	91
British Columbia	82	Ontario	87	Northwest Territory	92
Manitoba	83	Prince Edward Island	88	Labrador	93
New Brunswick	84	Quebec	89	Nunavut	94
Newfoundland	85	Saskatchewan	90

Station Identification – Required
Alphanumeric designation for the station where the data are collected. Station identification field entries must be identical in all records for a given station. Differences in characters, including spaces, hyphens, etc., prevent a proper match.

Direction of Travel – Required

Combined directions are permitted for volume stations only. Table 4-4 lists the codes for each direction. There should be a separate record for each direction of travel for the station.

**Table 4-4. Direction of Travel Codes**
Code	Direction
1	North
2	Northeast
3	East
4	Southeast
5	South
6	Southwest
7	West
8	Northwest
9	North-South or Northeast-Southwest combined (volume stations only)
0	East-West or Southeast-Northwest combined (volume stations only)

Lane of Travel – Required

Each lane can be considered separately (1-9) or all lanes in each direction can be combined (0). Table 4-5 lists the codes for each lane. Figure 4-1 shows an example of direction and lane coding.

All data for volume, class, and speed should be reported with the same resolution of lane/direction or lanes combined/direction as specified in the station record.

All data in either weight or IVR must be submitted by individual lane and by individual direction.

**Table 4-5. Lane of Travel Codes**
Code	Lane
0	Data with lanes combined
1	Outside (rightmost) lane
2-9	Other lanes

Note: The Station ID, Direction of Travel, and Lane of Travel make up the Station Code. There should be one Station Description record per Station Code. Stations can be either by lane or with lanes combined by direction, but not both.

Source: Federal Highway Administration.

Figure 4-1. Direction and Lane Code Example

Year of Data – Required
The four-digit year in which the data were collected.

Functional Classification – Required

One of the functional classification codes listed in Table 4-6 concatenated with either an "R" for rural or "U" for urban. For example, a code of 2R indicates a Rural Principal Arterial – Other Freeways and Expressways.

**Table 4-6. Functional Classification Codes**
Code	Functional Classification*
1	Interstate
2	Principal Arterial – Other Freeways and Expressways
3	Principal Arterial – Other
4	Minor Arterial
5	Major Collector
6	Minor Collector
7	Local

* Note that the Micromobility Station record has two additional functional classification options (i.e., 8 and 9). See Table 4-37

Number of Lanes in Direction Indicated – Required
The number of lanes in one direction at the site regardless of the number of lanes being monitored. Use 9 if there are more than eight lanes.

Vehicle Classification Groupings – Required/Optional

The total number of classes in the vehicle classification system being used as well as how vehicles are grouped together in those classes in relation to the 13 FHWA categories. The recommended default value is 13, which indicates that the standard FHWA 13-vehicle category classification system (see Appendix A) is being used. Other vehicle classification systems may be based on the HPMS or specific State classification schema defined in the State's Traffic Monitoring System (TMS) documentation. The value determines the number of count fields needed on the Vehicle Classification record (see Section 4.5). In Table 4-7, the numbers in parentheses refer to the 13 FHWA classes and describe how the FHWA classes relate to the classes being reported.

**Table 4-7. Values Corresponding to Vehicle Classification Groupings**
Value	Typology	How Vehicles are Classified
02	Two class groups	(classes 1-3) vehicles (classes 4-13) vehicles
03	Three class groups	(classes 1-3) vehicles (classes 4-7) single-unit vehicles (classes 8-13) combination vehicles
04	Four class groups	(classes 1-3) vehicles (classes 4-7) single-unit vehicles (classes 8-10) single-trailer combination vehicles (classes 11-13) multiple-trailer combination vehicles
44	Four class groups	(class 1) motorcycles (classes 2-3) two-axle, four-tire vehicles (classes 4-7) single-unit vehicles (classes 8-13) combination vehicles
05	Five class groups	(class 1) motorcycles (classes 2-3) two-axle, four-tire vehicles (classes 4-7) buses and single-unit vehicles (classes 8-10) single-trailer combination vehicles (classes 11-13) multiple-trailer combination vehicles
06	Six class groups	(class 1) motorcycles (classes 2-3) two-axle, four-tire vehicles (class 4) buses (classes 5-7) single-unit vehicles (classes 8-10) single-trailer combination vehicles (classes 11-13) multiple-trailer combination vehicles
66	Six class groups (HPMS definition)	(class 1) motorcycles (class 2) passenger cars (class 3) light-duty trucks (class 4) buses (classes 5-7) single-unit vehicles (classes 8-13) combination vehicles
07	Seven class groups	(class 1) motorcycles (class 2) passenger cars (class 3) light-duty trucks (class 4) buses (classes 5-7) single-unit vehicles (classes 8-10) single-trailer combination vehicles (classes 11-13) multiple-trailer combination vehicles
13	Thirteen class groups	FHWA's standard 13 class system
14	Fourteen class groups	FHWA's standard 13 class system plus one group*
15	Fifteen class groups	FHWA's standard 13 class system plus two groups*
Other Positive Integers		number of classes (unsupported by TMAS software)

*Note: For class 14 or 15 vehicles – use either of these two classes for vehicles that may not be classified, have multiple configurations, or specific for vehicles that need to be kept separate from other classes (e.g., special purpose vehicles).

Calibration of Weighing System – Required/Optional
Code the method used to calibrate the weighing system, e.g., comparing weigh-in-motion and weights from static scales. At a minimum, yearly calibration is recommended, and maybe more often depending upon the site, sensors, equipment, and array used.

A = ASTM Standard E1318 (yearly)

B = Subset of ASTM Standard E1318 (yearly)

C = Combination of test trucks and trucks from the traffic stream (but not ASTM E1318) (yearly)

D = Other sample of trucks from the traffic stream (yearly)

M = Statistical average of the steering axle of class nines (yearly)

R = LTPP Calibration Method (yearly)

S = Static calibration (yearly)

T = Test trucks only (yearly)

U = Uncalibrated

Z = Other method (yearly)
Type of Sensor – Required
Code the type of sensor used for traffic detection.

A = Automatic vehicle identification (AVI)

B = Bending plate

C = Capacitance strip

D = Capacitance mat/pad

E = Load cells (hydraulic or mechanical)

F = Fiber optic

G = Strain gauge or other sensors mounted on bridge components

H = Human observation (manual)

I = Infrared

J = In-line strain gauge load cell

K = Laser/Lidar

L = Inductive loop

M = Magnetometer

P = Piezoelectric

Q = Quartz piezoelectric

R = Road tube

S = Sonic/acoustic

T = Tape switch

U = Ultrasonic

V = Video image

W = Microwave (radar)

X = Radio wave (radar)

Y = Segmented strain gauge

Z = Other
Second Type of Sensor – Optional
If there are two types of sensors at the station, code the second using the same codes as Type of Sensor. Otherwise, code N for none.
Latitude – Required
Latitude of the station location on the centerline of the roadway using decimal degree coordinates. If the value is 039.178 412 (Illinois), then the field is coded as |39.178412|. It is recommended to provide a resolution to the 6^th decimal degree.
Longitude – Required
Longitude of the station location on the centerline of the roadway using decimal degree coordinates. If the value is -88.352 543 (Illinois), then the field is coded as |-88.352543|. It is recommended to provide a resolution to the 6^th decimal degree.
Previous Station ID – Optional
If the station replaces another station, give the station ID that was used previously.
Year Station Established – Required
The four-digit year that the station was first established.
Year Station Discontinued – Optional
The four-digit year that the station was permanently discontinued or abandoned.
County FIPS Code – Required
The three-digit FIPS county code (see Federal Information Processing Standards Publication 6, Counties of the States of the United States).
National Highway System – Required
N = No, not on National Highway System

Y = Yes, on National Highway System

Posted Route Signing – Required

This is the same as Route Signing in HPMS Field Manual. Table 4-8 lists the possible codes.

**Table 4-8. Posted Route Signing Codes**
Code	Description
1	Not signed
2	Interstate
3	U.S.
4	State
5	Off-Interstate Business Marker
6	County
7	Township
8	Municipal
9	Parkway Marker or Forest Route Marker
10	None of the above

Posted Route Signed Number – Required
The route number of the principal route on which the station is located. This is the same as Signed Route Number in HPMS Field Manual.

If the station is located on a city street, zero-fill this field.
Station Location Description – Required
This is an English text entry field. For stations located on a numbered route, enter the name of the nearest major intersecting route, State border, or landmark on State road maps and the distance and direction of the station from that landmark to the station (e.g., "12 miles south of the Kentucky border"). If the station is located on a city street, enter the city and street name. Abbreviate if necessary. Left justify this field.

No pipe characters are permitted in the Station Location Description field.

Examples

Station Description Record Examples

Delimited Station Data Format

RT|SFIPS|ID|DIR|LN|YR|FC|NL|VCG|CWS|TS1|TS2|LAT|LONG|PREVID|YREST|YRDIS|CFIPS|NHS|PRS|PRSN|STALOC

Example for a Volume Station (4-lane site with all directions and lanes combined)

S|17|1810A|9|0|2020|1R|2|||L||41.883650|-87.896019||2001||35|Y|2|0|.6 miles east of milepost 105 interchange

Example for a Classification Station (8-lane site with lanes combined)

S|17|1811B|1|0|2020|1R|4|13|P|L||40.903984|-88.908715||1945||49|Y|1|70|.5 miles past Steven City near County Line Road

S|17|1811B|5|0|2020|1R|4|13|P|L||40.903984|-88.908715||1945||49|Y|1|70|.5 miles past Steven City near County Line Road

Example for a Classification Station (4-lane site with lanes combined and a more-than-8-digit station ID)

S|28|KLM908792|1|0|2021|3U|2|13|A|K||39.067471|-77.114321||1966||31|Y|9||0.5 miles south of Veirs Mill Road

S|28|KLM908792|5|0|2021|3U|2|13|A|K||39.067471|-77.114321||1966||31|Y|9||0.5 miles south of Veirs Mill Road

Example for a Weight Station (2-lane site)

S|17|18142C|3|1|2020|5R|1|13|A|Q|L|39.359508|-88.692127||1965||49|N|6|708|.7 miles past Steven City near Route 16

S|17|18142C|7|1|2020|5R|1|13|A|Q|L|39.359508|-88.692127||1965||49|N|6|708|.7 miles past Steven City near Route 16

A double pipe symbol || means a missing value for that field

4.3 TRAFFIC VOLUME DATA FORMAT (FIXED WIDTH OR PIPE DELIMITED)

One record is used for each calendar day for which traffic monitoring data are being submitted. Each record contains a field for traffic volume occurring during each of the 24 hours of the day. Partial day data is fully acceptable with this format-meaning if there is only 8 hours of data for the given day, sending in those 8 valid hours is recommended. Full days of data are no longer required.

The 2022 TMG offers additional formatting flexibility to report traffic volume data. States and other agencies can submit traffic volume data to FHWA's TMAS system via either the historical fixed-width format or the new pipe-delimited format.

Up to 20-digits can be used for station IDs. For the fixed-width format, the station ID field needs to be right-justified and padded with zeros.

4.3.1 File Naming Recommendation

It is recommended that the file extension .VOL be used for all Volume data files. The filename should be descriptive to facilitate the deciphering of the file format and its contents.

An example file naming convention for the Traffic Volume record is:

ssabcxyzmmyyyy.VOL

4.3.2 Traffic Volume Data – Fixed-Width Format

With the historical fixed-width format, all numeric fields should be right-justified and padded with blanks. Blank fill fields for which no data are being reported. Table 4-9 summarizes the Traffic Volume record using the fixed-width format.

**Table 4-9. Traffic Volume Record – Fixed-Width Format**
Field	Columns	Width	Description	Type	Importance
1	1	1	Record Type (RT)	Alphanumeric	Required
2	2-3	2	State FIPS Code (SFIPS)	Integer	Required
3	4-5	2	Functional Classification (FC)	Alphanumeric	Required
4	6-25	20	Station Identification (ID)	Alphanumeric	Required
5	26	1	Direction of Travel (DIR)	Integer	Required
6	27	1	Lane of Travel (LN)	Integer	Required
7	28-31	4	Year of Data (YR)	Integer	Required
8	32-33	2	Month of Year (MOY)	Integer	Required
9	34-35	2	Day of Month (DOM)	Integer	Required
10	36	1	Day of Week (DOW)	Integer	Required
11	37	1	Restrictions (R)	Integer	Required
12	38	1	Time Increment (TI)	Alphanumeric	Optional
13 – 36	39-158	5	Hourly Traffic Volume Counted, see Table 4-10	Integer	Optional

Note: Fields designated as Required must be reported.

Fields designated as Optional are not required to be reported.

Fields designated as Required/Optional could be either required or optional based on values used for other related fields.

The Hourly Traffic Volume record is defined as follows (note that the data items used in both the Hourly Traffic Volume record and the Station Description record are not redefined below, but simply referenced to the earlier definitions in Section 4.2):

Record Type (Column 1) – Required

3 = Traffic volume record (Code the value "3" in the first column.)
State FIPS Code (Columns 2-3) – See Section 4.2, Field #2. – Required

Functional Classification Code (Columns 4-5) – See Section 4.2, Field #7. – Required

Station Identification (Columns 6-25) – See Section 4.2, Field #3. – Required

Direction of Travel (Column 26) - See Section 4.2, Field #4. – Required

Lane of Travel (Column 27) – See Section 4.2, Field #5. – Required

Year of Data (Columns 28-31) – The four-digit year when the data were collected. See Section 4.2, Field #6. – Required
Month of Year (Columns 32-33) – Required
01 = January

02 = February

03 = March

04 = April

05 = May

06 = June

07 = July

08 = August

09 = September

10 = October

11 = November

12 = December
Day of Month (Columns 34-35) – Required
The two-digit day of the month when data were collected.
Day of Week (Column 36) – Required
1 = Sunday

2 = Monday

3 = Tuesday

4 = Wednesday

5 = Thursday

6 = Friday

7 = Saturday
Restrictions (Column 37) – Required
0 = no restrictions

1 = construction or other activity affected traffic flow, traffic pattern not impacted

2 = traffic counting device problem (e.g., malfunction or overflow)

3 = weather affected traffic flow, traffic pattern not impacted

4 = construction or other activity affected traffic flow, traffic pattern impacted

5 = weather affected traffic flow, traffic pattern impacted

6 = none-regular event/trend

7 = special event one day

8 = special event more than one day
Time Increment (Column 38) – Optional
A 60-minute time interval is assumed if this column is left blank. This field can be used to designate either 5-minute or 15-minute binned volume data.

For 15-minute binned intervals of volume data use the following:
- Code 1 for the hourly interval 0.0-14.999
- Code 2 for the hourly interval 15.0-29.999
- Code 3 for the hourly interval 30.0-44.999
- Code 4 for the hourly interval 45.0-59.999

For 5-minute binned intervals of volume data use the following:

Code A for the hourly interval 0.0-4.999
Code B for the hourly interval 5.0-9.999
Code C for the hourly interval 10.0-14.999
Code D for the hourly interval 15.0-19.999
Code E for the hourly interval 20.0-24.999
Code F for the hourly interval 25.0-29.999
Code G for the hourly interval 30.0-34.999
Code H for the hourly interval 35.0-39.999
Code I for the hourly interval 40.0-44.999
Code J for the hourly interval 45.0-49.999
Code K for the hourly interval 50.0-54.999
Code L for the hourly interval 55.0-59.999

60-Minute Traffic Volume Counted, see Table 4-10 (Columns 39-158) – Optional
15-Minute Traffic Volume Counted, see examples with each hour having sub-hour parts for each line (4 parts for 15-minute intervals) – Optional

5-Minute Traffic Volume Counted, examples with each hour having sub-hour parts for each line (12 parts for 5-minute intervals) – Optional

If the data are missing, blank fill the appropriate columns.

**Table 4-10. Time Covered Fields – 60-Minute Data**
Field	Columns	Width	Description	Type	Importance
13	39-43	5	Traffic Volume Counted, after 00:00 – to 01:00 (BIN1)	Integer	Optional
14	44-48	5	Traffic Volume Counted, after 01:00 – to 02:00 (BIN2)	Integer	Optional
…	…	…	…	…	…
36	154-158	5	Traffic Volume Counted, after 23:00 – to 24:00 (BIN24)	Integer	Optional

An example Traffic Volume record is shown in Table 4-11.

Table 4-11. Traffic Volume Record Example
(60-minute Time Interval – 4 Lanes with All Lanes and Directions Combined)
Column Number:	1	2-3	4-5	6-25	26	27	28-31	32-33	34-35	36	37	38
Content Example:	3	17	2R	JacksonRoad1710A1234	9	0	2012	04	25	4	0	Blank

continued

Column Number:	39-43	44-48	49-53	54-58	59-63	64-68	69-73	74-78	79-83	84-88	89-93	94-98	99-103
Content Example:	00046	00022	00014	00013	00029	00030	00075	00136	00179	00218	00264	00293	00322

continued

Column Number:	104-108	109-113	114-118	119-123	124-128	129-133	134-138	139-133	144-148	149-153	154-158
Content Example:	00401	00439	00366	00261	00202	00143	00098	00054	00022	00019	00008

4.3.3 Traffic Volume Data – Pipe-Delimited Format

State highway agencies can also submit traffic volume data using the pipe-delimited format. The key difference between the fixed-width format and the pipe-delimited format is that with the pipe-delimited file, data elements no longer need to match the starting and ending columns. Length of data elements can be equal or shorter than the specified lengths. The field order for the pipe-delimited format is identical to the order for the fixed-width format (see Table 4-9). The difference in this format is that the fields are separated by a pipe symbol (|) instead of beginning in specified columns. Example records in this format are provided below. Given it is less demanding on the format, States are encouraged to use the pipe-delimited format for volume data recording and reporting.

Examples

Delimited Volume Record Format

RT|SFIPS|FC|ID|DIR|LN|YR|MOY|DOM|DOW|R|TI|BIN1|BIN2|BIN3|BIN4|BIN5|BIN6|BIN7|BIN8|BIN9|BIN10|BIN11|BIN12|BIN13|BIN14|BIN15
|BIN16|BIN17|BIN18|BIN19|BIN20|BIN21|BIN22|BIN23|BIN24

Example for 60-Minute Volume with 2 directions

3|26|1U|xyz123|3|1|2020|6|23|3|0||100|88|76|40|20|32|120|200|300|260|232|200|248|262|312|400|500|372|360|292|248|196|132|112

3|26|1U|xyz123|7|1|2020|6|23|3|0||130|88|76|40|20|32|120|200|300|260|232|200|248|262|312|400|500|372|360|292|248|196|132|112

Example for 15-Minute Volume with 2 directions

3|26|1U|xyz123|3|1|2020|6|23|3|0|1|25|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|26|1U|xyz123|3|1|2020|6|23|3|0|2|24|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|26|1U|xyz123|3|1|2020|6|23|3|0|3|23|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|26|1U|xyz123|3|1|2020|6|23|3|0|4|27|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|26|1U|xyz123|7|1|2020|6|23|3|0|1|32|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|26|1U|xyz123|7|1|2020|6|23|3|0|2|30|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|26|1U|xyz123|7|1|2020|6|23|3|0|3|35|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|26|1U|xyz123|7|1|2020|6|23|3|0|4|33|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|26|1U|xyz123|3|1|2020|6|24|4|0|1|21|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

Example for 5-Minute Volume with 2 directions

3|49|3U|lmnopq|3|1|2020|4|25|5|0|A|25|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|3|1|2020|4|25|5|0|B|24|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|3|1|2020|4|25|5|0|C|23|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|3|1|2020|4|25|5|0|D|27|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|3|1|2020|4|25|5|0|E|26|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|3|1|2020|4|25|5|0|F|23|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|3|1|2020|4|25|5|0|G|22|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|3|1|2020|4|25|5|0|H|28|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|3|1|2020|4|25|5|0|I|26|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|3|1|2020|4|25|5|0|J|24|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|3|1|2020|4|25|5|0|K|22|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|3|1|2020|4|25|5|0|L|26|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|7|1|2020|4|25|5|0|A|28|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|7|1|2020|4|25|5|0|B|24|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|7|1|2020|4|25|5|0|C|23|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|7|1|2020|4|25|5|0|D|22|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|7|1|2020|4|25|5|0|E|24|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|7|1|2020|4|25|5|0|F|29|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|7|1|2020|4|25|5|0|G|27|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|7|1|2020|4|25|5|0|H|25|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|7|1|2020|4|25|5|0|I|24|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|7|1|2020|4|25|5|0|J|22|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|7|1|2020|4|25|5|0|K|21|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

3|49|3U|lmnopq|7|1|2020|4|25|5|0|L|27|22|19|10|5|8|30|50|75|65|58|50|62|68|78|100|125|93|90|73|62|49|33|28

Example for 60-Minute Volume with only hours 10:00 am to 06:00 pm (8 hours) reported *

3|26|7U|abcdefg|7|4|2020|5|23|4|12|R|||||||||||24|0|6|120|100|160|480|835|1200|||||

* The double pipe symbol | | means there is a missing value.

4.4 VEHICLE SPEED DATA FORMAT (FIXED WIDTH OR PIPE DELIMITED)

The vehicle speed data file format is a variable-length record used to report the number of vehicles traveling in specified 5-mph speed bins during specified time periods. Each record can contain 1 hour of data, 15 minutes of data, or 5 minutes of data. The submitting State chooses the time interval for which data are being reported and indicates that time interval as a field in the record.

Vehicle speed records must have a minimum of 15 bins up to a maximum of 25 bins and should supply data in 5-mph speed bins as defined in the TMG. Any vehicle speed records that do not meet these specifications are purged by the TMAS software. All records should follow the record formats defined in the TMG.

When submitting data using the minimum number of speed bins (15), the first speed bin includes all vehicles traveling 20 mph or slower. The second speed bin is then defined as all vehicles traveling faster than 20 mph but less than or equal to 25 mph. The last of the fifteen speed bins is defined as all vehicles traveling faster than 85 mph.

States may also submit one or two additional speed bins for slow-traveling vehicles. States may create one additional slow-speed bin (for vehicles traveling 15 mph or slower), or two slow-speed bins (one for vehicles traveling 10 mph or slower, and the other for vehicles traveling greater than 10 mph up to 15 mph.)

Similarly, a State may create additional high-speed bins. Up to eight additional bins may be added to provide more detail on high-speed travel. The number of additional high-speed bins being reported should be indicated on the speed record. Finally, when additional high-speed bins are reported, the length of the speed record changes.

The 2022 TMG offers additional formatting flexibility to report vehicle speed data. States and other agencies can submit vehicle speed data to FHWA's TMAS system via either the historical fixed-width format or the new pipe-delimited format.

Up to 20-digits can be used for station IDs. For the fixed-width format, the station ID field needs to be right-justified and padded with zeros.

4.4.1 File Naming Recommendation

It is recommended that the file extension .SPD be used for all Speed data files. The filename should be descriptive to facilitate the deciphering of the file and its contents.

An example file naming convention for the Vehicle Speed record is:

ssabcxyzmmyyyy.SPD

4.4.2 Vehicle Speed Data – Fixed-Width Format

With the historical fixed-width format, all numeric fields should be right-justified and padded with blanks. Blank fill fields for which no data are being reported. The most critical aspect for this data format is that each of the data elements has its starting column and ending column locations. Data element sequencing must be followed. If missing data or length of a data element is shorter than specified, zeros (0) must be used to prefix the blank columns.

Table 4-12 summarizes the Vehicle Speed record fixed-width column format.

**Table 4-12. Vehicle Speed Record – Fixed-Width Format**
Field	Columns	Width	Description	Type	Importance
1	1	1	Record Type (RT)	Alphanumeric	Required
2	2-3	2	State FIPS Code (SFIPS)	Integer	Required
3	4-23	20	Station Identification (ID)	Alphanumeric	Required
4	24	1	Direction of Travel (DIR)	Integer	Required
5	25	1	Lane of Travel (LN)	Integer	Required
6	26-29	4	Year of Data (YR)	Integer	Required
7	30-31	2	Month of Year (MOY)	Integer	Required
8	32-33	2	Day of Month (DOM)	Integer	Required
9	34-35	2	Hour of Day (HOD)	Integer	Required
10	36	1	Speed Data Time Interval (I)	Integer	Optional
11	37	1	Definition of First Speed Bin (F)	Integer	Optional
12	38-39	2	Total Number of Speed Bins Reported (TN)	Integer	Optional
13	40	1	Restrictions (R)	Integer	Required
14	41-45	5	Total Interval Volume (TVOL)	Integer	Required
15	46-50	5	Bin 1 Count (BIN1)	Integer	Required
16	51-55	5	Bin 2 Count (BIN2)	Integer	Required
17	56-60	5	Bin 3 Count (BIN3)	Integer	Required
18	61-65	5	Bin 4 Count (BIN4)	Integer	Required
19	66-70	5	Bin 5 Count (BIN5)	Integer	Required
20	71-75	5	Bin 6 Count (BIN6)	Integer	Required
21	76-80	5	Bin 7 Count (BIN7)	Integer	Required
22	81-85	5	Bin 8 Count (BIN8)	Integer	Required
23	86-90	5	Bin 9 Count (BIN9)	Integer	Required
24	91-95	5	Bin 10 Count (BIN10)	Integer	Required
25	96-100	5	Bin 11 Count (BIN11)	Integer	Required
26	101-105	5	Bin 12 Count (BIN12)	Integer	Required
27	106-110	5	Bin 13 Count (BIN13)	Integer	Required
28	111-115	5	Bin 14 Count (BIN14)	Integer	Required
29	116-120	5	Bin 15 Count (BIN15)	Integer	Required
30	121-125	5	Bin 16 Count (BIN16)	Integer	Req./Opt.
31	126-130	5	Bin 17 Count (BIN17)	Integer	Req./Opt.
32	131-135	5	Bin 18 Count (BIN18)	Integer	Req./Opt.
33	136-140	5	Bin 19 Count (BIN19)	Integer	Req./Opt.
34	141-145	5	Bin 20 Count (BIN20)	Integer	Req./Opt.
35	146-150	5	Bin 21 Count (BIN21)	Integer	Req./Opt.
36	151-155	5	Bin 22 Count (BIN22)	Integer	Req./Opt.
37	156-160	5	Bin 23 Count (BIN23)	Integer	Req./Opt.
38	161-165	5	Bin 24 Count (BIN24)	Integer	Req./Opt.
39	166-170	5	Bin 25 Count (BIN25)	Integer	Req./Opt.

Note: Fields designated as Required must be reported.

Fields designated as Optional are not required to be reported.

Fields designated as Required/Optional could be either required or optional based on values used for other related fields.

The fields for the Vehicle Speed record are defined as follows:

Record Type (Column 1) – Required
T = Vehicle Speed record
State FIPS Code (Columns 2-3) – Required

See Section 4.2, Field #2.
Station Identification (Columns 4-23) – Required

See Section 4.2, Field #3.

This field should be right-justified with unused columns zero-filled.
Direction of Travel (Column 24) – Required

See Section 4.2, Field #4.
Lane of Travel (Column 25) – Required

See Section 4.2, Field #5.

Note: The Station ID, Direction of Travel, and Lane of Travel make up the Station Code. No combined lanes are allowed. There should be one Station Description record per Station Code.
Year of Data (Columns 26-29) – Required

See Section 4.2, Field #6.
Month of Year (Columns 30-31) – Required

See Section 4.3, Field #8.
Day of Month (Columns 32-33) – Required

See Section 4.3, Field #9.
Hour of Day (Columns 34-35) – Required
The beginning of the hour in which the count was taken:
- 00 = after 00:00 to 01:00
- 01 = after 01:00 to 02:00
- …
- 22 = after 22:00 to 23:00
- 23 = after 23:00 to 24:00
Speed Data Time Interval (Column 36) – Optional
A 60-minute time interval is assumed if this column is left blank. This field can be used to designate either 15-minute or 5-minute binned speed data.

For 15-minute binned intervals of speed data use the following:
- Code 1 for the interval 0.0-14.999
- Code 2 for the interval 15.0-29.999
- Code 3 for the interval 30.0-44.999
- Code 4 for the interval 45.0-59.999
For 5-minute binned intervals of speed data use the following:
- Code A for the interval 0.0-4.999
- Code B for the interval 5.0-9.999
- Code C for the interval 10.0-14.999
- Code D for the interval 15.0-19.999
- Code E for the interval 20.0-24.999
- Code F for the interval 25.0-29.999
- Code G for the interval 30.0-34.999
- Code H for the interval 35.0-39.999
- Code I for the interval 40.0-44.999
- Code J for the interval 45.0-49.999
- Code K for the interval 50.0-54.999
- Code L for the interval 55.0-59.999
Definition of First Speed Bin (Column 37) – Optional
If this field is left blank, the first speed bin is assumed to be defined as being all vehicles traveling equal to or slower than 20 mph.

If the State wishes to submit data that provide more detail of vehicles traveling at slower speeds, it may supply data in one or two additional slow speed bins. A value of "1" is indicates that the first speed bin is defined as "all vehicles traveling at equal to or slower than 15 mph." A value of "2" indicates that the first speed bin submitted will contain "all vehicles traveling at equal to or slower than 10 mph" while the second bin will be defined as "all vehicles traveling faster than 10 mph and at equal to or slower than 15 mph."

Total Number of Speed Bins Reported (Columns 38-39) – Optional

If this field is left blank the record should contain data in 15 speed bins; the first bin is defined as all vehicles traveling 20 mph or slower, and the last bin is defined as all vehicles traveling faster than 85 mph. The length of the record for 15 speed bins is 120 columns wide.

If the State is supplying data in additional speed bins, indicate the total number of speed bins being reported. This value is used to determine the correct record length (Table 4-13).

When used in conjunction with Definition of First Speed Bin (Column 37) it is possible to determine the definition of all speed bins being submitted.

**Table 4-13. Total Number of Speed Bins**
Total Number of Speed Bins (Defined in Columns 24-25)	Record Length (Number of Columns)
15	120
16	125
17	130
18	135
19	140
20	145
21	150
22	155
23	160
24	165
25	170

Restrictions (Column 40) – Required
0 = no restrictions

1 = construction or other activity affected traffic flow, traffic pattern not impacted

2 = traffic counting device problem (e.g., malfunction or overflow)

3 = weather affected traffic flow, traffic pattern not impacted

4 = construction or other activity affected traffic flow, traffic pattern impacted

5 = weather affected traffic flow, traffic pattern impacted

6 = none-regular event/trend

7 = special event one day

8 = special event more than one day
Total Interval Volume (Columns 41-45) – Optional
This numeric field is the total traffic volume for the interval covering all speed bins. For example, for the interval of 0.0-14.999 for hour 1 of April 11, 2020, the Volume data are total number of vehicles counted in all the speed bins during that time period. If all are measured and counted, this number will be equal to the summation of counts for all speed bins for that time interval. If the total volume is not collected, leave this field blank.

The following speed count fields are numeric fields with the traffic volume by vehicle speed for each interval being reported. Traffic volumes in each speed bin for each reporting interval should be entered as zero-filled or blank-filled right-justified integers in the appropriate columns.
Bin 1 Count (Columns 46-50) – Required
Bin 1 includes the number of vehicles in the slowest speed range being submitted. Right justify the integer volume number in the data entry field. The default condition for this speed bin is "all vehicles traveling equal to or slower than 20 mph." If a different definition is used, Definition of First Speed Bin (Column 37) should be used to define this speed bin. If there are no vehicles observed in this speed range during the time period being reported, enter "0", not " " (blank), to indicate that there are no vehicles in this speed range, and enter "0" similarly for each speed bin below.
Bin 2 Count (Columns 51-55) – Required
Bin 2 includes the number of vehicles in the second slowest speed range being submitted. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 3 Count (Columns 56-60) – Required
Bin 3 includes the number of vehicles in the third speed range being submitted. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 4 Count (Columns 61-65) – Required
Bin 4 includes the number of vehicles in the fourth speed range being submitted. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 5 Count (Columns 66-70) – Required
Bin 5 includes the number of vehicles in the fifth speed range being submitted. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 6 Count (Columns 71-75) – Required
Bin 6 includes the number of vehicles in the sixth speed range being submitted. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 7 Count (Columns 76-80) – Required
Bin 7 includes the number of vehicles in the seventh speed range being submitted. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 8 Count (Columns 81-85) – Required
Bin 8 includes the number of vehicles in the eighth speed range being submitted. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 9 Count (Columns 86-90) – Required
Bin 9 includes the number of vehicles in the ninth speed range being submitted. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 10 Count (Columns 91-95) – Required
Bin 10 includes the number of vehicles in the tenth speed range being submitted. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 11 Count (Columns 96-100) – Required
Bin 11 includes the number of vehicles in the eleventh speed range being submitted. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 12 Count (Columns 101-105) – Required
Bin 12 includes the number of vehicles in the twelfth speed range being submitted. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 13 Count (Columns 106-110) – Required
Bin 13 includes the number of vehicles in the thirteenth speed range being submitted. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 14 Count (Columns 111-115) – Required
Bin 14 includes the number of vehicles in the fourteenth speed range being submitted. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 15 Count (Columns 116-120) – Required
Bin 15 includes the number of vehicles in the fifteenth speed range being submitted. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 16 Count (Columns 121-125) – Required/Optional
Bin 16 includes the number of vehicles in the sixteenth speed range being submitted. It is used only when a State submits data in additional speed bins beyond the 15 required by FHWA. If this bin is used, Field 12 (Columns 38-39) should contain a value equal to or greater than 16. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0".
Bin 17 Count (Columns 126-130) – Required/Optional
Bin 17 includes the number of vehicles in the seventeenth speed range being submitted. It is used only when a State submits data in additional speed bins beyond the 15 required by FHWA. If this bin is used, Field 12 (Columns 38-39) should contain a value equal to or greater than 17. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 18 Count (Columns 131-135) – Required/Optional
Bin 18 includes the number of vehicles in the eighteenth speed range being submitted. It is used only when a State submits data in additional speed bins beyond the 15 required by FHWA. If this bin is used, Field 12 (Columns 38-39) should contain a value equal to or greater than 18. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 19 Count (Columns 136-140) – Required/Optional

Bin 19 includes the number of vehicles in the nineteenth speed range being submitted. It is used only when a State submits data in additional speed bins beyond the 15 required by FHWA. If this bin is used, Field 12 (Columns 38-39) should contain a value equal to or greater than 19. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."

Bin 20 Count (Columns 141-145) – Required/Optional
Bin 20 includes the number of vehicles in the twentieth speed range being submitted. It is used only when a State submits data in additional speed bins beyond the 15 required by FHWA. If this bin is used, Field 12 (Columns 38-39) should contain a value equal to or greater than 20. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 21 Count (Columns 146-150) – Required/Optional
Bin 21 includes the number of vehicles in the twenty-first speed range being submitted. It is used only when a State submits data in additional speed bins beyond the 15 required by FHWA. If this bin is used, Field 12 (Columns 38-39) should contain a value equal to or greater than 21. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 22 Count (Columns 151-155) – Required/Optional
Bin 22 includes the number of vehicles in the twenty-second speed range being submitted. It is used only when a State submits data in additional speed bins beyond the 15 required by FHWA. If this bin is used, Field 12 (Columns 38-39) should contain a value equal to or greater than 22. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 23 Count (Columns 156-160) – Required/Optional
Bin 23 includes the number of vehicles in the twenty-third speed range being submitted. It is used only when a State submits data in additional speed bins beyond the 15 required by FHWA. If this bin is used, Field 12 (Columns 38-39) should contain a value equal to or greater than 23. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 24 Count (Columns 161-165) – Required/Optional
Bin 24 includes the number of vehicles in the twenty-fourth speed range being submitted. It is used only when a State submits data in additional speed bins beyond the 15 required by FHWA. If this bin is used, Field 12 (Columns 38-39) should contain a value equal to or greater than 24. Right justify the integer

volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."
Bin 25 Count (Columns 166-170) – Required/Optional
Bin 25 includes the number of vehicles in the twenty-fifth speed range being submitted. It is used only when a State submits data in additional speed bins beyond the 15 required by FHWA. If this bin is used, Field 12 (Columns 38-39) should contain a value equal to or greater than 25. Right justify the integer volume number in the data entry field. If there are no vehicles observed in this speed range during the time period being reported, enter "0."

Example Vehicle Speed records are shown in Table 4-14 through Table 4-16.

**Table 4-14. Speed Record Example (15 Bins, 2 lanes, with Lanes or Directions Not Combined, at 5-Minute Intervals, with No Restrictions) – Fixed-Width Format**
Column Number:	1	2-3	4-23	24	25	26-29	30-31	32-33	36	37
Content 01 Example:	T	17	JacksonDouglas181141	1	1	2012	06	20	A	Blank
Content 02 Example:	T	17	JacksonDouglas181141	1	1	2012	06	20	B	Blank
Content 03 Example:	T	17	JacksonDouglas181141	1	1	2012	06	20	C	Blank
Content 04 Example:	T	17	JacksonDouglas181141	1	1	2012	06	20	D	Blank
Content 05 Example:	T	17	JacksonDouglas181141	1	1	2012	06	20	E	Blank
Content 06 Example:	T	17	JacksonDouglas181141	1	1	2012	06	20	F	Blank
Content 07 Example:	T	17	JacksonDouglas181141	1	1	2012	06	20	G	Blank
Content 08 Example:	T	17	JacksonDouglas181141	1	1	2012	06	20	H	Blank
Content 09 Example:	T	17	JacksonDouglas181141	1	1	2012	06	20	I	Blank
Content 10 Example:	T	17	JacksonDouglas181141	1	1	2012	06	20	J	Blank
Content 11 Example:	T	17	JacksonDouglas181141	1	1	2012	06	20	K	Blank
Content 12 Example:	T	17	JacksonDouglas181141	1	1	2012	06	20	L	Blank
Content 13 Example:	T	17	JacksonDouglas181141	5	1	2012	06	20	A	Blank
Content 14 Example:	T	17	JacksonDouglas181141	5	1	2012	06	20	B	Blank
Content 15 Example:	T	17	JacksonDouglas181141	5	1	2012	06	20	C	Blank
Content 16 Example:	T	17	JacksonDouglas181141	5	1	2012	06	20	D	Blank
Content 17 Example:	T	17	JacksonDouglas181141	5	1	2012	06	20	E	Blank
Content 18 Example:	T	17	JacksonDouglas181141	5	1	2012	06	20	F	Blank
Content 19 Example:	T	17	JacksonDouglas181141	5	1	2012	06	20	G	Blank
Content 20 Example:	T	17	JacksonDouglas181141	5	1	2012	06	20	H	Blank
Content 21 Example:	T	17	JacksonDouglas181141	5	1	2012	06	20	I	Blank
Content 22 Example:	T	17	JacksonDouglas181141	5	1	2012	06	20	J	Blank
Content 23 Example:	T	17	JacksonDouglas181141	5	1	2012	06	20	K	Blank
Content 24 Example:	T	17	JacksonDouglas181141	5	1	2012	06	20	L	Blank

continued

Column Number:	38-39	40	41-45	46-50	51-55	56-60	61-65	66-70	71-75	76-80	81-85
Content 01 Example:	15	0	00375	00000	00000	00000	00000	00000	00000	00000	00000
Content 02 Example:	15	0	00305	00000	00000	00000	00000	00000	00000	00000	00004
Content 03 Example:	15	0	00266	00000	00000	00000	00000	00000	00000	00000	00000
Content 04 Example:	15	0	00268	00000	00000	00000	00000	00000	00000	00000	00000
Content 05 Example:	15	0	00248	00000	00000	00000	00000	00000	00000	00000	00001
Content 06 Example:	15	0	00231	00000	00000	00000	00000	00000	00000	00000	00000
Content 07 Example:	15	0	00197	00000	00000	00000	00000	00000	00000	00000	00000
Content 08 Example:	15	0	00183	00000	00000	00000	00000	00000	00000	00000	00000
Content 09 Example:	15	0	00173	00000	00000	00000	00000	00000	00000	00000	00000
Content 10 Example:	15	0	00159	00000	00000	00000	00000	00000	00000	00000	00000
Content 11 Example:	15	0	00154	00000	00000	00000	00000	00000	00000	00000	00000
Content 12 Example:	15	0	00145	00000	00000	00000	00000	00000	00000	00000	00000
Content 13 Example:	15	0	00373	00000	00000	00000	00000	00000	00000	00000	00000
Content 14 Example:	15	0	00307	00000	00000	00000	00000	00000	00000	00000	00000
Content 15 Example:	15	0	00268	00000	00000	00000	00000	00000	00000	00000	00000
Content 16 Example:	15	0	00294	00000	00000	00000	00000	00000	00000	00000	00000
Content 17 Example:	15	0	00277	00000	00000	00000	00000	00000	00000	00000	00000
Content 18 Example:	15	0	00260	00000	00000	00000	00000	00000	00000	00000	00000
Content 19 Example:	15	0	00272	00000	00000	00000	00000	00000	00000	00000	00000
Content 20 Example:	15	0	00242	00000	00000	00000	00000	00000	00000	00000	00000
Content 21 Example:	15	0	00212	00000	00000	00000	00000	00000	00000	00000	00000
Content 22 Example:	15	0	00198	00000	00000	00000	00000	00000	00000	00000	00000
Content 23 Example:	15	0	00185	00000	00000	00000	00000	00000	00000	00000	00000
Content 24 Example:	15	0	00155	00000	00000	00000	00000	00000	00000	00000	00000

continued

Column Number:	86-90	91-95	96-100	101-105	106-110	111-115	116-120	121-125	126-130
Content 01 Example:	00007	00012	00048	00165	00086	00031	00021	00005	00000
Content 02 Example:	00005	00008	00025	00143	00079	00025	00013	00003	00000
Content 03 Example:	00003	00003	00032	00131	00058	00026	00011	00001	00001
Content 04 Example:	00002	00004	00037	00128	00043	00039	00012	00003	00000
Content 05 Example:	00001	00003	00039	00119	00039	00028	00015	00004	00000
Content 06 Example:	00002	00002	00025	00108	00042	00032	00015	00005	00000
Content 07 Example:	00000	00001	00018	00099	00035	00028	00011	00005	00000
Content 08 Example:	00000	00000	00013	00098	00032	00027	00009	00004	00000
Content 09 Example:	00000	00000	00008	00095	00031	00028	00008	00003	00000
Content 10 Example:	00000	00000	00007	00092	00028	00025	00005	00002	00000
Content 11 Example:	00000	00000	00011	00088	00025	00026	00003	00001	00000
Content 12 Example:	00000	00000	00012	00084	00021	00024	00004	00000	00000
Content 13 Example:	00008	00013	00049	00156	00087	00032	00022	00006	00000
Content 14 Example:	00006	00009	00026	00141	00082	00027	00011	00005	00000
Content 15 Example:	00002	00003	00031	00128	00061	00025	00013	00004	00001
Content 16 Example:	00000	00001	00035	00134	00065	00036	00015	00007	00001
Content 17 Example:	00000	00007	00031	00121	00058	00031	00021	00008	00000
Content 18 Example:	00000	00002	00026	00115	00055	00032	00022	00007	00001
Content 19 Example:	00000	00004	00027	00122	00056	00035	00023	00005	00000
Content 20 Example:	00000	00003	00021	00114	00049	00033	00018	00004	00000
Content 21 Example:	00000	00000	00015	00104	00048	00024	00019	00002	00000
Content 22 Example:	00000	00000	00012	00098	00047	00025	00013	00003	00000
Content 23 Example:	00000	00000	00008	00087	00051	00024	00012	00003	00000
Content 24 Example:	00000	00000	00005	00076	00044	00021	00009	00000	00000

Table 4-15. Speed Record Example (21 Bins, 4 Lanes with Lanes or Directions Not Combined at 60-Minute Interval with No Restrictions,
Total Volume Not Recorded) – Fixed Width Format
Column Number:	1	2-3	4-23	24	25	26-29	30-31	32-33	36	37	38-39
Content 01 Example:	T	17	JacksonDouglas181141	1	1	2012	06	20	Blank	1	21
Content 02 Example:	T	17	JacksonDouglas181141	1	2	2012	06	20	Blank	1	21
Content 03 Example:	T	17	JacksonDouglas181141	5	2	2012	06	20	Blank	1	21
Content 04 Example:	T	17	JacksonDouglas181141	5	1	2012	06	20	Blank	1	21

continued

Column Number:	41-45	86-90	91-95	96-100
Content 01 Example:	Blank	00005	00034	00054
Content 02 Example:	Blank	00007	00030	00046
Content 03 Example:	Blank	00010	00028	00056
Content 04 Example:	Blank	00008	00026	00036

continued

Column Number:	101-105	106-110	111-115	116-120	121-125	126-130
Content 01 Example:	00021	00015	00002	00001	00000	00000
Content 02 Example:	00024	00013	00003	00002	00000	00000
Content 03 Example:	00031	00021	00005	00004	00003	00000
Content 04 Example:	00029	00018	00003	00003	00002	00001

**Table 4-16. Speed Record Example (25 Bins, 2 Lanes with Lanes or Directions Not Combined at 60-Minute Interval) – Fixed Width Format**
Column Number:	1	2-3	4-23	24	25	26-29	30-31	32-33	34-35	36	37
Content 01 Example:	T	17	JacksonDouglas181141	3	1	2012	06	20	00	Blank	2
Content 02 Example:	T	17	JacksonDouglas181141	7	1	2012	06	20	00	Blank	2

continued

Column Number:	38-39	40	41-45	46-50	51-55	56-60	61-65	66-70	71-75	76-80	81-85	86-90	91-95
Content 01 Example:	25	0	000683	00000	00000	00000	00000	00000	00000	00000	00000	00000	00005
Content 02 Example:	25	0	000681	00000	00000	00000	00000	00000	00000	00000	00000	00000	00004

continued

Column Number:	96-100	101-105	106-110	111-115	116-120	121-125	126-130	131-135	136-140	141-145
Content 01 Example:	00014	00026	00056	00086	00109	00121	00095	00082	00042	00021
Content 02 Example:	00012	00028	00064	00085	00098	00127	00094	00081	00041	00018

continued

Column Number:	146-150	151-155	156-160	161-165	166-170
Content 01 Example:	00015	00011	00000	00000	00000
Content 02 Example:	00013	00013	00003	00000	00000

4.4.3 Vehicle Speed Data – Pipe-Delimited Format

State highway agencies can also submit vehicle speed data using the pipe-delimited format. The key difference between the fixed-width format and the pipe-delimited format is that with the pipe-delimited file, data elements no longer need to match the starting and ending columns. Length of data elements can be equal or shorter than the specified lengths. The field order for the pipe-delimited format is identical to the order for the fixed-width format (see Table 4-12). The difference in this format is that the fields are separated by a pipe symbol (|) instead of beginning in specified columns. Example records in this format are provided below. Given it is less demanding on the format, States are encouraged to use the pipe-delimited format for vehicle speed data recording and reporting.

Delimited Format Examples

Speed Data for 25 Speed Bins with Delimited Fields – Detailed

RT|SFIPS|ID|DIR|LN|YR|MOY|DOM|HOD|I|F|TN|R|TVOL|BIN1|BIN2|BIN3|BIN4|BIN5|BIN6|BIN7|BIN8|BIN9|BIN10|BIN11|BIN12|BIN13|BIN14|BIN15|BIN16

|BIN17|BIN18|BIN19|BIN20|BIN21|BIN22|BIN23|BIN24|BIN25

60-Minute Speed Data for 15 Speed Bins with 6 Lanes, No Restrictions with no Restrictions

T|54|123ABC|1|1|2021|4|25|00|||15|0|97|0|0|0|0|0|0|0|2|7|36|32|12|4|2|2|0

T|54|123ABC|1|2|2021|4|25|00|||15|0|94|0|0|0|0|0|0|0|2|7|34|31|12|4|2|2|0

T|54|123ABC|1|3|2021|4|25|00|||15|0|91|0|0|0|0|0|0|0|2|7|30|32|12|4|2|2|0

T|54|123ABC|5|1|2021|4|25|00|||15|0|109|0|0|0|1|0|0|1|8|14|33|30|15|5|2|0|0

T|54|123ABC|5|2|2021|4|25|00|||15|0|110|0|0|0|1|0|0|1|8|14|33|30|16|5|2|0|0

T|54|123ABC|5|3|2021|4|25|00|||15|0|113|0|0|0|1|0|0|1|8|14|35|30|15|7|2|0|0

15-Minute Speed Data for 20 Speed Bins, 4 Lanes, at 2:00 pm on Memorial Day with Construction in One Direction with no Restrictions

T|24|hijk12|2|1|2020|5|25|14|1|2|20|4|298|72|55|50|49|35|20|15|2|0|0|0|0|0|0|0|0|0|0|0|0|

T|24|hijk12|2|1|2020|5|25|14|2|2|20|4|322|68|51|48|47|43|30|20|10|5|0|0|0|0|0|0|0|0|0|0|0|

T|24|hijk12|2|1|2020|5|25|14|3|2|20|4|342|63|42|45|45|48|40|27|19|10|3|0|0|0|0|0|0|0|0|0|0|

T|24|hijk12|2|1|2020|5|25|14|4|2|20|4|370|60|39|40|43|52|50|36|25|16|7|2|0|0|0|0|0|0|0|0|0|

T|24|hijk12|2|2|2020|5|25|14|1|2|20|4|309|73|56|51|51|36|22|17|3|0|0|0|0|0|0|0|0|0|0|0|0|

T|24|hijk12|2|2|2020|5|25|14|2|2|20|4|330|70|53|50|48|44|30|20|10|5|0|0|0|0|0|0|0|0|0|0|0|

T|24|hijk12|2|2|2020|5|25|14|3|2|20|4|350|63|42|46|46|49|41|28|20|11|4|0|0|0|0|0|0|0|0|0|0|

T|24|hijk12|2|2|2020|5|25|14|4|2|20|4|375|61|40|41|44|53|50|36|25|16|7|2|0|0|0|0|0|0|0|0|0|

T|24|hijk12|6|1|2020|5|25|14|1|2|20|4|211|0|0|0|0|0|0|0|2|4|26|38|55|46|28|8|3|1|0|0|0|

T|24|hijk12|6|1|2020|5|25|14|2|2|20|4|221|0|0|0|0|0|0|0|3|5|27|39|56|47|29|9|4|2|0|0|0|

T|24|hijk12|6|1|2020|5|25|14|3|2|20|4|232|0|0|0|0|0|0|0|3|5|28|49|56|47|29|9|4|2|0|0|0|

T|24|hijk12|6|1|2020|5|25|14|4|2|20|4|252|0|0|0|0|0|0|0|3|5|28|56|61|52|32|9|4|2|0|0|0|

T|24|hijk12|6|2|2020|5|25|14|1|2|20|4|221|0|0|0|0|0|0|0|3|5|27|39|56|47|29|9|4|2|0|0|0|

T|24|hijk12|6|2|2020|5|25|14|2|2|20|4|231|0|0|0|0|0|0|0|4|6|28|40|57|48|31|11|4|2|0|0|0|

T|24|hijk12|6|2|2020|5|25|14|3|2|20|4|242|0|0|0|0|0|0|0|4|5|30|52|59|48|30|8|4|2|0|0|0|

T|24|hijk12|6|2|2020|5|25|14|4|2|20|4|262|0|0|0|0|0|0|0|3|5|28|56|66|57|32|9|4|2|0|0|0|

5-Minute Speed Data for 22 Speed Bins with 2 Lanes, Weather Restriction Travel

T|48|js1234|3|1|2021|11|23|11|A|1|22|5|627|0|0|0|0|0|0|5|52|97|111|149|98|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|3|1|2021|11|23|11|B|1|22|5|628|0|0|0|0|0|0|5|52|97|112|149|98|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|3|1|2021|11|23|11|C|1|22|5|629|0|0|0|0|0|0|5|53|97|111|149|99|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|3|1|2021|11|23|11|D|1|22|5|630|0|0|0|0|0|0|5|52|98|112|150|98|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|3|1|2021|11|23|11|E|1|22|5|631|0|0|0|0|0|0|5|54|97|111|150|100|68|35|10|1|0|0|0|0|0|0|

T|48|js1234|3|1|2021|11|23|11|F|1|22|5|632|0|0|0|0|0|0|5|55|98|111|150|100|68|35|9|1|0|0|0|0|0|0|

T|48|js1234|3|1|2021|11|23|11|G|1|22|5|634|0|0|0|0|0|0|6|55|98|111|150|101|68|35|9|1|0|0|0|0|0|0|

T|48|js1234|3|1|2021|11|23|11|H|1|22|5|635|0|0|0|0|0|0|7|55|98|111|150|101|68|35|9|1|0|0|0|0|0|0|

T|48|js1234|3|1|2021|11|23|11|I|1|22|5|637|0|0|0|0|0|0|8|56|98|111|150|101|68|35|9|1|0|0|0|0|0|0|

T|48|js1234|3|1|2021|11|23|11|J|1|22|5|639|0|0|0|0|0|0|10|56|98|111|150|101|68|35|9|1|0|0|0|0|0|0|

T|48|js1234|3|1|2021|11|23|11|K|1|22|5|641|0|0|0|0|0|1|11|56|98|111|150|101|68|35|9|1|0|0|0|0|0|0|

T|48|js1234|3|1|2021|11|23|11|L|1|22|5|645|0|0|0|0|0|3|13|56|98|111|150|101|68|35|9|1|0|0|0|0|0|0|

T|48|js1234|7|1|2021|11|23|11|A|1|22|5|630|0|0|0|0|0|1|7|52|97|111|149|98|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|7|1|2021|11|23|11|B|1|22|5|631|0|0|0|0|0|1|8|52|97|111|149|98|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|7|1|2021|11|23|11|C|1|22|5|632|0|0|0|0|0|1|8|53|97|111|149|98|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|7|1|2021|11|23|11|D|1|22|5|634|0|0|0|0|0|1|9|53|97|112|149|98|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|7|1|2021|11|23|11|E|1|22|5|635|0|0|0|0|0|1|10|53|97|112|149|98|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|7|1|2021|11|23|11|F|1|22|5|637|0|0|0|0|0|2|11|53|97|112|149|98|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|7|1|2021|11|23|11|G|1|22|5|639|0|0|0|0|0|2|11|54|98|112|149|98|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|7|1|2021|11|23|11|H|1|22|5|640|0|0|0|0|0|2|11|54|98|112|150|98|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|7|1|2021|11|23|11|I|1|22|5|641|0|0|0|0|0|3|11|54|98|112|150|98|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|7|1|2021|11|23|11|J|1|22|5|644|0|0|0|0|0|3|12|55|99|112|150|98|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|7|1|2021|11|23|11|K|1|22|5|647|0|0|0|0|0|3|12|56|100|113|150|98|67|34|12|2|0|0|0|0|0|0|

T|48|js1234|7|1|2021|11|23|11|L|1|22|5|650|0|0|0|0|0|3|13|56|101|113|151|98|67|34|12|2|0|0|0|0|0|0|

4.5 VEHICLE CLASSIFICATION DATA FORMAT (FIXED WIDTH OR PIPE DELIMITED)

The Vehicle Classification file contains one variable-length record for each time period (e.g., by 5 minute, 15 minute, or hour of the day) for which data are being submitted. That record includes the traffic volume by vehicle classification for that hour. The length of the record (number of columns in each record) is determined by the value in "Vehicle Classification Groupings," of the Station Description Record. This means that if two different kinds of data collection equipment are used at a site and those different pieces of equipment collect classification data in different formats (e.g., one uses length classes and the other uses the 13-FHWA categories), then an updated Station Description Record should be submitted prior to submitting data using the second classification system, or the records being submitted will not be read correctly. All lanes in one direction should have the same data being collected. FHWA uses the latest version of the State Description Record that is submitted. If this record type already exists in TMAS, and no change in the equipment functionality (e.g., the type of vehicle class data being collected) has occurred since that earlier record was submitted, it is not necessary to submit an additional Station Description Record for the data to be processed in TMAS. A single file can contain data from multiple stations and/or locations.

The 2022 TMG offers additional formatting flexibility to report vehicle classification data. States and other agencies can submit vehicle classification data to FHWA's TMAS system via either the historical fixed-width format or the new pipe-delimited format.

Up to 20-digits can be used for station IDs. For the fixed-width format, the station ID field needs to be right-justified and padded with zeros.

4.5.1 File Naming Recommendation

It is recommended that the file extension .CLA be used for all Vehicle Classification data. The filename should be descriptive to facilitate the deciphering of the file and its contents.

An example file naming convention for the Vehicle Classification record is:

ssabcxyzmmyyyy.CLA

4.5.2 Vehicle Classification – Fixed-Width Format

Table 4-17 summarizes the Vehicle Classification record format.

**Table 4-17. Vehicle Classification Record – Fixed-Width Format**
Field	Columns	Width	Description	Type	Importance
1	1	1	Record Type (RT)	Alphanumeric	Required
2	2-3	2	State FIPS Code (SFIPS)	Integer	Required
3	4-23	20	Station Identification (ID)	Alphanumeric	Required
4	24	1	Direction of Travel (DIR)	Integer	Required
5	25	1	Lane of Travel (LN)	Integer	Required
6	26-29	4	Year of Data (YR)	Integer	Required
7	30-31	2	Month of Year (MOY)	Integer	Required
8	32-33	2	Day of Month (DOM)	Integer	Required
9	34-35	2	Hour of Day (HOD)	Integer	Required
10	36	1	Classification Data Time Interval	Integer	Req./Opt.
11	37	1	Restrictions (R)	Integer	Required
12	38-42	5	Total Interval Volume (TVOL)	Integer	Required
13	43-47	5	Class 1 Count (BIN1)	Integer	Required
14	48-52	5	Class 2 Count (BIN2)	Integer	Required
15	53-57	5	Class 3 Count (BIN3)	Integer	Req./Opt.
16	58-62	5	Class 4 Count (BIN4)	Integer	Req./Opt.
17	63-67	5	Class 5 Count (BIN5)	Integer	Req./Opt.
18	68-72	5	Class 6 Count (BIN6)	Integer	Req./Opt.
19	73-77	5	Class 7 Count (BIN7)	Integer	Req./Opt.
20	78-82	5	Class 8 Count (BIN8)	Integer	Req./Opt.
21	83-87	5	Class 9 Count (BIN9)	Integer	Req./Opt.
22	88-92	5	Class 10 Count (BIN10)	Integer	Req./Opt.
23	93-97	5	Class 11 Count (BIN11)	Integer	Req./Opt.
24	98-102	5	Class 12 Count (BIN12)	Integer	Req./Opt.
25	103-107	5	Class 13 Count (BIN13)	Integer	Req./Opt.
26	108-112	5	Class 14 Count (BIN14)	Integer	Req./Opt.
27	113-117	5	Class 15 Count (BIN15)	Integer	Req./Opt.

Note: Fields designated as Required must be reported.

Fields designated as Optional are not required to be reported.

Fields designated as Required/Optional could be either required or optional based on values used for other related fields.

The fields for the Vehicle Classification record are:

Record Type (Column 1) – Required
C = Vehicle classification record (Code the letter "C" in the first column)
FIPS State Code (Columns 2-3) – Required
See section 4.2, Field #2.
Station Identification (Columns 4-23) – Required
See Section 4.2, Field #3.

This field should be right-justified with unused columns zero-filled.
Direction of Travel (Column 24) – Required
See Section 4.2, Field #4.
Lane of Travel (Column 25) – Required
See Section 4.2, Field #5.

Note: The Station ID, Direction of Travel, and Lane of Travel make up the Station Code. There should be one Station Description record per Station Code.
Year of Data (Columns 26-29) – Required
See Section 4.2, Field #6.
Month of Data (Columns 30-31) – Required
See Section 4.3, Field #8.
Day of Data (Columns 32-33) – Required
See Section 4.3, Field #9.
Hour of Data (Columns 34-35) – Required
Code the beginning of the hour in which the count was taken:
- 00 = after 00:00 to 01:00
- 01 = after 01:00 to 02:00
- …
- 22 = after 22:00 to 23:00
- 23 = after 23:00 to 24:00
Classification Data Time Interval – (Column 36) – Optional/Required
A 60-minute time interval is assumed if this column is left blank (optional). This field can be used to designate either 5-minute or 15-minute binned classification data (required).

For 15-minute binned intervals of classification data use the following:
- Code 1 for the interval 0.0 – 14.999
- Code 2 for the interval 15.0 – 29.999
- Code 3 for the interval 30.0 – 44.999
- Code 4 for the interval 45.0 – 59.999
For 5-minute binned intervals of classification data use the following:
- Code A for the interval 0.0 – 4.999
- Code B for the interval 5.0 – 9.999
- Code C for the interval 10.0 – 14.999
- Code D for the interval 15.0 – 19.999
- Code E for the interval 20.0 – 24.999
- Code F for the interval 25.0 – 29.999
- Code G for the interval 30.0 – 34.999
- Code H for the interval 35.0 – 39.999
- Code I for the interval 40.0 – 44.999
- Code J for the interval 45.0 – 49.999
- Code K for the interval 50.0 – 54.999
- Code L for the interval 55.0 – 59.999
Restrictions (Column 37) – Required
0 = no restrictions

1 = construction or other activity affected traffic flow, traffic pattern not impacted

2 = traffic counting device problem (e.g., malfunction or overflow)

3 = weather affected traffic flow, traffic pattern not impacted

4 = construction or other activity affected traffic flow, traffic pattern impacted

5 = weather affected traffic flow, traffic pattern impacted

6 = none-regular event/trend

7 = special event one day

8 = special event more than one day
Total Interval Volume (Columns 38-42) – Required
This numeric field is the total traffic volume for the hour. The total volume is needed because the data collection process might not be able to classify some vehicles, in which case the sum of the vehicle class counts will not equal the total hourly volume.

Fields 13 to 27:

The following class count fields are numeric fields with the traffic volume by vehicle class for each hour of data. "Vehicle Classification Groupings" in the Station Description Record determines the number of classes expected from a given station. This value also determines how many columns are expected in the remainder of each record submitted in each file. Truncate the vehicle classification record after the last classification field has been used. (That is, if only five vehicle classes are being reported, the record should only be 67 columns wide.)

The default classification system is the FHWA 13-class system (see Appendix A). Where a classification (grouping) system other than FHWA's 13-class system is used, the total number of columns for which data are entered will change from that described below. When no vehicles of a class being monitored are counted during a given hour, zero fill the data in the columns associated with that class of vehicles. Before submittal to FHWA, these counts should be checked for reasonableness and quality controlled. When FHWA 13-vehicle types are reported, the Vehicle Classification record would not be larger than 107 columns, with Classes 1-13 (fields 13-25) all considered to be Required. In this case, the vehicle classification grouping provided in the Station record (see Table 4-7) determines how many columns of class data are imported by TMAS. TMAS allows users to set a limit for each class count as part of its automated quality assurance checks.

Class 1 Count (Columns 43-47) – Required
Class 1 is for Motorcycles when using the 13 FHWA classification groups. If the FHWA 13-class system is not being used, this field will contain the traffic volume for the first class of vehicles being reported.
Class 2 Count (Columns 48-52) – Required
Class 2 is for Passenger Cars when using the 13 FHWA classification groups. If the FHWA 13-class system is not being used, this field will contain the traffic volume for the second class of vehicles being reported.
Class 3 Count (Columns 53-57) – Required/Optional
Class 3 is for Light Duty (2-axle, four-tire) Pick-up Trucks when using the 13 FHWA classification groups.

If the FHWA 13-class system is not being used, this field will contain the traffic volume for the third class of vehicles being reported.
Class 4 Count (Columns 58-62) – Required/Optional
Class 4 is for Buses when using the 13 FHWA classification groups. If the FHWA 13-class system is not being used, this field will contain the traffic volume for the fourth class of vehicles being reported.
Class 5 Count (Columns 63-67) – Required/Optional
Class 5 is for Two-Axle, Six-Tire, Single-Unit Trucks when using the 13 FHWA classification groups. If the FHWA 13-class system is not being used, this field will contain the traffic volume for the fifth class of vehicles being reported.
Class 6 Count (Columns 68-72) – Required/Optional
Class 6 is for Three-Axle, Single-Unit Trucks when using the 13 FHWA classification groups. If the FHWA 13-class system is not being used, this field will contain the traffic volume for the sixth class of vehicles being reported.
Class 7 Count (Columns 73-77) – Required/Optional
Class 7 is for Four-or-More Axle, Single-Unit Trucks when using the 13 FHWA classification groups. If the FHWA 13-class system is not being used, this field will contain the traffic volume for the seventh class of vehicles being reported.
Class 8 Count (Columns 78-82) – Required/Optional
Class 8 is for Four-or-Less Axle, Single-Trailer Combination Vehicles when using the 13 FHWA classification groups. If the FHWA 13-class system is not being used, this field will contain the traffic volume for the eighth class of vehicles being reported.21.
Class 9 Count (Columns 83-87) – Required/Optional
Class 9 is for Five-Axle, Single-Trailer Combination Vehicles when using the 13 FHWA classification groups. If the FHWA 13-class system is not being used, this field will contain the traffic volume for the ninth class of vehicles being reported.
Class 10 Count (Columns 88-92) – Required/Optional
Class 10 is for Six-or-More Axle, Single-Trailer Combination Vehicles when using the 13 FHWA classification groups. If the FHWA 13-class system is not being used, this field will contain the traffic volume for the tenth class of vehicles being reported.
Class 11 Count (Columns 93-97) – Required/Optional
Class 11 is for Five-or-Less Axle, Multiple-Trailer Combination Vehicles when using the 13 FHWA classification groups. If the FHWA 13-class system is not being used, this field will contain the traffic volume for the eleventh class of vehicles being reported.
Class 12 Count (Columns 98-102) – Required/Optional
Class 12 is for Six-Axle, Multiple-Trailer Combination Vehicles when using the 13 FHWA classification groups. If the FHWA 13-class system is not being used, this field will contain the traffic volume for the twelfth class of vehicles being reported.
Class 13 Count (Columns 103-107) – Required/Optional
Class 13 is for Seven-or-More Axle, Multiple-Trailer Combination Vehicles when using the 13 FHWA classification groups. If the FHWA 13-class system is not being used, this field will contain the traffic volume for the thirteenth class of vehicles being reported.

The agency may code special vehicle types or unclassified vehicles as either class 14 or 15 vehicles.

The vehicle classification record should be ended here if 13 classes are being reported. If volumes for additional classes of vehicles are being reported, add five additional columns for each additional vehicle class being reported. (These additional vehicle classes can include the vehicle categories of "Unclassified", "Unclassifiable" vehicles that are reported by some types of equipment, or some State-specific type of vehicle.)
Class 14 Count (Columns 108-112) – Required/Optional
Class 15 Count (Columns 113-117) – Required/Optional

Example Vehicle Classification records are shown in Table 4-18 through Table 4-19.

**Table 4-18. Vehicle Classification Record Example (3 Length-Class Bins, 4 Lanes with Lanes and Directions not Combined at 60-Minute Interval for 2 Hours) – Fixed Width Format**
Column Number:	1	2-3	4-23	24	25	26-29	30-31	32-33	34-35	36	38-42	43-47	48-52	53-57
Content 01 Example:	C	17	JohnHeisman01231811B	1	1	2012	04	25	00	Blank	00099	00051	00038	00010
Content 02 Example:	C	17	JohnHeisman01231811B	1	2	2012	04	25	00	Blank	00020	00005	00014	00001
Content 03 Example:	C	17	JohnHeisman01231811B	5	2	2012	04	25	00	Blank	00011	00002	00008	00001
Content 04 Example:	C	17	JohnHeisman01231811B	5	1	2012	04	25	00	Blank	00066	00023	00037	00006
Content 05 Example:	C	17	JohnHeisman01231811B	1	1	2012	04	25	01	Blank	00072	00042	00021	00009
Content 06 Example:	C	17	JohnHeisman01231811B	1	2	2012	04	25	01	Blank	00017	00005	00011	00001
Content 07 Example:	C	17	JohnHeisman01231811B	5	2	2012	04	25	01	Blank	00011	00002	00007	00002
Content 08 Example:	C	17	JohnHeisman01231811B	5	1	2012	04	25	01	Blank	00057	00021	00029	00007

**Table 4-19. Vehicle Classification Record Example (13 Axle-Class Bins, 2 Lanes with Lanes or Directions not Combined at 15-Minute Interval) – Fixed Width Format**
Column Number:	1	2-3	4-23	24	25	26-29	30-31	32-33	36	38-42
Content 01 Example:	C	17	JohnHeisman012318140	3	1	2012	12	01	1	00054
Content 02 Example:	C	17	JohnHeisman012318140	7	1	2012	12	01	1	00055
Content 03 Example:	C	17	JohnHeisman012318140	3	1	2012	12	01	2	00051
Content 04 Example:	C	17	JohnHeisman012318140	7	1	2012	12	01	2	00058
Content 05 Example:	C	17	JohnHeisman012318140	3	1	2012	12	01	3	00060
Content 06 Example:	C	17	JohnHeisman012318140	7	1	2012	12	01	3	00067
Content 07 Example:	C	17	JohnHeisman012318140	3	1	2012	12	01	4	00064
Content 08 Example:	C	17	JohnHeisman012318140	7	1	2012	12	01	4	00063

continued

Column Number:	43-47	48-52	53-57	58-62	63-67	68-72	78-82	83-87	88-92	93-97
Content 01 Example:	00000	00037	00006	00000	00001	00000	00002	00007	00000	00000
Content 02 Example:	00001	00038	00009	00000	00000	00000	00003	00005	00000	00000
Content 03 Example:	00000	00039	00008	00000	00001	00001	00001	00008	00000	00000
Content 04 Example:	00000	00037	00010	00000	00000	00000	00002	00009	00000	00000
Content 05 Example:	00001	00037	00006	00000	00000	00001	00004	00012	00001	00000
Content 06 Example:	00000	00036	00005	00000	00001	00000	00000	00015	00002	00000
Content 07 Example:	00001	00034	00009	00001	00001	00000	00002	00016	00000	00001
Content 08 Example:	00000	00038	00008	00000	00000	00000	00003	00013	00000	00000

continued

Column Number:	98-102	103-107	108-112	113-117
Content 01 Example:	00000	00001	00000	00000
Content 02 Example:	00000	00000	00000	00000
Content 03 Example:	00000	00001	00000	00000
Content 04 Example:	00000	00000	00000	00000
Content 05 Example:	00000	00000	00000	00000
Content 06 Example:	00000	00000	00000	00000
Content 07 Example:	00000	00000	00000	00000
Content 08 Example:	00000	00001	00000	00000

4.5.3 Vehicle Classification – Pipe-Delimited Format

State highway agencies can also submit vehicle classification data using the pipe-delimited format. The key difference between the fixed-width format and the pipe-delimited format is that with the pipe-delimited file, data elements no longer need to match the starting and ending columns. Length of data elements can be equal or shorter than the specified lengths. The field order for the pipe-delimited format is identical to the order for the fixed-width format (see Table 4-17). In this format, the fields are separated by a pipe symbol (|) instead of beginning in specified columns. Example records in this format are provided below.

Delimited Format Examples

Class Data for 15 Vehicle Bins with Delimited Fields – Detailed

RT|SFIPS|ID|DIR|LN|YR|MOY|DOM|HOD|I|R|TVOL|BIN1|BIN2|BIN3|BIN4|

BIN5|BIN6|BIN7|BIN8|BIN9|BIN10|BIN11|BIN12|BIN13|BIN14|BIN15

Hourly Class Data for 15 Class Bins with 2 Directions with No Restrictions

C|39|XYZ123|3|1|2021|4|25|00||0|132|5|67|13|10|2|3|1|7|16|2|1|1|0|3|1

C|39|XYZ123|7|1|2021|4|25|00||0|126|3|63|12|5|4|5|1|10|13|4|3|0|0|1|2

15-Minute Class Data for 5 Class Bins with 2 Directions and 4 Lanes with No Restrictions

C|39|ABC123|1|1|2021|4|25|00|1|0|96|5|67|13|10|1

C|39|ABC123|1|2|2021|4|25|00|1|0|236|10|175|35|14|2

C|39|ABC123|1|3|2021|4|25|00|1|0|215|8|168|32|5|2

C|39|ABC123|1|4|2021|4|25|00|1|0|89|4|67|12|4|2

C|39|ABC123|5|1|2021|4|25|00|1|0|102|3|73|14|10|2

C|39|ABC123|5|2|2021|4|25|00|1|0|235|5|185|30|15|0

C|39|ABC123|5|3|2021|4|25|00|1|0|230|7|173|36|13|1

C|39|ABC123|5|4|2021|4|25|00|1|0|97|5|67|13|10|2

C|39|ABC123|1|1|2021|4|25|00|2|0|102|4|68|24|6|0

C|39|ABC123|1|2|2021|4|25|00|2|0|201|3|167|23|7|1

C|39|ABC123|1|3|2021|4|25|00|2|0|192|5|147|30|8|2

C|39|ABC123|1|4|2021|4|25|00|2|0|97|5|65|15|10|2

C|39|ABC123|5|1|2021|4|25|00|2|0|91|1|64|22|4|0

C|39|ABC123|5|2|2021|4|25|00|2|0|179|0|147|26|6|0

C|39|ABC123|5|3|2021|4|25|00|2|0|212|5|167|34|4|2

C|39|ABC123|5|4|2021|4|25|00|2|0|78|2|57|13|6|0

C|39|ABC123|1|1|2021|4|25|00|3|0|102|4|68|24|6|0

C|39|ABC123|1|2|2021|4|25|00|3|0|201|3|167|23|7|1

C|39|ABC123|1|3|2021|4|25|00|3|0|192|5|147|30|8|2

C|39|ABC123|1|4|2021|4|25|00|3|0|97|5|65|15|10|2

C|39|ABC123|5|1|2021|4|25|00|3|0|91|1|64|22|4|0

C|39|ABC123|5|2|2021|4|25|00|3|0|179|0|147|26|6|0

C|39|ABC123|5|3|2021|4|25|00|3|0|212|5|167|34|4|2

C|39|ABC123|5|4|2021|4|25|00|3|0|78|2|57|13|6|0

C|39|ABC123|1|1|2021|4|25|00|4|0|102|4|68|24|6|0

C|39|ABC123|1|2|2021|4|25|00|4|0|201|3|167|23|7|1

C|39|ABC123|1|3|2021|4|25|00|4|0|192|5|147|30|8|2

C|39|ABC123|1|4|2021|4|25|00|4|0|97|5|65|15|10|2

C|39|ABC123|5|1|2021|4|25|00|4|0|91|1|64|22|4|0

C|39|ABC123|5|2|2021|4|25|00|4|0|179|0|147|26|6|0

C|39|ABC123|5|3|2021|4|25|00|4|0|212|5|167|34|4|2

C|39|ABC123|5|4|2021|4|25|00|4|0|78|2|57|13|6|0

4.6 WEIGHT DATA FORMAT (FIXED WIDTH OR PIPE DELIMITED)

The Weight Data Format is the mechanism currently used to submit weight data to TMAS. FHWA prefers that States submit weight data using the Individual Vehicle Record Formats (IVR) described in Section 4.7. Weight data should be submitted using the "W" or "Z" variants of the IVR record format (Sections 4.7.4 and 4.7.5, respectively).

For States still wishing to use the current Weight Data Format, a description of that file format is as follows. Each file submitted in this format contains one record for each vehicle. Each record describes that vehicle's axle weights and axle spacings. Agencies have the option to submit all vehicle types in weight data format as opposed to just sending in classes 4-13.

Up to 20-digits can be used for station IDs. For the fixed-width format, the station ID field needs to be right-justified and padded with zeros.

As a reminder, all weight data are to use English units.

4.6.1 File Naming Recommendation

It is recommended that the file extension .WGT be used for all Weight data files. The filename should be descriptive to facilitate the deciphering of the file and its contents.

An example of the file naming convention for the Weight record is:

ssabcxyzmmyyyy.WGT

4.6.2 Weight – Fixed-width Format

The fixed-width column data element format is the legacy TMAS data format. States can continue to submit data in such format. However, States can elect to submit the weight data via the new pipe-delimited file format described in Section 4.6.3.

Table 4-20 summarizes the Weight fixed-width column record format.

**Table 4-20. Weight Record – Fixed-Width Format**
Field	Columns	Width	Description	Type	Importance
1	1	1	Record Type (RT)	Alphanumeric	Required
2	2-3	2	State FIPS Code (SFIPS)	Integer	Required
3	4-23	20	Station Identification (ID)	Alphanumeric	Required
4	24	1	Direction of Travel (DIR)	Integer	Required
5	25	1	Lane of Travel (LN)	Integer	Required
6	26-29	4	Year of Data (YR)	Integer	Required
7	30-31	2	Month of Year (MOY)	Integer	Required
8	32-33	2	Day of Month (DOM)	Integer	Required
9	34-35	2	Hour of Day (HOD)	Integer	Required
10	36-37	2	Vehicle Class (CLS)	Integer	Required
11	38-40	3	Open (O)	Integer	Optional
12	41-46	6	Total Weight of Vehicle (GVW)	Integer	Required
13	47-48	2	Number of Axles (NAX)	Integer	Required
14	49-53	5	Axle Weight 1 (AW1)	Integer	Required
15	54-57	4	Axles 1-2 Spacing (ASP1)	Integer	Required
16	58-62	5	Axle Weight 2 (AW2)	Integer	Required
17	63-66	4	Axles 2-3 Spacing (ASP2)	Integer	Req./Opt.
18	67-71	5	Axle Weight 3 (AW3)	Integer	Req./Opt.
19	72-75	4	Axles 3-4 Spacing (ASP3)	Integer	Req./Opt.
20	76-80	5	Axle Weight 4 (AW4)	Integer	Req./Opt.
21	81-84	4	Axles 4-5 Spacing (ASP4)	Integer	Req./Opt.
22	85-89	5	Axle Weight 5 (AW5)	Integer	Req./Opt.
23	90-93	4	Axles 5-6 Spacing (ASP5)	Integer	Req./Opt.
24	94-98	5	Axle Weight 6 (AW6)	Integer	Req./Opt.
25	99-102	4	Axles 6-7 Spacing (ASP6)	Integer	Req./Opt.
26	103-107	5	Axle Weight 7 (AW7)	Integer	Req./Opt.
27	108-111	4	Axles 7-8 Spacing (ASP7)	Integer	Req./Opt.
28	112-116	5	Axle Weight 8 (AW8)	Integer	Req./Opt.
29	117-120	4	Axles 8-9 Spacing (ASP8)	Integer	Req./Opt.
30	121-125	5	Axle Weight 9 (AW9)	Integer	Req./Opt.
31	126-129	4	Axles 9-10 Spacing (ASP9)	Integer	Req./Opt.
32	130-134	5	Axle Weight 10 (AW10)	Integer	Req./Opt.
33	135-138	4	Axles 10-11 Spacing (ASP10)	Integer	Req./Opt.
34	139-143	5	Axle Weight 11 (AW11)	Integer	Req./Opt.
35	144-147	4	Axles 11-12 Spacing (ASP11)	Integer	Req./Opt.
36	148-152	5	Axle Weight 12 (AW12)	Integer	Req./Opt.
37	153-156	4	Axles 12-13 Spacing (ASP12)	Integer	Req./Opt.
38	157-161	5	Axle Weight 13 (AW13)	Integer	Req./Opt.

Note: Fields designated as Required must be reported.

Fields designated as Optional are not required to be reported.

Fields designated as Required/Optional could be either required or optional based on values used for other related fields.

The number of axles determines the number of axle weight and spacing fields.

For those vehicles with fourteen or more axles, add the appropriate number of additional fields.

Additional axle spacing and axle weight fields may be added in the same manner if needed up to a maximum of 25 axles per record.

The fields for the weight record are:

Record Type (Column 1) – Required
W = Truck weight record (Code the letter "W" in the first column.)
FIPS State Code (Columns 2-3) – Required
See Section 4.2, Field #2.
Station Identification (Columns 4-23) – Required
See Section 4.2, Field #3.

This field should be right-justified with unused columns zero-filled.

Direction of Travel Code (Column 24) – Required
See Section 4.2, Field #4.
Lane of Travel (Column 25) – Required
See Section 4.2, Field #5.

Note: The Station ID, Direction of Travel, and Lane of Travel make up the Station Code. There should be one Station Description record per Station Code.
Year of Data (Columns 26-29) – Required
See Section 4.2, Field #6.
Month of Data (Columns 30-31) – Required
See Section 4.3, Field #8.
Day of Data (Columns 32-33) – Required
See Section 4.3, Field #9.
Hour of Data (Columns 34-35) – Required
Code the beginning of the hour in which the count was taken:
- 00 = after 00:00 to 01:00
- 01 = after 01:00 to 02:00
- …
- 22 = after 22:00 to 23:00
- 23 = after 23:00 to 24:00
Vehicle Class (Columns 36-37) – Required
Enter the class of the vehicle from FHWA Vehicle Classes 1 to 13. (Note: vehicles from classes 1 - 3 are ordinarily omitted from weight data submittals.)

A dummy vehicle class of 'm' indicates that weight data for this hour are missing. A dummy vehicle class of 'd' indicates that weight data for this hour are not missing, and thus if there are no weight records for the hour, then there were no trucks during that hour. Without these indications, no weight records for an hour might be interpreted to mean that the WIM system was not working.
Open (Columns 38-40 – Optional
This field is for special studies or State use such as for vehicle speed (miles per hour) or pavement temperature (degrees Fahrenheit).
Total Weight of Vehicle (Columns 41-46) – Required
Enter the gross vehicle weight to the nearest pound. For example, 110,200.2 lbs. would be reported in the field as 110200. There are no decimals or commas used in the field. This should equal the sum of all the axle weights except for rounding.
Number of Axles (Columns 47-48) – Required
Enter the total number of axles in use by the vehicle (including any trailers).

The number of axles determines how many axle weight and spacing fields will be expected on each record. As a reminder, the axle weight and spacing fields should be reported in English units. The rest of the record alternates between axle weights and axle spacings, starting from the front of the vehicle. Axle weights are to the nearest pound. Axle spacings are to the nearest tenth of a foot. All values should be right-justified with leading blanks as needed.

Quality control (QC) checks should be performed on the axle weights and spacings.

Axle weights are to be reported to the nearest pound. Axle spacings are reported to the nearest tenth of a foot. All values should be right-justified with leading blanks as needed
Axle Weight 1 (Columns 49-53) – Required
Axles 1-2 Spacing (Columns 54-57) – Required
Axle Weight 2 (Columns 58-62) – Required
Axles 2-3 Spacing (Columns 63-66) – Required/Optional
Axle Weight 3 (Columns 67-71) – Required/Optional
Axles 3-4 Spacing (Columns 72-75) – Required/Optional
Axle Weight 4 (Columns 76-80) – Required/Optional
Axles 4-5 Spacing (Columns 81-84) – Required/Optional
Axle Weight 5 (Columns 85-89) – Required/Optional
Axles 5-6 Spacing (Columns 90-93) – Required/Optional
Axle Weight 6 (Columns 94-98) – Required/Optional
Axles 6-7 Spacing (Columns 99-102) – Required/Optional
Axle Weight 7 (Columns 103-107) – Required/Optional
Axles 7-8 Spacing (Columns 108-111) – Required/Optional
Axle Weight 8 (Columns 112-116) – Required/Optional
Axles 8-9 Spacing (Columns 117-120) – Required/Optional
Axle Weight 9 (Columns 121-125) – Required/Optional
Axles 9-10 Spacing (Columns 126-129) – Required/Optional
Axle Weight 10 (Columns 130-134) – Required/Optional
Axles 10-11 Spacing (Columns 135-138) – Required/Optional
Axle Weight 11 (Columns 139-143) – Required/Optional
Axles 11-12 Spacing (Columns 144-147) – Required/Optional
Axle Weight 12 (Columns 148-152) – Required/Optional
Axles 12-13 Spacing (Columns 153-156) – Required/Optional
Axle Weight 13 (Columns 157-161) – Required/Optional

Additional axle spacing and axle weight fields may be added in the same manner if needed up to a maximum of 25 axles per record

Example Weight records are shown in Table 4-21.

WEIGHT SITE WEIGHT FILE

**Table 4-21. Weight Record Example – Fixed-Width Format**
Column Number:	1	2-3	4-23	24	25	26-29	30-31	32-33	34-35	36-37	38-40	41-46
Content 01 Example:	W	17	JohnHeisman012318140	3	1	2012	11	07	16	09	Blank	057886
Content 02 Example:	W	17	JohnHeisman012318140	3	1	2012	11	07	16	04	Blank	018351
Content 03 Example:	W	17	JohnHeisman012318140	3	1	2012	11	07	16	06	Blank	047289

continued

Column Number:	47-48	49-53	54-57	58-62	63-66	67-71	72-75	76-80	81-84	85-89	90-93	94-98	99-102
Content 01 Example:	05	11210	0151	12300	0045	13730	0214	09815	0048	10831	Blank	Blank	Blank
Content 02 Example:	02	08522	0252	09829	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank
Content 03 Example:	03	09818	0131	19125	0046	18346	Blank	Blank	Blank	Blank	Blank	Blank	Blank

continued

Column Number:	103-107	108-111	112-116	117-120	121-125	126-129	130-134	135-138	139-143	144-147	148-152	153-156	157-161
Content 01 Example:	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank
Content 02 Example:	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank
Content 03 Example:	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank

In the Weight Record examples listed above, the Vehicle Class field (columns 36-37) indicates either class 09 (semi-trailer), class 04 (bus), or class 06 (dump-truck; 3-axle single unit) as illustrated below in Figure 4-2.

Class 9

5-axle tractor semitrailer

five axle semi

five axle semi with a middle axle

Class 4 Bus

two axle bus

three axle bus

four axle, double decker bus

Class 6

3-axle, single unit

three axle concrete mixer

three axle box truck

three axle flat bed truck

Source: Federal Highway Administration.

Figure 4-2. Illustration of Class 09 - Semi-Truck, 04 - Bus, and 06 - Dump-Truck

4.6.3 Weight Data – Pipe-Delimited Format

State highway agencies can submit the weight data using the pipe-delimited format. The key difference between the fixed-width format and the pipe-delimited format is that with the pipe-delimited file, data elements no longer need to match the starting and ending columns. Length of data elements can be equal or shorter than the specified lengths. The field order for the pipe-delimited format is identical to the order for the fixed-width format (see Table 4-20). In this format, the fields are separated by a pipe symbol (|) instead of beginning in specified columns. Example records in this format are provided below.

Delimited Format Examples

Weight Format – Detailed

RT|SFIPS|ID|DIR|LN|YR|MOY|DOM|HOD|CLS|O|GVW|NAX|AW1|ASP1|AW2|ASP2|AW3|ASP3|AW4|ASP4|AW5|ASP5|AW6|ASP6|AW7|ASP7|AW8…

2-Lane Roadway with 9 Individual Vehicles Recorded

W|35|123456|3|1|2021|4|25|00|9||61837|5|10500|145|12000|43|12500|210|13450|46|13387

W|35|123456|7|1|2021|4|25|00|5||14874|2|8462|185|6412

W|35|123456|3|1|2021|4|25|00|4||25886|3|9750|240|7680|45|8456

W|35|123456|3|1|2021|4|25|00|9||54828|5|9873|135|11678|42|10985|23|11245|45|11047

W|35|123456|7|1|2021|4|25|00|8||40561|4|9504|130|11546|205|9728|45|9783

W|35|123456|3|1|2021|4|25|00|9||70044|5|11620|165|12895|43|12530|220|16750|82|16249

W|35|123456|7|1|2021|4|25|00|10||79973|6|11463|145|10486|43|10876|43|10562|240|18045|46|18541

W|35|123456|7|1|2021|4|25|01|13||71753|8|10876|138|9540|42|9163|42|9405|180|8741|46|8523|160|7652|46|7853

W|35|123456|3|1|2021|4|25|01|9||72741|5|11231|165|14780|43|15345|275|15245|46|16140

4.7 DETAILED INDIVIDUAL VEHICLE RECORD (IVR) DATA FORMAT (FIXED WIDTH OR PIPE DELIMITED)

As an optional and recommended way to submit traffic monitoring data to FHWA, State and local highway agencies may submit traffic volume, speed, vehicle classification, and vehicle weight data as individual vehicle records (IVR) rather than using the more traditional formats described earlier in this chapter. TMAS will accept IVRs in the formats described below.

IVRs require more disk space than aggregated records, but they also allow much more detailed analysis of traffic patterns. Agencies are encouraged to submit data in these IVR formats whenever possible. While these types of records are not necessary for all data collection efforts, having a sample of such records available for use permits the investigation of several key traffic flow and vehicle characteristics (e.g. vehicle gap analysis, speed by class, and changes in axle spacing distributions) that are not possible when only aggregate traffic records are stored.

The submission of one IVR data file will:

Meet all of the FHWA reporting needs for the TMS.
Allow for more detailed QC checks to be performed.
Provide better quality data for use in national statistics.

Up to 20-digits can be used for station IDs. For the fixed-width format, the station ID field needs to be right-justified and padded with zeros.

Table 4-22 provides a quick reference for the units of measurement to be reported for weight, length, speed, and temperature.

**Table 4-22. Units of Measurement**
Measure	Unit	Resolution Reported
Weight	Pound	Pounds
Vehicle Length	Feet	Tenths of feet
Speed	Mph	Tenths of mph
Temperature Degrees	Degrees Fahrenheit	Degrees
Time	Seconds	Hundredth of second
Inter-Axle Spacing	Feet	Tenths of feet

Individual vehicle records can be collected by a variety of different traffic monitoring devices and technologies. However, thetype of data collected for each passing vehicle differs when these alternative technologies are used. Consequently, FHWA has developed five different variations of the Individual Vehicle Record format. Each of these variations corresponds to a specific type of data collection device. All of the formats use a fixed-width record structure, and the first 13 fields of data are the same for all five record formats. The final (14th) field contains a variable that describes the type of data contained in that record. After the first 14 fields, the remainder of each vehicle record differs based on the type and amount of data collected by that device for that vehicle.

The five different versions of the Individual Vehicle Record Format (variant letter to use) are described in the following sections:

Traffic Volume Only Format (V)
Speed, Length Classification Data Formats (T)
Axle Classification Data Format (C)
Weight Data Format for Reporting Axle Weights (W)
Vehicle Classification and Wheel Weights (Z)

Each of these record formats is described in detail below. In all cases, each format uses one record for each vehicle observation. All units are given in English units (pounds for weight, tenths of feet for distance, tenths of miles per hour for speed, and degrees Fahrenheit for temperature). All unused entries are to be blank filled.

A dummy vehicle signature of 'm' indicates that traffic data for an hour are missing. A dummy vehicle signature of 'd' indicates that traffic data for this hour are not missing, and there were no IVR records for the hour. Without these indications, no IVR records for an hour might be interpreted to mean that the traffic system was not working. These dummy records can be utilized for any of the IVR variants.

The first 13 fields contain the same information (with unique direction, lane, date, time, and signature codes) for all individual vehicle records.

An example of the file naming convention for the Individual Vehicle Record record is:

ssabcxyzmmyyyy.IVR

4.7.1 Traffic Volume Only Format (V)

Table 4-23 describes the data to be included in the first 13 fields of all Individual Vehicle Record records submitted to FHWA, regardless of which one of the five record types is being submitted.

**Table 4-23. Individual Vehicle Record Collected by Volume Device (V Variant) – Fixed-Width Format**
Field	Columns	Width	Description	Type	Importance
1	1	1	Record Type (RT)	Alphanumeric	Required
2	2-3	2	State FIPS Code (SFIPS)	Integer	Required
3	4-23	20	Station Identification (ID)	Alphanumeric	Required
4	24	1	Direction of Travel (DIR)	Integer	Required
5	25	1	Lane of Travel (LN)	Integer	Required
6	26-29	4	Year of Data (YR)	Integer	Required
7	30-31	2	Month of Year (MOY)	Integer	Required
8	32-33	2	Day of Month (DOM)	Integer	Required
9	34-35	2	Hour of Day (HOD)	Integer	Required
10	36-37	2	Minute of Hour (MOH)	Integer	Required
11	38-39	2	Second of Minute (SOM)	Integer	Required
12	40-41	2	Sub Second of Second (SSOS)	Integer	Required
13	42	1	Type of Base Counting Device (V)	Alphanumeric	Required
14	43-47	5	Vehicle Signature/Other Use (VS)	Integer	Optional

Note: Fields designated as Required must be reported.

Fields designated as Optional are not required to be reported.

Fields designated as Required/Optional could be either required or optional based on values used for other related fields.

Record Type (Column 1) – Required
I = Individual Vehicle Record
FIPS State Code (Columns 2-3) – Required
See Section 4.2, Field #2.
Station Identification (Columns 4-23) – Required
See Section 4.2, Field #3.

This field should be right-justified with unused columns zero-filled.
Direction of Travel Code (Column 24) – Required
See Section 4.2, Field #4.
Lane of Travel (Column 25) – Required
See Section 4.2, Field #5.

Note: The Station ID, Direction of Travel, and Lane of Travel make up the Station Code. There should be one Station Description record per Station Code.
Year of Data (Columns 26-29) – Required
See Section 4.2, Field #6.
Month of Year (Columns 30-31) – Required
See Section 4.3, Field #8.
Day of Month (Columns 32-33) – Required
See Section 4.3, Field #9.
Hour of Day (Columns 34-35) – Required
hh = Hour in which record was taken

Code the beginning of the hour in which the record was taken:
- 00 = after 00:00 to 01:00
- 01 = after 01:00 to 02:00
- …
- 22 = after 22:00 to 23:00
- 23 = after 23:00 to 24:00
Minute of Hour of Data (Columns 36-37)
mm = Minute in which record was taken

Code the beginning of the minute in which the record was taken:
- 00 = 0 minute to less than 1 minute
- 01 = 1 minute to less than 2 minutes
- …
- 58 = 58 minutes to less than 59 minutes
- 59 = 59 minutes to less than 60 minutes
Second of Minute of Data (Columns 38-39)
ss = Second in which record was taken

Code the beginning of the second in which the record was taken:
- 00 = 0 second to less than 1 second
- 01 = 1 second to less than 2 seconds
- …
- 58 = 58 seconds to less than 59 seconds
- 59 = 59 seconds to less than 60 seconds
Sub-Second of Second (Columns 40-41)
ff = Fraction of a second to the nearest hundredth of a second in which the record was taken

Code the fraction of a second to the nearest hundredth second in which the record was taken:
- 00 = 00 hundredth seconds to less than 01 hundredth seconds 01 = 01 hundredth seconds to less than 02 hundredth seconds
- …
- 98 = 98 hundredth seconds to less than 99 hundredth seconds
- 99 = 99 hundredth seconds to less than 100 hundredth seconds
Type of Base Counting Device (Column 42) – Required
This alphanumeric field details the type of counting device recording the individual record formats, and the type of data contained in this record. The value in this field affects the length of the record being read (the software reads the number of columns that is expected to exist), as well as the definition of the data contained in subsequent columns. Code the correct value for type of traffic counting device.

V = volume only type of device (the expected number of columns is 47)
Vehicle Signature or Other Use Field (Columns 43-47) – Optional

Enter the vehicle unique loop or magnetic signature using the right-most digits first.

Digit 1 (Column 43) contains the vehicle type code:
- Motorcycle (FHWA Class 1) =1
- Passenger car (FHWA Class 2) = 2
- Light Truck (FHWA Class 3) = 3 Bus (FHWA Class 4) = 4
- Single-unit vehicle (FHWA Classes 5, 6, and 7) = 5
- Single-trailer combination vehicle (FHWA Classes 8, 9, and 10) = 6
- Multiple-trailer combination vehicle (FHWA Classes 11, 12, and 13) = 7 Utilize a "m" as a dummy record when counts are missing for the given hour
- Utilize a "d" as a dummy record when counts were not present for the given hour but the traffic device was working.
Digit 2 (Column 44) – the # of axles for the vehicle. If more than 9 axles are observed, code alphanumerically, where 10 = A, 11 = B, etc.

Digit 3 (Column 45) – body type (body style defined by FHWA in Table 4-24 and Table 4-25)

Digit 4 (Column 46) – specific body style (body style defined by FHWA in Table 4-24 and Table 4-25)

Digit 5 (Column 47) – pulling additional part attribute
- 0 = No additional part
- 1 = FHWA 1, FHWA 2, FHWA 3 pulling a trailer/platform/vehicle/etc.
- 3 = Single unit truck (FHWA 4-7) pulling a FHWA 2/FHWA 3/tractor/single unit truck
- 5 = Single unit truck (FHWA 4-7) or Combination unit truck pulling an auto trailer
- 7 = Single unit truck (FHWA 4-7) pulling a trailer/platform (trailer truck type)
- 9 = Others

This signature field can also be used for other purposes such as vehicle overhang, vehicle width, or other uses. Blank fill all unused columns. For any distance measurement (English), the decimal is implied to be between columns 46 and 47 (XXXX.X)

**Table 4-24. Individual Codes for Class and Body Type 1<5**
Code 3	Body Type (Body Style)	Code 4	Specific Body Type (Specific Body Style)
0	Blocked (may be blocked or N/A)	0	N/A
1	Motorcycles (FHWA1)	0	Blocked
		1	Moped, Motorcycle
		2	2-front tire motorcycle
		3	2-rear tire motorcycle
		4	Sidecar motorcycle
		9	Others
2	Passenger car (FHWA2)	0	Blocked
		1	Sedan/SUV/Minivan (up to 8 seats)/Coupe/Sta. wagon/Sports car/Jeep
		9	Others
3	Non-passenger car (FHWA3)	0	Blocked
		1	Pickup, non-full-size
		3	Pickup, modified
		4	Panel van/Passenger van (9-15 seats)
		5	Limousine (e.g., Car limousine, SUV limousine, Hummer limousine)
		6	Mini motorhome/Minibus
		8	Ambulance
		9	Others
4	Bus (FHWA 4)	0	Blocked
		1	School, small
		2	School, mid/large
		3	City bus, small
		4	City bus, mid/large
		5	City bus, articulated
		6	Motorcoach (e.g., Greyhound)
		7	Shuttle bus (16 or more seats)
		9	Others
9	Bicycle	0	N/A

**Table 4-25. Individual Codes for Class and Body Type when Code 1>=5**
Code 3	Body Type (Body Style)	Code 4	Specific Body Type (Specific Body Style)
0	Blocked	0	Blocked
1	Van	0	Blocked
		1	Enclosed van/Open-top/Grain van/Curtain-side/Beverage van (for Code 1 <= 6 only)
		2	Delivery/Multi-stop/Step van
		3	Drop-frame van/Furniture van (for Code 1 >= 6 only)
		4	Tilt van (for Code 1 >= 6 only)
		5	Same type vans (for Code 1 = 7 only)
		6	Different type vans (for Code 1 = 7 only)
		9	Others
2	Platform	0	Blocked
		1	Basic platform/Double deck platform
		2	Low Boy Platform/Gooseneck
		3	Platform with device at front end
		4	Platform with device at rear end
		9	Others
3	Tanker	0	Blocked
		1	Chemical truck/Gas truck/Septic truck
		3	Dry bulk truck/Pneumatic truck
		9	Others
5	Service Truck	0	Blocked
		1	2-axle 6-tire Pickup
		2	Concrete mixer
		3	Bucket/Wrecker/Winch
		4	Garbage truck
		5	Flatbed tow truck (single/Double deck)
		6	Crane/Concrete pumper truck/Oil rig
		7	Ambulance/Fire truck
		9	Other Utility truck (Landscaping/Street sweeper/etc.)
6	Semi-tractor	0	Blocked
		1	Conventional cab/Day cab
		2	Extended cab/Sleeping cab
		3	Cab-Over Engine (COE) cab
		9	Others
7	Intermodal chassis	0	Blocked
		1	20 ft (1TEU) box container
		2	40 ft (2TEU)/53 ft box container
		5	Same type containers (for Code 1 = 7 only)
		6	Different type containers (for Code 1 = 7 only)
		7	Container chassis only
		9	Others
8	Dump	0	Blocked
		1	End/Side dump
		2	Bottom/Belly dump
		9	Others
9	Other specialty	0	Blocked
		1	Auto Carrier
		2	Mini motorhome
		3	Full size motorhome
		4	Livestock
		5	Logging/Pipe/Pole
		6	Agriculture
		9	Others (e.g., Armored personnel carrier)

Example V Variant records are shown in Table 4-26.

**Table 4-26. Individual Vehicle Record (Volume Site) Example (Southbound Lane 1, Note – Record Length Ends With 5 Blanks) – Fixed-Width Format**
Column Number:	1	2-3	4-23	24	25	26-29	30-31	32-33	34-35
Content 01 Example:	I	17	JohnHeisman012318140	5	1	2022	11	07	13
Content 02 Example:	I	17	JohnHeisman012318140	5	1	2022	11	07	13
Content 03 Example:	I	17	JohnHeisman012318140	5	1	2022	11	07	13

continued

Column Number:	36-37	38-39	40-41	42	43-47
Content 01 Example:	28	46	87	V	Blank
Content 02 Example:	34	50	54	V	Blank
Content 03 Example:	38	31	89	V	Blank

All units are given in English units with vehicle length in tenths of feet, inter-axle spacing in tenths of feet, axle weights in pounds, tenths of miles per hour for speed, and degrees Fahrenheit for temperature. All unused entries are to be blank filled.

State highway agencies can submit the IVR (V variant) data using the pipe-delimited format. The key difference between the fixed-width format and the pipe-delimited format is that with the pipe-delimited file, data elements no longer need to match the starting and ending columns. Length of data elements can be equal or shorter than the specified lengths. The field order for the pipe-delimited format is identical to the order for the fixed-width format (see Table 4-23). In this format, the fields are separated by a pipe symbol (|) instead of beginning in specified columns. Example records in this format are provided below.

Delimited Format Examples

Volume Format – Detailed

RT|SFIPS|ID|DIR|LN|YR|MOY|DOM|HOD|MOH|SOM|SSOS|V|VS|

8-Lane Roadway with 12 Individual Vehicles Recorded (No Vehicle Signatures Reported)

I|18|123|3|4|2021|4|25|2|12|5|31|V||

I|18|123|7|3|2021|4|25|2|12|5|37|V||

I|18|123|3|2|2021|4|25|2|12|7|4|V||

I|18|123|3|1|2021|4|25|2|12|8|23|V||

I|18|123|7|1|2021|4|25|2|12|9|89|V||

I|18|123|3|1|2021|4|25|2|12|12|15|V||

I|18|123|7|1|2021|4|25|2|12|15|85|V||

I|18|123|7|3|2021|4|25|2|12|15|92|V||

I|18|123|7|3|2021|4|25|2|12|17|14|V||

I|18|123|7|2|2021|4|25|2|12|17|90|V||

I|18|123|3|3|2021|4|25|2|12|18|1|V||

4.7.2 Speed and Length Classification Data Format (T)

This section includes columns 48-59 for all formats containing Vehicle Classification Data – including formats C, W, and Z.

To submit individual vehicle records that also contain vehicle speed data for each of those vehicles, use the above data format for the first 42 columns, place the letter "T" in column 42, and optionally add vehicle signature data in columns 43-47, then add data to columns 48-59 as described below in Table 4-27. Blank fill all columns for which data are not available.

**Table 4-27. Speed and Length Classification Individual Vehicle Record (T Variant) – Fixed-width Format**
Field	Columns	Width	Description	Type	Importance
1	1	1	Record Type (RT)	Alphanumeric	Required
2	2-3	2	State FIPS Code (SFIPS)	Integer	Required
3	4-23	20	Station Identification (ID)	Alphanumeric	Required
4	24	1	Direction of Travel (DIR)	Integer	Required
5	25	1	Lane of Travel (LN)	Integer	Required
6	26-29	4	Year of Data (YR)	Integer	Required
7	30-31	2	Month of Year (MOY)	Integer	Required
8	32-33	2	Day of Month (DOM)	Integer	Required
9	34-35	2	Hour of Day (HOD)	Integer	Required
10	36-37	2	Minute of Hour (MOH)	Integer	Required
11	38-39	2	Second of Minute (SOM)	Integer	Required
12	40-41	2	Sub Second of Second (SSOS)	Integer	Required
13	42	1	T	Alphanumeric	Required
14	43-47	5	Vehicle Signature/Other Use (VS)	Integer	Optional
15	48-51	4	Vehicle Speed (SPD)	Integer	Required
16	52-53	2	Vehicle Classification (CLS)	Integer	Req./Opt.
17	54-55	2	Number of Axles (NAX)	Integer	Req./Opt.
18	56-59	4	Total Vehicle Length (bumper to bumper) (TVL)	Integer	Req./Opt.

Note: R=Required, O=Optional, R/O=Required/Optional,

Fields designated as Required must be reported.

Fields designated as Optional are not required to be reported.

Fields designated as Required/Optional could be either required or optional based on values used for other related fields.

For Fields 1 – 14 Descriptions, see V Variant Descriptions.

Vehicle Speed (Columns 48-51 – Required
The speed of the vehicle to the nearest tenth of a mph. The decimal is implied between digits 50 and 51.

Blank fill if unused.

Example – for a 104.1 mph vehicle, it would be coded as 1041. For 55.0 mph, it would be coded 0550.
Vehicle Classification (Columns 52-53) – Required/Optional according to the following: Required for C, W and Z devices, Optional for T devices
The classification of the vehicle from FHWA classes 1 to 13. Blank fill if unused.
Number of Axles (Columns 54-55) – Required/Optional according to the following: Required for C, W and Z devices, Optional for T devices
The total number of detected axles in use by the vehicle (including any trailers). Blank fill if unused.

Note – for the number of axles on the recorded vehicle, the data items related to those axles (in record formats C, W, and Z) shall be classified as Required. Otherwise, the remainder of the fields through column 59 should be blank filled. The record should end after column 59 if no axle spacing data are available (record formats C, W, and Z).
Total Vehicle Length (bumper to bumper) (Columns 56-59) – Required/Optional
The total length of the vehicle from bumper to bumper to the nearest tenth of a foot. The decimal is implied between digits 58 and 59. If no total vehicle length is available blank fill this field.

If the data being submitted do not contain axle spacing information, the data record should be 59 characters in length.

Example T Variant records are shown in Table 4-28.

**Table 4-28. Individual Vehicle Record (Speed Site) Example (Northbound Lane 2) – Fixed-Width Format**
Column Number:	1	2-3	4-23	24	25	26-29	30-31	32-33	34-35	36-37
Content 01 Example:	I	17	JohnHeisman012318140	1	2	2012	11	07	09	24
Content 02 Example:	I	17	JohnHeisman012318140	1	2	2012	11	07	09	33
Content 03 Example:	I	17	JohnHeisman012318140	1	2	2012	11	07	09	42

continued

Column Number:	38-39	40-41	42	43-47	48-51	52-53	54-55	56-59
Content 01 Example:	58	38	T	Blank	0624	03	02	0163
Content 02 Example:	12	78	T	Blank	0613	09	05	0691
Content 03 Example:	14	36	T	Blank	0648	02	02	0097

State highway agencies can submit the IVR (T variant) data using the pipe-delimited format. The key difference between the fixed-width format and the pipe-delimited format is that with the pipe-delimited file, data elements no longer need to match the starting and ending columns. Length of data elements can be equal or shorter than the specified lengths. The field order for the pipe-delimited format is identical to the order for the fixed-width format (see Table 4-27). In this format, the fields are separated by a pipe symbol (|) instead of beginning in specified columns. Example records in this format are provided below.

Delimited Format Examples

Speed Format – Detailed

RT|SFIPS|ID|DIR|LN|YR|MOY|DOM|HOD|MOH|SOM|SSOS|T|VS|SPD|CLS|NAX|TVL|

6-lane Roadway with 12 individual vehicles recorded (No Vehicle Signatures, Vehicle classifications, Number of axles or Total Vehicle Lengths reported)

I|15|ABC123|1|3|2021|4|25|2|12|5|31|T||554||||

I|15|ABC123|5|3|2021|4|25|2|12|5|37|T||762||||

I|15|ABC123|1|2|2021|4|25|2|12|7|4|T||605||||

I|15|ABC123|1|1|2021|4|25|2|12|8|23|T||600||||

I|15|ABC123|5|1|2021|4|25|2|12|9|89|T||552||||

I|15|ABC123|1|1|2021|4|25|2|12|12|15|T||571||||

I|15|ABC123|5|1|2021|4|25|2|12|15|85|T||557||||

I|15|ABC123|5|3|2021|4|25|2|12|15|92|T||721||||

I|15|ABC123|5|3|2021|4|25|2|12|17|14|T||728||||

I|15|ABC123|5|2|2021|4|25|2|12|17|90|T||654||||

I|15|ABC123|1|3|2021|4|25|2|12|18|1|T||570||||

I|15|ABC123|1|2|2021|4|25|2|12|19|34|T||611|||

4.7.3 Axle Classification Data Format (C)

This section only applies to those individual records designated with a "C" in Field 13, column 42. The data to be included are described in Table 4-29.

The "C" variant of the Individual Vehicle Record format is used to describe the vehicle characteristics (number and spacing of axles) of traffic observed by axle sensing vehicle classification devices. It is a variable length record, where the length (number of columns) of the record is controlled by the number of axles being reported for each vehicle. The number of axles associated with each vehicle is given in columns 54-55 as described above. This value is used by the TMAS software reading the record to determine how many columns remain to be read in each record. Do NOT zero fill additional columns beyond those required to report the observed axles for each vehicle.

The maximum record size allowed for "C" formatted records is 155 columns. A record this long is needed only if a single vehicle has 25 axles. The number of columns included in each record can be computed with the following formula.

Last column = ((number of axles - 1) x 4) + 59

Where: number of axles is the value found in columns 40 and 41 of that record.

**Table 4-29. Individual Vehicle Record by Classification (Axle) Device (C Variant) – Fixed width**
Field	Columns	Width	Description	Type	Importance
1	1	1	Record Type (RT)	Alphanumeric	Required
2	2-3	2	State FIPS Code (SFIPS)	Integer	Required
3	4-23	20	Station Identification (ID)	Alphanumeric	Required
4	24	1	Direction of Travel (DIR)	Integer	Required
5	25	1	Lane of Travel (LN)	Integer	Required
6	26-29	4	Year of Data (YR)	Integer	Required
7	30-31	2	Month of Year (MOY)	Integer	Required
8	32-33	2	Day of Month (DOM)	Integer	Required
9	34-35	2	Hour of Day (HOD)	Integer	Required
10	36-37	2	Minute of Hour (MOH)	Integer	Required
11	38-39	2	Second of Minute (SOM)	Integer	Required
12	40-41	2	Sub Second of Second (SSOS)	Integer	Required
13	42	1	C	Alphanumeric	Required
14	43-47	5	Vehicle Signature/Other Use (VS)	Integer	Optional
15	48-51	4	Vehicle Speed (SPD)	Integer	Required
16	52-53	2	Vehicle Classification (CLS)	Integer	Required
17	54-55	2	Number of Axles (NAX)	Integer	Required
18	56-59	4	Total Vehicle Length (bumper to bumper) (TVL)	Integer	Optional
19	60-63	4	Axles 1-2 Spacing (ASP1)	Integer	Required
20	64-67	4	Axles 2-3 Spacing (ASP2)	Integer	Req./Opt.
21	68-71	4	Axles 3-4 Spacing (ASP3)	Integer	Req./Opt.
22	72-75	4	Axles 4-5 Spacing (ASP4)	Integer	Req./Opt.
23	76-79	4	Axles 5-6 Spacing (ASP5)	Integer	Req./Opt.
24	80-83	4	Axles 6-7 Spacing (ASP6)	Integer	Req./Opt.
25	84-87	4	Axles 7-8 Spacing (ASP7)	Integer	Req./Opt.
26	88-91	4	Axles 8-9 Spacing (ASP8)	Integer	Req./Opt.
27	92-95	4	Axles 9-10 Spacing (ASP9)	Integer	Req./Opt.
28	96-99	4	Axles 10-11 Spacing (ASP10)	Integer	Req./Opt.
29	100-103	4	Axles 11-12 Spacing (ASP11)	Integer	Req./Opt.
30+	Use additional spacing in 4-digit increments up to 25 axles			Integer	Req./Opt.

Note: R=Required, O=Optional, R/O=Required/Optional, Fields designated as Required must be reported.

Fields designated as Optional are not required to be reported.

Fields designated as Required/Optional could be either required or optional based on values used for other related fields.

The definitions of the data to be contained in columns 1 – 59 for the "C" format are described in Section 4.7.1. The data to be included in columns 60 and later are defined as follows:

Axle 1 to 2 Spacing (Columns 60-63) – Required for C, W, and Z record variants
Enter the total spacing between axles 1 and 2 as a right-justified value, in units of feet. All axle spacings are reported in tenths of a foot with an implied decimal between digits 3 and 4. For example, an axle spacing of 9.6 feet would be entered as "0096."
Axle 2 to 3 Spacing (Columns 64-67) – Required/Optional
Enter the total spacing between axles 2 and 3 as a right-justified, value, in units of feet.
Axle 3 to 4 Spacing (Columns 68-71) – Required/Optional
Enter the total spacing between axles 3 and 4 as a right-justified, value, in units of feet.
Axle 4 to 5 Spacing (Columns 72-75) – Required/Optional
Enter the total spacing between axles 4 and 5 as a right-justified, value, in units of feet.
Axle 5 to 6 Spacing (Columns 76-79) – Required/Optional
Enter the total spacing between axles 5 and 6 as a right-justified, value, in units of feet.
Axle 6 to 7 Spacing (Columns 80-83) – Required/Optional
Enter the total spacing between axles 6 and 7 as a right-justified, value, in units of feet.
Axle 7 to 8 Spacing (Columns 84-87) – Required/Optional
Enter the total spacing between axles 7 and 8 as a right-justified, value, in units of feet.
Axle 8 to 9 Spacing (Columns 88-91) – Required/Optional
Enter the total spacing between axles 8 and 9 as a right-justified, value, in units of feet.
Axle 9 to 10 Spacing (Columns 92-95) – Required/Optional
Enter the total spacing between axles 9 and 10 as a right-justified, value, in units of feet.
Axle 10 to 11 Spacing (Columns 96-99) – Required/Optional
Enter the total spacing between axles 10 and 11 as a right-justified, value, in units of feet.
Axle 11 to 12 Spacing (Columns 100-103) – Required/Optional
Enter the total spacing between axles 11 and 12 as a right-justified, value, in units of feet.

Each additional axle space measurement is allocated four columns. The maximum allowed number of axles is 25, which results in a maximum record length of 155 columns.

Example C Variant records are shown in Table 4-30.

**Table 4-30. Individual Vehicle Record (Classification Site) Example (Eastbound Lane 4) – Fixed-Width Format**
Column Number:	1	2-3	4-23	24	25	26-29	30-31	32-33	34-35	36-37	38-39	40-41	42	43-47	48-51	52-53	54-55
Content 01 Example:	I	17	JohnHeisman012318140	3	4	2012	11	07	18	58	33	48	C	Blank	0582	07	04
Content 02 Example:	I	17	JohnHeisman012318140	3	4	2012	11	07	18	59	57	75	C	Blank	0627	02	02
Content 03 Example:	I	17	JohnHeisman012318140	3	4	2012	11	07	19	00	13	58	C	Blank	0606	13	08

continued

Column Number:	56-59	60-63	64-67	68-71	72-75	76-79	80-83	84-87	88-91	92-95	96-99
Content 01 Example:	0584	0135	0251	0048	Blank	Blank	Blank	Blank	Blank	Blank	Blank
Content 02 Example:	0102	0076	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank
Content 03 Example:	0845	0152	0043	0154	0045	0128	0147	0046	Blank	Blank	Blank

State highway agencies can submit the IVR (C variant) data using the pipe-delimited format. The key difference between the fixed-width format and the pipe-delimited format is that with the pipe-delimited file, data elements no longer need to match the starting and ending columns. Length of data elements can be equal or shorter than the specified lengths. The field order for the pipe-delimited format is identical to the order for the fixed-width format (see Table 4-29). In this format, the fields are separated by a pipe symbol (|) instead of beginning in specified columns. Example records in this format are provided below.

Delimited Format Examples

Classification Format – Detailed

RT|SFIPS|ID|DIR|LN|YR|MOY|DOM|HOD|MOH|SOM|SSOS|C|VS| SPD|CLS|NAX|TVL|ASP1|ASP2|ASP3|ASP4|ASP5|…|ASP10|ASP11|

4-Lane Roadway with 12 Individual Vehicles Recorded

I|32|AB456|1|1|2021|4|25|2|12|5|31|C||554|3|2|135|112

I|32|AB456|5|1|2021|4|25|2|12|5|37|C||762|2|2|113|98

I|32|AB456|1|2|2021|4|25|2|12|7|4|C||605|6|3|245|150|45

I|32|AB456|1|1|2021|4|25|2|12|8|23|C||600|4|2|354|230

I|32|AB456|5|1|2021|4|25|2|12|9|89|C||552|9|5|680|155|43|260|47

I|32|AB456|1|1|2021|4|25|2|12|12|15|C||571|9|5|695|140|43|200|46

I|32|AB456|5|1|2021|4|25|2|12|15|85|C||557|3|2|154|128

I|32|AB456|1|2|2021|4|25|2|12|15|92|C||721|5|2|215|178

I|32|AB456|5|1|2021|4|25|2|12|17|14|C||728|2|2|120|87

I|32|AB456|5|2|2021|4|25|2|12|17|90|C||654|2|2|123|93

I|32|AB456|1|2|2021|4|25|2|12|18|1|C||570|9|5|651|160|44|190|100

I|15|AB456|1|2|2021|4|25|2|12|19|34|C||611|3|2|135|112

4.7.4 Weight Data Format for Reporting Axle Weights (W)

This section only applies to those individual records designated with a W in Field 13, Column 42. Table 4-31 describes the data to be included.

This variation of the individual record format (the "W" record format) is used to describe the number, spacing, and weight of axles for traffic observed by weigh-in-motion scales. The "W variant" is a variable length record, where the length (number of columns) of the record is controlled by the number of axles being reported for each vehicle. The number of axles associated with each vehicle is given in columns 54-55. This value is used by the TMAS software reading the record to determine how many columns should be read in each record. Do NOT zero fill additional columns beyond those required to report the observed axles for each vehicle.

A dummy vehicle signature of 'm' indicates that traffic data for this hour are missing. A dummy vehicle signature of 'd' indicates that traffic data for this hour are not missing, and thus if there are no traffic records for the hour, then there were no trucks during that hour. Without these indications, no traffic records for an hour might be interpreted to mean that the traffic system was not working.

The maximum record size permitted for "W" formatted records is 284 columns. A record this long is needed only if a single vehicle has 25 axles. The number of columns included in each record can be computed with the following formula.

Last column = ((number of axles - 1) x 9) + 68

Where:

number of axles is the value found in columns 54-55 of that record. Based on this 'last column' calculation, some optional fields could become required if it is determined that more than 2 axles are on the given vehicle being reported in the record.

**Table 4-31. Individual Vehicle Record by Weight (Axle) Device (W Variant) – Fixed Width Format**
Field	Columns	Width	Description	Type	Importance
1	1	1	Record Type (RT)	Alphanumeric	Required
2	2-3	2	State FIPS Code (SFIPS)	Integer	Required
3	4-23	20	Station Identification (ID)	Alphanumeric	Required
4	24	1	Direction of Travel (DIR)	Integer	Required
5	25	1	Lane of Travel (LN)	Integer	Required
6	26-29	4	Year of Data (YR)	Integer	Required
7	30-31	2	Month of Year (MOY)	Integer	Required
8	32-33	2	Day of Month (DOM)	Integer	Required
9	34-35	2	Hour of Day (HOD)	Integer	Required
10	36-37	2	Minute of Hour (MOH)	Integer	Required
11	38-39	2	Second of Minute (SOM)	Integer	Required
12	40-41	2	Sub Second of Second (SSOS)	Integer	Required
13	42	1	W	Alphanumeric	Required
14	43-47	5	Vehicle Signature/Other Use (VS)	Integer	Optional
15	48-51	4	Vehicle Speed (SPD)	Integer	Required
16	52-53	2	Vehicle Classification (CLS)	Integer	Required
17	54-55	2	Number of Axles (NAX)	Integer	Required
18	56-59	4	Total Vehicle Length (bumper to bumper) (TVL)	Integer	Optional
19	60-62	3	Pavement Temperature (PT)	Integer	Optional
20	63-68	6	Gross Vehicle Weight (GVW)	Integer	Required
21	69-73	5	Axle Weight 1 (AW1)	Integer	Required
22	74-77	4	Axles 1-2 Spacing (ASP1)	Integer	Required
23	78-82	5	Axle Weight 2 (AW2)	Integer	Required
24	83-86	4	Axles 2-3 Spacing (ASP2)	Integer	Req./Opt.
25	87-91	5	Axle Weight 3 (AW3)	Integer	Req./Opt.
26	92-95	4	Axles 3-4 Spacing (ASP3)	Integer	Req./Opt.
27	96-100	5	Axle Weight 4 (AW4)	Integer	Req./Opt.
28	101-104	4	Axles 4-5 Spacing (ASP4)	Integer	Req./Opt.
29	105-109	5	Axle Weight 5 (AW5)	Integer	Req./Opt.
30	110-113	4	Axles 5-6 Spacing (ASP5)	Integer	Req./Opt.
31	114-118	5	Axle Weight 6 (AW6)	Integer	Req./Opt.
32	119-122	4	Axles 6-7 Spacing (ASP6)	Integer	Req./Opt.
33	123-127	5	Axle Weight 7 (AW7)	Integer	Req./Opt.
34	128-131	4	Axles 7-8 Spacing (ASP7)	Integer	Req./Opt.
35	132-136	5	Axle Weight 8 (AW8)	Integer	Req./Opt.
36	137-140	4	Axles 8-9 Spacing (ASP8)	Integer	Req./Opt.
37	141-145	5	Axle Weight 9 (AW9)	Integer	Req./Opt.
38	146-149	4	Axles 9-10 Spacing (ASP9)	Integer	Req./Opt.
39	150-154	5	Axle Weight 10 (AW10)	Integer	Req./Opt.
40	155-158	4	Axles 10-11 Spacing (ASP10)	Integer	Req./Opt.
41	159-163	5	Axle Weight 11 (AW11)	Integer	Req./Opt.
42	164-167	4	Axles 11-12 Spacing (ASP11)	Integer	Req./Opt.
43	168-172	5	Axle Weight 12 (AW12)	Integer	Req./Opt.
44, 46, 48, …	Use additional spacing in 4-digit increments up to 25 axles	4	Use additional spacing in 4-digit increments up to 25 axles	Integer	Req./Opt.
45, 47, 49, …	Use additional weights in 5-digit increments up to 25 axles	5	Use additional weights in 5-digit increments up to 25 axles	Integer	Req./Opt.

Note: R = Required, O = Optional, R/O = Required/Optional

Fields designated as Required must be reported.

Fields designated as Optional are not required to be reported.

Fields designated as Required/Optional could be either required or optional based on values used for other related fields.

The data to be provided in columns 1 – 59 are described earlier in Sections 4.7.1 and 4.7.2. The data to be included in columns 60 and later are defined as follows:

Pavement Temperature (Columns 60-62) – Optional
Enter the pavement temperature rounded to the nearest integer Fahrenheit value. A negative sign may be placed in column 60 if appropriate. If the pavement temperature is unknown blank fill these digits.
Gross Vehicle Weight (Columns 63-68) – Required
Enter the total vehicle weight (GVW) as a right-justified, decimal value, in units of pounds. For example, the axle weight measured as 90,250 pounds could be entered as "_ 90250" or as "090250" (where "_" represents a blank space.) This value should equal the sum of all of the individual axle weights.
Axle Weight 1 (Columns 69-73) – Required
Enter the total axle 1 weight as a right-justified, decimal value, in units of pounds. For example, the axle weight measured as 9,120 pounds could be entered as "_ 9120" or as "09120" (where "_" represents a blank space.)
Axle 1 to 2 Spacing (Columns 74-77) – Required
Enter the total spacing between axles 1 and 2 as a right-justified value, in units of tenths of feet. All axle spacings are reported with an implied decimal between digits 3 and 4. For example, an axle spacing of 11.35 feet would be entered as "0114" or "_114" and an axle spacing of 9.6 feet would be entered as "0096" or " 96" (where "_" represents a blank space).
Axle Weight 2 (Columns 78-82) – Required
Enter the total axle 2 weight as a right-justified value, in units of pounds.
Axle 2 to 3 Spacing (Columns 83-86) – Required/Optional
Enter the total spacing between axles 2 and 3 as a right-justified value, in units of tenths of feet.
Axle Weight 3 (Columns 87-91) – Required/Optional
Enter the total axle 3 weight as a right-justified, decimal value, in units of pounds.
Axle 3 to 4 Spacing (Columns 92-95) – Required/Optional
Enter the total spacing between axles 3 and 4 as a right-justified value, in units of tenths of feet.
Axle Weight 4 (Columns 96-100) – Required/Optional
Enter the total axle 4 weight as a right-justified, value, in units of pounds.
Axle 4 to 5 Spacing (Columns 101-104) – Required/Optional
Enter the total spacing between axles 4 and 5 as a right-justified value, in units of tenths of feet.
Axle Weight 5 (Columns 105-109) – Required/Optional
Enter the total axle 5 weight as a right-justified value, in units of pounds.
Axle 5 to 6 Spacing (Columns 110-113) – Required/Optional
Enter the total spacing between axles 5 and 6 as a right-justified value, in units of tenths of feet.
Axle Weight 6 (Columns 114-118) – Required/Optional
Enter the total axle 6 weight as a right-justified value, in units of pounds.
Axle 6 to 7 Spacing (Columns 119-122) – Required/Optional
Enter the total spacing between axles 6 and 7 as a right-justified value, in units of tenths of feet.
Axle Weight 7 (Columns 123-127) – Required/Optional
Enter the total axle 7 weight as a right-justified value, in units of pounds.
Axle 7 to 8 Spacing (Columns 128-131) – Required/Optional
Enter the total spacing between axles 7 and 8 as a right-justified value, in units of tenths of feet.
Axle Weight 8 (Columns 132-136) – Required/Optional
Enter the total axle 8 weight as a right-justified value, in units of pounds.
Axle 8 to 9 Spacing (Columns 137-140) – Required/Optional
Enter the total spacing between axles 8 and 9 as a right-justified value, in units of tenths of feet.
Axle Weight 9 (Columns 141-145) – Required/Optional
Enter the total axle 9 weight as a right-justified value, in units of pounds.
Axle 9 to 10 Spacing (Columns 146-149) – Required/Optional
Enter the total spacing between axles 9 and 10 as a right-justified value, in units of tenths of feet.
Axle Weight 10 (Columns 150-154) – Required/Optional
Enter the total axle 10 weight as a right-justified value, in units of pounds.
Axle 10 to 11 Spacing (Columns 155-158) – Required/Optional
Enter the total spacing between axles 10 and 11 as a right-justified value, in units of tenths of feet.
Axle Weight 11 (Columns 159-163) – Required/Optional
Enter the total axle 11 weight as a right-justified value, in units of pounds.
Axle 11 to 12 Spacing (Columns 164-167) – Required/Optional
Enter the total spacing between axles 11 and 12 as a right-justified value, in units of tenths of feet.
Axle Weight 12 (Columns 168-172) – Required/Optional
Enter the total axle 12 weight as a right-justified value, in units of pounds.

For each additional axle beyond the 12th axle, an additional nine columns should be entered. The first four of these columns are the axle spacing to the next axle, followed by the five columns for the weight of that next axle. The maximum number of axles permitted is 25, which uses a record length of 284 columns.

Example W Variant records are shown in Table 4-32.

**Table 4-32. Individual Vehicle Record (Weight Site) Example (Westbound Lane 3) – Fixed-Width Format**
Column Number:	1	2-3	4-23	24	25	26-29	30-31	32-33	34-35	36-37	38-39	40-41	42	43-47	48-51
Content 01 Example:	I	17	JohnHeisman012318140	7	3	2012	11	07	05	12	Bl4	72	W	Blank	0551
Content 02 Example:	I	17	JohnHeisman012318140	7	3	2012	11	07	05	12	Bl8	Bl1	W	Blank	0572
Content 03 Example:	I	17	JohnHeisman012318140	7	3	2012	11	07	95	12	43	78	W	Blank	0560

continued

Column Number:	52-53	54-55	56-59	60-62	63-68	69-73	74-77	78-82	83-86	87-91	92-95	96-100	101-104	105-109
Content 01 Example:	03	02	0174	065	008660	03215	0142	05445	Blank	Blank	Blank	Blank	Blank	Blank
Content 02 Example:	05	02	0211	064	012143	05620	0187	06523	Blank	Blank	Blank	Blank	Blank	Blank
Content 03 Example:	09	05	0753	064	076978	12518	0152	15790	0043	16250	0285	16535	0085	15885

continued

Column Number:	110-113	114-118	119-122	123-127	128-131	132-136	137-140	141-145	146-149	150-154	155-158	159-163	164-167	168-172
Content 01 Example:	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank
Content 02 Example:	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank
Content 03 Example:	Blank	Blank	Blank	blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank

Use additional spacing in 4-digit increments up to 25 axles

Use additional weights in 3-digit increments up to 25 axles

State highway agencies can submit the IVR (W variant) data using the pipe-delimited format. The key difference between the fixed-width format and the pipe-delimited format is that with the pipe-delimited file, data elements no longer need to match the starting and ending columns. Length of data elements can be equal or shorter than the specified lengths. The field order for the pipe-delimited format is identical to the order for the fixed-width format (see Table 4-31). In this format, the fields are separated by a pipe symbol (|) instead of beginning in specified columns. Example records in this format are provided below.

Delimited Format Examples

Weight (Axle) Format – Detailed

RT|SFIPS|ID|DIR|LN|YR|MOY|DOM|HOD|MOH|SOM|SSOS|W|VS|SPD|CLS|NAX|TVL|PT|GVW|AW1|ASP1|AW2|ASP2|AW3|ASP3|AW4|

ASP4|…|AW11|ASP11|AW12|ASP12|…

4-Lane Roadway with 15 Individual Vehicles Recorded

I|12|135750|1|1|2021|4|25|2|12|5|31|W|65310|554|9|5|694|70|61837|10500|145|12000|43|12500|310|13450|46|13387

I|12|135760|5|1|2021|4|25|2|12|5|37|W|52810|762|5|2|275|69|14874|8462|185|6412

I|12|135760|5|2|2021|4|25|2|12|5|68|W|12120|648|1|2|75|69|232|88|53|144

I|12|135760|1|2|2021|4|25|2|12|7|4|W|43460|605|4|3|452|70|25886|9750|246|7680|43|8456

I|12|135760|1|1|2021|4|25|2|12|8|23|W|65227|600|9|5|585|70|54828|9873|173|11678|43|10985|300|11245|40|11047

I|12|135760|5|2|2021|4|25|2|12|8|68|W|22290|648|2|2|162|69|2438|1890|97|548

I|12|135760|5|1|2021|4|25|2|12|9|89|W|64220|552|8|4|429|69|40561|9504|130|11546|175|9728|41|9783

I|12|135760|1|1|2021|4|25|2|12|12|15|W|65949|571|9|5|560|70|70044|11620|165|12895|43|12530|230|16750|82|16249

I|12|135760|5|2|2021|4|25|2|12|8|68|W|22219|648|2|2|145|68|4096|3348|88|748

I|12|135760|5|1|2021|4|25|2|12|15|85|W|66227|557|10|6|708|69|79973|11463|152|10486|48|10866|48|10562|355|15995|42|16541

I|12|135760|1|2|2021|4|25|2|12|15|92|W|65950|721|9|5|546|70|72741|11231|175|14780|40|15345|235|15245|39|16140

I|12|135760|1|1|2021|4|25|2|12|17|14|W|32340|728|3|2|213|69|3243|1710|132|1533

I|12|135760|5|2|2021|4|25|2|12|17|90|W|32321|654|3|3|360|68|13114|2590|128|2824|167|7700

I|12|135760|5|1|2021|4|25|2|12|20|54|W|22210|728|2|2|125|69|1884|1088|87|796

I|12|135760|5|2|2021|4|25|2|12|27|92|W|42420|654|4|2|400|68|22580|14600|241|7980

4.7.5 Vehicle Classification and Wheel Weights (Z)

This section only applies to those individual records designated with a Z in Field 13, column 42. The data to be included are described in Table 4-33.

The "Z" variant of the individual record format is used to describe the number, spacing, and weight of axles for traffic observed by weigh-in-motion scales that measure both left and right axle weights. It differs from the "W" record by the fact that it allows the user to report the left- and right-side wheel path weights independently for each axle. These data are available when independent weight sensors are placed in the two wheel paths, which is typically the case for bending plate, load cell load scale, and some by wheel path Piezo systems. Like the "C" and "W" record variants, the "Z variant" is a variable length record, where the length (number of columns) of the record is controlled by the number of axles being reported for each vehicle. The number of axles associated with each vehicle is given in columns 54-55 as described in Section 4.7.2. This value is used by the TMAS software to determine how many remaining columns to expect in each record. Do NOT zero fill additional columns beyond those required to report the observed number of axles for each vehicle.

The maximum record size permitted for "Z" formatted records is 418 columns. A record this long is needed only if a single vehicle has 25 axles. The number of columns included in each record can be computed with the following formula.

Last column = (number of axles x 14) + 68

Where:

number of axles is the value found in columns 54-55 of the record.

**Table 4-33. Individual Vehicle Record Collected by Weight (Left and Right) Device (Z Variant) – Fixed-Width Format**
Field	Columns	Width	Description	Type	Importance
1	1	1	Record Type (RT)	Alphanumeric	Required
2	2-3	2	State FIPS Code (SFIPS)	Integer	Required
3	4-23	20	Station Identification (ID)	Alphanumeric	Required
4	24	1	Direction of Travel (DIR)	Integer	Required
5	25	1	Lane of Travel (LN)	Integer	Required
6	26-29	4	Year of Data (YR)	Integer	Required
7	30-31	2	Month of Year (MOY)	Integer	Required
8	32-33	2	Day of Month (DOM)	Integer	Required
9	34-35	2	Hour of Day (HOD)	Integer	Required
10	36-37	2	Minute of Hour (MOH)	Integer	Required
11	38-39	2	Second of Minute (SOM)	Integer	Required
12	40-41	2	Sub Second of Second (SSOS)	Integer	Required
13	42	1	Z	Alphanumeric	Required
14	43-47	5	Vehicle Signature/Other Use (VS)	Integer	Optional
15	48-51	4	Vehicle Speed (SPD)	Integer	Required
16	52-53	2	Vehicle Classification (CLS)	Integer	Required
17	54-55	2	Number of Axles (NAX)	Integer	Required
18	56-59	4	Total Vehicle Length (bumper to bumper) (TVL)	Integer	Optional
19	60-62	3	Pavement Temperature (PT)	Integer	Optional
20	63-68	6	Gross Vehicle Weight (GVW)	Integer	Required
21	69-73	5	Weight 1 Left Wheel Path (LW1)	Integer	Required
22	74-78	5	Weight 1 Right Wheel Path (RW1)	Integer	Required
23	79-82	4	Axles 1-2 Spacing (ASP1)	Integer	Required
24	83-87	5	Weight 2 Left Wheel Path (LW2)	Integer	Required
25	88-92	5	Weight 2 Right Wheel Path (RW2)	Integer	Required
26	93-96	4	Axles 2-3 Spacing (ASP2)	Integer	Req./Opt.
27	97-101	5	Weight 3 Left Wheel Path (LW3)	Integer	Req./Opt.
28	102-106	5	Weight 3 Right Wheel Path (RW3)	Integer	Req./Opt.
29	107-110	4	Axles 3-4 Spacing (ASP3)	Integer	Req./Opt.
30	111-115	5	Weight 4 Left Wheel Path (LW4)	Integer	Req./Opt.
31	116-120	5	Weight 4 Right Wheel Path (RW4)	Integer	Req./Opt.
32	121-124	4	Axles 4-5 Spacing (ASP4)	Integer	Req./Opt.
33	125-129	5	Weight 5 Left Wheel Path (LW5)	Integer	Req./Opt.
34	130-134	5	Weight 5 Right Wheel Path (RW5)	Integer	Req./Opt.
35	135-138	4	Axles 5-6 Spacing (ASP5)	Integer	Req./Opt.
36	139-143	5	Weight 6 Left Wheel Path (LW6)	Integer	Req./Opt.
37	144-148	5	Weight 6 Right Wheel Path (RW6)	Integer	Req./Opt.
38	149-152	4	Axles 6-7 Spacing (ASP6)	Integer	Req./Opt.
39	153-157	5	Weight 7 Left Wheel Path (LW7)	Integer	Req./Opt.
40	158-162	5	Weight 7 Right Wheel Path (RW7)	Integer	Req./Opt.
41	163-166	4	Axles 7-8 Spacing (ASP7)	Integer	Req./Opt.
42	167-171	5	Weight 8 Left Wheel Path (LW8)	Integer	Req./Opt.
43	172-176	5	Weight 8 Right Wheel Path (RW8)	Integer	Req./Opt.
44	177-180	4	Axles 8-9 Spacing (ASP8)	Integer	Req./Opt.
45	181-185	5	Weight 9 Left Wheel Path (LW9)	Integer	Req./Opt.
46	186-190	5	Weight 9 Right Wheel Path (RW9)	Integer	Req./Opt.
47	191-194	4	Axles 9-10 Spacing (ASP9)	Integer	Req./Opt.
48	195-199	5	Weight 10 Left Wheel Path (LW10)	Integer	Req./Opt.
49	200-204	5	Weight 10 Right Wheel Path (RW10)	Integer	Req./Opt.
50	205-208	4	Axles 10-11 Spacing (ASP10)	Integer	Req./Opt.
51	209-213	5	Weight 11 Left Wheel Path (LW11)	Integer	Req./Opt.
52	214-218	5	Weight 11 Right Wheel Path (RW11)	Integer	Req./Opt.
53	219-222	4	Axles 11-12 Spacing (ASP11)	Integer	Req./Opt.
54	223-227	5	Weight 12 Left Wheel Path (LW12)	Integer	Req./Opt.
55	228-232	5	Weight 12 Right Wheel Path (RW12)	Integer	Req./Opt.
56+	Use 4 columns for each axle up to 25 axles (include 10 columns of weight prior to the next axle distance)	4	Axle spacing	Integer	Req./Opt.
57+	Use 5 columns for each additional axle for the left wheel path weight, up to 25 axles	5	Weight Left Wheel Path	Integer	Req./Opt.
58+	Use 5 columns for each additional axle for the right wheel path weight, up to 25 axles	5	Weight Right Wheel Path	Integer	Req./Opt.

Note: R=Required, O=Optional, R/O=Required/Optional, Fields designated as Required must be reported.

Fields designated as Optional are not required to be reported.

Fields designated as Required/Optional could be either required or optional based on values used for other related fields.

The definitions of the data to be contained in columns 1 – 59 for the "Z" format are described in Sections 4.7.1 and 4.7.2. The data to be included in columns 60 and later are defined as follows:

Pavement Temperature (Columns 60-62) – Optional
Enter the pavement temperature rounded to the nearest integer Fahrenheit value. A negative sign may be placed in Column 60 if required. If the pavement temperature is unknown blank fill these digits.
Gross Vehicle Weight (Columns 63-68) – Required
Enter the total vehicle weight (GVW) as a right-justified, decimal value, in units of pounds. For example, the axle weight measured as 90,210 pounds could be entered as "_ 90210" or as "090210" (where "_" represents a blank space.) This value should equal the sum of all of the individual axle weights.
Weight 1 Left Wheel Path (Columns 69-73) – Required
Enter the left axle 1 weight as a right-justified value, in units of pounds. For example, the axle weight measured as 9,120 pounds could be entered as "09120" or "_9120". If no left weight measured leave the field empty.
Weight 1 Right Wheel Path (Columns 74-78) – Required
Enter the right axle 1 weight as a right-justified value, in units of pounds. If no right weight measured leave the field empty
Axle 1 to 2 Spacing (Columns 79-82) – Required
Enter the total spacing between axles 1 and 2 as a right-justified value, in units of tenths of feet. All axle spacings are reported in tenths of a foot with an implied decimal between digits 3 and 4. For example, an axle spacing of 11.35 feet would be entered as "0114."
Weight 2 Left Wheel Path (Columns 83-87) – Required
Enter the left axle 2 weight as a right-justified value, in units of pounds.
Weight 2 Right Wheel Path (Columns 88-92) – Required
Enter the right axle 2 weight as a right-justified value, in units of pounds.
Axle 2 to 3 Spacing (Columns 93-96) – Required/Optional
Enter the total spacing between axles 2 and 3 as a right-justified value, in units of tenths of feet.
Weight 3 Left Wheel Path (Columns 97-101) – Required/Optional
Enter the left axle 3 weight as a right-justified value, in units of pounds.
Weight 3 Right Wheel Path (Columns 102-106) – Required/Optional
Enter the right axle 3 weight as a right-justified, decimal value, in units of pounds.
Axle 3 to 4 Spacing (Columns 107-110) – Required/Optional
Enter the total spacing between axles 3 and 4 as a right-justified value, in units of tenths of feet.
Weight 4 Left Wheel Path (Columns 111-115) – Required/Optional
Enter the left axle 4 weight as a right-justified value, in units of pounds.
Weight 4 Right Wheel Path (Columns 116-120) – Required/Optional
Enter the right axle 4 weight as a right-justified value, in units of pounds.
Axle 4 to 5 Spacing (Columns 121-124) – Required/Optional
Enter the total spacing between axles 4 and 5 as a right-justified value, in units of tenths of feet.
Weight 5 Left Wheel Path (Columns 125-129) – Required/Optional
Enter the left axle 5 weight as a right-justified value, in units of pounds.
Weight 5 Right Wheel Path (Columns 130-134) – Required/Optional
Enter the right axle 5 weight as a right-justified value, in units of pounds.
Axle 5 to 6 Spacing (Columns 135-138) – Required/Optional
Enter the total spacing between axles 5 and 6 as a right-justified value, in units of tenths of feet.
Weight 6 Left Wheel Path (Columns 139-143) – Required/Optional
Enter the left axle 6 weight as a right-justified value, in units of pounds.
Weight 6 Right Wheel Path (Columns 144-148) – Required/Optional
Enter the right axle 6 weight as a right-justified value, in units of pounds.
Axle 6 to 7 Spacing (Columns 149-152) – Required/Optional
Enter the total spacing between axles 6 and 7 as a right-justified value, in units of tenths of feet.
Weight 7 Left Wheel Path (Columns 153-157) – Required/Optional
Enter the left axle 7 weight as a right-justified value, in units of pounds.
Weight 7 Right Wheel Path (Columns 158-162) – Required/Optional
Enter the right axle 7 weight as a right-justified value, in units of pounds.
Axle 7 to 8 Spacing (Columns 163-166) – Required/Optional
Enter the total spacing between axles 7 and 8 as a right-justified value, in units of tenths of feet.
Weight 8 Left Wheel Path (Columns 167-171) – Required/Optional
Enter the left axle 8 weight as a right-justified value, in units of pounds.
Weight 8 Right Wheel Path (Columns 172-176) – Required/Optional
Enter the right axle 8 weight as a right-justified value, in units of pounds.
Axle 8 to 9 Spacing (Columns 177-180) – Required/Optional
Enter the total spacing between axles 8 and 9 as a right-justified value, in units of tenths of feet.
Weight 9 Left Wheel Path (Columns 181-185) – Required/Optional
Enter the left axle 9 weight as a right-justified value, in units of pounds.
Weight 9 Right Wheel Path (Columns 186-190) – Required/Optional
Enter the right axle 9 weight as a right-justified value, in units of pounds.
Axle 9 to 10 Spacing (Columns 191-194) – Required/Optional
Enter the total spacing between axles 9 and 10 as a right-justified value, in units of tenths of feet.
Weight 10 Left Wheel Path (Columns 195-199) – Required/Optional
Enter the left axle 10 weight as a right-justified value, in units of pounds.
Weight 10 Right Wheel Path (Columns 200-204) – Required/Optional
Enter the right axle 10 weight as a right-justified value, in units of pounds.
Axle 10 to 11 Spacing (Columns 205-208) – Required/Optional
Enter the total spacing between axle 10 and 11 as a right-justified value, in units of tenths of feet.
Weight 11 Left Wheel Path (Columns 209-213) – Required/Optional
Enter the left axle 11 weight as a right-justified value, in units of pounds.
Weight 11 Right Wheel Path (Columns 214-218) – Required/Optional
Enter the right axle 11 weight as a right-justified value, in units of pounds.
Axle 11 to 12 Spacing (Columns 219-222) – Required/Optional
Enter the total spacing between axle 11 and 12 as a right-justified value, in units of tenths of feet.
Weight 12 Left Wheel Path (Columns 223-227) – Required/Optional
Enter the total axle 12 weight as a right-justified value, in units of pounds.
Weight 12 Right Wheel Path (Columns 228-232) – Required/Optional
Enter the total axle 12 weight as a right-justified value, in units of pounds.

For each additional axle beyond the twelfth axle, an additional fourteen columns should be entered. The first four of these columns contain the axle spacing from the previous axle, followed by five columns for the weight measured in the left wheel path for that axle, followed by five more columns for the weight measured in the right wheel path. The maximum number of axles permitted is 25, which creates a record length of 418 columns.

Example Z Variant records are shown in Table 4-34.

**Table 4-34. Individual Vehicle Record (Left and Right Site) Example (Westbound Lane 1) – Fixed-Width Format**
Column Number:	1	2-3	4-23	24	25	26-29	30-31	32-33	34-35	36-37	38-39	40-41	42	43-47	48-51	52-53
Content 01 Example:	Z	17	RobertPlantLane18119	7	1	2021	11	09	07	10	34	74	Z	Blank	0561	01
Content 02 Example:	Z	17	RobertPlantLane18119	7	1	2021	11	09	07	10	38	38	Z	Blank	0605	02
Content 03 Example:	Z	17	RobertPlantLane18119	7	1	2021	11	09	07	10	58	81	Z	Blank	0593	07
Content 04 Example:	Z	17	RobertPlantLane18119	7	1	2021	11	09	07	10	80	45	Z	Blank	0585	10
Content 05 Example:	Z	17	RobertPlantLane18119	7	1	2021	11	09	07	20	25	13	Z	Blank	0601	09

continued

Column Number:	54-55	56-59	60-62	63-68	69-73	74-78	79-82	83-87	88-92	93-96	97-101	102-106	107-110	111-115	116-120
Content 01 Example:	02	0074	071	000265	00075	00065	0051	00065	00060	Blank	Blank	Blank	Blank	Blank	Blank
Content 02 Example:	02	0174	071	003130	00780	00770	0078	00800	00780	Blank	Blank	Blank	Blank	Blank	Blank
Content 03 Example:	04	0174	070	041061	07335	06742	0128	03478	03765	0038	05200	04797	0045	04935	04809
Content 04 Example:	08	0778	071	085300	06025	06055	0161	05705	05885	0042	05870	05940	0042	05778	05822
Content 05 Example:	05	0652	070	077940	05410	05397	0158	08301	08304	0043	08305	08338	0257	08475	08473

continued

Column Number:	121-124	125-129	130-134	135-138	139-143	144-148	149-152	153-157	158-162	163-166	167-171	172-176	177-180	181-185	186-190
Content 01 Example:	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank
Content 02 Example:	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank
Content 03 Example:	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank
Content 04 Example:	0284	04719	04781	0043	04714	04735	0043	04820	04832	0043	04804	04815	Blank	Blank	Blank
Content 05 Example:	0044	08461	08476	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank

continued

Column Number:	191-194	195-199	200-204	205-208	209-213	214-218	219-222	223-227	228-232
Content 01 Example:	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank
Content 02 Example:	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank
Content 03 Example:	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank
Content 04 Example:	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank
Content 05 Example:	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank	Blank

Use 14 columns for each additional axle spacing up to 25 axles (include 5 columns of left weight and 5 for the right axle weight prior to the next axle distance)

State highway agencies can submit the IVR (Z variant) data using the pipe-delimited format. The key difference between the fixed-width format and the pipe-delimited format is that with the pipe-delimited file, data elements no longer need to match the starting and ending columns. Length of data elements can be equal or shorter than the specified lengths. The field order for the pipe-delimited format is identical to the order for the fixed-width format (see Table 4-33). In this format, the fields are separated by a pipe symbol (|) instead of beginning in specified columns. Example records in this format are provided below.

Delimited Format Examples

Weight (Left and Right) Format – Detailed

RT|SFIPS|ID|DIR|LN|YR|MOY|DOM|HOD|MOH|SOM|SSOS|Z|VS|SPD|CLS|NAX|TVL|PT|GVW|LW1|RW1|ASP1|LW2|RW2|ASP2|LW3|RW3|…|ASP12|LW12|

RW12|…

2-Lane Roadway with 15 Individual Vehicles Recorded

I|12|135750|1|1|2021|4|25|2|12|5|31|Z|65310|554|9|5|694|70|61837|5200|5300|145|5995|6005|43|5830|6670|310|6720|6730|46|6695|6694

I|12|135760|5|1|2021|4|25|2|12|5|37|Z|52810|762|5|2|275|69|14874|4101|4361|185|3052|3360

I|12|135760|5|2|2021|4|25|2|12|5|68|Z|12120|648|1|2|75|69|232||88|53||144

I|12|135760|1|2|2021|4|25|2|12|7|4|Z|43460|605|4|3|452|70|25886|4405|5345|246|3604|4076|43|4046|4410

I|12|135760|1|1|2021|4|25|2|12|8|23|Z|65227|600|9|5|585|70|54828|4507|5366|173|5521|6157|43|5274|5711|300|5505|5740|40|5294|5753

I|12|135760|5|2|2021|4|25|2|12|8|68|Z|22290|648|2|2|162|69|2438|852|1038|97|261|287|

I|12|135760|5|1|2021|4|25|2|12|9|89|Z|64220|552|8|4|429|69|40561|4503|5001|130|5438|6108|175|4508|5220|41|4597|5186

I|12|135760|1|1|2021|4|25|2|12|12|15|Z|65949|571|9|5|560|70|70044|5605|6015|165|5947|6948|43|6032|6498|230|8001|8749|82|7943|8306

I|12|135760|5|2|2021|4|25|2|12|8|68|Z|22219|648|2|2|145|68|3096|1140|1208|88|344|404|

I|12|135760|5|1|2021|4|25|2|12|15|85|Z|66227|557|10|6|708|69|75963|5353|6110|152|5006|5480|48|5216|5650|48|5100|5462|355|7899|8146|42|8105|8436

I|12|135760|1|2|2021|4|25|2|12|15|92|Z|65950|721|9|5|546|70|72741|5600|5631|175|7357|7423|40|7651|7694|235|7605|7640|39|8023|8117

I|12|135760|1|1|2021|4|25|2|12|17|14|Z|32340|728|3|2|213|69|3243|845|865|132|740|793

I|12|135760|5|2|2021|4|25|2|12|17|90|Z|32321|654|3|3|360|68|14114|1250|1340|128|1874|1950|167|3781|3919

I|12|135760|5|1|2021|4|25|2|12|20|54|Z|22210|728|2|2|125|69|1884|531|557|87|391|405

I|12|135760|5|2|2021|4|25|2|12|27|92|Z|42420|654|4|2|400|68|22580|7320|7280|241|3952|4028

4.8 MICROMOBILITY STATION RECORD DATA FORMAT (FIXED WIDTH OR PIPE DELIMITED)

Collecting and reporting Micromobility travel is growing in importance due to an increased number of users selecting more active modes of transportation (e.g., walking, biking, scootering, and other battery-powered devices). It is important to track the changes in walking, biking, and scootering that may result from changes in public attitudes, land use, new policy implementation, and the construction of new facilities.

Two types of records are needed for submitting Micromobility data to FHWA's TMAS system.

Micromobility Station Record – Section 4.8
Micromobility Count Record – Section 4.9

A Micromobility Station Record is needed for reporting all Micromobility data to FHWA. The Station Record provides data and information related to the location of the monitored site and other relevant data that can be used in conjunction with the Count Record for specific data analyses. If a Micromobility Station Record is omitted, any succeeding records containing Micromobility data will not be able to be processed by TMAS.

The TMAS software retains all approved Station Records as of December 31^st of each year. FHWA recommends that a yearly review of all Station Record fields be conducted to ensure the records are current and accurately reflect what is in the field.

A Station Record file is a text file often designated by the .txt file extension. Before uploading the file to TMAS, it is recommended to use .SMM as the file extension where SMM stands for Station Micromobility.

Below is an example Station Record file naming convention:

StationABC123.SMM

General Guidance

The Station Record consists of the data fields listed in Table 4-35. These data fields can be organized either by Pipe (|) Delimited format or Fixed Width Column format. The Pipe (|) Delimited format is recommended due to its flexibility and easy-to-use nature.

It is highly recommended to use the Pipe (|) delimited format.
With this format, there is no need to keep track of entry column locations.

Regardless of the format that is used, the length of each data field cannot exceed the specified field length (column width). Information exceeding the allowed field length (column width) in the Pipe-Delimited file will be truncated, while information less than the allowed width will be accepted as provided.

When using the Fixed Width Column format, any misalignment of the data field will lead to errors and the rejection or misinterpretation of the data.

**Table 4-35. Summary of the Micromobility Station Record Data Fields**
Field	Columns	Width	Description	Type	Importance
1	1	1	Micromobility Station Record Indicator (MSRI)	Alphanumeric	Required
2	2-3	2	State FIPS Code (SFIPS)	Integer	Required
3	4-6	3	County FIPS (CFIPS)	Integer	Required
4	7-16	10	Reporting Agency Indicator (RAI)	Alphanumeric	Required
5	17-76	60	Station ID (SID)	Alphanumeric	Required
6	77-87	11	Latitude (LAT)	Real	Required
7	88-98	11	Longitude (LONG)	Real	Required
8	99-100	2	Function Class and Area Type (FCAT)	Alphanumeric	Optional
9	101	1	Type of Sensor (TS)	Alphanumeric	Optional
10	102	1	Primary Count Purpose (PCP)	Alphanumeric	Optional
11	103-106	4	Year Station Established (YEARE)	Integer	Optional
12	107-110	4	Year Station Discontinued (YEARD)	Integer	Optional
13	111-112	2	Posted Route Sign (PRS)	Alphanumeric	Optional
14	113-120	8	Posted Route Sign Number (PRSN)	Alphanumeric	Optional
15	121-220	100	Other Notes (ON)	Alphanumeric	Optional

Specific Data Fields Explanation

A Station Record offers information characterizing where the traveling bicyclists and/or pedestrians are as well as other relevant information described in the data items. These variables help to efficiently analyze the data.

Micromobility Station Record Indicator (MSRI) (Width 1) – Required
- The letter "L" is always coded to indicate that file is a Micromobility (bicycle and/or pedestrian) Station Record. This field is not case sensitive.
State FIPS (SFPIS) (Width 2) – Required
- Refer to state_county_city_FIPS_codes to obtain the State's FIPS code. The State FIPS code indicates in which State the station is located.
County FIPS (CFIPS) (Width 3) – Required
- The County FIPS code ranges from 1 to 3 digits.
- County FIPS codes for all U.S. counties are maintained by the U.S. Census Bureau and can be found online at state_county_city_FIPS_codes.
Reporting Agency Indicator (RAI) (Width 10) – Required
- The Reporting Agency Indicator field has a maximum of 10 alphanumeric characters (containing only letters and/or numbers) and identifies the agency reporting the data to TMAS.
- If a State transportation department (e.g., FL DOT) or a contracting entity (e.g., ABC Company) acting on behalf of a State transportation department submits the record, the field should be coded with the letter "S".
- If a Metropolitan Planning Organization (MPO), a Council of Government (COG), or a contracting entity (e.g., ABC Company) acting on behalf of the MPO or COG submits the data, the field should be coded with the abbreviation of the MPO or COG.
  
  Example 1: The Baltimore Regional Transportation Board (BRTB), would enter BRTB as their abbreviation code.
  
  Example 2: The Susquehanna Economic Development Association Council of Governments (SEDA-COG), would enter SEDA as their abbreviation code.
- If a county/city (or equivalent) reports the Station Record information, the field should be coded with the county's or city's FIPS code. This can be found online at state_county_city_FIPS_codes.
- Other entities submitting data but not covered in the above categories should use their entity abbreviation.
  
  Example 3: The University of North Carolina (UNC) Highway Safety Research Center (HSRC) could enter either UNC_HSRC or HSRC_UNC as their abbreviation code.
Station ID (SID) (Width 60) – Required
- The Station ID field has a maximum of 60 characters and is created by the reporting agency. It represents a unique identifier for a counting location and counting technology arrangement.
  A counting technology arrangement refers to the types of sensors or technologies used. A counting arrangement may encompass different sensors or technologies in order to capture different travelers.
  
  For example, a site has both infrared and loop sensors to count pedestrians and bicycles. If the final data to be submitted to TMAS combines pedestrian and bicycle data into a single file, this multi-sensor or technology arrangement at this site should have one station ID. However, if the data submitted to TMAS are two files with one for pedestrian and the other one for bicycle, then the site will have two unique Station IDs.
  
  The goal is to enable agencies to use their native Station IDs for TMAS reporting. When combined with data field #4 (Reporting Agency Indicator), the entered values will create a unique record within a State regardless of how many entities submit data to TMAS.
  
  Example 1: If a counting site has two different counting devices monitoring different travelers and generating different count datasets to report, then that would constitute two stations. Therefore, two station records with different Station IDs should be created.
- The Station ID must be alphanumeric (containing only letters and/or numbers). No other symbols such as a star *, exclamation mark !, dash –, hashtag #, parenthesis (), ampersand & or dots … can be used.
Latitude (LAT) (Width 11) – Required
- Latitude refers to the geolocation of the Micromobility counting site in decimal degree format.
- The latitude needs to be reported to 6 decimal places.
- The latitude field has a total of 11 allocated digits (columns) in length.
- If the latitude coordinate is less than 11 columns in length and a fixed-width column format is used, the entry should be right justified, and blank spaces entered in the most left columns to ensure the 11-column length.
- A site's latitude is based on the World Geodetic System 1984 (WGS84) defined and maintained by the U.S. National Geospatial Intelligence Agency. All U.S. satellite-based survey, navigation, and mapping systems are based on the WGS84.
- All U.S. locations except American Samoa are in the northern hemisphere with a positive latitude as XX.XXXXXX degree. For example, the U.S. Capital Visitor Center has a latitude of 38.889601 degrees. The latitude entry for this site should be coded as 38.889601. American Samoa has a latitude of - 14.271012 degrees. Its latitude entry should be coded as -14.271012.
Longitude (LONG) (Width 11) – Required
- Longitude refers to the geolocation of the Micromobility counting site in decimal degree format.
- The longitude needs to be reported to 6 decimal places.
- The longitude field has a total of 11 allocated digits (columns) in length.
- If the longitude coordinate is less than 11 columns in length and a fixed-width column format is used, the entry should be right justified, and blank spaces entered in the most left columns to ensure the 11-columnlength.
- A site's longitude is based on the World Geodetic System 1984 (WGS84) defined and maintained by the U.S. National Geospatial Intelligence Agency. All U.S. satellite-based survey, navigation, and mapping systems are based on the WGS84.
- All U.S. locations except Guam and the Northern Mariana Islands are in the western hemisphere with a negative longitude as -XXX.XXXXXX degrees. For example, the Golden Gate Bridge in San Francisco has a longitude of -122.478611 degrees. The longitude entry for this site should be coded as -122.478611. The U.S. Capital Visitor Center has a longitude of -77.009056 degrees. Its longitude entry should be coded as -77.009056.

Function Class and Area Type (FCAT) (Width 2) – Optional

This two-digit field identifies the Function Class (FC) and Area Type of a trail or roadway that the bicycle lane(s) and/or sidewalks are part of (Table 4-36). The first digit represents the FC and the second digit signifies the area type.
Bicycle lanes and sidewalks can be and are often part of public streets/roadways where motorized, non-motorized, and micro-powered e-device travel occurs.
When the bicycle travel lanes and/or sidewalks are part of a roadway, use one of the 7 FHWA Roadway Function Classes to code the road's class.
When bicycle travel lane(s) or other non-motorized travel lanes are not part of the roadway or public street (independent alignment), the bicycle lane(s) are referred to as trails or shared-use paths and code 8 should be used.
For scenarios that are not covered by codes 1 through 8, use code 9.
Area Type can be either urban or rural. The letter "U" is the code for an urban area and the letter "R" is the code for a rural area.

**Table 4-36. Function Class and Area Type Codes**
Code	Description
1U	Urban-Interstate
2U	Urban-Principal Arterial – Other Freeways and Expressways
3U	Urban-Principal Arterial – Other
4U	Urban-Minor Arterial
5U	Urban-Major Collector
6U	Urban-Minor Collector
7U	Urban-Local
8U	Urban-Trail or Shared-Use Path (walking, running and bicycling on an independent alignment)
9U	Urban-Other Facility Type
1R	Rural-Interstate
2R	Rural-Principal Arterial – Other Freeways and Expressways
3R	Rural-Principal Arterial – Other
4R	Rural-Minor Arterial
5R	Rural-Major Collector
6R	Rural-Minor Collector
7R	Rural-Local
8R	Rural-Trail or Shared-Use Path (walking, running and bicycling on an independent alignment)
9R	Rural-Other Facility Type

Type of Sensor (TS) (Width 1) – Optional

This field indicates the specific sensor technology used to conduct the count. Use one of the codes in Table 4-37.

**Table 4-37. Type of Sensor Codes**
Code	Description
1	Video Image with Manual Reduction at a later time
2	Active Infrared (emits an infrared beam to a receiver)
3	Pressure sensor/mat
H	Human Observation
I	Passive Infrared (captures radiation emitted by surrounding objects. e.g., infrared camera)
K	Laser/Lidar
L	Inductive Loop
M	Magnetometer
P	Piezoelectric
Q	Quartz Piezoelectric
R	Air Tubes
S	Sonic/Acoustic
T	Tape Switch
U	Ultrasonic
V	Video Image with Automated or Semi-automated Reduction
W	Microwave Radar
X	Radio Wave Radar
Z	Other Type Not Listed
9	Multi sensors (e.g., a location has both infrared and loop sensors to count ped and bicycle separately but report the ped and bicycle data in a single count data file. )

Primary Count Purpose (PCP) (Width 1) – Optional

The field indicates the primary purpose of the data collection. If the data serves multiple purposes, select the purpose considered the most important or the greatest impetus for establishing the data collection location (Table 4-38).

**Table 4-38. Primary Count Purpose Codes**
Code	Description
E	Enforcement
L	Facility design
O	Operations and facility management
P	Planning or statistic reporting
R	Research
S	Related to Safe Routes to School effort
T	Reason not mentioned above

Year Station Established (YEARE) (Width 4) – Optional
- This field is used to code the four-digit year the count station was established.
Year Station Discontinued (YEARD) (Width 4) – Optional
- This field is used to code the four-digit year the count station was discontinued.
- When a station is discontinued, it is recommended to state the reason (e.g., due to a facility being realigned, or a permanent counter being removed) in Field #15.

Posted Route Sign (PRS) (Width 2) – Optional

This field indicates the type of route based on the HPMS Field Manual. Use one of the codes below (Table 4-39).

**Table 4-39. Posted Route Sign Codes**
Code	Description
10	Bureau of Indian Affairs
11	Not Signed
12	Interstate
13	U.S.
14	State
15	Off-Interstate Business Marker
16	County
17	Township
18	Municipal
19	Parkway Marker or Forest Route Marker
20	U.S. Bicycle Route
21	State or Local Bicycle Route
22	None of the above

Posted Sign Route Number (PRSN) (Width 8) – Optional
- This field is used to record the route number appearing on the posted sign of the route identified in the previous field.
- If the route number is less than 8 digits, leading or trailing spaces are ignored.
- Leave this field blank if Field #13 (Posted Route Sign) is coded with a blank or 11.
Other Notes (ON) (Width 100) – Optional
- This field is used to record any special circumstances and may contain any printable character. It is limited to 100 characters.
- For example, if the station is used to count crosswalks of an intersection, it can be described here.

Micromobility Station Record Pipe-delimited Format State Example

The example below has all the information needed for the Station Record. It shows that the record is for Micromobility data (MSRI=L). The station is in Maryland (SFIPS=24) and within Montgomery County (CFIPS=31). The Maryland DOT is reporting the data (RAI=S). The monitoring station (Station ID SID=ABC123) has a latitude of 39.086437 degrees (LAT =39.086437) and longitude of -77.161263 degrees (LONG=-77.161263). The site is part of a local road in an urban area (FCAT=7U). The count at the station is taken by human observation (TS=H) for the primary purpose of planning (PCP=P). The station was established in 2022 (YEARE=2022) and no information is offered on whether it is discontinued or not (YEARD=blank). The facility is on County Route 220 (PRS=16 and PRSN=220) with a note stating "Jones Creek Path belongs to Montgomery County, Maryland Public Works Department for O&M. The path is about 3.1 miles long."

Header

MSRI|SFIPS|CFIPS|RAI|SID|LAT|LONG|FCAT|TS|PCP|YEARE|YEARD|PRS|PRSN|ON

Actual Data

L|24|31|S|ABC123|39.086437|-77.161263|7U|H|P|2022||16|220|Jones Creek Path belongs to Montgomery County, Maryland Public Works Department for O&M. The path is about 3.1 miles long.

4.9 MICROMOBILITY COUNT RECORD DATA FORMAT (FIXED WIDTH OR PIPE DELIMITED)

Two types of records are needed for submitting Micromobility data to FHWA's TMAS system.

Micromobility Station Record – Section 4.8
Micromobility Count Record – Section 4.9

The Micromobility Count Record is used to report the actual count data to FHWA. The Count Record provides data and other information related to the count, which can be used in conjunction with the Station Record for specific data analyses. To submit a Count Record to FHWA's TMAS, a corresponding Station Record must first be uploaded and approved by TMAS. If a Micromobility Station Record has not been uploaded into TMAS, then the Count Record will not be processed. A Count Record file is a text file often designated by the .txt file extension.

Below is an example Count Record file naming convention:

CountABC123.CMM

General Guidance

The Count Record consists of the data fields listed in Table 4-40. These data fields can be organized either by Pipe (|) Delimited format or Fixed-Width Column format. The Pipe (|) Delimited format is recommended due to its flexibility and easy to use nature.

It is highly recommended to use the Pipe (|) delimited format.
With this format, there is no need to keep track of entry column locations.

Regardless of the format that is used, the length of each data field cannot exceed the specified field length (column width). Information exceeding the allowed field length (column width) in the Pipe Delimited file will be truncated while information less than the allowed width will be accepted as provided.

When using the Fixed-Width Column format, any misalignment of the data field will lead to errors and the rejection or misinterpretation of the data.

**Table 4-40. Summary of the Micromobility Count Record Data Fields**
Field	Columns	Width	Description	Type	Importance
1	1	1	Micromobility Count Record Indicator (MCRI)	Alphanumeric	Required
2	2-3	2	State FIPS Code (SFIPS)	Integer	Required
3	4-13	10	Reporting Agency Indicator (RAI)	Alphanumeric	Required
4	14-73	60	Station ID (SID)	Alphanumeric	Required
5	74	1	Type of Count (TC)	Alphanumeric	Required
6	75	1	Helmet Usage (HU)	Alphanumeric	Optional
7	76	1	Age (AGE)	Alphanumeric	Optional
8	77-80	4	Year of Counts (YEAR)	Integer	Required
9	81-82	2	Month of Counts (MONTH)	Alphanumeric	Required
10	83-84	2	Day of Counts (DAY)	Alphanumeric	Required
11	85-88	4	Count Start Time (in military time) (CST)	Integer	Required
12	89-90	2	Count Interval (in minutes) (CI)	Integer	Required
13	91-94	4	Count Data Reporting Scheme (CDRS)	Alphanumeric	Required
14	95-99	5	Counts (COUNTS)	Integer	Required

Specific Data Fields Explanation

A Count Record allows Micromobility data items to be reported at a variety of time intervals. The following data items should be reported when gathering Micromobility counts. Each Count Record should correspond to an existing Station Record already uploaded in TMAS.

Micromobility Count Record Indicator (MCRI) (Width 1) – Required
- The letter "N" is always coded to indicate that the file is a Micromobility (bicycle and/or pedestrian) Count Record. This field is not case sensitive.
State FIPS (SFIPS) (Width 2) – Required
- Refer to state_county_city_FIPS_codes to obtain the State's FIPS code. The State FIPS code indicates in which State the station is located.
Reporting Agency Indicator (RAI) (Width 10) – Required
- The Reporting Agency Indicator field has a maximum of 10 alphanumeric characters (containing only letters and/or numbers) and identifies the agency reporting the data to TMAS.
- Enter the same Data Reporting Agency Indicator that was used in the corresponding Station Record.
Station ID (SID) (Width 60) – Required
- The Station ID field has a maximum of 60 characters and is created by the reporting agency. It represents a unique identifier for a counting location and counting device. The goal is to enable agencies to use their native Station IDs for TMAS reporting. When combined with data field #3 (Reporting Agency Indicator), the entered values will create a unique record within a State regardless of how many entities submit data to TMAS.
- Enter the same Station ID that was used in the corresponding Station Record.

Type of Count (TC) (Width 1) – Required

This field indicates the type of traveler being counted. Use one of the codes from Table 4-41.
If the count data has subclassifications, ensure all types of counts are included by using a record (row) for each type.
Example 1: Station 12345678AB counts pedestrians and bicycles separately. Count data for each count interval (per specific year, month, day, and time) should be provided in row 1 for pedestrians (code 1) and row 2 for bicyclists (code 2).

Example 2: Station 12345678CD counts pedestrians, electric bicycles, and nonelectric bicycles separately. Count data for each count interval (per specific year, month, day, and time) should be provided in three rows: the first row for pedestrians (code 1), the second row for electric bikes (code E), and the third row is for non-electric bikes (code N).

Example 3: Station 12345678EF counts all traffic together. Count data for each interval will have only one row with a Type of Count of 9.

**Table 4-41. Type of Count Codes**
Code	Description
1	Pedestrians (walking and running) without electric-assisted devices
4	Wheelchair (manual or electrical)
5	Pedestrians (walking, running) with electric-assisted devices (e.g., electric skates, electric skateboards, electric scooters, Segways, and hoverboards)
Y	Pedestrians (walking and running) total (the sum of codes 1 and 5)
N	Manual Bicycles
E	Electric Bicycles including electric minibikes (i.e., small electric motorcycles without pedals)
2	Bicycles total (manual and electric)
7	Bicycle and Pedestrians total (the sums of codes 1, 5, N, and E)
3	Equestrians only
6	All-terrain vehicles on a trail (e.g., snowmobile or some other ATV)
8	All Micromobility traffic (the sum of codes 1,4, 5, N, and E
9	All traffic using the facility (the sum of codes 1, 4, 5, N, E, 3 and 6)
0	Animals other than horses counted under Equestrians

Helmet Usage (HU) (Width 1) – Optional

The field indicates the traveler helmet usage. Use one of the codes from Table 4-42.

**Table 4-42. Helmet Usage Codes**
Code	Description
N	Helmet usage is not collected.
B	Helmet usage is collected - # of travelers not wearing a helmet
W	Helmet usage is collected - # of travelers wearing a helmet
X	Helmet usage is collected - # of travelers wearing a helmet cannot be ascertained.

Age (AGE) (Width 1) – Optional

This field indicates the age of the traveler. Use one of the codes from Table 4-43.

**Table 4-43. Age Codes**
Code	Description
N	Age is not collected (no age identification is attempted)
C	Age identification is attempted - cases with child (pre-teen) identified
A	Age identification is attempted - cases with adult (teen or older) identified
X	Age identification is attempted - cases when age can't be ascertained

Year of Counts (YEAR) (Width 4) – Required
- Code the four digits of the year in which the data was collected.
Month Of Counts (MONTH) (Width 2) – Required
- Code the two digits (leading zero Is not required) for the month in which the data was collected.
Day of Counts (DAY) (Width 2) – Required
- Code the two digits (leading zero Is not required) for the day in which the data was collected.
Count Start Time in Military Time (CST) (Width 4) – Required
- This is the starting counting time. For example, Station ABCD123456 starts to count for the day at 6:00 am.
- Record the local time in effect on the date of the count using the 24-hour military (e.g., 13:30 pm is corded as 1330) format except no zero should be used as a prefix for hours prior to 10:00 am (e.g., 6:00 am is recorded as 600 not 0600.)
- The count start time must be divisible by 5. Hourly records are expected to start on the hour. 15-minute records are expected to start at 0, 15, 30, or 45 minutes past the hour. For a 5-minute interval, the count must start at a time ending in either 0 or 5.
- Due to daylight savings time, it has been typical practice with motorized counts to "overwrite an hour of data" in the fall and have a "missing hour" in the spring. This practice is continued for the TMG Micromobility format.
- If a count session continues past midnight, a new record with a new date should commence with the first interval that starts after midnight.
Count Interval in Minutes (CI) (Width 2) – Required
- The TMG allows for 5-, 10-, 15-, 20-, 30-, or 60-minute intervals.
- Counts should be collected and reported for the shortest feasible intervals (shorter if automated equipment is used, longer if manual counts are conducted).

Count Data Reporting Scheme (CDRS) (Width 4) – Required

This field identifies how the actual count data are reported to TMAS.
Report non-intersection-related count data by following codes in Table 4-44.
Non-intersection-related count data can be reported either by individual travel direction or by combining both travel directions.

**Table 4-44. Count Data Reporting Scheme for Non-Intersection Traveled Way Scenarios**
Code	Description
DDCC	Dual directional (combining counts) count reporting (e.g., combining north and south counts into a single combined count to report).
SDCN	Single directional count reporting for travel direction 1. Travel directions for direction 1 includes northwest, north, or northeast.
SDCS	Single directional count reporting for direction 2. Travel directions for direction 2 includes southwest, south, or southeast.
SDCE	Single directional count reporting for the east travel direction.
SDCW	Single directional count reporting for the west travel direction.

Report intersection-related count data by following codes in Table 4-45 and the further protocols explained below.

-   A typical intersection may have 4 crosswalks where a T intersection has 3 crosswalks. A crosswalk most likely allows dual direction travel.

-   When reporting intersection crosswalk counts, report the combined direction count for each crosswalk.

-   Crosswalk counts for a typical four-way or a "T" intersection should be coded as ICW1, ICW2, ICW3, and/or ICW4.

-   For intersections where there are more than 4 legs (5 or more crosswalks), codes should be continued as ICW5, ICW6 … as needed.

-   The crosswalk located in the northwest quadrant of a typical intersection is labeled as Intersection Crosswalk 1 (ICW1). Continue to identify the rest of the crosswalks sequentially in a clockwise direction.

-   When there is not an intersection leg located in the northwest quadrant of an intersection, the crosswalk located in the north direction shall be identified as Intersection Crosswalk number 1 (ICW1). Continue to identify the rest of the crosswalks sequentially in a clockwise direction.

-   When there are no intersection legs located in the northwest quadrant or the direct north direction, the crosswalk located with the leg in the northeast quadrant is labeled as Intersection Crosswalk number 1 (ICW1). Continue to identify the rest of the crosswalks sequentially in a clockwise direction.

-   When there are no intersections legs located in the northwest quadrant, the direct north direction, or the northeast quadrant, the crosswalk located with the leg in the east direction is labeled as Intersection Crosswalk number 1 (ICW1). Continue to identify the rest of the crosswalks sequentially in a clockwise direction.

-   See further illustrations with Figures 4.3, 4.4, and 4.5.

**Table 4-45. Count Data Reporting Scheme for Intersection Crosswalk Counting Scenarios**
Code	Description
ICW1	Combined directional counts for crosswalk # 1
ICW2	Combined directional counts for crosswalk # 2
ICW3	Combined directional counts for crosswalk # 3
ICW4	Combined directional counts for crosswalk # 4
ICWn	Combined directional counts for crosswalk # n

Source: Federal Highway Administration.

Figure 4-3. A Regular Intersection Crosswalk Numbering Illustration

Source: Federal Highway Administration.

Figure 4-4. A "T" Intersection Crosswalk Numbering Illustration 1

Source: Federal Highway Administration.

Figure 4-5. A "T" Intersection Crosswalk Numbering Illustration 2

Counts (COUNTS) (Width 5) – Required
- This field is used to record the actual count data observed during each interval.
- For any count intervals when the counter is not operating or the count data are not available, there is no need to include any records (rows) in the data file to indicate data are missing.
- If a counter is operating but no subjects were observed, 0 (zero), should be entered.

Micromobility Count Record Pipe Delimited Format Examples

Example 1

The Maryland Department of Transportation (Reporting Agency Indicator RAI=S and SFIPS=24) reports Micromobility counts (Micromobility Count Reporting Indicator MCRI=N) for a monitoring site (SID=abc123456789) counting pedestrian travel (TC=1) without identifying the traveler's helmet usage (HU=blank) or age (AGE =blank) for May 15, 2024 (YEAR=2024, MONTH=5, DAY=15) with a count start time at 8:00 am (CST=800) and an interval time of 60 minutes (CI=60). Counts are dual directional combined counts (CDRS=DDCC).

Header

MCRI|SFIPS|RAI|SID|TC|HU|Age|Year|Month|Day|CST|CI|CDRS|Counts

Actual Data

N|24|S|abc123456789|1|||2024|5|15|800|60|DDCC|200
N|24|S|abc123456789|1|||2024|5|15|900|60|DDCC|250
N|24|S|abc123456789|1|||2024|5|15|1000|60|DDCC|150
N|24|S|abc123456789|1|||2024|5|15|1100|60|DDCC|200
N|24|S|abc123456789|1|||2024|5|15|1200|60|DDCC|90
N|24|S|abc123456789|1|||2024|5|15|1300|60|DDCC|70
N|24|S|abc123456789|1|||2024|5|15|1400|60|DDCC|20
N|24|S|abc123456789|1|||2024|5|15|1500|60|DDCC|70
N|24|S|abc123456789|1|||2024|5|15|1600|60|DDCC|150
N|24|S|abc123456789|1|||2024|5|15|1700|60|DDCC|200
N|24|S|abc123456789|1|||2024|5|15|1800|60|DDCC|100
N|24|S|abc123456789|1|||2024|5|15|1900|60|DDCC|50
N|24|S|abc123456789|1|||2024|5|15|2000|60|DDCC|40
N|24|S|abc123456789|1|||2024|5|15|2100|60|DDCC|0
N|24|S|abc123456789|1|||2024|5|15|2200|60|DDCC|5
N|24|S|abc123456789|1|||2024|5|15|2300|60|DDCC|1
N|24|S|abc123456789|1|||2024|5|16|0|60|DDCC|1

Example 2

The Maryland Department of Transportation (Reporting Agency Indicator RAI=S and SFIPS=24) reports Micromobility counts (Micromobility Count Reporting Indicator MCRI=N) for a monitoring site (SID=abc123456789) counting pedestrians and bicyclist separately (TC=1 and TC=2) without identifying the traveler's helmet usage (HU=blank) or age (AGE =blank) for May 15, 2024 (YEAR=2024, MONTH=5, DAY=15) with count start time at 8:00 am (CST=800) and an interval time of 60 minutes (CI=60). Counts are dual directional combined counts (CDRS=DDCC).

Header

MCRI|SFIPS|RAI|SID|TC|HU|Age|Year|Month|Day|CST|CI|CDRS|Counts

Actual Data

N|24|S|abc123456789|1|||2024|5|15|800|60|DDCC|200
N|24|S|abc123456789|2|||2024|5|15|800|60|DDCC|50
N|24|S|abc123456789|1|||2024|5|15|900|60|DDCC|250
N|24|S|abc123456789|2|||2024|5|15|900|60|DDCC|90
N|24|S|abc123456789|1|||2024|5|15|1000|60|DDCC|150
N|24|S|abc123456789|2|||2024|5|15|1000|60|DDCC|60
N|24|S|abc123456789|1|||2024|5|15|1100|60|DDCC|200
N|24|S|abc123456789|2|||2024|5|15|1100|60|DDCC|80
N|24|S|abc123456789|1|||2024|5|15|1200|60|DDCC|90
N|24|S|abc123456789|2|||2024|5|15|1200|60|DDCC|80
N|24|S|abc123456789|1|||2024|5|15|1300|60|DDCC|70
N|24|S|abc123456789|2|||2024|5|15|1300|60|DDCC|50
N|24|S|abc123456789|1|||2024|5|15|1400|60|DDCC|20
N|24|S|abc123456789|2|||2024|5|15|1400|60|DDCC|10
N|24|S|abc123456789|1|||2024|5|15|1500|60|DDCC|70
N|24|S|abc123456789|2|||2024|5|15|1500|60|DDCC|50
N|24|S|abc123456789|1|||2024|5|15|1600|60|DDCC|150
N|24|S|abc123456789|2|||2024|5|15|1600|60|DDCC|60

Example 3

The Maryland Department of Transportation (Reporting Agency Indicator RAI=S and SFIPS=24) reports Micromobility counts (Micromobility Count Reporting Indicator MCRI=N) for a monitoring site (SID=abc123456789) counting only bicyclist (TC=2) with the capability of identifying the traveler's helmet usage (HU=B, W, or X) and age (AGE=C, A, or X ) for May 15, 2024 (YEAR=2024, MONTH=5, DAY=15) with count start time at 8:00 am (CST=800) and an interval time of 60 minutes (CI=60). Counts are dual directional combined counts (CDRS=DDCC).

Header

MCRI|SFIPS|RAI|SID|TC|HU|Age|Year|Month|Day|CST|CI|CDRS|Counts

Actual Data

N|24|S|abc123456789|2|B|C|2024|5|15|800|60|DDCC|200
N|24|S|abc123456789|2|B|A|2024|5|15|800|60|DDCC|11
N|24|S|abc123456789|2|B|X|2024|5|15|800|60|DDCC|5
N|24|S|abc123456789|2|W|C|2024|5|15|800|60|DDCC|201
N|24|S|abc123456789|2|W|A|2024|5|15|800|60|DDCC|8
N|24|S|abc123456789|2|W|X|2024|5|15|800|60|DDCC|4
N|24|S|abc123456789|2|X|C|2024|5|15|800|60|DDCC|12
N|24|S|abc123456789|2|X|A|2024|5|15|800|60|DDCC|1
N|24|S|abc123456789|2|X|X|2024|5|15|800|60|DDCC|1
N|24|S|abc123456789|2|B|C|2024|5|15|900|60|DDCC|250
N|24|S|abc123456789|2|B|A|2024|5|15|900|60|DDCC|36
N|24|S|abc123456789|2|B|X|2024|5|15|900|60|DDCC|12
N|24|S|abc123456789|2|W|C|2024|5|15|900|60|DDCC|267
N|24|S|abc123456789|2|W|A|2024|5|15|900|60|DDCC|66
N|24|S|abc123456789|2|W|X|2024|5|15|900|60|DDCC|21
N|24|S|abc123456789|2|X|C|2024|5|15|900|60|DDCC|6
N|24|S|abc123456789|2|X|A|2024|5|15|900|60|DDCC|3
N|24|S|abc123456789|2|X|X|2024|5|15|900|60|DDCC|1
N|24|S|abc123456789|2|B|C|2024|5|15|1000|60|DDCC|198
N|24|S|abc123456789|2|B|A|2024|5|15|1000|60|DDCC|35
N|24|S|abc123456789|2|B|X|2024|5|15|1000|60|DDCC|21

N|24|S|abc123456789|2|W|C|2024|5|15|1000|60|DDCC|10
N|24|S|abc123456789|2|W|A|2024|5|15|1000|60|DDCC|1
N|24|S|abc123456789|2|W|X|2024|5|15|1000|60|DDCC|2
N|24|S|abc123456789|2|X|C|2024|5|15|1000|60|DDCC|12
N|24|S|abc123456789|2|X|A|2024|5|15|1000|60|DDCC|11
N|24|S|abc123456789|2|X|X|2024|5|15|1000|60|DDCC|3

Return to top

Page last modified on May 18, 2026