These data are a polygon feature class that represents the administrative boundaries of the US Forest Service Research and Development Stations. These territories consist of a collection of states' geographic areas, within which all research and development facilities and lands are managed by a station headquarters.

(Link to Metadata) The BNDHASH dataset depicts Vermont village, town, county, and Regional Planning Commission (RPC) boundaries. It is a composite of generally 'best available' boundaries from various data sources (refer to ARC_SRC and SRC_NOTES attributes). However, this dataset DOES NOT attempt to provide a legally definitive boundary. The layer was originally developed from TBHASH, which was the master VGIS town boundary layer prior to the development and release of BNDHASH. By integrating village, town, county, RPC, and state boundaries into a single layer, VCGI has assured vertical integration of these boundaries and simplified maintenance. BNDHASH also includes annotation text for town, county, and RPC names. BNDHASH includes the following feature classes: 1) BNDHASH_POLY_VILLAGES = Vermont villages 2) BNDHASH_POLY_TOWNS = Vermont towns 3) BNDHASH_POLY_COUNTIES = Vermont counties 4) BNDHASH_POLY_RPCS = Vermont's Regional Planning Commissions 5) BNDHASH_POLY_VTBND = Vermont's state boundary 6) BNDHASH_LINE = Lines on which all POLY feature classes are built The master BNDHASH data is managed as an ESRI geodatabase feature dataset by VCGI. The dataset stores village, town, county, RPC, and state boundaries as seperate feature classes with a set of topology rules which binds the features. This arrangement assures vertical integration of the various boundaries. VCGI will update this layer on an annual basis by reviewing records housed in the VT State Archives - Secretary of State's Office. VCGI also welcomes documented information from VGIS users which identify boundary errors. NOTE - VCGI has NOT attempted to create a legally definitive boundary layer. Instead the idea is to maintain an integrated village/town/county/RPC/state boundary layer which provides for a reasonably accurate representation of these boundaries (refer to ARC_SRC and SRC_NOTES). BNDHASH includes all counties, towns, and villages listed in "Population and Local Government - State of Vermont - 2000" published by the Secretary of State. BNDHASH may include changes endorsed by the Legislature since the publication of this document in 2000 (eg: villages merged with towns). Utlimately the Vermont Secratary of State's Office and the VT Legislature are responsible for maintaining information which accurately describes the locations of these boundaries. BNDHASH should be used for general mapping purposes only. * Users who wish to determine which boundaries are different from the original TBHASH boundaries should refer to the ORIG_ARC field in the BOUNDARY_BNDHASH_LINE (line feature with attributes). Also, updates to BNDHASH are tracked by version number (ex: 2003A). The UPDACT field is used to track changes between versions. The UPDACT field is flushed between versions.

