Esri's ArcGIS Online tools provide three methods of filtering larger datasets using attribute or geospatial information that are a part of each individual dataset. These instructions provide a basic overview of the step a GeoHub end user can take to filter out unnecessary data or to specifically hone in a particular location to find data related to this location and download the specific information filtered through the search bar, as seen on the map or using the attribute filters in the Data tab.

Filtered (5% slope and less) direct normal solar resource data for the Southwest United States

This data provides filtered solar resource averaged over surface cells of 0.1 degrees in both latitude and longitude, or about 10 km in size. Exclusions: Contiguous Area 1km squared; US Census Urban Areas; MRLC Multi Resolution Land Characteristics Consortium http://www.mrlc.gov/; Argone National Lab ACEC Lands (Areas of Critical Environmental Concern) Federally Protected lands (FS - IRA (Inventoried Roadless Areas, FS - National Monument, FS - National Scenic Area, FS - Wilderness, FS - Wilderness Study Area, BLM - Wilderness, BLM - National Recreation Area, BLM - Forest Reserve, BLM - Wilderness Study Area, BLM - National Monument, BLM - National Conservation Area, FWS - National Wildlife Refuge, FWS - Waterfowl Production Area, FWS - Wildlife Management Area, FWS - Wilderness, FWS - Wilderness Study Area, FWS - Fish Hatchery, NPS - National Battlefield, NPS - National Battlefield Park, NPS - National Capital Park, NPS - National Historic Park, NPS - National Historic Site, NPS - National Lakeshore, NPS - National Mall, NPS - National Memorial, NPS - National Military Park, NPS - National Monument, NPS - National Park, NPS - National Parkway, NPS - National Preserve, NPS - National Recreation Area, NPS - National Reserve, NPS - National River, NPS - National Seashore, NPS - Wilderness, NPS - Wilderness Study Area, NPS - National Wild and Scenic River).

License Info

DISCLAIMER NOTICE This GIS data was developed by the National Renewable Energy Laboratory ("NREL"), which is operated by the Alliance for Sustainable Energy, LLC for the U.S. Department of Energy ("DOE"). The user is granted the right, without any fee or cost, to use, copy, modify, alter, enhance and distribute this data for any purpose whatsoever, provided that this entire notice appears in all copies of the data. Further, the user of this data agrees to credit NREL in any publications or software that incorporate or use the data.

Access to and use of the GIS data shall further impose the following obligations on the User. The names DOE/NREL may not be used in any advertising or publicity to endorse or promote any product or commercial entity using or incorporating the GIS data unless specific written authorization is obtained from DOE/NREL. The User also understands that DOE/NREL shall not be obligated to provide updates, support, consulting, training or assistance of any kind whatsoever with regard to the use of the GIS data.

THE GIS DATA IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL DOE/NREL BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER, INCLUDING BUT NOT LIMITED TO CLAIMS ASSOCIATED WITH THE LOSS OF DATA OR PROFITS, WHICH MAY RESULT FROM AN ACTION IN CONTRACT, NEGLIGENCE OR OTHER TORTIOUS CLAIM THAT ARISES OUT OF OR IN CONNECTION WITH THE ACCESS OR USE OF THE GIS DATA.

The User acknowledges that access to the GIS data is subject to U.S. Export laws and regulations and any use or transfer of the GIS data must be authorized under those regulations. The User shall not use, distribute, transfer, or transmit GIS data or any products incorporating the GIS data except in compliance with U.S. export regulations. If requested by DOE/NREL, the User agrees to sign written assurances and other export-related documentation as may be required to comply with U.S. export regulations.

This dataset was updated May, 2025.This ownership dataset was generated primarily from CPAD data, which already tracks the majority of ownership information in California. CPAD is utilized without any snapping or clipping to FRA/SRA/LRA. CPAD has some important data gaps, so additional data sources are used to supplement the CPAD data. Currently this includes the most currently available data from BIA, DOD, and FWS. Additional sources may be added in subsequent versions. Decision rules were developed to identify priority layers in areas of overlap.Starting in 2022, the ownership dataset was compiled using a new methodology. Previous versions attempted to match federal ownership boundaries to the FRA footprint, and used a manual process for checking and tracking Federal ownership changes within the FRA, with CPAD ownership information only being used for SRA and LRA lands. The manual portion of that process was proving difficult to maintain, and the new method (described below) was developed in order to decrease the manual workload, and increase accountability by using an automated process by which any final ownership designation could be traced back to a specific dataset.The current process for compiling the data sources includes: Clipping input datasets to the California boundary Filtering the FWS data on the Primary Interest field to exclude lands that are managed by but not owned by FWS (ex: Leases, Easements, etc) Supplementing the BIA Pacific Region Surface Trust lands data with the Western Region portion of the LAR dataset which extends into California. Filtering the BIA data on the Trust Status field to exclude areas that represent mineral rights only. Filtering the CPAD data on the Ownership Level field to exclude areas that are Privately owned (ex: HOAs) In the case of overlap, sources were prioritized as follows: FWS > BIA > CPAD > DOD As an exception to the above, DOD lands on FRA which overlapped with CPAD lands that were incorrectly coded as non-Federal were treated as an override, such that the DOD designation could win out over CPAD.In addition to this ownership dataset, a supplemental _source dataset is available which designates the source that was used to determine the ownership in this dataset. Data Sources: GreenInfo Network's California Protected Areas Database (CPAD2023a). https://www.calands.org/cpad/; https://www.calands.org/wp-content/uploads/2023/06/CPAD-2023a-Database-Manual.pdf US Fish and Wildlife Service FWSInterest dataset (updated December, 2023). https://gis-fws.opendata.arcgis.com/datasets/9c49bd03b8dc4b9188a8c84062792cff_0/explore Department of Defense Military Bases dataset (updated September 2023) https://catalog.data.gov/dataset/military-bases Bureau of Indian Affairs, Pacific Region, Surface Trust and Pacific Region Office (PRO) land boundaries data (2023) via John Mosley John.Mosley@bia.gov Bureau of Indian Affairs, Land Area Representations (LAR) and BIA Regions datasets (updated Oct 2019) https://biamaps.doi.gov/bogs/datadownload.html Data Gaps & Changes:Known gaps include several BOR, ACE and Navy lands which were not included in CPAD nor the DOD MIRTA dataset. Our hope for future versions is to refine the process by pulling in additional data sources to fill in some of those data gaps. Additionally, any feedback received about missing or inaccurate data can be taken back to the appropriate source data where appropriate, so fixes can occur in the source data, instead of just in this dataset.25_1: The CPAD Input dataset was amended to merge large gaps in certain areas of the state known to be erroneous, such as Yosemite National Park, and to eliminate overlaps from the original input. The FWS input dataset was updated in February of 2025, and the DOD input dataset was updated in October of 2024. The BIA input dataset was the same as was used for the previous ownership version.24_1: Input datasets this year included numerous changes since the previous version, particularly the CPAD and DOD inputs. Of particular note was the re-addition of Camp Pendleton to the DOD input dataset, which is reflected in this version of the ownership dataset. We were unable to obtain an updated input for tribral data, so the previous inputs was used for this version.23_1: A few discrepancies were discovered between data changes that occurred in CPAD when compared with parcel data. These issues will be taken to CPAD for clarification for future updates, but for ownership23_1 it reflects the data as it was coded in CPAD at the time. In addition, there was a change in the DOD input data between last year and this year, with the removal of Camp Pendleton. An inquiry was sent for clarification on this change, but for ownership23_1 it reflects the data per the DOD input dataset.22_1 : represents an initial version of ownership with a new methodology which was developed under a short timeframe. A comparison with previous versions of ownership highlighted the some data gaps with the current version. Some of these known gaps include several BOR, ACE and Navy lands which were not included in CPAD nor the DOD MIRTA dataset. Our hope for future versions is to refine the process by pulling in additional data sources to fill in some of those data gaps. In addition, any topological errors (like overlaps or gaps) that exist in the input datasets may thus carry over to the ownership dataset. Ideally, any feedback received about missing or inaccurate data can be taken back to the relevant source data where appropriate, so fixes can occur in the source data, instead of just in this dataset.

