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

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.

This feature class depicts the boundaries of Operable Unit 1 (OU1) within the Carson River Mercury Site (CRMS), including the four Area of Investigation boundaries. NDEP lead an initiative to refine the boundaries shown on maps identifying the Carson River Mercury Superfund Site (CRMS) from the initial site identification and description as the Carson River hydrographic basin beginning in Carson City, NV to its terminal points in Churchill County, NV. This description of the CRMS was used in many of the early site investigation studies and reports and continued to be used in all public education and long-term site management controls until approximately 2012. Using site contaminant fate and transport determinations from the CRMS OU1 Remedial Investigation (RI) and Conceptual Site Model (CSM), it seemed inappropriate to include the much larger area of the hydrographic basin as being potentially impacted by site contaminants of concern (CoC). NDEP created protocols to estimate areas that are likely to have been impacted by CoCs and created maps using these protocols to redraw the CRMS boundary limits. In the development of these protocols, NDEP used: Historic records and documentation of probable source areas; The 2012 archaeological mill site research and field study conducted by Broadbent and Associates to locate the historic source areas; Soil and sediment transport mechanisms identified in the CSM and general soil transport and sedimentology principals to predict areas where CoCs have likely been located at and downstream of the historic sources. The overall area of transport was estimated to be reasonably large to include possible anthropogenic activity as well as historic and future natural events such as flooding and channel migration. Additionally, NDEP added a "buffer” to extend the potential areas beyond the conservatively defined primary areas of potential contamination to further address unknown and future effects. These buffers have been identified separately from the primary areas of concern and labeled as such on maps using these protocols. These revisions were formalized in the 2013 Explanation of Significant Differences to the OU-1 Record of Decision (RoD) to adopt the new site definition and boundaries identified by NDEP as new estimates of the CRMS extents. NDEP identified four geographic areas of prime importance to the CRMS. Originally labeled by NDEP as "Risk Areas”, the intent of this terminology was to indicate these were the areas understood to have the most likely "risk” of contamination. Under consultation with EPA R9 risk assessment staff, the term has been changed to "Area of Investigation” to avoid confusion that any actual quantitative level of human or ecological risk has been determined for these areas. They are only estimates of potential contamination and new or additional information that contradicts these boundaries as being insufficient will be used to adopt new boundaries as appropriate. The four Areas of Investigation have become the foundation for the residential soil sampling program mandated by the OU-1 RoD. Summarized briefly; Investigation Area 1 (IA 1)- This includes all areas in the Carson River drainage basin from about the area of the historic settlement of Empire in Carson City, NV downstream to the existing or historic terminal points of the river at Carson Lake, Carson Sink, Indian Lakes and the Stillwater National Wildlife Refuge that lie outside the buffer zones of the other three Investigation Areas. It is least probable that CRMS CoCs will be located in these areas. It is unlikely that any sampling will be requested on areas developed within IA 1, but it might be requested in special circumstances, especially near and around the source areas of the contamination where historic activities could potentially have caused contamination beyond the typical boundaries as identified by the CSM. Investigation Area 2 (IA 2)- This area is defined as a buffer that lies 100 feet along a normal horizontal to the Investigation Area 3 boundary. For Comstock-era mill sites and isolated tailings piles, this translates to the area between 350 feet and 450 feet from the center point of the historic feature. For the 100-year FEMA floodplain and areas of irrigation, this is the area beginning at the limit of the flood plain boundary or irrigated land along a normal to 100 feet. Investigation Area 3 (IA 3)- This area is defined as a buffer that lies 100 feet along a normal horizontal to the Investigation Area 4 boundary for Comstock-era mills or isolated tailings piles. For Comstock-era mill sites and isolated tailings piles, this translates to the area between 250 feet and 350 feet from the center point of the historic feature. It is also defined as the limits of the FEMA 100-year floodplain or past or current flood irrigation practices. A tributary of the Carson River must have a Comstock-era mill site or tailings pile located along it to be mapped in IA3 and only the portion of the tributary downstream of the historic feature is included, not including the IA3 area and buffer drawn around the historic feature itself. If a tributary does not have FEMA 100-year flood plain defined, then IA3 has been defined as the area 100 feet along a normal to Investigation Area 4 boundary of that tributary. Investigation Area 4 (IA 4)- This area represents the highest likelihood of mercury contamination. Multiple steps were used to define the extent of this area, described below: The area within a 250 feet radius from the center point of a Comstock-era mill Comstock-era tailings pile polygon with a 250 ft buffer The centerline of the current channel of the Carson River enclosed in a polygon 100-feet wide (50 feet either side). Tributaries to the Carson River, where Comstock-era mills and tailings piles were located are enclosed in a polygon 50-feet wide (25 feet either side) from the approximate center of the tributary channel. Irrigation canals are enclosed in a polygon 20 feet wide (10 feet either side) from the approximate center of the ditch.

