topohpgn contains 2 foot contours derived from the 1998 PAG Regional Orthophoto project. It includes only those urbanized areas where DTM's are available. See more information.The Pima Association of Governments (PAG) and a number of local government jurisdictions participate in the Regional Orthophoto Project which started with this 1998 project and continues with updates every few years.The orthophoto projects for the various years are all different. Differences include methods, coverage areas, elevation modeling, resolution, and spectra (black and white or color).The 1998 project includes:1 foot resolution panchromatic (black and white) imagery of 581 (578??) sections of selected areas in eastern Pima County.1 meter resolution multispectral (color) imagery of 546 sections of selected areas in eastern Pima County.DEM elevation data for 240 sections of the project area.DTM elevation data for 369 sections of the project area.Contours for 341 sections of the project area.This layer is maintained by Pima County. Click here to visit Pima County's Open Data site. Click here to visit Pima County's GIS Library metadata. PurposeThis layer was developed to PAG's 1998 topography in Pima County, Arizona.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is not in any known applications.Known Errors No known errorsContactPima County - GISdata@pima.govUpdate FrequencyAs Needed

https://gis.pima.gov/data/contents/metadet.cfm?name=preserveValues for PropInterest field (pop-ups & file downloads): 1 = Agricultural Lease; 2 = Conservation Easement; 3 = Federal Lands; 4 = Fee Simple; 5 = Fee Simple w/ Reversionary Clause; 6 = Grazing Lease; 7 = Perpetual ROW; 8 = Restricted Covenant; 9 = Rezoning Condition; 10 = Section 7/10 Mitigation; 11 = State Lands; 12 = Use Agreement w/ BLMValues for RestrictType field (pop-ups & file downloads): 1 = MRC: Conservation Land; 2 = MRC: MSCP; 3 = RC; 4 = Conservation Easement; 5 = N/A

https://gis.pima.gov/data/contents/metadet.cfm?name=fp_ss***Download shapefile of this dataset here. (Normal download using button on Geospatial Data Portal item details page won't be successful.)***

