The same 20 features were measured for the in-graphs (representing the cellular structure associated with each boundary) and for the out-graphs (representing the corresponding areas in the background), giving 40 metrics in total.

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

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.

This dataset represents the Connecticut River Watershed Boundary and is from the Watershed Boundary Dataset (WBD). The WBD defines the areal extent of surface water drainage to a point, accounting for all land and surface areas. Watershed Boundaries are determined solely upon science-based hydrologic principles, not favoring any administrative boundaries or special projects, nor particular program or agency. The intent of defining Hydrologic Units (HU) for the Watershed Boundary Dataset is to establish a baseline drainage boundary framework, accounting for all land and surface areas. At a minimum, the WBD is being delineated and georeferenced to the USGS 1:24,000 scale topographic base map meeting National Map Accuracy Standards (NMAS). Hydrologic units are given a Hydrologic Unit Code (HUC). For example, a hydrologic region has a 2-digit HUC. A HUC describes where the unit is in the country and the level of the unit. The document "Federal Standards and Procedures for the National Watershed Boundary Dataset (WBD)" can be found here: http://pubs.usgs.gov/tm/tm11a3/pdf/WBD-Ed3_052212.pdfA hydrological unit is a drainage area delineated to nest in a multi-level, hierarchical drainage system. Its boundaries are defined by the hyrographic and topographic criteria that delinate an area of land upstream from a specific point on a river, stream, or similar surface waters. The hydrologic units are only synonymous with class watersheds when their boundaries include all the source area contributing surface water to a single defined outlet point.Please see http://nhd.usgs.gov/wbd.html for more information

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.

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.

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.

Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information

IntroductionDrug-induced liver injury (DILI) has been investigated at the patient level. Analysis of gene perturbation at the cellular level can help better characterize biological mechanisms of hepatotoxicity. Despite accumulating drug-induced transcriptome data such as LINCS, analyzing such transcriptome data upon drug treatment is a challenging task because the perturbation of expression is dose and time dependent. In addition, the mechanisms of drug toxicity are known only as literature information, not in a computable form.MethodsTo address these challenges, we propose a Multi-Dimensional Transcriptomic Ruler (MDTR) that quantifies the degree of DILI at the transcriptome level. To translate transcriptome data to toxicity-related mechanisms, MDTR incorporates KEGG pathways as representatives of mechanisms, mapping transcriptome data to biological pathways and subsequently aggregating them for each of the five hepatotoxicity mechanisms. Given that a single mechanism involves multiple pathways, MDTR measures pathway-level perturbation by constructing a radial basis kernel-based toxicity space and measuring the Mahalanobis distance in the transcriptomic kernel space. Representing each mechanism as a dimension, MDTR is visualized in a radar chart, enabling an effective visual presentation of hepatotoxicity at transcriptomic level.Results and DiscussionIn experiments with the LINCS dataset, we show that MDTR outperforms existing methods for measuring the distance of transcriptome data when describing for dose-dependent drug perturbations. In addition, MDTR shows interpretability at the level of DILI mechanisms in terms of the distance, i.e., in a metric space. Furthermore, we provided a user-friendly and freely accessible website (http://biohealth.snu.ac.kr/software/MDTR), enabling users to easily measure DILI in drug-induced transcriptome data.

The VA_TOWN dataset is a feature class component of the Virginia Administrative Boundaries dataset from the Virginia Geographic Information Network (VGIN). VA_COUNTY represents the best available city and county boundary information to VGIN.VGIN initially sought to develop an improved locality and town boundary dataset in late 2013, spurred by response of the Virginia Administrative Boundaries Workgroup community. The feature class initially started from the locality boundaries 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 VA_COUNTY feature class where locality data were a superior representation of the city or county boundary.

© Virginia Geographic Information Network (VGIN), and the Census and Localities and Towns submitting data to the project

This layer is a component of Feature classes representing locality (county, city, and town) boundaries in the Commonwealth of Virginia..

Firm age class limits.

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.

This dataset represents the international boundary between the United States of America and the United States of Mexico.This feature class is a digital representation of the international boundary between the United States and Mexico in accordance with the 1970 Treaty (Treaty to Resolve Pending Boundary Differences and Maintain the Rio Grande and Colorado River as the International Boundary). It has been generated from a combination of recent surveys and datum conversions. It is intended for mapping purposes only.

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

Corporate data contained within the NWFPP Boundary_2002 feature class is intended for spatial display and analysis purposes. Coverage is for use to describe the general extent of the Northwest Forest Plan. This shapefile contains polygon corporate data which depicts the Northwest Forest Plan boundary updated as requested by the Regional Interagency Executive Committee (RIEC) FEMAT 2002. This feature class is a product of the Pacific Northwest Region Coverage to Geodatabase Conversion Project in an effort to standardize data throughout the Region.

This dataset represents the Connecticut River Watershed Boundary and is from the Watershed Boundary Dataset (WBD). The WBD defines the areal extent of surface water drainage to a point, accounting for all land and surface areas. Watershed Boundaries are determined solely upon science-based hydrologic principles, not favoring any administrative boundaries or special projects, nor particular program or agency. The intent of defining Hydrologic Units (HU) for the Watershed Boundary Dataset is to establish a baseline drainage boundary framework, accounting for all land and surface areas. At a minimum, the WBD is being delineated and georeferenced to the USGS 1:24,000 scale topographic base map meeting National Map Accuracy Standards (NMAS). Hydrologic units are given a Hydrologic Unit Code (HUC). For example, a hydrologic region has a 2-digit HUC. A HUC describes where the unit is in the country and the level of the unit. The document "Federal Standards and Procedures for the National Watershed Boundary Dataset (WBD)" can be found here: http://pubs.usgs.gov/tm/tm11a3/pdf/WBD-Ed3_052212.pdfA hydrological unit is a drainage area delineated to nest in a multi-level, hierarchical drainage system. Its boundaries are defined by the hyrographic and topographic criteria that delinate an area of land upstream from a specific point on a river, stream, or similar surface waters. The hydrologic units are only synonymous with class watersheds when their boundaries include all the source area contributing surface water to a single defined outlet point.Please see http://nhd.usgs.gov/wbd.html for more information

Limit Class

## Overview

Limit Class is a dataset for object detection tasks - it contains E.g QQ7u annotations for 3,779 images.

## Getting Started

You can download this dataset for use within your own projects, or fork it into a workspace on Roboflow to create your own model.

  ## License

  This dataset is available under the [CC BY 4.0 license](https://creativecommons.org/licenses/CC BY 4.0).

description: Cities, Towns and Villages dataset current as of 2010. City Limits feature class located within the boundary data geodatabase.; abstract: Cities, Towns and Villages dataset current as of 2010. City Limits feature class located within the boundary data geodatabase.

This dataset depicts the boundaries of the Suisun Marsh.

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