We are also including tabular version that’s slightly more comprehensive (would include anything that didn’t join to the parcel basefile due to lot alterations or resubdivisions since 2023 and/or due to parcels comprised of condos). There are approximately 200 records that don't join to the spatial parcel file and some additional that are null in the spatial parcel file, altogether around 560 total. This Excel file can be downloaded HERE, and does not contain the latitude and longitude information.Data Dictionary:Attribute LabelDefinitionSourceTAX_IDUnique 26 character property tax identification numberOnondaga County PlanningPRINTKEYAbbreviated tax identification number (section-block-lot)Onondaga County PlanningADDRESSNUMProperty’s physical street addressOnondaga County PlanningADDRESSNAMProperty’s physical street nameOnondaga County PlanningTAX_ID_1City Tax ID number (26 digit number used for parcel mapping)City of Syracuse - AssessmentSBLProperty Tax Map Number (Section, Block, Lot)City of Syracuse - AssessmentPNUMBRProperty Number (10 digit number)City of Syracuse - AssessmentStNumParcel street numberCity of Syracuse - AssessmentStNameParcel street nameCity of Syracuse - AssessmentFullAddressStreet number and street nameCity of Syracuse - AssessmentZipParcel zip codeCity of Syracuse - Assessmentdesc_1Lot description including dimensionsCity of Syracuse - Assessmentdesc_2Lot description including dimensionsCity of Syracuse - Assessmentdesc_3Lot description including dimensionsCity of Syracuse - AssessmentSHAPE_IND City of Syracuse - AssessmentLUC_parcelNew York State property type classification code assigned by assessor during each roll categorizing the property by use. For more details: https://www.tax.ny.gov/research/property/assess/manuals/prclas.htmCity of Syracuse - AssessmentLU_parcelNew York State property type classification nameCity of Syracuse - AssessmentLUCat_OldLegacy land use category that corresponds to the overarching NYS category, i.e. all 400s = commercial, all 300s = vacant land, etc.NAland_avLand assessed valueCity of Syracuse - Assessmenttotal_avFull assessed valueCity of Syracuse - AssessmentOwnerProperty owner name (First, Initial, Last, Suffix)City of Syracuse - AssessmentAdd1_OwnPOBoxProperty owner mailing address (PO Box)City of Syracuse - AssessmentAdd2_OwnStAddProperty owner mailing address (street number, street name, street direction)City of Syracuse - AssessmentAdd3_OwnUnitInfoProperty owner mailing address unit info (unit name, unit number)City of Syracuse - AssessmentAdd4_OwnCityStateZipProperty owner mailing address (city, state or country, zip code)City of Syracuse - AssessmentFRONTFront footage for square or rectangular shaped lots and the effective front feet on irregularly shaped lots in feetCity of Syracuse - AssessmentDEPTHActual depth of rectangular shaped lots in feet (irregular lots are usually measured in acres or square feet)City of Syracuse - AssessmentACRESNumber of acres (where values were 0, acreage calculated as FRONT*DEPTH)/43560)City of Syracuse - Assessmentyr_builtYear built. Where year built was "0" or null, effective year built is given. (Effective age is determined by comparing the physical condition of one building with that of other like-use, newer buildings. Effective age may or may not represent the actual year built; if there have been constant upgrades or excellent maintenance this may be more recent than the original year built.)City of Syracuse - Assessmentn_ResUnitsNumber of residential unitsNA - Calculated fieldIPSVacantIs it a vacant structure? ("Commercial" or "Residential" = Yes; null = No)City of Syracuse - Division of Code EnforcementIPS_ConditionProperty Condition Score assigned to vacant properties by housing inspectors during routine vacant inspections (1 = Worst; 5 = Best)City of Syracuse - Division of Code EnforcementNREligibleNational Register of Historic Places Eligible ("NR Eligible (SHPO)," or "NR Listed")City of Syracuse - Neighborhood and Business DevelopmentLPSSLocally Protected Site Status ("Eligible/Architecturally Significant" or "Local Protected Site or Local District")City of Syracuse - Neighborhood and Business DevelopmentWTR_ACTIVEWater activity code ("I" = Inactive; "A" = Active)City of Syracuse - WaterRNIIs property located in Resurgent Neighborhood Initiative (RNI) Area? (1 = Yes; 0 = No)City of Syracuse - Neighborhood and Business DevelopmentDPW_QuadGeographic quadrant property is located in. Quadrants are divided Northwest, Northeast, Southwest, and Southeast based on property location in relation to I-81 and I-690. DPW uses the quad designation for some types of staff assignments.City of Syracuse - Department of Public WorksTNT_NAMETNT Sector property is located inCity of Syracuse - Neighborhood and Business DevelopmentNHOODCity NeighborhoodSyracuse-Onondaga County Planning Agency (SOCPA)NRSAIs property located in Neighborhood Revitalization Strategy Area (NRSA)? (1 = Yes; 0 = No)City of Syracuse - Neighborhood and Business DevelopmentDOCE_AreaGeographic boundary use to assign Division of Code Enforcement casesCity of Syracuse - Neighborhood and Business DevelopmentZONE_DIST_PREVFormer zoning district codeSyracuse-Onondaga County Planning Agency (SOCPA)REZONEReZone designation (adopted June 2023)City of Syracuse - Neighborhood and Business DevelopmentNew_CC_DISTCurrent Common Council District property is located inOnondaga County Board of ElectionsCTID_2020Census Tract ID (2020)U.S. Census BureauCTLAB_2020Census Tract Label (2020)U.S. Census BureauCT_2020Census Tract (2020)U.S. Census BureauSpecNhoodIs property located in a special Neighborhood historic preservation district? (1 = Yes; 0 or null = No)Syracuse-Onondaga County Planning Agency (SOCPA)InPDIs property located in preservation district? (1 = Yes; 0 or null = No)Syracuse-Onondaga County Planning Agency (SOCPA)PDNAMEPreservation District nameSyracuse-Onondaga County Planning Agency (SOCPA)ELECT_DISTElection district numberOnondaga County Board of ElectionsCITY_WARDCity ward numberOnondaga County Board of ElectionsCOUNTY_LEGOnondaga County Legislative District number (as of Dec 2022)Onondaga County Board of ElectionsNYS_ASSEMBNew York State Assembly District number (as of Dec 2022)Onondaga County Board of ElectionsNYS_SENATENew York State Senate District number (as of Dec 2022)Onondaga County Board of ElectionsUS_CONGRUnited States Congressional District numberOnondaga County Board of Elections

