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 Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) contains a record for each face / area hydrography feature relationship. 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 face to which a record in the Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) applies can be determined by linking to the Topological Faces Shapefile (FACES.shp) using the permanent topological face identifier (TFID) attribute. The area hydrography feature to which a record in the Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) applies can be determined by linking to the Area Hydrography Shapefile (AREAWATER.shp) using the area hydrography identifier (HYDROID) attribute. A face may be part of multiple area water features. An area water feature may consist of multiple faces.

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 shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. The Address Range / Feature Name Relationship File (ADDRFN.dbf) contains a record for each address range / linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute that can be used to link to the Address Ranges Relationship File (ADDR.dbf). The linear feature name is identified by the linear feature identifier (LINEARID) attribute that can be used to link to the Feature Names Relationship File (FEATNAMES.dbf).

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 MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Feature Names Relationship File (FEATNAMES.dbf) contains a record for each feature name and any attributes associated with it. Each feature name can be linked to the corresponding edges that make up that feature in the All Lines Shapefile (EDGES.shp), where applicable to the corresponding address range or ranges in the Address Ranges Relationship File (ADDR.dbf), or to both files. Although this file includes feature names for all linear features, not just road features, the primary purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute, which can be used to link to the Address Ranges Relationship File (ADDR.dbf). The linear feature is identified by the linear feature identifier (LINEARID) attribute, which can be used to relate the address range back to the name attributes of the feature in the Feature Names Relationship File or to the feature record in the Primary Roads, Primary and Secondary Roads, or All Roads Shapefiles. The edge to which a feature name applies can be determined by linking the feature name record to the All Lines Shapefile (EDGES.shp) using the permanent edge identifier (TLID) attribute. The address range identifier(s) (ARID) for a specific linear feature can be found by using the linear feature identifier (LINEARID) from the Feature Names Relationship File (FEATNAMES.dbf) through the Address Range / Feature Name Relationship File (ADDRFN.dbf).

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.

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

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 Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) contains a record for each face / area hydrography feature relationship. 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 face to which a record in the Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) applies can be determined by linking to the Topological Faces Shapefile (FACES.shp) using the permanent topological face identifier (TFID) attribute. The area hydrography feature to which a record in the Topological Faces / Area Hydrography Relationship File (FACESAH.dbf) applies can be determined by linking to the Area Hydrography Shapefile (AREAWATER.shp) using the area hydrography identifier (HYDROID) attribute. A face may be part of multiple area water features. An area water feature may consist of multiple faces.

This feature class contains center lines for many of the public and private roads, dirt roads, and highways in the County of Kern. The data includes road names, address range, road type, road class, and municipal information.

© Kern County Public Works Department Kern County Planning and Natural Resources Department Kern County Sheriff's Office Kern County Fire Department City of Bakersfield, IT Division, GIS Services This layer is sourced from maps.co.kern.ca.us.

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, stairways, and winter trails.

URL from idinfo/citation in CSDGM metadata.

These vector contour lines are derived from the 3D Elevation Program using automated and semi-automated processes. They were created to support 1:24,000-scale CONUS and Hawaii, 1:25,000-scale Alaska, and 1:20,000-scale Puerto Rico / US Virgin Island topographic map products, but are also published in this GIS vector format. Contour intervals are assigned by 7.5-minute quadrangle, so this vector dataset is not visually seamless across quadrangle boundaries. The vector lines have elevation attributes (in feet above mean sea level on NAVD88), but this dataset does not carry line symbols or annotation.Metadata Link for the USGS 1/3 arc-second Contour Downloadable Data Collectionhttps://www.sciencebase.gov/catalog/file/get/4f70ab22e4b058caae3f8deb?f=_disk_35%2F1e%2F20%2F351e2044b02ae4f163c2cdcaa66fda19a32a4ba4&transform=1&allowOpen=true

Analysis of ‘Bear Hunt Areas [ds2807]’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/843681bb-f39f-4533-ae50-95436860dac7 on 27 January 2022.

--- Dataset description provided by original source is as follows ---

