The Cahuilla Valley and Terwilliger Valley groundwater basins, 9-006 and 7-026 respectively (California Department of Water Resources 2016) located approximately 25 miles southwest of Palm Springs, are the sole-source for groundwater supply for the rural disadvantaged community and two Native American Tribes, the Ramona Band of Cahuilla and the Cahuilla. The characteristics and sustainable yield of the Cahuilla Valley and Terwilliger Valley groundwater basins are not well understood and are threatened by increasing water use and potential changes in water sustainability related to climate change. Previous USGS studies of the Cahuilla-Terwilliger Valley groundwater basins defined the thicknesses and characteristics of the alluvial sediments that constitute the main water-bearing unit of the aquifer system and identified where wells completed in the underlying fractured bedrock are located (Moyle, 1976; Landon and others, 2015; Woolfenden and Bright, 1988). However, although the fractured bedrock is an important part of the aquifer system for domestic and some irrigation supply, the thickness and hydraulic characteristics of the fractured bedrock are not well understood (Landon and others, 2015; Moyle 1976). Existing gravity data identified a possible conduit for groundwater flow beneath Cahuilla Creek in the Cahuilla and Durasno Valleys (Landon and others, 2015). Electrical resistivity tomography (ERT) data was collected in August 2018 to evaluate the cross-sectional depth to bedrock underlying a narrow section of Durasno Valley, and to help select locations for groundwater monitoring wells. Data from two transects were collected perpendicular to Cahuilla Creek, and offset by approximately 600 meters (m).

This layer contains the Township and Range data for the County of Riverside.

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.

Riverside County 2019 images. 6 inch resolution. Projected to California State Plane Zone VI.

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

© TLMA GIS

This layer is a component of TransportationFeatures.

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, 05/2015

© RCIT GIS, LAFCO

This layer is a component of Administrative Boundaires.

This Digital Raster Graphic (DRG) was created using scanned U.S. Geological Survey 7.5-minute 1 to 24,000 scale maps georeferenced in Universal Transverse Mercator (UTM) grid. DRGs can be acquired with or without collar information for use in Geographic Information System (GIS) environment. Collarless DRGs can be edge matched creating a continuous collection of topographic maps.

CDFW BIOS GIS Dataset, Contact: Karyn L Drennen, Description: The Biological Monitoring Program is a part of the Western Riverside County Multi-Species Habitat Conservation Plan (MSHCP), which was permitted in June, 2004. The Monitoring Program monitors the status of 146 Covered Species within a designated Conservation Area to provide information to permittees, land managers, the public, and wildlife agencies (i.e., the California Department of Fish and Wildlife and the U.S. Fish and Wildlife Service).

The TIGER/Line shapefiles and related database files (.dbf) 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 shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

