Skip to contentUnited States Department of Transportation - Federal Highway AdministrationSearch FHWAFeedback

Pavements

Profile Feedback Report Summaries

For additional information e-mail: ltppinfo@fhwa.dot.gov.

Report Number: BRE-50
Date Submitted: 7/12/1999

Subject/IMS Table: Out of range transverse profile for section 317005.
Resolved: Yes
Last Updated: 3/20/2001

LTPP Analysis/Operations Situation: Transverse profile for test section 317005 in Nebraska, dated 4/21/1995 at station 121.0 m, appears to be errant. The profile was taken by Dipstick and has a single jump between two consecutive points of over 150 mm. This is beyond the capability of the Dipstick. The Regional Office should check the validity of this data.

Resolution of Problem/Situation: The North Central Regional Office has corrected the elevation data in the MON_T_PROFILE_PROFILE table, as directed.


Report Number: BRE-51
Date Submitted: 7/14/1999

Subject/IMS Table: Orphan Records in table MON_T_PROF_X_Y.
Resolved: Yes
Last Updated: 7/19/2001

LTPP Analysis/Operations Situation: Orphan records were found for some transverse profile surveys in table MON_T_PROF_X_Y. It is possible that the record in MON_T_PROF_MASTER has not yet made it to level E. The Regional Offices should review all the orphan records and take appropriate action.

Resolution of Problem/Situation: The Regional Offices have reviewed the orphan records and corrected the data.


Report Number: BRE-55
Date Submitted: 9/21/1999

Subject/IMS Table: Longitudinal profile data collected prior to construction on section 100102
Resolved: Yes
Last Updated: 8/23/2004

LTPP Analysis/Operations Situation: One set of longitudinal profile tests is dated February 24, 1996 for section 100102. The SPS_ID table reports that construction was not completed on this project until May 1, 1996. The region should review their data to determine which (if either) of these dates is incorrect.

Resolution of Problem/Situation: Resolved as recommended.


Report Number: BRE-71
Date Submitted: 12/6/1999

Subject/IMS Table: Potential profilometer problem on section 231026.
Resolved: Yes
Last Updated: 12/15/1999

LTPP Analysis/Operations Situation: The International Roughness Index (IRI) data reported for early 1997 on section 231026 are out of line with the rest of the data. The data should be examined to determine if there was a calibration problem with the profilometer or some other system malfunction.

Resolution of Problem/Situation: Section 231026 is a seasonal site. Profiles were taken in January and February of 1997. In the Northeast, frost penetrates the pavement and causes the pavement to react producing different values. This phenomenon has been documented over the years and is unavoidable when collecting profile data in cold climates.


Report Number: CAR-7
Date Submitted: 5/20/1998

Subject/IMS Table: Recommended improvements in profile data collection and processing procedures.
Resolved: Yes
Last Updated: 8/23/2004

LTPP Analysis/Operations Situation: Analysis of the profile data has yielded a number of recommendations as to possible improvements in LTPP profile data collection and processing procedures. These recommendations are in an attachment to the feedback report and Chapter 8 of report FHWA-RD-00-113 "LTPP Profile Variability". Consider implementation of the proposed changes.

Resolution of Problem/Situation: The recommendations will be addressed in an addendum to the profile manual.


Report Number: CTL-1
Date Submitted: 6/14/2005

Subject/IMS Table: Recommendations for improving quality of 25-mm data collected in the LTPP program.
Resolved: No
Last Updated: 7/18/2005

LTPP Analysis/Operations Situation:

Resolution of Problem/Situation:


Report Number: CTL-2
Date Submitted: 6/14/2005

Subject/IMS Table: 25-mm Profile data collected by the Western regional office K.J. Law T-6600 Profiler.
Resolved: No
Last Updated: 7/18/2005

LTPP Analysis/Operations Situation:

Resolution of Problem/Situation:


Report Number: ERES-BW-9
Date Submitted: 8/31/1997

Subject/IMS Table: Replacing sequence numbers in profile data with coordinates.
Resolved: Yes
Last Updated: 2/06/2003

LTPP Analysis/Operations Situation: Recently, the "old" profile data were converted into Standard International (SI) metric units. Now there is a single profile data table containing the sequence number and the elevation data in mm units. However, there is a problematic incompatibility in the new SI metric data table. The "old" data now has 1,001 sequence numbers and the new data has 1,017 sequence numbers. This creates a major nuisance when time series profile plots are compared for quality checks or for any analysis related reasons. The recommendation is to eliminate the sequence number and replace it with the actual spacing data. With this change, data plots can be easily prepared to compare the profiles from different years of data.

