Air right lots are reflect a party’s right to construct an improvement above an existing area of land that is not owned by the constructor. They are a type of development right in real estate referring to the empty space about a property. These tax lot numbers start at 7000. There are approximately 704 air rights lots. Non-contiguous Air Rights Lots numbered in 8000 series can either be District owned Multifamily rental units or Existing Development Mixed (residential and commercial).Multifamily 8000 series lots can be proposed development projects that are inclusive of the Mayor’s Office Affordable/Public Housing Initiatives. Additionally, they can either be development sites that are owned by the District and the site is leased to developer. Due to financing and legal requirements, each set of government funded units are required to have separate parcel ID’s (SSL’s). All the units are rentals, none of the units will be for sale.Existing Development Mixed Use 8000 series lots are residential owner(s) that own both residential and commercial portions. The Lot split is done to ensure each party pays the appropriate real estate taxes assessed to each specific use. There is a master covenant lease outlining property access-rights-use between residential and commercial owner and lease holders. There is also a master lease related to the commercial space where the residential owner is the lease holder.

This repository contains data and codes that support the findings of the study.- PPD-EPC open dataset with the enriched spatial analyses scores and UPRN.- Batch Geocoding Notebook of PPD-EPC dataset with GeoPy - Here API- PyQGIS codes for proximity, terrain, and visibility spatial analyses.- Jupyter Notebook of Machine Learning algorithms for mass property valuation.

Download .zipThe analysis for limitations for large scale development was completed by considering several different factors including depth to bedrock, bedrock type glacial geology, and ground water availability as well as percent of slope and flooding potential.

The soils used in this analysis were digitized from the paper final soil survey field sheets. These sheets were taped together to form an area covering each of the USGS 7.5 minute quadrangle maps in the county. The areas for each quadrangle were then digitized using run-length encoding technique sampling along horizontal lines which represented the midline of cells with a height of 250 feet. The measurement increment along these lines was one decafoot (10 feet). The quadrangle files were then merged into a county file which has subsequently been converted to Arc/Info format.

The user should bear in mind that this coverage is only an approximation of the soil survey and should not be used for site specific analysis.

Additional details of the digitizing process are available upon request.

Original coverage data was converted from the .e00 file to a more standard ESRI shapefile(s) in November 2014.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesReal Estate & Land ManagementReal Estate and Lands Management2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