This polygon feature class contains the land, pond, and offshore areas within Dukes County MA. These data are intended for cartographic display and not survey-grade, legal definition.This dataset was compiled from several other datasets published by MassGIS. The coastline and inland ponds are believed to be at 1:25,000 scale based on wetlands data from the early 2000. The 3-mile extent is from an offshore 1:80,000 scale feature class. The town boundaries (on land) are from the Community Boundaries dataset of 2002. The town bounds across ponds were created by the MVC based on USGS topo maps.All data processing was done in ArcPro using primarily Identity geoprocessing tool to merge the various datasets together & to distinguish land, ponds, and off-shore. The attribute [type] was added to indicate a polygon as land, pond, or offshore.The two key files used from the MVC's data inventory were [town_detailed_duk_noh2o] and [interior_town_arcs6].Note: There are many town boundary datasets available and discrepancies in the town bounds among those datasets are numerous. This dataset of extents, does not claim to be the 'official' record of town bounds. If you need 'official', survey-grade data, please look elsewhere.

description: This polyline feature class represents the arc features that will define the boundaries of the BLM Land Use Planning Area (LUPA) in-progress polygons. Their attributes serve to store feature level metadata information for the polygon boundaries, as well as document the origin and characteristics of each arc.This state dataset may have published a dataset that is more current than the National dataset; there may be geometry variations between the state and national dataset which may have different results.The national dataset is updated following the data standard schedule.; abstract: This polyline feature class represents the arc features that will define the boundaries of the BLM Land Use Planning Area (LUPA) in-progress polygons. Their attributes serve to store feature level metadata information for the polygon boundaries, as well as document the origin and characteristics of each arc.This state dataset may have published a dataset that is more current than the National dataset; there may be geometry variations between the state and national dataset which may have different results.The national dataset is updated following the data standard schedule.

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 4.0 protection status (by GAP Status Code) and public access status for various land unit boundaries (PAD-US 4.0 Vector Analysis and Summary Statistics). Summary statistics are also available to explore and download from the PAD-US 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 analysis files are also available for combination with other raster data (PAD-US 4.0 Raster Analysis). The PAD-US Combined Fee, Designation, Easement feature class in the Full Inventory Database, with Military Lands and Tribal Areas from the Proclamation and Other Planning Boundaries feature class, 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.

description: This polyline feature class represents the arc features that will define the polygons for the BLM Administrative Unit areas. Their attributes serve to store feature level metadata information for the polygon boundaries, as well as document the origin and characteristics of each arc.This state dataset may have published a dataset that is more current than the National dataset; there may be geometry variations between the state and national dataset which may have different results.The national dataset is updated following the data standard schedule.; abstract: This polyline feature class represents the arc features that will define the polygons for the BLM Administrative Unit areas. Their attributes serve to store feature level metadata information for the polygon boundaries, as well as document the origin and characteristics of each arc.This state dataset may have published a dataset that is more current than the National dataset; there may be geometry variations between the state and national dataset which may have different results.The national dataset is updated following the data standard schedule.

description: This feature class depicts the boundaries of Land Survey features called sections, defined by the Public Lands Survey System Grid. Normally, 36 sections make up a township. The entire extent of each of these units should be collected, not just the portion on National Forest System lands. 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.; abstract: This feature class depicts the boundaries of Land Survey features called sections, defined by the Public Lands Survey System Grid. Normally, 36 sections make up a township. The entire extent of each of these units should be collected, not just the portion on National Forest System lands. 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.