The Hydrologic Soils Group Map was derived from the soil survey shape files obtained from Soils Datamart (https://sdmdataaccess.nrcs.usda.gov/) which were joined with an appropriate attribute table (derived from the component file ‘comp.txt’ and the mapping unit attribute file) which was distributed with the digital release of the soil surveys. See more information.This layer is maintained by Pima County. Click here to visit Pima County's Open Data site. Click here to visit Pima County's GIS Library metadata. PurposeThis layer was developed to show hydrologic soils groups in Pima County, Arizona.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is not in any known applications.Known Errors No known errorsContactPima County - GISdata@pima.govUpdate FrequencyAs Needed

Displays schools located in Pima County. Designated by school type: public, charter and private; and designated by school class: elementary, middle, high, and postsecondary. Created using Pima County School Superintendent's website (www.schools.pima.gov). Maintained by Pima County GIS. Click here to visit Pima County's Open Data site.PurposeThis layer was developed locate schools in Pima County, Arizona.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is not in any known applications.Known Errors New schools may be positioned using Orthophotos.ContactPima County - GISdata@pima.govUpdate FrequencyAs Needed

https://gis.pima.gov/data/contents/metadet.cfm?name=pcgprsbm***Note: overlapping data is present, and attention needs to be paid to dates on the instruments. Any questions should be addressed to transsyseim@pima.gov.***

FP_ZONEX shows areas of shallow 100-year floodplain (ZONE X - SHADED) with identified subclassifications for areas within unincorporated Pima County. Areas in this layer should have identical exterior boundaries to the area of ZONE X - SHADED polygons in the fp_dfirm layer.This layer is maintained by Pima County. Click here to visit Pima County's Open Data site. Click here to visit Pima County's GIS Library metadata. PurposeThis layer was developed to show FEMA Zone X Shaded Subzones in Pima County, Arizona.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is not in any known applications.Known Errors No known errorsContactPima County - GISdata@pima.govUpdate FrequencyAs Needed

Contains street linework, and boundary features for incorporated and other jurisdictions, schools, parks, fire stations, police stations, post offices, and points of interest.

https://gis.pima.gov/data/contents/metadet.cfm?name=pcgprrlm***Note: overlapping data is present, and attention needs to be paid to dates on the instruments. Any questions should be addressed to transsyseim@pima.gov.***

A paper copy of the Geologic Map of the Catalina Core Complex and San Pedro Trough (Dickinson, 1992) was scanned and digitized by U.S. Geological Survey staff and contractors at the Southwest Field Office (Tucson, AZ) in 2000-2001 for input into an ArcInfo geographic information system (GIS). The resulting geologic map database (in ArcInfo format) can be queried in many ways to produce a variety of geologic maps. Digital base map data files. (topography, roadways, towns, and hydrography) are not included: they may be obtained from a variety of commercial and government sources. Geologic map graphics and plot files that are provided in the Open-File Report are representations of the digital database and are not designed to be cartographic products.

FP_DFIRM shows areas in Pima County prone to 100-year and shallow 100-year flood events. ZONES A, AE, AH, AO # and AO - ALLUVIAL FAN # comprise the extent of the 100-year floodplain. The tailing numbers in the ZONE AO strings indicate flood depth in feet.ZONE D shows areas that have not been mapped by FEMA (primarily federal and tribal lands). Zone X shows areas that have been mapped but are outside of the 500-year floodplain.ZONE X -SHALLOW 100-YEAR shows the extent of the shallow 100-year floodplain, the 500 year floodplain and Areas protected by levee. The layer FP_ZONEX provides subclassifications for these areas.Note, FP_LOMX can be used to augment FP_DFIRM for large-scale mapping.Also note, FP_DFIRM should be used in conjunction with FP_SS for the floodprone land brochure mailings sent out by PCRFCD on an annual basis.For general FIRM information: See more information.This layer is maintained by Pima County. Click here to visit Pima County's Open Data site. Click here to visit Pima County's GIS Library metadata. PurposeThis layer was developed to show Flood Hazard Zones in Pima County, Arizona.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is not in any known applications.Known Errors A composite of FEMA maps with different scales and years.ContactPima County - GISdata@pima.govUpdate FrequencyAs Needed

Two foot interval contour lines created by CMG Drainage as part of the 2014 Green Valley Basin Management Study. Ground surface was derived from 2008 and 2011 PAG LiDAR. Known Errors/Qualifications: Topo elevations are +- 1 foot accuracy. Spatial Domain: Eastern Pima County Maintenance Format: Shape Primary Source Organization: CMG Drainage Primary Source Date: 20141101 Primary Source Format: DWG Secondary Source Organization: RFCD Secondary Source Contact: Kenneth Maits Secondary Source Format: Shape GIS Contact: Kenneth Maits, Two foot interval contour lines created by CMG Drainage as part of the 2014 Green Valley Basin Management Study. Ground surface was derived from 2008 and 2011 PAG LiDAR. Known Errors/Qualifications: Topo elevations are +- 1 foot accuracy. Spatial Domain: Eastern Pima County Library Input: Shape Std Primary Source Organization: CMG Drainage Primary Source Date: 20141101 Primary Source Format: DWG Secondary Source Organization: RFCD Secondary Source Contact: Kenneth Maits Secondary Source Format: Shape GIS Contact: Kenneth Maits

HIGHWAYS shows simplified linework (i.e., centerlines only that are dissolved on highway designation) for federal and state highways. Frontage roads, on- and off-ramps, etc., are excluded.HIGHWAYS has two primary uses:1) It is used for display on the "Major Streets and Scenic Routes Plan" map and MapGuide site, wherein these roads are considered de facto, or designated, scenic routes.2) It is used by the GIS Division's Special Projects Section in their basemap templates.For more information: https://gis.pima.gov/data/contents/metadet.cfm?name=highwaysPurposeDisplays the highways in Pima CountyDataset ClassificationLevel 0 - OpenKnown UsesLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactPima County GISUpdate FrequencyNot Maintained last update 2013

