The City of Tempe ZIP Codes feature class is intended to show the USPS ZIP Code boundaries within Tempe, Arizona.

The ZIP Codes feature class shows the USPS ZIP Code boundaries within Maricopa County, Arizona.

9/8/20: This layer represents Mohave County/Hualapai Nation five-digit ZIP Code areas used by the U.S. Postal Service to deliver mail more effectively. The first digit of a five-digit ZIP Code divides the United States into 10 large groups of states numbered from 0 in the Northeast to 9 in the far West. Within these areas, each state is divided into an average of 10 smaller geographical areas, identified by the second and third digits. These digits, in conjunction with the first digit, represent a sectional center facility or a mail processing facility area. The fourth and fifth digits identify a post office, station, branch or local delivery area. It provides area, post office name, and population for each ZIP Code area in the United States.

Our Azerbaijan zip code Database offers comprehensive postal code data for spatial analysis, including postal and administrative areas. This dataset contains accurate and up-to-date information on all administrative divisions, cities, and zip codes, making it an invaluable resource for various applications such as address capture and validation, map and visualization, reporting and business intelligence (BI), master data management, logistics and supply chain management, and sales and marketing. Our location data packages are available in various formats, including CSV, optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more. Product features include fully and accurately geocoded data, multi-language support with address names in local and foreign languages, comprehensive city definitions, and the option to combine map data with UNLOCODE and IATA codes, time zones, and daylight saving times. Companies choose our location databases for their enterprise-grade service, reduction in integration time and cost by 30%, and weekly updates to ensure the highest quality.

Cumulation of the weekly release of COVID-19 data for Maricopa County by Zip Code. Includes PCR Test Percent Positivity as viewed on the Maricopa County School Reopening Dashboard map by week. For more information about the data, visit: https://www.maricopa.gov/5594/School-Metrics.

For current COVID-19 cases data updates, please see the COVID-19 Cases Per 100,000 by Zip Code dashboard, which shows the COVID-19 case rate per 100,000 population by week for each zip code and is supported by the weekly release of data from the Maricopa County Department of Public Health (MCDPH) https://data.tempe.gov/datasets/covid-19-case-indicators/explore.--------This table provides a daily log of confirmed COVID-19 cases by Zip Code. Data are provided by the Arizona Department of Health Services (ADHS). Data Source: Arizona Department of Health Services (AZDHS) daily COVID-19 report by zip code (https://adhsgis.maps.arcgis.com/apps/opsdashboard/index.html#/84b7f701060641ca8bd9ea0717790906). Daily Change is calculated by taking the current day’s case value for a given Postal Code and subtracting the prior day’s value. This resulting value is the Daily Change. Based on reporting from ADHS Daily Change may be a positive or negative number or 0 if no change has been reported. Moving Average is calculated by summing the current day’s case count with the prior 6 days’ cases for a given Postal Code and dividing by 7.Arizona Department of Health Services (AZDHS) data are scheduled for daily updates at 9:00 AM (COVID-19 cases) and 12:00 PM (COVID-19 vaccinations), but the times when the AZDHS releases that days COVID-19 cases and vaccinations may vary. City of Tempe data are updated each afternoon at 3:00 PM to allow for possible AZDHS delays. When there are AZDHS delays in updating the daily data, dashboard data updates may be delayed by 24 hours. The charts and daily values list can be used to confirm the date of the most recent counts on the COVID-19 cases and vaccinations dashboards. If data are not released by the time of the scheduled daily dashboard refresh, that day's values may appear on the dashboard as an addition to the next day's value.Additional InformationSource: Arizona Department of Health Services (AZDHS) daily COVID-19 report by zip code (https://adhsgis.maps.arcgis.com/apps/opsdashboard/index.html#/84b7f701060641ca8bd9ea0717790906)Contact (author): n/aContact E-Mail (author): n/aContact (maintainer): City of Tempe Open Data TeamContact E-Mail (maintainer): data@tempe.govData Source Type: TablePreparation Method: Data are exposed via ArcGIS Server and its REST API.Publish Frequency: DailyPublish Method: Data are downloaded each afternoon once ADHS updates its public API. Data are transformed and appended to a table in Tempe’s Enterprise GIS.Data Dictionary

