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.)***

EXERCISE ONLYThis web map serves as the Public Information Map for Flood Hazards in Pima County, Arizona. It is compiled of three main layers:Enriched Special Flood Hazard Area layer from FEMA (http://landscape1.arcgis.com/arcgis/rest/services/USA_Flood_Risk/MapServer)Current Weather Conditions feed from ESRI (https://livefeeds.arcgis.com/arcgis/rest/services/LiveFeeds/NOAA_METAR_current_wind_speed_direction/MapServer)World Traffic from ESRI (https://traffic.arcgis.com/arcgis/rest/services/World/Traffic/MapServer)These layers allow for the public to have an understanding of both the flooding hazards, but also the traffic conditions associated with severe weather and flash flooding.

Zipped raster dataset of 2018 Land-Use-Land-Cover (named pima_landcover_noroads.zip)Download this zipped dataset here by clicking the download button at top right.https://gis.pima.gov/data/contents/metadet.cfm?name=lulc18

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=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.***

https://gis.pima.gov/data/contents/metadet.cfm?name=pcgpraqm***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.***

This dataset represents ZIP code boundaries in Pima County. ZIP codes are used by the USPS for mail delivery but are linear routes, not polygons. The ZIP code polygons in this dataset are approximations based on parcel boundaries and exclude unique ZIP codes (e.g., high-volume locations or PO boxes).

For more information, see Pima County's metadata here.

Purpose To display approximate areas of ZIP codes within Pima County for planning and geographical analysis.

Dataset Classification Level 0 – Open

Known Uses Supports planning, and demographic analysis.

Known Errors ZIP code polygons are approximations; USPS ZIP codes are based on mail carrier routes. Unique, military, and PO box ZIP codes are excluded.

Data Contact Steve Whitney Pima County GIS GISdata@pima.gov

Update Frequency As needed based on changes to ZIP code boundaries.

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.

fp_lomxb displays area boundaries in which the floodplain data has been revised by Letter Of Map Revision (LOMR).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 Floodplain Areas of Revision in Pima County, Arizona.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is not in any known applications.Known Errors Many of the revision area boundaries were digitized from paper copies or screen digitized using the FIRM panel as a reference.12/2013: While this layer is maintained as a Shapefile, the coverage format is still required for certain nightly processing. See Steve Whitney. - FEMA floodplain data extraction processContactPima County - GISdata@pima.govUpdate FrequencyAs Needed

Status: NOT MAINTAINEDContact: GIS_IT, City of Tucson Information Technology GIS Services, 520-791-4747, GIS_IT@tucsonaz.govIntended Use: For map display and provides finer level of detail than Pima County GIS library data layer WASHES.Supplemental Information: DATA QUALITY IS QUESTIONABLE because it has not been regularly maintained. Per Frank Sousa (Winter 2009), he would prefer to call this layer "drainage network" because it includes streets flow which may not be considered a watercourse. Started in 1999 it covered the municipal planning area, done in pieces startings with the core of the City. Was densified to make sure there was a line where there was 100 cfs flow or more for regulatory purposes. Streets flow mapping is incomplete. 7/10/2010 - loaded shapefile into EDITSDE geodatabase from Stormwater shapes folder. circa 1999 - Shapefile create by Frank Sousa in City of Tucson Stormwater from aerial photos, topography and ground knowledge. Additional edits done by Frank Sousa.

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.

Status: UPDATED occasionally using ArcMap Contact: Michael Liberti, Tucson Water, 520-837-2226, Michael.Liberti@tucsonaz.gov Intended Use: Primary data record of service area boundaries. Not intended for map display unless approved by data owner. Known errors/qualifications This is a rough approximation of the obligated areas served by Tucson Water and some errors may exist especially in those areas outside the City of Tucson limits. Does not include the non-potable service area boundaries. The non-potable water system includes all water types that have not been treated to potable standards: reclaimed water lines, raw CAP mains from the canal, secondary effluent piped from the County treatment plant to the Roger Road reclaimed plan, TARP water in the mains between the recovery wells and the treatment plant and the CAVSARP recovery wellfields. Boundaries may overlap other water company service area boundaries because their definition of the boundaries may vary.***SERVED = The parcel has a TW water meter and is consuming water.***OBLIGATED = Either 1) a vacant parcel inside the City of Tucson that does not have a TW meter, or 2) a vacant/abandoned parcel that has a meter, but is not consuming water. ***COMMITTED = a parcel outside the City of Tucson that 1) is in an area of intergovernmental contractual agreement (e.g. Dove Mountain/Continental Ranch...) 2) is a master planned development for which TW previously granted a service agreement (will have a corresponding GREENLINE feature) 3) is under 20 acres and is located adjacent to a delivery pipe and is served on three sides 4) a Tucson Unified School District parcel ***NOT OBLIGATED = Call Tucson Water Development Services for clarification. ALSO NOTE THAT PIPELINE RIGHT-OF-WAYS OUTSIDE TUCSON ARE ALSO COMMITTED (NO PARCEL) So, a parcel can be committed by contract, by prior approval or by location Individuals that live outside Tucson who are not currently served by TW fall under #3. Unless directed otherwise by Tucson Water, by default any parcel outside the City of Tucson that does not have a Tucson Water meter will NOT be served unless they annex. Replaces ObligatedServiceArea feature class formerly maintained in VMDB. The name ObligatedServiceArea is still used, but now is just a filtered view of ServiceArea. September 2010 - loaded ServiceArea shapefile into EDITSDE geodatabase to be maintained as feature class instead of shapefile. Renamed to ServiceArea. ObligatedServiceArea becomes a view of the ServiceArea feature class. sdetable -o create_view -T OBLIGATEDSERVICEAREA -t SERVICEAREA -w "SA_TYPE in ('SERVED','OBLIGATED','COMMITTED')" -c "OBJECTID,SHAPE,SA_TYPE,SA_SUBTYPE,REC_DATE,INSTALLYEAR" -i sde:sqlserver:pw-sql2005 -D editsdeAugust 2010 - ObligatedServiceArea criteria is redefined based on decisions by Mayor and Council. New shapefile called ServiceArea becomes the data of record.10/10/2008 Bryn Enright Copy of most recent Obligated Service Area provided to John Regan from Pima County to post in the GIS Library and MapGuide site.10/10/2008 Bryn Enright Renamed the feature class from admin.ObligatedServiceArea to admin.ObligatedServiceAreaHistory. The most current area will be made available in a new database view called admin.ObligatedServiceArea.10/10/2008 Bryn Enright "Appended the most recent obligated service area created by Michael Liberti which was created by:1. Dissolving the current service area (req_SA_current.shp) with committed areas outside the city (dove mtn, larry's marana, diamond bell, corona de tucson...)2. Erased the city polygon (LIMJURIS) from the dissolve.3. Added the entire city polygon back in (i.e. obligated area) but then erased all of the ""water providers"" with CCNs ('56' water right)." In = req_SA_obligated.shp Out = ADMIN.ObligatedServiceAreaJune 2008 Bryn Enright Shapefile imported into Geodatabase (EMAPDB) In = Req_ServiceArea_v1.shp Out = ObligatedServiceAreaJune 2008 Michael Liberti Layer dissolved to show only 1 polygon for obligated area. In = ServiceArea_v1.shp Out = Req_ServiceArea_v1.shpJune 2008 Michael Liberti Layer updated with new services and existing remote services that were not previously included.February 2008 Michael Liberti Layer updated with new services for the 2008 Update to the Water Plan 2000-2050November 2004 Michael Liberti "Modified PCLIS WATERCOS as collection of PARCELS intersecting SERVICES by M Liberti. Layer created for use in the Water Plan 2000-2050" In=PCLIS WATERCOS Out=ServiceArea_v1.shp Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet consectetur adipiscing elit. Massa enim nec dui nunc. Quis commodo odio aenean sed adipiscing diam donec adipiscing. Nulla pellentesque dignissim enim sit amet venenatis urna. Sit amet volutpat consequat mauris nunc congue nisi vitae. Fames ac turpis egestas maecenas pharetra convallis posuere morbi leo. Morbi tristique senectus et netus et malesuada fames ac turpis. Eget lorem dolor sed viverra ipsum nunc. Id ornare arcu odio ut sem. Morbi leo urna molestie at elementum eu. In metus vulputate eu scelerisque. Lobortis mattis aliquam faucibus purus in massa tempor nec feugiat. Ut sem viverra aliquet eget sit amet tellus cras adipiscing. Lobortis mattis aliquam faucibus purus in massa tempor. Donec massa sapien faucibus et molestie ac feugiat. Et odio pellentesque diam volutpat commodo sed egestas egestas. Pharetra magna ac placerat vestibulum lectus. Fermentum leo vel orci porta non pulvinar neque laoreet suspendissePurposeLorem 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.