COMPLETED 2010. The data was converted from the most recent (2010) versions of the adopted plans, which can be found at https://cms3.tucsonaz.gov/planning/plans/Supplemental Information: In March 2010, Pima Association of Governments (PAG), in cooperation with the City of Tucson (City), initiated the Planned Land Use Data Conversion Project. This 9-month effort involved evaluating mapped land use designations and selected spatially explicit policies for nearly 50 of the City's adopted neighborhood, area, and subregional plans and converting the information into a Geographic Information System (GIS) format. Further documentation for this file can be obtained from the City of Tucson Planning and Development Services Department or Pima Association of Governments Technical Services. A brief summary report was provided, as requested, to the City of Tucson which highlights some of the key issues found during the conversion process (e.g., lack of mapping and terminology consistency among plans). The feature class "Plan_boundaries" represents the boundaries of the adopted plans. The feature class "Plan_mapped_land_use" represents the land use designations as they are mapped in the adopted plans. Some information was gathered that is implicit based on the land use designation or zones (see field descriptions below). Since this information is not explicitly stated in the plans, it should only be viewed by City staff for general planning purposes. The feature class "Plan_selected_policies" represents the spatially explicit policies that were fairly straightforward to map. Since these policies are not represented in adopted maps, this feature class should only be viewed by City staff for general planning purposes only.2010 - created by Jamison Brown, working as an independent contractor for Pima Association of Governments, created this file in 2010 by digitizing boundaries as depicted (i.e. for the mapped land use) or described in the plans (i.e. for the narrative policies). In most cases, this involved tracing based on parcel (paregion) or street center line (stnetall) feature classes. Snapping was used to provide line coincidence. For some map conversions, freehand sketches were drawn to mimick the freehand sketches in the adopted plan. Field descriptionsField descriptions for the "Plan_boundaries" feature class: Plan_Name: Plan name Plan_Type: Plan type (e.g., Neighborhood Plan) Plan_Num: Plan number ADOPT_DATE: Date of Plan adoption IMPORTANT: A disclaimer about the data as it is unofficial. URL: Uniform Resource Locator Field descriptions for the "Plan_mapped_land_use" feature class: Plan_Name: Plan name Plan_Type: Plan type (e.g., Neighborhood Plan) Plan_Num: Plan number LU_DES: Land use designation (e.g., Low density residential) LISTED_ALLOWABLE_ZONES: Allowable zones as listed in the Plan LISTED_RAC_MIN: Minimum residences per acre (if applicable), as listed in the Plan LISTED_RAC_TARGET: Target residences per acre (if applicable), as listed in the Plan LISTED_RAC_MAX: Maximum residences per acre (if applicable), as listed in the Plan LISTED_FAR_MIN: Minimum Floor Area Ratio (if applicable), as listed in the Plan LISTED_FAR_TARGET: Target Floor Area Ratio (if applicable), as listed in the Plan LISTED_FAR_MAX: Maximum Floor Area Ratio (if applicable), as listed in the Plan BUILDING_HEIGHT_MAX Building height maximum (ft.) if determined by Plan policy IMPORTANT: A disclaimer about the data as it is unofficial. URL: Uniform Resource Locator IMPLIED_ALLOWABLE_ZONES: Implied (not listed in the Plan) allowable zones IMPLIED_RAC_MIN: Implied (not listed in the Plan) minimum residences per acre (if applicable) IMPLIED_RAC_TARGET: Implied (not listed in the Plan) target residences per acre (if applicable) IMPLIED_RAC_MAX: Implied (not listed in the Plan) maximum residences per acre (if applicable) IMPLIED_FAR_MIN: Implied (not listed in the Plan) minimum Floor Area Ratio (if applicable) IMPLIED_FAR_TARGET: Implied (not listed in the Plan) target Floor Area Ratio (if applicable) IMPLIED_FAR_MAX: Implied (not listed in the Plan) maximum Floor Area Ratio (if applicable) IMPLIED_LU_CATEGORY: Implied (not listed in the Plan) general land use category. General categories used include residential, office, commercial, industrial, and other.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactJohn BeallCity of Tucson Development Services520-791-5550John.Beall@tucsonaz.govUpdate FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Fire Taxation Districts in Pima County.For more information, visit https://gis.pima.gov/data/contents/metadet.cfm?name=firedistPurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 – OpenKnown UsesLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Known ErrorsFire taxation districts do not necessarily coincide with fire service areas, e.g. areas that are serviced by the Rural/Metro Corporation are not included in this layer. The City of Tucson and the City of South Tucson do not have a separate fire taxation district and are not included. This layer does not include tribal fire districts. District boundaries may not be exact. Non-taxed Federal, State, or Pima County owned properties are excluded from the following fire district boundaries: Sonoita Elgin, Arivaca,and Helmet Peak. This layer does not get updated until Assesor's data gets updated with the annexation information.Data ContactPima CountyWilliam Gerdesgisdata@tucsonaz.govPublisher ContactInformation Technology DepartmentGIS_IT@tucsonaz.govUpdate FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

