Skip to end of metadata
Go to start of metadata

Roadway Inventory is for storing various roadway characteristics and their locations, such as Functional Class, Number of Lanes, Lane Width, Shoulder Width, etc. Out of the box, the table is named PMSX_SEGMENT, and the corresponding window can be navigated to by clicking Asset Inventory and selecting Roadway Segment from the drop-down menu.

Out of the box, the table has these columns:

Column LabelColumn NameData TypeRequired to Run PMS at MinimumDescriptionImport Source Shape File HeaderImport Source Shape File Data Type
Segment IDPMSX_SEGMENT_IDIntegerYID used through out the system to identify each segment. Primary Key of the table.SEG_IDLong Integer
Segment NameSEGMENT_NAMEString
If there is a name assigned to the segmentSEG_NAMEText
Segment SequenceSEGMENT_SEQUENCEString
Allows the system to sort the segmentSEG_SEQLong Integer
Road NameROAD_NAMEString
Street/Road name of the segmentROAD_NAMEText
From DescriptionDESCRIPTION_FROMString
Begin description of the segmentDESCR_FROMText
To DescriptionDESCRIPTION_TOString
End description of the segmentDESCR_TOText
Start DistanceDISTANCE_STARTNumber (22,3)
Begin distance measure of the segmentDIST_STARTDouble
End DistanceDISTANCE_ENDNumber (22,3)
End distance measure of the segmentDIST_ENDDouble
Start LatitudeLATITUDE_STARTNumber (22,9)
Begin latitude of the segmentSTART_LATDouble
Start LongitudeLONGITUDE_STARTNumber (22,9)
Begin longitude of the segmentSTART_LONGDouble
End LatitudeLATITUDE_ENDNumber (22,9)
End latitude of the segmentEND_LATDouble
End LongitudeLONGITUDE_ENDNumber (22,9)
End longitude of the segmentEND_LONGDouble
AADTAADTIntegerYAADT on the segmentAADTLong Integer
LengthLENGTHNumber (22,3)YLength of the segmentLENGTHDouble
Number of LanesNUMBER_OF_LANESInteger
Number of lanes on the segmentNUM_LANESLong Integer
Lane MilesLANE_MILESNumber (22,3)YLane-miles of the segmentLANE_MILESDouble
Segment AreaSEGMENT_AREANumber (22,3)
Segment areaSEG_AREADouble
Lane Width (Per Lane)PER_LANE_WIDTHNumber (22,3)
Per lane widthPER_LN_WIDDouble
Shoulder WidthSHOULDER_WIDTHNumber (22,3)
Shoulder widthSHLDR_WIDDouble
Segment WidthSEGMENT_WIDTHNumber (22,3)
Segment width in totalSEG_WIDDouble
Percent TruckPCT_TRUCKNumber (22,2)
Truck percentagePCT_TRUCKDouble
Last Rehab YearYEAR_LAST_REHABInteger
Last year of rehabilitation on the segmentYEAR_REHABLong Integer
Last Preventive Maintenance YearYEAR_LAST_PMInteger
Last year of preventive treatment on the segmentYEAR_PMLong Integer
Address: Left Side FromADDRESS_LEFT_FROMInteger
Left side of the segment: Begin addressADDR_L_FRODouble
Address: Left Side ToADDRESS_LEFT_TOInteger
Left side of the segment: End addressADDR_L_TODouble
Address: Right Side FromADDRESS_RIGHT_FROMInteger
Right side of the segment: Begin addressADDR_R_FRODouble
Address: Right Side ToADDRESS_RIGHT_TOInteger
Right side of the segment: End addressADDR_R_TODouble
Address: FromADDRESS_FROMInteger
Segment Begin AddressADDR_FROMDouble
Address: ToADDRESS_TOString
Segment End AddressADDR_TODouble
Zip CodeZIP_CODEString
Zip codeZIP_CODEText
CityCITY_IDInteger
CityCITYText
CountyCOUNTY_IDInteger
CountyCOUNTYText
Maintenance JurisdictionMAINTENANCE_JUR_IDInteger
Maintenance JurisdictionJURISText
NHS TypeNHS_TYPE_IDInteger
NHS DesignationNHSText
Functional ClassFUNCTIONAL_CLASS_IDIntegerYFunctional ClassFCText
Pavement TypeWC_IDIntegerYPavement TypePVT_TYPEText
One-way Street?ONEWAYInteger
Whether the segment is one-wayONEWAYText
Divided Street (median)DIVIDEDInteger
Whether the segment is divided (with a median)DIVIDEDText
CommentCOMMENT_STRString
Comment

User UpdateUSER_UPDATEInteger
Last update user

Date UpdateDATE_UPDATEDate
Last update date/time

GeometryGEOMGeometry
Geometry. Hidden from the window.SHAPEGeometry

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 time, there are two types of data that are added to the table:

  • Drop-down Column: sometimes also called List of Values, Lookup Values, or T-List column, such as Functional Class or Pavement Type
  • A simple value: can be either Numeric or String, such as Lane Width or Description

To create the first type of columns, follow the instruction detailed in Create and Import Lookup Values and add them into the PMS_ROADWAY_INVENTORY table.

To create the second type of columns, follow the instruction detailed in Add Columns to a Table and add them into the PMS_ROADWAY_INVENTORY table.

Note: Take these following aspects into consideration when designing the table structure:

  • Whether the data is actually needed
  • Whether the data will be available through an interface or import
  • How the data is presented in the source data - you want to match the columns as closely as possible to the source data to reduce the efforts when setting up the import routine, but also make sure data meets the system requirement after being imported
  • What type of data will be available when importing from an external data source

After all the columns have been added to the table, the next step is to add those columns to the window. A window does not automatically display all the columns of a table. It only displays columns that are configured as part of the window.

To display the columns that are newly added to the PMSX_SEGMENT table, follow the instruction detailed in Add Columns to a Data Window.

At this point, the system will have an empty PMSX_SEGMENT table and the window will display an empty dataset.

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:

  1. Specify data source
  2. Specify rules of import (e.g., how existing data is imported)
  3. Column mapping and data conversion

Out of the box, a standard import using SHAPE file  (*.shp)  has been configured that matches the PMSX_SEGMENT configuration. The file specification and column mapping is detailed in the table above.

If there is client-specific configuration to PMSX_SEGMENT table to track additional roadway segment data, the template can be expanded to include those fields. In addition, the following objects needs to be updated to reflect those changes to ensure all the steps in the import are running correctly:

  • PMSX_SEGMENT table and window
  • Import configuration into the PMSX_SEGMENT table

Preferably, if additional import is needed, the import configuration should be setup in a way so that the next time when data needs to be updated, it will simply read the new data source and run the same import configuration. Occasionally, the initial data load and on-going data import use different data sources, and therefore separate import configurations have to be created.

To update an Import Configuration or update the existing one, follow the instruction detailed in Import Data into Tables.

After running the import, the system will have a populated table and the window will display the corresponding data.


  • No labels