Load Pavement Data Into Cartegraph
Cartegraph’s Pavement solution provides robust functionality including industry standard attributes, libraries, and condition assessment data compliant with ASTM-6433-11.
To fully realize the value of Cartegraph’s solution, certain data attributes must be available and stored correctly. Due to the flexibility of Cartegraph and the variety of standard operating procedures each data collection vendor employs, data can easily be missed or loaded incorrectly. This can result in a reduced return on investment in the Cartegraph solution. See this spreadsheet for guidance on pavement data best practices.
Refer to the following sections:
Cartegraph provides a supplemental MS Excel spreadsheet illustrating the required format for data delivery titled Cartegraph Pavement Collection.
Cartegraph Data Attributes
The following data attributes are either required (*) or highly recommended to support robust pavement management functionality in Cartegraph.
Pavement Inventory Table
|
NAME |
DATA TYPE |
DESCRIPTION |
|---|---|---|
|
* Cartegraph ID |
Text |
Unique identifier for Cartegraph Pavement (section) record. This ID is used to link all associated roadway section related tables |
|
* Pavement Length |
Quantity (Number w/ Unit) |
Length of the Pavement section Quantity fields require two data cells per row: 1 Number value and 1 Unit of Measure (m, km, mi, yd) |
|
* Pavement Width |
Quantity (Number w/ Unit) |
Width of the Pavement section Quantity fields require two data cells per row: 1 Number value and 1 Unit of Measure (m, km, mi, yd) |
|
* Pavement Classification |
Text (Lookup) |
Pavement Classification value for Cartegraph Pavement record. Default values are Asphalt, Brick and Block, Concrete, Earth, and Gravel |
|
* Function Classification |
Text (Lookup) |
Functional Classification value for Cartegraph Pavement record. Default values are Rural Arterial, Rural Collector, Rural Local, Urban Arterial, Urban Collector, and Urban Local |
|
Street |
Text (Lookup) |
Street name for Cartegraph Pavement record |
|
Street Ahead |
Text (Lookup) |
(Intersecting) Street Ahead name for Cartegraph Pavement record |
|
Street Back |
Text (Lookup) |
(Intersecting) Street Back name for Cartegraph Pavement record |
|
Construction Date |
Date |
Construction date helps establish a baseline for each asset. This baseline is crucial when managing condition and deterioration of high cost, high impact assets. |
- Pavement attributes must include Length and Width values
- Pavement Classifications should be limited to the following:
- Gravel
- Brick and Block
- Concrete
- Asphalt
- Earth
- Functional Classifications should be limited to the following:
- Rural Arterial
- Rural Collector
- Rural Local
- Urban Arterial
- Urban Collector
- Urban Local
Pavement Inspection Table
|
NAME |
DATA TYPE |
DESCRIPTION |
|---|---|---|
|
* Cartegraph ID |
Text |
Unique identifier for Cartegraph Pavement (section) record. This ID is used to link all associated roadway section related tables |
|
* Inspection ID |
Text |
Unique identifier for inspections |
|
* Inspection Date |
Date |
Inspection date |
|
Average IRI |
Quantity with Unit |
If applicable, a pre-calculated Average IRI value must be provided. Additionally, an Average IRI value should be converted and provided in a 0 to 100 scale for use in Cartegraph’s Overall Condition Index (OCI) calculation. |
Pavement Detailed Distress Table**
|
NAME |
DATA TYPE |
DESCRIPTION |
|---|---|---|
|
* Cartegraph ID |
Text |
Unique identifier for Cartegraph Pavement (section) record. This ID will be used to link all associated roadway section related tables |
|
* Inspection ID |
Text |
Unique identifier for Inspection records |
|
* Sample ID |
Text |
Unique identifier for Sample Areas |
|
Sample To |
Integer |
Identify the end of the Sample Area |
|
Sample From |
Integer |
Identify the beginning of the Sample Area |
|
Sample Length |
Quantity with Unit |
|
|
|
|
|
|
* Distress |
Text (Lookup) |
Values must match distresses specified in the ASTM-6433-11 standard. |
|
* Severity |
Text (Lookup) |
Low, Moderate, High |
|
* Extent |
Number |
Must be represented as a percentage number value |
Distress data should be collected in accordance with ASTM D-6433-11 standards, including extent and severity.
- Distress Severities must be limited to the following:
- Low
- Moderate
- High
- Standard distresses:
- Asphalt Longitudinal Cracking and Asphalt Transverse Cracking should be combined into a single distress.
- PCC Faulting Right and PCC Faulting Left should be combined into a single distress.
- PCC Longitudinal Cracking and PCC Transverse Cracking should be combined into a single distress.
- Asphalt Raveling & Weathering should be separated into Asphalt Raveling and Asphalt Weathering – Surface Wear.
- ASTM-6433-11 requires unique Distress + Severity combinations per Sample area.
Pavement Condition Category Table
|
NAME |
DATA TYPE |
DESCRIPTION |
|---|---|---|
|
* Cartegraph ID |
Text |
Unique identifier for Cartegraph Pavement (section) record. This ID is used to link all associated roadway section related tables |
|
* Inspection ID |
Text |
Unique identifier for Inspection records |
|
|
|
|
|
Condition Category |
Text (Lookup) |
A value that generally reflects a high-level condition using a 0 to 100 scale index. For example, Cartegraph OMS recognizes PCI as a Condition Category. IRI values provided in a converted 0 to 100 scale can be loaded as a Ride Condition Category thereby impacting the Overall Condition Index (OCI) value in |
|
Index |
Integer |
A value, on a 0 to 100 scale, which reflects the condition of the corresponding Condition Category |
Standard Scope of Work
Cartegraph staff provides the following data services to load customer’s pavement data into Cartegraph:
- Cartegraph provides a template file to third-party vendors, so processed data can be delivered to Cartegraph in the required format.
- Cartegraph provides a review, not to exceed two hours, of Cartegraph data requirements to customer and third-party vendor staff.
- Cartegraph provides a field map review, not to exceed two hours, to identify the Cartegraph destination fields for up to 10 additional data attributes which may have been collected.
- Cartegraph provides a one-time data load into the customer’s test environment.
- Cartegraph provides a one-time data load into the customer’s production environment.
Assumptions, Requirements, and Considerations:
- This scope of work is isolated to data load activities and does not include any manipulation of collected data.
- Data must be provided to Cartegraph staff in Esri shapefile or .csv formats
- If Pavement spatial data is not provided and does not currently exist in the customer Cartegraph database, Cartegraph loads Pavement condition data without impacting the existing spatial implementation.
- Prior to collection efforts, third-party vendors must ensure collected data can be linked to a Cartegraph Pavement ID.
- Cartegraph calculates PCI values based on the ASTM-6433-11 – Standard Practice for Roads and Parking Lots Pavement Condition Index Surveys standard. Data collection firms are required to provide Distress, Severity, and Extent values as specified by the aforementioned standard.