ADFACIL displays facilities-based addresses as derived from codes 1 through 6 in adr_pima, then overlaid with parcels to populate parcel-related attributes.Click here to visit Pima County's Open Data site.PurposeThis layer was developed to locate facility addresses in Pima County, Arizona.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is not in any known applications.Known Errors Facility addresses do not include all utility addresses as tracking started in 1998. Facility address points do not represent precise locations of facilities and are intended only to represent a general location within a particular parcel.ContactPima County - GISdata@pima.govUpdate FrequencyAs Needed

Status: COMPLETED 2010. The data was converted from the most recent (2010) versions of the adopted plans, which can be found at https://cms3.tucsonaz.gov/planning/plans/ Supplemental Information: In March 2010, Pima Association of Governments (PAG), in cooperation with the City of Tucson (City), initiated the Planned Land Use Data Conversion Project. This 9-month effort involved evaluating mapped land use designations and selected spatially explicit policies for nearly 50 of the City's adopted neighborhood, area, and subregional plans and converting the information into a Geographic Information System (GIS) format. Further documentation for this file can be obtained from the City of Tucson Planning and Development Services Department or Pima Association of Governments Technical Services. A brief summary report was provided, as requested, to the City of Tucson which highlights some of the key issues found during the conversion process (e.g., lack of mapping and terminology consistency among plans). The feature class "Plan_boundaries" represents the boundaries of the adopted plans. The feature class "Plan_mapped_land_use" represents the land use designations as they are mapped in the adopted plans. Some information was gathered that is implicit based on the land use designation or zones (see field descriptions below). Since this information is not explicitly stated in the plans, it should only be viewed by City staff for general planning purposes. The feature class "Plan_selected_policies" represents the spatially explicit policies that were fairly straightforward to map. Since these policies are not represented in adopted maps, this feature class should only be viewed by City staff for general planning purposes only. 2010 - created by Jamison Brown, working as an independent contractor for Pima Association of Governments, created this file in 2010 by digitizing boundaries as depicted (i.e. for the mapped land use) or described in the plans (i.e. for the narrative policies). In most cases, this involved tracing based on parcel (paregion) or street center line (stnetall) feature classes. Snapping was used to provide line coincidence. For some map conversions, freehand sketches were drawn to mimick the freehand sketches in the adopted plan. Field descriptions for the "Plan_mapped_land_use" feature class: Plan_Name: Plan name Plan_Type: Plan type (e.g., Neighborhood Plan) Plan_Num: Plan number LU_DES: Land use designation (e.g., Low density residential) LISTED_ALLOWABLE_ZONES: Allowable zones as listed in the Plan LISTED_RAC_MIN: Minimum residences per acre (if applicable), as listed in the Plan LISTED_RAC_TARGET: Target residences per acre (if applicable), as listed in the Plan LISTED_RAC_MAX: Maximum residences per acre (if applicable), as listed in the Plan LISTED_FAR_MIN: Minimum Floor Area Ratio (if applicable), as listed in the Plan LISTED_FAR_TARGET: Target Floor Area Ratio (if applicable), as listed in the Plan LISTED_FAR_MAX: Maximum Floor Area Ratio (if applicable), as listed in the Plan BUILDING_HEIGHT_MAX Building height maximum (ft.) if determined by Plan policy IMPORTANT: A disclaimer about the data as it is unofficial. URL: Uniform Resource Locator IMPLIED_ALLOWABLE_ZONES: Implied (not listed in the Plan) allowable zones IMPLIED_RAC_MIN: Implied (not listed in the Plan) minimum residences per acre (if applicable) IMPLIED_RAC_TARGET: Implied (not listed in the Plan) target residences per acre (if applicable) IMPLIED_RAC_MAX: Implied (not listed in the Plan) maximum residences per acre (if applicable) IMPLIED_FAR_MIN: Implied (not listed in the Plan) minimum Floor Area Ratio (if applicable) IMPLIED_FAR_TARGET: Implied (not listed in the Plan) target Floor Area Ratio (if applicable) IMPLIED_FAR_MAX: Implied (not listed in the Plan) maximum Floor Area Ratio (if applicable) IMPLIED_LU_CATEGORY: Implied (not listed in the Plan) general land use category. General categories used include residential, office, commercial, industrial, and other.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactJohn BeallCity of Tucson Development Services520-791-5550John.Beall@tucsonaz.govUpdate FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

