| Description | |||
| Abstract: Represents "Carriageways," which are linear features positioned along the center of the road bed that supports vehicular traffic between two at-grade intersections. Carriageways are represented as single lines, unless a street is physically divided by a median or structure. In the case of divided streets, the Carriageways appear as double-lines; one centerline for each of the road beds on either side of the divided road. | |||
| Purpose: Used for geocoding, linear referencing, street routing analysis, Cityworks Asset Management System, street source for Computer-Aided Dispatch System, and cartographic display of street centerlines. | |||
| Supplemental Information: Carriageways are not limited to the interior of the City's geographic corporation line. Carriageways that weave in and out of the City, such as the one representing Huguenot Road, that bridges the James River from southside and crosses through Henrico County to re-enter the City's north western extremity, are included to support efficient routing analysis. (In this case, the most expedient path would not entail remaining on city roads by doubling-back to another bridge). No attempt was made to include all surrounding county roads, but just enough of them to support efficient routing around the City. The FIPS code is used to identify which locality a carriageway falls inside of. Carriageway features are suitable for building a reliable network for routing analysis, via the OneWay field containing FT, TF, or blank values (two-way). These features also provide percentage (0-100) measures which may be used for linear referencing. Public Works' Transportation Assets are referenced with these measures along Carriageways. The CarriagewayID is the primary key for these features and this CarriagewayID value is also stored on Public Works' Transportation Assets, such that assets are inherently associated with specific streets, by name and address. The naming and addressing of street centerlines (Carriageways) is tightly coupled with Central Address and Address Points maintenance procedures. There are "authoritative sources" that span multiple agencies, who collaborate on edit changes to this data. 1) DPW performs all physical edit changes. 2) Community Development's Central Address GIS Specialist communicates the street naming and addressing updates that need to be made. 3) The Richmond Police Department's Computer-Aided Dispatch System's GIS/CAD administrator will often communicate street naming and addressing issues to the 2 previously mentioned groups; Central Address (DCD) and DPW GIS staff. 4) Public Works' Surveys Division will often assist in researching when there are questions about proper street naming. 5) Public Works' Streets and Engineering Division(s) will communicate physical changes (adds, deletes, modifications) that need to be made. 6) The subdivision process involves Community Development, Assessor, and Public Works; the creation of newly developed areas (subdivisions/plans of development) are used for determining how to represent new street features in the GIS. 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. Detailed Carriageway Documentation: http://www.richmondgov.com/GIS/documents/Centerlines_Documentation.pdf Documentation available internally to GIS professionals: Q:\Infrastructure\Geodatabase\Datasets\Centerlines\ | |||
| 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: | 200611 | ||
| Status | |||
| Progress: | Complete | ||
| Update Frequency: | As needed | ||
| Spatial Domain | |||
| West Coordinate: | -77.635025 | ||
| East Coordinate: | -77.344780 | ||
| North Coordinate: | 37.624046 | ||
| South Coordinate: | 37.431728 | ||
| 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_Carriageway | ||
| Entity Type: | Feature Class | ||
| Entity Count: | 27875 | ||
| Entity Name: | vector.ric.tran_CarriagewayHasAddressRanges | ||
| Entity Type: | Relationship | ||
| Entity Name: | vector.ric.tran_RoadHasCarriageways | ||
| Entity Type: | Relationship | ||
| Entity Name: | vector.ric.tran_StreetNameHasCarriageways | ||
| Entity Type: | Relationship | ||