Abstract This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied: The Geofabric Surface …Show full descriptionAbstract This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied: The Geofabric Surface Catchments product is derived from the National Catchment Boundaries (NCB) V1.1.4. This data defines a catchment for every stream segment containd within the Geofabric Surface Network product according to the GEODATA Nine Decond Digitial Elevation Model (DEM-9S) Version 3. These stream segment level boundaries may be used individually or in aggregation. The product is designed to represent geographic surface boundaries that have a hydrological relationship to surface water features. The NCB Level 1 and NCB Level 2 features are the top two levels in the NCB Catchment hierarchy and have been provided as polygon boundaries. This product contains one Geofabric feature type called Catchment. It also contains three NCB feature types including: NCBLevel1Drainage Division, NCBLevel2Drainage Basin and NCBPfafstetter. Purpose This product is intended to support the creation of or definition of topologically consistent and hydrologically enforced streamflow aggregation boundaries. The catchment attributes can be extending by linking the NCB Pfafstetter table to include the Pfafstetter reference system for identifying and aggregating catchments. This product is intended to supplement the Geofabric Surface Cartography and Geofabric Surface Network data products. This product is also used to as the basis for building contracted catchments in the Geofabric Hydrology Reporting Catchments product and provides a spatial framework for analysis and assessment of streams and their catchments. Dataset History Geofabric Surface Catchments is part of a suite of Geofabric products produced by the Australian Bureau of Meteorology. The geometry of this product is largely derived from the National Catchment Boundaries (NCB) V1.1.4. It consists of catchments, NCB Level 1 Drainage Divisions, NCB Level 2 Drainage Basins and the NCB Pfafstetter table. The feature class terminology for Geofabric Surface Catchment components has been modified to distinguish it in terms of the products underlying data model. The AHGFCatchments are based upon polygons converted from a regular 9 second grid delineating the NCBs for the Australian continent. The NCBs delineate hierarchically-nested catchments derived using an automated drainage analysis procedure based on a multi-flow extension of the version 3.1 flow direction grid associated with the 9 second DEM (GEODATA National 9 Second Digital Elevation Model (DEM-9S) Version 3, ANZLIC unique identifier: ANZCW0703011541). At the highest levels in the hierarchy the NCBs aggregate the 9 second drainage basins (9 second Basins product name and ANZLIC identifier to be inserted) into 12 topographically-defined Drainage Divisions (Level 1) and 191 Drainage Basins (Level 2) approximating the Australian Water Resources Council (AWRC) River Basins (Australia's River Basins, Geoscience Australia, 1997 ANZLIC identifier: ANZCW0703005427) where possible. At lower levels, the Level 2 units are sub-divided into successively finer sub-catchments using a modified version of the Pfafstetter procedure (Verdin, K. L. and Verdin, J. P. (1999) A topological system for delineation and codification of the Earth's river basins. Journal of Hydrology, 218(1-2), 1-12). This layer delineates the lowest level catchment units being the sub-catchments draining directly to a stream segment in the ANUDEM stream layer or, where there are no ANUDEM Derived Streams (ANUDEM Streams), the 9 second drainage basin. The higher level catchment membership of each of these sub-catchments is derived from its NCB code. Changes at v2.1 - SegnoLink updates. ! updates to NCB level 2 names to conform with HR_Regions. Changes at v2.1.1 ! Updates to NCB level 2 names to conform with HR_Regions. - SegnoLink attribute update to fix single catchment feature in Tasmania. - Correction to spelling of Numeralla river in AHGFCatchment (formerly Numaralla). - Correction of name for NCBLevel2DrainageBasinGroup, 'Moorabool River' Basin Group renamed to 'Little River'. - Fixed a series of NoFlow catchments (small internally draining catchments not related to a stream segment) in Murray-Darling were incorrectly attributed as externally draining via the ExtrnlBasn field in AHGFCatchments. - Fixed Basin attribute values in NCBPfafstetterm, which were incorrectly populated with BasinLevel field. Processing steps: ANUDEM v1.1.4 National Catchment Boundaries (NCBs) dataset is received and loaded into the Geofabric development GIS environment. feature classes from ANUDEM NCBs are recomposed into composited Geofabric Framework Dataset feature classes in the Geofabric Maintenance Geodatabase. re-composited feature classes in the Geofabric Maintenance Geodatabase Feature Dataset are assigned unique Hydro-IDs using ESRI ArcHydro for Surface Water (ArcHydro: 1.4.0.180 and ApFramework: 3.1.0.84) feature classes from the Geofabric Maintenance Geodatabase Feature Dataset are extracted and reassigned to the Geofabric Surface Catchment Feature Dataset within the Geofabric Surface Catchment Geodatabase. A complete set of data mappings, from input source data to Geofabric Products, is included in the Geofabric Product Guide, Appendices. Dataset Citation Bureau of Meteorology (2015) Geofabric Surface Catchments - V2.1.1. Bioregional Assessment Source Dataset. Viewed 18 July 2018, http://data.bioregionalassessments.gov.au/dataset/f50136c8-5ca0-4165-91d2-bb0ed66866e4.

