City and town boundaries for the purpose of establishing election divisions within a district. Created April 16, 2021. The districts contained within this dataset only represent districts that conduct an election. This dataset may not contain all districts within San Bernardino County. This dataset should only be used for the purpose of establishing election divisions within a district. It will be removed once the redistricting process has concluded.

This data contains both the Cities and Communities in San Bernardino County. Data is current as of December 2024. For questions about this dataset, please email opendata@isd.sbcounty.gov.

The [21-482] City of San Bernardino Review Map is a Web Map used in SBCTA analysis. It includes 3 distinct layers.

San Bernardino County City Limits current as of November 29, 2023.City limit boundaries are maintained through maps of annexations and detachments by the County of San Bernardino Surveyor's Office. City Limits GIS data stores non-contiguous city polygons as individual polygons. For questions about this dataset, please email opendata@isd.sbcounty.gov.This dataset contains the boundaries of incorporated areas (cities and towns) in San Bernardino County, created from the Cities and Communities feature service.

San Bernardino County City Limits current as of December 17, 2024.City limit boundaries are maintained through maps of annexations and detachments by the County of San Bernardino Surveyor's Office. City Limits GIS data stores non-contiguous city polygons as individual polygons. For questions about this dataset, please email opendata@isd.sbcounty.gov.This feature service will be retired soon and will no longer be updated with the latest changes. To ensure you always get the latest updates, please instead point your maps and apps to use the Cities and Towns (Incorporated Areas) feature layer.

Polygon Feature Layer used in SBCTA analysis. This layer's spatial reference is NAD_1983_StatePlane_California_V_FIPS_0405_Feet. It also has 10 fields. Fields include the following:OBJECTID: OIDSQ_MILES: DoubleACRES: DoubleREGION: StringCITY_NAME: Stringwebsite: StringCITY: StringGlobalID: GlobalIDShape_Area: DoubleShape_Length: Double

The San Bernardino County map viewer is a collection of maps and apps related to various administrative boundaries in San Bernardino County. All data is publicly available. The San Bernardino County map viewer contains the following maps:Parcels: Find and identify parcels by APN or address.Flood Control: Find and identify Flood Control facilities within San Bernardino CountyBoundaries: Explore various administrative boundaries in San Bernardino County, such as Supervisor districts, city limits, US Senate districts and moreHistorical Imagery: Imagery archives for the years 2008 - 2023Power Outages: Power outage data from CalOES showing power outages within San Bernardino County3D Scene: Interactively explore San Bernardino County geographic data in 3D.DIY Map Viewer: Create your own map using a variety of provided datasets, or add your ownThe San Bernardino County Map viewer was created by San Bernardino County's Information Services Department. For more information please contact the Information Services Department (ISD) Help Desk at (909)884-4884.

U.S. Census Bureau QuickFacts statistics for San Bernardino city, California. QuickFacts data are derived from: Population Estimates, American Community Survey, Census of Population and Housing, Current Population Survey, Small Area Health Insurance Estimates, Small Area Income and Poverty Estimates, State and County Housing Unit Estimates, County Business Patterns, Nonemployer Statistics, Economic Census, Survey of Business Owners, Building Permits.

This shapefile contains tax rate area (TRA) boundaries in San Bernardino County for the specified assessment roll year. Boundary alignment is based on the 2010 county parcel map. A tax rate area (TRA) is a geographic area within the jurisdiction of a unique combination of cities, schools, and revenue districts that utilize the regular city or county assessment roll, per Government Code 54900. Each TRA is assigned a six-digit numeric identifier, referred to as a TRA number. TRA = tax rate area number

The City of San Bernardino, CA Opportunity Site is a Web Map used in SBCTA analysis. It includes 3 distinct layers.