COMPLETED 2010. The data was converted from the most recent (2010) versions of the adopted plans, which can be found at https://cms3.tucsonaz.gov/planning/plans/ Supplemental Information: In March 2010, Pima Association of Governments (PAG), in cooperation with the City of Tucson (City), initiated the Planned Land Use Data Conversion Project. This 9-month effort involved evaluating mapped land use designations and selected spatially explicit policies for nearly 50 of the City's adopted neighborhood, area, and subregional plans and converting the information into a Geographic Information System (GIS) format. Further documentation for this file can be obtained from the City of Tucson Planning and Development Services Department or Pima Association of Governments Technical Services. A brief summary report was provided, as requested, to the City of Tucson which highlights some of the key issues found during the conversion process (e.g., lack of mapping and terminology consistency among plans). The feature class "Plan_boundaries" represents the boundaries of the adopted plans. The feature class "Plan_mapped_land_use" represents the land use designations as they are mapped in the adopted plans. Some information was gathered that is implicit based on the land use designation or zones (see field descriptions below). Since this information is not explicitly stated in the plans, it should only be viewed by City staff for general planning purposes. The feature class "Plan_selected_policies" represents the spatially explicit policies that were fairly straightforward to map. Since these policies are not represented in adopted maps, this feature class should only be viewed by City staff for general planning purposes only. 2010 - created by Jamison Brown, working as an independent contractor for Pima Association of Governments, created this file in 2010 by digitizing boundaries as depicted (i.e. for the mapped land use) or described in the plans (i.e. for the narrative policies). In most cases, this involved tracing based on parcel (paregion) or street center line (stnetall) feature classes. Snapping was used to provide line coincidence. For some map conversions, freehand sketches were drawn to mimick the freehand sketches in the adopted plan. Field descriptions Field descriptions for the "Plan_boundaries" feature class: Plan_Name: Plan name Plan_Type: Plan type (e.g., Neighborhood Plan) Plan_Num: Plan number ADOPT_DATE: Date of Plan adoption IMPORTANT: A disclaimer about the data as it is unofficial. URL: Uniform Resource Locator Field descriptions for the "Plan_mapped_land_use" feature class: Plan_Name: Plan name Plan_Type: Plan type (e.g., Neighborhood Plan) Plan_Num: Plan number LU_DES: Land use designation (e.g., Low density residential) LISTED_ALLOWABLE_ZONES: Allowable zones as listed in the Plan LISTED_RAC_MIN: Minimum residences per acre (if applicable), as listed in the Plan LISTED_RAC_TARGET: Target residences per acre (if applicable), as listed in the Plan LISTED_RAC_MAX: Maximum residences per acre (if applicable), as listed in the Plan LISTED_FAR_MIN: Minimum Floor Area Ratio (if applicable), as listed in the Plan LISTED_FAR_TARGET: Target Floor Area Ratio (if applicable), as listed in the Plan LISTED_FAR_MAX: Maximum Floor Area Ratio (if applicable), as listed in the Plan BUILDING_HEIGHT_MAX Building height maximum (ft.) if determined by Plan policy IMPORTANT: A disclaimer about the data as it is unofficial. URL: Uniform Resource Locator IMPLIED_ALLOWABLE_ZONES: Implied (not listed in the Plan) allowable zones IMPLIED_RAC_MIN: Implied (not listed in the Plan) minimum residences per acre (if applicable) IMPLIED_RAC_TARGET: Implied (not listed in the Plan) target residences per acre (if applicable) IMPLIED_RAC_MAX: Implied (not listed in the Plan) maximum residences per acre (if applicable) IMPLIED_FAR_MIN: Implied (not listed in the Plan) minimum Floor Area Ratio (if applicable) IMPLIED_FAR_TARGET: Implied (not listed in the Plan) target Floor Area Ratio (if applicable) IMPLIED_FAR_MAX: Implied (not listed in the Plan) maximum Floor Area Ratio (if applicable) IMPLIED_LU_CATEGORY: Implied (not listed in the Plan) general land use category. General categories used include residential, office, commercial, industrial, and other.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is intended to be used in the City of Tucson's Open Data portal and not for regular use in ArcGIS Online, ArcGIS Enterprise or other web applications.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactJohn BeallCity of Tucson Development Services520-791-5550John.Beall@tucsonaz.govUpdate FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Status: COMPLETED 2010. The data was converted from the most recent (2010) versions of the adopted plans, which can be found at https://cms3.tucsonaz.gov/planning/plans/Supplemental Information: In March 2010, Pima Association of Governments (PAG), in cooperation with the City of Tucson (City), initiated the Planned Land Use Data Conversion Project. This 9-month effort involved evaluating mapped land use designations and selected spatially explicit policies for nearly 50 of the City's adopted neighborhood, area, and subregional plans and converting the information into a Geographic Information System (GIS) format. Further documentation for this file can be obtained from the City of Tucson Planning and Development Services Department or Pima Association of Governments Technical Services. A brief summary report was provided, as requested, to the City of Tucson which highlights some of the key issues found during the conversion process (e.g., lack of mapping and terminology consistency among plans). The feature class "Plan_boundaries" represents the boundaries of the adopted plans. The feature class "Plan_mapped_land_use" represents the land use designations as they are mapped in the adopted plans. Some information was gathered that is implicit based on the land use designation or zones (see field descriptions below). Since this information is not explicitly stated in the plans, it should only be viewed by City staff for general planning purposes. The feature class "Plan_selected_policies" represents the spatially explicit policies that were fairly straightforward to map. Since these policies are not represented in adopted maps, this feature class should only be viewed by City staff for general planning purposes only.2010 - created by Jamison Brown, working as an independent contractor for Pima Association of Governments, created this file in 2010 by digitizing boundaries as depicted (i.e. for the mapped land use) or described in the plans (i.e. for the narrative policies). In most cases, this involved tracing based on parcel (paregion) or street center line (stnetall) feature classes. Snapping was used to provide line coincidence. For some map conversions, freehand sketches were drawn to mimick the freehand sketches in the adopted plan.Field descriptions: Field descriptions for the "Plan_boundaries" feature class: Plan_Name: Plan name Plan_Type: Plan type (e.g., Neighborhood Plan) Plan_Num: Plan number ADOPT_DATE: Date of Plan adoption IMPORTANT: A disclaimer about the data as it is unofficial. URL: Uniform Resource Locator Field descriptions for the "Plan_mapped_land_use" feature class: Plan_Name: Plan name Plan_Type: Plan type (e.g., Neighborhood Plan) Plan_Num: Plan number LU_DES: Land use designation (e.g., Low density residential) LISTED_ALLOWABLE_ZONES: Allowable zones as listed in the Plan LISTED_RAC_MIN: Minimum residences per acre (if applicable), as listed in the Plan LISTED_RAC_TARGET: Target residences per acre (if applicable), as listed in the Plan LISTED_RAC_MAX: Maximum residences per acre (if applicable), as listed in the Plan LISTED_FAR_MIN: Minimum Floor Area Ratio (if applicable), as listed in the Plan LISTED_FAR_TARGET: Target Floor Area Ratio (if applicable), as listed in the Plan LISTED_FAR_MAX: Maximum Floor Area Ratio (if applicable), as listed in the Plan BUILDING_HEIGHT_MAX Building height maximum (ft.) if determined by Plan policy IMPORTANT: A disclaimer about the data as it is unofficial. URL: Uniform Resource Locator IMPLIED_ALLOWABLE_ZONES: Implied (not listed in the Plan) allowable zones IMPLIED_RAC_MIN: Implied (not listed in the Plan) minimum residences per acre (if applicable) IMPLIED_RAC_TARGET: Implied (not listed in the Plan) target residences per acre (if applicable) IMPLIED_RAC_MAX: Implied (not listed in the Plan) maximum residences per acre (if applicable) IMPLIED_FAR_MIN: Implied (not listed in the Plan) minimum Floor Area Ratio (if applicable) IMPLIED_FAR_TARGET: Implied (not listed in the Plan) target Floor Area Ratio (if applicable) IMPLIED_FAR_MAX: Implied (not listed in the Plan) maximum Floor Area Ratio (if applicable) IMPLIED_LU_CATEGORY: Implied (not listed in the Plan) general land use category. General categories used include residential, office, commercial, industrial, and other.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Update FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