This topographic map is designed to be used as a basemap and a reference map. The map has been compiled by Esri and the ArcGIS user community from a variety of best available sources. The map is intended to support the ArcGIS Online basemap gallery. For more details on the map, please visit the World Topographic Map service description.

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 ContactJohn BeallCity of Tucson Development Services 520-791-5550John.Beall@tucsonaz.govUpdate FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

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

pcgpraqM is one of several Pima County Government Property Rights (PCGPR) layers. pcgpraqM displays Pima County Acquired Property Rights data, which include property, various easements, and other miscellaneous conveyances. The areas in question were either acquired by recorded deed or lease. Polygon features and attributes are based on recorded instruments. A nightly batch process appends all section shapefiles to create pcgpracq. The shape pcgpracq is further processed to join all area (polygon) values to related sql table attributes. If a duplicate/triplicate exists the polygon makes a copy of itself.The maintenance of this layer is handled by Pima County. For more detailed information, please refer to the original metadata, found here. PurposeShows information about property rights in Pima County.Dataset ClassificationLevel 0 - OpenKnown UsesUsed in the HP Dashboard Map.Known ErrorsThis layer has overlapping polygons that are not represented in the coverage format. Do not use a coverage format version of this layer. This layer is built from acquisition section drawings and related information stored in sql tables. This layer represents all document and/or classcode records related to an acquisition area (polygon). If an area (polygon) references more than one document and/or classcode, it creates a duplicate of itself and references the additional data. In that way all data is represented in the shapefile. In addition, the areas (polygons) are dissolved on common document data information. If a right of way area (polygon) was split during initial data entry along a section line, it is no longer represented by multiple polygons; the pieces are dissolved into one common area (polygon). As a result of the dissolve any BB_NO (unique identifier of the polygon disappears). In some cases, Pima County owned road Rights-Of-Way (ROW) do not encompass the entire portion of the overall road ROW.Data ContactPima County Information Technology Department - Geographic Information Systems201 N Stone Ave., 9th FloorTucson, AZ 85701GISDdata@pima.govUpdate FrequencyThe update of this layer is handled by Pima County. The last known update was 2014 but that date may not be accurate.

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

