The land area of Tempe, AZ was 40 in 2012.
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 -
Geographic and Area Datasets Involving Tempe, AZ
- API
ENERGY STAR Certified Commercial Dishwashers
data.energystar.gov | Last Updated 2024-10-31T13:33:17.000ZCertified 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
Maricopa County Regional Work Zone Data Exchange (WZDx) v1.1 Feed Sample
datahub.transportation.gov | Last Updated 2024-05-13T17:44:37.000ZThe WZDx Specification enables infrastructure owners and operators (IOOs) to make harmonized work zone data available for third party use. The intent is to make travel on public roads safer and more efficient through ubiquitous access to data on work zone activity. Specifically, the project aims to get data on work zones into vehicles to help automated driving systems (ADS) and human drivers navigate more safely. MCDOT leads the effort to aggregate and collect work zone data from the AZTech Regional Partners. A continuously updating archive of the WZDx feed data can be found at <a href="http://usdot-its-workzone-publicdata.s3.amazonaws.com/index.html" target="_blank" rel="noopener">ITS WorkZone Data Sandbox</a>. The live feed is currently compliant with <a href="https://github.com/usdot-jpo-ode/jpo-wzdx/tree/v1.1" target="_blank" rel="noopener">WZDx specification version 1.1</a>.
- API
King County Ambient Streams Monitoring - Site Water Quality Criteria
data.kingcounty.gov | Last Updated 2023-07-18T00:55:59.000Z - API
City of Mesa Population
citydata.mesaaz.gov | Last Updated 2024-07-01T14:40:25.000ZCity of Mesa population provided by Census Bureau Population Estimates Program (PEP) updated annually as of July 1. See <b><a href="https://www.census.gov/programs-surveys/popest/data/tables.html?utm_campaign=20240516pio&utm_medium=email&utm_source=govdelivery">Population and Housing Unit Estimates.</b></a> Census PEP estimates are used for state revenue sharing per AZ statute (42-5033.01). <b>This dataset is the authoritative source for all city metrics such as Crimes or Traffic Collisions per 1,000 residents.</b> 2024-2040 population projections provided by Maricopa County Association of Governments (MAG) and adopted June 2023. MAG's planning area and incorporated jurisdiction projections are published at <b><a href="https://azmag.gov/Portals/0/Maps-Data/Population-Housing/MAG-Socioeconomic-Projections-Report-2023.pdf?ver=02iYbZGsxK1mEY4JfIy5ZQ%3d%3d">2023 MAG Socioeconomic Projections</b></a> Other sources of population estimates include US Census American Community Survey 1-year and 5-year Estimates at https://citydata.mesaaz.gov/d/n5gn-m5c3 and https://citydata.mesaaz.gov/Economic-Development/d/9nqf-ygw6, Arizona Office of Economic Opportunity (OEO) at https://www.azcommerce.com/oeo/population/population-estimates/ (see link for OEO methodology which differs slightly from official US Census Estimates) and City of Mesa Office of Economic Development at https://www.selectmesa.com/business-environment/demographics (ESRI Community Analyst).
- API
Maricopa County Census Tracts
citydata.mesaaz.gov | Last Updated 2024-08-29T23:01:23.000ZGeospatial 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
- API
Restaurant Inspections in Tri-County Colorado 2018
data.colorado.gov | Last Updated 2024-10-31T10:58:24.000ZRestaurant Inspection data for food service facilities within Adams, Arapahoe, and Douglas counties in Colorado provided by Tri-County Health Department (TCHD) in 2018.
- API
Maricopa County Regional Work Zone Data Exchange (WZDx) v3.0 Feed Sample
datahub.transportation.gov | Last Updated 2024-05-13T17:45:57.000ZThe WZDx Specification enables infrastructure owners and operators (IOOs) to make harmonized work zone data available for third party use. The intent is to make travel on public roads safer and more efficient through ubiquitous access to data on work zone activity. Specifically, the project aims to get data on work zones into vehicles to help automated driving systems (ADS) and human drivers navigate more safely. MCDOT leads the effort to aggregate and collect work zone data from the AZTech Regional Partners. A continuously updating archive of the WZDx feed data can be found at <a href="http://usdot-its-workzone-publicdata.s3.amazonaws.com/index.html" target="_blank" rel="noopener">ITS WorkZone Data Sandbox</a>. The live feed is currently compliant with <a href="https://github.com/usdot-jpo-ode/jpo-wzdx/tree/v3.0" target="_blank" rel="noopener">WZDx specification version 3.0</a>.
- API
Mosquito Larval Counts
data.edmonton.ca | Last Updated 2024-10-28T18:03:43.000ZRecords of pools (bodies of water) sampled by city staff for presence of mosquito larvae.
- API
Horseshoe Crab Spawning Survey
data.delaware.gov | Last Updated 2022-10-06T19:41:25.000ZDelaware Bay shore survey data starting with 1999 which denotes peak spawning occurrences by day and lunar period, proportion of spawning in May (coinciding with shorebird stopovers), average water temperature, index values for female and male crabs per square meter by beach and bay-wide, the annual sex ratio, and index of abundance per beach.
- API
Land Use_data
opendata.utah.gov | Last Updated 2024-04-10T19:40:16.000ZThis 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.