description: The Soil Survey of Santa Cruz and Parts of Cochise and Pima Counties, Arizona, a product of the USDA Soil Conservation Service and the Forest Service in cooperation with the Arizona Agricultural Experiment Station, released in 1979, was created according to the site conditions in 1971, when soil scientists identified soils types on aerial photographs. The scale at which these maps were published is 1:20,000. These soil maps were automated for incorporation into the hydrologic modeling within a GIS. The aerial photos onto which the soils units were drawn had not been orthoganalized, and contained distortion. A total of 15 maps composed the study area. These maps were scanned into TIFF format using an 8-bit black and white drum scanner at 100 dpi. The images were imported into ERDAS IMAGINE and the white borders were removed through subset decollaring processes. Five CD-ROMs containing Digital Orthophoto Quarter Quads (DOQQs) were used to register and rectify the scanned soils maps. Polygonal data was then attributed according to the datasets.; abstract: The Soil Survey of Santa Cruz and Parts of Cochise and Pima Counties, Arizona, a product of the USDA Soil Conservation Service and the Forest Service in cooperation with the Arizona Agricultural Experiment Station, released in 1979, was created according to the site conditions in 1971, when soil scientists identified soils types on aerial photographs. The scale at which these maps were published is 1:20,000. These soil maps were automated for incorporation into the hydrologic modeling within a GIS. The aerial photos onto which the soils units were drawn had not been orthoganalized, and contained distortion. A total of 15 maps composed the study area. These maps were scanned into TIFF format using an 8-bit black and white drum scanner at 100 dpi. The images were imported into ERDAS IMAGINE and the white borders were removed through subset decollaring processes. Five CD-ROMs containing Digital Orthophoto Quarter Quads (DOQQs) were used to register and rectify the scanned soils maps. Polygonal data was then attributed according to the datasets.