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.

Current and sold City of Tucson property as well as some "Easement Only" properties. Status: Updated as needed. Contact: Ryan Tripp, City of Tucson Real Estate. Daniel Lawlor, City of Tucson Department of Transportation and Mobility.Intended Use: For display on Map Tucson. For current City property, use definition query LAYERDEF = "Current City Property." For sold property, use definition query LAYERDEF = "Sold City Property." Contains some records without geometry. Layer history note: March, 2012 - combined feature classes RE_COTPARC, RE_SOLDS and table RE_RP into RE_CITYPROPERTY.Dataset ClassificationLevel 0 - OpenData ContactDepartment of Transportation and MobilityDaniel Lawlordaniel.lawlor@tucsonaz.govJim Robinsonjames.robinson2@tucsonaz.gov

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 survey is completed by TCB volunteers when they clean up and adopted site. Survey results appear in the map as a table related to individual feature classes based on GUID/Global ID fields. Associated Elements:HubHub Site: https://tucson-clean-and-beautiful-cotgis.hub.arcgis.com/Hub Item Details: https://cotgis.maps.arcgis.com/home/item.html?id=e5a76516027f4f718857477f21b23696#overviewOpen to PublicVolunteer Report Map: https://cotgis.maps.arcgis.com/home/item.html?id=8b0cfefce0a04883967353fd64d70a0c#overviewVolunteer Report App: https://cotgis.maps.arcgis.com/home/item.html?id=e01073c557c344328a07544fb82478d2#overviewFeature Layer View: https://cotgis.maps.arcgis.com/home/item.html?id=1103f4e81c2743b795f6e8a7250147ffAdopt-a-Site App: https://cotgis.maps.arcgis.com/home/item.html?id=d40db845579c4b208906ad55358a7e52Adopt-a-Site Map: https://cotgis.maps.arcgis.com/home/item.html?id=7c9855e5a0a542089ac2a66dc4091f4bOpen to Volunteers and TCB StaffSurvey: https://cotgis.maps.arcgis.com/home/item.html?id=b45b263db42d4b6b93f13d9ed60a735e#overviewOpen to TCB StaffEditing Map: https://cotgis.maps.arcgis.com/home/item.html?id=fef204a9647946ae893ce5ac5b780ec1#overviewEditing Layers: https://cotgis.maps.arcgis.com/home/item.html?id=7a20673361904073bc7ee204252bb24e

The MS&R Plan identifies the general location and size of existing and proposed freeways, arterial and collector streets, future rights-of-way, setback requirements, typical intersections and cross sections, and gateway and scenic routes. The City’s Department of Transportation and the Planning and Development Services Department (PDSD) implement the MS&R Plan. The MS&R Plan is considered a Land Use Plan as defined in the Unified Development Code (UDC) Section 3.6, and, therefore, is subject to amendment in accordance with the standard Land Use Plan and Adoption and Amendment Procedures. The MS&R right-of-way lines are used in determining the setback for development through the MS&R Overlay provisions of the UDC. As stated in the current MS&R Plan, page 4, “The purpose of the Major Streets and Routes Plan is to facilitate future street widening, to inform the public which streets are the main thoroughfares, so that land use decisions can be based accordingly, and to reduce the disruption of existing uses on a property. By stipulating the required right-of-way, new development can be located so as to prepare for planned street improvements without demolition of buildings or loss of necessary parking.”PurposeThe major purposes of the Major Streets and Routes Plan are to identify street classifications, the width of public rights-of-way, to designate special routes, and to guide land use decisions. General Plan policies stipulate that planning and developing new transportation facilities be accomplished by identifying rights-of-way in the Major Streets and Routes Plan. The policies also aim to encourage bicycle and pedestrian travel, "minimize disruption of the environment," and "coordinate land use patterns with transportation plans" by using the street classification as a guide to land use decisions.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is intended to be used in the Open Data portal and not for regular use in ArcGIS Online and ArcGIS Enterprise.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 FrequencyAs needed

