The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses. For more information on the NHDPlus dataset see the NHDPlus v2 User Guide.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territories not including Alaska.Geographic Extent: The United States not including Alaska, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American SamoaProjection: Web Mercator Auxiliary Sphere Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: EPA and USGSUpdate Frequency: There is new new data since this 2019 version, so no updates planned in the futurePublication Date: March 13, 2019Prior to publication, the NHDPlus network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the NHDPlus Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, On or Off Network (flowlines only), Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original NHDPlus dataset. No data values -9999 and -9998 were converted to Null values for many of the flowline fields.What can you do with this layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS OnlineAdd this layer to a map in the map viewer. The layer is limited to scales of approximately 1:1,000,000 or larger but a vector tile layer created from the same data can be used at smaller scales to produce a webmap that displays across the full range of scales. The layer or a map containing it can be used in an application. Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute. Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map. Use as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class. Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of the ArcGIS Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

This dataset lists the employee name and taxable benefit for personal use of City of Greater Sudbury Vehicle as travel expenses for the year 2023. Expenses are broken down in separate tabs by Quarter (Q1, Q2, Q3 and Q4). Data for other years is available in separate datasets. Updated quarterly when expenses are prepared.

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.

Purpose

County 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 Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. Cities 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 Buffers
4. Place Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places (Coming Soon)
   
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system
• Place Name: CDTFA incorporated (city) or county name
• County: 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 System
• GNIS_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 System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_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.

Accuracy

CDTFA"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

Private wells in this layer come from the Department of Environmental Conservation's Water Supply Data Composite. Managed by the Water Supply Division's Well Driller and Well Location Program, the database contains private well information submitted by Vermont licensed well drillers. Licensed well drillers have been required to submit well completion reports (well logs) to the state since 1966. Well tags have been required since 1986. NOTE: the data contained here is only as accurate as what was submitted - many wells were completed, but not reported, many reports have missing information, were recorded inaccurately or poorly located geographically. Help us improve our database. Click the appropriate link within the feature's attributes to report a missing/inaccurate well report.Data is updated daily.For the Lithology Reports associated with Private Wells, download the Lithology Reports here: Private Wells - Lithology Reports

