Deprecation notice: This tool is deprecated because this functionality is now available with out-of-the-box tools in ArcGIS Pro. The tool author will no longer be making further enhancements or fixing major bugs.Use Add GTFS to a Network Dataset to incorporate transit data into a network dataset so you can perform schedule-aware analyses using the Network Analyst tools in ArcMap.After creating your network dataset, you can use the ArcGIS Network Analyst tools, like Service Area and OD Cost Matrix, to perform transit/pedestrian accessibility analyses, make decisions about where to locate new facilities, find populations underserved by transit or particular types of facilities, or visualize the areas reachable from your business at different times of day. You can also publish services in ArcGIS Server that use your network dataset.The Add GTFS to a Network Dataset tool suite consists of a toolbox to pre-process the GTFS data to prepare it for use in the network dataset and a custom GTFS transit evaluator you must install that helps the network dataset read the GTFS schedules. A user's guide is included to help you set up your network dataset and run analyses.Instructions:Download the tool. It will be a zip file.Unzip the file and put it in a permanent location on your machine where you won't lose it. Do not save the unzipped tool folder on a network drive, the Desktop, or any other special reserved Windows folders (like C:\Program Files) because this could cause problems later.The unzipped file contains an installer, AddGTFStoaNetworkDataset_Installer.exe. Double-click this to run it. The installation should proceed quickly, and it should say "Completed" when finished.Read the User's Guide for instructions on creating and using your network dataset.System requirements:ArcMap 10.1 or higher with a Desktop Standard (ArcEditor) license. (You can still use it if you have a Desktop Basic license, but you will have to find an alternate method for one of the pre-processing tools.) ArcMap 10.6 or higher is recommended because you will be able to construct your network dataset much more easily using a template rather than having to do it manually step by step. This tool does not work in ArcGIS Pro. See the User's Guide for more information.Network Analyst extensionThe necessary permissions to install something on your computer.Data requirements:Street data for the area covered by your transit system, preferably data including pedestrian attributes. If you need help preparing high-quality street data for your network, please review this tutorial.A valid GTFS dataset. If your GTFS dataset has blank values for arrival_time and departure_time in stop_times.txt, you will not be able to run this tool. You can download and use the Interpolate Blank Stop Times tool to estimate blank arrival_time and departure_time values for your dataset if you still want to use it.Help forum
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
Terms of UseData Limitations and DisclaimerThe user’s use of and/or reliance on the information contained in the Document 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.This is an ongoing data development project. Attempts have been made to contact all PWS systems, but not all have responded with information on their service area. MassDEP will continue to collect and verify this information. Some PWS service areas included in this datalayer have not been verified by the PWS or the municipality involved, but since many of those areas are based on information published online by the municipality, the PWS, or in a publicly available report, they are included in the estimated PWS service area datalayer.Please note: All PWS 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 PWS service area are necessarily served by the system, and some properties outside the mapped service areas could be served by the PWS – please contact the relevant PWS. Not all service areas have been confirmed by the systems.Please use the following citation to reference these data:MassDEP, Water Utility Resilience Program. 2025. Community and Non-Transient Non-Community Public Water System Service Area (PubV2025_3).IMPORTANT NOTICE: This MassDEP Estimated Water Service datalayer may not be complete, may contain errors, omissions, and other inaccuracies and the data are subject to change. This version is published through MassGIS. We want to learn about the data uses. If you use this dataset, please notify staff in the Water Utility Resilience Program (WURP@mass.gov).This GIS datalayer represents approximate service areas for Public Water Systems (PWS) in Massachusetts. In 2017, as part of its “Enhancing Resilience and Emergency Preparedness of Water Utilities through Improved Mapping” (Critical Infrastructure Mapping Project ), the MassDEP Water Utility Resilience Program (WURP) began to uniformly map drinking water service areas throughout Massachusetts using information collected from various sources. Along with confirming existing public water system (PWS) service area information, the project collected and verified estimated service area delineations for PWSs not previously delineated and will continue to update the information contained in the datalayers. As of the date of publication, WURP has delineated Community (COM) and Non-Transient Non-Community (NTNC) service areas. Transient non-community (TNCs) are not part of this mapping project.Layers and Tables:The MassDEP Estimated Public Water System Service Area data comprises two polygon feature classes and a supporting table. Some data fields are populated from the MassDEP Drinking Water Program’s Water Quality Testing System (WQTS) and Annual Statistical Reports (ASR).The Community Water Service Areas feature class (PWS_WATER_SERVICE_AREA_COMM_POLY) includes polygon features that represent the approximate service areas for PWS classified as Community systems.The NTNC Water Service Areas feature class (PWS_WATER_SERVICE_AREA_NTNC_POLY) includes polygon features that represent the approximate service areas for PWS classified as Non-Transient Non-Community systems.The Unlocated Sites List table (PWS_WATER_SERVICE_AREA_USL) contains a list of known, unmapped active Community and NTNC PWS services areas at the time of publication.ProductionData UniversePublic Water Systems in Massachusetts are permitted and regulated through the MassDEP Drinking Water Program. The WURP has mapped service areas for all active and inactive municipal and non-municipal Community PWSs in MassDEP’s Water Quality Testing Database (WQTS). Community PWS refers to a public water system that serves at least 15 service connections used by year-round residents or regularly serves at least 25 year-round residents.All active and inactive NTNC PWS were also mapped using information contained in WQTS. An NTNC or Non-transient Non-community Water System refers to a public water system that is not a community water system and that has at least 15 service connections or regularly serves at least 25 of the same persons or more approximately four or more hours per day, four or more days per week, more than six months or 180 days per year, such as a workplace providing water to its employees.These data may include declassified PWSs. Staff will work to rectify the status/water services to properties previously served by declassified PWSs and remove or incorporate these service areas as needed.Maps of service areas for these systems were collected from various online and MassDEP sources to create service areas digitally in GIS. Every PWS is assigned a unique PWSID by MassDEP that incorporates the municipal ID of the municipality it serves (or the largest municipality it serves if it serves multiple municipalities). Some municipalities contain more than one PWS, but each PWS has a unique PWSID. The Estimated PWS Service Area datalayer, therefore, contains polygons with a unique PWSID for each PWS service area.A service area for a community PWS may serve all of one municipality (e.g. Watertown Water Department), multiple municipalities (e.g. Abington-Rockland Joint Water Works), all or portions of two or more municipalities (e.g. Provincetown Water Dept which serves all of Provincetown and a portion of Truro), or a portion of a municipality (e.g. Hyannis Water System, which is one of four PWSs in the town of Barnstable).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 estimates based on the general location of the source wells or the general estimated location of the service area - these do not represent the actual service area.Service areas were mapped initially from 2017 to 2022 and reflect varying years for which service is implemented for that service area boundary. WURP maintains the dataset quarterly with annual data updates; however, the dataset may not include all current active PWSs. A list of unmapped PWS systems is included in the USL table PWS_WATER_SERVICE_AREA_USL available for download with the dataset. Some PWSs that are not mapped may have come online after this iteration of the mapping project; these will be reconciled and mapped during the next phase of the WURP project. PWS IDs that represent regional or joint boards with (e.g. Tri Town Water Board, Randolph/Holbrook Water Board, Upper Cape Regional Water Cooperative) will not be mapped because their individual municipal service areas are included in this datalayer.PWSs that do not have corresponding sources, may be part of consecutive systems, may have been incorporated into another PWSs, reclassified as a different type of PWS, or otherwise taken offline. PWSs that have been incorporated, reclassified, or taken offline will be reconciled during the next data update.Methodologies and Data SourcesSeveral methodologies were used to create service area boundaries using various sources, including data received from the systems 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 PWS websites. When provided with water line data rather than generalized areas, 300-foot buffers were created around the water 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.Verification ProcessSmall-scale PDF file maps with roads and other infrastructure were sent to every PWS for corrections or verifications. For small systems, 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 PWS 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 the PWS.Sources of information for estimated drinking water service areasThe following information was used to develop estimated drinking water service areas:EOEEA Water Assets Project (2005) water lines (these were buffered to create service areas)Horsely Witten Report 2008Municipal Master Plans, Open Space Plans, Facilities Plans, Water Supply System Webpages, reports and online interactive mapsGIS data received from PWSDetailed infrastructure mapping completed through the MassDEP WURP Critical Infrastructure InitiativeIn the absence of other service area information, for municipalities served by a town-wide water system serving at least 97% of the population, the municipality’s boundary was used. Determinations of which municipalities are 97% or more served by the PWS were made based on the Percent Water Service Map created in 2018 by MassDEP based on various sources of information including but not limited to:The Winter population served submitted by the PWS in the ASR submittalThe number of services from WQTS as a percent of developed parcelsTaken directly from a Master Plan, Water Department Website, Open Space Plan, etc. found onlineCalculated using information from the town on the population servedMassDEP staff estimateHorsely Witten Report 2008Calculation based on Water System Areas Mapped through MassDEP WURP Critical Infrastructure Initiative, 2017-2022Information found in publicly available PWS planning documents submitted to MassDEP or as part of infrastructure planningMaintenanceThe
Terms of UseData Limitations and DisclaimerThe user’s use of and/or reliance on the information contained in the Document 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.This is an ongoing data development project. Attempts have been made to contact all PWS systems, but not all have responded with information on their service area. MassDEP will continue to collect and verify this information. Some PWS service areas included in this datalayer have not been verified by the PWS or the municipality involved, but since many of those areas are based on information published online by the municipality, the PWS, or in a publicly available report, they are included in the estimated PWS service area datalayer.Please note: All PWS 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 PWS service area are necessarily served by the system, and some properties outside the mapped service areas could be served by the PWS – please contact the relevant PWS. Not all service areas have been confirmed by the systems.Please use the following citation to reference these data:MassDEP, Water Utility Resilience Program. 2025. Community and Non-Transient Non-Community Public Water System Service Area (PubV2025_3).IMPORTANT NOTICE: This MassDEP Estimated Water Service datalayer may not be complete, may contain errors, omissions, and other inaccuracies and the data are subject to change. This version is published through MassGIS. We want to learn about the data uses. If you use this dataset, please notify staff in the Water Utility Resilience Program (WURP@mass.gov).This GIS datalayer represents approximate service areas for Public Water Systems (PWS) in Massachusetts. In 2017, as part of its “Enhancing Resilience and Emergency Preparedness of Water Utilities through Improved Mapping” (Critical Infrastructure Mapping Project ), the MassDEP Water Utility Resilience Program (WURP) began to uniformly map drinking water service areas throughout Massachusetts using information collected from various sources. Along with confirming existing public water system (PWS) service area information, the project collected and verified estimated service area delineations for PWSs not previously delineated and will continue to update the information contained in the datalayers. As of the date of publication, WURP has delineated Community (COM) and Non-Transient Non-Community (NTNC) service areas. Transient non-community (TNCs) are not part of this mapping project.Layers and Tables:The MassDEP Estimated Public Water System Service Area data comprises two polygon feature classes and a supporting table. Some data fields are populated from the MassDEP Drinking Water Program’s Water Quality Testing System (WQTS) and Annual Statistical Reports (ASR).The Community Water Service Areas feature class (PWS_WATER_SERVICE_AREA_COMM_POLY) includes polygon features that represent the approximate service areas for PWS classified as Community systems.The NTNC Water Service Areas feature class (PWS_WATER_SERVICE_AREA_NTNC_POLY) includes polygon features that represent the approximate service areas for PWS classified as Non-Transient Non-Community systems.The Unlocated Sites List table (PWS_WATER_SERVICE_AREA_USL) contains a list of known, unmapped active Community and NTNC PWS services areas at the time of publication.ProductionData UniversePublic Water Systems in Massachusetts are permitted and regulated through the MassDEP Drinking Water Program. The WURP has mapped service areas for all active and inactive municipal and non-municipal Community PWSs in MassDEP’s Water Quality Testing Database (WQTS). Community PWS refers to a public water system that serves at least 15 service connections used by year-round residents or regularly serves at least 25 year-round residents.All active and inactive NTNC PWS were also mapped using information contained in WQTS. An NTNC or Non-transient Non-community Water System refers to a public water system that is not a community water system and that has at least 15 service connections or regularly serves at least 25 of the same persons or more approximately four or more hours per day, four or more days per week, more than six months or 180 days per year, such as a workplace providing water to its employees.These data may include declassified PWSs. Staff will work to rectify the status/water services to properties previously served by declassified PWSs and remove or incorporate these service areas as needed.Maps of service areas for these systems were collected from various online and MassDEP sources to create service areas digitally in GIS. Every PWS is assigned a unique PWSID by MassDEP that incorporates the municipal ID of the municipality it serves (or the largest municipality it serves if it serves multiple municipalities). Some municipalities contain more than one PWS, but each PWS has a unique PWSID. The Estimated PWS Service Area datalayer, therefore, contains polygons with a unique PWSID for each PWS service area.A service area for a community PWS may serve all of one municipality (e.g. Watertown Water Department), multiple municipalities (e.g. Abington-Rockland Joint Water Works), all or portions of two or more municipalities (e.g. Provincetown Water Dept which serves all of Provincetown and a portion of Truro), or a portion of a municipality (e.g. Hyannis Water System, which is one of four PWSs in the town of Barnstable).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 estimates based on the general location of the source wells or the general estimated location of the service area - these do not represent the actual service area.Service areas were mapped initially from 2017 to 2022 and reflect varying years for which service is implemented for that service area boundary. WURP maintains the dataset quarterly with annual data updates; however, the dataset may not include all current active PWSs. A list of unmapped PWS systems is included in the USL table PWS_WATER_SERVICE_AREA_USL available for download with the dataset. Some PWSs that are not mapped may have come online after this iteration of the mapping project; these will be reconciled and mapped during the next phase of the WURP project. PWS IDs that represent regional or joint boards with (e.g. Tri Town Water Board, Randolph/Holbrook Water Board, Upper Cape Regional Water Cooperative) will not be mapped because their individual municipal service areas are included in this datalayer.PWSs that do not have corresponding sources, may be part of consecutive systems, may have been incorporated into another PWSs, reclassified as a different type of PWS, or otherwise taken offline. PWSs that have been incorporated, reclassified, or taken offline will be reconciled during the next data update.Methodologies and Data SourcesSeveral methodologies were used to create service area boundaries using various sources, including data received from the systems 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 PWS websites. When provided with water line data rather than generalized areas, 300-foot buffers were created around the water 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.Verification ProcessSmall-scale PDF file maps with roads and other infrastructure were sent to every PWS for corrections or verifications. For small systems, 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 PWS 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 the PWS.Sources of information for estimated drinking water service areasThe following information was used to develop estimated drinking water service areas:EOEEA Water Assets Project (2005) water lines (these were buffered to create service areas)Horsely Witten Report 2008Municipal Master Plans, Open Space Plans, Facilities Plans, Water Supply System Webpages, reports and online interactive mapsGIS data received from PWSDetailed infrastructure mapping completed through the MassDEP WURP Critical Infrastructure InitiativeIn the absence of other service area information, for municipalities served by a town-wide water system serving at least 97% of the population, the municipality’s boundary was used. Determinations of which municipalities are 97% or more served by the PWS were made based on the Percent Water Service Map created in 2018 by MassDEP based on various sources of information including but not limited to:The Winter population served submitted by the PWS in the ASR submittalThe number of services from WQTS as a percent of developed parcelsTaken directly from a Master Plan, Water Department Website, Open Space Plan, etc. found onlineCalculated using information from the town on the population servedMassDEP staff estimateHorsely Witten Report 2008Calculation based on Water System Areas Mapped through MassDEP WURP Critical Infrastructure Initiative, 2017-2022Information found in publicly available PWS planning documents submitted to MassDEP or as part of infrastructure planningMaintenanceThe
In 2007, the California Ocean Protection Council initiated the California Seafloor Mapping Program (CSMP), designed to create a comprehensive seafloor map of high-resolution bathymetry, marine benthic habitats, and geology within California’s State Waters. The program supports a large number of coastal-zone- and ocean-management issues, including the California Marine Life Protection Act (MLPA) (California Department of Fish and Wildlife, 2008), which requires information about the distribution of ecosystems as part of the design and proposal process for the establishment of Marine Protected Areas. A focus of CSMP is to map California’s State Waters with consistent methods at a consistent scale. The CSMP approach is to create highly detailed seafloor maps through collection, integration, interpretation, and visualization of swath sonar data (the undersea equivalent of satellite remote-sensing data in terrestrial mapping), acoustic backscatter, seafloor video, seafloor photography, high-resolution seismic-reflection profiles, and bottom-sediment sampling data. The map products display seafloor morphology and character, identify potential marine benthic habitats, and illustrate both the surficial seafloor geology and shallow (to about 100 m) subsurface geology. It is emphasized that the more interpretive habitat and geology data rely on the integration of multiple, new high-resolution datasets and that mapping at small scales would not be possible without such data. This approach and CSMP planning is based in part on recommendations of the Marine Mapping Planning Workshop (Kvitek and others, 2006), attended by coastal and marine managers and scientists from around the state. That workshop established geographic priorities for a coastal mapping project and identified the need for coverage of “lands” from the shore strand line (defined as Mean Higher High Water; MHHW) out to the 3-nautical-mile (5.6-km) limit of California’s State Waters. Unfortunately, surveying the zone from MHHW out to 10-m water depth is not consistently possible using ship-based surveying methods, owing to sea state (for example, waves, wind, or currents), kelp coverage, and shallow rock outcrops. Accordingly, some of the data presented in this series commonly do not cover the zone from the shore out to 10-m depth. This data is part of a series of online U.S. Geological Survey (USGS) publications, each of which includes several map sheets, some explanatory text, and a descriptive pamphlet. Each map sheet is published as a PDF file. Geographic information system (GIS) files that contain both ESRI ArcGIS raster grids (for example, bathymetry, seafloor character) and geotiffs (for example, shaded relief) are also included for each publication. For those who do not own the full suite of ESRI GIS and mapping software, the data can be read using ESRI ArcReader, a free viewer that is available at http://www.esri.com/software/arcgis/arcreader/index.html (last accessed September 20, 2013). The California Seafloor Mapping Program is a collaborative venture between numerous different federal and state agencies, academia, and the private sector. CSMP partners include the California Coastal Conservancy, the California Ocean Protection Council, the California Department of Fish and Wildlife, the California Geological Survey, California State University at Monterey Bay’s Seafloor Mapping Lab, Moss Landing Marine Laboratories Center for Habitat Studies, Fugro Pelagos, Pacific Gas and Electric Company, National Oceanic and Atmospheric Administration (NOAA, including National Ocean Service–Office of Coast Surveys, National Marine Sanctuaries, and National Marine Fisheries Service), U.S. Army Corps of Engineers, the Bureau of Ocean Energy Management, the National Park Service, and the U.S. Geological Survey. These web services for the Offshore of Point Conception map area includes data layers that are associated to GIS and map sheets available from the USGS CSMP web page at https://walrus.wr.usgs.gov/mapping/csmp/index.html. Each published CSMP map area includes a data catalog of geographic information system (GIS) files; map sheets that contain explanatory text; and an associated descriptive pamphlet. This web service represents the available data layers for this map area. Data was combined from different sonar surveys to generate a comprehensive high-resolution bathymetry and acoustic-backscatter coverage of the map area. These data reveal a range of physiographic including exposed bedrock outcrops, large fields of sand waves, as well as many human impacts on the seafloor. To validate geological and biological interpretations of the sonar data, the U.S. Geological Survey towed a camera sled over specific offshore locations, collecting both video and photographic imagery; these “ground-truth” surveying data are available from the CSMP Video and Photograph Portal at https://doi.org/10.5066/F7J1015K. The “seafloor character” data layer shows classifications of the seafloor on the basis of depth, slope, rugosity (ruggedness), and backscatter intensity and which is further informed by the ground-truth-survey imagery. The “potential habitats” polygons are delineated on the basis of substrate type, geomorphology, seafloor process, or other attributes that may provide a habitat for a specific species or assemblage of organisms. Representative seismic-reflection profile data from the map area is also include and provides information on the subsurface stratigraphy and structure of the map area. The distribution and thickness of young sediment (deposited over the past about 21,000 years, during the most recent sea-level rise) is interpreted on the basis of the seismic-reflection data. The geologic polygons merge onshore geologic mapping (compiled from existing maps by the California Geological Survey) and new offshore geologic mapping that is based on integration of high-resolution bathymetry and backscatter imagery seafloor-sediment and rock samplesdigital camera and video imagery, and high-resolution seismic-reflection profiles. The information provided by the map sheets, pamphlet, and data catalog has a broad range of applications. High-resolution bathymetry, acoustic backscatter, ground-truth-surveying imagery, and habitat mapping all contribute to habitat characterization and ecosystem-based management by providing essential data for delineation of marine protected areas and ecosystem restoration. Many of the maps provide high-resolution baselines that will be critical for monitoring environmental change associated with climate change, coastal development, or other forcings. High-resolution bathymetry is a critical component for modeling coastal flooding caused by storms and tsunamis, as well as inundation associated with longer term sea-level rise. Seismic-reflection and bathymetric data help characterize earthquake and tsunami sources, critical for natural-hazard assessments of coastal zones. Information on sediment distribution and thickness is essential to the understanding of local and regional sediment transport, as well as the development of regional sediment-management plans. In addition, siting of any new offshore infrastructure (for example, pipelines, cables, or renewable-energy facilities) will depend on high-resolution mapping. Finally, this mapping will both stimulate and enable new scientific research and also raise public awareness of, and education about, coastal environments and issues. Web services were created using an ArcGIS service definition file. The ArcGIS REST service and OGC WMS service include all Offshore of Point Conception map area data layers. Data layers are symbolized as shown on the associated map sheets.
The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. An ArcInfo(tm) (ESRI) GIS database was designed for WICA using the National Park GIS Database Design, Layout, and Procedures created by the BOR. This was created through Arc Macro Language (AML) scripts that helped automate the transfer process and ensure that all spatial and attribute data was consistent and stored properly. Actual transfer of information from the interpreted aerial photographs to a digital, geo-referenced format involved two techniques, scanning (for the vegetation classes) and on-screen digitizing (for the land-use classes). Both techniques required the use of 14 digital black-and-white orthophoto quarter quadrangles (DOQQ's) covering the study area. Transferred information was used to create vegetation polygon coverages and ancillary linear coverages in ArcInfo(tm) for each WICA DOQQ. Attribute information including vegetation map unit, location, and aerial photo number was subsequently entered for all polygons.
The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. We used ERDAS Imagine ® Professional 9.2, ENVI ® 4.5, and ArcGIS ® 9.3 with Arc Workstation to develop the vegetation spatial database. Existing GIS datasets that we used to provide mapping information include a NPS park boundary shapefile for VICK (including a 100 meter buffer boundary around the Louisiana Circle, South Fort, and Navy Circle satellite units), a land cover shapefile created by the NWRC (Rangoonwala et al. 2007), and the National Elevation Dataset (NED) (used as the source of the 10-meter elevation model and derived streams, slope, and hillshade). To make the entire spatial data set consistent with NPSVI policies to map only to park boundaries, we clipped the vegetation in and around the previously buffered areas around the Louisiana Circle, South Fort, and Navy Circle satellite unit NPS boundaries. We also added to the spatial database vegetation polygons for the previously omitted Grant’s Canal satellite unit by heads-up digitizing this area from a National Agricultural Information Program (NAIP) image.
This data was created through the modification of an existing sewer service dataset from the CT Office of Policy and Management (OPM), in addition to sewer data from the Southeastern Connecticut Council Of Government (SCCOG) and the Town of Stonington. It also includes data from the Sewer Service Area 2018 file in areas where the OPM dataset was not as current. The OPM data was modified by reducing the extensive categories which represent all areas containing sewers to a "Connected" classification.SCCOG Data: Data was clipped to individual municipal boundaries for all 21 municipalities with sewer information within the SCCOG. The "Existing" category from attribute table was extracted via selection to create the "Connected" areas for 19/21 municipalities. The Town of Stonington data was merged with the SCCOG data as both had areas which were not included in the other. The North Stonington data was combined with SSA 2018 data to get the most accurate representation for that town. OPM Data: Data was modified to isolate the undefined and fragmented categories, (QA- using municipal websites, PDF maps and local contacts for verification where available) then Clipped to municipal boundaries. All the areas that are connected to sewers were Dissolved, only maintaining the key fields listed and described below. The datasets were combined using the Merge tool to get all the connected sewer service areas in the state.Description of Fields:TOWN- Represents all the municipalities with the state of CTs boundaries. CNTY_NAME- Represents the eight (8) county names to which each municipality belongs to. SEWERS- This field has two classes "Existing" and "No Sewer" and this identifies if a municipality has sewers existing within its boundary or not. SEWER-STATUS- The Sewer Status field represents the areas within in each municipality that are "Connected" to sewers.TREATMENTFACILITY- This field represents the sewer service treatment facility (endpoint) that processes the waste for each municipality. For municipalities without sewers, “Not Applicable” is the designated value. PASSTHROUGH- This field identifies if the wastewater passes through other municipalities on the way to the treatment facility (endpoint) as denoted by a "Yes" or "No" value. Feature class is symbolized on the Sewer Status field to show the “Connected” (green). DEEP welcomes the opportunity to receive any feedback that can help improve the quality of the information presented in this map by contacting Carlos Esguerra (carlos.esguerra@ct.gov).
The National Hydrography Dataset Plus High Resolution (NHDplus High Resolution) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US Geological Survey, NHDPlus High Resolution provides mean annual flow and velocity estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.For more information on the NHDPlus High Resolution dataset see the User’s Guide for the National Hydrography Dataset Plus (NHDPlus) High Resolution.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territoriesGeographic Extent: The Contiguous United States, Hawaii, portions of Alaska, Puerto Rico, Guam, US Virgin Islands, Northern Marianas Islands, and American SamoaProjection: Web Mercator Auxiliary Sphere Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: USGSUpdate Frequency: AnnualPublication Date: July 2022This layer was symbolized in the ArcGIS Map Viewer and while the features will draw in the Classic Map Viewer the advanced symbology will not. Prior to publication, the network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original dataset. No data values -9999 and -9998 were converted to Null values.What can you do with this layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS OnlineAdd this layer to a map in the map viewer. The layer or a map containing it can be used in an application. Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute.Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map.Use as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class.Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of the ArcGIS Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.
[Metadata] Flood Hazard Areas for the State of Hawaii as of May, 2021, downloaded from the FEMA Flood Map Service Center, May 1, 2021. The Statewide GIS Program created the statewide layer by merging all county layers (downloaded on May 1, 2021), as the Statewide layer was not available from the FEMA Map Service Center. For more information, please refer to summary metadata: https://files.hawaii.gov/dbedt/op/gis/data/s_fld_haz_ar_state.pdf. The National Flood Hazard Layer (NFHL) data incorporates all Flood Insurance Rate Map (FIRM) databases published by the Federal Emergency Management Agency (FEMA), and any Letters of Map Revision (LOMRs) that have been issued against those databases since their publication date. It is updated on a monthly basis. The FIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper FIRMs. The FIRM Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The FIRM Database is derived from Flood Insurance Studies (FISs), previously published FIRMs, flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by FEMA. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all FIRM Databases and corresponding LOMRs available on the publication date of the data set. The specification for the horizontal control of FIRM Databases is consistent with those required for mapping at a scale of 1:12,000. This file is georeferenced to the Earth's surface using the Geographic Coordinate System (GCS) and North American Datum of 1983.
This dataset contains model-based place (incorporated and census designated places) estimates in GIS-friendly format. PLACES covers the entire United States—50 states and the District of Columbia —at county, place, census tract, and ZIP Code Tabulation Area levels. It provides information uniformly on this large scale for local areas at four geographic levels. Estimates were provided by the Centers for Disease Control and Prevention (CDC), Division of Population Health, Epidemiology and Surveillance Branch. PLACES was funded by the Robert Wood Johnson Foundation in conjunction with the CDC Foundation. Data sources used to generate these model-based estimates are Behavioral Risk Factor Surveillance System (BRFSS) 2021 or 2020 data, Census Bureau 2010 population estimates, and American Community Survey (ACS) 2015–2019 estimates. The 2023 release uses 2021 BRFSS data for 29 measures and 2020 BRFSS data for 7 measures (all teeth lost, dental visits, mammograms, cervical cancer screening, colorectal cancer screening, core preventive services among older adults, and sleeping less than 7 hours) that the survey collects data on every other year. These data can be joined with the 2019 Census TIGER/Line place boundary file in a GIS system to produce maps for 36 measures at the place level. An ArcGIS Online feature service is also available for users to make maps online or to add data to desktop GIS software. https://cdcarcgis.maps.arcgis.com/home/item.html?id=2c3deb0c05a748b391ea8c9cf9903588
The data provided here denotes the authors’ revised service areas for a subset of 377 Public Housing Authorities (PHAs) for which HUD previously estimated service areas. Using HUD administrative data on the location of Housing Choice Voucher holders, HUD’s estimated service areas were revised to better capture voucher activity. Specifically, the authors developed two different tests and correction procedures. The first assesses if the estimated service area omits a sizable share of voucher holder locations (so is “too small”), and if so, adjusts to include census designated places or counties containing at least 5 percent of a PHA’s voucher holders. The second test checks whether the estimated service boundary includes areas the PHA does not appear to serve and that are clearly served by another PHA (so is “too large”), in this case adjusting by removing those areas. 148 of the 377 PHA estimated service areas were found to be too small, too large, or both, and so have revised service areas that differ from HUD’s estimated service areas. The detailed methodology is provided below. Additionally, a spreadsheet is supplied that identifies geographies that were added to and dropped from HUD’s estimated services to create the revised service areas for affected PHAs.
This is an experimental dataset that is designed to aid researchers in studying the HCV program. The methodology and the service areas themselves have not been validated by HUD’s Office of Public and Indian Housing (PIH) or the Public Housing Agencies. For additional discussion of the approach, see Tauber et al. (2024); please contact the authors with any questions or comments.Data Dictionary: DD_Extensions to Estimated Housing Authority Service Areas MethodologyMethodology: Extensions to Estimated Housing Authority Service Areas Methodology
Reference:Tauber, Kristen, Ingrid Gould Ellen, and Katherine O’Regan. 2024. “Whom Do We Serve? Refining Public Housing Agency Service Areas.” Cityscape 26(1) (2024): 395-400.
The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. GIS Database 2002-2005: Project Size = 1,898 acres Fort Larned National Historic Site (including the Rut Site) = 705 acres 16 Map Classes 11 Vegetated 5 Non-vegetated Minimum Mapping Unit = ½ hectare is the program standard but this was modified at FOLS to ¼ acre. Total Size = 229 Polygons Average Polygon Size = 8.3 acres Overall Thematic Accuracy = 92% To produce the digital map, a combination of 1:8,500-scale (0.75 meter pixels) color infrared digital ortho-imagery acquired on October 26, 2005 by the Kansas Applied Remote Sensing Program and 1:12,000-scale true color ortho-rectified imagery acquired in 2005 by the U.S. Department of Agriculture - Farm Service Agency’s Aerial Photography Field Office, and all of the GPS referenced ground data were used to interpret the complex patterns of vegetation and land-use. In the end, 16 map units (11 vegetated and 5 land-use) were developed and directly cross-walked or matched to corresponding plant associations and land-use classes. All of the interpreted and remotely sensed data were converted to Geographic Information System (GIS) databases using ArcGIS© software. Draft maps were printed, field tested, reviewed and revised. One hundred and six accuracy assessment (AA) data points were collected in 2006 by KNSHI and used to determine the map’s accuracy. After final revisions, the accuracy assessment revealed an overall thematic accuracy of 92%.
Terms of UseData Limitations and DisclaimerThe user’s use of and/or reliance on the information contained in the Document 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.This is an ongoing data development project. Attempts have been made to contact all PWS systems, but not all have responded with information on their service area. MassDEP will continue to collect and verify this information. Some PWS service areas included in this datalayer have not been verified by the PWS or the municipality involved, but since many of those areas are based on information published online by the municipality, the PWS, or in a publicly available report, they are included in the estimated PWS service area datalayer.Please note: All PWS 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 PWS service area are necessarily served by the system, and some properties outside the mapped service areas could be served by the PWS – please contact the relevant PWS. Not all service areas have been confirmed by the systems.Please use the following citation to reference these data:MassDEP, Water Utility Resilience Program. 2025. Community and Non-Transient Non-Community Public Water System Service Area (PubV2025_3).IMPORTANT NOTICE: This MassDEP Estimated Water Service datalayer may not be complete, may contain errors, omissions, and other inaccuracies and the data are subject to change. This version is published through MassGIS. We want to learn about the data uses. If you use this dataset, please notify staff in the Water Utility Resilience Program (WURP@mass.gov).
This GIS datalayer represents approximate service areas for Public Water Systems (PWS) in Massachusetts. In 2017, as part of its “Enhancing Resilience and Emergency Preparedness of Water Utilities through Improved Mapping” (Critical Infrastructure Mapping Project ), the MassDEP Water Utility Resilience Program (WURP) began to uniformly map drinking water service areas throughout Massachusetts using information collected from various sources. Along with confirming existing public water system (PWS) service area information, the project collected and verified estimated service area delineations for PWSs not previously delineated and will continue to update the information contained in the datalayers. As of the date of publication, WURP has delineated Community (COM) and Non-Transient Non-Community (NTNC) service areas. Transient non-community (TNCs) are not part of this mapping project.
Layers and Tables:
The MassDEP Estimated Public Water System Service Area data comprises two polygon feature classes and a supporting table. Some data fields are populated from the MassDEP Drinking Water Program’s Water Quality Testing System (WQTS) and Annual Statistical Reports (ASR).
The Community Water Service Areas feature class (PWS_WATER_SERVICE_AREA_COMM_POLY) includes polygon features that represent the approximate service areas for PWS classified as Community systems.The NTNC Water Service Areas feature class (PWS_WATER_SERVICE_AREA_NTNC_POLY) includes polygon features that represent the approximate service areas for PWS classified as Non-Transient Non-Community systems.The Unlocated Sites List table (PWS_WATER_SERVICE_AREA_USL) contains a list of known, unmapped active Community and NTNC PWS services areas at the time of publication.
Production
Data Universe
Public Water Systems in Massachusetts are permitted and regulated through the MassDEP Drinking Water Program. The WURP has mapped service areas for all active and inactive municipal and non-municipal Community PWSs in MassDEP’s Water Quality Testing Database (WQTS). Community PWS refers to a public water system that serves at least 15 service connections used by year-round residents or regularly serves at least 25 year-round residents.
All active and inactive NTNC PWS were also mapped using information contained in WQTS. An NTNC or Non-transient Non-community Water System refers to a public water system that is not a community water system and that has at least 15 service connections or regularly serves at least 25 of the same persons or more approximately four or more hours per day, four or more days per week, more than six months or 180 days per year, such as a workplace providing water to its employees.
These data may include declassified PWSs. Staff will work to rectify the status/water services to properties previously served by declassified PWSs and remove or incorporate these service areas as needed.
Maps of service areas for these systems were collected from various online and MassDEP sources to create service areas digitally in GIS. Every PWS is assigned a unique PWSID by MassDEP that incorporates the municipal ID of the municipality it serves (or the largest municipality it serves if it serves multiple municipalities). Some municipalities contain more than one PWS, but each PWS has a unique PWSID. The Estimated PWS Service Area datalayer, therefore, contains polygons with a unique PWSID for each PWS service area.
A service area for a community PWS may serve all of one municipality (e.g. Watertown Water Department), multiple municipalities (e.g. Abington-Rockland Joint Water Works), all or portions of two or more municipalities (e.g. Provincetown Water Dept which serves all of Provincetown and a portion of Truro), or a portion of a municipality (e.g. Hyannis Water System, which is one of four PWSs in the town of Barnstable).
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 estimates based on the general location of the source wells or the general estimated location of the service area - these do not represent the actual service area.
Service areas were mapped initially from 2017 to 2022 and reflect varying years for which service is implemented for that service area boundary. WURP maintains the dataset quarterly with annual data updates; however, the dataset may not include all current active PWSs. A list of unmapped PWS systems is included in the USL table PWS_WATER_SERVICE_AREA_USL available for download with the dataset. Some PWSs that are not mapped may have come online after this iteration of the mapping project; these will be reconciled and mapped during the next phase of the WURP project. PWS IDs that represent regional or joint boards with (e.g. Tri Town Water Board, Randolph/Holbrook Water Board, Upper Cape Regional Water Cooperative) will not be mapped because their individual municipal service areas are included in this datalayer.
Some PWSs that are not mapped may have come online after this iteration of the mapping project; these will be reconciled and mapped during the next phase of the WURP project. Those highlighted (e.g. Tri Town Water Board, Randolph/Holbrook Water Board, Upper Cape Regional Water Cooperative) represent regional or joint boards that will not be mapped, because their individual municipal service areas are included in this datalayer.
PWSs that do not have corresponding sources, may be part of consecutive systems, may have been incorporated into another PWSs, reclassified as a different type of PWS, or otherwise taken offline. PWSs that have been incorporated, reclassified, or taken offline will be reconciled during the next data update.
Methodologies and Data Sources
Several methodologies were used to create service area boundaries using various sources, including data received from the systems 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 PWS websites. When provided with water line data rather than generalized areas, 300-foot buffers were created around the water 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.
Verification Process
Small-scale PDF file maps with roads and other infrastructure were sent to every PWS for corrections or verifications. For small systems, 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 PWS 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 the PWS.
Sources of information for estimated drinking water service areas
The following information was used to develop estimated drinking water service areas:
EOEEA Water Assets Project (2005) water lines (these were buffered to create service areas)Horsely Witten Report 2008Municipal Master Plans, Open Space Plans, Facilities Plans, Water Supply System Webpages, reports and online interactive mapsGIS data received from PWSDetailed infrastructure mapping completed through the MassDEP WURP Critical Infrastructure InitiativeIn the absence of other service area information, for municipalities served by a town-wide water system serving at least 97% of the population, the municipality’s boundary was used. Determinations of which municipalities are 97% or more served by the PWS were made based on the Percent Water Service Map created in 2018 by MassDEP based on various sources of information including but not limited to:The Winter population served submitted by the PWS in the ASR submittalThe number of services from WQTS as a percent of
This web map references the live tiled map service from the OpenStreetMap project. OpenStreetMap (OSM) is an open collaborative project to create a free editable map of the world. Volunteers gather location data using GPS, local knowledge, and other free sources of information such as free satellite imagery, and upload it. The resulting free map can be viewed and downloaded from the OpenStreetMap server: http://www.OpenStreetMap.org. See that website for additional information about OpenStreetMap. It is made available as a basemap for GIS work in Esri products under a Creative Commons Attribution-ShareAlike license.Tip: This service is one of the basemaps used in the ArcGIS.com map viewer and ArcGIS Explorer Online. Simply click one of those links to launch the interactive application of your choice, and then choose Open Street Map from the Basemap control to start using this service. You'll also find this service in the Basemap gallery in ArcGIS Explorer Desktop and ArcGIS Desktop 10.
This is an update to the MSSA geometries and demographics to reflect the new 2020 Census tract data. The Medical Service Study Area (MSSA) polygon layer represents the best fit mapping of all new 2020 California census tract boundaries to the original 2010 census tract boundaries used in the construction of the original 2010 MSSA file. Each of the state's new 9,129 census tracts was assigned to one of the previously established medical service study areas (excluding tracts with no land area), as identified in this data layer. The MSSA Census tract data is aggregated by HCAI, to create this MSSA data layer. This represents the final re-mapping of 2020 Census tracts to the original 2010 MSSA geometries. The 2010 MSSA were based on U.S. Census 2010 data and public meetings held throughout California.
This web map features a vector basemap of OpenStreetMap (OSM) data created and hosted by Esri. Esri produced this vector tile basemap in ArcGIS Pro from a live replica of OSM data, hosted by Esri, and rendered using a creative cartographic style emulating a blueprint technical drawing. The vector tiles are updated every few weeks with the latest OSM data. This vector basemap is freely available for any user or developer to build into their web map or web mapping apps.OpenStreetMap (OSM) is an open collaborative project to create a free editable map of the world. Volunteers gather location data using GPS, local knowledge, and other free sources of information and upload it. The resulting free map can be viewed and downloaded from the OpenStreetMap site: www.OpenStreetMap.org. Esri is a supporter of the OSM project and is excited to make this new vector basemap available available to the OSM, GIS, and Developer communities.
Jackson County is comprised of 3 ambulance service providers each responsible for dispatching to a specified area known as an Ambulance Service Area (ASA). In the past, the ASA boundaries were somewhat arbitrary and regularly split taxlots. The lack of distinction between one ASA and another created a situation where two service providers would respond to the same residence from opposite directions. In the spring of 2008, the task of re-digitizing these boundaries was given to Karim Naguib at Jackson County GIS Services. There were three things that needed to be kept in mind while reproducing the ASA boundaries. 1) Maximize response times 2) Minimize overlapping responses 3) Make sure the boundaries were divided fairly To maximize response times it was important to consider access issues. In the previous ASA boundary, there were a handful of site addresses where a service provider would have to drive into another ASA and then double back to their own ASA in order to access a residence in distress. This issue lowered response times for the service providers and caused some confusion as to who the proper responder should be. The fastest way to isolate these issues was to display driveways from Jackson County GIS Services driveways layer. To minimize overlapping responses, it was important to make sure that there were very distinct boundaries between each of the ASA's. To complete this task, the previously existing ASA boundary was taken and the lines were followed throughout the entire county, and snapped to taxlot lines and vertexes rather than simply drawing them freehand style. It was during this process that the driveways layer was incorporated, making sure that where there was a confliction between taxlots, the service provider with the best access would get the response. The end result was a neat ASA boundary that matched taxlot boundaries. In order to make sure the boundaries were divided up evenly between the three providers, it was apparent that Jackson County GIS Services could not make the final decision. The first step to ensure this goal was met was to contact Gary Stevens at Jackson County Health and Human Services (our primary contact on this project). After email communications back and forth between Gary and Karim, in an attempt to talk each other through their ideas of how the ASA's should be drawn, they decided to meet face to face with representatives from each of the three service providers to make sure that everybody agreed on where the boundaries should be drawn. With representatives from Mercy Flights, Ashland Fire and Rescue, and the Rogue River Fire Department, as well as Gary Stevens present, the new ASA boundaries were edited in real-time. As the discussions were taking place, the lines were being re-digitized to match what the providers had agreed upon. Once all of the discussion had ended, the boundary was reviewed one more time to make sure that the changes were exactly what each provider had expected, and that each of them was happy with the outcome. After returning to the office, topology rules were created which were designed to point out mismatches in the lines of the ASA's. Where ever one ASA boundary crossed or did not perfectly overlap another, an error message would appear on the map showing exactly where the issue was. Once all of the errors were located and corrected, the topology rules were re-run to double check for accuracy.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
For complete collection of data and models, see https://doi.org/10.21942/uva.c.5290546.Original model developed in 2016-17 in ArcGIS by Henk Pieter Sterk (www.rfase.org), with minor updates in 2021 by Stacy Shinneman and Henk Pieter Sterk. Model used to generate publication results:Hierarchical geomorphological mapping in mountainous areas Matheus G.G. De Jong, Henk Pieter Sterk, Stacy Shinneman & Arie C. Seijmonsbergen. Submitted to Journal of Maps 2020, revisions made in 2021.This model creates tiers (columns) of geomorphological features (Tier 1, Tier 2 and Tier 3) in the landscape of Vorarlberg, Austria, each with an increasing level of detail. The input dataset needed to create this 'three-tier-legend' is a geomorphological map of Vorarlberg with a Tier 3 category (e.g. 1111, for glacially eroded bedrock). The model then automatically adds Tier 1, Tier 2 and Tier 3 categories based on the Tier 3 code in the 'Geomorph' field. The model replaces the input file with an updated shapefile of the geomorphology of Vorarlberg, now including three tiers of geomorphological features. Python script files and .lyr symbology files are also provided here.
This dataset contains model-based census tract level estimates for the PLACES 2022 release in GIS-friendly format. PLACES covers the entire United States—50 states and the District of Columbia (DC)—at county, place, census tract, and ZIP Code Tabulation Area levels. It provides information uniformly on this large scale for local areas at 4 geographic levels. Estimates were provided by the Centers for Disease Control and Prevention (CDC), Division of Population Health, Epidemiology and Surveillance Branch. PLACES was funded by the Robert Wood Johnson Foundation in conjunction with the CDC Foundation. Data sources used to generate these model-based estimates include Behavioral Risk Factor Surveillance System (BRFSS) 2020 or 2019 data, Census Bureau 2010 population estimates, and American Community Survey (ACS) 2015–2019 estimates. The 2022 release uses 2020 BRFSS data for 25 measures and 2019 BRFSS data for 4 measures (high blood pressure, taking high blood pressure medication, high cholesterol, and cholesterol screening) that the survey collects data on every other year. These data can be joined with the census tract 2015 boundary file in a GIS system to produce maps for 29 measures at the census tract level. An ArcGIS Online feature service is also available for users to make maps online or to add data to desktop GIS software. https://cdcarcgis.maps.arcgis.com/home/item.html?id=3b7221d4e47740cab9235b839fa55cd7
Deprecation notice: This tool is deprecated because this functionality is now available with out-of-the-box tools in ArcGIS Pro. The tool author will no longer be making further enhancements or fixing major bugs.Use Add GTFS to a Network Dataset to incorporate transit data into a network dataset so you can perform schedule-aware analyses using the Network Analyst tools in ArcMap.After creating your network dataset, you can use the ArcGIS Network Analyst tools, like Service Area and OD Cost Matrix, to perform transit/pedestrian accessibility analyses, make decisions about where to locate new facilities, find populations underserved by transit or particular types of facilities, or visualize the areas reachable from your business at different times of day. You can also publish services in ArcGIS Server that use your network dataset.The Add GTFS to a Network Dataset tool suite consists of a toolbox to pre-process the GTFS data to prepare it for use in the network dataset and a custom GTFS transit evaluator you must install that helps the network dataset read the GTFS schedules. A user's guide is included to help you set up your network dataset and run analyses.Instructions:Download the tool. It will be a zip file.Unzip the file and put it in a permanent location on your machine where you won't lose it. Do not save the unzipped tool folder on a network drive, the Desktop, or any other special reserved Windows folders (like C:\Program Files) because this could cause problems later.The unzipped file contains an installer, AddGTFStoaNetworkDataset_Installer.exe. Double-click this to run it. The installation should proceed quickly, and it should say "Completed" when finished.Read the User's Guide for instructions on creating and using your network dataset.System requirements:ArcMap 10.1 or higher with a Desktop Standard (ArcEditor) license. (You can still use it if you have a Desktop Basic license, but you will have to find an alternate method for one of the pre-processing tools.) ArcMap 10.6 or higher is recommended because you will be able to construct your network dataset much more easily using a template rather than having to do it manually step by step. This tool does not work in ArcGIS Pro. See the User's Guide for more information.Network Analyst extensionThe necessary permissions to install something on your computer.Data requirements:Street data for the area covered by your transit system, preferably data including pedestrian attributes. If you need help preparing high-quality street data for your network, please review this tutorial.A valid GTFS dataset. If your GTFS dataset has blank values for arrival_time and departure_time in stop_times.txt, you will not be able to run this tool. You can download and use the Interpolate Blank Stop Times tool to estimate blank arrival_time and departure_time values for your dataset if you still want to use it.Help forum