The Pima County Jurisdictional Boundaries layer (jurisbnd) delineates the boundaries of incorporated and unincorporated areas within Pima County, Arizona. The maintenance of this layer is handled by Pima County. For more detailed information, please refer to the original metadata, found here. PurposeTo show the boundaries of Pima County's jurisdictions, including Tucson, Marana, Oro Valley, Sahuarita, and South Tucson.Dataset ClassificationLevel 0 - OpenKnown Uses--Known Errors/QualificationsThis layer serves as a general reference and does not indicate ownership. Users should exercise caution in interpreting boundaries for legal or ownership purposes.Data ContactPima County Information Technology Department - Geographic Information Systems201 N Stone Ave., 9th FloorTucson, AZ 85701GISdata@pima.govUpdate FrequencyThe layer undergoes regular updates based on annexations by Pima County's GIS team. Updates to annexations are synchronized with adjustments to the jurisdictional boundaries layer, adhering to established topology rules. The jurisbnd layer is maintained as a standalone dataset.

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.

Regulatory layer see Development Standards 10-02 (COT Drainage Manual can be found on TDOT's map and records page under downloads as of July 2012: https://tdotmaps.transview.org/MandR/ ) and COT's Floodplain, Stormwater, and Erosion Hazard Management regulations in the Tucson City Code, Part II, Chapter 26: https://www.amlegal.com/nxt/gateway.dll/Arizona/tucson_az/tucsonarizonacharterandgeneralordinances?f=templates$fn=default.htm$3.0$vid=amlegal:tucson_azPurposeLorem 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 ContactGIS Services Division GIS_IT@tucsonaz.govUpdate FrequencyNot Maintained Last update: 2009

Displays Speed Limit Ordinances for the City of Tucson. Created by copying features from stnetall.PurposeLine Layer that shows the speed limits of streets in Tucson.Dataset ClassificationLevel 0 - OpenKnown UsesUsed in Various Web MapsKnown ErrorsUrban streets from 12000 scale & rural streets from 100000 scale; 1/3 streets rectified to parcel base. 10/2013: While this layer is maintained as a Shapefile, the coverage format is still required for certain nightly processing. Data ContactDepartment of Transportation and MobilityUpdate FrequencyUpdated as needed

ward_cot displays the six city council districts in the City of Tucson. Ward area legal boundaries are based on Pima County voting precinct legal boundaries. Last updated September 19, 2023.PurposeShows the six wards of the City of Tucson and the respective councilmembers elected them.Dataset ClassificationLevel 0 - OpenKnown Uses--Known Errors--Data ContactCity of Tucson Information Technology Department, GIS Services, GIS_IT@tucsonaz.govUpdate FrequencyUpdated as new annexation or redistricting occurs.

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.

File originated from: lfil_ex for landfill sites in eastern Pima County by Pima County, but is being updated by the City of Tucson - Environmental Services. For historic information on this file, refer to the Pima County GIS Technical Services. Additional attribute fields were added to this shapefile for the City of Tucson - Environmental Services projects. City landfill boundaries are approximate and updated as new information becomes available. Original file adopted from Pima County LFIL_EX gis file. See Pima County metadata for original filePurposeTo be used on the City of Tucson - Environmental Services Potential Environmental Concerns Webmap.Dataset ClassificationLevel 0 – OpenKnown UsesNoneKnown ErrorsBoundaries are for general, approximate location of landfill boundaries and are not exact. The City of Tucson has not verified boundaries which had no City of Tucson involvement.ContactTucson Department of Environmental and General ServicesUpdate FrequencyAs Needed

The neighborhoods - all layer provides polygons representing neighborhood associations and approximate neighborhood (subdivision) boundaries within the City of Tucson, Arizona. Unofficial neighborhoods are delineated based on the subdivisions layer and may not accurately reflect culturally recognized neighborhoods.Examples of features in this dataset include:Registered Neighborhood AssociationsUnregistered Neighborhoods (Subdivisions) PurposeShows the approximate boundaries of neighborhoods/subdivisions within the City of Tucson.Dataset ClassificationLevel 0 – OpenKnown Uses--Known ErrorsThis layer serves as a general representation of neighborhood associations and subdivision boundaries and may not capture all nuances or changes in neighborhood delineations. Users should verify boundaries with local authorities for precise neighborhood information.Data ContactPlanning and Development Services DepartmentMatt Berubematthew.berube@tucsonaz.govPublisher ContactInformation Technology DepartmentGIS_IT@tucsonaz.govUpdate Frequency/Maintenance DescriptionThe layer is maintained by the City of Tucson's Planning and Development Services Department and is periodically updated to reflect changes in neighborhood associations and subdivisions. Updates may include incorporating new subdivisions or modifications to existing boundaries based on community feedback or administrative changes. The layer is intended for reference purposes and should not be used for legal or regulatory decisions without validation from appropriate authorities.

The ESZ is used to verify location in creating calls for service and to determine the proper responses for unit recommendations. Layer was created from the Fire Station Boundary polygon shapefile provided by Ann Moser. Edits were done to edge match with streets and other jurisdictional boundaries. Additional edits for splitting boundaries along N/S Broadway and Alpha Trucks.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesFor CADKnown 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 FrequencyOccasionally using ArcMap.Last known update: January 2012

Status: Updated occasionallyContact: Johanna Kraus, 837.4941Lineage: created from AutoCAD static maps, cleaned up in 2007/2008 by Johanna Kraus - zones verified against static map and research done where necessary.Attributes: ZONE_COT - displayed on map, includes overlay designator of H (historic), N (neighborhood preservation) or U (urban overlay). ORIG_ZONE - hard zoning without overlayUsage: This layer is intended to be used in the Open Data portal and not for regular use in ArcGIS Online and ArcGIS Enterprise.Link to Open Data item: https://gisdata.tucsonaz.gov/datasets/zoning-tucson-open-data

This web map contains the City of Tucson's Green Stormwater Infrastructure assets ( traffic circle, chicane, median, curb cuts and basin in right of way). Data was collected in Survey 123 for ArcGIS and is stored in WGS 84 Geographic Coordinate System. You can access a custom analysis of the data in a dashboard here or a custom query and download of the data in a wed app here. Please contact Abdulai (GIS and Mapping) or James (PIO) if you have questions or issues with accessing the map and data.

Created by cboyer1

The dataset includes approximate flood-hazard boundary areas prepared by both detailed and approximate methods. Study limits were defined using the highlighted drainage-problem areas shown on the city's zoning base maps as a guide. Floodplain studies completed and sealed in 2007 and 2008 . Shape files created April 2011. Shape files exported from Autodesk Map 3D 2006 and projected using ArcMap 10.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is intended to be used in the 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 FrequencyMaintenance and frequency to be determined by City of Tucson, Planning and Development Services.

This layer displays all annexations of municipal jurisdictions within Pima County. Each annexation is visually represented, with the outer boundary of all annexations serving as the corporate limits. The maintenance of this layer is handled by Pima County. For more detailed information, please refer to the original metadata, found here. PurposeTo show the annexations of all jurisdictions within Pima County, including Tucson, Marana, Oro Valley, Sahuarita, and South Tucson.Dataset ClassificationLevel 0 - OpenKnown Uses--Known Errors/QualificationsThis layer has overlapping map features as a result of deannexations and any subsequent annexations in the same area.Data ContactPima County Information Technology Department - Geographic Information Systems201 N Stone Ave., 9th FloorTucson, AZ 85701GISDdata@pima.govUpdate FrequencyThis layer is updated regularly to reflect the latest annexations within Pima County. Updates occur as new annexation agreements are finalized and approved by the relevant authorities. The frequency of updates varies depending on the occurrence of annexation events, but efforts are made to ensure that the dataset remains current and accurate.

This dataset is a subset of Landfills - Eastern Pima County and only shows landfills owned by the City of Tucson.File originated from: lfil_ex for landfill sites in eastern Pima County by Pima County, but is being updated by the City of Tucson - Environmental Services. For historic information on this file, refer to the Pima County GIS Technical Services. Additional attribute fields were added to this shapefile for the City of Tucson - Environmental Services projects. City landfill boundaries are approximate and updated as new information becomes available.Link to full datasetPurposeTo be used on the City of Tucson - Environmental Services Potential Environmental Concerns Webmap.Dataset ClassificationLevel 0 – OpenKnown UsesNoneKnown ErrorsBoundaries are for general, approximate location of landfill boundaries and are not exact. The City of Tucson has not verified boundaries which had no City of Tucson involvement.ContactTucson Department of Environmental and General ServicesUpdate FrequencyAs Needed

Line layer of sidewalks in the City of Tucson.PurposeDisplays the location of sidewalks in the City of Tucson.Dataset ClassificationLevel 0 - OpenKnown Uses--Known ErrorsThis layer is not maintained. Information may not be up to date.Data ContactCity of Tucson Information Technology DepartmentGIS Services, GIS_IT@tucsonaz.govUpdate FrequencyNot Maintained

This is the map to be used to add or edit points on the GPLET Story Map.

This data contains City of Tucson mapped flood hazard areas. Related feature class: dsdFHZstudy2007CrossSections.Supplemental Information: 8/31/2010 - loaded shapefile into EDITSDE geodatabase from Stormwater shapes folder. Circa 2007 - Shapefile created by consultant JE Fuller who was hired by the City to map non-FEMA flood hazards. It is a composite of the city's old Flood Hazard Zones and the new Flood Hazard Zones. Cross sections (feature class: dsdFHZStudy2007CrossSections) are used to determine depth of water. Began by TDOT in the 70's and 80's, added to by Frank (some from JE Fuller study) to display areas that could flood but are too small to be looked at by FEMALAYER SOURCED FROM: https://uagis.maps.arcgis.com/home/item.html?id=d7beb3ff711c43f19482f398beaaee84

Illustrates the Sun Van Service AreaComplementary ADA is 3/4 mile buffer around Sun Tran Routes 1-61 and Sun Shuttle Route 450. Premium Optional ADA is outside of the 3/4 mile buffer and includes all areas within the City of Tucson, city limits. Fare changes were approved September 20, 2016 - the Premium Optional ADA will be priced separate from Complementary ADA services. In addition to geographic boundaries Premium (Optional) Sun Van services include: Same day service requests and service requests outside of the complementary Sun Tran (Sun Shuttle) route service hours.Status: UPDATED: Updates only required when Service Area expands or contracts.Contact: John Zukas, DOT, 520-837-6762, john.zukas@tucsonaz.govUsage: This layer is intended to be used in the Open Data portal and not for regular use in ArcGIS Online and ArcGIS Enterprise.Link to Open Data item: https://gisdata.tucsonaz.gov/datasets/sun-van-service-area-open-data

This map is on the Better Streets page. It is part of a dashboard showing arterial streets by the type of treatment they are receiving.