This feature class represents the Basins (6-digit Hydrologic Units) that overlap the Chihuahuan Desert REA Analysis Extent (CHD_Boundary_Poly).

The Watershed Boundary Dataset (WBD) is a comprehensive aggregated collection of hydrologic unit data consistent with the national criteria for delineation and resolution. It defines the areal extent of surface water drainage to a point except in coastal or lake front areas where there could be multiple outlets as stated by the Federal Standards and Procedures for the National Watershed Boundary Dataset (WBD) #8220;Standard#8221; (http:pubs.usgs.govtm11a3). Watershed boundaries are determined solely upon science-based hydrologic principles, not favoring any administrative boundaries or special projects, nor particular program or agency. This dataset represents the hydrologic unit boundaries to the 12-digit (6th level) for the entire United States. Some areas may also include additional subdivisions representing the 14- and 16-digit hydrologic unit (HU). At a minimum, the HUs are delineated at 1:24,000-scale in the conterminous United States, 1:25,000-scale in Hawaii, Pacific basin and the Caribbean, and 1:63,360-scale in Alaska, meeting the National Map Accuracy Standards (NMAS). Higher resolution boundaries are being developed where partners and data exist and will be incorporated back into the WBD. WBD data are delivered as a dataset of polygons and corresponding lines that define the boundary of the polygon. WBD polygon attributes include hydrologic unit codes (HUC), size (in the form of acres and square kilometers), name, downstream hydrologic unit code, type of watershed, non-contributing areas, and flow modifications. The HUC describes where the unit is in the country and the level of the unit. WBD line attributes contain the highest level of hydrologic unit for each boundary, line source information and flow modifications.

Please be advised that there are issues with the Small Area boundary dataset generalised to 20m which affect Small Area 268014010 in Ballygall D, Dublin City. The Small Area boundary dataset generalised to 20m is in the process of being revised and the updated datasets will be available as soon as the boundaries are amended. This feature layer was created using Census 2016 data produced by the Central Statistics Office (CSO) and Small Areas national boundary data (generalised to 20m) produced by Tailte Éireann. The layer represents Census 2016 theme 9.1, population aged 15+ by sex and social class. Attributes include population breakdown by social class and sex (e.g. skilled manual - males, non-manual - females). Census 2016 theme 9 represents Social Class and Socio-Economic Group. The Census is carried out every five years by the CSO to determine an account of every person in Ireland. The results provide information on a range of themes, such as, population, housing and education. The data were sourced from the CSO. The Small Area Boundaries were created with the following credentials. National boundary dataset. Consistent sub-divisions of an ED. Created not to cross some natural features. Defined area with a minimum number of GeoDirectory building address points. Defined area initially created with minimum of 65 – approx. average of around 90 residential address points. Generated using two bespoke algorithms which incorporated the ED and Townland boundaries, ortho-photography, large scale vector data and GeoDirectory data. Before the 2011 census they were split in relation to motorways and dual carriageways. After the census some boundaries were merged and other divided to maintain privacy of the residential area occupants. They are available as generalised and non generalised boundary sets.