Except as provided in Section 366, bear may be taken only as follows:(a) Areas:(1) Northern California: In the counties of Del Norte, Humboldt, Plumas, Shasta, Siskiyou, Tehama and Trinity; and those portions of Lassen and Modoc counties west of the following line: Beginning at Highway 395 and the Sierra-Lassen county line; north on Highway 395 to the junction of Highway 36; west on Highway 36 to the junction of Highway 139; north on Highway 139 to Highway 299; north on Highway 299 to County Road 87; west on County Road 87 to Lookout-Hackamore Road; north on Lookout-Hackamore Road to Highway 139; north on Highway 139 to the Modoc-Siskiyou county line; north on the Modoc-Siskiyou county line to the Oregon border.(2) Central California: In the counties of Alpine, Amador, Butte, Calaveras, Colusa, El Dorado, Glenn, Lake, Mendocino, Nevada, Placer, Sacramento, Sierra, Sutter, Yolo and Yuba and those portions of Napa and Sonoma counties northeast of Highway 128.(3) Southern Sierra: That portion of Kern County west of Highway 14 and east of the following line: Beginning at the intersection of Highway 99 and the Kern-Tulare county line; south on Highway 99 to Highway 166; west and south on Highway 166 to the Kern-Santa Barbara county line; and those portions of Fresno, Madera, Mariposa, Merced, Stanislaus, Tulare and Tuolumne counties east of Highway 99.(4) Southern California: In the counties of Los Angeles, Santa Barbara and Ventura; that portion of Riverside County north of Interstate 10 and west of Highway 62; and that portion of San Bernardino County south and west of the following line: Beginning at the intersection of Highway 18 and the Los Angeles-San Bernardino county line; east along Highway 18 to Highway 247; southeast on Highway 247 to Highway 62; southwest along Highway 62 to the Riverside-San Bernardino county line.(5) Southeastern Sierra: Those portions of Inyo and Mono counties west of Highway 395; and that portion of Madera County within the following line: Beginning at the junction of the Fresno-Madera-Mono county lines; north and west along the Madera-Mono county line to the boundary of the Inyo-Sierra National Forest; south along the Inyo-Sierra National Forest boundary to the Fresno-Madera county line; north and east on the Fresno-Madera county line to the point of beginning. Also, that portion of Inyo county west of Highway 395; and that portion of Mono county beginning at the intersection of Highway 6 and the Mono county line; north along Highway 6 to the Nevada state line; north along the Nevada state line to the Alpine county line; south along the Mono-Alpine county line to the Mono-Tuolumne county line and the Inyo National Forest Boundary; south along the Inyo National Forest Boundary to the Inyo-Sierra Forest boundary; south along the Inyo-Sierra Forest boundary to the Fresno-Madera county line; north and east along the Fresno-Madera county line to the junction of the Fresno-Madera-Mono county line; south along the Mono-Fresno county line to the Mono-Inyo County line; east along the Mono-Inyo county line to the point of beginning.

--- Original source retains full ownership of the source dataset ---

Analysis of ‘Bear Hunt Areas [ds2807]’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/1cc72ee5-f617-4686-8e3f-4783f16b8374 on 27 January 2022.

--- Dataset description provided by original source is as follows ---