Resolution of Problem/Situation: Recommended changes are not feasible.


Report Number: ERES-BW-54
Date Submitted: 12/7/1998

Subject/IMS Table: Correct deficiencies in the regional information management system (RIMS) or IMS databases to make IRI data releasable in table EXPERIMENT_SECTION.
Resolved: Yes
Last Updated: 3/2/2001

LTPP Analysis/Operations Situation: There is a lack of releasable IRI data for all portland cement concrete (PCC) rehabilitated sections (SPS-6, GPS-7, and GPS-9). No IRI data are currently releasable for the following PCC rehabilitated sections: SPS-6 data for 29 (MO), 40 (OK), 42 (PA), 46 (SD), and 47 (TN), and also GPS sections 297054, 297073, 294069, 295393, 295483, 407024, 404155, 421610, 427025, 427037, 421613, 421614, 421617, 421691, 421627, 429027, and 467049. No data are available from the IMS for IRI, FWD, distress (manual and PASCO), faulting, and traffic. Some data are currently at level E within these individual tables, but is not releasable in other tables such as EXPERIMENT_SECTION.

Resolution of Problem/Situation: Most of this problem was resolved with the data resolution effort and the EXPERIMENT_SECTION quality controls (QC) in the early part of 1999. The North Central Regional Office has reviewed and updated the EXPERIMENT_SECTION and TST_L05* data in the IMS for the sections noted in this report. All of this data are now available for public release. The construction data for the new SPS-6 built in Missouri in 1998 remains outstanding, but that data should be available and in the RIMS system by 5/1/2001.


Report Number: ERES-BW-124
Date Submitted: 2/07/2002

Subject/IMS Table: Inconsistent time series of rutting data in tables MON_T_PROF_INDEX_POINT and MON_T_PROF_INDEX_SECTION for SPS-8 AC sections 34-0801, 34-0802, 36-0801, and 36-0802
Resolved: Yes
Last Updated: 3/18/2002

LTPP Analysis/Operations Situation: While reviewing the Level E data for SPS-8 asphalt concrete (AC) sections in the MON_T_PROF_INDEX_POINT and MON_T_PROF_INDEX_SECTION tables, using Information Management System (IMS) release (11.5/NT 3.0) received on June 8, 2001, it was found that there is big variability in the data for following sections: 34-0801, 34-0802, 36-0801, and 36-0802 and that mean rut depths abruptly increase or decrease with time.

Resolution of Problem/Situation: The North Atlantic Regional Support Contractor has reviewed the Dipstick data for section 360801 surveyed on September 15, 1998 and has discovered that the data in the IMS was erroneous. This data has been deleted from the IMS. The Dipstick data has been reprocessed and uploaded into the IMS with the correct values. This data will be available in the next IMS upload June 2002.


Report Number: ERES-BW-125
Date Submitted: 2/07/2002

Subject/IMS Table: Inconsistent time series of roughness data in table MON_PROFILE_MASTER for SPS-8 AC section 36-0801
Resolved: Yes
Last Updated: 3/18/2002

LTPP Analysis/Operations Situation: While reviewing Level E data for SPS-8 asphalt concrete (AC) sections in the MON_PROFILE_MASTER table, using Information Management System (IMS) release (11.5/NT 3.0), it was found that there is big variability in the roughness data for section 36-0801. Specifically, the average International Roughness Index (IRI) values for longitudinal profile surveys performed on 1/12/1996 and 3/12/1996 are much higher than the IRI values for other surveys.

Resolution of Problem/Situation: This is a Seasonal Monitoring Program (SMP) site. We investigated the temperatures during the testing times and found that prior to arriving on site in January, the temperatures were quite cold for a number of days (-10° C to -15°C). Again in March the temperatures were in the -10°C to -15°C range for the days prior to the test. The water table was very high during this period and the section contains active sand. This section is also adjacent to Lake Ontario. The only conclusion that we can derive with this information is that the cold temperatures in combination with the high water level and active sand caused the IRI's to be higher than normal.


Report Number: ERES-BW-126
Date Submitted: 2/07/2002

Subject/IMS Table: Records for in transverse profile tables for SPS-8 PCC sections
Resolved: Yes
Last Updated: 6/05/2002

