Roads

ISO-19139 Metadata

Resource Identification Information:

Citation:
Title:  Roads

Presentation format:  mapDigital

Themes or categories of the resource:  transportation

Descriptive keywords:
Keywords:  Downloadable Data

Thesaurus name: ArcGIS Content Type
Descriptive keywords:
Keywords:  COLE_StreetNumbers

Abstract:  This is the road linework for Riverside County, including cities. This data layer replaces centerlines as the main cartographic and geocoding engine in analysis and mapping. The differences between this layer and TLMA's centerline data are as follows:This layer follows aerial photos as evidence of street existence.This layer tries to eliminate "paper streets", which appear in legal documents but does not exist in real life.Graded tracts with centerlines will be considered as "tentative" rather than full validated streets.This layer will contain address ranges.This layer will update city streets as needed.CLASS: Roads classification.1 - Interstate2 - Interstate Ramp3 - US Highway4 - US Highway Ramp5 - CA Highway6 - CA Highway Ramp7 - Expressway8 - Expressway Ramp9 - Major Road10 - Arterial Street11 - Collector Street12 - Residential Street13 - Tentative-TLMA

Purpose: The purpose of this project is to create a street "centerline" base data layer with good spatial accuracy and attributes that will meet the needs of Riverside County GIS. This layer must reflect the streets on the ground and must be drivable. Updated 10/2015 - Mickey Zolezio (Riverside Co) Beginning with Riverside County's GIS data for roads, this feature class was updated and extensively corrected. The original data was clipped to the CityAtlasGrid layer, which contains nearly 8900 records. The address ranges in fields L_F_ADD, L_T_ADD, R_F_ADD, & R_T_ADD were later found to be incorrect in about 75% of the road data segments in Lake Elsinore. The parcel GIS data from the county was used to supply the house numbers to make the corrections. Refer to the Lineage section for more information.

Dataset language:  eng
Dataset character set:  utf8

Resource constraints:
Constraints:
Limitations of use: None.

Spatial representation type:  vector

Processing environment:  Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.0.12790

Extent:
Geographic element - Bounding rectangle:
Extent contains the resource: true
West longitude: -117.472064
East longitude: -117.187017
North latitude: 33.780137
South latitude: 33.548899
Credits: TLMA GIS; J. Curtright, SCG, 2020.

Spatial Representation - Vector:

Level of topology for this dataset:  geometryOnly
Geometric objects:
Object type:  composite
Object count: 8894

Reference System Information:

Reference system identifier:
Value: 2230
Code space: EPSG
Version: 5.3(9.0.0)

Data Quality Information:

Lineage:
Process step:
Description: Upon close inspection, it was discovered that the address ranges (fields L_T_ADD, L_F_ADD, R_T_ADD, R_F_ADD) were incorrect in at least 75% of the road segments. It may be true that the various addressing schemes being used in Lake Elsinore frustrated attempts to populate those fields with usable data. Using the HOUSE_NO field in the county's parcel data, these fields were given new values. It was not always possible to chose values that will work with geocoding processes, so the goal was to use values that when plotted on a map, showed the situation on the ground. Sample of types of problems: Odd & even numbers on both sides of the street Overlapping ranges across intersections Some road segments have a house number well out of range of the other parcels. House numbers out of order. There are streets, such as Central, were the addresses go up as you go north, yet in the adjacent streets, addresses go down as you go north.

Source data:
Level of the source data: For the Lake Elsinore Enterprise GIS project, Riverside County's Road feature class was chosen over their Centerline data. The Road data was found to be spatially more accurate, and included more address range data than Centerline. It turns out that the county replaced their centerline data with Roads as the main cartographic and geocoding engine in analysis and mapping. The data have been clipped to the CityAtlasGrid feature class. Since then some adjustments were made to roads which didn't line up well with Lake Elsinore's 3 inch aerial data, and some roads were deleted because they didn't exist. New roads have been added, mostly in the Summerly development.

Distribution Information:

Format:
Format name: Feature Class

Metadata Information:

Metadata language:  eng
Metadata character set:  utf8


Last update:  2020-12-09

Scope of the data described by the metadata:  dataset
Scope name: dataset

Name of the metadata standard used: ISO 19139 Geographic Information - Metadata - Implementation Specification
Version of the metadata standard: 2007