The water area of Combee Settlement, FL 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 Combee Settlement, FL

  • API

    GRU Customer Reclaimed Water Consumption

    data.cityofgainesville.org | Last Updated 2022-09-27T18:05:00.000Z

    Monthly reclaimed water consumption in Kilo-gallons (kgals) by service address for all customers in the GRU Service Area. Reclaimed water is also known as sewer or wastewater. (Potable water use can be found in another dataset)

  • API

    Stormwater_Features

    data.cityofgainesville.org | Last Updated 2024-04-10T19:07:06.000Z

    For NPDES Stormwater sewer system enhanced mapping project. Contains a GIS polygon feature class of stormwater basins in Gainesville, FL as a result of the NPDES stormwater system mapping project. This feature does not participate in the GIS network, and is for cartographic purposes only. This file is current only up to 02/04/08 and may be incomplete, and only covers those areas of Gainesville, FL that have been mapped up to 02/04/08. The file is also subject to constant updating as project progresses. This feature class is for informational purposes only. Do not rely on this file for accuracy of dimensions, size or location. The City of Gainesville does not assume responsibility to update this information for any error or omission in this file. This shapefile may indicate the zoning/land use on the properties as shown. Do not rely on this file for accuracy of dimensions. For specific information, contact the City of Gainesville, Florida.

  • API

    Water Point Data Exchange - Plus (WPdx+)

    data.waterpointdata.org | Last Updated 2024-10-22T06:13:57.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

    Parcel

    data.bayareametro.gov | Last Updated 2024-10-16T14:05:35.000Z

  • API

    Census Tracts 2010 Centroids

    data.bayareametro.gov | Last Updated 2021-11-19T16:27:25.000Z

    Centroid of 2010 census tracts. Provides 2010 census tracts for the San Francisco Bay Region, clipped by the Metropolitan Transportation Commission to remove major coastal and bay water areas. 2010 Census tracts for the San Francisco Bay Region, clipped to remove major coastal and bay water areas. Features were extracted from, and clipped using, California 2018 TIGER/Line shapefiles by the Metropolitan Transportation Commission. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and are reviewed and updated by local participants prior to each decennial census as part of the Census Bureau’s Participant Statistical Areas Program (PSAP). The Census Bureau updates census tracts in situations where no local participant existed or where local or tribal governments declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of decennial census data. Census tracts generally have a population size between 1,200 and 8,000 people with an optimum size of 4,000 people. The spatial size of census tracts varies widely depending on the density of settlement. Ideally, census tract boundaries remain stable over time to facilitate statistical comparisons from census to census. However, physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, significant changes in population may result in splitting or combining census tracts. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some states to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. Census Tract Codes and Numbers—Census tract numbers have up to a 4-character basic number and may have an optional 2-character suffix; for example, 1457.02. The census tract numbers (used as names) eliminate any leading zeroes and append a suffix only if required. The 6-character numeric census tract codes, however, include leading zeroes and have an implied decimal point for the suffix. Census tract codes range from 000100 to 998999 and are unique within a county or equivalent area. The Census Bureau assigned a census tract code of 9900 to represent census tracts delineated to cover large bodies of water. In addition, census tract codes in the 9400s represent American Indian Areas and codes in the 9800s represent special land use areas. The Census Bureau uses suffixes to help identify census tract changes for comparison purposes. Local participants have an opportunity to review the existing census tracts before each census. If local participants split a census tract, the split parts usually retain the basic number, but receive different suffixes. In a few counties, local participants request major changes to, and renumbering of, the census tracts. Changes to individual census tract boundaries usually do not result in census tract numbering changes. Relationship to Other Geographic Entities—Within the standard census geographic hierarchy, census tracts never cross state or county boundaries, but may cross the boundaries of county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian, Alaska Native, and Native Hawaiian areas.

  • API

    Texas Commission on Environmental Quality - Supplemental Environmental Projects

    data.texas.gov | Last Updated 2024-10-02T17:09:00.000Z

    This is data represented in the Annual Enforcement Report, pursuant to Texas Water Code Section 5.126, and published each December following the end of the fiscal year. Supplemental Environmental Projects (SEPs) are environmentally beneficial projects that a respondent agrees to undertake in settlement of an enforcement action. Dollars directed to TCEQ-approved environmental projects may be used to offset assessed penalties in enforcement actions.

  • API

    RSBS SMO: Part 2 of 2, New York State Residential Statewide Baseline Study: Single and Multifamily Occupant Telephone or Web Survey

    data.ny.gov | Last Updated 2019-11-15T21:50:04.000Z

    How does your organization use this dataset? What other NYSERDA or energy-related datasets would you like to see on Open NY? Let us know by emailing OpenNY@nyserda.ny.gov. This is part 2 (contains: Clothes Washing and Drying; Water Heating; Home Lighting; Pool and Spa; Small Household Appliances; and Miscellaneous Equipment) of 2; part 1 (https://data.ny.gov/d/3m6x-h3qa) contains: Behavior and Demographics; Building Shell; Kitchen Appliances; and Heating and Cooling. The New York State Energy Research and Development Authority (NYSERDA), in collaboration with the New York State Department of Public Service (DPS), conducted a statewide residential baseline study (study) from 2011 to 2014 of the single-family and multifamily residential housing segments, including new construction, and a broad range of energy uses and efficiency measures. This dataset includes 2,982 single-family and 379 multifamily occupant survey completes for a total of 3,361 responses. The survey involved 2,285 Web, 1,041 telephone, and 35 mini-inspection surveys. The survey collected information on the following building characteristics: building shell, kitchen appliances, heating and cooling equipment, water heating equipment, clothes washing and drying equipment, lighting, pool and spa equipment, small household appliances, miscellaneous energy consuming equipment, as well as behaviors and characteristics of respondents.

  • API

    Land Use_data

    opendata.utah.gov | Last Updated 2024-04-10T19:40:16.000Z

    This dataset combines the work of several different projects to create a seamless data set for the contiguous United States. Data from four regional Gap Analysis Projects and the LANDFIRE project were combined to make this dataset. In the Northwestern United States (Idaho, Oregon, Montana, Washington and Wyoming) data in this map came from the Northwest Gap Analysis Project. In the Southwestern United States (Colorado, Arizona, Nevada, New Mexico, and Utah) data used in this map came from the Southwest Gap Analysis Project. The data for Alabama, Florida, Georgia, Kentucky, North Carolina, South Carolina, Mississippi, Tennessee, and Virginia came from the Southeast Gap Analysis Project and the California data was generated by the updated California Gap land cover project. The Hawaii Gap Analysis project provided the data for Hawaii. In areas of the county (central U.S., Northeast, Alaska) that have not yet been covered by a regional Gap Analysis Project, data from the Landfire project was used. Similarities in the methods used by these projects made possible the combining of the data they derived into one seamless coverage. They all used multi-season satellite imagery (Landsat ETM+) from 1999-2001 in conjunction with digital elevation model (DEM) derived datasets (e.g. elevation, landform) to model natural and semi-natural vegetation. Vegetation classes were drawn from NatureServe’s Ecological System Classification (Comer et al. 2003) or classes developed by the Hawaii Gap project. Additionally, all of the projects included land use classes that were employed to describe areas where natural vegetation has been altered. In many areas of the country these classes were derived from the National Land Cover Dataset (NLCD). For the majority of classes and, in most areas of the country, a decision tree classifier was used to discriminate ecological system types. In some areas of the country, more manual techniques were used to discriminate small patch systems and systems not distinguishable through topography. The data contains multiple levels of thematic detail. At the most detailed level natural vegetation is represented by NatureServe’s Ecological System classification (or in Hawaii the Hawaii GAP classification). These most detailed classifications have been crosswalked to the five highest levels of the National Vegetation Classification (NVC), Class, Subclass, Formation, Division and Macrogroup. This crosswalk allows users to display and analyze the data at different levels of thematic resolution. Developed areas, or areas dominated by introduced species, timber harvest, or water are represented by other classes, collectively refered to as land use classes; these land use classes occur at each of the thematic levels. Six layer files are included in the download packages to assist the user in displaying the data at each of the Thematic levels in ArcGIS.

  • API

    Tracts 2020

    data.delaware.gov | Last Updated 2024-03-01T14:44:49.000Z

    <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation.</SPAN></P><P><SPAN>Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2020 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2010 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area.</SPAN></P></DIV></DIV></DIV>