SCAG has developed its regional geospatial dataset of land use information at the parcel-level (approximately five million parcels) for 197 local jurisdictions in its region. The regional land use dataset is developed (1) to aid in SCAG’s regional transportation planning, scenario planning and growth forecasting, (2) facilitate policy discussion on various planning issues, and (3) enhance information database to better serve SCAG member jurisdictions, research institutes, universities, developers, general public, etc. This is SCAG's 2016 regional land use dataset developed for the Final Connect SoCal, the 2020-2045 Regional Transportation Plan/Sustainable Communities Strategy (RTP/SCS), including general plan land use, specific plan land use, zoning code and existing land use. Please note this data was reviewed by local jurisdictions and reflects each jurisdiction's input received during the Connect SoCal Local Input and Envisioning Process.Note: This dataset is intended for planning purposes only, and SCAG shall incur no responsibility or liability as to the completeness, currentness, or accuracy of this information. SCAG assumes no responsibility arising from use of this information by individuals, businesses, or other public entities. The information is provided with no warranty of any kind, expressed or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Users should consult with each local jurisdiction directly to obtain the official land use information.Data DictionaryField NameData TypeField DescriptionOBJECTIDObject IDInternal feature numberShapeGeometryType of geometrySCAGUID16Text2016 SCAG unique identification numberSCAGUID12Text2012 SCAG unique identification numberAPNTextAssessor’s parcel numberCOUNTYTextCounty nameCOUNTY_IDDoubleCounty FIPS codeCITYTextCity nameCITY_IDDoubleCity FIPS codeACRESDoubleAcreage informationYEARDoubleDataset yearCITY_GP_COText2016 Jurisdiction’s general plan land use designationSCAG_GP_COText2016 SCAG general plan land use codeDENSITYDoubleAverage density of residential/housing development (dwelling unit per acre) permitted based on jurisdiction’s general planLOWDoubleMinimum density of residential/housing development permitted (dwelling unit per acre) based on jurisdiction’s general planHIGHDoubleMaximum density of residential/housing development permitted (dwelling unit per acre) based on jurisdiction’s general planYEAR_ADOPTDateYear when jurisdiction adopted/last updated current general plan land use elementGP12_CITYText2012 jurisdiction’s general plan land use designationGP12_SCAGText2012 SCAG general plan land use codeSP_NAMETextSpecific plan nameCITY_SP_COText2016 Jurisdiction’s specific plan land use designationSCAG_SP_COText2016 SCAG specific plan land use codeDENSITY_SPDoubleAverage density of residential/housing development (dwelling unit per acre) permitted based on jurisdiction’s specific planLOW_SPDoubleMinimum density of residential/housing development permitted (dwelling unit per acre) based on jurisdiction’s specific planHIGH_SPDoubleMaximum density of residential/housing development permitted (dwelling unit per acre) based on jurisdiction’s specific planYR_AD_SPDateYear when jurisdiction adopted/last updated current specific planSP_INDEXShort IntegerSpecific plan index ('0' = outside specific plan area; '1' = inside specific plan area)CITY_ZN_COText2016 Jurisdiction’s zoning codeSCAG_ZN_COText2016 SCAG zoning codeZN12_CITYText2012 jurisdiction’s zoning codeLU16Text2016 SCAG existing land use codeLU12Text2012 SCAG existing land use codeNOTESTextAdditional informationShape_LengthDoubleLength of feature in internal unitsShape_AreaDoubleArea of feature in internal units squared2016 SCAG Land Use CodesLegendLand Use DescriptionSingle Family Residential1110 Single Family Residential1111 High Density Single Family Residential (9 or more DUs/ac)1112 Medium Density Single Family Residential (3-8 DUs/ac)1113 Low Density Single Family Residential (2 or less DUs/ac)Multi-Family Residential1120 Multi-Family Residential1121 Mixed Multi-Family Residential1122 Duplexes, Triplexes and 2- or 3-Unit Condominiums and Townhouses1123 Low-Rise Apartments, Condominiums, and Townhouses1124 Medium-Rise Apartments and Condominiums1125 High-Rise Apartments and CondominiumsMobile Homes and Trailer Parks1130 Mobile Homes and Trailer Parks1131 Trailer Parks and Mobile Home Courts, High-Density1132 Mobile Home Courts and Subdivisions, Low-DensityMixed Residential1140 Mixed Residential1100 ResidentialRural Residential1150 Rural ResidentialGeneral Office1210 General Office Use1211 Low- and Medium-Rise Major Office Use1212 High-Rise Major Office Use1213 SkyscrapersCommercial and Services1200 Commercial and Services1220 Retail Stores and Commercial Services1221 Regional Shopping Center1222 Retail Centers (Non-Strip With Contiguous Interconnected Off-Street Parking)1223 Retail Strip Development1230 Other Commercial1231 Commercial Storage1232 Commercial Recreation1233 Hotels and MotelsFacilities1240 Public Facilities1241 Government Offices1242 Police and Sheriff Stations1243 Fire Stations1244 Major Medical Health Care Facilities1245 Religious Facilities1246 Other Public Facilities1247 Public Parking Facilities1250 Special Use Facilities1251 Correctional Facilities1252 Special Care Facilities1253 Other Special Use FacilitiesEducation1260 Educational Institutions1261 Pre-Schools/Day Care Centers1262 Elementary Schools1263 Junior or Intermediate High Schools1264 Senior High Schools1265 Colleges and Universities1266 Trade Schools and Professional Training FacilitiesMilitary Installations1270 Military Installations1271 Base (Built-up Area)1272 Vacant Area1273 Air Field1274 Former Base (Built-up Area)1275 Former Base Vacant Area1276 Former Base Air FieldIndustrial1300 Industrial1310 Light Industrial1311 Manufacturing, Assembly, and Industrial Services1312 Motion Picture and Television Studio Lots1313 Packing Houses and Grain Elevators1314 Research and Development1320 Heavy Industrial1321 Manufacturing1322 Petroleum Refining and Processing1323 Open Storage1324 Major Metal Processing1325 Chemical Processing1330 Extraction1331 Mineral Extraction - Other Than Oil and Gas1332 Mineral Extraction - Oil and Gas1340 Wholesaling and WarehousingTransportation, Communications, and Utilities1400 Transportation, Communications, and Utilities1410 Transportation1411 Airports1412 Railroads1413 Freeways and Major Roads1414 Park-and-Ride Lots1415 Bus Terminals and Yards1416 Truck Terminals1417 Harbor Facilities1418 Navigation Aids1420 Communication Facilities1430 Utility Facilities1431 Electrical Power Facilities1432 Solid Waste Disposal Facilities1433 Liquid Waste Disposal Facilities1434 Water Storage Facilities1435 Natural Gas and Petroleum Facilities1436 Water Transfer Facilities1437 Improved Flood Waterways and Structures1438 Mixed Utilities1440 Maintenance Yards1441 Bus Yards1442 Rail Yards1450 Mixed Transportation1460 Mixed Transportation and UtilityMixed Commercial and Industrial1500 Mixed Commercial and IndustrialMixed Residential and Commercial1600 Mixed Residential and Commercial1610 Residential-Oriented Residential/Commercial Mixed Use1620 Commercial-Oriented Residential/Commercial Mixed UseOpen Space and Recreation1800 Open Space and Recreation1810 Golf Courses1820 Local Parks and Recreation1830 Regional Parks and Recreation1840 Cemeteries1850 Wildlife Preserves and Sanctuaries1860 Specimen Gardens and Arboreta1870 Beach Parks1880 Other Open Space and Recreation1890 Off-Street TrailsAgriculture2000 Agriculture2100 Cropland and Improved Pasture Land2110 Irrigated Cropland and Improved Pasture Land2120 Non-Irrigated Cropland and Improved Pasture Land2200 Orchards and Vineyards2300 Nurseries2400 Dairy, Intensive Livestock, and Associated Facilities2500 Poultry Operations2600 Other Agriculture2700 Horse RanchesVacant3000 Vacant3100 Vacant Undifferentiated3200 Abandoned Orchards and Vineyards3300 Vacant With Limited Improvements3400 Beaches (Vacant)1900 Urban VacantWater4000 Water4100 Water, Undifferentiated4200 Harbor Water Facilities4300 Marina Water Facilities4400 Water Within a Military Installation4500 Area of Inundation (High Water)Specific Plan7777 Specific PlanUnder Construction1700 Under ConstructionUndevelopable or Protected Land8888 Undevelopable or Protected LandUnknown9999 Unknown

