Facebook
Twitterhttps://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
Facebook
Twitterhttps://gis.pima.gov/data/contents/metadet.cfm?name=fp_ss***Download shapefile of this dataset here. (Normal download using button on Geospatial Data Portal item details page won't be successful.)***
Facebook
Twitterhttps://gis.pima.gov/data/contents/metadet.cfm?name=pcgpraqm***Note: overlapping data is present, and attention needs to be paid to dates on the instruments. Any questions should be addressed to transsyseim@pima.gov.***
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
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.
Facebook
TwitterZipped raster dataset of 2018 Land-Use-Land-Cover (named pima_landcover_noroads.zip)Download this zipped dataset here by clicking the download button at top right.https://gis.pima.gov/data/contents/metadet.cfm?name=lulc18
Facebook
TwitterA 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.
Facebook
TwitterStatus: 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.
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
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.
Facebook
Twitterhttps://gis.pima.gov/data/contents/metadet.cfm?name=pcgprsbm***Note: overlapping data is present, and attention needs to be paid to dates on the instruments. Any questions should be addressed to transsyseim@pima.gov.***
Facebook
TwitterADFACIL 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
Facebook
TwitterThis 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
Not seeing a result you expected?
Learn how you can add new datasets to our index.
Facebook
Twitterhttps://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