The LIST Feature Metadata Pointers dataset holds reliability dates, horizontal and vertical accuracies and source for every LIST spatial feature maintained by Land Tasmania, DPIPWE. All Land Information System for Tasmania (LIST) datasets hold a FMP (Feature Metadata Pointer) as an attribute for every feature. This dataset provides a breakup of accuracies for these FMP's thus allowing the user to determine the reliability date and accuracy for a particular feature.
The FMP dataset is to be used in conjunction with other LIST spatial datasets to enable users to ascertain the accuracy and reliability of the features within those other datasets.
The MassDEP Division of Watershed Management (DWM), Watershed Planning Program’s (WPP) 2018/2020 Integrated List of Waters data layer provides EPA-approved water quality assessment and listing decisions for the 2018/2020 reporting cycle, as required by the Clean Water Act (CWA) under Sections 305(b), 314, and 303(d). The objective of the CWA is to restore and maintain the chemical, physical, and biological integrity of the Nation's waters. As one step toward meeting this goal each state must administer a program to monitor and assess the quality of its surface waters and provide periodic status reports to the U.S. Environmental Protection Agency (EPA).More details...Map service also available.
The Geodatabase to Shapefile Warning Tool examines feature classes in input file geodatabases for characteristics and data that would be lost or altered if it were transformed into a shapefile. Checks include:
1) large files (feature classes with more than 255 fields or over 2GB), 2) field names longer than 10 characters
string fields longer than 254 characters, 3) date fields with time values 4) NULL values, 5) BLOB, guid, global id, and raster field types, 6) attribute domains or subtypes, and 7) annotation or topology
The results of this inspection are written to a text file ("warning_report_[geodatabase_name]") in the directory where the geodatabase is located. A section at the top provides a list of feature classes and information about the geodatabase as a whole. The report has a section for each valid feature class that returned a warning, with a summary of possible warnings and then more details about issues found.
The tool can process multiple file geodatabases at once. A separate text file report will be created for each geodatabase. The toolbox was created using ArcGIS Pro 3.7.11.
For more information about this and other related tools, explore the Geospatial Data Curation toolkit
The MassDEP Division of Watershed Management (DWM), Watershed Planning Program (WPP) 2014 Integrated List of Waters (305(b)/303(d)) data layer represents the combined reporting elements for the 2014 cycle of both sections 305(b) and 303(d) of the Federal Clean Water Act (CWA). The objective of this statute is to restore and maintain the chemical, physical, and biological integrity of the Nation's waters. As one step toward meeting this goal each state must administer a program to monitor and assess the quality of its surface waters and provide periodic status reports to the U.S. Environmental Protection Agency (EPA), the U.S. Congress, and the public.More details...Map service also available.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Comma separated file containg original data for the Cancer lists example. Each list is a collection of Entrez identifiers from human or from another species. The file was downloaded from the url: http://www.bushmanlab.org/links/genelists . (CSV 284 kb)
The 2022 Integrated List of Waters data is the spatial representation of the river, lake, and estuary segments assessed and summarized in the Massachusetts Year 2018 Integrated List of Waters report to the EPA developed pursuant to sections 305(b), 314, and 303(d) of the Federal Clean Water Act.Map service also available.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
This feature dataset contains feature classes that depict the distribution and critical habitat of species list under the Endangered Species Act which occur in Alaska waters. See Spatial Data Properies for a list of individual species. Please see http://alaskafisheries.noaa.gov/mapping/esa/ for more info.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Comma separated file containg original data for the Kidney lists example. Each list is a collection of affymetrix probesets from hgu133plus2 arrays. The file was downloaded from the url: https://www.ualberta.ca/medicine/institutes-centres-groups/atagc/research/gene-lists . (TSV 61 kb)
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
List of features at each address.
The MassDEP Division of Watershed Management (DWM), Watershed Planning Program’s (WPP) 2016 Integrated List of Waters data layer provides EPA-approved water quality assessment and listing decisions for the 2016 reporting cycle, as required by the Clean Water Act (CWA) under Sections 305(b), 314, and 303(d). The objective of the CWA is to restore and maintain the chemical, physical, and biological integrity of the Nation's waters. As one step toward meeting this goal each state must administer a program to monitor and assess the quality of its surface waters and provide periodic status reports to the U.S. Environmental Protection Agency (EPA).More details...Map service also available.
This data release contains the analytical results and the evaluated source data files of a geospatial analysis for identifying areas in Alaska that may have potential for sediment-hosted Pb-Zn (lead-zinc) deposits. The spatial analysis is based on queries of statewide source datasets Alaska Geochemical Database (AGDB3), Alaska Resource Data File (ARDF), and Alaska Geologic Map (SIM3340) within areas defined by 12-digit HUCs (subwatersheds) from the National Watershed Boundary dataset. The packages of files available for download are: 1. The results in geodatabase format are in SedPbZn_Results_gdb.zip. The analytical results for sediment-hosted Pb-Zn deposits are in a polygon feature class which contains the points scored for each source data layer query, the accumulative score, and a designation for high, medium, or low potential and high, medium, or low certainty for sediment-hosted Pb-Zn deposits for each HUC. The data is described by FGDC metadata. An mxd file, layer file, and cartographic feature classes are provided for display of the results in ArcMap. Files sedPbZn_scoring_tables.pdf (list of the scoring parameters for the analysis) and sedPbZn_Results_gdb_README.txt (description of the files in this download package) are included. 2. The results in shapefile format are in SedPbZn_Results_shape.zip. The analytical results for sediment-hosted Pb-Zn deposits are in a polygon feature class which contains the points scored for each source data layer query, the accumulative score, and designation for high, medium, or low potential and high, medium, or low certainty for sediment-hosted Pb-Zn deposits for each HUC. The results are also provided as a CSV file. The data is described by FGDC metadata. Files sedPbZn_scoring_tables.pdf (list of the scoring parameters for the analysis) and sedPbZn_Results_shape_README.txt (description of the files in this download package) are included. 3. The source data in geodatabase format are in SedPbZn_SourceData_gdb.zip. Data layers include AGDB3, ARDF, lithology from SIM3340, and HUC subwatersheds, with FGDC metadata. An mxd file and cartographic feature classes are provided for display of the source data in ArcMap. Also included are two python scripts 1) to score the ARDF records based on the presence of certain keywords, and 2) to evaluate the ARDF, AGDB3, and lithology layers for the potential for sediment-hosted Pb-Zn deposits within subwatershed polygons. Users may modify the scripts to design their own analyses. Files sedPbZn_scoring_table.pdf (list of the scoring parameters for the analysis) and sedPbZn_sourcedata_gdb_README.txt (description of the files in this download package) are included. 4. The source data in shapefile and CSV format are in SedPbZn_SourceData_shape.zip. Data layers include ARDF and lithology from SIM3340, and HUC subwatersheds, with FGDC metadata. The ARDF keyword tables available in the geodatabase package are presented here as CSV files. All data files are described with the FGDC metadata. Files sedPb_Zn_scoring_table.pdf (list of the scoring parameters for the analysis) and sedPbZn_sourcedata_shapefile_README.txt (description of the files in this download package) are included. 5. Appendices 2, 3 and 4, which are cited by the larger work OFR2020-1147. Files are presented in XLSX and CSV formats.
No description is available. Visit https://dataone.org/datasets/19c2e03c2dd9c6ef2bc0d4f38c75343b for complete metadata about this dataset.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
The Census Bureau adds landmark features to the database on an as-needed basis and makes no attempt to ensure that all instances of a particular feature were included. The landmarks were not used to build or maintain the 2010 Census address list, and the absence of a landmark such as a hospital or prison does not mean that associated living quarters were excluded from the 2010 Census enumeration. Area landmark and area water features can overlap; for example, a park or other special land-use feature may include a lake or pond. In this case, the polygon covered by the lake or pond belongs to a water feature and a park landmark feature. Other kinds of landmarks can overlap as well. Area landmarks can contain point landmarks, but TIGER/Line Shapefiles do not contain links to these features. All landmarks have a MAF/TIGER feature class code (MTFCC) that identifies the type of feature and may or may not have a specific feature name. A full MTFCC list with definitions for the 2019 TIGER/Line Shapefiles is provided in Appendix E. Each landmark has a unique area landmark identifier (AREAID) or point landmark identifier (POINTID) value.
A point feature class representing the random site selections within small lakes comprising the small lake sample frames from the cycle 1 to the most recent Status Network cycle. Refer to https://floridadep.gov/DEAR/Watershed-Monitoring-Section for more information on the Status monitoring network.
Approximate plot locations with invasive plant species. Each point has number of IPS on plot and lists species found. This feature class has locations in Illinois, Michigan, and Minnesota.
A point feature class representing the random site selections within low order streams, and small streams, comprising the low order stream and small stream sample frames from the Cycle 1 to the most recent Status Network cycle. Refer to https://floridadep.gov/dear/watershed-monitoring-section/content/status-monitoring-network for more information on the Status monitoring network.
WorldClim 2.1 provides downscaled estimates of climate variables as monthly means over the period of 1970-2000 based on interpolated station measurements. Here we provide analytical image services of precipitation for each month along with an annual mean. Each time step is accessible from a processing template.Time Extent: Monthly/Annual 1970-2000Units: mm/monthCell Size: 2.5 minutes (~5 km)Source Type: StretchedPixel Type: 16 Bit IntegerData Projection: GCS WGS84Mosaic Projection: GCS WGS84Extent: GlobalSource: WorldClim v2.1Using Processing Templates to Access TimeThere are 13 processing templates applied to this service, each providing access to the 12 monthly and 1 annual mean precipitation layers. To apply these in ArcGIS Online, select the Image Display options on the layer. Then pull down the list of variables from the Renderer options. Click Apply and Close. In ArcGIS Pro, go into the Layer Properties. Select Processing Templates from the left-hand menu. From the Processing Template pull down menu, select the version to display.What can you do with this layer?This layer may be added to maps to visualize and quickly interrogate each pixel value. The pop-up provides a graph of the time series along with the calculated annual mean value.This layer can be used in analysis. For example, the layer may be added to ArcGIS Pro and an area count of precipitation may be produced for a feature dataset using the zonal statistics tool. Statistics may be compared with the statistics from month to month to show seasonal patterns.To calculate precipitation by land area, or any other analysis, be sure to use an equal area projection, such as Albers or Equal Earth.Source Data: The datasets behind this layer were extracted from GeoTIF files produced by WorldClim at 2.5 minutes resolution. The mean of the 12 GeoTIFs was calculated (annual), and the 13 rasters were converted to Cloud Optimized GeoTIFF format and added to a mosaic dataset.Citation: Fick, S.E. and R.J. Hijmans, 2017. WorldClim 2: new 1km spatial resolution climate surfaces for global land areas. International Journal of Climatology 37 (12): 4302-4315.
This parcel lines feature class represents the current city parcel lines within the City of Los Angeles. It shares topology with the Landbase Parcel_polygons feature class. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way, ownership and land record information. The legal boundaries are determined on the ground by license surveyors in the State of California, and by recorded documents from the Los Angeles County Recorder's office and the City Clerk's office of the City of Los Angeles. Parcel and ownership information are available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.Associated information about the landbase parcel lines is entered into attributes. Principal attributes include:CV_LAYER: is the principal field that describes the various types of lines like street and freeway right-of-ways, tract, lots, government property and easements lines, private street lines, utility right-of-ways, and ownership lines. For a complete list of attribute values, please refer to Landbase_parcel_lines_data_dictionary.Landbase parcels lines layer was created in geographical information systems (GIS) software to display the location of parcel lots. The parcels lines layer is a feature class in the LACityLandbaseData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. The lines are derived from the polygon feature class in the landbase parcels layer, and information about the lines is entered into attributes. The CV_LAYER field values describe the various types of lines. The right-of-way, row, line features consist of CV_LAYER = 6, CV_LAYER = 106, and portions of CV_LAYER = 1 where that line is both the city boundary and the parcel line. In some cases, a parcel line will share two different type descriptions. Refer to CV_LAYER field metadata for further explantion. Parcel information should only be added to the Landbase Parcels layer if documentation exists, such as a Deed or a Plan approved by the City Council. When seeking the definitive description of real property, consult the recorded Deed or Plan.List of Fields:ASSETIDCV_LAYER: This value is a number representing a different type of user-assigned layer. Each of the line segments in the landbase parcels lines are assigned one of the CV_LAYER numbers, representing a different type of line work, described below. In some cases, a parcel line will share two different type descriptions. Such as, a parcel line may have CV_LAYER = 1 City Boundary line, and it is a CV_LAYER = 8 Tract line. The Tract line description is used first, and the City Boundary line description is used second. When selecting City Boundary line using CV_LAYER = 1, then (special way to select data...). The right-of-way, row, line features consist of CV_LAYER = 6, CV_LAYER = 106, and portions of CV_LAYER = 1 where that line is both the city boundary and the parcel line. Values: • 50 - Lot cut linework. • 38 - Freeway ease as easement lines. • 108 - Tract lines that are private street lines. • 8 - Tract lines, Rancho lines, Freeway (Fwy), and Right of way lines. • 30 - Former city boundary lines; other city or county boundary line. • 34 - Overlap lines. • 6 - Right of way (R/W) sidelines. • 19 - LA City easement lines. • 21 - All governmental lines (Fee). • 37 - APN (BPP) lines shown on tax assessors map (PCL maps); but no new PIN is created for the parcels polygon feature. • 48 - Subdivision title anno shown for ownership purpose (lot cut). • 10 - Lot lines. • 68 - SBBM (San Bernardino Base Meridian) section lines. • 1 - Boundary lines (existing). • 110 - Lot lines that are private street lines. • 18 - All governmental easement lines (except LA City and State freeway ease right of way lines). • 106 - Fwy traveled roadway lines; Dash right of way lines; Railroad and transmission lines. • 0 - Cadastral format.SHAPE: Feature geometry.OBJECTID: Internal feature number.ID: A unique numeric identifier of the polygon. The ID value is the last part of the PIN field value.MAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral tract index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers.
A point feature class representing the random site selections within large lakes comprising the large lake sample frames from Cycle 2 to the current Status Network cycle. Refer to https://floridadep.gov/dear/watershed-monitoring-section/content/status-monitoring-network for more information on the Status monitoring network.
Terms of Use:
Data Limitations Disclaimer
The MassDEP Estimated Sewer System Service Area Boundaries datalayer may not be complete, may contain errors, omissions, and other inaccuracies, and the data are subject to change. The user’s use of and/or reliance on the information contained in the Document (e.g. data) shall be at the user’s own risk and expense. MassDEP disclaims any responsibility for any loss or harm that may result to the user of this data or to any other person due to the user’s use of the Document.
All sewer service area delineations are estimates for broad planning purposes and should only be used as a guide. The data is not appropriate for site-specific or parcel-specific analysis. Not all properties within a sewer service area are necessarily served by the system, and some properties outside the mapped service areas could be served by the wastewater utility – please contact the relevant wastewater system. Not all service areas have been confirmed by the sewer system authorities.
This is an ongoing data development project. Attempts have been made to contact all sewer/wastewater systems, but not all have responded with information on their service area. MassDEP will continue to collect and verify this information. Some sewer service areas included in this datalayer have not been verified by the POTWs, privately-owned treatment works, GWDPs, or the municipality involved, but since many of those areas are based on information published online by the municipality, the utility, or in a publicly available report, they are included in the estimated sewer service area datalayer.
Please use the following citation to reference these data
MassDEP. Water Utility Resilience Program. 2025. Publicly-Owned Treatment Work and Non-Publicly-Owned Sewer Service Areas (PubV2024_12).
We want to learn about the data uses. If you use this dataset, please notify staff in the Water Resilience program (WURP@mass.gov).
Layers and Tables:
The MassDEP Estimated Sewer System Service Area data layer comprises two feature classes and a supporting table:
Publicly-Owned Treatment Works (POTW) Sewer Service Areas feature class SEWER_SERVICE_AREA_POTW_POLY includes polygon features for sewer service areas systems operated by publicly owned treatment works (POTWs)Non-Publicly Owned Treatment Works (NON-POTW) Sewer Service Areas feature class SEWER_SERVICE_AREA_NONPOTW_POLY includes polygon features for sewer service areas for operated by NON publicly owned treatment works (NON-POTWs)The Sewer Service Areas Unlocated Sites table SEWER_SERVICE_AREA_USL contains a list of known, unmapped active POTW and NON-POTW services areas at the time of publication.
ProductionData Universe
Effluent wastewater treatment plants in Massachusetts are permitted either through the Environmental Protection Agency’s (EPA) National Pollutant Discharge Elimination System (NPDES) surface water discharge permit program or the MassDEP Groundwater Discharge Permit Program. The WURP has delineated active service areas served by publicly and privately-owned effluent treatment works with a NPDES permit or a groundwater discharge permit.
National Pollutant Discharge Elimination System (NPDES) Permits
In the Commonwealth of Massachusetts, the EPA is the permitting authority for regulating point sources that discharge pollutants to surface waters. NPDES permits regulate wastewater discharge by limiting the quantities of pollutants to be discharged and imposing monitoring requirements and other conditions. NPDES permits are typically co-issued by EPA and the MassDEP. The limits and/or requirements in the permit ensure compliance with the Massachusetts Surface Water Quality Standards and Federal Regulations to protect public health and the aquatic environment. Areas served by effluent treatment plants with an active NPDES permit are included in this datalayer based on a master list developed by MassDEP using information sourced from the EPA’s Integrated Compliance Information System (ICIS).
Groundwater Discharge (GWD) Permits
In addition to surface water permittees, the WURP has delineated all active systems served by publicly and privately owned effluent treatment works with groundwater discharge (GWD) permits, and some inactive service areas. Groundwater discharge permits are required for systems discharging over 10,000 GPD sanitary wastewater – these include effluent treatment systems for public, district, or privately owned effluent treatment systems. Areas served by an effluent treatment plant with an active GWD permit are included in this datalayer based on lists received from MassDEP Wastewater staff.
Creation of Unique IDs for Each Service Area
The Sewer Service Area datalayer contains polygons that represent the service area of a particular wastewater system within a particular municipality. Every discharge permittee is assigned a unique NPDES permit number by EPA or a unique GWD permit identifier by MassDEP. MassDEP WURP creates a unique Sewer_ID for each service area by combining the municipal name of the municipality served with the permit number (NPDES or GWD) ascribed to the sewer that is serving that area. Some municipalities contain more than one sewer system, but each sewer system has a unique Sewer_ID. Occasionally the area served by a sewer system will overlap another town by a small amount – these small areas are generally not given a unique ID. The Estimated sewer Service Area datalayer, therefore, contains polygons with a unique Sewer_ID for each sewer service area. In addition, some municipalities will have multiple service areas being served by the same treatment plant – the Sewer_ID for these will contain additional identification, such as the name of the system, to uniquely identify each system.
Classifying System Service Areas
WURP staff reviewed the service areas for each system and, based on OWNER_TYPE, classified as either a publicly-owned treatment work (POTW) or a NON-POTW (see FAC_TYPE field). Each service area is further classified based on the population type served (see SECTOR field).
Methodologies and Data Sources
Several methodologies were used to create service area boundaries using various sources, including data received from the sewer system in response to requests for information from the MassDEP WURP project, information on file at MassDEP, and service area maps found online at municipal and wastewater system websites. When MassDEP received sewer line data rather than generalized areas, 300-foot buffers were created around the sewer lines to denote service areas and then edited to incorporate generalizations. Some municipalities submitted parcel data or address information to be used in delineating service areas. Many of the smaller GWD permitted sewer service areas were delineated using parcel boundaries related to the address on file.
Verification Process
Small-scale pdf file maps with roads and other infrastructure were sent to systems for corrections or verifications. If the system were small, such as a condominium complex or residential school, the relevant parcels were often used as the basis for the delineated service area. In towns where 97% or more of their population is served by the wastewater system and no other service area delineation was available, the town boundary was used as the service area boundary. Some towns responded to the request for information or verification of service areas by stating that the town boundary should be used since all, or nearly all, of the municipality is served by one wastewater system.
To ensure active systems are mapped, WURP staff developed two work flows. For NPDES-permitted systems, WURP staff reviewed available information on EPA’s ICIS database and created a master list of these systems. Staff will work to routinely update this master list by reviewing the ICIS database for new NPDES permits. The master list will serve as a method for identifying active systems, inactive systems, and unmapped systems. For GWD permittees, GIS staff established a direct linkage to the groundwater database, which allows for populating information into data fields and identifying active systems, inactive systems, and unmapped systems.
All unmapped systems are added to the Sewer Service Area Unlocated List (SEWER_SERVICE_AREAS_USL) for future mapping. Some service areas have not been mapped but their general location is represented by a small circle which serves as a placeholder - the location of these circles are estimated based on the general location of the treatment plant or the general estimated location of the service area - these do not represent the actual service area.
Percent Served Statistics The attribute table for the POTW sewer service areas (SEWER_SERVICE_AREA_POTW_POLY) has several fields relating to the percent of the town served by the particular system and one field describing the percent of town served by all systems in the town. The field ‘Percent AREA Served by System’ is strictly a calculation done dividing the area of the system by the total area of the town and multiplying by 100. In contrast, the field ‘Percent Served by System’, is not based on a particular calculation or source – it is an estimate based on various sources – these estimates are for planning purposes only. Data includes information from municipal websites and associated plans, the 1990 Municipal Priority list from CMR 310 14.17, the 2004 Pioneer Institute for Public Policy Research “percent on sewer” document, information contained on NPDES Permits and MassDEP Wastewater program staff input. Not all POTW systems have percent served statistics. Percentage may reflect the percentage of parcels served, the percent of area within a community served or the population served and should not be used for legal boundary definition or regulatory interpretation.
Sources of information for estimated wastewater service areas:
EEOA Water Assets
The LIST Feature Metadata Pointers dataset holds reliability dates, horizontal and vertical accuracies and source for every LIST spatial feature maintained by Land Tasmania, DPIPWE. All Land Information System for Tasmania (LIST) datasets hold a FMP (Feature Metadata Pointer) as an attribute for every feature. This dataset provides a breakup of accuracies for these FMP's thus allowing the user to determine the reliability date and accuracy for a particular feature.
The FMP dataset is to be used in conjunction with other LIST spatial datasets to enable users to ascertain the accuracy and reliability of the features within those other datasets.