Please note that this dataset is not an official City of Toronto land use dataset. It was created for personal and academic use using City of Toronto Land Use Maps (2019) found on the City of Toronto Official Plan website at https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/official-plan/official-plan-maps-copy, along with the City of Toronto parcel fabric (Property Boundaries) found at https://open.toronto.ca/dataset/property-boundaries/ and Statistics Canada Census Dissemination Blocks level boundary files (2016). The property boundaries used were dated November 11, 2021. Further detail about the City of Toronto's Official Plan, consolidation of the information presented in its online form, and considerations for its interpretation can be found at https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/official-plan/ Data Creation Documentation and Procedures Software Used The spatial vector data were created using ArcGIS Pro 2.9.0 in December 2021. PDF File Conversions Using Adobe Acrobat Pro DC software, the following downloaded PDF map images were converted to TIF format. 9028-cp-official-plan-Map-14_LandUse_AODA.pdf 9042-cp-official-plan-Map-22_LandUse_AODA.pdf 9070-cp-official-plan-Map-20_LandUse_AODA.pdf 908a-cp-official-plan-Map-13_LandUse_AODA.pdf 978e-cp-official-plan-Map-17_LandUse_AODA.pdf 97cc-cp-official-plan-Map-15_LandUse_AODA.pdf 97d4-cp-official-plan-Map-23_LandUse_AODA.pdf 97f2-cp-official-plan-Map-19_LandUse_AODA.pdf 97fe-cp-official-plan-Map-18_LandUse_AODA.pdf 9811-cp-official-plan-Map-16_LandUse_AODA.pdf 982d-cp-official-plan-Map-21_LandUse_AODA.pdf Georeferencing and Reprojecting Data Files The original projection of the PDF maps is unknown but were most likely published using MTM Zone 10 EPSG 2019 as per many of the City of Toronto's many datasets. They could also have possibly been published in UTM Zone 17 EPSG 26917 The TIF images were georeferenced in ArcGIS Pro using this projection with very good results. The images were matched against the City of Toronto's Centreline dataset found here The resulting TIF files and their supporting spatial files include: TOLandUseMap13.tfwx TOLandUseMap13.tif TOLandUseMap13.tif.aux.xml TOLandUseMap13.tif.ovr TOLandUseMap14.tfwx TOLandUseMap14.tif TOLandUseMap14.tif.aux.xml TOLandUseMap14.tif.ovr TOLandUseMap15.tfwx TOLandUseMap15.tif TOLandUseMap15.tif.aux.xml TOLandUseMap15.tif.ovr TOLandUseMap16.tfwx TOLandUseMap16.tif TOLandUseMap16.tif.aux.xml TOLandUseMap16.tif.ovr TOLandUseMap17.tfwx TOLandUseMap17.tif TOLandUseMap17.tif.aux.xml TOLandUseMap17.tif.ovr TOLandUseMap18.tfwx TOLandUseMap18.tif TOLandUseMap18.tif.aux.xml TOLandUseMap18.tif.ovr TOLandUseMap19.tif TOLandUseMap19.tif.aux.xml TOLandUseMap19.tif.ovr TOLandUseMap20.tfwx TOLandUseMap20.tif TOLandUseMap20.tif.aux.xml TOLandUseMap20.tif.ovr TOLandUseMap21.tfwx TOLandUseMap21.tif TOLandUseMap21.tif.aux.xml TOLandUseMap21.tif.ovr TOLandUseMap22.tfwx TOLandUseMap22.tif TOLandUseMap22.tif.aux.xml TOLandUseMap22.tif.ovr TOLandUseMap23.tfwx TOLandUseMap23.tif TOLandUseMap23.tif.aux.xml TOLandUseMap23.tif.ov Ground control points were saved for all georeferenced images. The files are the following: map13.txt map14.txt map15.txt map16.txt map17.txt map18.txt map19.txt map21.txt map22.txt map23.txt The City of Toronto's Property Boundaries shapefile, "property_bnds_gcc_wgs84.zip" were unzipped and also reprojected to EPSG 26917 (UTM Zone 17) into a new shapefile, "Property_Boundaries_UTM.shp" Mosaicing Images Once georeferenced, all images were then mosaiced into one image file, "LandUseMosaic20211220v01", within the project-generated Geodatabase, "Landuse.gdb" and exported TIF, "LandUseMosaic20211220.tif" Reclassifying Images Because the original images were of low quality and the conversion to TIF made the image colours even more inconsistent, a method was required to reclassify the images so that different land use classes could be identified. Using Deep learning Objects, the images were re-classified into useful consistent colours. Deep Learning Objects and Training The resulting mosaic was then prepared for reclassification using the Label Objects for Deep Learning tool in ArcGIS Pro. A training sample, "LandUseTrainingSamples20211220", was created in the geodatabase for all land use types as follows: Neighbourhoods Insitutional Natural Areas Core Employment Areas Mixed Use Areas Apartment Neighbourhoods Parks Roads Utility Corridors Other Open Spaces General Employment Areas Regeneration Areas Lettering (not a land use type, but an image colour (black), used to label streets). By identifying the letters, it then made the reclassification and vectorization results easier to clean up of unnecessary clutter caused by the labels of streets. Reclassification Once the training samples were created and saved, the raster was then reclassified using the Image Classification Wizard tool in ArcGIS Pro, using the Support...

The Office of the Deputy Mayor for Planning and Economic Development (DMPED) is charged with executing the Mayor's economic development strategy. DMPED manages a portfolio of real estate projects located across the District of Columbia. More information is available on the Project Pipeline Database (PPD) Public Access Dashboard.

Here are a few use cases for this project:

1. Urban Planning: Public entities such as urban planning departments could utilize this computer vision model to get a better understanding of urban environments, the distribution of land cover classes, and to plan future development.

2. Agricultural Optimization: Farmers and agricultural businesses could use the model to determine optimal crop placement based on available barren land, proximity to rivers for irrigation, and avoidance of residential regions.

3. Environmental Conservation: Conservation organizations could use it to identify forest and rangeland areas, monitor these regions over time and track changes due to industrial development or natural phenomena like deforestation.

