| Description | |||
| Abstract: Represents Speed Humps located within pavement edge of streets. | |||
| Purpose: Speed Humps are used for controlling speed on residential streets and are located mid-block or mid segment (i.e. not in an intersection). To support the use of a GIS-based Asset Management System (AMS). Speed Humps are used for spatial analyses and geographic visualization, supporting work coordination, asset replacement/planning, asset inventorying, mapping, and over-all management of these assets. | |||
| Supplemental Information: From 2004 - 2007, Public Works' was engaged in the implementation of an AMS. As part of the AMS implementation, Public Works' consultant captured imagery of the City's right-of-way by driving a GPS/camera equipped van throughout the City of Richmond, from which stereo measurement software was used to locate asset objects visible in the 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. Speed Humps 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. This close relationshiop permits 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. 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 | |||
| 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.545946 | ||
| East Coordinate: | -77.420173 | ||
| North Coordinate: | 37.588115 | ||
| South Coordinate: | 37.462452 | ||
| Spatial Data Information | |||
| Data Type: | vector digital data | ||
| Data Format: | SDE Feature Class | ||
| 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_SpeedHump | ||
| Entity Type: | Feature Class | ||
| Entity Count: | 78 | ||