Description: 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
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Data was spatially adjusted in 2020.This data set of line features represent Riverside County's recorded street centerlines.This data set was designed to carry out functions of the Transportation department and is not a true street network layer. Centerlines do not have complete "connectivity" due to the fact that this layer is primarily roads that have been recorded but does not necessarily contain all roads. OBJECTID - Internal feature number. STNAME - Recorded name of the centerline. TYPE - Used to classify roads, primarily by surface type. Description of the codes found in the attribute "TYPE" TYPE DESCRIPTION C01 Federal Aid Interstate C02 State Highways C03 F.A.U. Maintained C04 F.A.S. Maintained C05 Paved Surface Maintained C06 Paved Surface (Traveled) C07 Graveled Surface Maintained C08 Graveled Surface (Traveled) C09 Dirt Surface Maintained C10 Dirt Surface (Traveled) C11 Accepted For Public Use C12 Non-County/Accepted for P.U. C13 Non-County road C14 Vacated C15 Abandon C16 Maintained F.A.U./Non-County C17 Maintained F.A.S./Non-County C18 Maintained Paved/Accepted C19 Maintained Paved/Non-County C20 Maintained Paved/Vacated C21 Maintained Gravel/Accepted C22 Maintained Gravel/Non-County C23 Maintained Gravel/Vacated C24 Maintained Dirt/Accepted C25 Maintained Dirt/Non-County C26 Maintained Dirt/Vacated C27 Accepted/Vacated C28 Maintained Under Contract C29 City Road C30 Paved Maintained/Dirt Maintained C31 Dedicated and Accepted/CFD Maintained W01 Maintained for City W02 Maintained for City/Non-County W03 Maintained for City/Non-County (Reversed) W04 Maintained for City/Accepted W05 F.A.U. Maintained/Maintained for City W06 Dirt Surface Maintained/Maintained for City W07 Paved Surface Maintained/Maintained for City W08 Graveled Surface Maintained/Maintained for City Z01 Traffic Division Modeling Connectivity Use Only (The "W" series within the TYPE field were initially created for the City of Wildomar, but have had their application expanded to include any Centerline where the County maintains the road for a City - typically for a limited period after a City's incorporation. The "W" will continue as a convention to make it easy to distinguish such roads from roads normally maintained by the County, even though it is understood that the "W" will lose its initial association with the City of Wildomar over time.). GENPLANTYPE - General Plan Classification of the Road. Not corrected for the RCLIS 2003 updated at thsi time. Description of the codes found in the attribute "GENPLANTYPE" GENPLANTYPE SYMBOL DESCRIPTION 01 101 FREEWAY 02 201 EXPRESSWAY 03 301 URBAN ARTERIAL 04 304 URBAN ARTERIAL (PROPOSED) 05 401 ARTERIAL 06 404 ARTERIAL (PROPOSED) 07 501 MOUNTAIN ARTERIAL 08 504 MOUNTAIN ARTERIAL (PROPOSED) 09 13 MAJOR 10 16 MAJOR (PROPOSED) 11 21 SECONDARY 12 24 SECONDARY (PROPOSED) 13 801 SPECIFIC PLAN ROAD 14 804 SPECIFIC PLAN ROAD (PROPOSED) 15 25 SCENIC ROUTE 16 28 SCENIC ROUTE (PROPOSED) 17 0 COLLECTOR(PROPOSED) indicates that the road is part of the "General PLan Alignment" but does not currently exist as a legal centerline. This type of centerline will be stored in the CENTERLINEREF data set. DIRECTION - Represents the direction of traffic flow. Presently not supported. NAMEID - Numerical representation of the recorded street name. Unique STNAME and NAMEID values are tracked in the STNMS table. RDNUMBER - Used by the Transportation Department to identify county maintained roads. Used for accounting purposes. SEGNUMBER - Used in combination with the RDNUMBER to uniquely identify an individual centerline, segment, or length. No longer supported. FLAG - Indicates whether or not an arc will be used in a street network data set. Presently not used because there is no street network data set. L_F_ADD - The starting address for the left side of the street. L_T_ADD - The ending address for the left side of the street. R_F_ADD - The starting address for the right side of the street. R_T_ADD - The ending address for the right side of the street. PRE_DIR - The street direction prefix. Example: 'E' for east. STREET_NAME - The base legal street name of the centerline. Example: "MAIN". STREET_TYPE - The Street Name Type abbreviation. Example: 'ST' for street. Valid values for the STREET_TYPE field are: ' ' - ' ' (No Type is a space) AVE - AVENUE BLVD - BOULEVARD CIR - CIRCLE CT - COURT CV - COVE DR - DRIVE EXPY - EXPRESSWAY FWY - FREEWAY HWY - HIGHWAY LN - LANE LOOP - LOOP PATH - PATH PKWY - PARKWAY PL - PLACE PT - POINT RD - ROAD SQ - SQUARE ST- STREET TER - TERRACE TRL - TRAIL WALK - WALK WAY - WAY SUF_DIR - The street direction suffix. Example: "N' for north. TRACT - The tract map number in which the centerline can be found. MODIFIED - Modified Date CREATED - Created Date SOURCE_NOTES - References to legal documentation related to the Centerline found during research, including such things as recordation histroy, name change history, and acceptance for or termination of maintenance information, FULL_NAME - Name used to construct ROUTE_NAME field values. Used to detect changes in the STNAME value. AREA_PLAN_ABBREVIATION - Abbreviated Area Plan Name used to create ROUTE_NAME Valid values for AREA_PLAN_ABBREVIATION are: DESCN - Desert Center ECDES - East County/Desert ECVAP - Eastern Coachella Valley Plan ELSIN - Lake Elsinore EVALE - Eastvale HIGHG - Highgrove HVWIN - Harvest Valley/Winchester JURUP - Jurupa LAKEV - Lakeview/Nuevo LMATH - Lake Mathews MARCH - March MEADV - Mead Valley PASS - Pass Area PVERD - Palo Verde Valley RECHE - Reche Canyon REMAP - REMAP (Riverside Extended Mountain Area Plan) RIVER - Riverside/Corona/Norco SANJA - San Jacinto Valley SBCO - San Bernardino County SUNCI - Sun City/Menifee Valley SWAP - Southwest Area Plan TEMES - Temescal Valley WCVAP - Western Coachella Valley Area Plan SUBROUTE - Optional Identifier used to build ROUTE_NAME to separate branches or distiguish discontinuous portions of a street within an area plan that are unlikely to ever form a continuous route. ROUTE_NAME - Primary field used to construct a Linear Referencing derivative of the Centerlines layer. THis values is a component of ROUTE_ALT1 and ROUTE_ALT2 and is overriden by those fields when they have values. ROUTE_DIR1 - Used with ROUTE_NAME to build values for ROUTE_ALT1 when there is a value assigned. ROUTE_ALT1 - First Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Norh or East. ROUTE_DIR2 - Used with ROUTE_NAME to build values for ROUTE_ALT2 when there is a value assigned. ROUTE_ALT2 - Second Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Souh or West. BUILD_PRIORITY - Used to create Linear Referenced Routes. Sets the corner from which to build routes. Valuid values for BUILD_PRIORITY are: UL - Upper Left (Default) LL - Lower Left UR - Upper Right LR - Lower Right LINE_LINK - Geometric ID of Centerline arc. Made up of the From X/Y coordinate, the To X/Y coordinate and the Length. Used to detect geometric changes to an existing Centerline. CL_ID - Duplicate of OBJECTID. USed for detecting newly added segments to the network each week or to relate and join exported versions of CENTERLINES back to the original CENTERLINE feature class.FROM_X_COORDINATE, FROM_Y_COORDINATE, TO_X_COORDINATE and TO_Y_COORDINATE: The coordinate data for the end points of the line in numeric format.ROUTE_ORIENTED: Indicates if the line is drawn in the direction that corresponds to the Routes created based on the ROUTE_NAME fields.TRAVEL_DIRECTIONS: Indicates whether the road can be driven and in what directions. Values include "Both Ways", "From-To", "To-From" and "No Ways".CA_ROAD_SYSTEM_PAGE: The map page location of the California Roadway System (CRS) Maps containing the Centerline: See http://www.dot.ca.gov/hq/tsip/hseb/crs_maps/CA_ROAD_SYSTEM_INDEX: The map index grid location of the California Roadway System (CRS) Maps containing the Centerline: See http://www.dot.ca.gov/hq/tsip/hseb/crs_maps/CA_FUNCTIONAL_CLASS: The California Functional Classification of the Roadway per the CRS maps. Only classifications between 1 and 5 may qualify for state and federal funds. Classifications include:1 - Interstate2 - Other Freeway or Expressway3 - Other Principal Arterial4 - Minor Arterial5 - Major Collector6 - Minor Collector7 - LocalFEDERAL_ROUTE and FEDERAL_ROUTE_TYPE: The number of the Federal Interstate or U.S. Highway and the operational type of the facility, where applicable.STATE_ROUTE and STATE_ROUTE_TYPE: The number of the State Route or Highway and the operational type of the facility, where applicable.COUNTY_ROUTE: The number of a County Route.CITY_LEFT or CITY_RIGHT: The City or Community name to the left or right of the Centerline. Used for address geolocators.STATE: CA for Califonia. For geolocators that use the State field.ZIP_LEFT or ZIP_RIGHT: The ZIP code to the left or right of the Centerline. Used for address geolocators.FULL_NAME_MIXED_CASE: The full street name in mixed Upper and Lower case letters, sometimes also called Title case. May be used for labeling and geolocators.FROM_ELEVATION: The elevation level of the Start or From end of the Centerline expressed as a whole number with 0 being the default base level. This field can be used by Network Analyst to maintain elevation based separations of roads that meet at an intersection.TO_ELEVATION: The elevation level of the End or To end of the Centerline expressed as a whole number with 0 being the default base level. This field can be used by Network Analyst to maintain elevation based separations of roads that meet at an intersection.ROADCLASS: The ranking of the road into 3 classes for use with Network Analyst so that it will prefer routes with lower rankings over those with higher rankings. Normally the values are 1 when the CA_FUNCTIONAL_CLASS is 1, 2 when the CA_FUNCTIONAL_CLASS is 2 through 4, and 3 when the CA_FUNCTIONAL_CLASS is 5 and higher.SPEED_MILES_PER_HOUR: The posted or prime facia speed limit of the road in miles per hour. By default all new roads are first assigned with a 25 mph speed limit unless they are otherwise edited to reflect speed limit documentation or determined to have a different prime facia requirement.MINUTE: The number of minutes required to traverse the segment based on the shape length and SPEED_MILES_PER_HOUR value. This field can be used by Network Analyst to estimate the drive times for a given generated route.
Service Item Id: d1785335833440538d233de738b30ca1
Copyright Text: If you need additional information about CENTERLINES, please contact the Transportation Department at 951-955-6880 or on the web at http://www.tlma.co.riverside.ca.us/trans/office.shtm
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Intersection points derived from the Centerline Feature Class. Used for locating Intersections programmatically using cross-street references.
Service Item Id: d1785335833440538d233de738b30ca1
Copyright Text: Maintained by Richard Fairhurst of the Riverside County Transportation Department. Updated 06/28/2012.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: This data layer contains polygon features representing public parks of Riverside County. Included within the data are national forests and parks, county parks and preserves, city parks, and community parks. The data is collected from various government agencies such as the city governments, park and recreation districts, county and state governments, and US Forest Service. Spatial accuracy of parks is based of Riverside County parcels. Due to parcel shift, please perform spatial analysis with care.*Updated 08/22/2012 with parks from City of Riverside, Moreno Valley, and Riverside vicinity. P.KangPark name corrections and additional parks added 6/2014. Mickey Zolezio
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Policies are statements that guide the course of action the County must take to achieve the goals outlined in the three guidance documents, Consensus Planning principles, Vision and General Plan Principles. Data was spatially adjusted in 2020.
Value: TEMECULA VALLEY WINE COUNTRY POLICY AREA - EQUESTRIAN DISTRICT Label: TEMECULA VALLEY WINE COUNTRY POLICY AREA - EQUESTRIAN DISTRICT Description: N/A Symbol:
Value: TEMECULA VALLEY WINE COUNTRY POLICY AREA - RESIDENTIAL DISTRICT Label: TEMECULA VALLEY WINE COUNTRY POLICY AREA - RESIDENTIAL DISTRICT Description: N/A Symbol:
Value: TEMECULA VALLEY WINE COUNTRY POLICY AREA - WINERY DISTRICT Label: TEMECULA VALLEY WINE COUNTRY POLICY AREA - WINERY DISTRICT Description: N/A Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: This data set is a product of the final reconciled version of the PQP (Public/Quasi-Public Conserved Lands) and is a working copy of the baseline information, which will periodically be updated to correct inconsistencies, erroneous inclusions or results of required PQP replacement.The reconciliation was the result of a long term verification process to establish an accurate baseline for lands held in conservation. Efforts to begin the verification of this data set began in 2006 in order to meet the requirements of the MSHCP, which states that within five years of pemit issuance, the RCA shall verify the precise agreage,location amount and status of PQP lands in the MSHCP conservation area. Efforts were delayed however, when questions arose from the Wildlife Agencies as to whether particular properties were considered PQP or Additional Reserve Lands in the original baseline data as depicted on the PQP map at the time of adoption. Discussions culminated in a minor amendment adjustment (MA 2007-01) where these issues were adressed and finalized and the PQP reconciliation process resumed, verifying and authenticating inclusions. The timeline of PQP reconciliation was additionally compromised by the lack of prompt responses from partner agencies and special districts. During the 2010 calendar year, RCA made considerable headway in the PQP reconciliation process by completing the review of public/quasi-public lands within all of the cities and determined the status of these lands using accessible sources. In cases where there was no response from the individual entity, assessment was made with as much accuracy as possible expending input from local knowledge and prior designations. County departments were reviewed including Flood, Waste, Parks and RCTC. Federal and State properites were completed using current ownership as well as other sources when determining consistency of conserved land activities. BLM maps, numerous websites and the Wildlife Conservation Board were also utilized in the analysis. Properties managed or owned by environmental agencies were evaluated, such as the Center for Land Management and Riverside Land Conservancy and the preparation for proposed MOU's began. Comparisons were also made to other existing conserved land databases.When the initial review was complete, acreage assessments were made and it was determined that there was a need to add properties to establish the 347,000 acre base. The procedure to include other reviewed and qualified conserved lands is as follows: 1: Add in all additional State and Federal Lands within Rough Step Unit 9, 2: Add in all additional State and Federal Lands within Rough Step 4 not in criteria cells, 3: Add in all additional State and Federal Lands within Rough Step 2 not in criteria cells, 4: Add in selected State and Federal Lands within other Rough Step Units as needed, 5: Consider County (ie Parks, Flood Control etc) Water Districs and other quailfied lands not in criteria cells.This process was followed until the acreage threshold was met.There are inclusions in this database where status is yet to be determined. These properties are marked as 'Pending' in the Final Status field .They are currently unresolved until funding source questions for the OHV park and issue of BLM exchange parcels are resolved. Acreage for these properties have not been included in the required 347,000 acres to ensure appropriate coverage. A draft distribution of the reconciled version of Public/Quasi-Public land was sent to the Wildlife agencies for review in October 2011. This review led to sereral changes before being finalized by the agencies on July 19, 2012. Inspection of the PQP baseline data led to additional analysis of public ownership information. Consequently, supplemental properties were identified as appearing to meet the criteria for additional public/quasi-public conserved lands. These properties were documented, put in a GIS data layer, and set aside for further review.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Data was spatially adjusted in 2020. Recorded Maps with recording type, book, page and date with subdivision name if applicable.Recording Types include:AD - Assessment DistrictAM - Assessors Map Book (as historically recorded by the Assessors)IC - IN - InstrumentMB - Map Book (Tracts)OC - Orange County MapOM - Official MapPM - Parcel MapRS - Record of SurveySB - San Bernardino MapSD - San Diego MapSR - State Relinquishment
Service Item Id: d1785335833440538d233de738b30ca1
Copyright Text: Riverside County Transportation Department
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: This data set of polygon features represents Riverside County's specific plans. A specific plan is used to facilitate effective implementation of the general plan. The specific plan must specify in detail the land uses, public and private facilities needed to support the land uses, phasing of development, standards for the conservation, development, and use of natural resources, and a program of implementation measures, including financing measures.
Service Item Id: d1785335833440538d233de738b30ca1
Copyright Text: Riverside County Planning Department
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 16 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: This data set of polygon features represents Riverside County's Incorporated City Boundaries. Topology has been run and all gaps and overlaps have been fixed. The data has been adjusted to match Riverside County Parcel Boundaries. The city name field is used to represent the citys' name. Every polygon that represents an incorporated city must have a city name. Data was spatially adjusted in 2020. Maintained by Adam Grim, 12/2020
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Data was spatially adjusted in 2020. CITYNAME: City nameANNEXATION: Annexation numberLAFCO_NUM: Local Area Formation Commission numberRECORDED_DATE: Date of recordation for annexationINST_NUM: Recorders office instrument numberCITY_FIPS: Federal Information Processing Standard city numberMaintained by Adam Grim: 12/2020
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: This data set of polygon feature represents Riverside County's City Sphere of Influence. Areas that are affected by a neighboring City, but are not annexed to them. Topology has been run and all gaps and overlaps have been fixed. The data has been adjusted to match Riverside County Parcel Boundaries. Data was spatially adjusted in 2020. Maintained by Adam Grim: 12/2020
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Current General Plan Land Use for Riverside County. The General Plan provides new land use designations for all parcels in the unincorporated area of Riverside County. While delivery of this data was received by the County at this time, please be advised that GIS has NOT OFFICIALLY VERIFIED the data or PERFORMED ADEQUATE QUALITY CONTROL VALIDATION for ACCURACY or DISCREPANCIES. In addition, consistency review is planned for comparison of current Zoning classifications with General Plan designations. Until completion of this review, please be aware that discrepancies can occur on any parcel. *The data now reflects the current city boundaries, March Joint Powers Authority landuse designations have been removed. Please contact MJPA for landuse information. ***Please use the cartographic representations (Landuse, Overlay, Foundation Component) within this data layer for all map products. Data was spatially adjusted in 2020.
Service Item Id: d1785335833440538d233de738b30ca1
Copyright Text: Riverside County Planning Department
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: A highways data layer based off TLMA.STREETS. This layer contains the highway type, number and speed limit fields. There is also an Alias field for alternative names. Latest changes - Changed a section of the I-215/SH-60 combined from a primary designation of SH-60 to I-215. SH-60 is now the alias in the section of I-215 between Riverside and Moreno Valley. Future changes - 90/60/215 Interchange configuration, 215/60 realignment. 04/24/09 - New state highway relinquishments on Highway 86, 195. Parts of those highways have been removed. Hwy 86S now Hwy 86.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 20 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Minor water districts provide services to local communities and operate within the boundaries of larger "major" water districts. Data was spatially adjusted in 2020.Updated by:Mickey Zolezio 7/2015
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 18 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none