These geocoded locations are based on the Allegheny County extract of Educational Names & Addresses (EdNA) via Pennsylvania Department of Education website as of April 19, 2018. Several addresses were not able to be geocoded (ex. If PO Box addresses were provided, they were not geocoded.)If viewing this description on the Western Pennsylvania Regional Data Center’s open data portal (http://www.wprdc.org), this dataset is harvested on a weekly basis from Allegheny County’s GIS data portal (http://openac.alcogis.opendata.arcgis.com/). The full metadata record for this dataset can also be found on Allegheny County’s GIS portal. You can access the metadata record and other resources on the GIS portal by clicking on the “Explore” button (and choosing the “Go to resource” option) to the right of the “ArcGIS Open Dataset” text below. Category: Education Organization: Allegheny County Department: Department of Human Services Temporal Coverage: as of April 19, 2018 Data Notes: Coordinate System: GCS_North_American_1983 Development Notes: none Other: none Related Document(s): Data Dictionary - none Frequency - Data Change: April, 19, 2018 data Frequency - Publishing: one-time Data Steward Name: See http://www.edna.ed.state.pa.us/Screens/Extracts/wfExtractEntitiesAdmin.aspx for more information. Data Steward Email: RA-DDQDataCollection@pa.gov (Data Collection Team)

All applicants for a Basic Business License operating from a residential location the District of Columbia must provide a Home Occupation (HOP) for the premise address from which the business activity is conducted in order to demonstrate the activity does not conflict with building and zoning codes. A home occupation is a business, profession or other economic activity conducted full- or part-time in the principal residence of the person conducting the business. This permit is required for operating a business from a residential home.

Note: The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services beginning in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.

Purpose

County boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.

This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This layer removes the coastal buffer polygons. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
3. Cities 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
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, gis@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_COUNTY: 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.
• CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.
• CENSUS_GEOID: numeric geographic identifiers from the US Census Bureau
• CENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.
• GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.
• CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.
• AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or county
• CENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.
• 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.

Jurisdictional Unit, 2022-05-21. For use with WFDSS, IFTDSS, IRWIN, and InFORM.This is a feature service which provides Identify and Copy Feature capabilities. If fast-drawing at coarse zoom levels is a requirement, consider using the tile (map) service layer located at https://nifc.maps.arcgis.com/home/item.html?id=3b2c5daad00742cd9f9b676c09d03d13.OverviewThe Jurisdictional Agencies dataset is developed as a national land management geospatial layer, focused on representing wildland fire jurisdictional responsibility, for interagency wildland fire applications, including WFDSS (Wildland Fire Decision Support System), IFTDSS (Interagency Fuels Treatment Decision Support System), IRWIN (Interagency Reporting of Wildland Fire Information), and InFORM (Interagency Fire Occurrence Reporting Modules). It is intended to provide federal wildland fire jurisdictional boundaries on a national scale. The agency and unit names are an indication of the primary manager name and unit name, respectively, recognizing that:There may be multiple owner names.Jurisdiction may be held jointly by agencies at different levels of government (ie State and Local), especially on private lands, Some owner names may be blocked for security reasons.Some jurisdictions may not allow the distribution of owner names. Private ownerships are shown in this layer with JurisdictionalUnitIdentifier=null,JurisdictionalUnitAgency=null, JurisdictionalUnitKind=null, and LandownerKind="Private", LandownerCategory="Private". All land inside the US country boundary is covered by a polygon.Jurisdiction for privately owned land varies widely depending on state, county, or local laws and ordinances, fire workload, and other factors, and is not available in a national dataset in most cases.For publicly held lands the agency name is the surface managing agency, such as Bureau of Land Management, United States Forest Service, etc. The unit name refers to the descriptive name of the polygon (i.e. Northern California District, Boise National Forest, etc.).These data are used to automatically populate fields on the WFDSS Incident Information page.This data layer implements the NWCG Jurisdictional Unit Polygon Geospatial Data Layer Standard.Relevant NWCG Definitions and StandardsUnit2. A generic term that represents an organizational entity that only has meaning when it is contextualized by a descriptor, e.g. jurisdictional.Definition Extension: When referring to an organizational entity, a unit refers to the smallest area or lowest level. Higher levels of an organization (region, agency, department, etc) can be derived from a unit based on organization hierarchy.Unit, JurisdictionalThe governmental entity having overall land and resource management responsibility for a specific geographical area as provided by law.Definition Extension: 1) Ultimately responsible for the fire report to account for statistical fire occurrence; 2) Responsible for setting fire management objectives; 3) Jurisdiction cannot be re-assigned by agreement; 4) The nature and extent of the incident determines jurisdiction (for example, Wildfire vs. All Hazard); 5) Responsible for signing a Delegation of Authority to the Incident Commander.See also: Unit, Protecting; LandownerUnit IdentifierThis data standard specifies the standard format and rules for Unit Identifier, a code used within the wildland fire community to uniquely identify a particular government organizational unit.Landowner Kind & CategoryThis data standard provides a two-tier classification (kind and category) of landownership. Attribute Fields JurisdictionalAgencyKind Describes the type of unit Jurisdiction using the NWCG Landowner Kind data standard. There are two valid values: Federal, and Other. A value may not be populated for all polygons.JurisdictionalAgencyCategoryDescribes the type of unit Jurisdiction using the NWCG Landowner Category data standard. Valid values include: ANCSA, BIA, BLM, BOR, DOD, DOE, NPS, USFS, USFWS, Foreign, Tribal, City, County, OtherLoc (other local, not in the standard), State. A value may not be populated for all polygons.JurisdictionalUnitNameThe name of the Jurisdictional Unit. Where an NWCG Unit ID exists for a polygon, this is the name used in the Name field from the NWCG Unit ID database. Where no NWCG Unit ID exists, this is the “Unit Name” or other specific, descriptive unit name field from the source dataset. A value is populated for all polygons.JurisdictionalUnitIDWhere it could be determined, this is the NWCG Standard Unit Identifier (Unit ID). Where it is unknown, the value is ‘Null’. Null Unit IDs can occur because a unit may not have a Unit ID, or because one could not be reliably determined from the source data. Not every land ownership has an NWCG Unit ID. Unit ID assignment rules are available from the Unit ID standard, linked above.LandownerKindThe landowner category value associated with the polygon. May be inferred from jurisdictional agency, or by lack of a jurisdictional agency. A value is populated for all polygons. There are three valid values: Federal, Private, or Other.LandownerCategoryThe landowner kind value associated with the polygon. May be inferred from jurisdictional agency, or by lack of a jurisdictional agency. A value is populated for all polygons. Valid values include: ANCSA, BIA, BLM, BOR, DOD, DOE, NPS, USFS, USFWS, Foreign, Tribal, City, County, OtherLoc (other local, not in the standard), State, Private.DataSourceThe database from which the polygon originated. Be as specific as possible, identify the geodatabase name and feature class in which the polygon originated.SecondaryDataSourceIf the Data Source is an aggregation from other sources, use this field to specify the source that supplied data to the aggregation. For example, if Data Source is "PAD-US 2.1", then for a USDA Forest Service polygon, the Secondary Data Source would be "USDA FS Automated Lands Program (ALP)". For a BLM polygon in the same dataset, Secondary Source would be "Surface Management Agency (SMA)."SourceUniqueIDIdentifier (GUID or ObjectID) in the data source. Used to trace the polygon back to its authoritative source.MapMethod:Controlled vocabulary to define how the geospatial feature was derived. Map method may help define data quality. MapMethod will be Mixed Method by default for this layer as the data are from mixed sources. Valid Values include: GPS-Driven; GPS-Flight; GPS-Walked; GPS-Walked/Driven; GPS-Unknown Travel Method; Hand Sketch; Digitized-Image; DigitizedTopo; Digitized-Other; Image Interpretation; Infrared Image; Modeled; Mixed Methods; Remote Sensing Derived; Survey/GCDB/Cadastral; Vector; Phone/Tablet; OtherDateCurrentThe last edit, update, of this GIS record. Date should follow the assigned NWCG Date Time data standard, using 24 hour clock, YYYY-MM-DDhh.mm.ssZ, ISO8601 Standard.CommentsAdditional information describing the feature. GeometryIDPrimary key for linking geospatial objects with other database systems. Required for every feature. This field may be renamed for each standard to fit the feature.JurisdictionalUnitID_sansUSNWCG Unit ID with the "US" characters removed from the beginning. Provided for backwards compatibility.JoinMethodAdditional information on how the polygon was matched information in the NWCG Unit ID database.LocalNameLocalName for the polygon provided from PADUS or other source.LegendJurisdictionalAgencyJurisdictional Agency but smaller landholding agencies, or agencies of indeterminate status are grouped for more intuitive use in a map legend or summary table.LegendLandownerAgencyLandowner Agency but smaller landholding agencies, or agencies of indeterminate status are grouped for more intuitive use in a map legend or summary table.DataSourceYearYear that the source data for the polygon were acquired.Data InputThis dataset is based on an aggregation of 4 spatial data sources: Protected Areas Database US (PAD-US 2.1), data from Bureau of Indian Affairs regional offices, the BLM Alaska Fire Service/State of Alaska, and Census Block-Group Geometry. NWCG Unit ID and Agency Kind/Category data are tabular and sourced from UnitIDActive.txt, in the WFMI Unit ID application (https://wfmi.nifc.gov/unit_id/Publish.html). Areas of with unknown Landowner Kind/Category and Jurisdictional Agency Kind/Category are assigned LandownerKind and LandownerCategory values of "Private" by use of the non-water polygons from the Census Block-Group geometry.PAD-US 2.1:This dataset is based in large part on the USGS Protected Areas Database of the United States - PAD-US 2.`. PAD-US is a compilation of authoritative protected areas data between agencies and organizations that ultimately results in a comprehensive and accurate inventory of protected areas for the United States to meet a variety of needs (e.g. conservation, recreation, public health, transportation, energy siting, ecological, or watershed assessments and planning). Extensive documentation on PAD-US processes and data sources is available.How these data were aggregated:Boundaries, and their descriptors, available in spatial databases (i.e. shapefiles or geodatabase feature classes) from land management agencies are the desired and primary data sources in PAD-US. If these authoritative sources are unavailable, or the agency recommends another source, data may be incorporated by other aggregators such as non-governmental organizations. Data sources are tracked for each record in the PAD-US geodatabase (see below).BIA and Tribal Data:BIA and Tribal land management data are not available in PAD-US. As such, data were aggregated from BIA regional offices. These data date from 2012 and were substantially updated in 2022. Indian Trust Land affiliated with Tribes, Reservations, or BIA Agencies: These data are not considered the system of record and are not intended to be used as such. The Bureau of Indian Affairs (BIA), Branch of Wildland Fire Management (BWFM) is not the originator of these data. The

Note: The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services beginning in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.

Purpose
County boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.

This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers (this dataset)
   • Without Coastal Buffers
3. Cities 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
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)
   • 
     