Except as provided in Section 366, bear may be taken only as follows:(a) Areas:(1) Northern California: In the counties of Del Norte, Humboldt, Plumas, Shasta, Siskiyou, Tehama and Trinity; and those portions of Lassen and Modoc counties west of the following line: Beginning at Highway 395 and the Sierra-Lassen county line; north on Highway 395 to the junction of Highway 36; west on Highway 36 to the junction of Highway 139; north on Highway 139 to Highway 299; north on Highway 299 to County Road 87; west on County Road 87 to Lookout-Hackamore Road; north on Lookout-Hackamore Road to Highway 139; north on Highway 139 to the Modoc-Siskiyou county line; north on the Modoc-Siskiyou county line to the Oregon border.(2) Central California: In the counties of Alpine, Amador, Butte, Calaveras, Colusa, El Dorado, Glenn, Lake, Mendocino, Nevada, Placer, Sacramento, Sierra, Sutter, Yolo and Yuba and those portions of Napa and Sonoma counties northeast of Highway 128.(3) Southern Sierra: That portion of Kern County west of Highway 14 and east of the following line: Beginning at the intersection of Highway 99 and the Kern-Tulare county line; south on Highway 99 to Highway 166; west and south on Highway 166 to the Kern-Santa Barbara county line; and those portions of Fresno, Madera, Mariposa, Merced, Stanislaus, Tulare and Tuolumne counties east of Highway 99.(4) Southern California: In the counties of Los Angeles, Santa Barbara and Ventura; that portion of Riverside County north of Interstate 10 and west of Highway 62; and that portion of San Bernardino County south and west of the following line: Beginning at the intersection of Highway 18 and the Los Angeles-San Bernardino county line; east along Highway 18 to Highway 247; southeast on Highway 247 to Highway 62; southwest along Highway 62 to the Riverside-San Bernardino county line.(5) Southeastern Sierra: Those portions of Inyo and Mono counties west of Highway 395; and that portion of Madera County within the following line: Beginning at the junction of the Fresno-Madera-Mono county lines; north and west along the Madera-Mono county line to the boundary of the Inyo-Sierra National Forest; south along the Inyo-Sierra National Forest boundary to the Fresno-Madera county line; north and east on the Fresno-Madera county line to the point of beginning. Also, that portion of Inyo county west of Highway 395; and that portion of Mono county beginning at the intersection of Highway 6 and the Mono county line; north along Highway 6 to the Nevada state line; north along the Nevada state line to the Alpine county line; south along the Mono-Alpine county line to the Mono-Tuolumne county line and the Inyo National Forest Boundary; south along the Inyo National Forest Boundary to the Inyo-Sierra Forest boundary; south along the Inyo-Sierra Forest boundary to the Fresno-Madera county line; north and east along the Fresno-Madera county line to the junction of the Fresno-Madera-Mono county line; south along the Mono-Fresno county line to the Mono-Inyo County line; east along the Mono-Inyo county line to the point of beginning.

--- Original source retains full ownership of the source dataset ---

Analysis of ‘Bear Hunt Areas [ds2807]’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/35eaa861-c0b5-4ca9-9b5a-f4ee25b81583 on 26 January 2022.

--- Dataset description provided by original source is as follows ---

Except as provided in Section 366, bear may be taken only as follows:(a) Areas:(1) Northern California: In the counties of Del Norte, Humboldt, Plumas, Shasta, Siskiyou, Tehama and Trinity; and those portions of Lassen and Modoc counties west of the following line: Beginning at Highway 395 and the Sierra-Lassen county line; north on Highway 395 to the junction of Highway 36; west on Highway 36 to the junction of Highway 139; north on Highway 139 to Highway 299; north on Highway 299 to County Road 87; west on County Road 87 to Lookout-Hackamore Road; north on Lookout-Hackamore Road to Highway 139; north on Highway 139 to the Modoc-Siskiyou county line; north on the Modoc-Siskiyou county line to the Oregon border.(2) Central California: In the counties of Alpine, Amador, Butte, Calaveras, Colusa, El Dorado, Glenn, Lake, Mendocino, Nevada, Placer, Sacramento, Sierra, Sutter, Yolo and Yuba and those portions of Napa and Sonoma counties northeast of Highway 128.(3) Southern Sierra: That portion of Kern County west of Highway 14 and east of the following line: Beginning at the intersection of Highway 99 and the Kern-Tulare county line; south on Highway 99 to Highway 166; west and south on Highway 166 to the Kern-Santa Barbara county line; and those portions of Fresno, Madera, Mariposa, Merced, Stanislaus, Tulare and Tuolumne counties east of Highway 99.(4) Southern California: In the counties of Los Angeles, Santa Barbara and Ventura; that portion of Riverside County north of Interstate 10 and west of Highway 62; and that portion of San Bernardino County south and west of the following line: Beginning at the intersection of Highway 18 and the Los Angeles-San Bernardino county line; east along Highway 18 to Highway 247; southeast on Highway 247 to Highway 62; southwest along Highway 62 to the Riverside-San Bernardino county line.(5) Southeastern Sierra: Those portions of Inyo and Mono counties west of Highway 395; and that portion of Madera County within the following line: Beginning at the junction of the Fresno-Madera-Mono county lines; north and west along the Madera-Mono county line to the boundary of the Inyo-Sierra National Forest; south along the Inyo-Sierra National Forest boundary to the Fresno-Madera county line; north and east on the Fresno-Madera county line to the point of beginning. Also, that portion of Inyo county west of Highway 395; and that portion of Mono county beginning at the intersection of Highway 6 and the Mono county line; north along Highway 6 to the Nevada state line; north along the Nevada state line to the Alpine county line; south along the Mono-Alpine county line to the Mono-Tuolumne county line and the Inyo National Forest Boundary; south along the Inyo National Forest Boundary to the Inyo-Sierra Forest boundary; south along the Inyo-Sierra Forest boundary to the Fresno-Madera county line; north and east along the Fresno-Madera county line to the junction of the Fresno-Madera-Mono county line; south along the Mono-Fresno county line to the Mono-Inyo County line; east along the Mono-Inyo county line to the point of beginning.