The pathway representation consists of segments and intersection elements. A segment is a linear graphic element that represents a continuous physical travel path terminated by path end (dead end) or physical intersection with other travel paths. Segments have one street name, one address range and one set of segment characteristics. A segment may have none or multiple alias street names. Segment types included are Freeways, Highways, Streets, Alleys (named only), Railroads, Walkways, and Bike lanes. SNDSEG_PV is a linear feature class representing the SND Segment Feature, with attributes for Street name, Address Range, Alias Street name and segment Characteristics objects. Part of the Address Range and all of Street name objects are logically shared with the Discrete Address Point-Master Address File layer. Appropriate uses include: Cartography - Used to depict the City's transportation network _location and connections, typically on smaller scaled maps or images where a single line representation is appropriate. Used to depict specific classifications of roadway use, also typically at smaller scales. Used to label transportation network feature names typically on larger scaled maps. Used to label address ranges with associated transportation network features typically on larger scaled maps. Geocode reference - Used as a source for derived reference data for address validation and theoretical address _location Address Range data repository - This data store is the City's address range repository defining address ranges in association with transportation network features. Polygon boundary reference - Used to define various area boundaries is other feature classes where coincident with the transportation network. Does not contain polygon features. Address based extracts - Used to create flat-file extracts typically indexed by address with reference to business data typically associated with transportation network features. Thematic linear _location reference - By providing unique, stable identifiers for each linear feature, thematic data is associated to specific transportation network features via these identifiers. Thematic intersection _location reference - By providing unique, stable identifiers for each intersection feature, thematic data is associated to specific transportation network features via these identifiers. Network route tracing - Used as source for derived reference data used to determine point to point travel paths or determine optimal stop allocation along a travel path. Topological connections with segments - Used to provide a specific definition of _location for each transportation network feature. Also provides a specific definition of connection between each transportation network feature. (defines where the streets are and the relationship between them ie. 4th Ave is west of 5th Ave and 4th Ave does intersect with Cherry St) Event _location reference - Used as source for derived reference data used to locate event and linear referencing.Data source is TRANSPO.SNDSEG_PV. Updated weekly.

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

This polyline feature class represents the arc features that will define the boundaries of the Bureau of Land Management (BLM) Eastern States (ES) Land Use Planning Areas (LUPA) polygons. Land Use Planning Areas are geographic areas within which the BLM makes decisions during land use planning efforts.

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. 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. The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR GIS Spatial Data Standards. DWR makes no warranties or guarantees, either expressed or implied, as to the completeness, accuracy or correctness of the data, nor accepts or assumes any liability arising from or for any incorrect, incomplete or misleading subject data. The official DWR GIS Data Steward for this dataset is Brett Wyckoff, who may be contacted at 916-902-6779, or at brett.wyckoff@water.ca.gov. Comments, problems, improvements, updates, or suggestions should be forwarded to the official GIS Data Steward as available and appropriate.

Class B Units represent a footprint of a residential or commercial unit on the ground. The boundary is defined by a surveyed line around the land the unit sits on. The Class B Units data is being continuously maintained based on registered Unit Plans. All data is based on computed design to fit mathematically within survey control. Unit boundaries are created by entering data that has been submitted by registered unit plans.

Creative Commons License Creative Common By Attribution 4.0 (Australian Capital Territory), Please read Data Terms and Conditions statement before data use.

Local Government Area depicts polygons of gazette boundaries defining the Local Government Area. It contains all of the cadastral line data or topographic features which are used to define the boundaries between adjoining shires, municipalities, cities (Local Government Act 1993) and the unincorporated areas of NSW. The dataset also contains Council Names and ABS Codes It is a feature class within the NSW Digital Cadastral Database (DCDB).