GapMaps Live is an easy-to-use location intelligence platform available across 25 countries globally that allows you to visualise your own store data, combined with the latest demographic, economic and population movement intel right down to the micro level so you can make faster, smarter and surer decisions when planning your network growth strategy.

With one single login, you can access the latest estimates on resident and worker populations, census metrics (eg. age, income, ethnicity), consuming class, retail spend insights and point-of-interest data across a range of categories including fast food, cafe, fitness, supermarket/grocery and more.

Some of the world's biggest brands including McDonalds, Subway, Burger King, Anytime Fitness and Dominos use GapMaps Live as a vital strategic tool where business success relies on up-to-date, easy to understand, location intel that can power business case validation and drive rapid decision making.

Primary Use Cases for GapMaps Live includes:

1. Retail Site Selection - Identify optimal locations for future expansion and benchmark performance across existing locations.
2. Customer Profiling: get a detailed understanding of the demographic profile of your customers and where to find more of them.
3. Analyse your catchment areas at a granular grid levels using all the key metrics
4. Target Marketing: Develop effective marketing strategies to acquire more customers.
5. Marketing / Advertising (Billboards/OOH, Marketing Agencies, Indoor Screens)
6. Customer Profiling
7. Target Marketing
8. Market Share Analysis

Some of features our clients love about GapMaps Live include: - View business locations, competitor locations, demographic, economic and social data around your business or selected location - Understand consumer visitation patterns (“where from” and “where to”), frequency of visits, dwell time of visits, profiles of consumers and much more. - Save searched locations and drop pins - Turn on/off all location listings by category - View and filter data by metadata tags, for example hours of operation, contact details, services provided - Combine public data in GapMaps with views of private data Layers - View data in layers to understand impact of different data Sources - Share maps with teams - Generate demographic reports and comparative analyses on different locations based on drive time, walk time or radius. - Access multiple countries and brands with a single logon - Access multiple brands under a parent login - Capture field data such as photos, notes and documents using GapMaps Connect and integrate with GapMaps Live to get detailed insights on existing and proposed store locations.

A supplementary dataset related to the paper discussing preparation of a digital elevation model derived from DMR 5G (LiDAR-based DEM of the Czech Republic) cleaned of modern artificial features. It includes data used as a clipping mask and data produced during the testing phase.

Contents:

• ..\clipping_buffers.gdb\ - Clipping buffers based on ZABAGED dataset used for masking the original data stored as ESRI geodatabase.
• ..\drainages\ - Drainages with Strahler order higher than four (potential watercourses) for the original and filtered DEMs.
  • drainages_filtered - Drainges identified in the filtered DEM stored as GeoTIFF.
  • drainages_original - Drainges identified in the original DEM stored as GeoTIFF.
• ..\LSC\ - Locations with significant land surface curvature for the original and filtered DEMs.
  • LSC_filtered - Significant LSC identified in the filtered DEM stored as GeoTIFF.
  • LSC_original - Significant LSC identified in the original DEM stored as GeoTIFF.
• ..\visibility\ - Viewsheds computed over the original and filtered DEMs.
  • Libice\ - Sample viewsheds computed for the early medieval hillfort of Libice.
    • Libice_visibility_filtered - Viewshed based on the filtered DEM stored as GeoTIFF.
    • Libice_visibility_original - Viewshed based on the original DEM stored as GeoTIFF.
    • observer_points - Observer points used for calculating the viewsheds.
  • regular_grid\ - Cumulative viewsheds calculated for regularly spaced points in a 10 x 10 km grid with a visibility radius of 5 km and an observer height of 2 m; a total of 574 viewsheds.
    • visibility_filtered - Cumulative viewshed for the filtered DEM stored as GeoTIFF.
    • visibility_original - Cumulative viewshed for the original DEM stored as GeoTIFF.
    • visibility_test_buffers - Buffers used for the viewshed calculations stored as ESRI shapefile.
    • visibility_test_observers - Observer points used for the viewshed calculations stored as ESRI shapefile.

Preprint version of the related paper:

Novák, David and Pružinec, Filip, Potential and Implications of Automated Pre-Processing of Lidar-Based Digital Elevation Models for Large-Scale Archaeological Landscape Analysis. Available at SSRN: https://ssrn.com/abstract=4063514