4. Traffic Management: Transportation departments could leverage the model to analyze the layout of current highways and residential areas, generating data that aids in the planning of future infrastructure or the improvement of current ones.

5. Real Estate and Business Planning: Real estate companies could use the model to identify residential and industrial areas for investment opportunities. Likewise, businesses could use it for strategic placement of new branches or stores based on the land cover classes.

Develop Louisville Focuses on the full range of land development activities, including planning and design, vacant property initiatives, advanced planning, housing & community development programs, permits and licensing, land acquisition, public art and clean and green sustainable development partnerships.Data Dictionary:“LBA” is the abbreviation for the Louisville and Jefferson County LBA Authority, Inc."Parcel ID" is an identification code assigned to a piece of real estate by the Jefferson County Property Valuation Administration. The Parcel ID is used for record keeping and tax purposes.“IMPROV” stands for whether or not the real estate parcel had an “improvement” (i.e., a structure) situated on it at the time it was sold. “1” indicates that a structure existed when the parcel was sold and “0” indicates that the parcel was an empty, piece of land.“APPLICANT” is the individual(s) or active business entity that submitted an Application to Purchase the real estate parcel and whose application was presented to and approved by the LBA’s Board of Directors. The Board of Directors must approve each application before a transfer deed is officially recorded with the Office of the County Clerk of Jefferson County, Kentucky.“SALE DATE” is the date that the Applicant signed the transfer deed for the respective real estate parcel.“SALE AMOUNT” is the amount that the Applicant paid to purchase the respective real estate parcel.“SALE PROGRAM” is the LBA’s disposition program that the Applicant participated in to acquire the real estate parcel.The Office of Community Development defines each “Sale Program” as follows:Budget Rate (“Budget Rate Policy for New Construction Projects”) – Applicant submitted a proposed construction project for the empty, piece of land.Cut It Keep It - Applicant requested to maintain the empty piece of land situated on the same block as a real estate parcel owned by the Applicant. Applicant must retain ownership of the lot for three (3) years before the Applicant can sell it.Demo for Deed (“Last Look – Demo for Deed”) – Applicant requested to demolish the structure situated on the real estate parcel and retain the land for a future use.Flex Rate (“Flex Rate Policy for New Construction Projects”) – Applicant submitted a proposed construction project for the empty, piece of land but did not have proof of funding or a timeline as to when the project would be completed.Metro Redevelopment – The real estate parcel was part of a redevelopment project being considered by Metro Government.Minimum Pricing Policy – The pricing policy that was approved by the LBA’s Board of Directors and in effect as of the real estate parcel’s sale date.RFP (“Request for Proposals”) - Applicant requested to rehabilitate the structure in order to place it back into productive use within the neighborhood.Save the Structure (“Last Look – Save the Structure”) - Applicant requested to rehabilitate the structure in order to place it back into productive use within the neighborhood.Side Yard – The Applicant requested to acquire the LBA’s adjoining piece of land to make the Applicant’s occupied, real estate parcel larger and more valuable.SOI (“Solicitation of Interest”) – The LBA assembled two (2) or more real estate parcels and the Applicant submitted a redevelopment project for the subject parcels.For more information about each of the current disposition programs that the LBA offers, please refer to the following website pages:https://louisvilleky.gov/government/community-development/vacant-lot-sales-programshttps://louisvilleky.gov/government/community-development/vacant-structures-saleContact:Connie Suttonconnie.sutton@louisvilleky.gov

This layer contains the data for the homeowners associations (HOAs) in the City of Round Rock, located in Williamson County, Texas. This layer is part of an original dataset provided and maintained by the City of Round Rock GIS/IT Department. The data in this layer are represented as polygons.A homeowners association is a private association often formed by a real estate developer for the purpose of marketing, managing, and selling homes and lots in a residential subdivision.

Properties participating in the Purchase of Development Rights program. The PDR applicant property boundary data layer is an integral part of the planning data in the Lexington-Fayette-Urban County Government Geographic Information System. This information is used by the Division of Planning in case review, enforcement, and long range planning. GIS data layers are accessed by personnel in most LFUCG divisions for basic applications such as viewing, querying, and map output production.

This is the Fiscal Year 2015 Tax dataset. The data is current as of January 1, 2014.