The California Department of Fish and Game (CDFG) contracted with the California Native Plant Society (CNPS) and Aerial Information Systems (AIS) to produce an alliance-level, vegetation classification and map of Western Riverside County, California. The resulting classification and map products will be used to help establish a monitoring basis for the vegetation and habitats of the Western Riverside County Multi-Species Habitat Conservation Plan (MSHCP). The plan aims to conserve over 500,000 acres of land out of the 1.26 million acre total. This area is the largest MSHCP ever attempted and is an integral piece of the network of Southern California Habitat Conservation Plans and Natural Community Conservation Planning (Dudek 2001, Dudek 2003). Riverside County is one of the fastest growing counties in California, as well as one of the most biodiverse counties in the United States. A wide array of habitats are found within the non-developed lands in Western Riverside County, including coastal sage scrub, vernal pools, montane coniferous forest, chaparral, foothill woodland, annual grassland, and desert. In the CNPS contract, vegetation resources were assessed quantitatively through field surveys, data analysis, and final vegetation classification. Field survey data were analyzed statistically to come up with a floristically-based classification. Each vegetation type sampled was classified according to the National Vegetation Classification System to the alliance level (and association level if possible). The vegetation alliances were described floristically and environmentally in standard descriptions, and a final key was produced to differentiate among 101 alliances, 169 associations, and 3 unique stands (for final report, see https://nrm.dfg.ca.gov/FileHandler.ashx?DocumentID=18245). In a parallel but separate effort by AIS (as reported in this dataset), vegetation mapping was undertaken through interpretation of ortho-rectified, aerial photographs for vegetation signatures in color infrared (CIR) and in natural color (imagery flown in winter or summer). A detailed map has been produced through the following process: 1) hand-delineation of polygons on base CIR imagery, 2) digitization of polygons, and 3) attribution of the vegetation types and overstory cover values. The map was created in a Geographic Information System (GIS) digital format, as was the database of field surveys. The dataset was produced through an on-screen photo interpretation procedure using three sets of geo-referenced imagery. The data is classified to a floristic classification derived through clustering analysis procedures based on species dominance and significance. The classification is based on the MCV (Manual of California Vegetation) in which 103 alliances and 169 floristic associations have been defined for the study area. Over 3300 full plot and reconnaissance points have been used in helping classify the mapped polygons. Mapped polygons are classified to either an association, alliance or mapping unit which may be an aggregation of associations or alliances. The dataset encompasses the western portions of Riverside County from the county boundary on the west eastward to the summit of the San Jacinto Mountains and Anza valley.

Riverside County 2007 imagery. 1 foot resolution. Projected to California State Plane Zone VI.

Geospatial data about Riverside County, CA Zipcodes. Export to CAD, GIS, PDF, CSV and access via API.

Riverside County 2011 images. 1 foot resolution. Projected to Web Mercator.

Riverside County 2012 images. 1 foot resolution. Projected to Web Mercator.

CDFW BIOS GIS Dataset, Contact: Lynn Sweet, Description: This map is one in a series of vegetation maps produced by the University of California, Riverside Center for Conservation Biology (UCR CCB) for the Coachella Valley Multiple Species Habitat Conservation Plan. UCR CCB created a fine-scale vegetation map of the Dos Palmas Conservation Area (Reserve Management Unit 4 under the Plan) that covers approximately 25,800 acres in the Coachella Valley of Riverside County, California.

To show the adjacent counties of the County of Riverside, CA.

Riverside County 2020 images, 6 inch and 3 inch resolution. Projected to Web Mercator.

Data was spatially adjusted in 2020. CSA_NUMBER: The CSA numberNAME: Name of CSASUBZONE: Wine Country referenceST_LIGHTING: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"ST_SWEEPING: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"PARK_REC: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"FIRE_PROTECT: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"SEWER: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"WATER: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"TRASH: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"ROAD_MAINT: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"FLOOD_CTRL: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"POLICE: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"DRAINAGE_CTRL: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"LIBRARY: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"LANDSCAPING: "Y" or "N" to denote if CSA funds activity. Blank is an assumed "N"SPHERE_NUMBER: Not used

Geospatial data about Adams County, Illinois Zoning. Export to CAD, GIS, PDF, CSV and access via API.

The data set for the Corona South 7.5' quadrangle was prepared under the U.S. Geological Survey Southern California Areal Mapping Project (SCAMP) as part of an ongoing effort to develop a regional geologic framework of southern California, and to utilize a Geographic Information System (GIS) format to create regional digital geologic databases. These regional databases are being developed as contributions to the National Geologic Map Database of the National Cooperative Geologic Mapping Program of the USGS.

This data set maps and describes the geology of the Corona South 7.5' quadrangle, Riverside and Orange Counties, California. Created using Environmental Systems Research Institute's ARC/INFO software, the data base consists of the following items: (1) a map coverage containing geologic contacts and units, (2) a coverage containing structural data, (3) a coverage containing geologic unit annotation and leaders, and (4) attribute tables for geologic units (polygons), contacts (arcs), and site-specific data (points). In addition, the data set includes the following graphic and text products: (1) a postscript graphic plot-file containing the geologic map, topography, cultural data, a Correlation of Map Units (CMU) diagram, a Description of Map Units (DMU), and a key for point and line symbols, and (2) PDF files of the Readme (including the metadata file as an appendix), and the graphic produced by the Postscript plot file.

The Corona South quadrangle is located near the northern end of the Peninsular Ranges Province. Diagonally crossing the quadrangle is the northern end of the Elsinore Fault zone, a major active right-lateral strike-slip fault zone of the San Andreas Fault system. East of the fault zone is the Perris block and to the west the Santa Ana Mountains block. Basement in the Perris block part of the quadrangle is almost entirely Cretaceous volcanic rocks and granitic rocks of the Cretaceous Peninsular Ranges batholith. Three small exposures of very low metamorphic grade siliceous rocks correlated on the basis of lithology with Mesozoic age rocks are located near the eastern edge of the quadrangle. Exposures of batholithic rocks is restricted to mostly granodiorite of the Cajalco pluton that underlies extensive areas to the east and north. There are limited amounts of undifferentiated granitic rock and one small body of gabbro. The most extensive basement rocks are volcanic shallow intrusives and extrusives of the Estelle Mountain volcanics. The volcanics, predominantly latite and rhyolite, are quarried as a source of crushed rock.

West of the Elsinore Fault zone is a thick section of Bedford Canyon Formation of Jurassic age. This unit consists of incipiently metamorphosed marine sedimentary rocks consisting of argillite, slate, graywacke, impure quartzite, and small pods of limestone. Bedding and other primary sedimentary structures are commonly preserved and tight folds are common. Incipiently developed transposed layering, S1, is locally well developed. Included within the siliceous rocks are small outcrops of fossiliferous limestone than contain a fauna indicating the limestone formed in a so-called black smoker environment. Unconformably overlying and intruding the Bedford Canyon Formation is the Santiago Peak Volcanics of Cretaceous age. These volcanics consist of basaltic andesite, andesite, dacite, rhyolite, breccia and volcanoclastic rocks. Much of the unit has been hydrothermally altered; the alteration was contemporaneous with the volcanism. A minor occurrence of serpentine and associated silica-carbonate rock occurs in association with the volcanics.

Sedimentary rocks of late Cretaceous and Paleogene age and a few Neogene age rocks occur within the Elsinore Fault zone. Marine sandstone of the middle Miocene Topanga Formation occurs within the fault zone southeast of Corona. Underlying the Topanga Formation is the nonmarine undivided Sespe and Vaqueros Formation that are predominantly sandstone. Sandstone, siltstone, and conglomerate of the marine and nonmarine Paleocene Silverado Formation extends essentially along the entire length of the fault zone in the quadrangle. Clay beds in the Silverado Formation have been an important source of clay. In the northwest corner of the quadrangle is a thick, faulted, sedimentary section that ranges in age from Cretaceous to early Pliocene-Miocene.

Emanating from the Santa Ana Mountains is an extensive alluvial fan complex that underlies Corona and the surrounding valleys. This fan complex includes both Pleistocene and Holocene age deposits.

The Elsinore Fault zone at the base of the Santa Ana Mountains splays in the northwestern part of the quadrangle; beyond the quadrangle boundary the name Elsinore Fault is generally not used. The southern splay takes a more western trend and to the west of the quadrangle is termed the Whittier Fault, a major active fault. The eastern splay continues on strike along the east side of the Chino (Puente) Hills north of the quadrangle where it is termed the Chino Fault. The Chino Fault appears to have very limited displacement.

The geologic map data base contains original U.S. Geological Survey data generated by detailed field observation recorded on 1:24,000 scale aerial photographs. The map was created by transferring lines from the aerial photographs to a 1:24,000 scale topographic base. The map was digitized and lines, points, and polygons were subsequently edited using standard ARC/INFO commands. Digitizing and editing artifacts significant enough to display at a scale of 1:24,000 were corrected. Within the database, geologic contacts are represented as lines (arcs), geologic units are polygons, and site-specific data as points. Polygon, arc, and point attribute tables (.pat, .aat, and .pat, respectively) uniquely identify each geologic datum.