Point of Contact

California Department of Technology, Office of Digital Services, gis@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_COUNTY: 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.
• CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.
• CENSUS_GEOID: numeric geographic identifiers from the US Census Bureau
• CENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.
• GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.
• CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.
• AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or county
• CENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.
• 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.

Low with indicative cycling distances and cycling times to the city centre (centre Stadspark). Low with range zones of (planned) velostations at 5 min / 400m walk. (see also geodata-portal - https://geoportaal.antwerpen.be/portal/home/search.html?q=velo , open geodata-portal - http://portal-stadantwerpen.opendata.arcgis.com/datasets?q=velo ) quantified in city in figures - https://stadinaantal.antwerpen.be/Databank/Jive/?workspace_guid=69b8bda6-60e6-4f4c-a92d-33dfb1c3b43b ) Low with reach zones of (planned) neighbourhood bicycle parkings at 2 min/ 150m walk. (see also geodata-portal - https://geoportaal.antwerpen.be/portal/home/search.html?q=neighbourly bicycle parking , open geodata-portal - http://portal-stadantwerpen.opendata.arcgis.com/datasets?q=neighbourly bicycle parking ) numerically - https://stadinaantal.antwerpen.be/Databank/Jive/?workspace_guid=e4edca4c-2f63-43ce-b307-a11b9114d5d4 ) Low with reach zones of street bicycle parking (bicycle brackets) at 2 min/150m walking. (see also geodata-portal - https://geoportaal.antwerpen.be/portal/home/search.html?q=neighbourly bicycle parking , open geodata-portal - http://portal-stadantwerpen.opendata.arcgis.com/datasets?q=neighbourly bicycle parking ) quantified in city in figures - city%20in%20figures) ) Low with range zones of guarded bicycle parkings at 5 min/ 400m, 15 min/ 1km walking and 15 min/ 3km cycling. (see also geodata-portal - https://geoportaal.antwerpen.be/portal/home/search.html?q=neighbourly bicycle parking , open geodata-portal - http://portal-stadantwerpen.opendata.arcgis.com/datasets?q=neighbourly bicycle parking ) numerically - https://stadinaantal.antwerpen.be/Databank/Jive/?workspace_guid=a8bce82c-8a54-48fc-8f2a-39451e97a470 ) These data layers are updated annually in January, provided that the facility is managed and updated annually by the relevant sector/service. Because the center of the City Park is considered the center of the city, the following concentric buffers are drawn around it: 1 km of bird's eye view reflects 1 , 2 5 km of actual cycling distance or 5 min . cycling (at 15 km/h by regular bicycle ). 2 km of bird's eye view reflects 2.5 km of actual cycling distance or 10 min . cycling (at 15 km/h by regular bicycle ). 3 km of bird's eye view reflects 3.75 km of actual cycling distance or 15 min . cycling (at 15 km/h by regular bicycle ). 4 km of bird's eye view reflects 5 km of actual cycling distance or 20 min . cycling (at 15 km/h by regular bicycle ). 5 km of bird's eye view reflects 6.75 km of actual cycling distance or 25 min . cycling (at 15 km/h by regular bicycle ). 6 km of bird's eye view reflects 7.5 km of actual cycling distance or 30 min . cycling (at 15 km/h by regular bicycle ). 8 km of bird's eye view reflects 10 km of actual cycling distance or 4 0 min . cycling (at 15 km/h by regular bicycle ). 10 km of bird's eye view reflects 12.5 km of actual cycling distance or 5 0 min . cycling (at 15 km/h with regular bike ) / 38 min . bicycles (at 20 km/h with electric bike ) / 25 min . cycling (at 30 km/h with speed pedelec ) . 20 km of bird's eye view reflects 25 km of actual cycling distance or 10 0 min . cycling (at 15 km/h with regular bike ) / 75 min . bicycles (at 20 km/h with electric bike ) / 50 min . cycling (at 30 km/h with speed pedelec ) . 30 km of bird's eye view reflects 37.5 km of actual cycling distance or 15 0 min . cycling (at 15 km/h with regular bike ) / 113 min . bicycles (at 20 km/h with electric bike ) / 75 min . cycling (at 30 km/h with speed pedelec ) .

The Address Coordinator in the Planning Department assigns new addresses during the application review process per the address manual. The status field can be used to filter out valid addresses. The True, Multi, Corner (status will be changed to true when the building configuration is identified), and Model values are all valid addresses.Other Statuses:Preliminary - subdivision addresses assigned during the review process and are not official until the plat is recorded; Temporary - addresses assigned to power poles and construction trailers during the building process; Land - addresses for undeveloped properties; Range - used to aid the address coordinator in assigning new addresses when calculating the address range on a new street segment; Retired - former addresses that are no longer in use like shopping center reconfigurations.Use field: This field helps clarify what the address is representing such as power meters for subdivision fountains or pump houses in multi-family developments.The address field is a concatenation of the individual address fields except for the unit number (field name = Units).Address with suffix field concatenates the address number and any suffix for use in geocoders.

The project lead for the collection of this data was Carrington Hilson. Elk (3 adult females) were captured and equipped with GPS collars (Lotek Iridium) transmitting data from 2017-2021. The Davison herd does not migrate between traditional summer and winter seasonal ranges. Therefore, annual home ranges were modeled using year-round data to demarcate high use areas in lieu of modeling the specific winter ranges commonly seen in other ungulate analyses in California. GPS locations were fixed between 1-6 hour intervals in the dataset. To improve the quality of the data set as per Bjørneraas et al. (2010), the GPS data were filtered prior to analysis to remove locations which were: i) further from either the previous point or subsequent point than an individual pronghorn is able to travel in the elapsed time, ii) forming spikes in the movement trajectory based on outgoing and incoming speeds and turning angles sharper than a predefined threshold , or iii) fixed in 2D space and visually assessed as a bad fix by the analyst. The methodology used for this migration analysis allowed for the mapping of the herd’s home range. Brownian bridge movement models (BBMMs; Sawyer et al. 2009) were constructed with GPS collar data from 3 elk, including 9 annual home range sequences, location, date, time, and average location error as inputs in Migration Mapper. BBMMs were produced at a spatial resolution of 50 m using a sequential fix interval of less than 27 hours. Large water bodies were clipped from the final output. Home range is visualized as the 50th percentile contour (high use) and the 99th percentile contour of the year-round utilization distribution. Home range designations for this herd may expand with a larger sample.

