Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>This layer shows all adopted compatibility zones for airports in or around Riverside County.</SPAN></SPAN></P><P><SPAN>LOC_ID: FAA designated Airport call sign</SPAN></P><P><SPAN>NAME: Airport name</SPAN></P><P><SPAN>ZONES: Compatibility zone names</SPAN></P><P><SPAN>Maintained by Mickey Zolezio 5/2015</SPAN></P><P><SPAN>For specific information regarding Compatibility Zones go to:</SPAN></P><P><SPAN>http://www.rcaluc.org/</SPAN></P><P><SPAN /></P><P><SPAN /></P><P><SPAN /></P><P><SPAN /></P></DIV></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
Copyright Text: Riverside County Airport Land Use Commission
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>The Airport Influence Area is used for planning purposes and for disclosure purposes relating to real estate.</SPAN></SPAN></P><P><SPAN>LOC_ID: FAA designated Airport call sign</SPAN></P><P><SPAN>NAME: Airport name</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
Copyright Text: Riverside County Airport Land Use Commission
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>This data set of line feature represents Riverside County's airport runways.</SPAN></SPAN></P><P><SPAN><SPAN>RWY_ID: FAA designated runway call sign</SPAN></SPAN></P><P><SPAN><SPAN>ST_NAME: State location of runway</SPAN></SPAN></P><P><SPAN><SPAN>STFIPS: State designation</SPAN></SPAN></P><P><SPAN><SPAN>RWY_LEN: Length of runway in feet, if available</SPAN></SPAN></P><P><SPAN><SPAN>RWY_WDTH: Width of runway in feet, if available</SPAN></SPAN></P><P><SPAN><SPAN>RWY_SFC_TY: Runway surface type</SPAN></SPAN></P><OL><LI><P><SPAN>AFSC: Aggregate Friction Seal Coat</SPAN></P></LI><LI><P><SPAN>ASPH: Asphalt</SPAN></P></LI><LI><P><SPAN>CONC: Concrete</SPAN></P></LI><LI><P><SPAN>DIRT: Dirt</SPAN></P></LI><LI><P><SPAN>GRVD: Grooved</SPAN></P></LI><LI><P><SPAN>GRVL: Gravel</SPAN></P></LI><LI><P><SPAN>PFC: Porous Friction Courses</SPAN></P></LI><LI><P><SPAN>PSP: Pierced Steel Plank</SPAN></P></LI><LI><P><SPAN>RFSC: Rubberized Friction Seal Coat</SPAN></P></LI><LI><P><SPAN>TURF: Turf</SPAN></P></LI><LI><P><SPAN>TRTD: Treated</SPAN></P></LI><LI><P><SPAN>WC: Wire Combed</SPAN></P></LI></OL><P><SPAN>RWY_STATUS: Status of runway (Proposed/Existing)</SPAN></P><P><SPAN>NAME: Name of airport</SPAN></P><P><SPAN>LOC_ID: FAA assinged airport call sign</SPAN></P><P><SPAN /></P><P><SPAN /></P></DIV></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
Copyright Text: Riverside County Airport Land Use Commission
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>This is the Area Plan Boundary for the Riverside County Integrated Plan (RCIP).</SPAN></SPAN></P><P><SPAN><SPAN>AP_CODE: Area Plan Number</SPAN></SPAN></P><P><SPAN>NAME: Area Plan Name</SPAN></P><P><SPAN>ACRES: Acres derived from area</SPAN></P><P><SPAN>SQ_MILES: Square miles derived from area</SPAN></P><P><SPAN>Last updated by Emily Lee 3/23/2016 after GPA960, GPAs 2010-2015, and GPA960 ERRATA</SPAN></P><P><SPAN /></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-size:12pt">Data was spatially adjusted in 2020.</SPAN></P><DIV><DIV><P><SPAN>This data set of line features represent Riverside County's recorded street centerlines.</SPAN></P><P><SPAN><SPAN>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. </SPAN></SPAN></P><P><SPAN><SPAN>OBJECTID - Internal feature number. </SPAN></SPAN></P><P><SPAN><SPAN>STNAME - Recorded name of the centerline. </SPAN></SPAN></P><P><SPAN><SPAN>TYPE - Used to classify roads, primarily by surface type. </SPAN></SPAN></P><P><SPAN><SPAN>Description of the codes found in the attribute "TYPE" </SPAN></SPAN></P><P><SPAN><SPAN>TYPE DESCRIPTION </SPAN></SPAN></P><P><SPAN><SPAN>C01 Federal Aid Interstate </SPAN></SPAN></P><P><SPAN><SPAN>C02 State Highways </SPAN></SPAN></P><P><SPAN><SPAN>C03 F.A.U. Maintained </SPAN></SPAN></P><P><SPAN><SPAN>C04 F.A.S. Maintained </SPAN></SPAN></P><P><SPAN><SPAN>C05 Paved Surface Maintained </SPAN></SPAN></P><P><SPAN><SPAN>C06 Paved Surface (Traveled) </SPAN></SPAN></P><P><SPAN><SPAN>C07 Graveled Surface Maintained </SPAN></SPAN></P><P><SPAN><SPAN>C08 Graveled Surface (Traveled) </SPAN></SPAN></P><P><SPAN><SPAN>C09 Dirt Surface Maintained </SPAN></SPAN></P><P><SPAN><SPAN>C10 Dirt Surface (Traveled) </SPAN></SPAN></P><P><SPAN><SPAN>C11 Accepted For Public Use </SPAN></SPAN></P><P><SPAN><SPAN>C12 Non-County/Accepted for P.U. </SPAN></SPAN></P><P><SPAN><SPAN>C13 Non-County road </SPAN></SPAN></P><P><SPAN><SPAN>C14 Vacated </SPAN></SPAN></P><P><SPAN><SPAN>C15 Abandon </SPAN></SPAN></P><P><SPAN><SPAN>C16 Maintained F.A.U./Non-County </SPAN></SPAN></P><P><SPAN><SPAN>C17 Maintained F.A.S./Non-County </SPAN></SPAN></P><P><SPAN><SPAN>C18 Maintained Paved/Accepted </SPAN></SPAN></P><P><SPAN><SPAN>C19 Maintained Paved/Non-County </SPAN></SPAN></P><P><SPAN><SPAN>C20 Maintained Paved/Vacated </SPAN></SPAN></P><P><SPAN><SPAN>C21 Maintained Gravel/Accepted </SPAN></SPAN></P><P><SPAN><SPAN>C22 Maintained Gravel/Non-County </SPAN></SPAN></P><P><SPAN><SPAN>C23 Maintained Gravel/Vacated </SPAN></SPAN></P><P><SPAN><SPAN>C24 Maintained Dirt/Accepted </SPAN></SPAN></P><P><SPAN><SPAN>C25 Maintained Dirt/Non-County </SPAN></SPAN></P><P><SPAN><SPAN>C26 Maintained Dirt/Vacated </SPAN></SPAN></P><P><SPAN><SPAN>C27 Accepted/Vacated </SPAN></SPAN></P><P><SPAN><SPAN>C28 Maintained Under Contract </SPAN></SPAN></P><P><SPAN><SPAN>C29 City Road </SPAN></SPAN></P><P><SPAN><SPAN>C30 Paved Maintained/Dirt Maintained </SPAN></SPAN></P><P><SPAN><SPAN>C31 Dedicated and Accepted/CFD Maintained </SPAN></SPAN></P><P><SPAN><SPAN>W01 Maintained for City </SPAN></SPAN></P><P><SPAN><SPAN>W02 Maintained for City/Non-County </SPAN></SPAN></P><P><SPAN><SPAN>W03 Maintained for City/Non-County (Reversed) </SPAN></SPAN></P><P><SPAN><SPAN>W04 Maintained for City/Accepted </SPAN></SPAN></P><P><SPAN><SPAN>W05 F.A.U. Maintained/Maintained for City </SPAN></SPAN></P><P><SPAN><SPAN>W06 Dirt Surface Maintained/Maintained for City </SPAN></SPAN></P><P><SPAN><SPAN>W07 Paved Surface Maintained/Maintained for City </SPAN></SPAN></P><P><SPAN><SPAN>W08 Graveled Surface Maintained/Maintained for City </SPAN></SPAN></P><P><SPAN><SPAN>Z01 Traffic Division Modeling Connectivity Use Only </SPAN></SPAN></P><P><SPAN><SPAN>(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.). </SPAN></SPAN></P><P><SPAN><SPAN>GENPLANTYPE - General Plan Classification of the Road. Not corrected for the RCLIS 2003 updated at thsi time. </SPAN></SPAN></P><P><SPAN><SPAN>Description of the codes found in the attribute "GENPLANTYPE" </SPAN></SPAN></P><P><SPAN><SPAN>GENPLANTYPE SYMBOL DESCRIPTION </SPAN></SPAN></P><P><SPAN><SPAN>01 101 FREEWAY </SPAN></SPAN></P><P><SPAN><SPAN>02 201 EXPRESSWAY </SPAN></SPAN></P><P><SPAN><SPAN>03 301 URBAN ARTERIAL </SPAN></SPAN></P><P><SPAN><SPAN>04 304 URBAN ARTERIAL (PROPOSED) </SPAN></SPAN></P><P><SPAN><SPAN>05 401 ARTERIAL </SPAN></SPAN></P><P><SPAN><SPAN>06 404 ARTERIAL (PROPOSED) </SPAN></SPAN></P><P><SPAN><SPAN>07 501 MOUNTAIN ARTERIAL </SPAN></SPAN></P><P><SPAN><SPAN>08 504 MOUNTAIN ARTERIAL (PROPOSED) </SPAN></SPAN></P><P><SPAN><SPAN>09 13 MAJOR </SPAN></SPAN></P><P><SPAN><SPAN>10 16 MAJOR (PROPOSED) </SPAN></SPAN></P><P><SPAN><SPAN>11 21 SECONDARY </SPAN></SPAN></P><P><SPAN><SPAN>12 24 SECONDARY (PROPOSED) </SPAN></SPAN></P><P><SPAN><SPAN>13 801 SPECIFIC PLAN ROAD </SPAN></SPAN></P><P><SPAN><SPAN>14 804 SPECIFIC PLAN ROAD (PROPOSED) </SPAN></SPAN></P><P><SPAN><SPAN>15 25 SCENIC ROUTE </SPAN></SPAN></P><P><SPAN><SPAN>16 28 SCENIC ROUTE (PROPOSED) </SPAN></SPAN></P><P><SPAN><SPAN>17 0 COLLECTOR</SPAN></SPAN></P><P><SPAN><SPAN>(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. </SPAN></SPAN></P><P><SPAN><SPAN>DIRECTION - Represents the direction of traffic flow. Presently not supported. </SPAN></SPAN></P><P><SPAN><SPAN>NAMEID - Numerical representation of the recorded street name. Unique STNAME and NAMEID values are tracked in the STNMS table. </SPAN></SPAN></P><P><SPAN><SPAN>RDNUMBER - Used by the Transportation Department to identify county maintained roads. Used for accounting purposes. </SPAN></SPAN></P><P><SPAN><SPAN>SEGNUMBER - Used in combination with the RDNUMBER to uniquely identify an individual centerline, segment, or length. No longer supported. </SPAN></SPAN></P><P><SPAN><SPAN>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. </SPAN></SPAN></P><P><SPAN><SPAN>L_F_ADD - The starting address for the left side of the street. </SPAN></SPAN></P><P><SPAN><SPAN>L_T_ADD - The ending address for the left side of the street. </SPAN></SPAN></P><P><SPAN><SPAN>R_F_ADD - The starting address for the right side of the street. </SPAN></SPAN></P><P><SPAN><SPAN>R_T_ADD - The ending address for the right side of the street. </SPAN></SPAN></P><P><SPAN><SPAN>PRE_DIR - The street direction prefix. Example: 'E' for east. </SPAN></SPAN></P><P><SPAN><SPAN>STREET_NAME - The base legal street name of the centerline. Example: "MAIN". </SPAN></SPAN></P><P><SPAN><SPAN>STREET_TYPE - The Street Name Type abbreviation. Example: 'ST' for street. </SPAN></SPAN></P><P><SPAN><SPAN>Valid values for the STREET_TYPE field are: </SPAN></SPAN></P><P><SPAN><SPAN>' ' - ' ' (No Type is a space) </SPAN></SPAN></P><P><SPAN><SPAN>AVE - AVENUE </SPAN></SPAN></P><P><SPAN><SPAN>BLVD - BOULEVARD </SPAN></SPAN></P><P><SPAN><SPAN>CIR - CIRCLE </SPAN></SPAN></P><P><SPAN><SPAN>CT - COURT </SPAN></SPAN></P><P><SPAN><SPAN>CV - COVE </SPAN></SPAN></P><P><SPAN><SPAN>DR - DRIVE </SPAN></SPAN></P><P><SPAN><SPAN>EXPY - EXPRESSWAY </SPAN></SPAN></P><P><SPAN><SPAN>FWY - FREEWAY </SPAN></SPAN></P><P><SPAN><SPAN>HWY - HIGHWAY </SPAN></SPAN></P><P><SPAN><SPAN>LN - LANE </SPAN></SPAN></P><P><SPAN><SPAN>LOOP - LOOP </SPAN></SPAN></P><P><SPAN><SPAN>PATH - PATH </SPAN></SPAN></P><P><SPAN><SPAN>PKWY - PARKWAY </SPAN></SPAN></P><P><SPAN><SPAN>PL - PLACE </SPAN></SPAN></P><P><SPAN><SPAN>PT - POINT </SPAN></SPAN></P><P><SPAN><SPAN>RD - ROAD </SPAN></SPAN></P><P><SPAN><SPAN>SQ - SQUARE </SPAN></SPAN></P><P><SPAN><SPAN>ST- STREET </SPAN></SPAN></P><P><SPAN><SPAN>TER - TERRACE </SPAN></SPAN></P><P><SPAN><SPAN>TRL - TRAIL </SPAN></SPAN></P><P><SPAN><SPAN>WALK - WALK </SPAN></SPAN></P><P><SPAN><SPAN>WAY - WAY </SPAN></SPAN></P><P><SPAN><SPAN>SUF_DIR - The street direction suffix. Example: "N' for north. </SPAN></SPAN></P><P><SPAN><SPAN>TRACT - The tract map number in which the centerline can be found. </SPAN></SPAN></P><P><SPAN><SPAN>MODIFIED - Modified Date </SPAN></SPAN></P><P><SPAN><SPAN>CREATED - Created Date </SPAN></SPAN></P><P><SPAN><SPAN>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, </SPAN></SPAN></P><P><SPAN><SPAN>FULL_NAME - Name used to construct ROUTE_NAME field values. Used to detect changes in the STNAME value. </SPAN></SPAN></P><P><SPAN><SPAN>AREA_PLAN_ABBREVIATION - Abbreviated Area Plan Name used to create ROUTE_NAME </SPAN></SPAN></P><P><SPAN><SPAN>Valid values for AREA_PLAN_ABBREVIATION are: </SPAN></SPAN></P><P><SPAN><SPAN>DESCN - Desert Center </SPAN></SPAN></P><P><SPAN><SPAN>ECDES - East County/Desert </SPAN></SPAN></P><P><SPAN><SPAN>ECVAP - Eastern Coachella Valley Plan </SPAN></SPAN></P><P><SPAN><SPAN>ELSIN - Lake Elsinore </SPAN></SPAN></P><P><SPAN><SPAN>EVALE - Eastvale </SPAN></SPAN></P><P><SPAN><SPAN>HIGHG - Highgrove </SPAN></SPAN></P><P><SPAN><SPAN>HVWIN - Harvest Valley/Winchester </SPAN></SPAN></P><P><SPAN><SPAN>JURUP - Jurupa </SPAN></SPAN></P><P><SPAN><SPAN>LAKEV - Lakeview/Nuevo </SPAN></SPAN></P><P><SPAN><SPAN>LMATH - Lake Mathews </SPAN></SPAN></P><P><SPAN><SPAN>MARCH - March </SPAN></SPAN></P><P><SPAN><SPAN>MEADV - Mead Valley </SPAN></SPAN></P><P><SPAN><SPAN>PASS - Pass Area </SPAN></SPAN></P><P><SPAN><SPAN>PVERD - Palo Verde Valley </SPAN></SPAN></P><P><SPAN><SPAN>RECHE - Reche Canyon </SPAN></SPAN></P><P><SPAN><SPAN>REMAP - REMAP (Riverside Extended Mountain Area Plan) </SPAN></SPAN></P><P><SPAN><SPAN>RIVER - Riverside/Corona/Norco </SPAN></SPAN></P><P><SPAN><SPAN>SANJA - San Jacinto Valley </SPAN></SPAN></P><P><SPAN><SPAN>SBCO - San Bernardino County </SPAN></SPAN></P><P><SPAN><SPAN>SUNCI - Sun City/Menifee Valley </SPAN></SPAN></P><P><SPAN><SPAN>SWAP - Southwest Area Plan </SPAN></SPAN></P><P><SPAN><SPAN>TEMES - Temescal Valley </SPAN></SPAN></P><P><SPAN><SPAN>WCVAP - Western Coachella Valley Area Plan </SPAN></SPAN></P><P><SPAN><SPAN>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. </SPAN></SPAN></P><P><SPAN><SPAN>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. </SPAN></SPAN></P><P><SPAN><SPAN>ROUTE_DIR1 - Used with ROUTE_NAME to build values for ROUTE_ALT1 when there is a value assigned. </SPAN></SPAN></P><P><SPAN><SPAN>ROUTE_ALT1 - First Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Norh or East. </SPAN></SPAN></P><P><SPAN><SPAN>ROUTE_DIR2 - Used with ROUTE_NAME to build values for ROUTE_ALT2 when there is a value assigned. </SPAN></SPAN></P><P><SPAN><SPAN>ROUTE_ALT2 - Second Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Souh or West. </SPAN></SPAN></P><P><SPAN><SPAN>BUILD_PRIORITY - Used to create Linear Referenced Routes. Sets the corner from which to build routes. </SPAN></SPAN></P><P><SPAN><SPAN>Valuid values for BUILD_PRIORITY are: </SPAN></SPAN></P><P><SPAN><SPAN>UL - Upper Left (Default) </SPAN></SPAN></P><P><SPAN><SPAN>LL - Lower Left </SPAN></SPAN></P><P><SPAN><SPAN>UR - Upper Right </SPAN></SPAN></P><P><SPAN><SPAN>LR - Lower Right </SPAN></SPAN></P><P><SPAN><SPAN>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. </SPAN></SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>ROUTE_ORIENTED: Indicates if the line is drawn in the direction that corresponds to the Routes created based on the ROUTE_NAME fields.</SPAN></P><P><SPAN>TRAVEL_DIRECTIONS: Indicates whether the road can be driven and in what directions. Values include "Both Ways", "From-To", "To-From" and "No Ways".</SPAN></P><P><SPAN>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/</SPAN></P><P><SPAN>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/</SPAN></P><P><SPAN>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:</SPAN></P><P><SPAN>1 - Interstate</SPAN></P><P><SPAN>2 - Other Freeway or Expressway</SPAN></P><P><SPAN>3 - Other Principal Arterial</SPAN></P><P><SPAN>4 - Minor Arterial</SPAN></P><P><SPAN>5 - Major Collector</SPAN></P><P><SPAN>6 - Minor Collector</SPAN></P><P><SPAN>7 - Local</SPAN></P><P><SPAN>FEDERAL_ROUTE and FEDERAL_ROUTE_TYPE: The number of the Federal Interstate or U.S. Highway and the operational type of the facility, where applicable.</SPAN></P><P><SPAN>STATE_ROUTE and STATE_ROUTE_TYPE: The number of the State Route or Highway and the operational type of the facility, where applicable.</SPAN></P><P><SPAN>COUNTY_ROUTE: The number of a County Route.</SPAN></P><P><SPAN>CITY_LEFT or CITY_RIGHT: The City or Community name to the left or right of the Centerline. Used for address geolocators.</SPAN></P><P><SPAN>STATE: CA for Califonia. For geolocators that use the State field.</SPAN></P><P><SPAN>ZIP_LEFT or ZIP_RIGHT: The ZIP code to the left or right of the Centerline. Used for address geolocators.</SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>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.</SPAN></P></DIV></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
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
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>Intersection points derived from the Centerline Feature Class. Used for locating Intersections programmatically using cross-street references.</SPAN></P></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
Copyright Text: Maintained by Richard Fairhurst of the Riverside County Transportation Department. Updated 06/28/2012.
Description: <DIV STYLE="text-align:Left;"><P><SPAN>Data was spatially adjusted in 2020.</SPAN></P><P><SPAN>Centerline Routes for Linear Referencing</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>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. </SPAN></SPAN></P><P><SPAN><SPAN>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. </SPAN></SPAN></P><P><SPAN>Maintained by Adam Grim, 12/2020</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Data was spatially adjusted in 2020. </SPAN></P><P><SPAN>CITYNAME: City name</SPAN></P><P><SPAN>ANNEXATION: Annexation number</SPAN></P><P><SPAN>LAFCO_NUM: Local Area Formation Commission number</SPAN></P><P><SPAN>RECORDED_DATE: Date of recordation for annexation</SPAN></P><P><SPAN>INST_NUM: Recorders office instrument number</SPAN></P><P><SPAN>CITY_FIPS: Federal Information Processing Standard city number</SPAN></P><P><SPAN /></P><P><SPAN>Maintained by Adam Grim: 12/2020</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Data was spatially adjusted in 2020. </SPAN></P><P><SPAN>ANNEXATION:</SPAN></P><P><SPAN>LAFCO_NUM: Local Area Formation Commission number</SPAN></P><P><SPAN>RECORDED_DATE: Empty</SPAN></P><P><SPAN>PROPOSED_CITY: Name of city to be annexed to</SPAN></P><P><SPAN>ACTION: Annexation</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>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. </SPAN></SPAN></P><P><SPAN>Maintained by Adam Grim: 12/2020</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>MACs - Municipal Advisory Councils, and CCs - Community Councils, are established by the Board of Supervisors. They are bodies appointed by the Board to provide an extra avenue for communication from the affected communities back to the Board member who represents them, about issues of concern to them. Their boundaries come from the Supervisors who established them. Data was spatially adjusted in 2020. </SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /><SPAN /></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>NAME: CAC/MAC name</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /><SPAN /></P><P STYLE="margin:0 0 0 0;"><SPAN>TYPE: "MAC" = Municipal Advisory Councils, "CC" = Community Council</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /><SPAN /></P><P><SPAN>Maintained by Mickey Zoleizo, 9/2015</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>To show the adjacent counties of the County of Riverside, CA.</SPAN></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Data was spatially adjusted in 2020. </SPAN></P><P><SPAN><SPAN>CSA_NUMBER: The CSA number</SPAN></SPAN></P><P><SPAN>NAME: Name of CSA</SPAN></P><P><SPAN><SPAN>SUBZONE: Wine Country reference</SPAN></SPAN></P><P><SPAN>ST_LIGHTING: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"</SPAN></P><P><SPAN><SPAN>ST_SWEEPING: </SPAN></SPAN><SPAN>"Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"</SPAN></P><P><SPAN><SPAN>PARK_REC: </SPAN></SPAN><SPAN>"Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"</SPAN></P><P><SPAN><SPAN>FIRE_PROTECT: </SPAN></SPAN><SPAN>"Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"</SPAN></P><P><SPAN>SEWER: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"</SPAN></P><P><SPAN>WATER: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"</SPAN></P><P><SPAN>TRASH: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"</SPAN></P><P><SPAN>ROAD_MAINT: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"</SPAN></P><P><SPAN>FLOOD_CTRL: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"</SPAN></P><P><SPAN>POLICE: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"</SPAN></P><P><SPAN>DRAINAGE_CTRL: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"</SPAN></P><P><SPAN>LIBRARY: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"</SPAN></P><P><SPAN>LANDSCAPING: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"</SPAN></P><P><SPAN>SPHERE_NUMBER: Not used</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
Copyright Text: Riverside County Planning, RCIT GIS
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This data set of polygon features represents Riverside County's desert tortoise area. Data was spatially adjusted in 2020</SPAN></P><P><SPAN>UNIT_NAME: Name of desert tortoise areas</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>The Subdivision Map Act requires that agencies imposing fees have a general drainage plan for the fee area, a special fund for the fees and an equitable distribution of the fees prior to implementation. Since the District does not have land use authority, it cannot implement drainage fees directly. The District must therefore request that the County and/or local cities adopt drainage fees within their jurisdictions for the District. The District generally agrees to create the special funds for the fees and to prepare an ADP. </SPAN></SPAN></P><P><SPAN><SPAN>The ADP is a document specifically prepared for the County and cities to adopt. The Area Drainage Plan is essentially the Master Drainage Plan with additional language supporting the costs and distribution of the fee within the plan area. To ensure the equitable distribution of fees, the ADP/MDP boundaries are generally based on watersheds. The total costs of facilities within the watershed are first calculated. The watershed area is then adjusted to discount publicly owned lands and areas on steep slopes not likely to develop. Finally, the total facility cost is divided by the revised watershed area to determine a per acre fee for the plan area. </SPAN></SPAN></P><P><SPAN><SPAN>Due to State Law, the collection of drainage fees varies depending on the type of development. Developments falling under the Subdivision Map Act (those requiring a division of lands) pay fees on a per acre basis. Developments falling outside of the Subdivision Map Act (known as discretionary developments) can only be assessed fees based on their impacts to the watershed. The ADP Rules and Regulations state that these impacts can be related to the amount of impervious surface area that the development creates. Therefore, discretionary developments are charged not on a gross acreage basis, but on the total impervious acreage created by their development.</SPAN></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
Copyright Text: Credit for this material belongs solely to the Riverside County Flood Control and Water Conservation District.
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>Established in 1982, Government Code Section 65570 mandates FMMP to biennially report on the conversion of farmland and grazing land, and to provide maps and data to local government and the public. </SPAN></SPAN></P><P><SPAN><SPAN>FMMP 2016 Data</SPAN></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
Copyright Text: A citation for the Farmland Mapping and Monitoring Program on any map products, graphic media, or data analyses based on the data is appreciated.
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>County Faults/Fault Zones (Per Riverside County General Plan 10/2003). Alquist-Priolo Earthquake Fault Zones have been designated by the California Division of Mines and Geology for the Elsinore, San Jacinto, and San Andreas fault zones in Riverside County. Within the rapidly growing county, State A-P mapping has not kept pace with development. The County of Riverside has zoned fault systems and required similar special studies prior to development. These are referred to as County Fault Zones on Figure S-2 and in the Technical Background Report. Within A-P and County Fault Zones, proposed tracts of four or more dwelling units must investigate the potential for and setback from ground rupture hazards. As there are many active faults in Riverside County, with new fault strands being continually discovered, all proposed structures designed for human occupancy should be required to investigate the potential for and setback from ground rupture. Also of concern are structures, not for human occupancy, that can cause harm if damaged by an earthquake, such as utility, communications, and transportation lifelines. The County regulates most development projects within earthquake fault zones (Figure S-2). Projects include all land divisions and most structures for human occupancy. Before a project can be permitted within an A-P Earthquake Fault Zone, County Fault Zone, or within 150 feet of any other potentially active or active fault mapped in published United States Geological Survey (USGS) or California Division of Mining and Geology (CDMG) reports, a geologic investigation must demonstrate that proposed buildings will not be constructed across active faults.</SPAN></SPAN></P><P STYLE="font-size:16ptmargin:7 0 7 0;"><SPAN><SPAN>Updated 2/2016 with Thermal and Indio California Geologic Survey Quads</SPAN></SPAN></P><P><SPAN><SPAN /></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
Copyright Text: USGS, California Division of Mining and Geology
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>County Faults/Fault Zones (Per Riverside County General Plan 10/2003) Alquist-Priolo Earthquake Fault Zones have been designated by the California Division of Mines and Geology for the Elsinore, San Jacinto, and San Andreas fault zones in Riverside County. Within the rapidly growing county, State A-P mapping has not kept pace with development. The County of Riverside has zoned fault systems and required similar special studies prior to development. These are referred to as County Fault Zones on Figure S-2 and in the Technical Background Report. Within A-P and County Fault Zones, proposed tracts of four or more dwelling units must investigate the potential for and setback from ground rupture hazards. As there are many active faults in Riverside County, with new fault strands being continually discovered, all proposed structures designed for human occupancy should be required to investigate the potential for and setback from ground rupture. Also of concern are structures, not for human occupancy, that can cause harm if damaged by an earthquake, such as utility, communications, and transportation lifelines. The County regulates most development projects within earthquake fault zones (Figure S-2). Projects include all land divisions and most structures for human occupancy. Before a project can be permitted within an A-P Earthquake Fault Zone, County Fault Zone, or within 150 feet of any other potentially active or active fault mapped in published United States Geological Survey (USGS) or California Division of Mining and Geology (CDMG) reports, a geologic investigation must demonstrate that proposed buildings will not be constructed across active faults.</SPAN></SPAN></P><P STYLE="font-size:16ptmargin:7 0 7 0;"><SPAN><SPAN>Updated 2/2016 with Thermal and Indio California Geologic Survey Quads</SPAN></SPAN></P><P><SPAN><SPAN /></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
Copyright Text: USGS, California Division of Mining and Geology
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>Government Code 51175-89 directs the California Department of Forestry and Fire Protection (CAL FIRE) to identify areas of very high fire hazard severity zones within Local Responsibility Areas (LRA). Mapping of the areas, referred to as Very High Fire Hazard Severity Zones (VHFHSZ), is based on data and models of, potential fuels over a 30-50 year time horizon and their associated expected fire behavior, and expected burn probabilities to quantify the likelihood and nature of vegetation fire exposure (including firebrands) to buildings. Details on the project and specific modeling methodology can be found at </SPAN></SPAN><A href="http://frap.cdf.ca.gov/projects/hazard/methods.html"><SPAN><SPAN>http://frap.cdf.ca.gov/projects/hazard/methods.html</SPAN></SPAN></A><SPAN><SPAN>. Local Responsibility Area VHFHSZ maps were initially developed in the mid-1990s and are now being updated based on improved science, mapping techniques, and data. This specific geographic information system dataset depicts final CAL FIRE recommendations for Very High FHSZs within the local jurisdiction. The process of finalizing these boundaries involved an extensive local review process, the details of which are available at </SPAN></SPAN><A href="http://frap.cdf.ca.gov/projects/hazard/btnet/"><SPAN><SPAN>http://frap.cdf.ca.gov/projects/hazard/btnet/ </SPAN></SPAN></A><SPAN><SPAN>(click on "Continue as guest without logging in"). Local government has 120 days to designate, by ordinance, very high fire hazard severity zones within its jurisdiction after receiving the recommendation. Local government can add additional VHFHSZs. There is no requirement for local government to report their final action to CAL FIRE when the recommended zones are adopted. Consequently, users are directed to the appropriate local entity (county, city, fire department, or Fire Protection District) to determine the status of the local fire hazard severity zone ordinance. To display the areas of VHFHSZ recommended by CAL FIRE, simply display on the attribute HAZ_CLASS, as that has been filtered to represent only areas in the Very High Class, and only for areas that are in Local Responsibility Area (LRA) status.</SPAN></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
Copyright Text: CAL FIRE recoginzes the important contribution of various local government entities that contributed data, maps, and comments that were critical components of the FHSZ mapping process.
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Current General Plan Land Use for Riverside County. </SPAN><SPAN>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. </SPAN><SPAN><SPAN>Data was spatially adjusted in 2020. </SPAN></SPAN></P><P><SPAN /></P><P><SPAN /></P></DIV></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
Copyright Text: Riverside County Planning Department
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 0 0;"><SPAN>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.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>This data set of polygon features represents Riverside County's liquefaction zones.</SPAN></SPAN></P><P><SPAN>ZONE: Internal attribute</SPAN></P><P><SPAN>SUSCEPTIBILITY: Generalized description of liquefaction susceptibility</SPAN></P><P><SPAN>DEFINITION_1: General description field</SPAN></P><P><SPAN>DEFINITION_2: General description field</SPAN></P><P><SPAN>DEFINITION_3: General description field </SPAN></P><P><SPAN>DEFINITION_4: General description field</SPAN></P><P><SPAN /></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 0 0;"><SPAN>2020 Spatial Adjustment</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /></P><P STYLE="margin:0 0 0 0;"><SPAN>This is the boundary layer of the Mulit-Species Habitat Conservation Plan (MSHCP). Western MSHCP boundary also used for Western MSHCP Open Space Fee Area. Per Ord. 810, Sec 8.</SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN>Section 8. Western Riverside County Multiple Species Habitat Conservation Plan Fee Area Boundary. The boundary of the Western Riverside County Multiple Species Habitat Conservation Plan Fee Area is the same as the MSHCP boundary as set forth in that document entitled MSHCP Plan Area Map dated June 2003, which is on file with the Clerk of the Board.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>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.</SPAN></P><P><SPAN>*Updated 08/22/2012 with parks from City of Riverside, Moreno Valley, and Riverside vicinity. P.Kang</SPAN></P><P><SPAN>Park name corrections and additional parks added 6/2014. Mickey Zolezio</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>This layer contains the activities, projects, and developments that are entered into the Public Land Use System (PLUS).</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>APN: Assessor parcel number associated with permit</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>CASE_ID: PLUS permit name</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>CASE_DESCR: Description of permitted activity</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>CASE_MODULE: The PLUS module that originated the permit</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>CASE_TYPE: The type of case</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>CASE_WORK_CLASS: A sub-type of the CASE_TYPE</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>DEPARTMENT: County department issuing permit</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>CASE_STATUS: Permit status</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>APPLIED_DATE: Date of permit application</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>APPROVED_DATE: Date of permit approval</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>COMPLETED_DATE: Date of permitted activity completion</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>EXPIRED_DATE: Date of permit expiration</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>RECORDED_PAGE: The recorded map type, book and page number</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>SUBDIVISION_NAME: Subdivision or development name</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>LOT: Lot number</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>BLOCK: Internal attribute</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>BUILDING_COUNT: The number of buildings</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>UNIT_COUNT: The number of the units</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>FLOOR_COUNT: Number of floors for assessed structure</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>HEIGHT: The height of the structure</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>FCC_CODE: Internal attribute</SPAN></SPAN></P><P /><DIV><P><SPAN /></P></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>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.</SPAN></SPAN></P><P><SPAN><SPAN /></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 0 0;"><SPAN>The PUBLIC_SITES data layer is used to identify the locations of Agricultural Commission, Animal Services, Assessor, Clerk, Recorder, Auditor, Board of Supervisors, Clerk of Board, Child Support Services, Cityhall, Community Health Agency, County Administration, County Counsel, District Attorney, DMV, EDA, Environment Health, Executive Office, Facilities Management, Fire Emergency Services, Fire Stations, Fleet Services, Flood Control, Hospitals, Human Resources, HR, Information Technology, IT, Library, Mental Health, Metrolink, Museum, Police, Probation, Public Defender, Public Social Services, Regional Parks, Registrar of Voters, Vote, Voting, Sheriff, Superior Court, Transportation and Land Management Agency, TLMA, Treasurer, Tax Collector, Veterans Services, and Waste Management.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>This data set of line feature represents Riverside County's railroads.</SPAN></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>This data set of polygon features represents Riverside County's Road and Bridge Benefit Districts. There are 4 Road and Bridge Benefit Districts within the county. Fees are assessed on new development projects to provide funding for road and bridge improvements within each district. </SPAN><SPAN>2020 Spatial Correction</SPAN></SPAN></P><P><SPAN>DISTRICT_NAME: Name of district</SPAN></P><P><SPAN>ACREAGE: Acreage of district</SPAN></P><P><SPAN>DISTRICT_ZONE: Zone designation for District</SPAN></P><P><SPAN>DISTRICT_NAME_ZONE: Concatenated field combining DISTRICT_NAME & DISTRICT_ZONE.</SPAN></P><P><SPAN /><SPAN /></P><P><SPAN /><SPAN /></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>This data set of polygon features represents Riverside County's school districts. Layer was provided by Riverside County Office of Education (RCOE).Data was spatially adjusted in 2020.</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>Last updated 2/2020</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN /></P><P STYLE="margin:0 0 7 0;"><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>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.</SPAN></P></DIV></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
Copyright Text: Riverside County Planning Department
Description: <DIV STYLE="text-align:Left;"><P STYLE="font-size:16ptmargin:7 0 7 0;"><SPAN><SPAN>This data set of polygon features represents Stephen's Kangaroo Rat habitat within Riverside County. See attached documentation for habitat classification descriptions.</SPAN></SPAN></P><DIV><P><SPAN /></P></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This data set of polygon features represents the Stephen's Kangaroo Rat plan and fee area within Riverside County. Data was spatially adjusted in 2020. </SPAN></P><P /><P><SPAN><SPAN /></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><P STYLE="font-size:16ptmargin:7 0 7 0;"><SPAN><SPAN>This data set of polygon features represents Stephen's Kangaroo Rat core reserves within Riverside County.</SPAN></SPAN></P><DIV><P><SPAN /></P></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN STYLE="font-size:12pt">2020 Spatial Adjustment</SPAN></P><P><SPAN><SPAN>The Transportation Uniform Mitigation Fee is supposed to make up for the shortfall of funds necessary for the transportaton needs of communities in CVAG and WRCOG.</SPAN></SPAN></P><P><SPAN>Boundaries were updated per WRGOG 3/14/2022. Spatial Adjustment may be needed. There is currently an overlap between the Southwest zone and the San Jacinto zone. This will be corrected per WRCOG.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Depicts areas in Riverside County desingated as Indian Lands, based on the Public Land Survey System to align with the Township, Range, and Sections as they are described. </SPAN></P><P><SPAN>Data was downloaded from the Bureau of Indian Affairs (BIA) website, then clipped with Riverside County boundaries. Please note that some tribal lands go beyond Riverside County boundaries. </SPAN></P><P><SPAN>Data was last confirmed on 10/1/2015 and processed by RCIT-GIS, Emily Lee.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
Copyright Text: The Bureau of Indian Affairs (BIA) Pacific Regional Office, RCIT-GIS
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>This layer contains the Township and Range data for the County of Riverside.</SPAN></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>These polygons represent Western Riverside County's Vegetation types. It was originally obtained from WRCOG and produced by KTUA consultants. Source date approx. 1994. RBF consultants made minor updates through field verification.</SPAN></SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>This data set of polygon features represents Riverside County's water bodies.</SPAN></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>This data set of polygon feature represents Riverside County's water district. Data was spatially adjusted in 2020.</SPAN></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Minor water districts provide services to local communities and operate within the boundaries of larger "major" water districts. Data was spatially adjusted in 2020.</SPAN></P><P><SPAN><SPAN>Updated by:</SPAN></SPAN></P><P><SPAN>Mickey Zolezio 7/2015</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>Watersheds were derived from data directly received from the State of California. The coverage shows Watershed boundaries as defined by the State Water Resources Control Board.</SPAN></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>Area plan subunits for the MSHCP Criteria Area.</SPAN></SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>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.</SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>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.</SPAN></P><P><SPAN>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. </SPAN></P><P><SPAN>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. </SPAN></P><P><SPAN>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.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>Criteria Area Species Survey Areas</SPAN></SPAN></P><P><SPAN>Species of Concern Area ID:</SPAN></P><P><SPAN>Area 1: Brodiaea filifolia, Atriplex serenana var.davidsonil, Atriplex parishii, Centromadia pungens ssp laevis, Erodium macrophyllum, Lasthenia glabrata var.coulter, Myosurus minimus</SPAN></P><P><SPAN>Area 2: Atriplex coronata var. natatior, Atriplex parishii, Atriplex serenana var. davidsonii, Brodiaea filifolia, Erodium macrophyllum, Centromadia pengens ssp. laevis, Lasthenia glabrata var. coulteri, Myosurus minimus</SPAN></P><P><SPAN>Area 3: Atriplex cononata var. natatior, Atriplex parishii, Atriplex serenana var. davidsonii, Brodiaea filifolia, Centromadia pungens ssp. laevis, Erodium macrophyllum, Lasthenia glabrata ssp. couteri, Myosurus minimus, Nama stenocarpum</SPAN></P><P><SPAN>Area 3a (9): Atriplex coronata var. natatior, Atriplex parishii, Atriplex serenana var. davidsonii, Brodiaea filifolia, Centromadia pungens ssp. laevis, Erodium macrophyllum, Lasthenia glabrata ssp. couteri, Myosurus minimus, Nama stenocarpum</SPAN></P><P><SPAN>Area 4: Atriples serenana var. davidsonii, Atriplex parishii, Brodiaea filifolia, Centromadia pungens ssp. laevis, Erodium macrophyllum, Lasthenia glabrata ssp. coulteri, Myosurus minimus</SPAN></P><P><SPAN>Area 5: Berberis nevinii, Ceanothus ophiochilus, Erodium macrophyllum</SPAN></P><P><SPAN>Area 6: Berberis nevinii, Centromadkia pungens var. laevis, Erodium macrophyllum</SPAN></P><P><SPAN>Area 7: Antriplex serenana var. davidsonii, Atriplex parishii, Erodium macrophyllum, Lasthenia glabrata var. couteri, Lepechinia cardiophylla, Navarretia prostrata</SPAN></P><P><SPAN>Area 8: Lepechinia cardiophylla</SPAN></P><P><SPAN>NOTE: There was a slight discrepancy between the display of these codes in the database as compared to the adopted map. Area 3a as identified on the map is designated as area 9 in the database. This metadata reflects the codes displayed on the adopted map.</SPAN></P><P><SPAN>NOTE: The County believes that these species reflect current information as described in the ERRATA to the MSHCP 8/9/2004, but has not formally received or accepted the data as a deliverabel.</SPAN></P><P><SPAN>This layer was named WRC_SSA_CASPC, and was changed to current name on 02/27/2015.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>ZIP Code boundaries were developed from street delivery 5-digit ZIP Codes. These polygons identify areas where mail is delivered (from a city block or two to a whole rural town).</SPAN></SPAN></P><P><SPAN><SPAN>ZIPCODE: Zip Code number</SPAN></SPAN></P><P><SPAN>NAME: Community name, per USPS.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN><SPAN>This is the Zoning polygon layer for planning purposes. Data was spatially adjusted in 2020. </SPAN></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Service Item Id: 2b902ed724f14f038681962e8cf6de1d
Copyright Text: Riverside County Planning Department