The BNDHASH dataset depicts Vermont villages, towns, counties, Regional Planning Commissions (RPC), and LEPC (Local Emergency Planning Committee) boundaries. It is a composite of generally 'best available' boundaries from various data sources (refer to ARC_SRC and SRC_NOTES attributes). However, this dataset DOES NOT attempt to provide a legally definitive boundary. The layer was originally developed from TBHASH, which was the master VGIS town boundary layer prior to the development and release of BNDHASH. By integrating village, town, county, RPC, and state boundaries into a single layer, VCGI has assured vertical integration of these boundaries and simplified maintenance. BNDHASH also includes annotation text for town, county, and RPC names. BNDHASH includes the following feature classes: 1) VILLAGES = Vermont villages 2) TOWNS = Vermont towns 3) COUNTIES = Vermont counties 4) RPCS = Vermont's Regional Planning Commissions 5) LEPC = Local Emergency Planning Committee boundaries 6) VTBND = Vermont's state boundary The master BNDHASH layer is managed as ESRI geodatabase feature dataset by VCGI. The dataset stores villages, towns, counties, and RPC boundaries as seperate feature classes with a set of topology rules which binds the features. This arrangement assures vertical integration of the various boundaries. VCGI will update this layer on an annual basis by reviewing records housed in the VT State Archives - Secretary of State's Office. VCGI also welcomes documented information from VGIS users which identify boundary errors. NOTE - VCGI has NOT attempted to create a legally definitive boundary layer. Instead the idea is to maintain an integrated village/town/county/rpc boundary layer which provides for a reasonably accurate representation of these boundaries (refer to ARC_SRC and SRC_NOTES). BNDHASH includes all counties, towns, and villages listed in "Population and Local Government - State of Vermont - 2000" published by the Secretary of State. BNDHASH may include changes endorsed by the Legislature since the publication of this document in 2000 (eg: villages merged with towns). Utlimately the Vermont Secratary of State's Office and the VT Legislature are responsible for maintaining information which accurately describes the location of these boundaries. BNDHASH should be used for general mapping purposes only. * Users who wish to determine which boundaries are different from the original TBHASH boundaries should refer to the ORIG_ARC field in the BOUNDARY_BNDHASH_LINE (line featue with attributes). Also, updates to BNDHASH are tracked by version number (ex: 2003A). The UPDACT field is used to track changes between versions. The UPDACT field is flushed between versions.

A feature class describing the spatial location of the administrative boundary of the lands managed by the Forest Supervisor's office. An area encompassing all the National Forest System lands administered by an administrative unit. The area encompasses private lands, other governmental agency lands, and may contain National Forest System lands within the proclaimed boundaries of another administrative unit. All National Forest System lands fall within one and only one Administrative Forest Area. This dataset is derived from the USFS Southwestern Region ALP (Automated Lands Program) data Project. This is one of six layers derived from ALP for the purpose of supplying data layers for recourse GIS analysis and data needs within the Forest Service. The six layers are Surface Ownership, Administrative Forest Boundary, District Boundary, Townships, Sections, and Wilderness. There were some gapes in the ALP data so a small portion of this dataset comes from CCF (Cartographic Feature Files) datasets and the USFS Southwestern Region Core Data Project. ALP data is developed from data sources of differing accuracy, scales, and reliability. Where available it is developed from GCDB (Geographic Coordinate Data Base) data. GCDB data is maintained by the Bureau of Land Management in their State Offices. GCDB data is mostly corner data. Not all corners and not all boundaries are available in GCDB so ALP also utilizes many other data sources like CFF data to derive its boundaries. GCDB data is in a constant state of change because land corners are always getting resurveyed. The GCDB data used in this dataset represents a snapshot in time at the time the GCDB dataset was published by the BLM and may not reflect the most current GCDB dataset available. The Forest Service makes no expressed or implied warranty with respect to the character, function, or capabilities of these data. These data are intended to be used for planning and analyses purposes only and are not legally binding with regards to title or location of National Forest System lands.