This data is used to generate the COVID-19 Gilbert Dashboard at alex.gilbertaz.gov/covid19. It includes total confirmed cases in Gilbert ZIP codes, cases broken out by ZIP code, and new cases reported each day. All data is from the azdhs.gov COVID-19 ZIP code map.

This dataset is part of the Geographical repository maintained by Opendatasoft.This dataset contains data for zip codes 5 digits in United States of America.ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data for each decennial census. The Census Bureau delineates ZCTA boundaries for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands once each decade following the decennial census. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery.Processors and tools are using this data.EnhancementsAdd ISO 3166-3 codes.Simplify geometries to provide better performance across the services.Add administrative hierarchy.

Annual (1986-2020) land-use/land cover maps at 30-meter resolution of the Tucson metropolitan area, Arizona and the greater Santa Cruz Watershed including Nogales, Sonora, Mexico. Maps were created using a combination of Landsat imagery, derived transformation and indices, texture analysis and other ancillary data fed to a Random Forest classifier in Google Earth Engine. The maps contain 13 classes based on the National Land Cover Classification scheme and modified to reflect local land cover types. Data are presented as a stacked, multi-band raster with one "band" for each year (Band 1 = 1986, Band 2 = 1987 and so on). Note that the year 2012 was left out of our time series because of lack of quality Landsat data. A color file (.clr) is included that can be imported to match the color of the National Land Cover Classification scheme. This data release also contains two JavaScript files with the Google Earth Engine code developed for pre-processing Landsat imagery and for image ...

Zip codes identified by the Arizona Department of Health Services to promote ownership of marijuana establishments in communities disproportionately affected by the enforcement of Arizona’s previous marijuana laws under Prop 207 (passed by Arizona voters in Nov. 2020).In December 2021, the Arizona Department of Health Services will issue 26 adult-use Marijuana Establishment licenses to applicants who qualify under the social equity ownership program. More information about the State of Arizona's Medical Marijuana Social Equity Ownership Program can be found here: https://azdhs.gov/licensing/marijuana/social-equity/index.php To see if you quality go to the map on this page: https://www.azdhs.gov/licensing/marijuana/social-equity/index.php#qualification The source data for this data layer was the Census 2020 Zip Code Tabulation Areas (ZCTAs). Zip codes for the Medical Marijuana Social Equity Ownership Program were selected by the Arizona Department of Health Services, which were then identified in the ZCTA 2020 GIS layer.

