Transportation Assets
Keywords: Bridges, Traffic Cabinets, Crosswalks, Street Lanes, Loop Detectors, Parking Meter Poles, Pavement Markings, Pavement Stripes, Pedestrian Signals, Railroad Crossings, School Zones, Sidewalks, Traffic Signals, Traffic Signal Poles, Sign Mounts, Signs, Speed Humps, Speed Limits
Published: 200604
Richmond GIS Layer Inventory
Contact Richmond GIS
 
Description
  Abstract: Contains features representing Bridges, Traffic Cabinets, Crosswalks, Street Lanes, Loop Detectors, Parking Meter Poles, Pavement Markings, Pavement Stripes, Pedestrian Signals, Railroad Crossings, School Zones, Sidewalks, Traffic Signals, Traffic Signal Poles, Sign Mounts, Signs, Speed Humps, and Speed Limits.
  Purpose: Transporation Assets were collected for use in supporting Public Works' Asset Management System and processes. With a GIS-based Asset Management System (AMS), these assets are used for spatial analyses and geographic visualization, supporting work coordination, asset replacement/planning, asset inventorying, and over-all management of Public Works assets.
  Supplemental Information: From 2004 - 2007, Public Works' was engaged in the implementation of an Asset Management System (AMS). As part of the AMS implementation, Public Works' consultant captured imagery of the City's right-of-way (ROW) by deploying a GPS/camera equipped van which drove and took pictures throughout the City of Richmond ROW. The resulting imagery enabled stereo measurement software to be used to locate asset objects visible in those images. This type of terrestrial photogrammetry enabled technicians to interpret assets from the imagery and convert those assets into geographic coordinates. The majority of the asset types were collected in this fashion, and the inventory of both point and linear assets along the designated Carriageways were attributed and delivered to the City in GIS format. Linear assets/information, i.e. lanes, sidewalks, pavement stripes, are linearly referenced (LRS) from Carriageway features, each of which serve as individual route features (percent along). Point assets do not use LRS, but they do have reference to Carriageway features and include a) intersection ahead and behind (IntersectionID), and b) route ahead and behind (StreetNameID), and c) distance ahead and behind (distance to intersections). These are provided to assist in potential uses of textual references for locating assets. Transportation Assets are tightly coupled to the Carriageways in the Centerlines dataset, in ways that permit queries and anlaysis of Public Works' assets by street name, section and address ranges. Point assets may also carry the IntersetionID of an Intersection feature that it is associate with, thereby enabling asset inventory reporting and analyses by City intersections. Some Transportation Assets have a "Condition" field that is populated with good, fair, poor, which were interpreted from the vendor, to be used for planning work responses. Feature level metadata is provided in the EditBy and EditDate fields. Every feature in the GIS layer tracks who edited it, and when it was last edited. Internal documentation about Asset Object Data Collection for GIS Professionals: Q:\Infrastructure\Geodatabase\Datasets\TransportationAssets\TransmapManuals Internal documentation about Carriageway LRS routes for GIS Professionals: Q:\Infrastructure\Geodatabase\Datasets\Centerlines\Transportation\lrsSampleIllustrations.ppt
 
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
  Beginning Date: 200501
  Ending Date: 200505
 
Status
  Progress: Complete
  Update Frequency: As needed
 
Spatial Domain
  West Coordinate: -77.601472
  East Coordinate: -77.384933
  North Coordinate: 37.603760
  South Coordinate: 37.451182
 
Spatial Data Information
  Data Type: vector digital data
  Data Format: SDE Feature Dataset
  Data Projection: Lambert Conformal Conic
 
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_SignalHead
  Entity Type: Feature Class
  Entity Count: 3946
  Entity Name: vector.ric.tran_SignalPole
  Entity Type: Feature Class
  Entity Count: 2034
  Entity Name: vector.ric.tran_SignMount
  Entity Type: Feature Class
  Entity Count: 39936
  Entity Name: vector.ric.tran_SpeedHump
  Entity Type: Feature Class
  Entity Count: 78
  Entity Name: vector.ric.tran_SpeedLimit
  Entity Type: Feature Class
  Entity Count: 28199
  Entity Name: vector.ric.tran_PavementMarking
  Entity Type: Feature Class
  Entity Count: 8765
  Entity Name: vector.ric.tran_PavementStripe
  Entity Type: Feature Class
  Entity Count: 14362
  Entity Name: vector.ric.tran_RailroadCrossing
  Entity Type: Feature Class
  Entity Count: 122
  Entity Name: vector.ric.tran_SchoolZone
  Entity Type: Feature Class
  Entity Count: 623
  Entity Name: vector.ric.tran_LoopDetector
  Entity Type: Feature Class
  Entity Count: 428
  Entity Name: vector.ric.tran_ParkingMeterPole
  Entity Type: Feature Class
  Entity Count: 1358
  Entity Name: vector.ric.tran_Crosswalk
  Entity Type: Feature Class
  Entity Count: 2442
  Entity Name: vector.ric.tran_Lane
  Entity Type: Feature Class
  Entity Count: 32480
  Entity Name: vector.ric.tran_Cabinet
  Entity Type: Feature Class
  Entity Count: 490
  Entity Name: vector.ric.tran_BridgePoint
  Entity Type: Feature Class
  Entity Count: 165
  Entity Name: vector.ric.tran_Sidewalk
  Entity Type: Feature Class
  Entity Count: 16751
  Entity Name: vector.ric.tran_PedestrianSignal
  Entity Type: Feature Class
  Entity Count: 1087
  Entity Name: vector.ric.tran_SignMountHasSigns
  Entity Type: Relationship