Hosted feature layers used in TCB Adopt-a-Site editing map. These layers replaced the sde layers originally published in 2015 as the ultimate source of truth. Associated Elements:HubHub Site: https://tucson-clean-and-beautiful-cotgis.hub.arcgis.com/Hub Item Details: https://cotgis.maps.arcgis.com/home/item.html?id=e5a76516027f4f718857477f21b23696#overviewOpen to PublicVolunteer Report Map: https://cotgis.maps.arcgis.com/home/item.html?id=8b0cfefce0a04883967353fd64d70a0c#overviewVolunteer Report App: https://cotgis.maps.arcgis.com/home/item.html?id=e01073c557c344328a07544fb82478d2#overviewFeature Layer View: https://cotgis.maps.arcgis.com/home/item.html?id=1103f4e81c2743b795f6e8a7250147ffAdopt-a-Site App: https://cotgis.maps.arcgis.com/home/item.html?id=d40db845579c4b208906ad55358a7e52Adopt-a-Site Map: https://cotgis.maps.arcgis.com/home/item.html?id=7c9855e5a0a542089ac2a66dc4091f4bOpen to Volunteers and TCB StaffSurvey: https://cotgis.maps.arcgis.com/home/item.html?id=b45b263db42d4b6b93f13d9ed60a735e#overviewOpen to TCB StaffEditing Map: https://cotgis.maps.arcgis.com/home/item.html?id=fef204a9647946ae893ce5ac5b780ec1#overviewEditing Layers: https://cotgis.maps.arcgis.com/home/item.html?id=7a20673361904073bc7ee204252bb24e

This Hub is used to help Tucson Clean and Beautiful volunteers and staff manage Adopt-a-Site volunteer reporting. A volunteer work report should be completed through the online form below by the volunteer leader after each project/event. To complete the survey, start by signing in using the link in the upper right corner, or create an account by clicking on the Join the TC&B Volunteer Team button below.HubHub Site: https://tucson-clean-and-beautiful-cotgis.hub.arcgis.com/Hub Item Details: https://cotgis.maps.arcgis.com/home/item.html?id=e5a76516027f4f718857477f21b23696#overviewOpen to PublicVolunteer Report Map: https://cotgis.maps.arcgis.com/home/item.html?id=8b0cfefce0a04883967353fd64d70a0c#overviewVolunteer Report App: https://cotgis.maps.arcgis.com/home/item.html?id=e01073c557c344328a07544fb82478d2#overviewFeature Layer View: https://cotgis.maps.arcgis.com/home/item.html?id=1103f4e81c2743b795f6e8a7250147ffOpen to Volunteers and TCB StaffSurvey: https://cotgis.maps.arcgis.com/home/item.html?id=b45b263db42d4b6b93f13d9ed60a735e#overviewOpen to TCB StaffEditing Map: https://cotgis.maps.arcgis.com/home/item.html?id=fef204a9647946ae893ce5ac5b780ec1#overviewEditing Layers: https://cotgis.maps.arcgis.com/home/item.html?id=7a20673361904073bc7ee204252bb24e

Hosted feature layers used in TCB Adopt-a-Site editing map. These layers replaced the sde layers originally published in 2015 as the ultimate source of truth. Associated Elements:HubHub Site: https://tucson-clean-and-beautiful-cotgis.hub.arcgis.com/Hub Item Details: https://cotgis.maps.arcgis.com/home/item.html?id=e5a76516027f4f718857477f21b23696#overviewOpen to PublicVolunteer Report Map: https://cotgis.maps.arcgis.com/home/item.html?id=8b0cfefce0a04883967353fd64d70a0c#overviewVolunteer Report App: https://cotgis.maps.arcgis.com/home/item.html?id=e01073c557c344328a07544fb82478d2#overviewFeature Layer View: https://cotgis.maps.arcgis.com/home/item.html?id=1103f4e81c2743b795f6e8a7250147ffAdopt-a-Site App: https://cotgis.maps.arcgis.com/home/item.html?id=d40db845579c4b208906ad55358a7e52Adopt-a-Site Map: https://cotgis.maps.arcgis.com/home/item.html?id=7c9855e5a0a542089ac2a66dc4091f4bOpen to Volunteers and TCB StaffSurvey: https://cotgis.maps.arcgis.com/home/item.html?id=b45b263db42d4b6b93f13d9ed60a735e#overviewOpen to TCB StaffEditing Map: https://cotgis.maps.arcgis.com/home/item.html?id=fef204a9647946ae893ce5ac5b780ec1#overviewEditing Layers: https://cotgis.maps.arcgis.com/home/item.html?id=7a20673361904073bc7ee204252bb24e