fp_bfe displays the flood hazard elevation contours that indicate the water surface elevation resulting from a flood that has a 1% chance of equaling or exceeding that level in any given year (100-year flood). 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 base flood elevation 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

This is a Pima County GIS dataset that has been trimmed to the extent of the Altar Valley Conservation Alliance AOI by means of a "clip" using the AVCA_boundary_2017 dataset as the extent feature. The following is the metadata provided by Pima County: "clsadopt displays the Conservation Lands System Priority Biological Resource categories of the Sonoran Desert Conservation Plan, providing conservation guidelines as adopted in the environmental element of the Comprehensive Plan. Known Errors/Qualifications: Clsadopt is based on a series of 55 species habitat models and Priority Conservation Areas developed by biologists. Original polygons were dissolved on DESC field. Cls_sci & cls_spp are used as overlays. Spatial Domain: Pima County Rectified: source map Maintenance Organization: PC ITD GIS Maintenance Description: Recon contacts John Regan with infrequent changes. Maintenance Frequency: Varies Maintenance Format: Shape Primary Source Organization: Recon Primary Source Contact: Leslie Smith Primary Source Document: res_120601 Primary Source Date: 200112 Primary Source Scale: 24000 Primary Source Format: Coverage GIS Contact: John Regan MapGuide Layer Name: CLS Categories MapGuide Scale Range: 0 - 400000"

A map created from year 2000 census data provided by Pima County GIS displaying median property values by census tract. This map was created as a base for Webapp production as part of GIST603B Lab 4.