LTPP Analysis/Operations Situation: While reviewing the Level E data for SPS-8 sections in the MON_T_PROF_DEV_CONFIG, MON_T_PROF_INDEX_SECTION, MON_T_PROF_INDEX_POINT, MON_T_PROF_MASTER, and MON_T_PROF_PROFILE tables, using Information Management System (IMS) release (11.5/NT 3.0) received on June 8, 2001, it was found that for portland cement concrete (PCC) sections 08-0811, 08-0812, 39-0809, and 39-0810 data exist in these tables (at level E), although they should have data only for asphalt concrete (AC) sections.

Resolution of Problem/Situation: From the start (1989) of the LTPP program, we collected transverse profile data on all sections using the PASCO/CGH device through round five (1996). We did this to make the measurement sequence in the field the same for all sections. Therefore, we should not delete transverse profile data on PCC sections even though this information is no longer collected.


Report Number: LW-63
Date Submitted: 3/15/2006

Subject/IMS Table: Erroneous or mssing values in MON_PROFILE_MASTER.
Resolved: Yes
Last Updated: 6/15/2006

LTPP Analysis/Operations Situation: The attached 5 records do not have: OPERATOR_COMMENT, RCO_COMMENT, PROFILE_MANUFACTURER, PROFILE_MODEL_NUMBER. The missing values need to be entered and it seems that the PROFILE_MANUFACTURER and PROFILE_MODEL_NUMBER should be "K.J. LAW ENG." and "T6600". The attached 40 records have an erroneous profile model number.  The K.J. Law unit is entered as "DNC69" when it seems that they all should be the K. J. LAW, "DNC690".

Resolution of Problem/Situation: The Regional offices have reviewed the records listed in this Data Analysis and Operations Feedback Report.  We have determined that the correct PROFILE_MODEL_NUMBER should be ‘T6600’.  Corrections have been completed to the IMS database.


Report Number: NC-1
Date Submitted: 6/18/1998

Subject/IMS Table: Inconsistent profile data from year-to-year, possibly due to unrecorded maintenance, rehabilitation, or errors in subsectioning.
Resolved: Yes
Last Updated: 12/7/1998

LTPP Analysis/Operations Situation: Review of GPS profiles in the LTPP database indicates that rehabilitation and maintenance for several test sections may not have been recorded. In addition, a few profiles may have been tested or subsectioned in the wrong location. Summary tables and profile plots of sections were provided for each region where visual profile review indicates that further regional review is necessary.

Resolution of Problem/Situation: Data has been reviewed and corrected where necessary. Erroneous data has been removed from the database.


Report Number: NC-2
Date Submitted: 8/14/1998

Subject/IMS Table: GPS Profiles affected by lost lock.
Resolved: Yes
Last Updated: 1/21/1999

LTPP Analysis/Operations Situation: Review of GPS profiles in the LTPP database indicates that equipment-related spikes remain in some profiles of the database. Several of these spikes were logically deleted during initial review by the Regional Offices. Many others were not identified using the available QC methods and tools.

Resolution of Problem/Situation: The Data Analysis Technical Support (DATS) team reprocessed these data files, after eliminating the equipment-related spikes. This report serves as a record of the work that was done to improve the quality of the LTPP profile database.


Report Number: NC-3
Date Submitted: 8/14/1998

Subject/IMS Table: GPS profile data sets exhibiting lost lock or other equipment related distortion.
Resolved: Yes
Last Updated: 1/21/1999

LTPP Analysis/Operations Situation: Review of GPS profiles in the LTPP database indicates that lost lock (97 visits) and other equipment-related profile distortion (104 visits) remain in the database profiles. Some of this distortion was noted in field and regional office comments in the MON-PROFILE_MASTER file, but the affected data still remain in the database at level E.

Resolution of Problem/Situation: All profile runs in which lost lock and equipment-related chatter had been noted were reduced to level D or less. Comments or were attached to these files to indicate the presence of equipment-related profile distortions.


Report Number: NC-4
Date Submitted: 9/28/1998

Subject/IMS Table: SPS profile data sets exhibiting spikes not deleted by the Regional Offices.
Resolved: Yes
Last Updated: 1/21/1999

LTPP Analysis/Operations Situation: Review of SPS profiles in the LTPP database indicates that equipment-related spikes remain in some profiles of the database. Several of these spikes were logically deleted during initial review by the Regional Offices. Many others were not identified using the available QC methods and tools.

Resolution of Problem/Situation: The DATS team reprocessed these data files, after eliminating the equipment-related spikes. This report serves as a record of the work done to improve the quality of the LTPP profile database.