The data includes the fields found in the Property database at: http://www.cambridgema.gov/Assess/PropertyDatabase

For GIS users: Link the field GIS-ID in the dataset to the ML field in the GIS data layer.

Detailed information on individual parcels within Cumberland County, NC, including the City of Fayetteville, the Town of Hope Mills, the Town of Spring Lake, the Town of Eastover, the Town of Falcon, the Town of Godwin, the Town of Linden, the Town of Stedman, and the Town of Wade. Attributes include:Parcel REID (PIN Number): A unique identifier assigned to each parcel for tax purposes.Owner Information: Name and contact details of the property owner(s).Parcel Boundaries: Geospatial data defining the exact boundaries of each parcel.Assessed Value: The assessed value of the land and any improvements for property tax purposes.Land Use: Current land use classification (e.g., residential, commercial, agricultural).Size: Area of the parcel in square feet or acres.Zoning: Zoning classification and any applicable zoning restrictions.Legal Descriptions: Detailed legal description of the parcel boundaries and location.This layer is crucial for tax assessors, urban planners, developers, and other stakeholders who require accurate and up-to-date parcel information for decision-making and operational purposes. It supports a wide range of applications, including property tax assessments, land use planning, infrastructure development, and real estate transactions.More information at https://cumberlandgis.maps.arcgis.com/apps/webappviewer/index.html?id=a6ea68995c2349e9a177366288589be7

Transfer of Development Rights (TDR) and Purchase of Development Rights (PDR) are two tools used to protect lands from development. "Transfer of Development Rights (TDR) is a voluntary, incentive-based program that allows landowners to sell development rights from their land to a developer or other interested party who then can use these rights to increase the density of development at another designated location. While the seller of development rights still owns the land and can continue using it, an easement is placed on the property that prevents further development. A TDR program protects land resources at the same time providing additional income to both the landowner and the holder of the development rights." Source: https://www.uwsp.edu/cnr-ap/clue/Documents/PlanImplementation/Transfer_of_Development_Rights.pdf The Purchase of Development Rights (PDR) is a voluntary program in which a land trust or a local, county or state agency buys the development rights on a parcel of land, primarily agricultural. PDRs "permanently extinguish all preexisting development potential of a particular property and are not used to offset development elsewhere in the county. Other than very limited rights reserved to the original grantor and their immediate family, no further commercial or residential subdivision is allowed. The grantor of the easement and all subsequent owners of the property retain full fee simple ownership of the land, but are bound by the terms of the Deed of Easement" in perpetuity. Source: https://www.harfordcountymd.gov/368/HALPP These data are intended for general guidance and use only.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/Environment/MD_ProtectedLands/FeatureServer/9

A Development Site (DV), referenced using a Development Site Number, is a property boundary that the Seattle Department of Construction and Inspections (SDCI) uses to apply code standards. A Development Site may overlap with one or more King County tax parcels.Source Data: DPD.DevsitesDefinition Query: Where DEVSITE STATUS IN ('ACTIVE', 'PRESUMED', 'UPDATE') And DEVSITE ID does not begin with 'UN' And DEVSITE ID does not begin with 'WB' And SEATTLE is not equal to 0Symbology Category Expression: var disp_txt = $feature["PRCLID"]; if (Find("RW", disp_txt, 0)>-1) { return "Right-of-Way"; } else { return "Non-Right-of-Way"; }Refresh: Daily

