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.

This dataset represents Fire Taxation Districts in Pima County. These districts outline areas where property taxes are levied to support fire protection services, excluding certain areas such as tribal fire districts, non-taxed Federal, State, or Pima County properties, and cities without separate fire taxation districts. For example, the City of Tucson and the City of South Tucson do not have distinct fire taxation districts and are not included in this dataset.

Examples of features mapped in this layer include:

Taxed Fire District Boundaries Non-taxed Federal, State, or County properties excluded from certain fire districts

For more information, visit the Pima County Fire Taxation Districts Metadata.

Purpose To provide geographic information on fire taxation districts within Pima County, aiding in tax management and fire service planning.

Dataset Classification Level 0 – Open

Known Uses Used for taxation management, fire service planning, and public information purposes.

Known Errors

Fire taxation districts do not necessarily align with fire service areas, e.g., areas serviced by the Rural/Metro Corporation are excluded.
The City of Tucson and the City of South Tucson are not included as they do not have separate fire taxation districts.
Tribal fire districts are excluded from this dataset.
District boundaries may not be precise, and updates rely on annexation updates from the Assessor's data.

Data Contact Pima Countygisdata@pima.gov

Publisher Contact Information Technology Department GIS_IT@tucsonaz.gov

Update Frequency Updates are dependent on Assessor's data and annexation updates.

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.

Fire Taxation Districts in Pima County.For more information, visit https://gis.pima.gov/data/contents/metadet.cfm?name=firedistPurposeLorem 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 ErrorsFire taxation districts do not necessarily coincide with fire service areas, e.g. areas that are serviced by the Rural/Metro Corporation are not included in this layer. The City of Tucson and the City of South Tucson do not have a separate fire taxation district and are not included. This layer does not include tribal fire districts. District boundaries may not be exact. Non-taxed Federal, State, or Pima County owned properties are excluded from the following fire district boundaries: Sonoita Elgin, Arivaca,and Helmet Peak. This layer does not get updated until Assesor's data gets updated with the annexation information.Data ContactPima CountyWilliam Gerdesgisdata@tucsonaz.govPublisher ContactInformation Technology DepartmentGIS_IT@tucsonaz.govUpdate FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

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.

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

Plan submitted by: WBeard on 10/21/2021 USER DESCRIPTION: The areas of Arizona City/Eloy and South Casa Grande have a greater community of interest being in the same district as Marana (CD 6 on map) than with Yuma. The population balance is created by adjusting the amount of the City of Tucson within CD 7 on this map. USER PLAN OBJECTIVE: The area east of Tohono reservation in Pinal County (ELoy/S Casa Grande/AZ City) have more in common with Marana than with Yuma. Population balanced in City of Tucson. Maintains more communities of interest and doesn't affect VRA requirements.