Data Repository

Boundaries depicting service areas for APS and SRP. Produced by the Maricopa County Office of Enterprise Technology

Census block groups are clusters of blocks within the same census tract that have the same first digit of their 4-character census block number. Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and by non-visible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Generally, census blocks are small in area; for example, a block in a city. Census blocks in suburban and rural areas may be large, irregular and bounded by a variety of features, such as roads, streams, and/or transmission line rights-of-way. In remote areas, census blocks may encompass hundreds of square miles.

Polygon data about the year of construction of the buildings pertaining to zip codes in AZ with tabular data about each county and its boundaries.

Polygon data about the year of construction of the buildings in AZ with tabular data about each county and its boundaries.

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.

Municipal boundaries for cities in Arizona as of October 2016.

The 2018 TIGER/Line Shapefiles reflect available governmental unit boundaries of the counties and equivalent entities as of January 1, 2018.

A polygon layer of park boundaries maintained by a city or county in Arizona. The original data for the CAP service area came from Maricopa, Pinal and Pima counties. The original data was edited for location and content. Additional county and city park data was added outside of the CAP service area. Most data was obtained from the corresponding jurisdictional parks and recreation websites. The park boundaries were most often drawn to the parcel boundaries, however, at times, the boundaries were drawn based on an aerial photograph, generally from Bing or ESRI aerial layers.

A polygon layer of golf course boundaries. The original data came from Maricopa County. The original data was edited for location and content and golf courses for other counties were added based on ESRI and Bing aerials as well as individual county parcel spatial layers. Generally, the polygons follow parcel boundaries where appropriate. In other cases, the boundary was drawn based on the general tee box and greens for the course based on aerial photos. Some tabular data was obtained by web research from a number of various sites.

The purpose of these data is to provide a reasonably accurate depiction of who or what agency manages the surface of a given area of land.

The purpose of these data is to provide a reasonably accurate depiction of who or what agency manages the surface of a given area of land.

Location and supplemental information for open pharmacies that have been granted a permit from the Arizona State Board of Pharmacy.

Arizona PCAs reflect similarities in demographics and primary care services utilization patterns. They are a common geographic unit adopted by the Arizona Department for Health Services for health statistical analysis. A specific methodology process, rules and exceptions were developed to guide the creation of PCAs, which are built from 2010 US Census Tracts. All PCAs have a population greater than 10,000 but less than 200,000, have an area no greater than 7500 square miles, shall not cross county lines, and shall follow existing political boundaries whenever possible. If no political boundary exists, demographics (in urban areas) and proximity to safety net facilities and neighboring communities (in rural areas) are used to form a PCA. There are a couple exceptions to these rules. Tribal PCAs are exempt from population and area minimum and maximum rules, and can cross county lines. If the Census Designated Place (CDP) that defines a PCA crosses county lines and its population adds up to at least 10,000 but less than 150,000 then the resulting PCA can cross a county line.

This data set is a general reference for schools or "learning sites" on Arizona as of 2018. It represents schools from the AZ Department of Education, AZ School Facilities Board, private schools, some technical schools, colleges and universities.

This data set consists of the Arizona state boundary.

Tempe Campus Buildings shapefile

This data set represents point locations of cities and towns in Arizona. The data contains point locations for incorporated cities, Census Designated Places and populated places.

The Walkability Index dataset characterizes every Census 2010 block group in the U.S. based on its relative walkability. Walkability depends upon characteristics of the built environment that influence the likelihood of walking being used as a mode of travel. The Walkability Index is based on the EPA's previous data product, the Smart Location Database (SLD). Block group data from the SLD was the only input into the Walkability Index, and consisted of four variables from the SLD weighted in a formula to create the new Walkability Index. This dataset shares the SLD's block group boundary definitions from Census 2010.

This dataset provides locations and technical specifications of wind turbines in the United States, almost all of which are utility-scale. Utility-scale turbines are ones that generate power and feed it into the grid, supplying a utility with energy. They are usually much larger than turbines that would feed a homeowner or business.

Boundary shapefile of all the zip codes in the state of Arizona as of 2017.