Take a guided trip through the data in this Story Map, featuring helpful narratives, interactive maps, and illustrative graphs. Explore how race, age, income, and unemployment vary across Tucson and how they relate to each other and to poverty. Learn about how race, age, and unemployment relate to poverty in Tucson and what parts of our City are experiencing the most economic stress. This Story Map provides an updated geographic view at many of the American Community Survey indicators identified in the 2007 and 2012 Poverty & Urban Stress Report. Scroll down to follow the narrative we've provided or use the bookmarks in the upper-right-hand corner to skip to key topics. Each map in this story is interactive, so click around and find the stories of interest to you.

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.

Hosted feature layers used in TCB Adopt-a-Site editing map. These layers replaced the sde layers originally published in 2015 as the ultimate source of truth. Associated Elements:HubHub Site: https://tucson-clean-and-beautiful-cotgis.hub.arcgis.com/Hub Item Details: https://cotgis.maps.arcgis.com/home/item.html?id=e5a76516027f4f718857477f21b23696#overviewOpen to PublicVolunteer Report Map: https://cotgis.maps.arcgis.com/home/item.html?id=8b0cfefce0a04883967353fd64d70a0c#overviewVolunteer Report App: https://cotgis.maps.arcgis.com/home/item.html?id=e01073c557c344328a07544fb82478d2#overviewFeature Layer View: https://cotgis.maps.arcgis.com/home/item.html?id=1103f4e81c2743b795f6e8a7250147ffAdopt-a-Site App: https://cotgis.maps.arcgis.com/home/item.html?id=d40db845579c4b208906ad55358a7e52Adopt-a-Site Map: https://cotgis.maps.arcgis.com/home/item.html?id=7c9855e5a0a542089ac2a66dc4091f4bOpen to Volunteers and TCB StaffSurvey: https://cotgis.maps.arcgis.com/home/item.html?id=b45b263db42d4b6b93f13d9ed60a735e#overviewOpen to TCB StaffEditing Map: https://cotgis.maps.arcgis.com/home/item.html?id=fef204a9647946ae893ce5ac5b780ec1#overviewEditing Layers: https://cotgis.maps.arcgis.com/home/item.html?id=7a20673361904073bc7ee204252bb24e

zip displays ZIP Code areas. Known Errors/Qualifications: Metropolitan boundaries are delineated well. Rural boundaries are extrapolated in some areas. Refer to US Postal Service for latest ZIP Code routes and for exact individual addresses. Zip codes defined by the US Postal Service as "unique", "military", and "post office box" are not included in this layer as they have no defined areas.

10/2013: While this layer is maintained as a feature class in gdbmaint, the coverage format is still required for certain nightly processing. See Steve Whitney. Lineage: Modified 85704 and 85718 zip code polygons as per USPS records requested by Matt from Tucson Water. Modified 85641 based on boundary of Coyote Creek Lots 1-395. Added 85756 zip code based on KOLD on-line news story, 7/1/08. Modified 85718 boundary per anonymous mapguide printout from City, 5/14/09. Modified 85756/85706 boundary using USPS lookup from parcel layer, 5/19/09. Added 85622 based on Green Valley news article and zip+4 lookup, 8/17/09. Removed 85744 based on zip+4 lookup and it was a single business "unique" zip code for IBM. Modified 85629 based on zip+4 notified by Michelene, 4/22/14. Modified boundary of 85742 and 85737 per Irene Swanson 9/2/14. Modified 85653 as per Robin Freiman 9/11/14. Modified 85704 as per Robin Freiman, 10/31/14. Modified 85658 as per Jennifer Patterson (recorders office) 9/10/15. Modified 85641 as per Michelene 4/8/16. Modified 85741 per Robin 1/13/17. Modified 85755 1/27/17 per Robin. 10/25/17 Modified 85341 and 85321 per Robin. Modify 85653 per Marana. 4/19/21 Modified 85629,85756 and 85641 per Nicholas Jordan. Spatial Domain: Pima County Rectified: parcel Maintenance Organization: PC ITD GIS Maintenance Format: GDB Std Export Primary Source Organization: US Postal Service Primary Source Document: http://new.usps.com Primary Source Date: 2000 Primary Source Format: Paper GIS Contact: Ray Brice

MapGuide Layer Name: Zip Code Areas MapGuide Scale Range: 0 - 100000000