The project lead for the collection of this data was Carrington Hilson. Elk (3 adult females) were captured and equipped with GPS collars (Lotek Iridium) transmitting data from 2017-2021. The Red Schoolhouse herd does not migrate between traditional summer and winter seasonal ranges. Therefore, annual home ranges were modeled using year-round data to demarcate high use areas in lieu of modeling the specific winter ranges commonly seen in other ungulate analyses in California. GPS locations were fixed between 1-6 hour intervals in the dataset. To improve the quality of the data set as per Bjørneraas et al. (2010), the GPS data were filtered prior to analysis to remove locations which were: i) further from either the previous point or subsequent point than an individual pronghorn is able to travel in the elapsed time, ii) forming spikes in the movement trajectory based on outgoing and incoming speeds and turning angles sharper than a predefined threshold , or iii) fixed in 2D space and visually assessed as a bad fix by the analyst. The methodology used for this migration analysis allowed for the mapping of the herd’s home range. Brownian bridge movement models (BBMMs; Sawyer et al. 2009) were constructed with GPS collar data from 3 elk, including 7 annual home range sequences, location, date, time, and average location error as inputs in Migration Mapper. BBMMs were produced at a spatial resolution of 50 m using a sequential fix interval of less than 27 hours. Large water bodies were clipped from the final output. Home range is visualized as the 50th percentile contour (high use) and the 99th percentile contour of the year-round utilization distribution. Home range designations for this herd may expand with a larger sample.

