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.

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.

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: 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.

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

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.

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

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.

paregion displays all tax parcels, common areas, and private roadway parcels in Pima County. Known Errors/Qualifications: Parcels are derived from the Pima County Parcel Fabric. A relatively small number of parcels have more than one polygon per parcel, which are displayed as multi-part polygons with a total area for all polygon parts. Subdivision common areas are typical example of where you will find multi-part polygons. Roadway areas that are not assigned a tax code by the Assessor are "True Void" areas, having no polygon or attributes. These include a major portion of county street areas. However, private street areas will have assigned tax codes, attributes, and polygonal shape. The ADDRESS_OL field contains the situs address. ADDRESS_OL only includes situs addresses that have a one-parcel to one-situs address relationship as indicated by an ADR_STATUS field value of "ONE". ADRRESS_OL values that are null or blank mean that the parcel has either no situs address or multiple situs addresses as indicated by ADR_STATUS field values of "NONE" or "MULTIPLE" respectively. The MAIL1 through MAIL5 fields contain the owner name and mailing address. The Full Cash Initial Amount Value, and the Limited Net Assessed (Taxable) Value are displayed for analysis and are not reflective of the Market Value.

Parcel ownership attributes are only appended after validity is audited by the Assessor’s. This may happen some time after the new parcel line work is added. Ownership attributes includes MAIL1-MAIL5, LEGAL1-LEGAL5, both SEQ_NUM fields, LOT, RECORDDATE, and Value fields. If the parcel has not yet been audited, these fields will display Null or NA Lineage: The Parcel Fabric was created using the CAD parcel base drawings, which were migrated to a Parcel Fabric feature dataset on 2/28/2018 using the ESRI local Government Data Model format. Paregion tax parcel are now maintained in the Parcel Fabric. ADR_STATUS field was added on 3/5/2019 to help identify the type of situs address field ADDRESS_OL. Spatial Domain: Pima County Rectified: parcel Maintenance Organization: PC ITD GIS Maintenance Description: The "Paregion Assembly" process runs every night. Parcel Type 7 are selected from the Parcel Fabric and then through a series overlay processes geospatial attributes are added. Then Assessor attributes are added using a parcel ID join with AsrData and Tax Assembly tables. Maintenance Frequency: Daily Library Input: GDB Spec Primary Source Organization: PC ITD GIS Primary Source Contact: Jack Avis Primary Source Document: Parcel Fabric Features Primary Source Date: 20180711 Primary Source Scale: 200.0 Primary Source Format: Geodatabase Secondary Source Organization: Pima County Assessor Secondary Source Document: Assessor databases - AsrData and Tax Assembly Secondary Source Format: Database GIS Contact: Jack Avis

MapGuide Layer Name: Parcels - Pima MapGuide Scale Range: 0 - 25000

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

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

pa_ncode displays non-taxcoded polygons as extracted from the GIS parcel Section coverages. It also contains attributes for the jurisdiction in which the non-taxcoded polygons fall within. The maintenance of this layer is handled by Pima County. For more detailed information, please refer to the original metadata, found here.Purposepa_ncode displays historical non-taxcoded polygons as unofficial rights-of-way and drainage way features.Dataset ClassificationLevel 0 - OpenKnown UsesUsed in HP Dashboard.Known Errorspa_ncode polygons are extracted from the GIS parcel Section coverages by selecting for parcel taxcode equal to "999999991", "999999993", "999999994", or "999999999", which are the codes used to indicate a non-taxcoded areas, as researched from Assessor's Record Maps. You must select taxcodes not equal to null to filter out island polygons.Data ContactPima County Information Technology Department - Geographic Information Systems201 N Stone Ave., 9th FloorTucson, AZ 85701GISDdata@pima.govUpdate FrequencyNot Maintained but efforts are made to ensure that the dataset remains current and accurate.

trs displays the smallest unit in the Public Land Survey System; Township/Ranges are subdivided into 36 Sections; each Section is approximately one square mile. The coverage format includes a tr (Township) region subclass.

This layer has been adjusted to Section corner data from the GIS parcel Section AutoCAD drawings. It also includes the half Township South of 12S14E Sections 31-34, designated as 12F14E (field TR).

-

Known Errors/Qualifications: The Canoa Land Grant area is not part of the Public Land Survey System. The trs layer includes sections in the Canoa Land Grant area as if it had been included in the survey. Lineage: The TRS layer for Pima County was extracted from a state-wide layer of PLSS Section boundaries as received from ALRIS. The ALRIS layer was tablet digitized from USGS 7.5 minute topographic quadrangle paper maps. In 1992, a database of Section corner locations was acquired from ADOT, and the TRS layer was adjusted to match those ADOT Section corners that were surveyed to an acceptable level. In 2010, the Section boundaries were adjusted to Section corner locations from the GIS parcel AutoCAD drawings. Spatial Domain: Pima County Rectified: parcel Maintenance Format: Coverage Primary Source Organization: ALRIS Primary Source Date: 1988 Primary Source Scale: 24000 Primary Source Format: Coverage Secondary Source Organization: Pima County DOT Secondary Source Contact: Steve Whitney Secondary Source Date: 1992 Secondary Source Format: Database GIS Contact: Steve Whitney