The "Restoration Projects" feature layer is a component of the "Pollinator Restoration 2022" map which is itself a component of the "USFWS Pollinator Restoration Projects Mapper" which is a dashboard showing management projects that benefit pollinators across the Western U.S. See below for a description of the "USFWS Pollinator Restoration Projects Mapper."The "USFWS Pollinator Restoration Projects Mapper" is under development by the Region 1 (Pacific Northwest) USFWS Science Applications program. Completion is anticipated by Winter 2023. Contact: Alan Yanahan (alan_yanahan@fws.gov).The purpose of the "USFWS Pollinator Restoration Projects Mapper" is to inform future pollinator conservation efforts by providing a way to identify geographic areas where additional pollinator conservation may be needed.The "USFWS Pollinator Restoration Projects Mapper" maps the locations of where on-the-ground projects that are beneficial to pollinators have taken place. Its primary focus is projects on public lands. The majority of records included in this tool come from internal databases for the USFWS, US Forest Service, and the Bureau of Land Management, which were queried for relevant projects. The tool is not intended as a database for reporting projects to. Rather, the tool synthesizes records from existing databases.The geographic scope of the tool includes the western states of Arizona, California, Idaho, Nevada, Oregon, Utah, and Washington.When possible, the tool includes projects from 2014 to the present. This timespan was chosen because it matches the timespan of the USFWS Monarch Conservation Database For consistency, the tool groups pollinator beneficial projects into the following four activity types:Restoration: Actions taken after a disturbance, such as planting native forbs after a wildfireMaintenance: Actions taken outside the growing season that maintain habitat quality through regular disturbance using manual or chemical means. Examples: mowing, spraying weeds, prescribed fireConservation: Acquiring land or creating easements that are managed for biodiversityEnhancement: Actions that increase forb diversity and nectar resources, such as planting native milkweedThe tool includes a map that aggregates project point locations within 49 square mile sized hexagon grid cells. Users can click on individual grid cells to activate a pop-up menu to cycle through the projects that occurred within that grid cell. Information for each project include, but are not limited to, acreage, type of activity (i.e., restoration, maintenance, conservation, enhancement), data source, and lead organization.The tool also includes a dashboard to view bar graphs and pie charts that display project acreages and project number based on location (i.e., state), project activity type (i.e., restoration, maintenance, conservation, enhancement), data source, and management type. Data can be filtered by data source, activity type, and year. Data filtering will update the map, bar graphs, and pie charts.