--- Original source retains full ownership of the source dataset ---

Except as provided in Section 366, bear may be taken only as follows:(a) Areas:(1) Northern California: In the counties of Del Norte, Humboldt, Plumas, Shasta, Siskiyou, Tehama and Trinity; and those portions of Lassen and Modoc counties west of the following line: Beginning at Highway 395 and the Sierra-Lassen county line; north on Highway 395 to the junction of Highway 36; west on Highway 36 to the junction of Highway 139; north on Highway 139 to Highway 299; north on Highway 299 to County Road 87; west on County Road 87 to Lookout-Hackamore Road; north on Lookout-Hackamore Road to Highway 139; north on Highway 139 to the Modoc-Siskiyou county line; north on the Modoc-Siskiyou county line to the Oregon border.(2) Central California: In the counties of Alpine, Amador, Butte, Calaveras, Colusa, El Dorado, Glenn, Lake, Mendocino, Nevada, Placer, Sacramento, Sierra, Sutter, Yolo and Yuba and those portions of Napa and Sonoma counties northeast of Highway 128.(3) Southern Sierra: That portion of Kern County west of Highway 14 and east of the following line: Beginning at the intersection of Highway 99 and the Kern-Tulare county line; south on Highway 99 to Highway 166; west and south on Highway 166 to the Kern-Santa Barbara county line; and those portions of Fresno, Madera, Mariposa, Merced, Stanislaus, Tulare and Tuolumne counties east of Highway 99.(4) Southern California: In the counties of Los Angeles, Santa Barbara and Ventura; that portion of Riverside County north of Interstate 10 and west of Highway 62; and that portion of San Bernardino County south and west of the following line: Beginning at the intersection of Highway 18 and the Los Angeles-San Bernardino county line; east along Highway 18 to Highway 247; southeast on Highway 247 to Highway 62; southwest along Highway 62 to the Riverside-San Bernardino county line.(5) Southeastern Sierra: Those portions of Inyo and Mono counties west of Highway 395; and that portion of Madera County within the following line: Beginning at the junction of the Fresno-Madera-Mono county lines; north and west along the Madera-Mono county line to the boundary of the Inyo-Sierra National Forest; south along the Inyo-Sierra National Forest boundary to the Fresno-Madera county line; north and east on the Fresno-Madera county line to the point of beginning. Also, that portion of Inyo county west of Highway 395; and that portion of Mono county beginning at the intersection of Highway 6 and the Mono county line; north along Highway 6 to the Nevada state line; north along the Nevada state line to the Alpine county line; south along the Mono-Alpine county line to the Mono-Tuolumne county line and the Inyo National Forest Boundary; south along the Inyo National Forest Boundary to the Inyo-Sierra Forest boundary; south along the Inyo-Sierra Forest boundary to the Fresno-Madera county line; north and east along the Fresno-Madera county line to the junction of the Fresno-Madera-Mono county line; south along the Mono-Fresno county line to the Mono-Inyo County line; east along the Mono-Inyo county line to the point of beginning.

This data set is a digital soil survey and generally is the most detailed level of soil geographic data developed by the National Cooperative Soil Survey. The information was prepared by digitizing maps, by compiling information onto a plan metric correct base and digitizing, or by revising digitized maps using remotely sensed and other information. This data set consists of georeferenced digital map data and computerized attribute data. The map data are in a soil survey area extent format and include a detailed, field verified inventory of soils and miscellaneous areas that normally occur in a repeatable pattern on the landscape and that can be cartographically shown at the scale mapped. A special soil features layer (point and line features) is optional. This layer displays the location of features too small to delineate at the mapping scale, but they are large enough and contrasting enough to significantly influence use and management. The soil map units are linked to attributes in the National Soil Information System relational database, which gives the proportionate extent of the component soils and their properties.

