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.

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.

This resource is a member of a series. 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.

This map shows the boundaries of the San Bernardino County Fire Protection District, Regional Service Zones. Data in this service is used in the LAFCO Maps.

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. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

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.

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.

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. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

This map shows the boundaries of the San Bernardino County Fire Protection District, Regional Service Zones. Data in this service is used in the LAFCO Maps.

This service shows the boundaries for County Service Area 20

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 Address Ranges Feature Shapefile (ADDRFEAT.dbf) contains the geospatial edge geometry and attributes of all unsuppressed address ranges for a county or county equivalent area. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. Single-address address ranges have been suppressed to maintain the confidentiality of the addresses they describe. Multiple coincident address range feature edge records are represented in the shapefile if more than one left or right address ranges are associated to the edge. The ADDRFEAT shapefile contains a record for each address range to street name combination. Address range associated to more than one street name are also represented by multiple coincident address range feature edge records. Note that the ADDRFEAT shapefile includes all unsuppressed address ranges compared to the All Lines Shapefile (EDGES.shp) which only includes the most inclusive address range associated with each side of a street edge. The TIGER/Line shapefile contain potential address ranges, not individual addresses. The address ranges in the TIGER/Line Files are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist.

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. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

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.

This service shows the boundaries for County Service Area 18

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 filewith no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent dataset, or they can be combined to cover the entire nation. The Area Hydrography Shapefile contains the geometry and attributes of both perennial and intermittent area hydrography features, including ponds, lakes, oceans, swamps (up to the U.S. nautical three-mile limit), glaciers, and the area covered by large rivers, streams, and/or canals that are represented as double-line drainage. Single-line drainage water features can be found in the Linear Hydrography Shapefile (LINEARWATER.shp). Linear water features includes single-line drainage water features and artificial path features, where they exist, that run through double-line drainage features such as rivers, streams, and/or canals, and serve as a linear representation of these features.

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 Address Ranges Relationship File (ADDR.dbf) contains the attributes of each address range. Each address range applies to a single edge and has a unique address range identifier (ARID) value. The edge to which an address range applies can be determined by linking the address range to the All Lines Shapefile (EDGES.shp) using the permanent topological edge identifier (TLID) attribute. Multiple address ranges can apply to the same edge since an edge can have multiple address ranges. Note that the most inclusive address range associated with each side of a street edge already appears in the All Lines Shapefile (EDGES.shp). The TIGER/Line Files contain potential address ranges, not individual addresses. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. The address ranges in the TIGER/Line Files are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist.

This data set maps and describes the geology of the Telegraph 7.5' quadrangle, San Bernardino County, California. Created using Environmental Systems Research Institute's ARC/INFO software, the data base consists of the following items: (1) a double precision map coverage containing geologic contacts and units, (2) a coverage containing site-specific structural data, (3) a coverage containing geologic-unit label leaders and their associated 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), an index map, a regional geologic and structure map, and a key for point and line symbols; (2) PDF files of this Readme (including the metadata file as an appendix), Description of Map Units (DMU), and the graphic produced by the PostScript plot file. The Telegraph Peak quadrangle is located in the eastern San Gabriel Mountains part of the Transverse Ranges Province of southern California. The generally east-striking structural grain characteristic of the crystalline rocks of much of the San Gabriel Mountains is apparent, but not well developed in the Telegraph Peak quadrangle. Here, the east-striking structural grain is somewhat masked by the northwest-striking grain associated with the San Andreas Fault zone. Faults within the quadrangle include northwest-striking, right-lateral strike-slip faults of the San Andreas system. The active San Andreas Fault, located in the northern part of the quadrangle, dominates the younger structural elements. North of the San Andreas Fault is the inactive Cajon Valley Fault that was probably an early strand of the San Andreas system. It was active during deposition of the middle Miocene Cajon Valley Formation. South of the San Andreas, the Punchbowl Fault, which is probably a long-abandoned segment of the San Andreas Fault (Matti and Morton, 1993), has a sinuous trace apparently due to compression in the eastern San Gabriel Mountains that post-dates displacement on the fault. The Punchbowl Fault separates two major subdivisions of the Mesozoic Pelona Schist and is left-laterally offset by a northeast-striking fault in the northwestern part of the quadrangle. Within the Punchbowl Fault zone is a thin layer of highly deformed basement rock, which is clearly not part of the Pelona Schist. To the southeast, in the Devore quadrangle, this included basement rock attains a thickness of several hundred feet. Along strike to the northwest, Tertiary sedimentary rocks are included within the fault zone. South of the Punchbowl Fault are several arcuate (in plan) faults that are part of an antiformal schuppen-like fault complex of the eastern San Gabriel Mountains. Most of these arcuate faults are reactivated and deformed older faults, and probably include the eastern part of the San Gabriel Fault. The Vincent Thrust of late Cretaceous or early Tertiary age separates the Pelona Schist in the lower plate from a heterogeneous basement complex in the upper plate. Immediately above the Vincent Thrust is a variable thickness of mylonitic rock generally interpreted as a product of displacement on the thrust. The upper plate includes two Paleozoic units, a schist and gneiss sequence and a schist, quartzite, and marble metasedimentary sequence. Both sequences are thrust over the Mesozoic Pelona Schist along the Vincent Thrust, and intruded by Tertiary (late Oligocene) granitic rocks, granodiorite of Telegraph Peak, that also intrude the Vincent Thrust. The Pelona Schist consists mostly of greenschist to amphibolite metamorphic grade meta-basalt (greenschist and amphibolite) and meta-graywacke (siliceous and white mica schist), with minor impure quartzite and marble, in which all primary structures have been destroyed and all layering transposed. Cretaceous granitic rocks, chiefly tonalite, intrude the schist and gneiss sequence, but not the Pelona Schist or the Vincent Thrust. North of the San Andreas Fault, bedrock units consist of undifferentiated Cretaceous tonalite, here informally named tonalite of Circle Mountain, with some included small boldies of gneiss and marble. These basement rocks are the westward continuation of rocks of the San Bernardino Mountains and not rocks of the San Gabriel Mountains south of the San Andreas Fault. Also north of the San Andreas Fault are the Oligocene Vaqueros Formation, middle Miocene Cajon Valley Formation, and Pliocene rocks of Phelan Peak. The latter two formations are divided into several conglomerate and arkosic sandstone subunits. In the northeastern corner of the quadrangle, the rocks of Phelan Peak are unconformably overlain by the Quaternary Harold Formation and Shoemaker Gravel. Quaternary units ranging from early Pleistocene to recent are mapped, and represent alluvial fan, landslide, talus, and wash environments. The geologic map database contains original U.S. Geological Survey data generated by detailed field observation and by interpretation of aerial photographs. This digital Open-File map supercedes an older analog Open-File map of the quadrangle, and includes extensive new data on the Quaternary deposits, and revises some fault and bedrock distribution within the San Gabriel Mountains. The digital map was compiled on a base-stable cronoflex copy of the Telegraph 7.5' topographic base and then scribed. This scribe guide was used to make a 0.007 mil blackline clear-film, from which lines and point were hand digitized. Lines, points, and polygons were subsequently edited at the USGS 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 as polygons, and site-specific data as points. Polygon, arc, and point attribute tables (.pat, .aat, and .pat, respectively) uniquely identify each geologic datum.

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. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

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.

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. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.