5 datasets found
  1. TIGER/Line Shapefile, Current, County, Santa Barbara County, CA, All Roads

    • catalog.data.gov
    Updated Dec 15, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geospatial Products Branch (Point of Contact) (2023). TIGER/Line Shapefile, Current, County, Santa Barbara County, CA, All Roads [Dataset]. https://catalog.data.gov/dataset/tiger-line-shapefile-current-county-santa-barbara-county-ca-all-roads
    Explore at:
    Dataset updated
    Dec 15, 2023
    Dataset provided by
    United States Census Bureauhttp://census.gov/
    Area covered
    Santa Barbara County, California
    Description

    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.

  2. c

    Lompoc Yerba Santa - Final Critical Habitat - USFWS [ds748] GIS Dataset

    • map.dfg.ca.gov
    Updated Sep 11, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2023). Lompoc Yerba Santa - Final Critical Habitat - USFWS [ds748] GIS Dataset [Dataset]. https://map.dfg.ca.gov/metadata/ds0748.html
    Explore at:
    Dataset updated
    Sep 11, 2023
    Description

    CDFW BIOS GIS Dataset, Contact: U.S. Fish & Wildlife Service USFWS, Description: These data identify the area (in general) where final critical habitat for the Lompoc yerba santa (Eriodictyon capitatum) occurs. Critical habitat for the species occurs in two areas in western Santa Barbara County California: the Solomon Hills southeast of the City of Santa Maria and in the Santa Ynez Mountains east of Point Conception.

  3. d

    Offshore Oil Leases

    • catalog.data.gov
    • s.cnmilf.com
    • +3more
    Updated Mar 30, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California State Lands Commission (2024). Offshore Oil Leases [Dataset]. https://catalog.data.gov/dataset/offshore-oil-leases-fe3da
    Explore at:
    Dataset updated
    Mar 30, 2024
    Dataset provided by
    California State Lands Commission
    Description

    California State Lands Commission Offshore Oil Leases in the vicinity of Santa Barbara, Ventura, and Orange County.The polygons in this layer show the position of Offshore Oil Leases as documented by former State Lands Senior Boundary Determination Officer, Cris N. Perez and as reviewed and updated by GIS and Boundary staff.Background: This layer represents active offshore oil and gas agreements in California waters, which are what remain of the more than 60 originally issued. These leases were issued prior to the catastrophic 1969 oil spill from Platform A in federal waters off Santa Barbara County, and some predate the formation of the Commission. Between 2010 and 2014, the bulk of the approximately $300 million generated annually for the state's General Fund from oil and gas agreements was from these offshore leases.In 1921, the Legislature created the first tidelands oil and gas leasing program. Between 1921 and 1929, approximately 100 permits and leases were issued and over 850 wells were drilled in Santa Barbara and Ventura Counties. In 1929, the Legislature prohibited any new leases or permits. In 1933, however, the prohibition was partially lifted in response to an alleged theft of tidelands oil in Huntington Beach. It wasn't until 1938, and again in 1955, that the Legislature would allow new offshore oil and gas leasing. Except for limited circumstances, the Legislature has consistently placed limits on the areas that the Commission may offer for lease and in 1994, placed the entirety of California's coast off-limits to new oil and gas leases. Layer Creation Process:In 1997 Cris N. Perez, Senior Boundary Determination Officer of the Southern California Section of the State Lands Division, prepared a report on the Commission’s Offshore Oil Leases to:A. Show the position of Offshore Oil Leases. B. Produce a hard copy of 1927 NAD Coordinates for each lease. C. Discuss any problems evident after plotting the leases.Below are some of the details Cris included in the report:I have plotted the leases that were supplied to me by the Long Beach Office and computed 1927 NAD California Coordinates for each one. Where the Mean High Tide Line (MHTL) was called for and not described in the deed, I have plotted the California State Lands Commission CB Map Coordinates, from the actual field surveys of the Mean High Water Line and referenced them wherever used. Where the MHTL was called for and not described in the deed and no California State Lands Coordinates were available, I digitized the maps entitled, “Map of the Offshore Ownership Boundary of the State of California Drawn pursuant to the Supplemental Decree of the U.S. Supreme Court in the U.S. V. California, 382 U.S. 448 (1966), Scale 1:10000 Sheets 1-161.” The shore line depicted on these maps is the Mean Lower Low Water (MLLW) Line as shown on the Hydrographic or Topographic Sheets for the coastline. If a better fit is needed, a field survey to position this line will need to be done.The coordinates listed in Cris’ report were retrieved through Optical Character Recognition (OCR) and used to produce GIS polygons using Esri ArcGIS software. Coordinates were checked after the OCR process when producing the polygons in ArcMap to ensure accuracy. Original Coordinate systems (NAD 1927 California State Plane Zones 5 and 6) were used initially, with each zone being reprojected to NAD 83 Teale Albers Meters and merged after the review process.While Cris’ expertise and documentation were relied upon to produce this GIS Layer, certain polygons were reviewed further for any potential updates since Cris’ document and for any unusual geometry. Boundary Determination Officers addressed these issues and plotted leases currently listed as active, but not originally in Cris’ report. On December 24, 2014, the SLA boundary offshore of California was fixed (permanently immobilized) by a decree issued by the U.S. Supreme Court United States v. California, 135 S. Ct. 563 (2014). Offshore leases were clipped so as not to exceed the limits of this fixed boundary. Lease Notes:PRC 1482The “lease area” for this lease is based on the Compensatory Royalty Agreement dated 1-21-1955 as found on the CSLC Insider. The document spells out the distinction between “leased lands” and “state lands”. The leased lands are between two private companies and the agreement only makes a claim to the State’s interest as those lands as identified and surveyed per the map Tract 893, Bk 27 Pg 24. The map shows the State’s interest as being confined to the meanders of three sloughs, one of which is severed from the bay (Anaheim) by a Tideland sale. It should be noted that the actual sovereign tide and or submerged lands for this area is all those historic tide and submerged lands minus and valid tide land sales patents. The three parcels identified were also compared to what the Orange County GIS land records system has for their parcels. Shapefiles were downloaded from that site as well as two centerline monuments for 2 roads covered by the Tract 893. It corresponded well, so their GIS linework was held and clipped or extended to make a parcel.MJF Boundary Determination Officer 12/19/16PRC 3455The “lease area” for this lease is based on the Tract No. 2 Agreement, Long Beach Unit, Wilmington Oil Field, CA dated 4/01/1965 and found on the CSLC insider (also recorded March 12, 1965 in Book M 1799, Page 801).Unit Operating Agreement, Long Beach Unit recorded March 12, 1965 in Book M 1799 page 599.“City’s Portion of the Offshore Area” shall mean the undeveloped portion of the Long Beach tidelands as defined in Section 1(f) of Chapter 138, and includes Tract No. 1”“State’s Portion of the Offshore Area” shall mean that portion of the Alamitos Beach Park Lands, as defined in Chapter 138, included within the Unit Area and includes Tract No. 2.”“Alamitos Beach Park Lands” means those tidelands and submerged lands, whether filled or unfilled, described in that certain Judgment After Remittitur in The People of the State of California v. City of Long Beach, Case No. 683824 in the Superior Court of the State of California for the County of Los Angeles, dated May 8, 1962, and entered on May 15, 1962 in Judgment Book 4481, at Page 76, of the Official Records of the above entitled court”*The description for Tract 2 has an EXCEPTING (statement) “therefrom that portion lying Southerly of the Southerly line of the Boundary of Subsidence Area, as shown on Long Beach Harbor Department {LBHD} Drawing No. D-98. This map could not be found in records nor via a PRA request to the LBHD directly. Some maps were located that show the extents of subsidence in this area being approximately 700 feet waterward of the MHTL as determined by SCC 683824. Although the “EXCEPTING” statement appears to exclude most of what would seem like the offshore area (out to 3 nautical miles from the MHTL which is different than the actual CA offshore boundary measured from MLLW) the 1964, ch 138 grant (pg25) seems to reference the lands lying seaward of that MHTL and ”westerly of the easterly boundary of the undeveloped portion of the Long Beach tidelands, the latter of which is the same boundary (NW) of tract 2. This appears to then indicate that the “EXCEPTING” area is not part of the Lands Granted to City of Long Beach and appears to indicate that this portion might be then the “State’s Portion of the Offshore Area” as referenced in the Grant and the Unit Operating Agreement. Section “f” in the CSLC insider document (pg 9) defines the Contract Lands: means Tract No. 2 as described in Exhibit “A” to the Unit Agreement, and as shown on Exhibit “B” to the Unit Agreement, together with all other lands within the State’s Portion of the Offshore Area.Linework has been plotted in accordance with the methods used to produce this layer, with record lines rotated to those as listed in the descriptions. The main boundaries being the MHTL(north/northeast) that appears to be fixed for most of the area (projected to the city boundary on the east/southeast); 3 nautical miles from said MHTL on the south/southwest; and the prolongation of the NWly line of Block 50 of Alamitos Bay Tract.MJF Boundary Determination Officer 12-27-16PRC 4736The “lease area” for this lease is based on the Oil and Gas Lease and Agreement as found on the CSLC insider and recorded August 17, 1973 in BK 10855 PG 432 Official Records, Orange County. The State’s Mineral Interests are confined to Parcels “B-1” and “B-2” and are referred to as “State Mineral Lands” comprising 70.00 Acres. The lessee each has a right to certain uses including but not limited to usage of utility corridors, 110 foot radius parcels surrounding well-sites and roads. The State also has access to those same roads per this agreement/lease. Those uses are allowed in what are termed “State Lands”-Parcel E and “Leased Lands” which are defined as the “South Bolsa Lease Area”-Parcel C (2 parcels) and “North Bolsa Lease Area”-Parcel D. The “State Lands”-Parcel E are actually 3 parcels, 2 of which are within road right-of-ways. MJF Boundary Determination Officer 12-28-16

  4. Microsoft Buildings Footprint Training Data with Heights

    • cityscapes-projects-gisanddata.hub.arcgis.com
    Updated Feb 27, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Esri (2019). Microsoft Buildings Footprint Training Data with Heights [Dataset]. https://cityscapes-projects-gisanddata.hub.arcgis.com/datasets/esri::microsoft-buildings-footprint-training-data-with-heights-
    Explore at:
    Dataset updated
    Feb 27, 2019
    Dataset authored and provided by
    Esrihttp://esri.com/
    License

    Open Database License (ODbL) v1.0https://www.opendatacommons.org/licenses/odbl/1.0/
    License information was derived automatically

    Area covered
    Description

    Microsoft recently released a free set of deep learning generated building footprints covering the United States of America. As part of that project Microsoft shared 8 million digitized building footprints with height information used for training the Deep Learning Algorithm. This map layer includes all buildings with height information for the original training set that can be used in scene viewer and ArcGIS pro to create simple 3D representations of buildings. Learn more about the Microsoft Project at the Announcement Blog or the raw data is available at Github.Click see Microsoft Building Layers in ArcGIS Online.Digitized building footprint by State and City

    Alabama Greater Phoenix City, Mobile, and Montgomery

    Arizona Tucson

    Arkansas Little Rock with 5 buildings just across the river from Memphis

    California Bakersfield, Fresno, Modesto, Santa Barbara, Sacramento, Stockton, Calaveras County, San Fran & bay area south to San Jose and north to Cloverdale

    Colorado Interior of Denver

    Connecticut Enfield and Windsor Locks

    Delaware Dover

    Florida Tampa, Clearwater, St. Petersburg, Orlando, Daytona Beach, Jacksonville and Gainesville

    Georgia Columbus, Atlanta, and Augusta

    Illinois East St. Louis, downtown area, Springfield, Champaign and Urbana

    Indiana Indianapolis downtown and Jeffersonville downtown

    Iowa Des Moines

    Kansas Topeka

    Kentucky Louisville downtown, Covington and Newport

    Louisiana Shreveport, Baton Rouge and center of New Orleans

    Maine Augusta and Portland

    Maryland Baltimore

    Massachusetts Boston, South Attleboro, commercial area in Seekonk, and Springfield

    Michigan Downtown Detroit

    Minnesota Downtown Minneapolis

    Mississippi Biloxi and Gulfport

    Missouri Downtown St. Louis, Jefferson City and Springfield

    Nebraska Lincoln

    Nevada Carson City, Reno and Los Vegas

    New Hampshire Concord

    New Jersey Camden and downtown Jersey City

    New Mexico Albuquerque and Santa Fe

    New York Syracuse and Manhattan

    North Carolina Greensboro, Durham, and Raleigh

    North Dakota Bismarck

    Ohio Downtown Cleveland, downtown Cincinnati, and downtown Columbus

    Oklahoma Downtown Tulsa and downtown Oklahoma City

    Oregon Portland

    Pennsylvania Downtown Pittsburgh, Harrisburg, and Philadelphia

    Rhode Island The greater Providence area

    South Carolina Greensville, downtown Augsta, greater Columbia area and greater Charleston area

    South Dakota greater Pierre area

    Tennessee Memphis and Nashville

    Texas Lubbock, Longview, part of Fort Worth, Austin, downtown Houston, and Corpus Christi

    Utah Salt Lake City downtown

    Virginia Richmond

    Washington Greater Seattle area to Tacoma to the south and Marysville to the north

    Wisconsin Green Bay, downtown Milwaukee and Madison

    Wyoming Cheyenne

  5. Home Dispatch

    • nifc.hub.arcgis.com
    Updated Dec 4, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    National Interagency Fire Center (2023). Home Dispatch [Dataset]. https://nifc.hub.arcgis.com/datasets/nifc::nv-blm-mobilizations-wfl1/about?layer=2
    Explore at:
    Dataset updated
    Dec 4, 2023
    Dataset authored and provided by
    National Interagency Fire Centerhttps://www.nifc.gov/
    Area covered
    Description

    Geographic points depicting the locations of Dispatch Centers within Tier 1, 2, and 3 Dispatch Areas across the nation. Tier 1 refers to the National Interagency Coordination Center (NICC) which administers the entire country. Tier 2 are the Geographic Area Coordination Centers (GACCs). Tier 3 are the Local Dispatch Centers. Depending on availability of addresses, points may represent actual Dispatch Center offices or only the general city in which the center exists. If no address is listed in the DispAddress field, the location is specific to the city only and not to an address.3/27/2023 - 3/30//2023- Geographic changes made only where DispAddress had changed. Tabular changes to DispName, DispUnitID, DispContactPhone, DispEmail, DispAddress all updated using data from Unit IDx application current as of 3/30/2023. Edits by JKuenzi, USFS. Changes include but are not limited to:DispName from "Angeles Emergency Communication Center" to "Angeles Communication Center"DispName from "Billings Interagency Dispatch Center" to "Billings Dispatch Center" DispName from "Bitterroot Interagency Dispatch Center" to "Bitterroot Dispatch Center"DispName from "Blackfeet Dispatch" to "Blackfeet Agency Dispatch Center" DispName from "Blue Mountain Interagency Communication Center" to "Blue Mountains Interagency Dispatch Center"DispName from "Boise Dispatch Center" to "Boise Interagency Dispatch Center"DispName from "Central California Interagency Communication Center" to "Central California Command Center"DispName from "Coeur d'Alene Interagency Dispatch Center" to "Coeur d'Alene Dispatch Center"DispName from "Columbia Cascade Communication Center" to "Columbia Cascade Communications Center"DispName from "Dillon Interagency Dispatch Center" to "Dillon Dispatch Center"DispName from "Florida Interagency Dispatch Center" to "Florida Interagency Coordination Center"DispName from "Fort Belknap Dispatch" to "Fort Belknap Agency Dispatch Center"DispName from "Great Falls Interagency Dispatch Center" to "Great Falls Dispatch Center"DispName from "Helena Interagency Dispatch Center" to "Helena Dispatch Center"DispName from "Howard Forest Command Center" to "Howard Forest Emergency Command Center" DispName from "Illinois Interagency Dispatch Center" to "Illinois Interagency Coordination Center"DispName from "Kern County Fire Department Emergency Communication Center" to "Kern County Emergency Command Center"DispName from "Kootenai Interagency Dispatch Center" to "Kootenai Dispatch Center"DispName from "Las Vegas Interagency Communication Center" to "Las Vegas Interagency Dispatch Center"DispName from "Lewistown Interagency Dispatch Center" to "Lewistown Dispatch Center"DispName from "Los Padres Communications Center" to "Los Padres Communication Center"DispName from "Madera-Mariposa-Merced Emergency Command Center" to "Madera-Mariposa-Merced Command Center"DispName from "Mid-Atlantic Coordination Center" to "Mid-Atlantic Interagency Coordination Center"DispName from "Miles City Interagency Dispatch Center" to "Miles City Dispatch Center"DispName from "Missoula Interagency Dispatch Center" to "Missoula Dispatch Center"DispName from "Missouri-Iowa Interagency Fire Center to Missouri-Iowa Interagency Dispatch Center"DispName from "North Dakota Interagency Dispatch Center" to "North Dakota Dispatch Center"DispName from "Northeast Washington Interagency Communication Center" to "Northeast Washington Interagency Communications Center"DispName from "Orange County Fire Authority Emergency Command Center" to "Orange County Command Center"DispName from "Oroville Emergency Command Center" to "Butte Emergency Command Center" DispName from "Owens Valley Interagency Communications Center" to "Owens Valley Interagency Command Center"DispName from "Plumas Emergency Communications Center" to "Plumas Emergency Communication Center"DispName from "Perris Emergency Command Center" to "Riverside Emergency Command Center"DispName from "Rocky Boy's Dispatch" to "Rocky Boy's Agency Dispatch Center"DispName from "Roseburg Interagency Coordination Center" to "Roseburg Interagency Communication Center"DispName from "San Benito-Monterey Emergency Command Center" to "San Benito Monterey Emergency Command Center"DispName from "Santa Barbara Dispatch Center" to "Santa Barbara Dispatch CenterDispName from "Santa Clara Command Center" to "Santa Clara Emergency Command Center'DispName from "South Central Interagency Dispatch Center" to "South Idaho Interagency Dispatch Center"DispName from "Tuolumne Calaveras Command Center" to "Tuolumne Calaveras Emergency Command Center"DispName from "Yakima Agency Dispatch Center" to "Yakama Agency Dispatch Center"DispName from "Yreka Interagency Dispatch Center" to "Yreka Interagency Command Center"DispName from "Fresno-Sierra Emergency Command Center" to "Sierra Interagency Communication Center"DispName from "Red Bluff Emergency Command Center" to "Tehama Glenn Emergency Command Center"DispName from "Visalia Emergency Command Center" to "Tulare Emergency Command Center"DispName from "Saint Helena Emergency Command Center" to "Lake Napa Command Center"07/08/2022 - Tabular change only. DispName corrected from "Columbia Cascades Communication Center" to "Columbia Cascade Communication Center" , per Desraye Assali, R6 Fire and Aviation GIS Coordinator. Edits by JKuenzi, USFS.5/5/2022 - Geospatial and tabular changes. Removal of Wellpinit, WA. Change was made to National Dispatch Boundary in 10/27/2021, to combine USWASAC with USWANEC, but removal of corresponding Dispatch Center was missed. Change verified by Ted Pierce, NW GACC Deputy Center Coordinator and Jill Jones, NE Washington Interagency Communications Center Mgr with Washington DNR. Edits by JKuenzi. 04/29/2022 - Tabular change only. Address of Colville Agency Dispatch (USWACAC) changed from "90 Polman Rd" to "90 Mount Tolman Rd". Information provided by Jill Jones, Interagency Dispatch Center Mgr for NE Washington Interagency Comm Center, and verified by call to USWACAC. No other changes made - locations and phone number were already correct. Edits by JKuenzi.04/04/2022 - Tabular changes only. Name change in Southern California from Monte Vista Interagency Center (USCAMVIC) to San Diego Interagency Center (USCASDIC) per James Tomaselli, Southern California Geographical Area Coordination Center Manager. Edits by JKuenzi. Following discussion between NRCC (Northern Rockies Geographic Area Coordination Center), USMTBZC in Bozeman, MT, and USMTBDC in Billings, MT, plans to merge Bozeman into Billings anticipated to start 4/18/2022, but will transition throughout 2022 year and be finalized on or near January 2023. USMTBZC (Bozeman Interagency Dispatch Center Office) was removed from the data earlier, but the effective start date of the implementation has been delayed from earlier expectations. Information provided by Kathy Pipkin, Northern Rockies Center Manager, and Kat Sorenson, R1 Asst Aircraft Coordinator. Edits by JKuenzi. 03/11/2022 - Geospatial and tabular changes. Information provided by Kathy Pipkin, Northern Rockies Center Manager, and Kat Sorenson, R1 Asst Aircraft Coordinator. Edits by JKuenzi.USMTBZC (Bozeman Interagency Dispatch) was absorbed into USMTBDC (Billings Interagency Dispatch). USMTBZC in Bozemen, MT, was removed . Change expected to go into effect on 3/31/2022. Rocky Boy's Dipsatch (Box Elder, MT), Blackfeet Dispatch (Browning, MT), Fort Belknap Dispatch (Harlem, MT), and Flathead Dispatch (Ronan, MT) all changed from DispatchTier 3 to DispatchTier 4.01/05/2022 - Geospatial and tabular changes. USMTFPAC (Fort Peck Dispatch) was closed/stopped as of 03/09/2020 per WFMI (Wildland Fire Management Information) application. USMTFPAC polygon was merged into USMTLEC per USMTLEC Center Manager. USMTFPAC (Fort Peck Dispatch) office location in Poplar, MT, was removed. Edits by JKuenzi, USFS.02/19/2021 - Geospatial and tabular changes. Fairbanks Area Forestry Dispatch, Delta Area Forestry Dispatch, and Tok Area Forestry Dispatch merged into Northern Forestry Dispatch Center (USAKNFDC) per per Jennifer L Jenkins - BLM GIS Specialist, and Ray Crowe - BLM Alaska Interagency Coordination Center (AICC) Center Manager, Dan Labarre - DNR, and Gabriella Branson - DNR. Locations for Delta and Tok were deleted. Tabular information for Fairbanks was updated with merged information. Edits by JKuenzi, USFS.12/21/2019 - 10/22/2020 - Geospatial and tabular changes. Table updated to match NWCG data standards. Original data only correct to nearest city location. Current layer updated to match building locations, except where noted. Locations derived from U.S. Census City locations, IRWIN Duty Stations data, Personal knowledge, geocoded locations produced by Texas A&M GeoServices, or calls with the actual dispatch offices, and confirmed using Google Earth Pro and Google Maps, where possible. Phone numbers added. FireNet emails added. Note that additional emails may be in use by the Dispatch Office, but have not been included. Edits by JKuenzi, USFS.

  6. Not seeing a result you expected?
    Learn how you can add new datasets to our index.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geospatial Products Branch (Point of Contact) (2023). TIGER/Line Shapefile, Current, County, Santa Barbara County, CA, All Roads [Dataset]. https://catalog.data.gov/dataset/tiger-line-shapefile-current-county-santa-barbara-county-ca-all-roads
Organization logo

TIGER/Line Shapefile, Current, County, Santa Barbara County, CA, All Roads

Explore at:
Dataset updated
Dec 15, 2023
Dataset provided by
United States Census Bureauhttp://census.gov/
Area covered
Santa Barbara County, California
Description

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.

Search
Clear search
Close search
Google apps
Main menu