| Description | |||
| Abstract: Pavement Sections event table, representing VDOT's pavement section definitions as translated to match the City's Carriageways. | |||
| Purpose: This event table is used to define the VDOT pavement sections as events that are used with dynamic segmentation to display against the City's Carriageway features; used to create tran_PavementCarriageway feature class. | |||
| Supplemental Information: The table named, "tran_pavement_event" is the GIS event table that is the source were the City maintains the translation of VDOT's pavement sections to our carriageways. Pavement sections are stored in an event table because VDOT pavement sections will sometimes terminate "along" an existing carriageway feature, such as 100 feet from an intersection in a mid-block location. The transportation model (carriageways) is not to be highly segmented to support pavement management so event tables and dynamic segmentation is used to create this feature class. After Pavement Carriageways are created via dynamic segmentation, they are dissolved by the PavementID field to create the tran_PavementSection feature class, which is easier to work with for GIS mapping and in Cartegraph software; it then represents each VDOT pavement section as a unique record/feature representation. The original VDOT pavement sections inventory always modeled streets as single lines, as a single table record. As discussed in the Carriageways metadata, the City models divided roads as double lines, if the street is physically divided, i.e. median. Therefore, Public Works' pavement management engineers have interatively gone through the exercise, with the support of GIS staff, to create new records in their pavement inventory for the "other-side-of-the-street," when divided carriageways were present. City pavement engineers treat divided streets as separate pavement entities. The resulting feature classes are considered to be works in progress, as none of the City's pavement engineers has actually completed the process of translating VDOT pavement sections against carriageways. Documentation internal to the City's GIS professionals can be found here: Q:\Infrastructure\Geodatabase\Datasets\Pavement\ | |||
| Contact | |||
| Custodian: | Pravin Mathur | ||
| Department: | Public Works | ||
| Position: | GIS/Cityworks Manager | ||
| Address: | 900 E Broad St, 7th floor | ||
| City: | Richmond | ||
| State: | Virginia | ||
| Zip Code: | 23219 | ||
| Email: | Pravin.Mathur@richmondgov.com | ||
| Time Period of Content | |||
| Date: | 200508 | ||
| Status | |||
| Progress: | In work | ||
| Update Frequency: | Annually | ||
| Spatial Domain | |||
| West Coordinate: | REQUIRED: Western-most coordinate of the limit of coverage expressed in longitude. | ||
| East Coordinate: | REQUIRED: Eastern-most coordinate of the limit of coverage expressed in longitude. | ||
| North Coordinate: | REQUIRED: Northern-most coordinate of the limit of coverage expressed in latitude. | ||
| South Coordinate: | REQUIRED: Southern-most coordinate of the limit of coverage expressed in latitude. | ||
| Spatial Data Information | |||
| Data Type: | tabular digital data | ||
| Data Format: | SDE Table | ||
| Access and Usage Information | |||
| Access Constraints: | none | ||
| Use Constraints: | All GIS layers and datasets are owned by the City of Richmond and can not be modified, re-distributed, and/or re-sold without a sub-licensing agreement. All guarantees of validity expire once a dataset leaves the City of Richmond firewall or physical premises. Acknowledgement of the City of Richmond GIS would be appreciated in products derived from these data. | ||
| Entity and Attribute Information | |||
| Entity Name: | vector.ric.tran_PavementEvent | ||
| Entity Type: | Table | ||
| Entity Count: | 15457 | ||