Report Number: NC-5
Date Submitted: 9/28/1998

Subject/IMS Table: SPS profile data sets exhibiting lost lock or other equipment related distortion.
Resolved: Yes
Last Updated: 1/21/1999

LTPP Analysis/Operations Situation: Review of SPS profiles in the LTPP database indicates that lost lock and other equipment-related profile distortion remain in the database profiles. Some of this distortion was noted in field and Regional Office comments in the MON-PROFILE_MASTER file, but the affected data still remain in the database at level E.

Resolution of Problem/Situation: All profile runs in which lost lock and equipment-related chatter had been noted were reduced to level D or less. Comments or were attached to these files to indicate the presence of equipment-related profile distortions.


Report Number: NC-7
Date Submitted: 12/23/1998

Subject/IMS Table: Profiler Filter Wavelength Change.
Resolved: Yes
Last Updated: 2/2/1999

LTPP Analysis/Operations Situation: High pass filtering for the DNC 690 was set at 91 m; for the T-6600 profiler it is set at 100 m. Review of overlaid profiles collected at the same site using both sets of equipment indicates that some of the differences in profile are possible the result of this difference in high-pass filter level.

Resolution of Problem/Situation: No action to be taken on this feedback report.


Report Number: NC-8
Date Submitted: 1/18/2000

Subject/IMS Table: Shifted starts, lost lock, saturation spikes in North Atlantic Region profile data.
Resolved: Yes
Last Updated: 10/4/2000

LTPP Analysis/Operations Situation: Review of the North Atlantic Region longitudinal profile data that was in the IMS database prior to September 1999 indicates that some profiles are shifted (28 runs), contain saturation spikes (8 runs), exhibit lost lock (80 runs), are located incorrectly (15 runs), and have unreported maintenance/rehabilitation (15 sections) that may require deletion, reprocessing, or updating.

Resolution of Problem/Situation: Profile data in question has been reprocessed or deleted from the database as necessary.


Report Number: NC-9
Date Submitted: 1/18/2000

Subject/IMS Table: Shifted starts, lost lock, saturation spikes in North Central Region profile data.
Resolved: Yes
Last Updated: 10/23/2000

LTPP Analysis/Operations Situation: Review of the North Central Region longitudinal profile data that was in the IMS database prior to September 1999 indicates that some profiles are shifted (42 runs), contain saturation spikes (72 runs), exhibit lost lock (1 run), are incorrectly located (68 runs), and have unreported maintenance/rehabilitation (61 sections) that may require deletion, reprocessing, or updating.

Resolution of Problem/Situation: Profile data in question has been reprocessed or deleted from the database as necessary.


Report Number: NC-10
Date Submitted: 1/18/2000

Subject/IMS Table: Shifted starts, lost lock, saturation spikes in the Southern Region profile data.
Resolved: Yes
Last Updated: 1/8/2001

LTPP Analysis/Operations Situation: Review of the longitudinal profile data in the IMS for the Southern Region before September 1999 indicates that some profiles are shifted (229 runs), contain saturation spikes (279 runs), exhibit lost lock (17 runs), are incorrectly located (40 runs), and have unreported maintenance/rehabilitation (30 sections) that may require deletion, reprocessing, or updating.

Resolution of Problem/Situation: Profile data in question has been reprocessed or deleted from the database as necessary.


Report Number: NC-11
Date Submitted: 1/18/2000

Subject/IMS Table: Shifted starts, lost lock, saturation spikes in the Western Region profile data.
Resolved: Yes
Last Updated: 9/8/2000

LTPP Analysis/Operations Situation: Review of the longitudinal profile data in the IMS for Western Region before September 1999 indicates that some profiles are shifted (1,863 runs), contain saturation spikes (70 runs), exhibit lost lock (6 runs), are incorrectly located (5 runs), and have unreported maintenance/rehabilitation (25 sections) that may require deletion, reprocessing, or updating.

Resolution of Problem/Situation: Profile data in question has been reprocessed or deleted from the database as necessary.


Report Number: SME-1
Date Submitted: 6/25/1996

Subject/IMS Table: Irrational trends in profile data IRI values.
Resolved: Yes
Last Updated: 8/23/2004

LTPP Analysis/Operations Situation: It has been found that irrational trends in IRI with time in the North Central Region were in some cases attributable to either (1) saturation spikes in the data (often caused by the white stripe at the beginning of a test section); (2) use of incorrect section boundaries in the processing of data for multiple test sections at a single site. Similar irrational trends exist in data for other regions, but the causes have not been investigated.

