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: 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.
Service Item Id: 2132721bca3a44cd9f3ddad33f0be25d
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: 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.
Service Item Id: 2132721bca3a44cd9f3ddad33f0be25d
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: This feature class contains historic parcels (APNs) which are no long in the current PARCELS layer, as well as parcels from the latest close-of-roll.Last update: 08/2014Field information:APN - Assessor's Parcel NumberYEAR - Last time the parcel appears in PARCELS layer.
Value: Coachella Valley Stormwater Channel and Delta Conservation Area Label: Coachella Valley Stormwater Channel and Delta Conservation Area Description: N/A Symbol:
Value: Indio Hills/Joshua Tree National Park Linkage Conservation Area Label: Indio Hills/Joshua Tree National Park Linkage Conservation Area Description: N/A Symbol:
Description: This is a collection of dam inundation hazard areas for Riverside County. The sources of this data are Riverside County TLMA and the State of California's Office of Emergency Services. It is not a complete list.
Description: This data is intended for identifying the areas where a floodplain is located that is officially adopted for regulatory purposes under Ordinance 458 of Riverside County.District mapping is a combination of FEMA A-zone mapping, DWR Awareness Mapping, Colorado River 100-year by BLM, Flood Hazard Reports by USA-COE, and twelve additional special study areas by RCFC and one by CVWD. All regulatory floodplains are based on the estimated 100-year flood event. The NO BUILD and RESTRICTED areas are also regulatory floodplains with limitations defined case by case in additional to plain REGULATORY and are based on FEMA Defined Floodways and special study floodways by RCFC. All of these are officially adopted by the Board of Supervisors of Riverside County under Ordinance no. 458 codified as Chapter 15.80.
Service Item Id: 2132721bca3a44cd9f3ddad33f0be25d
Copyright Text: FEMA. Floodplain Management (FPM) Section, Regulatory Division, Riverside County Flood Control and Water Conservation District (RCFC &WCD) and Coachella Valley Water District (CVWD).
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center 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: 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.
Color: [0, 0, 0, 255] Background Color: [255, 255, 190, 255] Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: 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.
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Required attributes defined by EnerGov GIS Deployment Guidelines Spatial Collection point feature class.</SPAN></P><P><SPAN STYLE="font-weight:bold;">Name </SPAN><SPAN>- User defined name of the spatial collection.</SPAN></P><P><SPAN STYLE="font-weight:bold;">Description</SPAN><SPAN> - User defined description of the spatial collection.</SPAN></P><P><SPAN STYLE="font-weight:bold;">CreatedDate</SPAN><SPAN> - Date of spatial collection creation.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>Required attributes defined by EnerGov GIS Deployment Guidelines Spatial Collection point feature class.</SPAN></P><P><SPAN STYLE="font-weight:bold;">Name</SPAN><SPAN> - User defined name of the spatial collection.</SPAN></P><P><SPAN STYLE="font-weight:bold;">Description</SPAN><SPAN> - User defined description of the spatial collection.</SPAN></P><P><SPAN STYLE="font-weight:bold;">CreatedDate</SPAN><SPAN> - Date of spatial collection creation.</SPAN></P><P><SPAN /></P></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Required attributes defined by EnerGov GIS Deployment Guidelines Spatial Collection polygon feature class</SPAN></P><P><SPAN STYLE="font-weight:bold;">Name </SPAN><SPAN>- User defined name of the spatial collection.</SPAN></P><P><SPAN STYLE="font-weight:bold;">Description</SPAN><SPAN> - User defined description of the spatial collection.</SPAN></P><P><SPAN STYLE="font-weight:bold;">CreatedDate</SPAN><SPAN> - Date of spatial collection creation.</SPAN></P><P><SPAN /></P><P><SPAN /></P></DIV></DIV></DIV>
Description: Intersection points derived from the Centerline Feature Class. Used for locating Intersections programmatically using cross-street references.
Service Item Id: 2132721bca3a44cd9f3ddad33f0be25d
Copyright Text: Maintained by Richard Fairhurst of the Riverside County Transportation Department. Updated 06/28/2012.
Description: The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.
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.Maintained by Stella Spadafora, 06/04/12
Description: Using Assessor Book Boundaries as a building block; Assessor Books are grouped into regions within Riverside County based on office location.R = Riverside OfficeI = Indio OfficeT = Temecula OfficeWithin each region are numbered inspection areas.Schema:ASSESSOR_BOOK: Assessor Book BoundaryBUILDING_INSPECTION_AREA: Building & Safety inspection area.GRADING_INSPECTION_AREA: Larger areas specifically for inspecting grading permits.
Service Item Id: 2132721bca3a44cd9f3ddad33f0be25d
Copyright Text: TLMA, Building & Safety Department, RCIT
Description: BEAT: A NUMBER ASSIGNED TO AN INDIVIDUAL INSPECTOR. THE FIRST DIGIT REFERS TO THE SUPERVISOR DISTRICT. THERE IS ONLY ONE UNIQUE INSPECTOR PER BEAT.DISTRICT: SUPERVISOR DISTRICTOFFICE: THE OFFICE THAT THE INSPECTOR REPORTS TO.ASSESSOR BOOKS: LIST OF ASSESSOR BOOKS ENCOMPASSED BY THE BEAT BOUNDARY.
Description: TRACT: CENSUS TRACT NUMBER BLOCK_GROUP: CENSUS BLOCK GROUP NUMBERGEOID: CENSUS ID CONTAINING STATE, COUNTY, TRACT AND BLOCK GROUP NUMBERSCENSUS_DATE: DATE OF CENSUS DATA USED TO CREATE FEATUREFISCAL_YEAR: ACTIVE FISCAL YEAR
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Field Definition:</SPAN></P><P><SPAN STYLE="font-weight:bold;">EJC_NAME</SPAN><SPAN>= Environmental Justice Community Name.</SPAN></P><P><SPAN>DATA SOURCE: </SPAN></P><P><SPAN STYLE="font-weight:bold;">CalEnviroscreen 3.0 (CES) </SPAN><SPAN>represents a 2018 statewide analysis from the California Office of Environmental Health Hazard Assessment (OEHHA). Source Link: </SPAN><A href="https://oehha.ca.gov/calenviroscreen"><SPAN>https://oehha.ca.gov/calenviroscreen</SPAN></A></P><P><SPAN STYLE="font-weight:bold;">Cumulative Environmental Vulnerabilities Assessment (CEVA) </SPAN><SPAN>represents data from the Center for Regional Change at UC Davis. Their effors encompassed a County wide study and the report was published in June, 2013. Report Link: </SPAN><A href="https://regionalchange.ucdavis.edu/report/revealing-invisible-coachella-valley"><SPAN>https://regionalchange.ucdavis.edu/report/revealing-invisible-coachella-valley</SPAN></A></P><P><SPAN>The Environmental Justice Communities attribute information for Riverside County derived from the efforts of State and university research and analysis. Note, only attribute information from these sources were used. For spatial reference, census tract and census block group polygons were derived from the</SPAN><SPAN><SPAN>Census Bureau as released to the public in the form of TIGER/Line Shapefiles. Source Link: </SPAN><A href="https://www.census.gov:443/geographies/mapping-files/time-series/geo/tiger-line-file.html"><SPAN>https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-line-file.html</SPAN></A><SPAN>. </SPAN></SPAN></P></DIV></DIV></DIV>
Service Item Id: 2132721bca3a44cd9f3ddad33f0be25d
Copyright Text: US Census, California Office of Environmental Health Hazard Assessment (OEHHA), Center for Regional Change UC Davis, RCIT, Riverside County Planning Department.
Description: 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 http://frap.cdf.ca.gov/projects/hazard/methods.html. 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 http://frap.cdf.ca.gov/projects/hazard/btnet/ (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.
Service Item Id: 2132721bca3a44cd9f3ddad33f0be25d
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.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: STATION - FIRE STATIONBATTALION - ADMINISTRATIVE GROUP OF FIRE STATIONS UNDER BATTALION CHIEFDIVISION_NAME - ADMINISTRATIVE GROUP OF BATTALIONS UNDER DIVISION CHIEF
Service Item Id: 2132721bca3a44cd9f3ddad33f0be25d
Copyright Text: RCIT, RIVERSIDE COUNTY FIRE DEPT, FIREGIS
Description: Using Assessor Book Boundaries as a building block; Assessor Books are grouped into regions within Riverside County based on office location.R = Riverside OfficeI = Indio OfficeT = Temecula OfficeWithin each region are numbered inspection areas.Schema:ASSESSOR_BOOK: Assessor Book BoundaryBUILDING_INSPECTION_AREA: Building & Safety inspection area.GRADING_INSPECTION_AREA: Larger areas specifically for inspecting grading permits.
Service Item Id: 2132721bca3a44cd9f3ddad33f0be25d
Copyright Text: TLMA, Building & Safety Department, RCIT
Description: 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.
Description: Minor water districts provide services to local communities and operate within the boundaries of larger "major" water distircts.Updated by: Mickey Zoleizo 7/2015
Description: This polygon feature class represents the Riverside County Assessor Map Book Boundaries. It is created by dissolving the ASSESSOR_BOOKPAGE_BOUNDARY feature class based on its BOOK attributes.
Value: City of Corona (River Run Seniors Apartments);2002-1 Label: City of Corona (River Run Seniors Apartments), District 2002-1 Description: N/A Symbol:
Value: City of Lake Elsinore (City Center Townhomes);2005-6 Label: City of Lake Elsinore (City Center Townhomes), District 2005-6 Description: N/A Symbol:
Value: City of Lake Elsinore (Running Deer Estates);2006-8 Label: City of Lake Elsinore (Running Deer Estates), District 2006-8 Description: N/A Symbol:
Value: City of Lake Elsinore(City Center Townhomes);2004-1 Label: City of Lake Elsinore(City Center Townhomes), District 2004-1 Description: N/A Symbol:
Value: City of Murrieta (Meadowlane/Amberwalk I&II);2004-3 Label: City of Murrieta (Meadowlane/Amberwalk I&II), District 2004-3 Description: N/A Symbol:
Value: City of Palm Springs (Escena of Palm Springs);2005-2 Label: City of Palm Springs (Escena of Palm Springs), District 2005-2 Description: N/A Symbol:
Value: City of San Jacinto (Rancho San Jacinto Phase 2);2002-1 Label: City of San Jacinto (Rancho San Jacinto Phase 2), District 2002-1 Description: N/A Symbol:
Value: Jurupa Area Recreation & Park District (TR31496);2005-1 Label: Jurupa Area Recreation & Park District (TR31496), District 2005-1 Description: N/A Symbol:
Description: This is a polygon layer of the Riverside County's Development Agreement records. 01/07/2013, Update - DA No. 7 fee changed to reflect annual CPI(Consumer Price Index) adjustments. NAME: Name of development impact areaAREA_NUMBER: Area Plan number
Description: 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 http://frap.cdf.ca.gov/projects/hazard/methods.html. 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 http://frap.cdf.ca.gov/projects/hazard/btnet/ (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.
Service Item Id: 2132721bca3a44cd9f3ddad33f0be25d
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.
Value: TEMECULA VALLEY WINE COUNTRY EQUESTRIAN DISTRICT POLICY AREA Label: TEMECULA VALLEY WINE COUNTRY EQUESTRIAN DISTRICT POLICY AREA Description: N/A Symbol:
Value: TEMECULA VALLEY WINE COUNTRY RESIDENTIAL DISTRICT POLICY AREA Label: TEMECULA VALLEY WINE COUNTRY RESIDENTIAL DISTRICT POLICY AREA Description: N/A Symbol:
Value: TEMECULA VALLEY WINE COUNTRY WINERY DISTRICT POLICY AREA Label: TEMECULA VALLEY WINE COUNTRY WINERY DISTRICT POLICY AREA Description: N/A Symbol:
Value: TEMESCAL WASH POLICY AREA Label: TEMESCAL WASH POLICY AREA Description: N/A Symbol:
Description: This featire class only contains permits administered by the Building and Safety Department.This feature class is updated by a python script each morning from the previous day's building permits. The script is named BRS_UPDATE.py and is located in the //agency/agencydfs/Tran/Files/rfairhur/Python_Scripts directory. The original data is stored in the Plus_Conversion_Data.gdb file geodatabase in the //agency/agencydfs/Tran/Files/rfairhur/Layers/Plus_Conversion_Data directory.The fields in this feature class are:APN: Assessor parcel number(s) associated with each permitCASE_ID: PLUS permit numberCASE_DESCR: Description of permitted activityCASE_MODULE: The PLUS module in which the case located. All permits in this feature class are in the PERMIT module.CASE_TYPE: The PLUS case type category of the caseCASE_WORK_CLASS: The PLUS work class subcategory of the caseDEPARTMENT: County department issuing permit. For this feature class, all permits have a value of BLD for the Building and Safety Department.CASE_STATUS: The PLUS permit statusAPPLIED_DATE: Date of permit applicationAPPROVED_DATE: Date of permit approvalCOMPLETED_DATE: Date of permitted activity completionEXPIRED_DATE: Date of permit expirationRECORDED_PAGE: The Recorder's book and page number location of the recorded map that created the APNSUBDIVISION_NAME: The Subdivision Name of the recorded map, either per the Assessors or per the Tract/Lot field converted from LMS as of 11/30/2017.LOT: The Assessors Lot field value for the APNBLOCK: The Assessors Block field value for the APNBUILDING_COUNT: The number of buildings covered by the permitUNIT_COUNT: The number of residential, commmercial or industrial units covered by the permit as assigned by the Building and Safety Department.FLOOR_COUNT: The number of floors in the building covered by the permitHEIGHT: The height of the (tallest) building covered by the permitFCC_CODE: Internal attributeBLD_TRACT: The Tract that created or will create the lot the building permit is located withinBLD_LOT: The Lot of the BLD_TRACT that contains or will contain the building permitNEW_APN: When available, the new APN used to replace the shape of the permit after maps have recorded.UNIT_STATS_COUNT: The TRANS_PLUS_RESIDENTIAL_PERMITS_STATS feature class uses this column of unit counts for the statistics it summarizes. This field is primarily maintained for counting BRS permits primary dwelling units, and excludes permits for Second Units, Casitas, Pool Houes, Guest Quarters and duplicate unit values on any multi-parcel permit from being countedLOCATION: General location of permitted activityMODEL_NUMBER: When available, the Model or Plan number of the residential permit. Parsed from CASE_DESCR when available.
Value: TEMECULA VALLEY WINE COUNTRY EQUESTRIAN DISTRICT POLICY AREA Label: TEMECULA VALLEY WINE COUNTRY EQUESTRIAN DISTRICT POLICY AREA Description: N/A Symbol:
Value: TEMECULA VALLEY WINE COUNTRY RESIDENTIAL DISTRICT POLICY AREA Label: TEMECULA VALLEY WINE COUNTRY RESIDENTIAL DISTRICT POLICY AREA Description: N/A Symbol:
Value: TEMECULA VALLEY WINE COUNTRY WINERY DISTRICT POLICY AREA Label: TEMECULA VALLEY WINE COUNTRY WINERY DISTRICT POLICY AREA Description: N/A Symbol:
Value: TEMESCAL WASH POLICY AREA Label: TEMESCAL WASH POLICY AREA Description: N/A Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center 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: bottom Horizontal Alignment: center 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: bottom Horizontal Alignment: center 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: Approved General Plan Circulation Element as adopted by the Board of Supervisors, October 7, 2003. This dataset represents the ultimate right of way of Riverside County's Integrated Plan Circulation Element.
Service Item Id: 2132721bca3a44cd9f3ddad33f0be25d
Copyright Text: Transportation TLMA Riverside County
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.
Description: 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.
Description: 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.
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.