The USGS Protected Areas Database of the United States (PAD-US) is the nation's inventory of protected areas, including public open space and voluntarily provided, private protected areas, identified as an A-16 National Geospatial Data Asset in the Cadastral Theme (http://www.fgdc.gov/ngda-reports/NGDA_Datasets.html). PAD-US is an ongoing project with several published versions of a spatial database of areas dedicated to the preservation of biological diversity, and other natural, recreational or cultural uses, managed for these purposes through legal or other effective means. The geodatabase maps and describes public open space and other protected areas. Most areas are public lands owned in fee; however, long-term easements, leases, and agreements or administrative designations documented in agency management plans may be included. The PAD-US database strives to be a complete “best available” inventory of protected areas (lands and waters) including data provided by managing agencies and organizations. The dataset is built in collaboration with several partners and data providers (http://gapanalysis.usgs.gov/padus/stewards/). See Supplemental Information Section of this metadata record for more information on partnerships and links to major partner organizations. As this dataset is a compilation of many data sets; data completeness, accuracy, and scale may vary. Federal and state data are generally complete, while local government and private protected area coverage is about 50% complete, and depends on data management capacity in the state. For completeness estimates by state: http://www.protectedlands.net/partners. As the federal and state data are reasonably complete; focus is shifting to completing the inventory of local gov and voluntarily provided, private protected areas. The PAD-US geodatabase contains over twenty-five attributes and four feature classes to support data management, queries, web mapping services and analyses: Marine Protected Areas (MPA), Fee, Easements and Combined. The data contained in the MPA Feature class are provided directly by the National Oceanic and Atmospheric Administration (NOAA) Marine Protected Areas Center (MPA, http://marineprotectedareas.noaa.gov ) tracking the National Marine Protected Areas System. The Easements feature class contains data provided directly from the National Conservation Easement Database (NCED, http://conservationeasement.us ) The MPA and Easement feature classes contain some attributes unique to the sole source databases tracking them (e.g. Easement Holder Name from NCED, Protection Level from NOAA MPA Inventory). The "Combined" feature class integrates all fee, easement and MPA features as the best available national inventory of protected areas in the standard PAD-US framework. In addition to geographic boundaries, PAD-US describes the protection mechanism category (e.g. fee, easement, designation, other), owner and managing agency, designation type, unit name, area, public access and state name in a suite of standardized fields. An informative set of references (i.e. Aggregator Source, GIS Source, GIS Source Date) and "local" or source data fields provide a transparent link between standardized PAD-US fields and information from authoritative data sources. The areas in PAD-US are also assigned conservation measures that assess management intent to permanently protect biological diversity: the nationally relevant "GAP Status Code" and global "IUCN Category" standard. A wealth of attributes facilitates a wide variety of data analyses and creates a context for data to be used at local, regional, state, national and international scales. More information about specific updates and changes to this PAD-US version can be found in the Data Quality Information section of this metadata record as well as on the PAD-US website, http://gapanalysis.usgs.gov/padus/data/history/.) Due to the completeness and complexity of these data, it is highly recommended to review the Supplemental Information Section of the metadata record as well as the Data Use Constraints, to better understand data partnerships as well as see tips and ideas of appropriate uses of the data and how to parse out the data that you are looking for. For more information regarding the PAD-US dataset please visit, http://gapanalysis.usgs.gov/padus/. To find more data resources as well as view example analysis performed using PAD-US data visit, http://gapanalysis.usgs.gov/padus/resources/. The PAD-US dataset and data standard are compiled and maintained by the USGS Gap Analysis Program, http://gapanalysis.usgs.gov/ . For more information about data standards and how the data are aggregated please review the “Standards and Methods Manual for PAD-US,” http://gapanalysis.usgs.gov/padus/data/standards/ .

This dataset contains tree canopy cover layers as derived and calculated via a land cover classification for the City of Mesa using 2024 MAG Imagery. The land cover classification utilized a Support Vector Machine Classifier and was calculated for various areas including city boundary, census tracts, census blocks, council district, etc.This dataset also contains the point locations and attributes of trees maintained by the City of Mesa. The point dataset was obtained by WCA from WCA in September 2024. The attributes of interest to this study included unique TreeID, Exact DBH, DBH Range, Height Range, Botanical Name, Common Name, Latitude, and Longitude. Updates to the tree layer were made by joining the results from the September 2024 i-Tree report. An i-Tree Eco Analysis was run in September 2024 using i-Tree Eco v6.0.38 and the results were joined based on unique tree ID to the Mesa’s tree inventory. Attributes added were: Structural Value ($), Carbon Storage (lb), Carbon Storage ($), Gross Carbon Sequestration (lb/yr), Gross Carbon Sequestration ($/yr), Avoided Runoff (cubicFT/yr), Avoided Runoff ($/yr), Pollution Removal (oz/yr), Pollution Removal ($/yr), Total Annual Benefits ($/yr), Height (ft), Canopy Cover (sqft), Tree Condition, Leaf Area (sqft), Leaf Biomass (lb), Leaf Area Index Basal Area (sqft), Cond, i-Tree_ID_BotName, i-Tree_ID_ComName and i-Tree_ID Genus. The exact definitions, meanings, calculations, etc. for the i-Tree Values can be found on i-Tree’s website via the i-Tree Eco User Manual. For certain layers the individual i-Tree values were aggregated by census tract, census block, zip code, etc. These results can be seen in the polygon layers with the following attribute values: CanopyCoverPer_Final, COUNT_Tree_ID, SUM_Replacement_Value_, SUM_Carbon_Storage_lb_, SUM_Carbon_Storage_, SUM_Gross_Carbon_Sequestration_lb_, SUM_Gross_Carbon_Sequestration_y, SUM_Avoided_Runoff_ftÂ_yr_, SUM_Avoided_Runoff_yr_, SUM_Pollution_Removal_oz_yr_, SUM_Pollution_Removal_yr_, and SUM_Total_Annual_Benefits_yr_