Resolution of Problem/Situation: The data has been reviewed by the Regional Offices and corrections or deletions made where necessary.


Report Number: TSSC-1
Date Submitted: 6/9/1999

Subject/IMS Table: Data collected by T6600 profilers: Missing vehicle identification (VIN) number in the Software Version field in the MON_PROFILE_MASTER for some records.
Resolved: Yes
Last Updated: 12/10/1999

LTPP Analysis/Operations Situation: The field Software Version in the MON_PROFILE_MASTER table contains the K.J. Law software version used to collect data as well as the vehicle identification number (VIN) of the profiler that collected the data. The VIN has to be entered into the parameter screen in PROQUAL. When profile data are processed with PROQUAL to create an IMS upload file, the VIN entered into PROQUAL is written to the IMS upload file. There are many records in the IMS that do not have the VIN because this parameter has not been entered into PROQUAL.

Resolution of Problem/Situation: The data has been reviewed by the Regional Offices and corrections made.


Report Number: TSSC-2
Date Submitted: 6/9/1999

Subject/IMS Table: Data collected by T6600 profilers: Non-standard entries used for the field Lane Measured in MON_PROFILE_MASTER table.
Resolved: Yes
Last Updated: 12/10/1999

LTPP Analysis/Operations Situation: The field Lane Measured in the MON_PROFILE_MASTER table denotes the lane on which associated data were collected. This entry is made into the profiler data collection software prior to profile data collection. The LTPP Profile Manual specifies that this field should be "inside" or "outside". Operators are entering descriptions other than those specified in the LTPP Profile Manual. Some of the none standard descriptors used include: OSL, 1, 2, Lane 1, LN1 or no entry.

Resolution of Problem/Situation: The data has been reviewed by the Regional Offices and corrections made. The Regional Offices have been instructed to strictly follow proscribed procedures when making entries into the profiler data collection software prior to profile data collection.


Report Number: TSSC-3
Date Submitted: 6/9/1999

Subject/IMS Table: Data collected by T6600 profiler: Non-standard entries entered in field Surface Condition in the MON_PROFILE_MASTER table.
Resolved: Yes
Last Updated: 6/13/2000

LTPP Analysis/Operations Situation: The description for surface condition of the test section is entered into the profile data collection software by the profiler operator. The LTPP Profile Manual specifies the following valid entries for this field: V. Good, Good, Fair, and Poor. Guidelines on how these conditions are assigned are provided in the LTPP Profile Manual. Operators are using descriptions other than those specified in the LTPP Profile Manual or are leaving the field blank. Some of the non-standard entries include: New, OK, Dry/Medium etc.

Resolution of Problem/Situation: The data has been reviewed by the Regional Offices and corrections made.


Report Number: TSSC-4
Date Submitted: 6/9/1999

Subject/IMS Table: Data collected by T6600 profilers: Unreasonable high temperature values in the Temperature field of MON_PROFILE_MASTER table.
Resolved: Yes
Last Updated: 12/10/1999

LTPP Analysis/Operations Situation: The operator enters the air temperature into the profile data collection program prior to collecting profile data. Some of the entries in this field exceed reasonable air temperatures. There are cases where the air temperature is between 55 °C to70 °C.

Resolution of Problem/Situation: The data has been reviewed by the Regional Offices and corrections made.


Report Number: TSSC-5
Date Submitted: 6/9/1999

Subject/IMS Table: Data collected by T6600 profilers: Non-standard description in field the Cloud Conditions in MON_PROFILE_MASTER table of IMS for some records.
Resolved: Yes
Last Updated: 12/10/1999

LTPP Analysis/Operations Situation: This entry is input into the profile data collection software by the profiler operator. The LTPP Profile Manual requires that one of the following descriptions be used: Clear, Cloudy, P. Cloudy. These standard descriptions were specified in order to ensure uniformity amongst the regions. Profiler operators are entering non-standard entries into this field, including: CL, Dark, Hazy, Overcast, Sunny, Partly Clo (last characters cut-off due to limit of field width), M. Cloudy.

Resolution of Problem/Situation: The data has been reviewed by the Regional Offices and corrections made.


Report Number: TSSC-6
Date Submitted: 6/9/1999

Subject/IMS Table: Data collected by T6600 profilers: The Stop Method field in the MON_PROFILE_MASTER table is different from Distance from some records.
Resolved: Yes
Last Updated: 12/10/1999