In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) data set (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the Process Step section of the Feature Class metadata. A data set named cnty24k97_1 was made available (approximately 2004) through the California Department of Forestry and Fire Protection - Fire and Resource Assessment Program (CDF - FRAP) and the California Spatial Information Library (CaSIL). In late 2006, the Department of Fish and Game (DFG) reviewed cnty24k97_1. Comparisons were made to a high-quality 100K dataset (co100a/county100k from the former Teale Data Center GIS Solutions Group) and legal boundary descriptions from ( http://www.leginfo.ca.gov ). The cnty24k97_1 data set was missing Anacapa and Santa Barbara islands. DFG added the missing islands using previously-digitized coastline data (coastn27 of State Lands Commission origin), corrected a few county boundaries, built region topology, added additional attributes, and renamed the data set to county24k. In 2007, the California Mapping Coordinating Committee (CMCC) requested that the California Department of Forestry and Fire Protection (CAL FIRE) resume stewardship of the statewide county boundaries data. CAL FIRE adopted the changes made by DFG and collected additional suggestions for the county data from DFG, DOC, and local government agencies. CAL FIRE incorporated these suggestions into the latest revision, which has been renamed cnty24k09_1. Detailed documentation of changes is included in the Process Step section of the Feature Class metadata. This Geo database contains 3 feature classes representing California county boundaries (arc, polygon, and multipart-polygon feature classes) and also contains a polygon feature class representing the state boundary: 1. Line - can be useful for cartographic purposes, especially when different line symbology is needed for different boundaries (e.g. Coastline, Mexico, Nevada, etc). 2. Multipart - features from a common county are combined into a single record (equivalent to a region feature class in a coverage). May be useful for selections and overlays when all parts of a county are needed. 3. Poly - all county features are represented as individual polygons. 4. State Poly - state boundary polygon to be used for cartography or overlay analysis that requires a state polygon.

An area encompassing all the National Forest System lands administered by an administrative unit. The area encompasses private lands, other governmental agency lands, and may contain National Forest System lands within the proclaimed boundaries of another administrative unit. All National Forest System lands fall within one and only one Administrative Forest Area.

This data is intended for read-only use. These data were prepared to describe Forest Service administrative area boundaries. The purpose of the data is to provide display, identification, and analysis tools for determining current boundary information for Forest Service managers, GIS Specialists, and others.

The Forest Service has multiple types of boundaries represented by different feature classes (layers): Administrative, Ownership and Proclaimed. 1) ADMINISTRATIVE boundaries (e.g. AdministrativeForest and RangerDistrict feature classes) encompass National Forest System lands managed by an administrative unit. These are dynamic layers that should not be considered "legal" boundaries as they are simply intended to identify the specific organizational units that administer areas. As lands are acquired and disposed, the administrative boundaries are adjusted to expand or shrink accordingly. Please note that ranger districts are sub units of National Forests. An administrative forest boundary can contain one or more Proclaimed National Forests, National Grasslands, Purchase Units, Research and Experimental Areas, Land Utilization Projects and various "Other" Areas. If needed, OWNERSHIP boundaries (e.g. BasicOwnership and SurfaceOwnership feature classes) should be reviewed along with these datasets to determine parcels that are federally managed within the administrative boundaries. 2) OWNERSHIP boundaries (e.g. BasicOwnership and SurfaceOwnership feature classes) represent parcels that are tied to legal transactions of ownership. These are parcels of Federal land managed by the USDA Forest Service. Please note that the BasicOwnership layer is simply a dissolved version of the SurfaceOwnership layer. 3) PROCLAIMED boundaries (e.g. ProclaimedForest and ProclaimedForest_Grassland) encompass areas of National Forest System land that is set aside and reserved from public domain by executive order or proclamation. Please note that the ProclaimedForest layer contains only proclaimed forests while ProclaimedForest_Grassland layer contains both proclaimed forests and proclaimed grasslands. For boundaries that reflect current National Forest System lands managed by an administrative unit, see the ADMINISTRATIVE boundaries (AdministrativeForest and RangerDistrict feature classes). For a visual comparison of the different kinds of USFS boundary datasets maintained by the USFS, see the Forest Service Boundary Comparison map at https://usfs.maps.arcgis.com/apps/CompareAnalysis/index.html?appid=fe7b9f56217949a291356f08cfccb119. USFS boundaries are often referenced in national datasets maintained by other federal agencies. Please note that variations may be found between USFS data and other boundary datasets due to differing update frequencies. PAD-US (Protected Areas Database of the United States), maintained by the U.S. Geological Survey, is a "best available" inventory of protected areas including data provided by managing agencies and organizations including the Forest Service. For more information see https://gapanalysis.usgs.gov/padus/data/metadata/. SMA (Surface Management Agency), maintained by the Bureau of Land Management, depicts Federal land for the United States and classifies this land by its active Federal surface managing agency. It uses data provided by the Forest Service and other agencies, combined with National Regional Offices collection efforts. For more information see https://landscape.blm.gov/geoportal/catalog/search/resource/details.page?uuid=%7B2A8B8906-7711-4AF7-9510-C6C7FD991177%7D.