The geospatial data reflected in the protected area layer mostly pertain to natural and wilderness areas where development of utility-scale renewable energy is prohibited and were heavily based on RETI 1.0 blackout areas.1 The protected area layer is distinguished for solar PV technology by the BLM greater sage grouse habitat management area which provides separate exclusion areas for the different technology types. Tables 1 and 2 below lists the data sources and precise selection query for each dataset, if applicable, that make up the protected area layer.Table 1: Datasets used in the Protected Area Layer Dataset Example Designations Citation or hyperlink PAD-US (CBI Edition) National Parks, GAP Status 1 and 2, State Parks, Open Spaces, Natural Areas “PAD-US (CBI Edition) Version 2.1b, California”. Conservation Biology Institute. 2016. https://databasin.org/datasets/64538491f43e42ba83e26b849f2cad28. Conservation Easements California Conservation Easement Database (CCED), 2022a. 2022. www.CALands.org. Accessed December 2022. Inventoried Roadless Areas “Inventoried Roadless Areas.” US Forest Service. Dec 12, 2022. https://www.fs.usda.gov/detail/roadless/2001roadlessrule/maps/?cid=stelprdb5382437 BLM National Landscape Conservation System Wilderness Areas, Wilderness Study Areas, National Monuments, National Conservation Lands, Conservation Lands of the California Desert, Scenic Rivers https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-wilderness-areas https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-wilderness-study-areas https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-national-monuments-nca-forest-reserves-other-poly/ Greater Sage Grouse Habitat Conservation Areas (BLM) For solar technology: BLM_Managm IN (‘PHMA’, ‘GHMA’, ‘OHMA’) For wind technology: BLMP_Managm = ‘PHMA’ “Nevada and Northeastern California Greater Sage-Grouse Approved Resource Management Plan Amendment.” US Department of the Interior Bureau of Land Management Nevada State Office. 2015. https://eplanning.blm.gov/public_projects/lup/103343/143707/176908/NVCA_Approved_RMP_Amendment.pdf Other BLM Protected Areas Areas of Critical Environmental Concern (ACECs), Recreation Areas (SRMA, ERMA, OHV Designated Areas), including Vinagre Wash Special Recreation Management Area, National Scenic Areas, including Alabama Hills National Scenic Area https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-off-highway-vehicle-designations