The approximate geographic area of the Livable Centers Initiative during the "10 Year Update" process, published in January 2013. View the full report here. Specifically, this layer is shown in Exhibit 1, page vii, the "LCI Study Area."Executive Summary:UNLOCKING NEW OPPORTUNITIES The City of Sandy Springs intends to achieve a variety of objectives through the LCI 10-Year Update (January 2013 version). LCI refers to the Livable Centers Initiative, a program of the Atlanta Regional Commission (ARC) that assists local governments and organizations in planning efforts that are significant to the region. This plan incorporates additional material from the Sandy Springs City Center Master Plan that was unavailable when the previous version of this update was submitted in Sept. 2012. Exhibit 1 on page vii identifies the LCI study area and the City Center study area contained within it. This document (LCI Plan) places special emphasis on the City Center study area as the portion of the LCI study area best positioned for reinvestments that meet community goals. At the same time, it addresses the remainder of the LCI study area, which also offers important opportunities for reinvestment that complement the qualities of City Center and adjacent neighborhoods. A grant from the Atlanta Regional Commission (ARC) supported the joint planning process that created this update and the City Center Master Plan, which is available as a companion document. Joint objectives, described on page vi, under LCI Plan Outcomes, include: • enhancing quality of life • promoting economic development • strengthening sense of community This LCI Plan establishes a framework for public and private action that capitalizes on new demographic and market trends. The LCI Plan will equip the City to fill unmet demand for an active, pedestrian-oriented downtown area that includes expanded transportation options. The following conditions have unlocked this unparalleled level of opportunity to create civic and economic value in the study area: • Real estate market interest in walkable, mixed-use development can transform the study area over time into a district with significant new housing, job and retail options—while enhancing the City’s fiscal position. • Public interest in parks,walkable streets and cultural events that bring people together can shape private investment helping to build a welcoming place full of life and community. • The City’s interest in and ability to make infrastructure investments and to update development policies to attract and support private investment can help address the issues of mixed-use development. • The City Center can attract new high value development in ways that preserve and enhance nearby traditional residential neighb

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/ It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/ It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributedGIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

Street vacations allow property owners to petition the Seattle City Council to acquire public right-of-way next to their property from the City. Street vacations “vacate” the public’s right to use a street and return it to private property. Street vacations are only applicable when there is an adjacent development project planned. The Street Vacation Policies state a preference for retaining right-of-way in neighborhood residential zones. In addition to the basic street purpose of access and utilities, streets in residential areas provide for things like open space, consistency in the development pattern, natural drainage, wildlife corridors and other things. For more information, please visit this City website.Displays data from CADASTRAL.LEGAL_STVACATE_PLGN_PV. Updated weekly.

Multifamily Properties - AssistedThis National Geospatial Data Asset (NGDA) dataset, shared as a Department of Housing and Urban Development (HUD) feature layer, displays rental housing properties with five or more dwelling units in the United States. Per HUD, "HUD's Multifamily Housing property portfolio consist primarily of rental housing properties with five or more dwelling units such as apartments or town houses, but can also be nursing homes, hospitals, elderly housing, mobile home parks, retirement service centers, and occasionally vacant land. HUD provides subsidies and grants to property owners and developers designed to promote the development and preservation of affordable rental units for low-income populations and those with special needs, such as the elderly and disabled". Tyler House in Washington, D.C.Data currency: current federal service (Multifamily Properties - Assisted)NGDAID: 183 (Assisted Housing - Multifamily Properties (Assisted) – National Geospatial Data Asset (NGDA))For more information, please visit: Office of Multifamily HousingSupport documentation: DD_HUD Assisted Multifamily PropertiesFor feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Real Property Theme Community. Per the Federal Geospatial Data Committee (FGDC), Real Property is defined as "the spatial representation (location) of real property entities, typically consisting of one or more of the following: unimproved land, a building, a structure, site improvements and the underlying land. Complex real property entities (that is "facilities") are used for a broad spectrum of functions or missions. This theme focuses on spatial representation of real property assets only and does not seek to describe special purpose functions of real property such as those found in the Cultural Resources, Transportation, or Utilities themes."For other NGDA Content: Esri Federal Datasets

This updated Listings tour allows for multiple viewpoints of the same location to be attributed to the record. the data has been delineated to derived more usable information that can be accessed in the popup. Users of this app can download images from this tour as well.

