The water area of Three Points, AZ was 0 in 2018.

Land Area

Water Area

Land area is a measurement providing the size, in square miles, of the land portions of geographic entities for which the Census Bureau tabulates and disseminates data. Area is calculated from the specific boundary recorded for each entity in the Census Bureau's geographic database. Land area is based on current information in the TIGER® data base, calculated for use with Census 2010.

Water Area figures include inland, coastal, Great Lakes, and territorial sea water. Inland water consists of any lake, reservoir, pond, or similar body of water that is recorded in the Census Bureau's geographic database. It also includes any river, creek, canal, stream, or similar feature that is recorded in that database as a two- dimensional feature (rather than as a single line). The portions of the oceans and related large embayments (such as Chesapeake Bay and Puget Sound), the Gulf of Mexico, and the Caribbean Sea that belong to the United States and its territories are classified as coastal and territorial waters; the Great Lakes are treated as a separate water entity. Rivers and bays that empty into these bodies of water are treated as inland water from the point beyond which they are narrower than 1 nautical mile across. Identification of land and inland, coastal, territorial, and Great Lakes waters is for data presentation purposes only and does not necessarily reflect their legal definitions.

Above charts are based on data from the U.S. Census American Community Survey | ODN Dataset | API - Notes:

1. ODN datasets and APIs are subject to change and may differ in format from the original source data in order to provide a user-friendly experience on this site.

2. To build your own apps using this data, see the ODN Dataset and API links.

3. If you use this derived data in an app, we ask that you provide a link somewhere in your applications to the Open Data Network with a citation that states: "Data for this application was provided by the Open Data Network" where "Open Data Network" links to http://opendatanetwork.com. Where an application has a region specific module, we ask that you add an additional line that states: "Data about REGIONX was provided by the Open Data Network." where REGIONX is an HREF with a name for a geographical region like "Seattle, WA" and the link points to this page URL, e.g. http://opendatanetwork.com/region/1600000US5363000/Seattle_WA