We constructed a time-series spatial dataset of parcel boundaries for the period 1962-2005, in roughly 4-year intervals, by digitizing historical plat maps for Dane County and combining them with the 2005 GIS digital parcel dataset. The resulting datasets enable the consistent tracking of subdivision and development for all parcels over a given time frame. The process involved 1) dissolving and merging the 2005 digital Dane County parcel dataset based on contiguity and name, 2) further merging 2005 parcels based on the hard copy 2005 Plat book, and then 3) the reverse chronological merging of parcels to reconstruct previous years, at 4-year intervals, based on historical plat books. Additional land use information such as 1) whether a structure was actually constructed (using the companion digitized aerial photo dataset), 2) cover crop, and 3) permeable surface area, can be added to these datasets at a later date.

Attachment regarding 1. A rezoning request by Morgan Property Group on Parcels 2719, 2720, 2721, 69884, 60612, 2508, from R-1 Residential to CD-CB Conditional District Community Business for a retail shopping center with specific uses prohibited. The total accumulative parcel totals is approximately 27.53 acres.

Using a variety of datasets, the Martha's Vineyard Commission identified land on Martha's Vineyard that is either: (a) Fully Developed (can't be subdivided for additional development); (b) Conserved; (c) Available for Development (land is currently vacant); or (d) Potentially Available for Development (the land presently has some development but could be subdivided per current zoning). Wetlands are regarded as Conserved Land. Potentially Available land was determined using parcel boundaries, current zoning, and existing structures using the CommunityViz software.The most recent datasets available at the time of analysis were utilized to compile this dataset. Parcel data all complies with the MassGIS Level 3 parcel data standard; Structures are per aerial photo interpretation by MassGIS; Conserved Land is compiled by the MVC from input from the Island's Conservation Partnership; Zoning Boundaries are delineated by the MVC based on the district's descriptions in the Town's Zoning Bylaws.

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)

The planning map includes the Buckeye Planning Area, Parcels, Annexations, Community Master Plans and Planned Area Developments, Subdivisions, Subdivision Phases, Zoning, General Plan Land Use, Downtown Incentive District and Luke Air Force Base layers. Parcels are scale dependent and draw when you zoom into an area of interest on the map. This application is enabled to allow searching by address through ESRI's database, APN through the parcel layer and for the names of community master plans, subdivisions and subdivision phases.

Polygon feature class. These property parcel polygons show land designated as a separate and distinct parcel on a legally recorded subdivision plan or description filed in the Land Registry Office, has principal frontage upon public street or place. Updated as an ongoing process.