Fire Department Connections (FDC's) points within Fuquay-Varina. These are primarily privately owned and maintained. Mapping of FDC's primarily began from 2015 and later from as-built information provided by new developments, so this should be considered a very limited dataset. Please note that ALL public utility data layers can be downloaded in a single .mpkx (ArcGIS Pro map package file), updated every Friday evening. This .mpkx file can be opened directly with ArcGIS Pro version 3+. Alternatively, you can extract the file geodatabase within it by renaming the file ending .mpkx to .zip and treating it like a zip archive file, for use in any version of ArcGIS Pro or ArcMap software. You can also use QGIS, a powerful, free, and open-source GIS software.The Town of Fuquay-Varina creates, maintains, and serves out a variety of utility information to the public, including its Potable Water System, Sanitary Sewer System, and Stormwater Collection System features. This is the same utility data displayed in our public web map. This utility data includes some features designated as 'private' that are not owned or maintained by the Town, but may be helpful for modeling and other informational purposes. Please pay particular attention to the terms of use and disclaimer associated with these data. Some data includes the use of Subtypes and Domains that may not translate well to Shapefile or GeoJSON downloads available through our Open Data site. Please beware the dangers of cartographic misrepresentation if you are unfamiliar with filtering and symbolizing data based on attributes. Water System Layers:Water LinesWater ValvesWater ManholesFire HydrantsFire Department ConnectionsWater MetersRPZ (Backflow Preventers)Water TankWater Booster StationsHarnett County Water District AreaSewer System Layers:Gravity Sewer LinesForced Sewer LinesSewer ManholesSewer ValvesSewer CleanoutsSewer Pump StationsWastewater Treatment PlantsStormwater System Layers:Stormwater Lines (Pipes)Stormwater Points (Inlets/Outlets/Manholes)Stormwater Control Measure Points (SCM's, such as Wet Ponds / Retention Basins)

Interactive GIS Mapping Tool – Urgent Drinking Water Needs (UDWN) Web Map in California

Use Constraints:

This mapping tool is for reference and guidance purposes only and is not a binding legal document to be used for legal determinations. The data provided may contain errors, inconsistencies, or may not in all cases appropriately represent the current status of Urgent Drinking Water Needs project locations. The data in this map are subject to change at any time and should not be used as the sole source for decision making. By using this data, the user acknowledges all limitations of the data and agrees to accept all errors stemming from its use. The Urgent Drinking Water Needs map does not provide the locations of individual households that were provided funding through grant agreements with non-profit organizations.

Description:

This map displays Urgent Drinking Water Needs due to drought, contamination, or other eligible emergencies. This includes projects approved for funding from July 1, 2014 to November 18, 2022, including both active and completed projects. The data comes from the State Water Resources Control Board (SWRCB) Cleanup and Abatement Account’s (CAA) project database and was exported on November 18, 2022. The map contains four layers: UDWN_Projects, UDWN_Summary_by_county, CA_Assembly_Districts_WEB, and CA_Senate_Districts_WEB.

The attributes for each project in the UDWN_Projects layer include the recipient of grant funding (grantee), community served, type of project, grant amount, funding program, date the project was approved, date the project was completed, Disadvantaged Community status, Small Disadvantaged Community status, the public water system number, status of the project (Active or Completed), and the state fiscal year in which the project was approved.

How to Use the Interactive Mapping Tool:When the map loads, it displays the state of California, UDWN Project locations, and California county boundaries. The “About” tab is located on the left-hand side of the map and displays instructions for using the map. The next tab display pre-set filters, the legend, and a layer list. Clicking on the “Legend” tab in the menu will show the legend of the map. Projects that appear as blue dots are still active, while projects that appear as red dots have already been completed.Note: Layers that show CA Assembly and Senate Districts were created by the Sierra Nevada Conservancy (SNC). These layers must be toggled on in the layers list to be seen. To view information about a specific project, click on a project location. A pop-up box will appear with the following information: (a) county name, (b) community served, (c) type of project, (d) approved funding amount, (e) approval date, and (f) status. To view information about the total funding and number of projects in a county, click within a county boundary and a pop up will appear.Use the pre-set filters to filter projects by status, fiscal year, funding program, county, assembly district, and/or senate district using the drop-down menu. The filters can be toggled on or off using the switches on the right side of the menu. To create a custom filter, click the filter icon at the bottom of the preset filter menu and enter the desired parameters. For one parameter, click “add expression” to create a custom filter. For more than one, click “add set” to create a custom filter.To export and download filtered data, open the Attribute Table located at the bottom of the map, click the “Options” drop down menu, select “Export all to CSV” from the drop-down menu, and download the desired information.

Map Layers:UDWN_Projects – This layer shows all active or completed UDWN projects from July 1, 2014 to November 18, 2022. Active projects are represented with blue dots while completed projects are represented with red dots. The attributes in this layer include what county the project is in, the community served, the type of project, approved funding amount, approval date, and status.UDWN_Summary_by_county – This layer shows the boundary lines for all the counties in California. The attributes in this layer include the total number of projects and total funding approved in that county since July 1, 2014. CA_Assembly_Districts_WEB – This layer shows the boundary lines for all the assembly districts in California. It is owned and maintained by the Sierra Nevada Conservancy (SNC) and boundaries may not be accurate. CA_Senate_Districts_WEB – This layer shows the boundary lines for all the senate districts in California. It is owned and maintained by the Sierra Nevada Conservancy (SNC) and boundaries may not be accurate.

Informational Pop-up Box:County – California county where the project is locatedCommunity Served – California community that is benefiting from UDWN funding Type of Project – Project type, which can include bottled water, consolidation, hauled water, pilot study, POU, pump, tank, treatment, and well Approved Funding Amount – Amount of money in U.S. dollars approved for the projectApproval Date – Date that the project was approved for fundingStatus – Current status of the project (active or closed)Date Created:

Data created on November 18, 2022 and valid up to this date.

Sources:

Urgent Drinking Water Needs data was exported from the CAA Database.

The Sierra Nevada Conservancy (SNC) created the California Senate and Assembly layers.

Points of Contact:

Christina Raynard is the creator and owner of this layer. Christina.raynard@waterboards.ca.gov (State Water Resources Control Board, Division of Financial Assistance)

Terms of Use

No special restrictions or limitations on using the item’s content have been provided.

Sieve filters are lacking in ArcGIS. Therefore, I developed a simple model that will perform a sieve filter based on the Jeffrey Evans' comments in the following forum:http://gis.stackexchange.com/questions/91609/where-can-i-use-a-sieve-filterThe basic idea of the sieve filter is that you can remove small "specks" or "polygons" from a categorical raster replacing them with their neighoring values. Unlike a focal majority operation which generalizes your data the sieve filter preserves the basic shapes of the "polygons". the only parameter required is the minimum number of cells in "polygon" (region group in raster terminology).Alternatively there may be some instances where you wish to generalize your data using a focal majority operation. However, the focal majority will return No Data in the case of a tie. Usually these are single cells or very small clusters of cells. The focal sieve tool allows you to remove these "specks" from your data. Hence, you get the generalization of the focal majority but use the sieve operation to clean up the specks. The focal sieve tool requires both a neighborhood size like a typical focal statistic but also a minimum number of cells.

Data acquisitionOccurrence data for bee species were downloaded from ALA60 using ALA4R version 1.8.064 in R version 3.6.265.Floral visitation data were obtained from ALA60, Museums Victoria, the Western Australian Museum66,67, and publications (Tables S1 and S2). Floral visitation records were checked for errors and synonymies using the Australian Plant Name Index68. Life-history traits for bee species were sourced, in most cases, from the most recent taxonomic descriptions, or other publications (Tables S1 and S2). A one-hectare resolution Major Vegetation Subgroup (MVS) map was sourced from Geoscience Australia’s National Mapping Division (NMD)61. Fire frequency data from 1988 to 2016 were downloaded from the Department of Environment and Energy (DEE)69, 2019–20 wildfire occurrence data (National Indicative Aggregated Fire Extent Dataset — NIAFED — version 20200623) were sourced from the Department of Agriculture, Water and the Environment (DAWE)36, and 2019–20 wildfire intensity data (Google Earth Engine Burnt Area Map — GEEBAM) were sourced from the Department of Planning, Industry and Environment (DPIE)62. All raster data sources were matched in resolution to the one-hectare MVS map. These GIS data sources may vary in spatial uncertainty or resolution and their caveats can be found at their respective locations online.Data filtering and analysesOccurrence data from ALA were filtered to include only reliable (“preserved specimens”, “machine observations” — e.g., malaise traps, — and data from published datasets) and “present” (compared to “absent”) records. Records without geographic locations or that did not align with base maps were excluded from GIS analyses. Species were then filtered for minimum sample size (n = 30) and minimum number of unique localities (n = 5). However, if there were 15 or more unique localities and a sample size of less than 30, the species was included.The MVS map was reprojected to a world geodetic system (WGS 1984, EPSG:4326) and clipped to the 2019–20 wildfire map in QGIS version 3.1270. The NIAFED and GEEBAM maps were aligned and matched to the resolution of the MVS map using the package raster version 3.0-1271 in R version 3.6.265. Major vegetation subgroups61, 2019–20 wildfire status36, and fire frequency69 were extracted for each ALA record using raster. The proportion of each MVS burnt was calculated by clipping MVS maps with the 2019–20 burn map in ArcMap Version 10.6.172. All map files used in our analyses are available at (html location to be confirmed upon acceptance) for use with our R script.We complemented species distributional data (ALA60 point data) with spatial information on their associated habitat (MVS61), to avoid reliance on the limited data for some species. To determine the potential distribution of each species we buffered the latitudinal and longitudinal extents of the raster datasets (MVS, fire frequency, NIAFED, and GEEBAM) by 20% in each direction. For geographically-restricted species with latitudinal or longitudinal ranges less than one degree (~111 km), we buffered their extent by one degree in each direction along that axis or axes. These values were chosen as conservative estimates of species distributional extents, but we recognize that this treatment may over-inflate the distribution of some species with highly-localized ranges. These data are broken into four files:Map_data — hosts all of the map files used in the analysesBee-plant_point_data — hosts the ALA download data, combined bee dataset, and the life history and plant data spreadsheetWard_comparison_data — hosts some of the data used for the Ward co-analysis using our methodAll_other_R_data — hosts many of the runfiles from our main analysis

Traditional methods for monitoring influenza are haphazard and lack fine-grained details regarding the spatial and temporal dynamics of outbreaks. Twitter gives researchers and public health officials an opportunity to examine the spread of influenza in real-time and at multiple geographical scales. In this paper, we introduce an improved framework for monitoring influenza outbreaks using the social media platform Twitter. Relying upon techniques from geographic information science (GIS) and data mining, Twitter messages were collected, filtered, and analyzed for the thirty most populated cities in the United States during the 2013–2014 flu season. The results of this procedure are compared with national, regional, and local flu outbreak reports, revealing a statistically significant correlation between the two data sources. The main contribution of this paper is to introduce a comprehensive data mining process that enhances previous attempts to accurately identify tweets related to influenza. Additionally, geographical information systems allow us to target, filter, and normalize Twitter messages.

Water Meter points within Fuquay-Varina. Most meter devices are owned and maintained by the Town, which provides water utility services. However, on some commercial sites, for example, the meter box and meter yoke are actually privately owned and maintained while the meter device is owned and maintained by the Town. This water meter dataset is constantly under development and improvement as there is increasing demand to integrate GIS meter information with other solutions. Please note that some meter points are not field-validated and some are not associated with a valid METERID for water service, and may essentially be duplicated legacy locations from old GIS data. Please note that ALL public utility data layers can be downloaded in a single .mpkx (ArcGIS Pro map package file), updated every Friday evening. This .mpkx file can be opened directly with ArcGIS Pro version 3+. Alternatively, you can extract the file geodatabase within it by renaming the file ending .mpkx to .zip and treating it like a zip archive file, for use in any version of ArcGIS Pro or ArcMap software. You can also use QGIS, a powerful, free, and open-source GIS software.The Town of Fuquay-Varina creates, maintains, and serves out a variety of utility information to the public, including its Potable Water System, Sanitary Sewer System, and Stormwater Collection System features. This is the same utility data displayed in our public web map. This utility data includes some features designated as 'private' that are not owned or maintained by the Town, but may be helpful for modeling and other informational purposes. Please pay particular attention to the terms of use and disclaimer associated with these data. Some data includes the use of Subtypes and Domains that may not translate well to Shapefile or GeoJSON downloads available through our Open Data site. Please beware the dangers of cartographic misrepresentation if you are unfamiliar with filtering and symbolizing data based on attributes. Water System Layers:Water LinesWater ValvesWater ManholesFire HydrantsFire Department ConnectionsWater MetersRPZ (Backflow Preventers)Water TankWater Booster StationsHarnett County Water District AreaSewer System Layers:Gravity Sewer LinesForced Sewer LinesSewer ManholesSewer ValvesSewer CleanoutsSewer Pump StationsWastewater Treatment PlantsStormwater System Layers:Stormwater Lines (Pipes)Stormwater Points (Inlets/Outlets/Manholes)Stormwater Control Measure Points (SCM's, such as Wet Ponds / Retention Basins)

The purpose of this layer is for reconnaissance level planning and regional assessment of historical tidal wetlands of the San Francisco Bay Area.Layer geometry was updated in 2025 as part of a county-wide data refresh. Updated geometry was taken from SFEI “Historical Habitats” gis data, filtering for “marsh” “tidal” and “channel”. SFEI used the 1971 map* the original hist_marsh_mrgn layer was made to represent and refined its boundaries with additional historical habitat data.More information can be found at: https://www.sfei.org/projects/napa-valley-historical-ecology-atlas

This is the 2022 version of the Aquifer Risk Map. The 2021 version of the Aquifer Risk Map is available here.This aquifer risk map is developed to fulfill requirements of SB-200 and is intended to help prioritize areas where domestic wells and state small water systems may be accessing raw source groundwater that does not meet primary drinking water standards (maximum contaminant level or MCL). In accordance with SB-200, the risk map is to be made available to the public and is to be updated annually starting January 1, 2021. The Fund Expenditure Plan states the risk map will be used by Water Boards staff to help prioritize areas for available SAFER funding. This is the final 2022 map based upon feedback received from the 2021 map. A summary of methodology updates to the 2022 map can be found here.This map displays raw source groundwater quality risk per square mile section. The water quality data is based on depth-filtered, declustered water quality results from public and domestic supply wells. The process used to create this map is described in the 2022 Aquifer Risk Map Methodology document. Data processing scripts are available on GitHub. Download/export links are provided in this app under the Data Download widget.This draft version was last updated December 1, 2021. Water quality risk: This layer contains summarized water quality risk per square mile section and well point. The section water quality risk is determined by analyzing the long-tern (20-year) section average and the maximum recent (within 5 years) result for all sampled contaminants. These values are compared to the MCL and sections with values above the MCL are “high risk”, sections with values within 80%-100% of the MCL are “medium risk” and sections with values below 80% of the MCL are “low risk”. The specific contaminants above or close to the MCL are listed as well. The water quality data is based on depth-filtered, de-clustered water quality results from public and domestic supply wells.Individual contaminants: This layer shows de-clustered water quality data for arsenic, nitrate, 1,2,3-trichloropropane, uranium, and hexavalent chromium per square mile section. Domestic Well Density: This layer shows the count of domestic well records per square mile. The domestic well density per square mile is based on well completion report data from the Department of Water Resources Online System for Well Completion Reports, with records drilled prior to 1970 removed and records of “destruction” removed.State Small Water Systems: This layer displays point locations for state small water systems based on location data from the Division of Drinking Water.Public Water System Boundaries: This layer displays the approximate service boundaries for public water systems based on location data from the Division of Drinking Water.Reference layers: This layer contains several reference boundaries, including boundaries of CV-SALTS basins with their priority status, Groundwater Sustainability Agency boundaries, census block group boundaries, county boundaries, and groundwater unit boundaries. ArcGIS Web Application

The dataset contains a map of the main classes of agricultural land use (dominant crop types and other land use types) in Germany for the year 2023. It complements a series of maps that are produced annually at the Thünen Institute beginning with the year 2017 on the basis of satellite data. The maps cover the entire open landscape, i.e., the agriculturally used area (UAA) and e.g., uncultivated areas. The map was derived from time series of Sentinel-1, Sentinel-2, Landsat 8 and additional environmental data. Map production is based on the methods described in Blickensdörfer et al. (2022).

All optical satellite data were managed, pre-processed and structured in an analysis-ready data (ARD) cube using the open-source software FORCE - Framework for Operational Radiometric Correction for Environmental monitoring (Frantz, D., 2019), in which SAR and environmental data were integrated.

The map extent covers all areas in Germany that are defined as agricultural land, grassland, small woody features, heathland, peatland or unvegetated areas according to ATKIS Basis-DLM (Geobasisdaten: © GeoBasis-DE / BKG, 2020).

Version v201:
Post-processing of the maps included a sieve filter as well as a ruleset for the reduction of non-plausible areas using the Basis-DLM and the digital terrain model of Germany (Geobasisdaten: © GeoBasis-DE / BKG, 2015).

The maps are available as cloud optimized GeoTiffs, which makes downloading the full dataset optional. All data can directly be accessed in QGIS, R, Python or any supported software of your choice using the URL that will be provided on request. By doing so the entire map area or only the regions of interest can be accessed. QGIS legend files for data visualization can be downloaded separately.

Class-specific accuracies for each year are proveded in the respective tables. We provide this dataset "as is" without any warranty regarding the accuracy or completeness and exclude all liability.

_

Mailing list

If you do not want to miss the latest updates, please enroll to our mailing list.

_

References:

Blickensdörfer, L., Schwieder, M., Pflugmacher, D., Nendel, C., Erasmi, S., & Hostert, P. (2022). Mapping of crop types and crop sequences with combined time series of Sentinel-1, Sentinel-2 and Landsat 8 data for Germany. Remote Sensing of Environment, 269, 112831.

BKG, Bundesamt für Kartographie und Geodäsie (2015). Digitales Geländemodell Gitterweite 10 m. DGM10. https://sg.geodatenzentrum.de/web_public/gdz/dokumentation/deu/dgm10.pdf (last accessed: 28. April 2022).

BKG, Bundesamt für Kartographie und Geodäsie (2020). Digitales Basis-Landschaftsmodell.
https://sg.geodatenzentrum.de/web_public/gdz/dokumentation/deu/basis-dlm.pdf (last accessed: 28. April 2022).

Frantz, D. (2019). FORCE—Landsat + Sentinel-2 Analysis Ready Data and Beyond. Remote Sensing, 11, 1124.

Statistisches Bundesamt, Deutschland (2024). Ökosystematlas Deutschland
https://oekosystematlas-ugr.destatis.de/ (last accessed: 08.02.2024).

_
National-scale crop type maps for Germany from combined time series of Sentinel-1, Sentinel-2 and Landsat data (2017 to 2021) © 2024 by Schwieder, Marcel; Tetteh, Gideon Okpoti; Blickensdörfer, Lukas; Gocht, Alexander; Erasmi, Stefan; licensed under CC BY 4.0.

Funding was provided by the German Federal Ministry of Food and Agriculture as part of the joint project “Monitoring der biologischen Vielfalt in Agrarlandschaften” (MonViA, Monitoring of biodiversity in agricultural landscapes).

This layer presents detectable thermal activity from MODIS satellites for the last 7 days. MODIS Global Fires is a product of NASA’s Earth Observing System Data and Information System (EOSDIS), part of NASA's Earth Science Data. EOSDIS integrates remote sensing and GIS technologies to deliver global MODIS hotspot/fire locations to natural resource managers and other stakeholders around the World.

Area Covered: World

What can I do with this layer?
The MODIS thermal activity layer can be used to visualize and assess wildfires worldwide. However, it should be noted that this dataset contains many “false positives” (e.g., oil/natural gas wells or volcanoes) since the satellite will detect any large thermal signal.


It takes approximately 2 – 4 hours after satellite overpass for MODIS Rapid Response to process the data, and for the Fire Information for Resource Management System (FIRMS) to update the website. Occasionally, hardware errors can result in processing delays beyond the 2-4 hour range. Additional information on the MODIS system status can be found at MODIS Rapid Response.

Attribute Information

• Latitude and Longitude: The center point location of the 1km (approx.) pixel flagged as containing one or more fires/hotspots (fire size is not 1km, but variable). Stored by Point Geometry. See What does a hotspot/fire detection mean on the ground?
• Brightness: The brightness temperature measured (in Kelvin) using the MODIS channels 21/22 and channel 31.
• Scan and Track: The actual spatial resolution of the scanned pixel. Although the algorithm works at 1km resolution, the MODIS pixels get bigger toward the edge of the scan. See What does scan and track mean?
• Date and Time: Acquisition date of the hotspot/active fire pixel and time of satellite overpass in UTC (client presentation in local time). Stored by Acquisition Date.
  
• Acquisition Date: Derived Date/Time field combining Date and Time attributes.
• Satellite: Whether the detection was picked up by the Terra or Aqua satellite.
• Confidence: The detection confidence is a quality flag of the individual hotspot/active fire pixel.
• Version: Version refers to the processing collection and source of data. The number before the decimal refers to the collection (e.g. MODIS Collection 6). The number after the decimal indicates the source of Level 1B data; data processed in near-real time by MODIS Rapid Response will have the source code “CollectionNumber.0”. Data sourced from MODAPS (with a 2-month lag) and processed by FIRMS using the standard MOD14/MYD14 Thermal Anomalies algorithm will have a source code “CollectionNumber.x”. For example, data with the version listed as 5.0 is collection 5, processed by MRR, data with the version listed as 5.1 is collection 5 data processed by FIRMS using Level 1B data from MODAPS.
• Bright.T31: Channel 31 brightness temperature (in Kelvins) of the hotspot/active fire pixel.
• FRP: Fire Radiative Power. Depicts the pixel-integrated fire radiative power in MW (MegaWatts). FRP provides information on the measured radiant heat output of detected fires. The amount of radiant heat energy liberated per unit time (the Fire Radiative Power) is thought to be related to the rate at which fuel is being consumed (Wooster et. al. (2005)).
• DayNight: The standard processing algorithm uses the solar zenith angle (SZA) to threshold the day/night value; if the SZA exceeds 85 degrees it is assigned a night value. SZA values less than 85 degrees are assigned a day time value. For the NRT algorithm the day/night flag is assigned by ascending (day) vs descending (night) observation. It is expected that the NRT assignment of the day/night flag will be amended to be consistent with the standard processing.
• Hours Old: Derived field that provides age of record in hours between Acquisition date/time and latest update date/time. 0 = less than 1 hour ago, 1 = less than 2 hours ago, 2 = less than 3 hours ago, and so on.

This map is provided for informational purposes and is not monitored 24/7 for accuracy and

City of Seattle 2 ft contours derived from Lidar captured in 2021. Contour lines display at 2ft, 10ft and 50ft intervals dependent on scale. Lines have been smoothed and generalized for display and performance.

Development Detail:

This vector tile service includes topographic contour lines representing elevation at 2-foot intervals within the city of Seattle.

The contours were derived from a bare earth - digital elevation model (DEM) with a pixel resolution of 1.5 feet. The lidar data that created the DEM were collected by NV5 Geospatial over the spring and summer months of 2021 and provided to the city by King County in 2022.

The DEM used to generate the contours was filtered using the Focal Statistics tool in ArcGIS, which served to limit some abrupt changes in cell values. A 3x3 rectangular neighborhood analysis was applied and a mean value was calculated per raster cell.

After running the Focal Statistics tool, 2-foot contours were generated from the filtered DEM. To reduce file size and improve performance, the contours were generalized further using the Smooth Line tool in ArcGIS. A smoothing algorithm type of Polynomial Approximation with Exponential Kernel (PAEK) and a smoothing tolerance of 20 feet was selected in the Smooth Line tool parameter options.

Finally, after executing both generalization tools (Focal Statistics and Smooth Line), all lines less than 25 feet in length were omitted from the final output.

Please note: The 2-foot contours are intended to be used for general reference and cartographic purposes only and should not be used for analysis purposes.

This layer presents detectable thermal activity from MODIS satellites for the last 7 days. MODIS Global Fires is a product of NASA’s Earth Observing System Data and Information System (EOSDIS), part of NASA's Earth Science Data. EOSDIS integrates remote sensing and GIS technologies to deliver global MODIS hotspot/fire locations to natural resource managers and other stakeholders around the World.

Area Covered: World

What can I do with this layer?
The MODIS thermal activity layer can be used to visualize and assess wildfires worldwide. However, it should be noted that this dataset contains many “false positives” (e.g., oil/natural gas wells or volcanoes) since the satellite will detect any large thermal signal.


It takes approximately 2 – 4 hours after satellite overpass for MODIS Rapid Response to process the data, and for the Fire Information for Resource Management System (FIRMS) to update the website. Occasionally, hardware errors can result in processing delays beyond the 2-4 hour range. Additional information on the MODIS system status can be found at MODIS Rapid Response.

Attribute Information

• Latitude and Longitude: The center point location of the 1km (approx.) pixel flagged as containing one or more fires/hotspots (fire size is not 1km, but variable). Stored by Point Geometry. See What does a hotspot/fire detection mean on the ground?
• Brightness: The brightness temperature measured (in Kelvin) using the MODIS channels 21/22 and channel 31.
• Scan and Track: The actual spatial resolution of the scanned pixel. Although the algorithm works at 1km resolution, the MODIS pixels get bigger toward the edge of the scan. See What does scan and track mean?
• Date and Time: Acquisition date of the hotspot/active fire pixel and time of satellite overpass in UTC (client presentation in local time). Stored by Acquisition Date.
  
• Acquisition Date: Derived Date/Time field combining Date and Time attributes.
• Satellite: Whether the detection was picked up by the Terra or Aqua satellite.
• Confidence: The detection confidence is a quality flag of the individual hotspot/active fire pixel.
• Version: Version refers to the processing collection and source of data. The number before the decimal refers to the collection (e.g. MODIS Collection 6). The number after the decimal indicates the source of Level 1B data; data processed in near-real time by MODIS Rapid Response will have the source code “CollectionNumber.0”. Data sourced from MODAPS (with a 2-month lag) and processed by FIRMS using the standard MOD14/MYD14 Thermal Anomalies algorithm will have a source code “CollectionNumber.x”. For example, data with the version listed as 5.0 is collection 5, processed by MRR, data with the version listed as 5.1 is collection 5 data processed by FIRMS using Level 1B data from MODAPS.
• Bright.T31: Channel 31 brightness temperature (in Kelvins) of the hotspot/active fire pixel.
• FRP: Fire Radiative Power. Depicts the pixel-integrated fire radiative power in MW (MegaWatts). FRP provides information on the measured radiant heat output of detected fires. The amount of radiant heat energy liberated per unit time (the Fire Radiative Power) is thought to be related to the rate at which fuel is being consumed (Wooster et. al. (2005)).
• DayNight: The standard processing algorithm uses the solar zenith angle (SZA) to threshold the day/night value; if the SZA exceeds 85 degrees it is assigned a night value. SZA values less than 85 degrees are assigned a day time value. For the NRT algorithm the day/night flag is assigned by ascending (day) vs descending (night) observation. It is expected that the NRT assignment of the day/night flag will be amended to be consistent with the standard processing.
• Hours Old: Derived field that provides age of record in hours between Acquisition date/time and latest update date/time. 0 = less than 1 hour ago, 1 = less than 2 hours ago, 2 = less than 3 hours ago, and so on.

This map is provided for informational purposes and is not monitored 24/7 for accuracy and

This layer presents the best-known point and perimeter locations of wildfire occurrences within the United States over the past 7 days. Points mark a location within the wildfire area and provide current information about that wildfire. Perimeters are the line surrounding land that has been impacted by a wildfire.Consumption Best Practices:

As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest using the included "Age" fields that maintain the number of days or hours since a record was created or last modified, compared to the last service update. These queries fully support the ability to cache a response, allowing common query results to be efficiently provided to users in a high demand service environment. When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable.Source:  Wildfire points are sourced from Integrated Reporting of Wildland-Fire Information (IRWIN) and perimeters from National Interagency Fire Center (NIFC). Current Incidents: This layer provides a near real-time view of the data being shared through the Integrated Reporting of Wildland-Fire Information (IRWIN) service. IRWIN provides data exchange capabilities between participating wildfire systems, including federal, state and local agencies. Data is synchronized across participating organizations to make sure the most current information is available. The display of the points are based on the NWCG Fire Size Classification applied to the daily acres attribute.Current Perimeters: This layer displays fire perimeters posted to the National Incident Feature Service. It is updated from operational data and may not reflect current conditions on the ground. For a better understanding of the workflows involved in mapping and sharing fire perimeter data, see the National Wildfire Coordinating Group Standards for Geospatial Operations.Update Frequency:  Every 15 minutes using the Aggregated Live Feed Methodology based on the following filters:Events modified in the last 7 daysEvents that are not given a Fire Out DateIncident Type Kind: FiresIncident Type Category: Prescribed Fire, Wildfire, and Incident Complex

Area Covered: United StatesWhat can I do with this layer? The data includes basic wildfire information, such as location, size, environmental conditions, and resource summaries. Features can be filtered by incident name, size, or date keeping in mind that not all perimeters are fully attributed.Attribute InformationThis is a list of attributes that benefit from additional explanation. Not all attributes are listed.Incident Type Category: This is a breakdown of events into more specific categories.Wildfire (WF) -A wildland fire originating from an unplanned ignition, such as lightning, volcanos, unauthorized and accidental human caused fires, and prescribed fires that are declared wildfires.Prescribed Fire (RX) - A wildland fire originating from a planned ignition in accordance with applicable laws, policies, and regulations to meet specific objectives.Incident Complex (CX) - An incident complex is two or more individual incidents in the same general proximity that are managed together under one Incident Management Team. This allows resources to be used across the complex rather than on individual incidents uniting operational activities.IrwinID: Unique identifier assigned to each incident record in both point and perimeter layers.

Acres: these typically refer to the number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.Discovery: An estimate of acres burning upon the discovery of the fire.Calculated or GIS:  A measure of acres calculated (i.e., infrared) from a geospatial perimeter of a fire.Daily: A measure of acres reported for a fire.Final: The measure of acres within the final perimeter of a fire. More specifically, the number of acres within the final fire perimeter of a specific, individual incident, including unburned and unburnable islands.

Dates: the various systems contribute date information differently so not all fields will be populated for every fire.FireDiscovery: The date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes.

Containment: The date and time a wildfire was declared contained. Control: The date and time a wildfire was declared under control.ICS209Report: The date and time of the latest approved ICS-209 report.Current: The date and time a perimeter is last known to be updated.FireOut: The date and time when a fire is declared out.ModifiedOnAge: (Integer) Computed days since event last modified.DiscoveryAge: (Integer) Computed days since event's fire discovery date.CurrentDateAge: (Integer) Computed days since perimeter last modified.CreateDateAge: (Integer) Computed days since perimeter entry created.

GACC: A code that identifies one of the wildland fire geographic area coordination centers. A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.Fire Mgmt Complexity: The highest management level utilized to manage a wildland fire event.Incident Management Organization: The incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned.Unique Fire Identifier: Unique identifier assigned to each wildland fire. yyyy = calendar year, SSUUUU = Point Of Origin (POO) protecting unit identifier (5 or 6 characters), xxxxxx = local incident identifier (6 to 10 characters)RevisionsJan 4, 2021: Added Integer fields 'Days Since...' to Current_Incidents point layer and Current_Perimeters polygon layer. These fields are computed when the data is updated, reflecting the current number of days since each record was last updated. This will aid in making 'age' related, cache friendly queries.Mar 12, 2021: Added second set of 'Age' fields for Event and Perimeter record creation, reflecting age in Days since service data update.Apr 21, 2021: Current_Perimeters polygon layer is now being populated by NIFC's newest data source. A new field was added, 'IncidentTypeCategory' to better distinguish Incident types for Perimeters and now includes type 'CX' or Complex Fires. Five fields were not transferrable, and as a result 'Comments', 'Label', 'ComplexName', 'ComplexID', and 'IMTName' fields will be Null moving forward.Apr 26, 2021: Updated Incident Layer Symbology to better clarify events, reduce download size and overhead of symbols. Updated Perimeter Layer Symbology to better distingish between Wildfires and Prescribed Fires.May 5, 2021: Slight modification to Arcade logic for Symbology, refining Age comparison to Zero for fires in past 24-hours.Aug 16, 2021: Enabled Time Series capability on Layers (off by default) using 'Fire Discovery Date' for Incidents and 'Creation Date' for Perimeters.This layer is provided for informational purposes and is not monitored 24/7 for accuracy and currency.If you would like to be alerted to potential issues or simply see when this Service will update next, please visit our Live Feed Status Page!

Stormwater collection/conveyance point features in Fuquay-Varina (e.g. inlets and outlets, and stormwater manholes/junction boxes). Please note that many of the stormwater point features represent privately owned and maintained stormwater features, and these are essential for mapping and understanding the stormwater drainage network sub-systems at the neighborhood level. Please pay attention to the Subtype field to identify the different categories of public vs. private; inlet vs. outlet; and manhole types of stormwater features. Directionality (start vs. end vertices) of these line features reflects real world flow direction. The GIS data in the area of Downtown Fuquay-Varina has a lot of old and erroneous stormwater features. A project is currently underway to correct much of this inaccurate stormwater data. Please note that ALL public utility data layers can be downloaded in a single .mpkx (ArcGIS Pro map package file), updated every Friday evening. This .mpkx file can be opened directly with ArcGIS Pro version 3+. Alternatively, you can extract the file geodatabase within it by renaming the file ending .mpkx to .zip and treating it like a zip archive file, for use in any version of ArcGIS Pro or ArcMap software. You can also use QGIS, a powerful, free, and open-source GIS software.The Town of Fuquay-Varina creates, maintains, and serves out a variety of utility information to the public, including its Potable Water System, Sanitary Sewer System, and Stormwater Collection System features. This is the same utility data displayed in our public web map. This utility data includes some features designated as 'private' that are not owned or maintained by the Town, but may be helpful for modeling and other informational purposes. Please pay particular attention to the terms of use and disclaimer associated with these data. Some data includes the use of Subtypes and Domains that may not translate well to Shapefile or GeoJSON downloads available through our Open Data site. Please beware the dangers of cartographic misrepresentation if you are unfamiliar with filtering and symbolizing data based on attributes. Water System Layers:Water LinesWater ValvesWater ManholesFire HydrantsFire Department ConnectionsWater MetersWater Meter VaultsRPZ (Backflow Preventers)Water TankWater Booster StationsHarnett County Water District AreaSewer System Layers:Gravity Sewer LinesForced Sewer LinesSewer ManholesSewer ValvesSewer CleanoutsSewer Pump StationsWastewater Treatment PlantsStormwater System Layers:Stormwater Lines (Pipes)Stormwater Points (Inlets/Outlets/Manholes)Stormwater Control Measure Points (SCM's, such as Wet Ponds / Retention Basins)