The City of Phoenix (COP) zoning boundaries were digitized from a hard copy data set, by contract, in 1991. Since that time, updates to the data have been made on an ongoing basis as land is rezoned. The layer is digitized at a relatively small scale, from approximately 1:10 to 1:10,000. Changes are made when inconsistencies are found.Contact Information: zoning@phoenix.gov
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
City of Phoenix parcel boundaries and details are shown for use to provide the best readability when used with different basemaps or aerial photos. Not intended for surveying, legal or engineering purposes. For non-commercial purposes only! This data is updated monthly.
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.
Lakes inside Indian Bend Wash.. Visit https://dataone.org/datasets/knb-lter-cap.309.6 for complete metadata about this dataset.
The Neighborhood Services Department maintains a listing of neighborhood organizations so residents can get more involved in decisions affecting their neighborhoods. Through Neighborhood Notification, we can help identify and obtain contact information for neighborhoods, enabling us to provide information directly to neighborhood leaders and organizations.
ADHS inspects, certifies and licenses medical health care institutions and providers of medical services, child care centers, business hearing dispensers, and DUI and domestic violence treatment centers. Each month, an extract from the ADHS Division of Licensing SQL view is geocoded using ADHS's internal geocoder, and post-processed using a Python script to create feature classes by facility type. Tabular data is maintained by each respective bureau in the licensing division, while the GIS Team extracts the data and creates GIS layers and shares them publicly. ADHS Division of Licensing Mission Statement: To protect the health and safety of Arizonans by providing information, establishing standards, and licensing and regulating health and child care services. Last updated: February 2025Update Frequency: MonthlyData FAQs:Some records have “license_expiration” earlier than the “rundate” while the “OPERTION_STATUS” is “ACTIVE”, should we treat all records with “OPERATION_STATUS” of “ACTIVE” as open at the time the data is released? Answer: Yes - ACTIVE is all the current licenses. In 2019 there was a perpetual rule change that affected certain facilities so in lieu of an expiration date, we began tracking the annual fee due date in the "license_expiration" field. Per rule, these facilities can submit annual requirements up to 30 days after the fee due date (aka license expiration in the provider database) so we do expect some to be earlier than the run date. Is the FACID of the same facility maintained unique and same throughout all releases? If a facility is purchased by a different company or has it’s name changed, is the FACID changed? Answer: The FACID represents a licensed premise - in many cases the facility ID is maintained when purchased by a different owner but under federal rule, certain facilities may choose to have a new CMS certification number which would require a new FACID be issued for that premise. What’s the unit type of capacities for different categories? Answer: This varies - it can be child capacity, bed count, dialysis station, etc. For Group_Home_for_Individuals_with_a_Developmental_Disability and Residential_Facility, how to tell if the employer’s office is at the facility VS the employer’s office is somewhere else and employees are sent to those facilities? Also is there a way to tell if a facility only has part time workers (Like workers only need to be at the residential facility less than 8hr per day or less than 5 days a week )? Answer: This is not currently available on the public databaseThe data contains a 'COUNTY' field and a "N_County' field - which one should I use to filter results? Answer: N_County - this is the county that's assigned when a record is geocoded using the physical street address, vs one that is assigned manually during the licensing process.
Residential Completion data is provided to MAG by member agencies on a quarterly basis, then processed and geocoded by MAG staff. The Residential Completion database contains a record for every residential completion in Maricopa County from April 1, 1990 (1990 Census date) through December 31, 2002.
Geospatial data about Phoenix City Boundary. Export to CAD, GIS, PDF, CSV and access via API.
Geospatial data about Phoenix Zoning. Export to CAD, GIS, PDF, CSV and access via API.
The dataset is the result of applying parameters developed for the object-oriented classification of high resolution, true-color aerial photography (Walker and Briggs in press). The source image used is the true-color Landiscor aerial photography (3 m) collected over Phoenix in the spring of 1997.
Boundary of the groundwater plume data from Arizona Department of Environmental Quality (ADEQ). The plume is comprised of two Superfund sites: the West Van Buren WQARF Superfund site and the Motorola 52nd Street Superfund site. The area designated as the plume was created by the groundwater contamination from the two Superfund sites.
This dataset has been created to meet the needs of the research community of Arizona State University. Apart from purely vizualization purposes (i.e. displaying the data on various maps) it can potentially be used for spatial modeling. The data consist of engineering-quality contours, also known as isolines, created from the NED 10-meter Digital Elevation Model subset to the extent somewhat exceeding Cetral Arizona - Phoenix LTER. Contours ( lines connecting points of equal height above sea level) are drawn at 15 meter intervals with the base set at 145 m of elevation. Contours are an exact interpretation of the grid surface model and may sometimes appear blocky looking, may cross, appear to intersect, or form an unclosed branching line. All these are valid engineering-quality interpretations of the elevation surface that cartographers typically modify (smooth) for aesthetic purposes.
Cross sections as approved by the Federal Emergency management Agency (FEMA) for the Flood Insurance Rate Maps (FIRM)
The Rio Vista Village, meaning river view, is predominately undeveloped with the exception of the Anthem Commerce Park, Anthem Outlets and Anthem West, a single-family residential community. New River Wash and the lush Sonoran Desert landscape offer an abundant amount of open space and recreational possibilities throughout the village. The area is truly unique with panoramic views of the Black and Daisy Mountains, and wide expansion of the Sonoran Desert. A majority of the vacant land in the village is owned by the Arizona State Land Department. Interstate-17 serves as a major north-south transportation route for metro Phoenix, connecting the Valley to northern Arizona.More information about the character of the Rio Vista Village can be found here .
3 parks inside Indian Bend Wash.. Visit https://dataone.org/datasets/knb-lter-cap.312.5 for complete metadata about this dataset.
A map of all City of Phoenix Council Districts.
1:250000 scale Digital Elevation Model of Arizona. Digital Elevation Model (DEM) is the terminology adopted by the USGS to describe terrain elevation data sets in a digital raster form. The standard DEM consists of a regular array of elevations cast on a designated coordinate projection system. The DEM data are stored as a series of profiles in which the spacing of the elevations along and between each profile is in regular whole number intervals. The normal orientation of data is by columns and rows. Each column contains a series of elevations ordered from south to north with the order of the columns from west to east. The DEM is formatted as one ASCII header record (A-record), followed by a series of profile records (B-records) each of which include a short B-record header followed by a series of ASCII integer elevations per each profile. The last physical record of the DEM is an accuracy record (C-record). A 30-minute DEM (2- by 2-arc second data spacing) consists of four 15-by 15-minute DEM blocks. Two 30-minute DEM's provide the same coverage as a standard USGS 30- by 60-minute quadrangle. Saleable units are 30- by 30-minute blocks, that is, four 15- by 15-minute DEM's representing one half of a 1:100,000-scale map.
© mapservices@phoenix.gov
Profile baselines as approved by the Federal Emergency Management Agency (FEMA) for the Flood Insurance Rate Maps (FIRM)
The City of Phoenix (COP) zoning boundaries were digitized from a hard copy data set, by contract, in 1991. Since that time, updates to the data have been made on an ongoing basis as land is rezoned. The layer is digitized at a relatively small scale, from approximately 1:10 to 1:10,000. Changes are made when inconsistencies are found.Contact Information: zoning@phoenix.gov