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.

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

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:Metadata is missing or incomplete for some layers at this time and will be continuously improved.We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.PurposeCounty and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. This feature layer is for public use.Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal BuffersCities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal Buffers (this dataset)Without Coastal BuffersPlace AbbreviationsUnincorporated Areas (Coming Soon)Census Designated Places (Coming Soon)Cartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the authoritative source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except COASTAL, Area_SqMi, Shape_Area, and Shape_Length to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCOPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering systemPlace Name: CDTFA incorporated (city) or county nameCounty: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information SystemPlace Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area namesCNTY Abbr: CalTrans Division of Local Assistance abbreviations of county namesArea_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.AccuracyCDTFA"s source data notes the following about accuracy:City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the California State Board of Equalization"s 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties.In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose.SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon.Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these items, or others, from the shoreline cuts, please reach out using the contact information above.Offline UseThis service is fully enabled for sync and export using Esri Field Maps or other similar tools. Importantly, the GlobalID field exists only to support that use case and should not be used for any other purpose (see note in field descriptions).Updates and Date of ProcessingConcurrent with CDTFA updates, approximately every two weeks, Last Processed: 12/17/2024 by Nick Santos using code path at https://github.com/CDT-ODS-DevSecOps/cdt-ods-gis-city-county/ at commit 0bf269d24464c14c9cf4f7dea876aa562984db63. It incorporates updates from CDTFA as of 12/12/2024. Future updates will include improvements to metadata and update frequency.

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 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.

