Facebook
TwitterThe 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.
Facebook
TwitterThe 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.
Facebook
TwitterAssessor Book Boundaries are the aggregated boundaries of the first three digits of an Assessor Parcel Number (APN).
Facebook
TwitterThe TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, stairways, and winter trails.
Facebook
Twitterhttps://creativecommons.org/publicdomain/zero/1.0/https://creativecommons.org/publicdomain/zero/1.0/
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.
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.
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.
Facebook
TwitterRecorded subdivision boundaries for Maricopa County. Includes the Maricopa County Recorder (MCR) number and subdivision name.
Facebook
TwitterREQUIRED: A brief narrative summary of the data set.
Facebook
TwitterParcels 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 Maricopa County. State and Federal lands are not represented. Vertical parcels are annotated using the Floor field.
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
This dataset contain the parcels from the Maricopa County Assessor's office. The area covered is in Maricopa County (Phoenix metro area), Arizona. Major cities include Phoenix, Scottsdale, Mesa and Tempe. Various types of property usage are depicted in this layer. The most common are residential, commercial, industrial and agricultural properties. Multiple sources were used to collect the information including but not limited to CAD packages, aerial photography, and digitizing from paper maps. Adjustments are made where necessary in the process of updating and some parcel lines are only approximate. In cases where a line adjustment might create a loss of landsize it is typically taken out from the right of way to minimize the loss of landsize in the property. The line symbology for different property lines are not available in this dataset. In addition to standard fields the data has unique assessor parcel number for identification, basic temporal information and the location of property.
Facebook
TwitterCross sections as approved by the Federal Emergency management Agency (FEMA) for the Flood Insurance Rate Maps (FIRM)
Facebook
TwitterProfile baselines as approved by the Federal Emergency Management Agency (FEMA) for the Flood Insurance Rate Maps (FIRM)
Facebook
TwitterThis 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"
Facebook
TwitterWater surface elevations of the base flood as approved by the Federal mergency management Agency (FEMA) for the Flood Insurance Rate Maps (FIRM). The base flood elevation, in feet, is in relation to the National Geodetic Vertical Datum of 1929. Profile baselines are for the Flood Insurance Rate Maps (FIRM). The cross section data are used for the production of Flood Insurance Rate Maps. The Flood Insurance Rate Maps (FIRMs) show different floodplains with different zone designations. These are primarily for insurance rating purposes, but the zone differentiation can be very helpful for other floodplain management purposes. The differentiated floodplain zones are used for the production of Flood Insurance Rate Maps. Maricopa County has been subdivided into FIRM panels for the publication and distribution of FIRMs. Profile baselines are for the Flood Insurance Rate Maps (FIRM).
Facebook
TwitterThis map depicts existing and future land use conditions for Maricopa County, Arizona. The Existing Land Use data are derived from Maricopa County Assessor parcels, public land data from Arizona State Land Department, and numerous other sources.
Facebook
TwitterFloodplain zones as approved by the Federal Emergency Management Agency (FEMA) for the Flood Insurance Rate Maps (FIRM). Differentiated according to the FEMA letter coding scheme.
Facebook
TwitterParcels 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 400. State and Federal lands are not represented. Vertical parcels are annotated using the Floor field.
Facebook
TwitterThe 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.
Facebook
TwitterParcels 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.
Facebook
TwitterParcels 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 200. State and Federal lands are not represented. Vertical parcels are annotated using the Floor field.
Facebook
TwitterParcels 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 400. State and Federal lands are not represented. Vertical parcels are annotated using the Floor field.
Facebook
TwitterThe 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.