To download:1. Click the Download button above.2. A side panel will appear showing download options. Under Shapefile, click the Download button.3. When the download completes, browse to the location of the downloaded .zip, copy it to the location where you manage your redistricting files, then right-click to extract the contents. You will then be able to use the file in GIS software.If, rather than downloading the data, you wish the reference online versions of these datasets directly to ensure you are always using the most up-to-date data, please contact the County of San Bernardino Innovation and Technology Departments at 909-884-4884 or by emailing OpenData@isd.sbcounty.gov for informations and instructions for doing so.This dataset should only be used for the purpose of establishing election divisions within a district. It will be removed once the redistricting process has concluded.

Urban heat islands are small areas where temperatures are unnaturally high - usually due to dense buildings, expansive hard surfaces, or a lack of tree cover or greenspace. People living in these communities are exposed to more dangerous conditions, especially as daytime high and nighttime low temperatures increase over time. NOAA Climate Program Office and CAPA Strategies have partnered with cities around the United States to map urban heat islands. Using Sentinel-2 satellite thermal data along with on-the-ground sensors, air temperature and heat indexes are calculated for morning, afternoon, and evening time periods. The NOAA Visualization Lab, part of the NOAA Satellite and Information Service, has made the original heat mapping data available as dynamic image services.Dataset SummaryPhenomenon Mapped: heat indexUnits: degrees Fahrenheit Cell Size: 30 metersPixel Type: 32 bit floating pointData Coordinate Systems: WGS84 Mosaic Projection: WGS84 Extent: cities within the United StatesSource: NOAA and CAPA StrategiesPublication Date: September 20, 2021What can you do with this layer?This imagery layer supports communities' UHI spatial analysis and mapping capabilities. The symbology can be manually changed, or a processing template applied to the layer will provide a custom rendering. Each city can be queried.Related layers include Morning Heat Index and Evening Heat Index. Cities IncludedBoulder, CO Brooklyn, NY Greenwich Village, NY Columbia, SC Columbia, MO Columbus, OH Knoxville, TN Jacksonville, FL Las Vegas, NV Milwaukee, WI Nashville, TN Omaha, NE Philadelphia, PA Rockville, MD Gaithersburg, MD Takoma Park, MD San Francisco, CA Spokane, WA Abingdon, VA Albuquerque, NM Arlington, MA Woburn, MA Arlington, VA Atlanta, GA Charleston, SC Charlottesville, VA Clarksville, IN Farmville, VA Gresham, OR Harrisonburg, VA Kansas City, MO Lynchburg, VA Manhattan, NY Bronx, NY Newark, NJ Jersey City, NJ Elizabeth, NJ Petersburg, VA Raleigh, NC Durham, NC Richmond, VA Richmond, IN Salem, VA San Diego, CA Virginia Beach, VA Winchester, VA Austin, TX Burlington, VT Cincinnati, OH Detroit, MI El Paso, TX Houston, TX Jackson, MS Las Cruces, NM Miami, FL New Orleans, LA Providence, RI Roanoke, VA San Jose, CA Seattle, WA Vancouver, BC Canada Boston, MA Fort Lauderdale, FL Honolulu, HI Boise, ID Nampa, ID Los Angeles, CA Yonkers, NY Oakland, CA Berkeley, CA San Juan, PR Sacramento, CA San Bernardino, CA Victorville, CA West Palm Beach, FL Worcester, MA Washington, D.C. Baltimore, MD Portland, ORCities may apply to be a part of the Heat Watch program through the CAPA Strategies website. Attribute Table Informationcity_name: Afternoon Heat Index Observations in Floating-Point (°F)