This dataset is OBSOLETE as of 12/3/2024 and will be removed from ArcGIS Online on 12/3/2025.An updated version of this dataset is available at Land Use FY2024.This data set derives from several sources, and is updated annually with data current through July 1 of the reported year. The primary source is a data dump from the VISION assessing data system, which provided data up to date as of January 1, 2012, and is supplemented by information from subsequent building permits and Development Logs. (Use codes provided by this system combine aspects of land use, tax status, and condominium status. In an effort to clarify land use type the data has been cleaned and subdivided to break the original use code into several different fields.) The data set has further been supplemented and updated with development information provided by building permits issued by the Inspectional Services Department and from data found in the Development Log publication. Information from these sources is added to the data set periodically. Land use status is up to date as of the Last Modified date.Differences From “Official” Parcel LayerThe Cambridge GIS system maintains a separate layer of land parcels reflecting up to date subdivision and ownership. The parcel data associated with the Land Use Data set differs from the “official” parcel layer in a number of cases. For that reason this separate parcel layer is provided to work with land use data in a GIS environment. See the Assessing Department’s Parcel layer for the most up-to-date land parcel boundaries.Table of Land Use CodesThe following table lists all land use code found in the data layer:Land Use CodeLand Use DescriptionCategory0101MXD SNGL-FAM-REMixed Use Residential0104MXD TWO-FAM-RESMixed Use Residential0105MXD THREE-FM-REMixed Use Residential0111MXD 4-8-UNIT-APMixed Use Residential0112MXD >8-UNIT-APTMixed Use Residential0121MXD BOARDING-HSMixed Use Residential013MULTIUSE-RESMixed Use Residential031MULTIUSE-COMMixed Use Commercial0340MXD GEN-OFFICEMixed Use Commercial041MULTIUSE-INDMixed Use Industrial0942Higher Ed and Comm MixedMixed Use Education101SNGL-FAM-RESResidential1014SINGLE FAM W/AUResidential104TWO-FAM-RESResidential105THREE-FM-RESResidential106RES-LAND-IMPTransportation1067RES-COV-PKGTransportation1114-8-UNIT-APTResidential112>8-UNIT-APTResidential113ASSISTED-LIVAssisted Living/Boarding House121BOARDING-HSEAssisted Living/Boarding House130RES-DEV-LANDVacant Residential131RES-PDV-LANDVacant Residential132RES-UDV-LANDVacant Residential1322RES-UDV-PARK (OS) LNVacant Residential140CHILD-CARECommercial300HOTELCommercial302INN-RESORTCommercial304NURSING-HOMEHealth316WAREHOUSECommercial323SH-CNTR/MALLCommercial324SUPERMARKETCommercial325RETAIL-STORECommercial326EATING-ESTBLCommercial327RETAIL-CONDOCommercial330AUTO-SALESCommercial331AUTO-SUPPLYCommercial332AUTO-REPAIRCommercial334GAS-STATIONCommercialLand Use CodeLand Use DescriptionCategory335CAR-WASHCommercial336PARKING-GARTransportation337PARKING-LOTTransportation340GEN-OFFICEOffice341BANKCommercial342MEDICAL-OFFCHealth343OFFICE-CONDOOffice345RETAIL-OFFICOffice346INV-OFFICEOffice353FRAT-ORGANIZCommercial362THEATRECommercial370BOWLING-ALLYCommercial375TENNIS-CLUBCommercial390COM-DEV-LANDVacant Commercial391COM-PDV-LANDVacant Commercial392COM-UDV-LANDVacant Commercial3922CRMCL REC LNDVacant Commercial400MANUFACTURNGIndustrial401WAREHOUSEIndustrial404RES-&-DEV-FCOffice/R&D406HIGH-TECHOffice/R&D407CLEAN-MANUFIndustrial409INDUST-CONDOIndustrial413RESRCH IND CNDIndustrial422ELEC GEN PLANTUtility424PUB UTIL REGUtility428GAS-CONTROLUtility430TELE-EXCH-STAUtility440IND-DEV-LANDVacant Industrial442IND-UDV-LANDVacant Industrial920ParklandsPublic Open Space930Government OperationsGovernment Operations934Public SchoolsEducation940Private Pre & Elem SchoolEducation941Private Secondary SchoolEducation942Private CollegeHigher Education9421Private College Res UnitsEducation Residential943Other Educ & Research OrgHigher EducationLand Use CodeLand Use DescriptionCategory953CemeteriesCemetery955Hospitals & Medical OfficHealth956MuseumsHigher Education957Charitable ServicesCharitable/Religious960ReligiousCharitable/Religious971Water UtilityUtility972Road Right of WayTransportation975MBTA/RailroadTransportation9751MBTA/RailroadTransportation995Private Open SpacePrivately-Owned Open SpaceExplore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription ML type: Stringwidth: 16precision: 0 Map-Lot: This a unique parcel identifier found in the deed and used by the Assessing data system. In a few cases, where parcels have been subdivided subsequent to January 1, 2012, a placeholder Map-Lot number is assigned that differs from that used elsewhere.

