...
Out of the box, the table has these the following columns:
Column Label | Column Name | Data Type | Required to Run PMS at Minimum | Description | Import Source Shape File Header | Import Source Shape File Data Type |
---|---|---|---|---|---|---|
Segment ID | PMSX_SEGMENT_ID | Integer | Y | ID used through out the system to identify each segment. Primary Key of the table. | SEG_ID | Long Integer |
Segment Name | SEGMENT_NAME | String | If there is a name assigned to the segment | SEG_NAME | Text | |
Segment Sequence | SEGMENT_SEQUENCE | String | Allows the system to sort the segment | SEG_SEQ | Long Integer | |
Road Name | ROAD_NAME | String | Street/Road name of the segment | ROAD_NAME | Text | |
From Description | DESCRIPTION_FROM | String | Begin description of the segment | DESCR_FROM | Text | |
To Description | DESCRIPTION_TO | String | End description of the segment | DESCR_TO | Text | |
Start Distance | DISTANCE_START | Number (22,3) | Begin distance measure of the segment | DIST_START | Double | |
End Distance | DISTANCE_END | Number (22,3) | End distance measure of the segment | DIST_END | Double | |
Start Latitude | LATITUDE_START | Number (22,9) | Begin latitude of the segment | START_LAT | Double | |
Start Longitude | LONGITUDE_START | Number (22,9) | Begin longitude of the segment | START_LONG | Double | |
End Latitude | LATITUDE_END | Number (22,9) | End latitude of the segment | END_LAT | Double | |
End Longitude | LONGITUDE_END | Number (22,9) | End longitude of the segment | END_LONG | Double | |
AADT | AADT | Integer | Y | AADT on the segment | AADT | Long Integer |
Length | LENGTH | Number (22,3) | Y | Length of the segment | LENGTH | Double |
Number of Lanes | NUMBER_OF_LANES | Integer | Number of lanes on the segment | NUM_LANES | Long Integer | |
Lane Miles | LANE_MILES | Number (22,3) | Y | Lane-miles of the segment | LANE_MILES | Double |
Segment Area | SEGMENT_AREA | Number (22,3) | Segment area | SEG_AREA | Double | |
Lane Width (Per Lane) | PER_LANE_WIDTH | Number (22,3) | Per lane width | PER_LN_WID | Double | |
Shoulder Width | SHOULDER_WIDTH | Number (22,3) | Shoulder width | SHLDR_WID | Double | |
Segment Width | SEGMENT_WIDTH | Number (22,3) | Segment width in total | SEG_WID | Double | |
Percent Truck | PCT_TRUCK | Number (22,2) | Truck percentage | PCT_TRUCK | Double | |
Last Rehab Year | YEAR_LAST_REHAB | Integer | Last year of rehabilitation on the segment | YEAR_REHAB | Long Integer | |
Last Preventive Maintenance Year | YEAR_LAST_PM | Integer | Last year of preventive treatment on the segment | YEAR_PM | Long Integer | |
Address: Left Side From | ADDRESS_LEFT_FROM | Integer | Left side of the segment: Begin address | ADDR_L_FRO | Double | |
Address: Left Side To | ADDRESS_LEFT_TO | Integer | Left side of the segment: End address | ADDR_L_TO | Double | |
Address: Right Side From | ADDRESS_RIGHT_FROM | Integer | Right side of the segment: Begin address | ADDR_R_FRO | Double | |
Address: Right Side To | ADDRESS_RIGHT_TO | Integer | Right side of the segment: End address | ADDR_R_TO | Double | |
Address: From | ADDRESS_FROM | Integer | Segment Begin Address | ADDR_FROM | Double | |
Address: To | ADDRESS_TO | String | Segment End Address | ADDR_TO | Double | |
Zip Code | ZIP_CODE | String | Zip code | ZIP_CODE | Text | |
City | CITY_ID | Integer | City | CITY | Text | |
County | COUNTY_ID | Integer | County | COUNTY | Text | |
Maintenance Jurisdiction | MAINTENANCE_JUR_ID | Integer | Maintenance Jurisdiction | JURIS | Text | |
NHS Type | NHS_TYPE_ID | Integer | NHS Designation | NHS | Text | |
Functional Class | FUNCTIONAL_CLASS_ID | Integer | Y | Functional Class | FC | Text |
Pavement Type | WC_ID | Integer | Y | Pavement Type | PVT_TYPE | Text |
One-way Street? | ONEWAY | Integer | Whether the segment is one-way | ONEWAY | Text | |
Divided Street (median) | DIVIDED | Integer | Whether the segment is divided (with a median) | DIVIDED | Text | |
Comment | COMMENT_STR | String | Comment | |||
User Update | USER_UPDATE | Integer | Last update user | |||
Date Update | DATE_UPDATE | Date | Last update date/time | |||
Geometry | GEOM | Geometry | Geometry. Hidden from the window. | SHAPE | Geometry |
Table and Window Configuration
The configuration of this dataset starts by expanding the PMSX_SEGMENT table structure to include customer-specific roadway inventory data elements (i.e., columns).
Most of the timeFor standard configurations, there are two types of data that are added to the table:
...
At this point, the system will have an empty PMSX_SEGMENT table and the window will display an empty dataset.
Info |
---|
Note: Shapefile projections need to be 4326 format. |
Import Data
The next step of configuring Roadway Inventory data is to create an import routine (often called Import Configuration in AgileAssets system), and load the data into the table. An Import Configuration includes the following:
...