Urban heat islands are small areas where temperatures are unnaturally high - usually due to dense buildings, expansive hard surfaces, or a lack of tree cover or greenspace. People living in these communities are exposed to more dangerous conditions, especially as daytime high and nighttime low temperatures increase over time. NOAA Climate Program Office and CAPA Strategies have partnered with cities around the United States to map urban heat islands. Using Sentinel-2 satellite thermal data along with on-the-ground sensors, air temperature and heat indexes are calculated for morning, afternoon, and evening time periods. The NOAA Visualization Lab, part of the NOAA Satellite and Information Service, has made the original heat mapping data available as dynamic image services.Dataset SummaryPhenomenon Mapped: heat indexUnits: degrees Fahrenheit Cell Size: 30 metersPixel Type: 32 bit floating pointData Coordinate Systems: WGS84 Mosaic Projection: WGS84 Extent: cities within the United StatesSource: NOAA and CAPA StrategiesPublication Date: September 20, 2021What can you do with this layer?This imagery layer supports communities' UHI spatial analysis and mapping capabilities. The symbology can be manually changed, or a processing template applied to the layer will provide a custom rendering. Each city can be queried.Related layers include Afternoon Heat Index and Evening Heat Index. Cities IncludedBoulder, CO Brooklyn, NY Greenwich Village, NY Columbia, SC Columbia, MO Columbus, OH Knoxville, TN Jacksonville, FL Las Vegas, NV Milwaukee, WI Nashville, TN Omaha, NE Philadelphia, PA Rockville, MD Gaithersburg, MD Takoma Park, MD San Francisco, CA Spokane, WA Abingdon, VA Albuquerque, NM Arlington, MA Woburn, MA Arlington, VA Atlanta, GA Charleston, SC Charlottesville, VA Clarksville, IN Farmville, VA Gresham, OR Harrisonburg, VA Kansas City, MO Lynchburg, VA Manhattan, NY Bronx, NY Newark, NJ Jersey City, NJ Elizabeth, NJ Petersburg, VA Raleigh, NC Durham, NC Richmond, VA Richmond, IN Salem, VA San Diego, CA Virginia Beach, VA Winchester, VA Austin, TX Burlington, VT Cincinnati, OH Detroit, MI El Paso, TX Houston, TX Jackson, MS Las Cruces, NM Miami, FL New Orleans, LA Providence, RI Roanoke, VA San Jose, CA Seattle, WA Vancouver, BC Canada Boston, MA Fort Lauderdale, FL Honolulu, HI Boise, ID Nampa, ID Los Angeles, CA Yonkers, NY Oakland, CA Berkeley, CA San Juan, PR Sacramento, CA San Bernardino, CA Victorville, CA West Palm Beach, FL Worcester, MA Washington, D.C. Baltimore, MD Portland, ORCities may apply to be a part of the Heat Watch program through the CAPA Strategies website. Attribute Table Informationcity_name: Morning Heat Index Observations in Floating-Point (°F)

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.

This parcel lines feature class represents the current city parcel lines within the City of Los Angeles. It shares topology with the Landbase Parcel_polygons feature class. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way, ownership and land record information. The legal boundaries are determined on the ground by license surveyors in the State of California, and by recorded documents from the Los Angeles County Recorder's office and the City Clerk's office of the City of Los Angeles. Parcel and ownership information are available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.Associated information about the landbase parcel lines is entered into attributes. Principal attributes include:CV_LAYER: is the principal field that describes the various types of lines like street and freeway right-of-ways, tract, lots, government property and easements lines, private street lines, utility right-of-ways, and ownership lines. For a complete list of attribute values, please refer to Landbase_parcel_lines_data_dictionary.Landbase parcels lines layer was created in geographical information systems (GIS) software to display the location of parcel lots. The parcels lines layer is a feature class in the LACityLandbaseData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. The lines are derived from the polygon feature class in the landbase parcels layer, and information about the lines is entered into attributes. The CV_LAYER field values describe the various types of lines. The right-of-way, row, line features consist of CV_LAYER = 6, CV_LAYER = 106, and portions of CV_LAYER = 1 where that line is both the city boundary and the parcel line. In some cases, a parcel line will share two different type descriptions. Refer to CV_LAYER field metadata for further explantion. Parcel information should only be added to the Landbase Parcels layer if documentation exists, such as a Deed or a Plan approved by the City Council. When seeking the definitive description of real property, consult the recorded Deed or Plan.List of Fields:ASSETIDCV_LAYER: This value is a number representing a different type of user-assigned layer. Each of the line segments in the landbase parcels lines are assigned one of the CV_LAYER numbers, representing a different type of line work, described below. In some cases, a parcel line will share two different type descriptions. Such as, a parcel line may have CV_LAYER = 1 City Boundary line, and it is a CV_LAYER = 8 Tract line. The Tract line description is used first, and the City Boundary line description is used second. When selecting City Boundary line using CV_LAYER = 1, then (special way to select data...). The right-of-way, row, line features consist of CV_LAYER = 6, CV_LAYER = 106, and portions of CV_LAYER = 1 where that line is both the city boundary and the parcel line. Values: • 50 - Lot cut linework. • 38 - Freeway ease as easement lines. • 108 - Tract lines that are private street lines. • 8 - Tract lines, Rancho lines, Freeway (Fwy), and Right of way lines. • 30 - Former city boundary lines; other city or county boundary line. • 34 - Overlap lines. • 6 - Right of way (R/W) sidelines. • 19 - LA City easement lines. • 21 - All governmental lines (Fee). • 37 - APN (BPP) lines shown on tax assessors map (PCL maps); but no new PIN is created for the parcels polygon feature. • 48 - Subdivision title anno shown for ownership purpose (lot cut). • 10 - Lot lines. • 68 - SBBM (San Bernardino Base Meridian) section lines. • 1 - Boundary lines (existing). • 110 - Lot lines that are private street lines. • 18 - All governmental easement lines (except LA City and State freeway ease right of way lines). • 106 - Fwy traveled roadway lines; Dash right of way lines; Railroad and transmission lines. • 0 - Cadastral format.SHAPE: Feature geometry.OBJECTID: Internal feature number.ID: A unique numeric identifier of the polygon. The ID value is the last part of the PIN field value.MAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral tract index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers.