This dataset comprises road centerlines for all roads in San Diego County. Road centerline information is collected from recorded documents (subdivision and parcel maps) and information provided by local jurisidictions (Cities in San Diego County, County of San Diego). Road names and address ranges are as designated by the official address coordinator for each jurisidcition. Jurisdictional information is created from spatial overlays with other data layers (e.g. Jurisdiction, Census Tract).The layer contains both public and private roads. Not all roads are shown on official, recorded documents. Centerlines may be included for dedicated public roads even if they have not been constructed. Public road names are the official names as maintained by the addressing authority for the jurisdiction in which the road is located. Official road names may not match the common or local name used to identify the road (e.g. State Route 94 is the official name of certain road segments commonly referred to as Campo Road).Private roads are either named or unnamed. Named private roads are as shown on official recorded documents or as directed by the addressing authority for the jurisdiction in which the road is located. Unnamed private roads are included where requested by the local jurisidiction or by SanGIS JPA members (primarily emergency response dispatch agencies). Roads are comprised of road segments that are individually identified by a unique, and persistent, ID (ROADSEGID). Roads segments are terminated where they intersect with each other, at jurisdictional boundaries (i.e. city limits), certain census tract and law beat boundaries, at locations where road names change, and at other locations as required by SanGIS JPA members. Each road segment terminates at an intersection point that can be found in the ROADS_INTERSECTION layer.Road centerlines do not necessarily follow the centerline of dedicated rights-of-way (ROW). Centerlines are adjusted as needed to fit the actual, constructed roadway. However, many road centerline segments are created intially based on record documents prior to construction and may not have been updated to meet as-built locations. Please notify SanGIS if the actual location differs from that shown. See the SanGIS website for contact information and reporting problems (http://www.sangis.org/contact/problem.html).Note, the road speeds in this layer are based on road segment class and were published as part of an agreement between San Diego Fire-Rescue, the San Diego County Sheriff's Department, and SanGIS. The average speed is based on heavy fire vehicles and may not represent the posted speed limit.

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

This map shows only shows the San Bernardino County as a view of the total population of people age 18+ in the San Bernardino County as well as the total population in that area. The map shows the density of the total population in 2020 and the total people who are 18+ in the San Bernardino County. This just goes to show that there are a lot of people living in the San Bernardino County who are at 18+ but most part there are more total population in 2020 then people counted to be 18+. A lot of citizens live in the population dense areas like Ontario, Rancho Cucamango, Fontana, and Redlands. On the other hand not a lot of people live in Big Bear City, and West Wood because it is more expensive to live up there than it is to live in an apartment in the bigger cities.To create this layer, the USA Census Tract layer from live atlas was filtered in San Bernardino County then enriched with 2020 data of number of total citizens in 2020 and citizens at the age of 18+.

The Parcels (Public) web map provides parcel boundary information for the City of Big Bear Lake, made available for public planning and informational purposes. This version complies with California Assembly Bill AB 1785, which prohibits the publication of parcel owner names and mailing addresses in publicly accessible platforms—therefore, those fields have been redacted. Boundaries are derived from San Bernardino County parcel data and updated periodically, but are not survey-grade and may not reflect the most current assessor or recorded parcel information. For authoritative property details, users should consult the San Bernardino County Assessor’s Office. The City provides this map “as-is” and assumes no liability for errors, omissions, or misuse of the data.Dependent Application: Parcel Viewer

This shapefile contains boundaries representing the Town of Apple Valley City Council Districts for the purpose of establishing election divisions within a district. 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.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 contains the geographic data used to create maps for the San Diego County Regional Equity Indicators Report led by the Office of Equity and Racial Justice (OERJ). The full report can be found here: https://data.sandiegocounty.gov/stories/s/7its-kgpt

Demographic data from the report can be found here: https://data.sandiegocounty.gov/dataset/Equity-Report-Data-Demographics/q9ix-kfws

Filter by the Indicator column to select data for a particular indicator map.

Export notes: Dataset may not automatically open correctly in Excel due to geospatial data. To export the data for geospatial analysis, select Shapefile or GEOJSON as the file type. To view the data in Excel, export as a CSV but do not open the file. Then, open a blank Excel workbook, go to the Data tab, select “From Text/CSV,” and follow the prompts to import the CSV file into Excel. Alternatively, use the exploration options in "View Data" to hide the geographic column prior to exporting the data.

USER NOTES: 4/7/2025 - The maps and data have been removed for the Health Professional Shortage Areas indicator due to inconsistencies with the data source leading to some missing health professional shortage areas. We are working to fix this issue, including exploring possible alternative data sources.

5/21/2025 - The following changes were made to the 2023 report data (Equity Report Year = 2023). Self-Sufficiency Wage - a typo in the indicator name was fixed (changed sufficienct to sufficient) and the percent for one PUMA corrected from 56.9 to 59.9 (PUMA = San Diego County (Northwest)--Oceanside City & Camp Pendleton). Notes were made consistent for all rows where geography = ZCTA. A note was added to all rows where geography = PUMA. Voter registration - label "92054, 92051" was renamed to be in numerical order and is now "92051, 92054". Removed data from the percentile column because the categories are not true percentiles. Employment - Data was corrected to show the percent of the labor force that are employed (ages 16 and older). Previously, the data was the percent of the population 16 years and older that are in the labor force. 3- and 4-Year-Olds Enrolled in School - percents are now rounded to one decimal place. Poverty - the last two categories/percentiles changed because the 80th percentile cutoff was corrected by 0.01 and one ZCTA was reassigned to a different percentile as a result. Low Birthweight - the 33th percentile label was corrected to be written as the 33rd percentile. Life Expectancy - Corrected the category and percentile assignment for SRA CENTRAL SAN DIEGO. Parks and Community Spaces - corrected the category assignment for six SRAs.

5/21/2025 - Data was uploaded for Equity Report Year 2025. The following changes were made relative to the 2023 report year. Adverse Childhood Experiences - added geographic data for 2025 report. No calculation of bins nor corresponding percentiles due to small number of geographic areas. Low Birthweight - no calculation of bins nor corresponding percentiles due to small number of geographic areas.

Prepared by: Office of Evaluation, Performance, and Analytics and the Office of Equity and Racial Justice, County of San Diego, in collaboration with the San Diego Regional Policy & Innovation Center (https://www.sdrpic.org).

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 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 shapefile contains tax rate area (TRA) boundaries in San Diego County for the specified assessment roll year. Boundary alignment is based on the 2014 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

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.

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.

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.

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.

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.