Geographic and Area Datasets Involving Three Points, AZ

  • API

    Elevation Benchmarks

    data.cityofchicago.org | Last Updated 2013-02-28T15:29:13.000Z

    The following dataset includes "Active Benchmarks," which are provided to facilitate the identification of City-managed standard benchmarks. Standard benchmarks are for public and private use in establishing a point in space. Note: The benchmarks are referenced to the Chicago City Datum = 0.00, (CCD = 579.88 feet above mean tide New York). The City of Chicago Department of Water Management’s (DWM) Topographic Benchmark is the source of the benchmark information contained in this online database. The information contained in the index card system was compiled by scanning the original cards, then transcribing some of this information to prepare a table and map. Over time, the DWM will contract services to field verify the data and update the index card system and this online database.This dataset was last updated September 2011. Coordinates are estimated. To view map, go to https://data.cityofchicago.org/Buildings/Elevation-Benchmarks-Map/kmt9-pg57 or for PDF map, go to http://cityofchicago.org/content/dam/city/depts/water/supp_info/Benchmarks/BMMap.pdf. Please read the Terms of Use: http://www.cityofchicago.org/city/en/narr/foia/data_disclaimer.html.

  • API

    Homeless Services Program Demographics

    citydata.mesaaz.gov | Last Updated 2024-10-04T05:42:03.000Z

    Information about individuals experiencing homelessness and receiving services through Maricopa Regional Continuum of Care Coordinated Entry Points managed by Maricopa Association of Governments (MAG). See Reporting Interval and Report Date columns for more information about the date range covered. Information about "Mesa residents only" defined by value "client" in Demographic Audience field. Information about all individuals (Mesa resident and non-resident) receiving services from a Mesa-based provider defined by value "provider" in the Demographic Audience field. Data is collected by the Homeless Management Information System Arizona (HMIS AZ). See also https://community.solari-inc.org/homeless-management-information-system/

  • API

    Violence Reduction - Shotspotter Alerts

    data.cityofchicago.org | Last Updated 2024-10-01T12:40:45.000Z

    This dataset contains all ShotSpotter alerts since the introduction of ShotSpotter to some Chicago Police Department (CPD) districts in 2017. ShotSpotter is a gunshot detection system designed to automatically determine the location of potential outdoor gunfire. ShotSpotter audio sensors are placed in several CPD districts throughout the city (specific districts are noted below). If at least three sensors detect a sound that the ShotSpotter software determines to be potential gunfire, a location is determined and the alert is sent to human ShotSpotter analysts for review. Either the alert is sent to CPD, or it is dismissed. Each alert can contain multiple rounds of gunfire; sometimes there are multiple alerts for what may be determined to be one incident. More detail on the technology and its accuracy can be found on the company’s website <a href="https://www.shotspotter.com">here</a>. It should also be noted that ShotSpotter alerts may increase year-over-year while gun violence did not necessarily increase accordingly because of improvements in detection sensors. ShotSpotter does not exist in every CPD district, and it was not rolled out in every district at the same time. ShotSpotter was first deployed in Chicago in 2017, and sensors exist in the following districts as of the May 2021 launch of this dataset: 002, 003, 004, 005, 006, 007, 008, 009, 010, 011, 015, and 025.

  • API

    ENERGY STAR Certified Commercial Dishwashers

    data.energystar.gov | Last Updated 2024-10-03T13:17:26.000Z

    Certified models meet all ENERGY STAR requirements as listed in the Version 3.0 ENERGY STAR Program Requirements for Commercial Dishwashers that are effective as of July 27, 2021. A detailed listing of key efficiency criteria are available at https://www.energystar.gov/products/commercial_food_service_equipment/commercial_dishwashers/key_product_criteria.

  • API

    Beach Water and Weather Sensor Locations

    data.cityofchicago.org | Last Updated 2015-06-04T21:55:52.000Z

    The locations of the Chicago Park District water and weather sensors that feed https://data.cityofchicago.org/d/qmqz-2xku and https://data.cityofchicago.org/d/k7hf-8y75.

  • API

    Water Point Data Exchange - Plus (WPdx+)

    data.waterpointdata.org | Last Updated 2024-10-04T06:09:24.000Z

    WPdx+ is an enhanced version of the WPdx-Basic dataset. For a full comparison between the two datasets, please visit our blog at https://www.waterpointdata.org/2021/10/07/introducing-wpdx-plus/. The Water Point Data Exchange (WPdx) is the global platform for sharing water point data. The WPdx Data Standard was designed by a wide range of stakeholders from across sectors and around the world. The core attributes included in the standard are already being collected by governments, researchers, and organizations around the world. To read more about the standard or to contribute water point data visit www.waterpointdata.org.

  • API

    Iowa Watershed Boundaries: Subwatersheds (HUC 12)

    mydata.iowa.gov | Last Updated 2023-12-05T18:03:00.000Z

    The Watershed Boundary Dataset (WBD) defines the areal extent of surface water drainage to a point, accounting for all land and surface areas. Watershed Boundaries are determined solely upon science-based hydrologic principles, not favoring any administrative boundaries or special projects, nor particular program or agency. The intent of defining Hydrologic Units (HU) for the Watershed Boundary Dataset is to establish a base-line drainage boundary framework, accounting for all land and surface areas. At a minimum, the WBD is being delineated and georeferenced to the USGS 1:24,000 scale topographic base map meeting National Map Accuracy Standards (NMAS). Hydrologic units are given a Hydrologic Unit Code (HUC). For example, a hydrologic region has a 2-digit HUC. A HUC describes where the unit is in the country and the level of the unit. "A hydrologic unit is a drainage area delineated to nest in a multi-level, hierarchical drainage system. Its boundaries are defined by hydrographic and topographic criteria that delineate an area of land upstream from a specific point on a river, stream or similar surface waters. A hydrologic unit can accept surface water directly from upstream drainage areas, and indirectly from associated surface areas such as remnant, non-contributing, and diversions to form a drainage area with single or multiple outlet points. Hydrologic units are only synonymous with classic watersheds when their boundaries include all the source area contributing surface water to a single defined outlet point."

  • API

    Area Table June 2019 Status V2

    opendata.fcc.gov | Last Updated 2023-08-01T13:34:54.000Z

    <b>The data collected to create this dataset was in place through data as of June, 2021. For more recent broadband availability data, please see https://broadbandmap.fcc.gov; for more information about the related data collection, please see https://www.fcc.gov/BroadbandData.</b> Summary data of fixed broadband coverage by geographic area

  • API

    DWR Dam Safety Jurisdictional Dam

    data.colorado.gov | Last Updated 2024-10-04T06:05:12.000Z

    A Jurisdictional Dam is a dam creating a reservoir with a capacity of more than 100 acre-feet, or creates a reservoir with a surface area in excess of 20 acres at the high-water line, or exceeds 10 feet in height measured vertically from the elevation of the lowest point of the natural surface of the ground where that point occurs along the longitudinal centerline of the dam up to the crest of the emergency spillway of the dam. For reservoirs created by excavation, or where the invert of the outlet conduit is placed below the surface of the natural ground at its lowest point beneath the dam, the jurisdictional height shall be measured from the invert of the outlet at the longitudinal centerline of the embankment or from the bottom of the excavation at the longitudinal centerline of the dam, whichever is greatest. Jurisdictional height is defined in Rule 4.2.19. The State Engineer shall have final authority over determination of the jurisdictional height of the dam.

  • API

    Maricopa County Census Tracts

    citydata.mesaaz.gov | Last Updated 2024-08-29T23:01:23.000Z

    Geospatial attributes of census tracts in Maricopa County, version 2022. Sourced from US Census https://catalog.data.gov/dataset/tiger-line-shapefile-2022-state-arizona-az-census-tract and filtered for County = 013