The Maricopa County Assessor static parcel maps are made available as zipped PDF files. Map IDs are broken down as Township & Range - Section - Quarter Section - Quarter Quarter. For example 807-18-04-00 would be: 807 -- Township 3 North, Range 4 East 18 -- Section 18 04 -- The SouthEast Quarter 00 -- There are no separate quarter quarter maps. MapIDs are only generated where parcels exist with Maricopa County. Last update of a MapID is indicated by the BEGIN_DATE field.

Assessor Book Boundaries are the aggregated boundaries of the first three digits of an Assessor Parcel Number (APN).

The Year 2000 Land Use coverage was created as a joint effort of MAG and MAG member agency staff. Land Use components were classified into 46 categories. The Year 2000 Land Use coverage is used for a variety of planning purposes including socioeconomic forecasting and air quality modeling.

REQUIRED: A brief narrative summary of the data set.

Recorded subdivision boundaries for Maricopa County. Includes the Maricopa County Recorder (MCR) number and subdivision name.

SOURCE

This data was obtained from the Maricopa County Assessor under the search "Fast Food". The query has approximately 1342 results, with only 1000 returned due MCA Data Policies.

DATA CLEANING

Due to some Subdivision Name values posessing unescaped commas that interfered with Pandas' ability to properly align the columns, some manual cleaning in Libre Office was performed by me.

Aside from a handful of Null values, the data is fairly clean and requires little from Pandas.

NULL VALUES

Here are the sums and percentage of NULLS in the dataframe. Interestingly, there are 17 NULLS that do not have any physical addresses. This amounts to 1.7% of values for the Address, City, and Zip, and are all corresponding rows for those missing values.

I have looked into a couple of these on the Maricopa County Assessor's GIS Portal, and they do not appear to have any assigned physical addresses. This is a good avenue of exploration for EDA. Possibly an error that could be corrected, or some obscure legal reason, but interesting nonetheless.

Additionally, there are 391 NULLS in Subdivision Name accounting for 39.1%. This is a feature that I am interested in exploring to determine if there are any predominant groups. It could also generate a list of Entities that can be searched later to see if the dataset can be enriched beyond it's initial 1,000 record limit.

There are 348 NULLS in the MCR column. This is the definition according to the MCA Glossary

MCR (MARICOPA COUNTY RECORDER NUMBER)
Often associated with recorded plat maps.

This seems to be an uninteresting nominal value, so I will drop this columns.

While Property Type and Rental have no NULLS, 100% of those values are Fast Food Restaurant and N (for No), and therefore offer no useful information, and will be dropped.

I will leave the S/T/R column, although it also seems to be uninteresting nominal values, I am curious if there are predominent groups, and since it also has no NULLS, might be useful for further data enrichment.

Parcels are identified by an Assessor's Parcel Number (APN) consisting of a three digit Book number, a two digit Map number, a three digit Item number, possibly a Split letter. This dataset contains all active parcels within the area encompassed by Book Series 100. State and Federal lands are not represented. Vertical parcels are annotated using the Floor field.

The 1995 Land Use coverage was created as a joint effort of MAG (Maricopa Association of Governments) and MAG member agency staff. Land Use components were classified into 24 categories. The 1995 Land Use coverage is used for a variety of planning purposes including socioeconomic forecasting and air quality modeling.

The City of Tempe ZIP Codes feature class is from Maricopa County GIS Open Data and is intended to show the USPS ZIP Code boundaries within Tempe, Arizona.

The centerlines feature class is intended to show current and future street centerlines in Maricopa County, Arizona.

Parcels are identified by an Assessor's Parcel Number (APN) consisting of a three digit Book number, a two digit Map number, a three digit Item number, possibly a Split letter. This dataset contains all active parcels within the area encompassed by Book Series 500. State and Federal lands are not represented. Vertical parcels are annotated using the Floor field.

This is the digitized version of a map of the Hohokam canal system in what is now the Phoenix metropolitan area. It is based on the thesis research by J. B. Howard "Paleohydraulics: Techniques for modeling the operation and growth of prehistoric canal systems"

The cities annex feature class is intended to track city and town annexations in Maricopa County, Arizona.

This dataset contains the Maricopa County, Arizona City Council District boundaries for those cities with council districts. This includes Phoenix, Surprise, Buckeye, Peoria, Glendale and Mesa.

Cumulation of the weekly release of COVID-19 data for Maricopa County by City, Zip Code, ESD, HSD, and USD. Includes PCR Test Percent Positivity and COVID Case Rate per 100k population 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.

The Fire District boundaries in Maricopa County, Arizona show the response areas for parcels of land which are not protected by a local town or city for fire or medical emergencies.

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.