The datasets that are included in the composite layer making up the protected area layer are given below: Dataset Example Designations Citation or hyperlink PAD-US (CBI Edition) National Parks, GAP Status 1 and 2, State Parks, Open Spaces, Natural Areas “PAD-US (CBI Edition) Version 2.1b, California”. Conservation Biology Institute. 2016. https://databasin.org/datasets/64538491f43e42ba83e26b849f2cad28. Conservation Easements California Conservation Easement Database (CCED), 2022a. 2022. www.CALands.org. Accessed December 2022. Inventoried Roadless Areas “Inventoried Roadless Areas.” US Forest Service. Dec 12, 2022. https://www.fs.usda.gov/detail/roadless/2001roadlessrule/maps/?cid=stelprdb5382437 BLM National Landscape Conservation System Wilderness Areas, Wilderness Study Areas, National Monuments, National Conservation Lands, Conservation Lands of the California Desert, Scenic Rivers https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-wilderness-areas https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-wilderness-study-areas https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-national-monuments-nca-forest-reserves-other-poly/ Greater Sage Grouse Habitat Conservation Areas (BLM) For solar technology: BLM_Managm IN (‘PHMA’, ‘GHMA’, ‘OHMA’) For wind technology: BLMP_Managm = ‘PHMA’ “Nevada and Northeastern California Greater Sage-Grouse Approved Resource Management Plan Amendment.” US Department of the Interior Bureau of Land Management Nevada State Office. 2015. https://eplanning.blm.gov/public_projects/lup/103343/143707/176908/NVCA_Approved_RMP_Amendment.pdf Other BLM Protected Areas Areas of Critical Environmental Concern (ACECs), Recreation Areas (SRMA, ERMA, OHV Designated Areas), including Vinagre Wash Special Recreation Management Area, National Scenic Areas, including Alabama Hills National Scenic Area https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-off-highway-vehicle-designations https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ca-areas-of-critical-environmental-concern https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-az-area-of-critical-environmental-concern-polygon [Big Marias ACEC and Beale Slough Riparian and Cultural ACEC] BLM, personal communication, November 2, 2022. Mono Basin NFSA https://pcta.maps.arcgis.com/home/item.html?id=cf1495f8e09940989995c06f9e290f6b#overview Terrestrial 30x30 Conserved Areas Gap Status 1 and 2 CA Nature. 30x30 Conserved Areas, Terrestrial. 2021. https://www.californianature.ca.gov/datasets/CAnature::30x30-conserved-areas-terrestrial/ Accessed September 2022. CPAD Open Spaces and Parks under city or county level California Protected Areas Database (CPAD), 2022b. 2022. https://www.calands.org/cpad/. Accessed February 22, 2023. USFS Special Interest Management Areas https://data-usfs.hub.arcgis.com/datasets/usfs::special-interest-management-areas-feature-layer/about Proposed Protected Area Molok Luyuk Extension (Berryessa Mtn NM Expansion) CalWild, personal communication, January 19, 2023. This layer is featured in the CEC 2023 Land-Use Screens for Electric System Planning data viewer.For more information about this layer and its use in electric system planning, please refer to the Land Use Screens Staff Report in the CEC Energy Planning Library. Change Log: Version 1.1 (January 22, 2024 10:40 AM) Layer revised to allow for gaps to remain when combining all components of the protected area layer.