The metropolitan planning organization (MPO) polygon feature class provides California MPO legislative boundaries, primarily for regional planning applications.

This data set contains the administrative boundaries at country level of the world and is based on the geometry from EBM v12.x. of EuroGeographics for the members of Eurogeographics, the Global Administrative Units Layer (2015) from FAO (UN) and geometry from the Turkish National Statistical Office. This dataset consists of 2 feature classes (regions, boundaries) per scale level and there are 6 different scale levels (100K, 1M, 3M, 10M, 20M and 60M). The public data set (1M - 60M) is available under the Download link indicated below. The full data set (100K - 60M) GISCO.CNTR_2016 is available via the EC restricted download link.

Overview

The Drishti-AI Balanced Plant Disease Dataset is a large-scale, high-quality dataset designed for plant disease classification and computer vision research. It consolidates multiple public datasets into a unified, balanced, and structured collection suitable for deep learning applications in agricultural AI.

This dataset provides a strong benchmark for researchers and developers to train and evaluate models for automated plant disease detection.

Dataset Engineering Summary Data Aggregation and Curation

Collected and integrated data from six public plant disease datasets available on Kaggle Hub.

Processed and standardized all images to a uniform 256×256 RGB format.

Merged a total of 308,984 images from various open sources.

Class Unification

Created a MASTER_CLASS_MAP to merge over 200 inconsistent source labels (e.g., Apple_Scab, Apple_scab) into 112 standardized master classes.

Ensured consistent naming conventions and clear class boundaries across species.

Data Processing

Performed resizing, color correction, and conversion to 3-channel RGB format.

Stratified data into:

Train: 80%

Validation: 10%

Test: 10%

Data Balancing

Implemented a hybrid balancing strategy using Albumentations:

Oversampling: Classes with fewer than 1,000 images were augmented to reach a minimum threshold.

Undersampling: Classes exceeding 10,000 samples were capped to prevent bias.

Validation and test sets were preserved without augmentation to ensure evaluation integrity.

Final Dataset Artifact

Name: Drishti_AI_Balanced

Total Size: ~10.18 GB

Total Images: ~345,000

Classes: 112

Key Features

112 plant disease and healthy leaf classes.

Fully balanced class distribution for fair model training.

Standardized 256×256 RGB images for compatibility with most CNN architectures.

Clean, ready-to-train folder structure.

Curated for research in agricultural computer vision and sustainability-focused AI.

Intended Use

This dataset is intended for:

Training and evaluation of CNNs, Transformers, and other deep learning models.

Transfer learning and fine-tuning experiments.

Research on plant pathology and disease diagnosis.

Educational projects in data-centric machine learning and image classification.

Technical Details

Image Format: JPEG

Image Size: 256×256

Color Channels: RGB (3)

Split Ratio: 80/10/10 (train/validation/test)

Balancing Technique: Augmentation-based oversampling and undersampling

Total Files: ~345,000

License

This dataset is distributed under the Creative Commons Attribution 4.0 International (CC BY 4.0) license. You are free to use, modify, and share the dataset with proper attribution.

Citation

If you use this dataset in your work, please cite it as:

Mishra, A. (2025). Drishti-AI Balanced Plant Disease Dataset. Kaggle. https://www.kaggle.com/datasets/[your-dataset-link ]

About the Author

Ansh Mishra is an AI and data science enthusiast focused on data-centric AI and computer vision. He created the Drishti-AI Balanced Dataset, a large-scale plant disease dataset built to advance agricultural AI research and deep learning applications.

