| Description | |||
| Abstract: Represents water objects as linears. Contains features representing the hydrological boundary lines for lakes, rivers, and streams; it is mainly used for representing Streams, through the use of definition queries. | |||
| Purpose: Used for mapping and geospatial analysis. | |||
| Supplemental Information: Hydrologic surface water features (streams) were combined with stormwater features in this dataset, in order to eventually support the modeling and tracing of water flow through both the man-made infrastructure and natural water features. Currently, the stormwater features have topological relationships that allow for building a network that can be used for tracing upstream/downstream flows. Stormwater system and natural streams, however, are currently disconnected. Stream data could be improved and included to participate in stormwater's network, which would allow tracing all the way to/from the James River to/from source points of the stormwater system. Notes on natural hydrologic features: The City's original base mapping initiative included Water Bodies and Streams, which were merely interpreted from the 1999 orthophotography product. For the purposes of supporting a network, the base mapping was not well organized, as streams included shorelines and outlines of water bodies, in addition to creeks identified by a single line representation. In 2008, the GIS Team subtyped streams into unsimplified & simplified features. The intention of creating the "simplified" features was to model all flowing water systems as a single line; including the James River's main channel. These single lines were also identified as base features in the City's Data Quality Standards, upon which thematic area boundaries may be created. Important Note: The hydrology dataset will require further evaluation & re-organization as Stormwater comes on-line in DPU and when the City needs to support stream network modeling; additional attribution of streams will be needed, i.e. perennial -vs- non perennial indicators. While the original data collection activities did not result in the population of the EditBy and EditDate attribute fields, feature level metadata is now enabled on these assets with the use of these fields. Every feature in the GIS layers can be tracked according to who edited it, and when it was last edited. | |||
| Contact | |||
| Custodian: | Neville Simon | ||
| Department: | Community Development | ||
| Position: | Engineer III | ||
| Address: | 400 Jeff Davis Hwy | ||
| City: | Richmond | ||
| State: | Virginia | ||
| Zip Code: | 232224 | ||
| Email: | Neville.Simon@richmondgov.com | ||
| Time Period of Content | |||
| Date: | 1999 | ||
| Status | |||
| Progress: | In work | ||
| Update Frequency: | As needed | ||
| Spatial Domain | |||
| West Coordinate: | -77.603270 | ||
| East Coordinate: | -77.383462 | ||
| North Coordinate: | 37.602714 | ||
| South Coordinate: | 37.445504 | ||
| 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.hydr_Stream | ||
| Entity Type: | Feature Class | ||
| Entity Count: | 4537 | ||