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

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

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.

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

railroad displays the Union Pacific Lines in Pima County. Known Errors/Qualifications: Undetermined Spatial Domain: Pima County Rectified: quads Maintenance Format: GDB Std Export Primary Source Organization: USGS Primary Source Document: Quads Primary Source Date: 1992 Primary Source Scale: 24000 Primary Source Format: Paper Secondary Source Organization: US Census Bureau Secondary Source Document: TIGER files GIS Contact: Steve Whitney

MapGuide Layer Name: Railroads MapGuide Scale Range: 0 - 500000

DISTVOTE displays the boundaries of voter precincts in Pima County as modified and adopted by the Pima County Board of Supervisors November 21, 2017. Becoming active March 1, 2018. Known Errors/Qualifications: This layer was screen digitized on the street centerline base. Only generally rectified to parcel base. Boundaries overlap parcels in some areas. Lineage: 03/01/2006 - Received new layer from Elections, and processed it to populate Congressional and Legislative districts. 03/01/2008 - Precincts split/added per Elections, other attributes updated accordingly. 02/20/2012 - Precincts split/combined and renumbered per Elections, other attributes updated accordingly. 01/21/2014 - Precincts consolidated and renumbered per Elections staff, other attributes updated accordingly, slivers in geometry removed. 2/28/2018 - Precinct 229 split to make 249 and boundary between 6 and 175 moved. Spatial Domain: Pima County Rectified: parcel Maintenance Description: Elections will notify ITD GIS when there are precinct boundary changes. Maintenance Format: GDB Std Export Primary Source Organization: PC Elections Division Primary Source Contact: Mary Martinson Primary Source Date: 2012 Primary Source Format: Paper GIS Contact: Clark Phillips

MapGuide Layer Name: Voter Precincts MapGuide Scale Range: 0 - 100000000

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.

9/2013: While this layer is maintained as a Shapefile, the coverage format is still required for certain nightly processing. See Steve Whitney. 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: Shape 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 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.

Annex displays all annexations and deannexations for all municipal jurisdictions in Pima County. Each annexation or deannexation is displayed. The outer boundary of all annexations is the corporate limits. Known Errors/Qualifications: This layer has overlapping map features as a result of deannexations and any subsequent annexations in the same area. Spatial Domain: Pima County Rectified: parcel Maintenance Organization: PC DOT Engineering Information Mgmt Maintenance Frequency: Varies Maintenance Format: GDB Std Export Primary Source Organization: Pima County municipalities Primary Source Date: 1998 Primary Source Scale: 3000 GIS Contact: Lynn Jarzombek MapGuide Layer Name: Annexations MapGuide Scale Range: 0 - 1000000

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

washes displays the natural drainage of the area. This data theme contains multiple regulatory classifications, the correct current classification is stored in the CFS_CODE2, CFS_NUM2, and CFS_SHORT2 fields. Known Errors/Qualifications: Orthophoto washes are more detailed and are not edgematched to DLG washes. In the current regulatory scheme all washes between 2,000 CFS and 10,000 CFS are stored in the 5,000 to 10,000 category pending review. Lineage: Future plans to merge this layer with layer Wash_02K and the City's layer wash_ci, then rectify. Spatial Domain: Pima County Rectified: orthophoto90 Maintenance Description: The washes feature class is exported from the geodatabase on a nightly basis. The washes annotation is in a separate cover: washanno

Naming unknown/unnamed washes from USGS quad....04/14/08 Maintenance Format: GDB Std Export Primary Source Organization: PC Primary Source Document: Orthophotos Primary Source Date: 1990 Primary Source Scale: 12000 Secondary Source Organization: USGS Secondary Source Document: Transportation DLG Secondary Source Date: 1988 Secondary Source Scale: 100000 GIS Contact: Mary Beth Clark

MapGuide Layer Name: Washes - All MapGuide Scale Range: 0 - 100000