The dataset is an update of a feature class representing four different Pinelands boundaries in Southern New Jersey. It represents the Pinelands Preservation Area District and the Pinelands Protection Area as per the New Jersey Pinelands Protection Act of 1979 (P.L. 1979, Chapter 111, approved June 28, 1979), the Pinelands Comprehensive Management Plan area (N.J.S.A. 13:18A-1 et. seq.), and the Pinelands National Reserve boundary as per the National Parks and Recreation Act of 1978 (P.L. 95-625, Sec. 502). Originally the dataset was created manually by interpreting text documents which described the boundary lines and drafting this information onto mylar using USGS photo quads as a base. In 1994, the coverage was digitized and converted to New Jersey State Plane NAD 83 Feet. In 2002, the boundaries were adjusted to a seamless parcel layer. In 2014/15 the boundaries were adjusted to The State of New Jersey Composite of Parcels Data layer developed by the New Jersey Office of Information Technology and an updated Pinelands Management Area layer to make the lines coincidental where applicable. The composite parcel layer is "In work", so changes made in the composite parcel layer after the release of this data set will not be reflected in this version. The boundaries are intended to provide reasonable representation of the boundaries for planning purposes. They are not survey grade. The current geometry is not static and is prone to change. Downloaded March 2020

(Link to Metadata) The BNDHASH dataset depicts Vermont village, town, county, and Regional Planning Commission (RPC) boundaries. It is a composite of generally 'best available' boundaries from various data sources (refer to ARC_SRC and SRC_NOTES attributes). However, this dataset DOES NOT attempt to provide a legally definitive boundary. The layer was originally developed from TBHASH, which was the master VGIS town boundary layer prior to the development and release of BNDHASH. By integrating village, town, county, RPC, and state boundaries into a single layer, VCGI has assured vertical integration of these boundaries and simplified maintenance. BNDHASH also includes annotation text for town, county, and RPC names. BNDHASH includes the following feature classes: 1) BNDHASH_POLY_VILLAGES = Vermont villages 2) BNDHASH_POLY_TOWNS = Vermont towns 3) BNDHASH_POLY_COUNTIES = Vermont counties 4) BNDHASH_POLY_RPCS = Vermont's Regional Planning Commissions 5) BNDHASH_POLY_VTBND = Vermont's state boundary 6) BNDHASH_LINE = Lines on which all POLY feature classes are built The master BNDHASH data is managed as an ESRI geodatabase feature dataset by VCGI. The dataset stores village, town, county, RPC, and state boundaries as seperate feature classes with a set of topology rules which binds the features. This arrangement assures vertical integration of the various boundaries. VCGI will update this layer on an annual basis by reviewing records housed in the VT State Archives - Secretary of State's Office. VCGI also welcomes documented information from VGIS users which identify boundary errors. NOTE - VCGI has NOT attempted to create a legally definitive boundary layer. Instead the idea is to maintain an integrated village/town/county/RPC/state boundary layer which provides for a reasonably accurate representation of these boundaries (refer to ARC_SRC and SRC_NOTES). BNDHASH includes all counties, towns, and villages listed in "Population and Local Government - State of Vermont - 2000" published by the Secretary of State. BNDHASH may include changes endorsed by the Legislature since the publication of this document in 2000 (eg: villages merged with towns). Utlimately the Vermont Secratary of State's Office and the VT Legislature are responsible for maintaining information which accurately describes the locations of these boundaries. BNDHASH should be used for general mapping purposes only. * Users who wish to determine which boundaries are different from the original TBHASH boundaries should refer to the ORIG_ARC field in the BOUNDARY_BNDHASH_LINE (line feature with attributes). Also, updates to BNDHASH are tracked by version number (ex: 2003A). The UPDACT field is used to track changes between versions. The UPDACT field is flushed between versions.