MapGuide Layer Name: Section Grid MapGuide Scale Range: 0 - 100000

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

Contains trailheads, trail access points, and pullouts. Trailheads are designed specifically for access to multi-use paths and wildland trails and may have trail-specific parking and other amenities (e.g. restrooms, drinking fountains, ramadas, or picnic tables). Trail access points provide access to trails through parks or neighborhoods and may not have any trail-specific parking or other amenities. Pullouts are road-side pullouts located in Tucson Mountain Park. The pullouts may or may not provide access to a trail but can be used for scenic views and wildlife viewing opportunities. Known Errors/Qualifications: The trailhds layer includes conceptual, closed, and open trailheads. Most users should filter on STATUS = 'OPEN' to display only open trailheads.

The data are derived from multiple sources (e.g. GPS, heads-up digitizing, geospatial data from other jurisdictions and agencies) and should be considered representational as quality can vary across sources. Spatial Domain: Pima County Maintenance Organization: PC ITD GIS Maintenance Description: Data are updated as new trailheads are developed or as Pima County receives updates from the other jurisdictions and agencies. Maintenance Frequency: Varies Maintenance Format: GDB Std Export Primary Source Organization: Pima County NRPR Primary Source Contact: Elisabeth Van Der Leeuw Primary Source Date: 20130821 Primary Source Format: Shape GIS Contact: Ray Brice

MapGuide Layer Name: Trailheads MapGuide Scale Range: 0 - 100000000

This is the 2017 shapefile version of the AVCA administrative boundary. It generally follows the previous Resource 2000 boundary with the following modifications. Priority of drawing went first to the Pima County Parcel map, then to the NHD watershed boundary, and finally to Santa Cruz Parcels.This file is a derivative of the AVCA_Boundary_2017 feature service located here: https://services6.arcgis.com/r8sri7egU6P44VfN/arcgis/rest/services/AVCA_Boundary_2017/FeatureServer2/9/2019 added computed (GIS) acres based on various common coordinate systems: NAD83 UTM zone 12N = 577,866StatePlane = 578,224Pima County Coordinate System: 578,451

MPA Boundary Creation:Created from a variety of source reference input. Small topological errors resolved to larger adjacent poly where necessary. Polylines may not be exact compared to source datasets necessary to resolve topological errors.Pima County:Oro ValleyDigitized from 2016 General Plan, referencing GIS linework from previous General Plan & Environmentally Sensitive Lands Project (previous TSSW project work for OV).https://www.orovalleyaz.gov/files/assets/public/documents/town-manager/general-plan/yourvoiceourfuturegeneralplan.pdfhttps://www.orovalleyaz.gov/files/assets/public/documents/town-manager/general-plan/general-plan-land-use-map.pdfAreas where OV General Plan conflicted with Marana General Plan – area had since been annexed into Marana and has included in the Marana GP polys. MaranaDigitized from Make Marana – 2040 General PlanMap atlas available at: https://static1.squarespace.com/static/54cc191ce4b0f886f4762582/t/5e50496454d84d590324e663/1582320010384/Marana+Map+Atlas+2.27.19+w_editsa.pdfSpecifically referenced Figure 1: Planning Area map dated 2/2019SahuaritaDigitized from Aspire 2035 – Sahuarity’s General Plan https://sahuaritaaz.gov/DocumentCenter/View/1169/Aspire-2035-Sahuaritas-General-Plan-Amended-2020?bidId=City of Tucson Digitized from COT Future Growth Scenario Plan .pdf https://www.tucsonaz.gov/files/integrated-planning/LT-7_Future_Growth_Scenario_Map_7-8-13.pdfPart of Plan Tucsonhttps://www.tucsonaz.gov/pdsd/plan-tucsonSanta Cruz County: **Note: The following had instances of overlapping polygons in the reference data and were left as a topological exceptions of overlapping polygons. Nogales & Patagonia General Plans, as both had the area covered in their GPs Tres Alamos General Plan & Benson GPSt David GP and Denson GPCCNogalesVerified linework from Nogales General Plan 2010http://www.azplanningcenter.com/Nogales/Files/2010_08_20-000-ExecutiveSummary_IntroductionAndOverview.pdfPatagoniaVerified linework from 2009 General Planhttps://issuu.com/seagoedd/docs/patagonia_general_plan?layout=http%253A%252F%252Fskin.issuu.com%252Fv%252Flight%252Flayout.xml&showFlipBtn=trueCochise County Created from various input GIS datasets:Comprehensive Plan Growth Areas feature classComprehensive Plan Design feature class