LTPP Analysis/Operations Situation: The field Stop Method indicates the method that was used to terminate profile data collection. As specified in Section 2.3.5.5 of the LTPP Profile Manual, the Stop Method should always be the "distance" for data collected by the profilers. There are records in the database that do not have distance as the specified stop method. Some of the records have "pendant" as the Stop Method, while others have "photocell" as the Stop Method.

Resolution of Problem/Situation: The data has been reviewed by the Regional Offices and it was decided not to remove data with "photocell" as the Stop Method as this procedure was used in the past.


Report Number: TSSC-7
Date Submitted: 6/9/1999

Subject/IMS Table: Data collected by T6600 profilers: The Stop Distance in the MON_PROFILE_MASTER table is zero for some entries.
Resolved: Yes
Last Updated: 12/10/1999

LTPP Analysis/Operations Situation: The field Stop Distance denotes the station at which data collection was terminated at a test section. A value close to 152.5 for this field indicates that this section was profiled as a separate section. Higher values indicates this section was sub-sectioned. There are several records where the Stop Distance is zero. It is unclear how a value of zero can be present in this field. The Western Region has the most cases where this phenomenon was noted.

Resolution of Problem/Situation: The data has been reviewed by the Regional Offices and corrections made.


Report Number: TSSC-8
Date Submitted: 6/9/1999

Subject/IMS Table: Data collected by T6600 profilers: Regional Office Code.
Resolved: Yes
Last Updated: 6/13/2000

LTPP Analysis/Operations Situation: The Regional Office Code is assigned in the office after review of the profile data. Guidelines for assigning the Regional Office Code are found in Directive P-6 dated 4/10/1995. Each Regional Office appears to be using a method that is specific to their region when assigning this code. The data in the IMS indicate that only the Southern Regional Office appears to be following the guidelines specified in Directive P-6.

Resolution of Problem/Situation: The data has been reviewed by the Regional Offices and corrections made.


Report Number: TSSC-9
Date Submitted: 6/9/1999

Subject/IMS Table: Data collected by T6600 profilers: Some records in the Profiler Manufacturer field of MON_PROFILE_MASTER table in IMS contains blanks and incorrect entries.
Resolved: Yes
Last Updated: 12/10/1999

LTPP Analysis/Operations Situation: Section 2.2.5.2 of the LTPP Profile Manual specifies that in the parameter settings screen of PROQUAL, the profiler model and manufacturer should be entered as T6600/K.J. LAW ENG. There are records in the IMS that have this field as blank or incorrect (profiler manufacturer has been entered as T6600). There are also cases where the profiler manufacturer has been entered as K.J. Law, KJLAW, K.J. LAW ENGRG, K.J. LAW, LAW ENG, etc.

Resolution of Problem/Situation: The data has been reviewed by the Regional Offices and corrections made.


Report Number: TSSC-10
Date Submitted: 6/9/1999

Subject/IMS Table: Data collected by T6600 profilers: The field Profile Model Number in the MON_PROFILE_MASTER table of IMS contains incorrect values or is blank for some records.
Resolved: Yes
Last Updated: 3/16/2000

LTPP Analysis/Operations Situation: The model number of the optical K.J. Law profilers that were used initially in the LTPP program was DNC690. The model number for the infrared K.J. Law profilers is T6600. Two problems were identified in the Profile Model Number field. They are: (1) There are cases where the model number was specified to be T6600 for data that was collected with a DNC690. (2) There are records that have the Model Number field blank or incorrect values in this field.

Resolution of Problem/Situation: The data has been reviewed by the Regional Offices and corrections made.


Report Number: TSSC-71
Date Submitted: 8/18/2004

Subject/IMS Table: Pavement Surface Temperature for Dipstick Profile Measurements in MON_PROFILE_MASTER
Resolved: No
Last Updated: 5/31/2005

LTPP Analysis/Operations Situation: Guidelines for longitudinal profile measurements with a dipstick require measurement of the pavement surface temperature. Because the automated profilers collect air temperature information, data entry instructions for dipstick data indicate that the pavement surface temperatures should not be entered into the database. Therefore, the field TEMPERATURE in this table should be null if DEVICE_TYPE=D. The feedback report has a listing of measurements where DEVICE_TYPE=D and TEMPERATURE is not null.

Resolution of Problem/Situation: Not resolved.

 

 
PDF files can be viewed with the Acrobat® Reader®
This page last modified on 03/22/07
 

FHWA
United States Department of Transportation - Federal Highway Administration