The dataset is a feature class showing the boundaries of 515 groundwater basins and subbasins as defined by the California Department of Water Resources as last modified by the Basin Boundary Emergency Regulation adopted on October 21, 2015 and subsequent modifications requested through the Basin Boundary Modification Request Process. This data is current as of December 9, 2022. The file is in ESRI geodatabase format and is intended for use with compatible GIS software. Groundwater basins are represented as polygon features and designated on the basis of geological and hydrological conditions - usually the occurrence of alluvial or unconsolidated deposits. When practical, large basins are also subdivided by political boundaries, as in the Central Valley. Basins are named and numbered per the convention of the Department of Water Resources.

Spatial analysis and statistical summaries of the Protected Areas Database of the United States (PAD-US) provide land managers and decision makers with a general assessment of management intent for biodiversity protection, natural resource management, and outdoor recreation access across the nation. This data release presents results from statistical summaries of the PAD-US 3.0 protection status (by GAP Status Code) and public access status for various land unit boundaries (Protected Areas Database of the United States 3.0 Vector Analysis and Summary Statistics). Summary statistics are also available to explore and download (Comma-separated Table [CSV], Microsoft Excel Workbook (.xlsx), Portable Document Format [.pdf] Report) from the PAD-US Lands and Inland Water Statistics Dashboard ( https://www.usgs.gov/programs/gap-analysis-project/science/pad-us-statistics ). The vector GIS analysis file, source data used to summarize statistics for areas of interest to stakeholders (National, State, Department of the Interior Region, Congressional District, County, EcoRegions I-IV, Urban Areas, Landscape Conservation Cooperative), and complete Summary Statistics Tabular Data (CSV) are included in this data release. Raster GIS analysis files are also available for combination with other raster data (Protected Areas Database of the United States (PAD-US) 3.0 Raster Analysis). The PAD-US 3.0 Combined Fee, Designation, Easement feature class in the full inventory, with Military Lands and Tribal Areas from the Proclamation and Other Planning Boundaries feature class (Protected Areas Database of the United States (PAD-US) 3.0, https://doi.org/10.5066/P9Q9LQ4B), was modified to prioritize and remove overlapping management designations, limiting overestimation in protection status or public access statistics and to support user needs for vector and raster analysis data. Analysis files in this data release were clipped to the Census State boundary file to define the extent and fill in areas (largely private land) outside the PAD-US, providing a common denominator for statistical summaries.

GDB Version: ArcGIS Pro 3.3Additional Resources:Shapefile DownloadShapefile Download (Clipped to VIMS shoreline)Administrative Boundary Data Standard REST Endpoint (Unclipped) - REST Endpoint (Clipped)The Administrative Boundary feature classes represent the best available boundary information in Virginia. VGIN initially sought to develop an improved city, county, and town boundary dataset in late 2013, spurred by response of the Virginia Administrative Boundaries Workgroup community. The feature class initially started from an extraction of features from the Census TIGER dataset for Virginia. VGIN solicited input from localities in Virginia through the Road Centerlines data submission process as well as through public forums such as the Virginia Administrative Boundaries Workgroup and VGIN listservs. Data received were analyzed and incorporated into the appropriate feature classes where locality data were a superior representation of boundaries. Administrative Boundary geodatabase and shapefiles are unclipped to hydrography features by default. The clipped to hydro dataset is included as a separate shapefile download below.

The USGS Protected Areas Database of the United States (PAD-US) is the nation's inventory of protected areas, including public land and voluntarily provided private protected areas, identified as an A-16 National Geospatial Data Asset in the Cadastre Theme ( https://communities.geoplatform.gov/ngda-cadastre/ ). The PAD-US is an ongoing project with several published versions of a spatial database including areas dedicated to the preservation of biological diversity, and other natural (including extraction), recreational, or cultural uses, managed for these purposes through legal or other effective means. The database was originally designed to support biodiversity assessments; however, its scope expanded in recent years to include all open space public and nonprofit lands and waters. Most are public lands owned in fee (the owner of the property has full and irrevocable ownership of the land); however, permanent and long-term easements, leases, agreements, Congressional (e.g. 'Wilderness Area'), Executive (e.g. 'National Monument'), and administrative designations (e.g. 'Area of Critical Environmental Concern') documented in agency management plans are also included. The PAD-US strives to be a complete inventory of U.S. public land and other protected areas, compiling “best available” data provided by managing agencies and organizations. The PAD-US geodatabase maps and describes areas using thirty-six attributes and five separate feature classes representing the U.S. protected areas network: Fee (ownership parcels), Designation, Easement, Marine, Proclamation and Other Planning Boundaries. An additional Combined feature class includes the full PAD-US inventory to support data management, queries, web mapping services, and analyses. The Feature Class (FeatClass) field in the Combined layer allows users to extract data types as needed. A Federal Data Reference file geodatabase lookup table (PADUS3_0Combined_Federal_Data_References) facilitates the extraction of authoritative federal data provided or recommended by managing agencies from the Combined PAD-US inventory. This PAD-US Version 3.0 dataset includes a variety of updates from the previous Version 2.1 dataset (USGS, 2020, https://doi.org/10.5066/P92QM3NT ), achieving goals to: 1) Annually update and improve spatial data representing the federal estate for PAD-US applications; 2) Update state and local lands data as state data-steward and PAD-US Team resources allow; and 3) Automate data translation efforts to increase PAD-US update efficiency. The following list summarizes the integration of "best available" spatial data to ensure public lands and other protected areas from all jurisdictions are represented in the PAD-US (other data were transferred from PAD-US 2.1). Federal updates - The USGS remains committed to updating federal fee owned lands data and major designation changes in annual PAD-US updates, where authoritative data provided directly by managing agencies are available or alternative data sources are recommended. The following is a list of updates or revisions associated with the federal estate: 1) Major update of the Federal estate (fee ownership parcels, easement interest, and management designations where available), including authoritative data from 8 agencies: Bureau of Land Management (BLM), U.S. Census Bureau (Census Bureau), Department of Defense (DOD), U.S. Fish and Wildlife Service (FWS), National Park Service (NPS), Natural Resources Conservation Service (NRCS), U.S. Forest Service (USFS), and National Oceanic and Atmospheric Administration (NOAA). The federal theme in PAD-US is developed in close collaboration with the Federal Geographic Data Committee (FGDC) Federal Lands Working Group (FLWG, https://communities.geoplatform.gov/ngda-govunits/federal-lands-workgroup/ ). 2) Improved the representation (boundaries and attributes) of the National Park Service, U.S. Forest Service, Bureau of Land Management, and U.S. Fish and Wildlife Service lands, in collaboration with agency data-stewards, in response to feedback from the PAD-US Team and stakeholders. 3) Added a Federal Data Reference file geodatabase lookup table (PADUS3_0Combined_Federal_Data_References) to the PAD-US 3.0 geodatabase to facilitate the extraction (by Data Provider, Dataset Name, and/or Aggregator Source) of authoritative data provided directly (or recommended) by federal managing agencies from the full PAD-US inventory. A summary of the number of records (Frequency) and calculated GIS Acres (vs Documented Acres) associated with features provided by each Aggregator Source is included; however, the number of records may vary from source data as the "State Name" standard is applied to national files. The Feature Class (FeatClass) field in the table and geodatabase describe the data type to highlight overlapping features in the full inventory (e.g. Designation features often overlap Fee features) and to assist users in building queries for applications as needed. 4) Scripted the translation of the Department of Defense, Census Bureau, and Natural Resource Conservation Service source data into the PAD-US format to increase update efficiency. 5) Revised conservation measures (GAP Status Code, IUCN Category) to more accurately represent protected and conserved areas. For example, Fish and Wildlife Service (FWS) Waterfowl Production Area Wetland Easements changed from GAP Status Code 2 to 4 as spatial data currently represents the complete parcel (about 10.54 million acres primarily in North Dakota and South Dakota). Only aliquot parts of these parcels are documented under wetland easement (1.64 million acres). These acreages are provided by the U.S. Fish and Wildlife Service and are referenced in the PAD-US geodatabase Easement feature class 'Comments' field. State updates - The USGS is committed to building capacity in the state data-steward network and the PAD-US Team to increase the frequency of state land updates, as resources allow. The USGS supported efforts to significantly increase state inventory completeness with the integration of local parks data in the PAD-US 2.1, and developed a state-to-PAD-US data translation script during PAD-US 3.0 development to pilot in future updates. Additional efforts are in progress to support the technical and organizational strategies needed to increase the frequency of state updates. The PAD-US 3.0 included major updates to the following three states: 1) California - added or updated state, regional, local, and nonprofit lands data from the California Protected Areas Database (CPAD), managed by GreenInfo Network, and integrated conservation and recreation measure changes following review coordinated by the data-steward with state managing agencies. Developed a data translation Python script (see Process Step 2 Source Data Documentation) in collaboration with the data-steward to increase the accuracy and efficiency of future PAD-US updates from CPAD. 2) Virginia - added or updated state, local, and nonprofit protected areas data (and removed legacy data) from the Virginia Conservation Lands Database, provided by the Virginia Department of Conservation and Recreation's Natural Heritage Program, and integrated conservation and recreation measure changes following review by the data-steward. 3) West Virginia - added or updated state, local, and nonprofit protected areas data provided by the West Virginia University, GIS Technical Center. For more information regarding the PAD-US dataset please visit, https://www.usgs.gov/gapanalysis/PAD-US/. For more information about data aggregation please review the PAD-US Data Manual available at https://www.usgs.gov/core-science-systems/science-analytics-and-synthesis/gap/pad-us-data-manual . A version history of PAD-US updates is summarized below (See https://www.usgs.gov/core-science-systems/science-analytics-and-synthesis/gap/pad-us-data-history for more information): 1) First posted - April 2009 (Version 1.0 - available from the PAD-US: Team pad-us@usgs.gov). 2) Revised - May 2010 (Version 1.1 - available from the PAD-US: Team pad-us@usgs.gov). 3) Revised - April 2011 (Version 1.2 - available from the PAD-US: Team pad-us@usgs.gov). 4) Revised - November 2012 (Version 1.3) https://doi.org/10.5066/F79Z92XD 5) Revised - May 2016 (Version 1.4) https://doi.org/10.5066/F7G73BSZ 6) Revised - September 2018 (Version 2.0) https://doi.org/10.5066/P955KPLE 7) Revised - September 2020 (Version 2.1) https://doi.org/10.5066/P92QM3NT 8) Revised - January 2022 (Version 3.0) https://doi.org/10.5066/P9Q9LQ4B Comparing protected area trends between PAD-US versions is not recommended without consultation with USGS as many changes reflect improvements to agency and organization GIS systems, or conservation and recreation measure classification, rather than actual changes in protected area acquisition on the ground.

The NSW Administrative Boundaries Web Service is a dynamic map of administrative and property boundaries. Administrative Areas Boundaries depict a polygon feature class within the NSW Digital Cadastral Database maintained by LPI. The administrative boundaries provided through this web service includes: Counties, Suburbs, Parishes, Local Government Areas, State Forests, National Parks, State Electoral Districts. For detailed information, for each individual dataset contained in this web services, please see the Digital Cadastre Database Dictionary published at http://www.lpi.nsw.gov.au/mapping_and_imagery/spatial_data.

This web service allows users to easily integrate NSW Administrative Boundaries into OGC compliant spatial platforms and applications. Administrative Boundaries can be used to aggregate information for analytical purposes and analyse time series trends. Administrative boundary data in combination with geo-coded address data, demographic information and agency specific business information underpins the ability to perform high quality spatial analysis.