This web map is part of SDGs Today. Please see sdgstoday.orgInformation on the amount of water flowing in streams and rivers is critical to the management of water resources, emergency response to flooding, fisheries management, and many other uses. This layer provides access to near real-time stream gauge readings compiled from a variety of agencies and organizations. The Live Stream Gauges layer contains near real-time measurements of water depth from multiple reporting agencies recording at sensors across the world. This layer updates every hour. Flow forecasts are provided where available. These sensor feeds are owned and maintained by the GIS community via the Community Maps Program. For details on the coverage in this map and to find out how to contribute your organization's gauges, please email environment@esri.com. Contributors to the Live Stream Gauges Service:United States Geological Survey (USA)National Weather Service (USA) Washington State Department of Ecology (USA)San Joaquin County (USA)Maricopa County Flood Control District (USA)Minnesota Department of Natural Resources (USA)PEGELONLINE (Germany)Bureau of Meteorology (Australia)Horizons Regional Council (New Zealand) Environment Agency (UK)Nebraska Department of Natural Resources (USA)Iowa Flood Center (USA)Oregon Water Resource Department (USA)Dartmouth Flood Observatory (Global)Meteorological Service of Canada (Canada)Volusia County Florida (USA)Somali Water and Land Information Management (Somalia)

Information on the amount of water flowing in streams and rivers is critical to the management of water resources, emergency response to flooding, fisheries management, and many other uses. This layer provides access to near real-time stream gauge readings compiled from a variety of agencies and organizations.Dataset SummaryThe Live Stream Gauges layer contains near real-time measurements of water depth from multiple reporting agencies recording at sensors across the world. This layer updates every hour. Flow forecasts are provided where available. These sensor feeds are owned and maintained by the GIS community via the Community Maps Program. For details on the coverage in this map and to find out how to contribute your organization's gauges, please email environment@esri.com.Contributors to the Live Stream Gauges Service:United States Geological Survey (USA)National Weather Service (USA) * Includes Stage Status * Includes Flood Forecast Status *Washington State Department of Ecology (USA)San Joaquin County (USA)Maricopa County Flood Control District (USA)Minnesota Department of Natural Resources (USA)PEGELONLINE (Germany) * Includes Stage Status *Bureau of Meteorology (Australia)Horizons Regional Council (New Zealand) Environment Agency (UK)Nebraska Department of Natural Resources (USA) * Includes Stage Status *Iowa Flood Center (USA)Oregon Water Resource Department (USA)Dartmouth Flood Observatory (Global) * Includes Stage Status * Suspended *Meteorological Service of Canada (Canada)Volusia County Florida (USA) * Suspended *Somali Water and Land Information Management (Somalia) * Includes Stage Status *Office of Public Works (Ireland)RevisionsApr 15, 2025: Added fields for Flood Forecast Status for Full, 24 Hour, 48 Hour, and 72 Hour Forecast PeriodsFeb 13, 2024: Dartmouth Flood Observatory, suspended by government cutbacksDec 13, 2024: Added 'Status Classification' field, allowing symbol level draw order based on severity of flood status!Aug 26, 2024: Corrected update issue with USGS source data reported by several users.Aug 14, 2024: Updated USGS feed to pull from JSON data source, see: https://waterservices.usgs.gov/Jul 24, 2024: Added Office of Public Works (Ireland) dataJul 10, 2024: National Weather Service (NOAA) source reinstated after provider fix!Jul 8, 2024: Volusia County Florida, suspended during administrative holdJul 5, 2024: National Weather Service (NOAA) source stopped updating, suspended waiting on provider to correctMay 28, 2024: National Weather Service (NOAA) source updated, replaced retired AHPS with NWPSJan 22, 2024: Reinstated Somali Water and Land Management source after they successfully migrated to HTTPS ProtocolJan 3, 2024: Somali Water and Land Management source deactivated until Web Site issues are resolved!Mar 20, 2023: Nebraska DNR has been updated to leverage new source and now honors Stage Status!Feb 16, 2023: Nebraska DNR source update temporarily disabled due to source repository change!Aug 10, 2021: Added missing source for Nova Scotia CanadaJul 3, 2021: Added Somali Water and Land Information Management dataJun 30, 2021: Added Volusia County dataFeb 9, 2021: Refinements and Fixes:Corrections to Flow conversion for 'Environment Agency - UK'Corrections to Flow conversion for 'Horizons Regional Council - New Zealand'Added display of Metric Stage Height and Flow to PopupJan 27, 2021: Official release of Feature Service offering. Upgrades include:Automatic addition of new source stationsRemoval of stations with data older than 180 daysAddition of 'Governing Location' field that provides geographic State or Province (optional) plus Country NameAddition of 'Hours Since Last Update' field that maintains the age since gauge data was last updated

Plan submitted by: redistrictadmin on 10/15/2021 USER DESCRIPTION: In this version based off the newly adopted LD Test Map Version 2.0, Flagstaff is moved from District 7 to District 6 in its entirety only as a demonstration. District 7 also has moved east to Highway 191, including Springerville, Eager and St. John’s. Including Yavapai County in District 7 as well as all eastern parts currently included in the district not meeting the allowable population deviation; without Yavapai it is 113,000 short of target. The only option to rectify population is to include in District 7: Maricopa, or Gila and Pinal. In this version, Flagstaff cannot be kept whole in a single district and allow us to achieve the population balancing that is needed. For more information on the methodology used to create these boundaries, please visit: https://redistricting-irc-az.hub.arcgis.com/pages/draft-maps USER PLAN OBJECTIVE: N/A