Access APIAdministrative Boundaries Theme - Federal Electoral Division Please Note WGS 84 service aligned to GDA94 This dataset has spatial reference [WGS 84 ≈ GDA94] which may result in misalignments when viewed in GDA2020 environments. A similar service with a ‘multiCRS’ suffix is available which can support GDA2020, GDA94 and WGS 84 ≈ GDA2020 environments. In due course, and allowing time for user feedback and testing, it is intended that the original service name will adopt the new …Show full description Access APIAdministrative Boundaries Theme - Federal Electoral Division Please Note WGS 84 service aligned to GDA94 This dataset has spatial reference [WGS 84 ≈ GDA94] which may result in misalignments when viewed in GDA2020 environments. A similar service with a ‘multiCRS’ suffix is available which can support GDA2020, GDA94 and WGS 84 ≈ GDA2020 environments. In due course, and allowing time for user feedback and testing, it is intended that the original service name will adopt the new multiCRS functionally.NSW Federal Electoral Division is a feature class which represents a gazetted area of a federal electoral division that has been defined by redistribution. NSW Federal Electoral Division is a feature class within the Administrative boundaries theme. It represents a gazetted area of a federal electoral division that has been defined by redistribution. Australian Electoral Commission is responsible for this dataset. Any changes that occur to the dataset should have a reference in the authority of reference feature class in the Administrative boundaries. Features are typically positioned in alignment within the extents of the cadastral polygons and NSW Lot and Property data changes impact this dataset. This dataset is current as per last redistribution. Metadata Type Esri Feature Service Update Frequency As required Contact Details Contact us via the Spatial Services Customer Hub Relationship to Themes and Datasets Administrative Boundaries Theme of the Foundation Spatial Data Framework (FSDF) Accuracy The dataset maintains a positional relationship to, and alignment with, the Lot and Property digital datasets. This dataset was captured by digitising the best available cadastral mapping at a variety of scales and accuracies, ranging from 1:500 to 1:250 000 according to the National Mapping Council of Australia, Standards of Map Accuracy (1975). Therefore, the position of the feature instance will be within 0.5mm at map scale for 90% of the well-defined points. That is, 1:500 = 0.25m, 1:2000 = 1m, 1:4000 = 2m, 1:25000 = 12.5m, 1:50000 = 25m and 1:100000 = 50m. A program of positional upgrade (accuracy improvement) is currently underway. Spatial Reference System (dataset) Geocentric Datum of Australia 1994 (GDA94), Australian Height Datum (AHD) Spatial Reference System    (web service) EPSG 4326: WGS 84 Geographic 2D WGS 84 Equivalent To GDA94 Spatial Extent Full State Standards and Specifications Open Geospatial Consortium (OGC) implemented and compatible for consumption by common GIS platforms. Available as either cache or non-cache, depending on client use or requirement. Information about the Feature Class and Domain Name descriptions for the NSW Administrative Boundaries Theme can be found in the NSW Cadastral Delivery Model Data Dictionary Some of Spatial Services Datasets are designed to work together for example NSW Address Point and NSW Address String (table), NSW Property (Polygon) and NSW Property Lot (table) and NSW Lot (polygons). To do this you need to add a Spatial Join. A Spatial Join is a GIS operation that affixes data from one feature layer’s attribute table to another from a spatial perspective. To see how NSW Address, Property, Lot Geometry data and tables can be spatially joined, download the Data Model Document. Distributors Service Delivery, DCS Spatial Services 346 Panorama Ave Bathurst NSW 2795 Dataset Producers and Contributors Administrative Spatial Programs, DCS Spatial Services 346 Panorama Ave Bathurst NSW 2795

This polygon feature class dataset contains properties that are managed by the Parks & Recreation Department of Hillsborough County. The Parks & Recreation Department operates numerous parks, playgrounds, athletic fields, and recreation centers. The department also provides programs, events, and activities to Hillsborough County residents year-round. The dataset was developed using property appraisal dataset and field surveys for park boundaries. The dataset is updated as needed basis when park properties status changes.

State Electoral District dataset represents current NSW or NSW Federal electoral boundaries in conjunction with the Electoral Commission, containing all of the cadastral line data or topographic …Show full descriptionState Electoral District dataset represents current NSW or NSW Federal electoral boundaries in conjunction with the Electoral Commission, containing all of the cadastral line data or topographic data features which form, by definition, the boundaries between adjoining electorates. It is a polygon feature class within the NSW Digital Cadastral Database (DCDB).