MAP type: Stringwidth: 5precision: 0 This Map portion of the unique parcel identifier found in the deed and used by the Assessing data system. In a few cases, where parcels have been subdivided subsequent to January 1, 2012, a placeholder Map-Lot number is assigned that differs from that used elsewhere.

LOT type: Stringwidth: 5precision: 0 This is the Lot portion of the unique parcel identifier found in the deed and used by the Assessing data system. In a few cases, where parcels have been subdivided subsequent to January 1, 2012, a placeholder Map-Lot number is assigned that differs from that used elsewhere.

Location type: Stringwidth: 254precision: 0 In the great majority of cases this is the street address of the parcel as it is recorded in the Registry of Deed record. In instances where edits were made to the base parcel layer the best address available at the time is employed.

LandArea type: Doublewidth: 8precision: 15

LUCode type: Stringwidth: 254precision: 0 The four digit text string in this field indicates the primary usage of a parcel. While the codes are based on the standard Massachusetts assessing land use classification system, they differ in a number of cases; the coding system used here is unique to this data set. Note that other minor uses may occur on a property and, in some cases, tenants may introduce additional uses not reflected here (eg, office space used as a medical office, home based businesses).

LUDesc type: Stringwidth: 254precision: 0 The short description gives more detail about the specific use indicated by the Land Use Code. Most descriptions are taken from the standard Massachusetts assessing land use classification system.

Category type: Stringwidth: 254precision: 0 This broader grouping of land uses can be used to map land use data. You can find the land use data mapped at: https://www.cambridgema.gov/CDD/factsandmaps/mapgalleries/othermaps

ExistUnits type: Doublewidth: 8precision: 15 This value indicates the number of existing residential units as of July 1 of the reported year. A residential unit may be a house, an apartment, a mobile home, a group of rooms or a single room that is occupied (or, if vacant, intended for occupancy) as separate living quarters. This includes units found in apartment style graduate student housing residences and rooms in assisted living facilities and boarding houses are treated as also housing units. The unit count does not include college or graduate student dormitories, nursing home rooms, group homes, or other group quarters living arrangements.

MixedUseTy type: Stringwidth: 254precision: 0 Two flags are used for this field. “Groundfloor” indicates that a commercial use is found on the ground floor of the primary building, and upper floors are used for residential purposes. “Mixed” indicates that two or more uses are found throughout the structure or multiple structures on the parcel, one of which is residential.

GQLodgingH type: Stringwidth: 254precision: 0 A value of “Yes” indicates that the primary use of the property is as a group quarters living arrangement. Group quarters are a place where people live or stay, in a group living arrangement, that is owned or managed by an entity or organization providing housing and/or services for the residents. Group quarters include such places as college residence halls, residential treatment centers, skilled nursing facilities, group homes, military barracks, correctional facilities, and workers’ dormitories.

Most university dormitories are included under the broader higher education land use code, as most dormitories are included in the larger parcels comprising the bulk of higher education campuses.

GradStuden type: Stringwidth: 254precision: 0 A value of “Yes” indicates the parcel is used to house graduate students in apartment style units. Graduate student dormitories are treated as a higher education land use.

CondoFlag type: Stringwidth: 254precision: 0 “Yes” indicates that the parcel is owned as a condominium. Condo properties can include one or more uses, including residential, commercial, and parking. The great majority of such properties in Cambridge are residential only.

TaxStatus type: Stringwidth: 254precision: 0 A value indicates that the parcel is not subject to local property taxes. The following general rules are employed to assign properties to subcategories, though special situations exist in a number of cases.

o Authority: Properties owned the Cambridge Redevelopment Authority and Cambridge Housing Authority. o City: Properties owned by the City of Cambridge or cemetery land owned by the Town of Belmont. o Educ: Includes properties used for education purposes, ranging from pre-schools to university research facilities. (More detail about the level of education can be found using the Land Use Code.) o Federal: Properties owned by the federal government, including the Post Office. Certain properties with assessing data indicating Cambridge Redevelopment Authority ownership are in fact owned by the federal government as part of the Volpe Transportation Research Center and are so treated here. o Other: Nontaxable properties owned by a nonprofit organization and not