The Road Event Collection Methods interface allows the user to create metadata, edit the metadata if necessary, and export the metadata to a pipe delimited file to be used in the HPMS submittal. This "metadata" describes the dataset which explains variability in the collection and reporting of traffic data in HPMS. When the user selects the Road Event Collection Methods icon (), this interface will appear:
There are some controls offered on this interface:
| Control | Description |
| Year | This picklist contains a list of all current and previous years for which Traffic data has been stored within the TDM system. |
| Recalculate | This button instigates a recalculation of all rows where the Override checkbox has not been selected; if any unsaved changes exist on the table, the user must save them before performing this action. |
| Override | This checkbox allows the user to override the current row and edit its "Value" field. |
| Export to Pipe Delimited File |
This link creates a text file with the first row containing the Text File Field Names separated by pipe (|) symbols and the subsequent rows containing data separated in the same manner. The current Text File Field Names are:
|
| Save Changes |
This button will save the data in the interface table to the database table TrafficHPMSMetadata. |
| Discard Changes | This button will discard any changes made since the last save. |
In the interface and in the exported file, each metadata type will list data grouped by F_System and the value in the "Is Urban?" field. Each metadata type will have 14 values – one for each functional classification in urban areas (7) plus one for each functional classification in rural areas (7). The image below shows an example of this in the interface and the exported file; notice the Yes/No pattern and doubled numbers emphasized in the red boxes.
Comments
0 comments
Please sign in to leave a comment.