Sierra Nevada Conservancy (SNC) boundary. The boundary was mapped to correspond with statute AB 2600 (2004) and as re-defined in AB 1201 (2005). Work on the boundary was completed by CalFire, GreenInfo Network, and the California Department of Fish and Game. Meets and bounds description of the area as defined in statute: PRC Section 33302 (f) defines the Sierra Nevada Region as the area lying within the Counties of Alpine, Amador, Butte, Calaveras, El Dorado, Fresno, Inyo, Kern, Lassen, Madera, Mariposa, Modoc, Mono, Nevada, Placer, Plumas, Shasta, Sierra, Tehama, Tulare, Tuolumne, and Yuba, described as the area bounded as follows: On the east by the eastern boundary of the State of California; the crest of the White/Inyo ranges; and State Routes 395 and 14 south of Olancha; on the south by State Route 58, Tehachapi Creek, and Caliente Creek; on the west by the line of 1,250 feet above sea level from Caliente Creek to the Kern/Tulare County line; the lower level of the western slope's blue oak woodland, from the Kern/Tulare County line to the Sacramento River near the mouth of Seven-Mile Creek north of Red Bluff; the Sacramento River from Seven-Mile Creek north to Cow Creek below Redding; Cow Creek, Little Cow Creek, Dry Creek, and the Shasta National Forest portion of Bear Mountain Road, between the Sacramento River and Lake Shasta; the Pit River Arm of Shasta Lake; the northerly boundary of the Pit River watershed; the southerly and easterly boundaries of Siskiyou County; and within Modoc County, the easterly boundary of the Klamath River watershed; and on the north by the northern boundary of the State of California; excluding both of the following: (1) The Lake Tahoe Region, as described in Section 66905.5 of the Government Code, where it is defined as 'Region. '(2) The S