The project leads for the collection of this data were Josh Bush and Tom Batter. Elk (8 adult females, 11 adult males) from the Bear Creek Ranch – Antelope Valley herd were captured and equipped with Lotek GPS collars (LifeCycle 800 GlobalStar, Lotek Wireless, Newmarket, Ontario, Canada), transmitting data from 2017-2022. The study area was within the Bear Valley and Cache Creek Elk Management Units, west of Route 20 south to Wilber Springs, where certain individuals appear to cross this highway. Route 20 is likely a barrier to movement to the east as this herd does not overlap with the Cortina Ridge herd on the other side of this highway. The Bear Creek Ranch – Antelope Valleyherd contains short distance, elevation-based movements likely due to seasonal habitat conditions, but this herd does not migrate between traditional summer and winter seasonal ranges. Instead, the herd displays a residential pattern, slowly moving up or down elevational gradients. Therefore, annual home ranges were modeled using year-round data to demarcate high use areas in lieu of modeling the specific winter ranges commonly seen in other ungulate analyses in California. GPS locations were fixed at 13-hour intervals in the dataset. To improve the quality of the data set as per Bjørneraas et al. (2010), the GPS data were filtered prior to analysis to remove locations which were: i) further from either the previous point or subsequent point than an individual elk is able to travel in the elapsed time, ii) forming spikes in the movement trajectory based on outgoing and incoming speeds and turning angles sharper than a predefined threshold , or iii) fixed in 2D space and visually assessed as a bad fix by the analyst. The methodology used for this analysis allowed for the mapping of the herd’s annual range based on a small sample. Brownian Bridge Movement Models (BBMMs; Sawyer et al. 2009) were constructed with GPS collar data from 17 elk in total, including 37 year-long sequences, location, date, time, and average location error as inputs in Migration Mapper to assess annual range. Annual range BBMMs were produced at a spatial resolution of 50 m using a sequential fix interval of less than 27 hours. Population-level annual range designations for this herd may expand with a larger sample, filling in some of the gaps between high-use annual range polygons in the map. Annual range is visualized as the 50th percentile contour (high use) and the 99th percentile contour of the year-round utilization distribution.

The project lead for the collection of this data was Carrington Hilson. Elk (3 adult females) were captured and equipped with GPS collars (Lotek Iridium) transmitting data from 2017-2021. The Camp Lincoln herd does not migrate between traditional summer and winter seasonal ranges. Therefore, annual home ranges were modeled using year-round data to demarcate high use areas in lieu of modeling the specific winter ranges commonly seen in other ungulate analyses in California. GPS locations were fixed between 1-6 hour intervals in the dataset. To improve the quality of the data set as per Bjørneraas et al. (2010), the GPS data were filtered prior to analysis to remove locations which were: i) further from either the previous point or subsequent point than an individual pronghorn is able to travel in the elapsed time, ii) forming spikes in the movement trajectory based on outgoing and incoming speeds and turning angles sharper than a predefined threshold , or iii) fixed in 2D space and visually assessed as a bad fix by the analyst. The methodology used for this migration analysis allowed for the mapping of the herd’s home range. Brownian bridge movement models (BBMMs; Sawyer et al. 2009) were constructed with GPS collar data from 3 elk, including 4 annual home range sequences, location, date, time, and average location error as inputs in Migration Mapper. BBMMs were produced at a spatial resolution of 50 m using a sequential fix interval of less than 27 hours. Large water bodies were clipped from the final output. Home range is visualized as the 50th percentile contour (high use) and the 99th percentile contour of the year-round utilization distribution. Home range designations for this herd may expand with a larger sample.

Points of Diversion (POD): Depicts the location of each water right diversion point (POD) and provides basic information about the associated water right. All current and individually held water rights are shown in this data set except for those held by irrigation districts, applications, temporary transfers, instream leases, and limited licenses.Current code definitions at: https://www.oregon.gov/owrd/WRDFormsPDF/wris_code_key.pdf.Compilation procedures document at: https://arcgis.wrd.state.or.us/data/OWRD_WR_GIS_procedures.pdf. ----- Places of Use (POU): Depicts the location of each water right place of use (POU) polygon and provides basic information about the associated water right. All current and individually held water rights are shown in this data set except for those held by irrigation districts, applications, temporary transfers, instream leases, and limited licenses.Current code definitions at: https://www.oregon.gov/owrd/WRDFormsPDF/wris_code_key.pdf.Compilation procedures document at: https://arcgis.wrd.state.or.us/data/OWRD_WR_GIS_procedures.pdf.

Shows land use areas in unincorporated areas of San Mateo County according to the County's General Plan.