To download:1. Click the Download button above.2. A side panel will appear showing download options. Under Shapefile, click the Download button.3. When the download completes, browse to the location of the downloaded .zip, copy it to the location where you manage your redistricting files, then right-click to extract the contents. You will then be able to use the file in GIS software.If, rather than downloading the data, you wish the reference online versions of these datasets directly to ensure you are always using the most up-to-date data, please contact the County of San Bernardino Innovation and Technology Departments at 909-884-4884 or by emailing OpenData@isd.sbcounty.gov for informations and instructions for doing so.This dataset should only be used for the purpose of establishing election divisions within a district. It will be removed once the redistricting process has concluded.

This web map shows the Redlands city boundary, San Bernardino kangaroo rat habitat, and the parcel intersecting the habitat boundary.

The boundary for the City of Yucaipa was extracted from the San Bernardino County City Limits dataset. From the description for San Bernardino County City Limits dataset - "The City Limits GIS layer shows the city limit boundaries in the County of San Bernardino. City limit boundaries are maintained through maps of annexations and detachments by the County of San Bernardino Surveyor's Office. City Limits GIS data stores non-contiguous city polygons as individual polygons. For questions about this dataset, please email opendata@isd.sbcounty.gov."This GIS dataset produced by the City of Yucaipa is shared as a public resource. While every practical effort is made to ensure data accuracy, the City of Yucaipa makes no warranties concerning the accuracy, completeness or suitability of its data and it should not be applied as a legal description. Information obtained from this data is to be used for reference purposes only. No responsibility is assumed for damages or other liabilities due to the accuracy, availability, use or misuse of the information provided.

To download:1. Click the Download button above.2. A side panel will appear showing download options. Under Shapefile, click the Download button.3. When the download completes, browse to the location of the downloaded .zip, copy it to the location where you manage your redistricting files, then right-click to extract the contents. You will then be able to use the file in GIS software.If, rather than downloading the data, you wish the reference online versions of these datasets directly to ensure you are always using the most up-to-date data, please contact the County of San Bernardino Innovation and Technology Departments at 909-884-4884 or by emailing OpenData@isd.sbcounty.gov for informations and instructions for doing so.This dataset should only be used for the purpose of establishing election divisions within a district. It will be removed once the redistricting process has concluded.

The City Spheres of Influence was created for the LAFCO maps and updated on 11/8/21. Data is created and mantained by San Bernardino County Innovation and Technology's GIS team.