This geodatabase includes the boundaries of the California Natural Resource Agency’s State Conservancies. The collection of the State Conservancies boundaries was initiated in January 2012 by the Sierra Nevada Conservancy, and the geodatabase was updated in 2022 to include Sierra Nevada Conservancy boundary expansion. The geodatabase was constructed from GIS data requested from each of the State Conservancies. The following documentation describes the contacts who provided data, and where available, the type of spatial information provided. Baldwin Hills Conservancy: A shapefile of the Baldwin Hills Conservancy boundary was requested and received from Amanda Recinos, amanda@greeninfo.org, of GreenInfo Network on behalf of the Executive Officer of the Baldwin Hills Conservancy, David McNeill, on 10 January 2012. This boundary has not been modified from the original boundary provided. California State Coastal Conservancy: The California State Coastal Conservancy was updated by San Jenniches, sjenniches@scc.ca.gov, of the Coastal Conservancy in Fiscal Year 2014-2015. The SNC did not receive the boundary directly from the Coastal Conservancy; the feature class was provided by Nickolas Perez, Nickolas.Perez@water.ca.gov, of the California Natural Resources Agency to the SNC on 30 April 2015. Coachella Valley Mountains Conservancy: A shapefile of the Coachella Valley Mountains Conservancy boundary was requested and received fromKerrie Godrey, kgodfrey@cvmc.ca.gov, of the Coachella Valley Mountains Conservancy on 10 January 2012. This boundary has not been modified from the original boundary provided. Delta Conservancy: A shapefile of the legal Delta and Suisun Marsh boundaries were provided by Elisa Sabatina with the Delta Conservancy, Elisa.Sabatini@deltaconservancy.ca.gov, on 10 January 2012. This boundary has not been modified from the original boundary provided. Rivers and Mountains Conservancy (San Gabriel/Lower LA): A shapefile of the Rivers and Mountains Conservancy was provided by Luz Torres, ltorres@rmc.ca.gov, of the Rivers and Mountains Conservancy on 10 January 2012. This boundary has not been modified from the original boundary provided. San Diego River Conservancy: Michael Nelson, mnelson@sdrc.ca.gov, the Executive Officer of the San Diego River Conservancy reported via email on 11 January 2012 that no prior GIS boundary existed for the Conservancy. Mr. Nelson provided written consent to the SNC, via an email dated 11 January 2012, to develop the San Diego River Conservancy GIS boundary from a PDF document supplied by Mr. Nelson that showed the general location of the San Diego River Conservancy’s boundary as occupying a one half mile buffer from the San Diego River. This boundary has not been modified from the original boundary provided. San Joaquin River Conservancy: The San Joaquin River Conservancy boundary was created from using both the legislation description of the boundary and a pdf version of the San Joaquin River Conservancy boundary provided by Marile Colindres, marile.colindres@sjrc.ca.gov, of the San Joaquin Conservancy on 24 February 2012. This boundary has not been modified from the since the creation of the boundary from the legal description in 2012. Santa Monica Mountains Conservancy: The SNC was not able to acquire GIS data from the Santa Monica Mountains Conservancy staff; therefore, the SNC created a boundary to represent the Santa Moninca Mountains Conservancy by using the description of the Conservancy from their website. Specifically, the SNC used the text from their website to select watersheds for GIS boundary: “the Santa Monica Mountains Conservancy zone covers an area from the edge of the Mojave Desert to the Pacific Ocean. The zone encompasses the whole of the Santa Monica Mountains, the Simi Hills, the Verdugo Mountains and significant portions of the Santa Susana and San Gabriel Mountains. In addition, the Mountains Recreation and Conservation Authority also owns or manages thousands of acres in the Sierra Pelona Mountains and in the Whittier-Puente Hills. From north to south, these areas drain into the Santa Clara River, Calleguas Creek, numerous smaller coastal watersheds in the Santa Monica Mountains, and the Los Angeles River and Rio Hondo.The Sierra Nevada Conservancy (SNC) boundary was mapped to correspond with statute AB 2600 (2004) and as re-defined in SB 208 (2022). Work on the boundary was completed by CalFire, GreenInfo Network, and the California Department of Fish and Game. Meets and bounds description of the area as defined in statute: PRC Section 33302 (f) defines the Sierra Nevada Region as the area lying within the Counties of Alpine, Amador, Butte, Calaveras, El Dorado, Fresno, Inyo, Kern, Lassen, Madera, Mariposa, Modoc, Mono, Nevada, Placer, Plumas, Shasta, Sierra, Siskiyou, Tehama, Trinity, Tulare, Tuolumne, and Yuba, described as the area bounded as follows: On the east by the eastern boundary of the State of California; the crest of the White/Inyo ranges; and State Routes 395 and 14 south of Olancha; on the south by State Route 58, Tehachapi Creek, and Caliente Creek; on the west by the line of 1,250 feet above sea level from Caliente Creek to the Kern/Tulare County line; the lower level of the western slope’s blue oak woodland, from the Kern/Tulare County line to the Sacramento River near the mouth of Seven-Mile Creek north of Red Bluff; the Sacramento River from Seven-Mile Creek north to Cow Creek below Redding; Cow Creek, Little Cow Creek, Dry Creek, and up to the southern boundary of the Pit River watershed where Bear Creek Mountain Road and Dry Creek Road intersect; the southern boundary of the Pit River watershed; the western boundary of the upper Trinity watershed in the County of Trinity; on the north by the boundary of the upper Trinity watershed in the County of Trinity and the upper Sacramento, McCloud, and Pit River watersheds in the County of Siskiyou; and within the County of Modoc, the easterly boundary of the Klamath River watershed; and on the north in the County of Modoc by the northern boundary of the State of California; excluding both of the following: (1) The Lake Tahoe Region, as described in Section 6605.5 of the Government Code, where it is defined as "region" (2) The San Joaquin River Parkway, as described in Section 32510. According to GreenInfo Network and the California Department of Fish and Game, the blue oak woodland used to define a portion of the Sierra Nevada Conservancy's western boundary was delineated using referenced vegetation and imagery data.The Tahoe Conservancy boundary was created by using the Tahoe Regional Planning Agency (TRPA) boundary received from the Tahoe Conservancy staff and clipping the TRPA boundary to the State of California boundary, using the Teale Albers projection. The TRPA boundary was received by the SNC from the Tahoe Conservancy staff in 2011, and the Tahoe Conservancy boundary was created by the SNC in 2012. Notes:Some conservancy boundaries overlap.