Washes displays the natural drainage of the area. This data theme contains multiple regulatory classifications, the correct current classification is stored in the CFS_CODE2, CFS_NUM2, and CFS_SHORT2 fields. Lineage: Future plans to merge this layer with layer Wash_02K and the City's layer wash_ci, then rectify. Spatial Domain: Pima County Rectified: orthophoto90 Maintenance Description: The washes feature class is exported from the geodatabase on a nightly basis. The washes annotation is in a separate cover: washanno Naming unknown/unnamed washes from USGS quad....04/14/08 Maintenance Format: GDB Std Export Primary Source Organization: PC Primary Source Document: Orthophotos Primary Source Date: 1990 Primary Source Scale: 12000 Secondary Source Organization: USGS Secondary Source Document: Transportation DLG Secondary Source Date: 1988 Secondary Source Scale: 100000 GIS Contact: Mary Beth Clark MapGuide Layer Name: Washes - All MapGuide Scale Range: 0 - 100000PurposeLorem 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 ErrorsKnown Errors/Qualifications: Orthophoto washes are more detailed and are not edgematched to DLG washes. In the current regulatory scheme all washes between 2,000 CFS and 10,000 CFS are stored in the 5,000 to 10,000 category pending review.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.

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

paregion displays all parcels in Pima County. Known Errors/Qualifications: paregion contains duplicate taxcodes for parcels, i.e. undeveloped subdivisions in which all lots are assigned the same taxcode, until the lots are developed. Further, a relatively small number of other parcels have more than one polygon per parcel resulting in duplicate taxcodes. Subdivision common areas are typical examples. Parcels with duplicate taxcodes in paregion duplicate parcel valuation data. Summing valuations for these duplicated taxcode parcels from paregion will result in inflated totals. Users should normalize their analysis results based on the frequency of duplicate taxcodes.

Some areas that are not assigned a tax code by the Assessor are "void" areas, having no attributes. Void roadway areas that "bleed" beyond the county border are the most common case. They include a major portion of county street areas. The coverage format will always have these "void" areas due to the nature of the coverage format. These areas are not in our library's paregion shapefile format. Spatial Domain: Pima County Rectified: parcel Maintenance Organization: PC ITD GIS Maintenance Description: Steve Whitney's processing assembles the section DWG drawing data daily and creates the coverage in the library. Jeff McConnell's special paregion processing (ParcelToShape) makes the library shapefile from the coverage, deleting all areas with blank (null) parcel codes, resulting in true voids where there are no parcels, such as most right-of-way. The coverage format always has the interior "island" areas due to the nature of the coverage format. Maintenance Frequency: Daily Maintenance Format: Coverage Primary Source Organization: PC ITD GIS Primary Source Contact: Steve Whitney Primary Source Date: 2006 Primary Source Scale: 200 Primary Source Format: DWG GIS Contact: Steve Whitney

MapGuide Layer Name: Parcels (Landbase) MapGuide Scale Range: 0 - 25000

Sun Tran maintains bus stop locations in the Trapeze routing software system. Stop data shows stop locations. Known Errors/Qualifications: Data is digitized "heads up" in Trapeze on the pre-rubbersheeted stnetall file in lat/lon.

There may be inactive stops included. Users should filter using inactive = 1 to show only active stops. Lineage: Digitized by Sun Tran staff in Trapeze routing system software. Exported once per month by COT/TDOT Management Services staff. Spatial Domain: Eastern Pima County Rectified: parcel Maintenance Organization: COT/TDOT/Management Services Maintenance Description: Sun Tran maintains in their database system and notifies Peter Johnson every 3 month for any updates. Using ArcGIS, Davita Mueller exports to shapefile in local coordinate system. Maintenance Frequency: Quarterly Maintenance Format: Shape Primary Source Organization: COT/TDOT/Management Services Primary Source Contact: Davita Mueller Primary Source Document: busstop.shp Primary Source Date: 20120620 Primary Source Format: Database Secondary Source Organization: Sun Tran GIS Contact: Steve Whitney

MapGuide Layer Name: Bus Stops - Sun Tran MapGuide Scale Range: 0 - 200000