The physical location covered by an interagency, dispatch center for the effective coordination, mobilization and demobilization of emergency management resources. A dispatch center actively supports incidents within its boundaries and the resources assigned to those incidents.07/28/2025 - Updated email for USIDCIC from SM.FS.idcic@usda.gov to idcic@firenet.gov; edited by JHobson01/23/2025 - Updated email for USCAANCC to firenet email; edited by KJHansen6/27/2023 - Tabular changes only. Edits by JHobson, NPS. For Taos Interagency Dispatch Center, change Email from pdl_r3_Taos_Dispatch_Center@fs.fed.us to nmtdc@firenet.gov. For Santa Fe Interagency Dispatch Center, change Email from nmsfc01dispatch@fs.fed.us to nmsfc@firenet.gov.For Missoula Interagency Dispatch Center, change Email from sm.fs.mtmdc@firenet.gov to mtmdc@firenet.gov.Albuquerque Interagency Dispatch Center, change Email from nmabc01.dispatch@usda.gov to nmabc@firenet.gov. 3/31/2023 - 4/4/2023 - Tabular changes only. DispLocation and GACCUnitID updated using Unit IDx information current as of 4/3/2023. Edits by JKuenzi, USFS. Text changes to table include:For GACCUnitID, change USNWCC to USORNWC.For GACCUnitID, change USUTGBCC to USUTGBC.For USAZPHC, change DispLocation from Phoenix, AZ, to Mesa, AZ.For USORCOC, change DispLocation from Prineville,OR, to Redmond, OR.For USOREIC, change DispLocation from Eugene, OR, to Springfield, OR.For USPRCIC, change DispLocation from Boqueron, PR, to Palmer de Rio, PR.For USUTNUC, change DispLocation from Salt Lake City, UT, to Draper, UT.For USVAVIC, change DispLocation from Roanoke, VA, to Charlottesville, VA.For USWYTDC, change DispLocation from Moose, WY, to Bondurant, WY.3/23/2023-3/24/2023 - Tabular changes only. ContactPhone updated using Unit IDx information current as of 3/24/2023. Text changes per Official Unit IDs list "Unit Idx Name" field supplied by Kara Stringer (Combined Dispatch Centers 03222023.xlsx), co-lead for NWCG Unit ID Committee. Edits by JKuenzi, USFS. Changes include:GACCName from "Southwest Coordination Center" to "Southwest Area Coordination Center"GACCName from "Southern California Geographic Area Coordination Center" to "Southern California Coordination Center"DispUnitID from USCAMRNC to USCAMRCCDispName from "Angeles Emergency Communication Center" to "Angeles Communication Center"DispName from "Bitterroot Interagency Dispatch Center" to "Bitterroot 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 "Coeur d'Alene Interagency Dispatch Center" to "Coeur d'Alene Dispatch 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 "Grass Valley Emergency Comm Center" to 'Grass Valley Interagency Emergency Command Center"DispName from "Great Falls Interagency Dispatch Center" to "Great Falls 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 "Las Vegas Interagency Communication Center" to "Las Vegas Interagency 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 "Mat-Su/Southwest Area Forestry Dispatch" to "Mat-Su/Southwest Area Dispatch"DispName from "Mid-Atlantic Coordination Center" to "Mid-Atlantic Interagency Coordination 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 "Owens Valley Interagency Communications Center" to "Owens Valley Interagency Command Center"DispName from "Plumas Emergency Communications Center" to "Plumas Emergency Communication 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 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 "Valdez-Copper River Area Forestry Dispatch" to "Valdez-Copper River Area Dispatch"DispName from 'Woodacre Emergency Command Center" to "Woodacre Headquarters 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 "Uinta Basin Interagency Fire Center" to "Uintah Basin Interagency Fire Center"DispName from "Wisconsin Interagency Dispatch Center (federal) /Wisconsin State Dispatch Center (state)" to "Wisconsin Interagency Dispatch Center"DispName from "Michigan Interagency Dispatch Center (federal) /Michigan State Dispatch Center (state)" to "Michigan Interagency Dispatch Center"DispName from "Fresno-Sierra Emergency Command Center" to "Sierra Interagency Communication Center"DispName from "Perris Emergency Command Center" to "Riverside Emergency Command 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 "Orville Emergency Command Center" to "Butte Emergency Command Center"DispName from "Saint Helena Emergency Command Center" to "Lake Napa Command Center" 1/11/2023 - Tabular and geospatial changes. USMTBFAC (Blackfeet Reservation) merged into USMTGDC (Great Falls Interagency Dispatch Center). USMTBFAC remains as 4th Tier Dispatch. USMTFHA (Flathead Reservation) merged into USMTMDC (Missoula Interagency Dispatch Center). USMTFHA remains as 4th Tier Dispatch. Changes made by Kat Sorenson, R1 Asst Aircraft Coordinator, and Kara Stringer, IRWIN Business Lead. Edits by JKuenzi.1/10/2023 - Tabular and geospatial changes. Two islands on west edge of John Day Dispatch area (USORJDCC) absorbed into USORCOC Dispatch per direction from Kaleigh Johnson (Asst Ctr Mgr), Jada Altman (Central Oregon Center Mgr), and Jerry Messinger (Air Tactical Group Supervisor). Update made to Dispatch and Initial Attack Frequency Zone boundaries. Edits by JKuenzi,11/08/2022 - Tabular and geospatial changes. Update made to Dispatch and Initial Attack Frequency Zone boundaries between Miles City Interagency Dispatch Center (USMTMCC) and Billings Interagency Dispatch Center (USMTBDC), along Big Horn and Rosebud County line near Little Wolf Mountains, per Kat Sorenson, R1 Asst Aircraft Coordinator, and Kelsey Pluhar, DNRC Asst. Center Manager at Miles City Interagency Dispatch Center. Area in Big Horn County is dispatched by MTMCC. Edits by JKuenzi,09/06/2022-09/26/2022 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southern California and Great Basin in the state of Nevada. Boundary modified between CAOVCC (Owens Valley Interagency Communications Center) and NVSFC (Sierra Front Interagency Dispatch Center), specifically between Queen Valley and Mono Valley. The team making the change is made up of Southern Calif (JTomaselli) and Great Basin (GDingman) GACCs, with input from Ian Mills and Lance Rosen (BLM). Changes proposed will be put into effect for the 2023 calendar year, and will also impact alignments of Initial Attack Frequency Zone boundaries and GACC boundaries in the area described. Initial edits provided by Ian Mills and Daniel Yarborough. Final edits by JKuenzi, USFS.A description of the change is as follows: The northwest end of changes start approximately 1 mile west of Mt Olsen and approximately 0.5 mile south of the Virginia Lakes area. Head northwest passing on the northeast side of Red Lake and the south side of Big Virginia Lake to follow HWY 395 North east to CA 270. East through Bodie to the CA/NV state line. Follows the CA/NV State Line south to HWY CA 167/NV 359. East on NV359 to where the HWY intersects the corner of FS/BLM land. Follows the FS/BLM boundary to the east and then south where it ties into the current GACC boundary.09/22/2022 - Tabular changes only. The DispLocation value of "Prineville, OR", was updated to "Redmond, OR", and the ContactPhone value was updated for Central Oregon Interagency Dispatch Ctr (USORCOC) per direction from Desraye Assali, Supervisory GIS Specialist in Region 6. The original correction had been made 9/30/2020, in the National Dispatch Office Location dataset, but had been missed in the National Dispatch Boundary dataset. Edits by JKuenzi, USFS.09/07/2022 - 09/08/2022 - Tabular and geospatial changes. Multiple boundaries modified in Northern Rockies GACC to bring lines closer in accordance with State boundaries. Information provided by Don Copple, State Fire Planning & Intelligence Program Manager for Montana Dept of Natural Resources & Conservation (DNRC), Kathy Pipkin, Northern Rockies GACC Center Manager, and Kat Sorenson, R1 Asst Aircraft Coordinator. Edits by JKuenzi, USFS. The following changes were made:Boundary changes made to the following: Bitterroot Interagency Dispatch Ctr (USMTBDC), Dillon Interagency Dispatch Ctr (USMTDDC), Flathead Dispatch (USMTFHA), Great Falls Interagency Dispatch Ctr