Internal view of the parcel layer. This view contains all the attributes that can be seen by County employees.There are approximately 51,300 real property parcels in Napa County. Parcels delineate the approximate boundaries of property ownership as described in Napa County deeds, filed maps, and other source documents. GIS parcel boundaries are maintained by the Information Technology Services GIS team. Assessor Parcel Maps are created and maintained by the Assessor Division Mapping Section. Each parcel has an Assessor Parcel Number (APN) that is its unique identifier. The APN is the link to various Napa County databases containing information such as owner name, situs address, property value, land use, zoning, flood data, and other related information. Data for this map service is sourced from the Napa County Parcels dataset which is updated nightly with any recent changes made by the mapping team. There may at times be a delay between when a document is recorded and when the new parcel boundary configuration and corresponding information is available in the online GIS parcel viewer.From 1850 to early 1900s assessor staff wrote the name of the property owner and the property value on map pages. They began using larger maps, called “tank maps” because of the large steel cabinet they were kept in, organized by school district (before unification) on which names and values were written. In the 1920s, the assessor kept large books of maps by road district on which names were written. In the 1950s, most county assessors contracted with the State Board of Equalization for board staff to draw standardized 11x17 inch maps following the provisions of Assessor Handbook 215. Maps were originally drawn on linen. By the 1980’s Assessor maps were being drawn on mylar rather than linen. In the early 1990s Napa County transitioned from drawing on mylar to creating maps in AutoCAD. When GIS arrived in Napa County in the mid-1990s, the AutoCAD images were copied over into the GIS parcel layer. Sidwell, an independent consultant, was then contracted by the Assessor’s Office to convert these APN files into the current seamless ArcGIS parcel fabric for the entire County. Beginning with the 2024-2025 assessment roll, the maps are being drawn directly in the parcel fabric layer.Parcels in the GIS parcel fabric are drawn according to the legal description using coordinate geometry (COGO) drawing tools and various reference data such as Public Lands Survey section boundaries and road centerlines. The legal descriptions are not defined by the GIS parcel fabric. Any changes made in the GIS parcel fabric via official records, filed maps, and other source documents are uploaded overnight. There is always at least a 6-month delay between when a document is recorded and when the new parcel configuration and corresponding information is available in the online parcel viewer for search or download.Parcel boundary accuracy can vary significantly, with errors ranging from a few feet to several hundred feet. These distortions are caused by several factors such as: the map projection - the error derived when a spherical coordinate system model is projected into a planar coordinate system using the local projected coordinate system; and the ground to grid conversion - the distortion between ground survey measurements and the virtual grid measurements. The aim of the parcel fabric is to construct a visual interpretation that is adequate for basic geographic understanding. This digital data is intended for illustration and demonstration purposes only and is not considered a legal resource, nor legally authoritative.SFAP & CFAP DISCLAIMER: Per the California Code, RTC 606. some legal parcels may have been combined for assessment purposes (CFAP) or separated for assessment purposes (SFAP) into multiple parcels for a variety of tax assessment reasons. SFAP and CFAP parcels are assigned their own APN number and primarily result from a parcel being split by a tax rate area boundary, due to a recorded land use lease, or by request of the property owner. Assessor parcel (APN) maps reflect when parcels have been separated or combined for assessment purposes, and are one legal entity. The goal of the GIS parcel fabric data is to distinguish the SFAP and CFAP parcel configurations from the legal configurations, to convey the legal parcel configurations. This workflow is in progress. Please be advised that while we endeavor to restore SFAP and CFAP parcels back to their legal configurations in the primary parcel fabric layer, SFAP and CFAP parcels may be distributed throughout the dataset. Parcels that have been restored to their legal configurations, do not reflect the SFAP or CFAP parcel configurations that correspond to the current property tax delineations. We intend for parcel reports and parcel data to capture when a parcel has been separated or combined for assessment purposes, however in some cases, information may not be available in GIS for the SFAP/CFAP status of a parcel configuration shown. For help or questions regarding a parcel’s SFAP/CFAP status, or property survey data, please visit Napa County’s Surveying Services or Property Mapping Information. For more information you can visit our website: When a Parcel is Not a Parcel | Napa County, CA

We are also including a 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). This Excel file can be downloaded HERE, and does not contain the latitude and longitude information.Data Dictionary: Attribute Label Definition Source

TAX_ID Unique 26 character property tax identification number Onondaga County Planning

PRINTKEY Abbreviated tax identification number (section-block-lot) Onondaga County Planning

ADDRESSNUM Property’s physical street address Onondaga County Planning

ADDRESSNAM Property’s physical street name Onondaga County Planning

LAT Latitude Onondaga County Planning

LONG Longitude Onondaga County Planning

TAX_ID_1 City Tax ID number (26 digit number used for parcel mapping) City of Syracuse - Assessment

SBL Property Tax Map Number (Section, Block, Lot) City of Syracuse - Assessment

PNUMBR Property Number (10 digit number) City of Syracuse - Assessment

StNum Parcel street number City of Syracuse - Assessment

StName Parcel street name City of Syracuse - Assessment

FullAddress Street number and street name City of Syracuse - Assessment

Zip Parcel zip code City of Syracuse - Assessment

desc_1 Lot description including dimensions City of Syracuse - Assessment

desc_2 Lot description including dimensions City of Syracuse - Assessment

desc_3 Lot description including dimensions City of Syracuse - Assessment

SHAPE_IND

City of Syracuse - Assessment

LUC_parcel New 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.htm City of Syracuse - Assessment

LU_parcel New York State property type classification name City of Syracuse - Assessment

LUCat_Old Legacy land use category that corresponds to the overarching NYS category, i.e. all 400s = commercial, all 300s = vacant land, etc. NA

land_av Land assessed value City of Syracuse - Assessment

total_av Full assessed value City of Syracuse - Assessment

Owner Property owner name (First, Initial, Last, Suffix) City of Syracuse - Assessment

Add1_OwnPOBox Property owner mailing address (PO Box) City of Syracuse - Assessment

Add2_OwnStAdd Property owner mailing address (street number, street name, street direction) City of Syracuse - Assessment

Add3_OwnUnitInfo Property owner mailing address unit info (unit name, unit number) City of Syracuse - Assessment

Add4_OwnCityStateZip Property owner mailing address (city, state or country, zip code) City of Syracuse - Assessment

FRONT Front footage for square or rectangular shaped lots and the effective front feet on irregularly shaped lots in feet City of Syracuse - Assessment

DEPTH Actual depth of rectangular shaped lots in feet (irregular lots are usually measured in acres or square feet) City of Syracuse - Assessment

ACRES Number of acres (where values were 0, acreage calculated as FRONT*DEPTH)/43560) City of Syracuse - Assessment

yr_built Year 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 - Assessment

n_ResUnits Number of residential units NA - Calculated field

IPSVacant Is it a vacant structure? ("Commercial" or "Residential" = Yes; null = No) City of Syracuse - Division of Code Enforcement

IPS_Condition Property Condition Score assigned to vacant properties by housing inspectors during routine vacant inspections (1 = Worst; 5 = Best) City of Syracuse - Division of Code Enforcement

NREligible National Register of Historic Places Eligible ("NR Eligible (SHPO)," or "NR Listed") City of Syracuse - Neighborhood and Business Development

LPSS Locally Protected Site Status ("Eligible/Architecturally Significant" or "Local Protected Site or Local District") City of Syracuse - Neighborhood and Business Development

WTR_ACTIVE Water activity code ("I" = Inactive; "A" = Active) City of Syracuse - Water

RNI Is property located in Resurgent Neighborhood Initiative (RNI) Area? (1 = Yes; 0 = No) City of Syracuse - Neighborhood and Business Development

DPW_Quad Geographic 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 Works

TNT_NAME TNT Sector property is located in City of Syracuse - Neighborhood and Business Development

NHOOD City Neighborhood Syracuse-Onondaga County Planning Agency (SOCPA)

NRSA Is property located in Neighborhood Revitilization Strategy Area (NRSA)? (1 = Yes; 0 = No) City of Syracuse - Neighborhood and Business Development

DOCE_Area Geographic boundary use to assign Division of Code Enforcement cases City of Syracuse - Neighborhood and Business Development

ZONE_DIST_PREV Former zoning district code Syracuse-Onondaga County Planning Agency (SOCPA)

REZONE ReZone designation (adopted June 2023) City of Syracuse - Neighborhood and Business Development

New_CC_DIST Current Common Council District property is located in Onondaga County Board of Elections

CTID_2020 Census Tract ID (2020) U.S. Census Bureau

CTLAB_2020 Census Tract Label (2020) U.S. Census Bureau

CT_2020 Census Tract (2020) U.S. Census Bureau

SpecNhood Is property located in a special Neighborhood historic preservation district? (1 = Yes; 0 or null = No) Syracuse-Onondaga County Planning Agency (SOCPA)

InPD Is property located in preservation district? (1 = Yes; 0 or null = No) Syracuse-Onondaga County Planning Agency (SOCPA)

PDNAME Preservation District name Syracuse-Onondaga County Planning Agency (SOCPA)

ELECT_DIST Election district number Onondaga County Board of Elections

CITY_WARD City ward number Onondaga County Board of Elections

COUNTY_LEG Onondaga County Legislative District number (as of Dec 2022) Onondaga County Board of Elections

NYS_ASSEMB New York State Assembly District number (as of Dec 2022) Onondaga County Board of Elections

NYS_SENATE New York State Senate District number (as of Dec 2022) Onondaga County Board of Elections

US_CONGR United States Congressional District number Onondaga County Board of Elections

Dataset Contact InformationOrganization: Neighborhood & Business DevelopmentPosition:Data Program ManagerCity:Syracuse, NYE-Mail Address:opendata@syrgov.netPlease note there is a data quality issue in this iteration with the preservation district (“InPD,” “PDNAME”) and special neighborhood historic district (“SpecNhood”) fields erroneously showing null results for all parcels.

This data provides the geographic location for parcel boundary lines within the jurisdiction of the Carteret County, NC and is based on recorded surveys and deeds. This dataset is maintained by the Carteret County Mapping/Land Records Division. Data is updated on an as needed basis. The description for each field name in the layer is included below:PIN: first 8 digits of PIN15; this would include the MAPNUM, SUBMAP, and BLOCKMAPNUM: first 4 digits of PIN15BLOCK: two digit block number found on old mylars; also digits number 7 and 8 of the PIN15PDOT: part of the PIN15; digits number 9-12 (before the last 3 digits of the PIN15)MAPNAM: first 6 digits of PIN15 map and submapAll fields above are parts of the PIN15 (primary parcel identifier), which is determined by the location of the centroid of a parcel within the State Plane NC Grid SystemCONDO_: condo unit number and also the last 3 digits of the PIN15MOTHER: if a parcel was split from another parcel, the new parcel number would be considered the child and the original would be considered the parent or motherPRID: old parcel number style based on prior mapping system before NC Grid system mapsPIN15: the primary tax parcel identifierWHAT: acreage calculated within ArcGISDeedDate_2: unused fieldOWNER: tax parcel ownerDBOOK: deed book containing most recent deed to propertyDPAGE: deed page containing most recent deed to propertyDDATE: most recent deed date for propertySALE_PRICE: recorded sale priceLAND_VALUE: value of land on propertySTRUC_VAL: value of structure(s) on propertyOTHER_VAL: other value of the propertyBLT_CONDO: year condo was builtMAIL_APT: property owner mailing address unitMAIL_HOUSE: property owner mailing address house numberMAIL_DIR: property owner mailing address street directionalMAIL_ST: property owner mailing address street nameMAIL_STTYP: property owner mailing address street suffix (e.g. Dr., St. etc.)MAIL_CITY: mailing address cityMAIL_STATE: mailing address stateMAIL_ZI4: mailing address zip +4MAIL_ZI5: mailing address zip codeMAIL_ADD2: mailing address additional part (e.g. P.O. Box)TOWNSHIP: township codeCITY_LIMIT: the city limit that the parcel is withinNBHD: Neighborhood codeFIRE_DIST: fire district that the parcel is withinRESCUE_DST: rescue district that the parcel is withinLEGAL_DSC: legal descriptionTOTAL_ACR: total deeded acreageY_BLT_HOUS: year house was builtTOT_SQ_FT: total square footage of structure on propertyROLL_TYPE: roll type of property (regularly taxed property or tax-exempt)BATHROOMS: number of bathroomsBEDROOMS: number of bedroomsSITE_HOUSE: site address house numberSITE_ST: site address street nameSITE_DIR: site address street directionalSITE_STTYP: site address street suffix (e.g. Dr., St., etc.)SITE_APTNO: site address unitSITE_CITY: site address city/communityExpr1: old deed date field; not usedTotal_EMV: total estimated tax valueUse_Val: plat book containing survey of propertyDef_Val: plat page containing survey of propertyMAIL_APT_N: mailing address unit (not used)CONDO_SQFT: condo unit square footageDistrict: district code (indicates the community)CONDO_NUM: condo number of floorsTowns_Desc: township nameTrue_City: true city Use_code: land use codeUse_desc: land use descriptionPerm_N1: permit #1Perm_N2: permit #2Perm_Ty1: permit #1 typePerm_Ty2: permit #2 typePerm_De1: permit #1 descriptionPerm_De2: permit #2 descriptionPerm_Is1: permit #1 issue datePerm_Is2: permit #2 issue dateSCH_Dat1: permit #1 scheduled completion dateSCH_Dat2: permit #2 scheduled completion dateACTL_DA1: permit #1 actual completion date ACTL_DA2: permit #2 actual completion dateFondTyp1: foundation type 1FondDes1: foundation type 1 descriptionFondTyp2: foundation type 2FondDes2: foundation type 2 descriptionExWllTyp1: exterior wall type 1ExWllDes1: exterior wall type 1 descriptionExWllTyp2: exterior wall type 2ExWllDes2: exterior wall type 2 descriptionHeatTyp1: heating type 1HeatDes1: heating type 1 descriptionHeatTyp2: heating type 2HeatDes2: heating type 2 descriptionFlrTyp1: flooring type 1FlrDes1: flooring type 1 descriptionFlrTyp2: flooring type 2FlrDes2: flooring type 2 descriptionCondCod: condition codeCondDes: condition descriptionRStrTyp1: roof structure type 1RStrDes: roof structure type 1 descriptionRStrTyp2: roof structure type 2RStrDes2: roof structure type 2 descriptionRCovTyp1: roof covering type 1RCovDes1: roof covering type 1 descriptionRCovTyp2: roof covering type 2RCovDes2: roof covering type 2 descriptionaicuz: stands for "Air Installation Compatible Use Zone"; planning zones pertaining to military air bases and the surrounding real estateRisk_level: risk level for military air plane accident potential within the AICUZ zonesNoise_lvl: noise level zones surrounding military air basesHtdSqFt: heated square footage of structure on the property

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

Webmap of Allegheny municipalities and parcel data. Zoom for a clickable parcel map with owner name, property photograph, and link to the County Real Estate website for property sales information.

Data Dictionary: Attribute Label Definition Source

TAX_ID Unique 26 character property tax identification number Onondaga County Planning

SHAPE_Leng Shape length NA - Calculated field

SHAPE_Area Shape area NA - Calculated field

PRINTKEY Abbreviated tax identification number (section-block-lot) Onondaga County Planning

ADDRESSNUM Property’s physical street address Onondaga County Planning

ADDRESSNAM Property’s physical street name Onondaga County Planning

SBL Property Tax Map Number (Section, Block, Lot) City of Syracuse - Assessment

PNUMBR Property Number (10 digit number) City of Syracuse - Assessment

StNum Parcel street number City of Syracuse - Assessment

StName Parcel street name City of Syracuse - Assessment

FullAddress Street number and street name City of Syracuse - Assessment

Zip Parcel zip code City of Syracuse - Assessment

desc_1 Lot description including dimensions City of Syracuse - Assessment

desc_2 Lot description including dimensions City of Syracuse - Assessment

desc_3 Lot description including dimensions City of Syracuse - Assessment

SHAPE_IND

City of Syracuse - Assessment

LUC_parcel New 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.htm City of Syracuse - Assessment

LU_parcel New York State property type classification name City of Syracuse - Assessment

LUCat_Old Legacy land use category that corresponds to the overarching NYS category, i.e. all 400s = commercial, all 300s = vacant land, etc. NA

land_av Land assessed value City of Syracuse - Assessment

total_av Full assessed value City of Syracuse - Assessment

Owner Property owner name (First, Initial, Last, Suffix) City of Syracuse - Assessment

OwnerFullAddress Property owner assessed address (street number, street name, street direction [or PO Box], unit name, unit number, city, state or country, zip code) City of Syracuse - Assessment

Add1_OwnPOBox Property owner mailing address (PO Box) City of Syracuse - Assessment

Add2_OwnStAdd Property owner mailing address (street number, street name, street direction) City of Syracuse - Assessment

Add3_OwnUnitInfo Property owner mailing address unit info (unit name, unit number) City of Syracuse - Assessment

Add4_OwnCityStateZip Property owner mailing address (city, state or country, zip code) City of Syracuse - Assessment

FRONT Front footage for square or rectangular shaped lots and the effective front feet on irregularly shaped lots in feet City of Syracuse - Assessment

DEPTH Actual depth of rectangular shaped lots in feet (irregular lots are usually measured in acres or square feet) City of Syracuse - Assessment

ACRES Number of acres (where values were 0, acreage calculated as FRONT*DEPTH)/43560) City of Syracuse - Assessment

yr_built Year 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 - Assessment

n_ResUnits Number of residential units NA - Calculated field

IPSVacant Is it a vacant structure? ("Commercial" or "Residential" = Yes; null = No) City of Syracuse - Division of Code Enforcement

IPS_Condition Property Condition Score assigned to vacant properties by housing inspectors during routine vacant inspections (1 = Worst; 5 = Best) City of Syracuse - Division of Code Enforcement

NREligible National Register of Historic Places Eligible ("NR Eligible (SHPO)," or "NR Listed") City of Syracuse - Neighborhood and Business Development

LPSS Locally Protected Site Status ("Eligible/Architecturally Significant" or "Local Protected Site or Local District") City of Syracuse - Neighborhood and Business Development

WTR_ACTIVE Water activity code ("I" = Inactive; "A" = Active) City of Syracuse - Water

RNI Is property located in Resurgent Neighborhood Initiative (RNI) Area? (1 = Yes; 0 = No) City of Syracuse - Neighborhood and Business Development

DPW_Quad Geographic 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 Works

DPW_Sani DPW sanitation trash and recycling pick-up day (trash service weekly, recycling biweekly) City of Syracuse - Department of Public Works

DPW_Recycle DPW recycling biweekly pick-up group (either Week A or Week B), collection occurs every other week City of Syracuse - Department of Public Works

TNT_NAME TNT Sector property is located in City of Syracuse - Neighborhood and Business Development

NHOOD City Neighborhood Syracuse-Onondaga County Planning Agency (SOCPA)

NRSA Is property located in Neighborhood Revitilization Strategy Area (NRSA)? (1 = Yes; 0 = No) City of Syracuse - Neighborhood and Business Development

DOCE_Insp1 Geographic boundary use to assign Division of Code Enforcement cases for housing inspectors City of Syracuse - Division of Code Enforcement

DOCE_Insp2 Geographic boundary use to assign Division of Code Enforcement cases for building inspectors City of Syracuse - Division of Code Enforcement

DOCE_Permit Geographic boundary use to assign Division of Code Enforcement cases for permit inspectors City of Syracuse - Division of Code Enforcement

DOCE_Comm Geographic boundary use to assign Division of Code Enforcement cases for commercial and electrical inspectors City of Syracuse - Division of Code Enforcement

FIRE_DIST Fire engine districts City of Syracuse - Fire Department

ZONE_DIST_PREV Former zoning district code Syracuse-Onondaga County Planning Agency (SOCPA)

REZONE ReZone designation (adopted June 2023, last updated 2024-12-17) City of Syracuse - Neighborhood and Business Development

CC_DIST Current Common Council District property is located in Onondaga County Board of Elections

CTID_2020 Census Tract ID (2020) U.S. Census Bureau

CTLAB_2020 Census Tract Label (2020) U.S. Census Bureau

CT_2020 Census Tract (2020) U.S. Census Bureau

SpecNhood Is property located in a special Neighborhood historic preservation district? (1 = Yes; 0 or null = No) Syracuse-Onondaga County Planning Agency (SOCPA)

InPD Is property located in preservation district? (1 = Yes; 0 or null = No) Syracuse-Onondaga County Planning Agency (SOCPA)

PDNAME Preservation District name Syracuse-Onondaga County Planning Agency (SOCPA)

ELECT_DIST Election district number Onondaga County Board of Elections

CITY_WARD City ward number Onondaga County Board of Elections

COUNTY_LEG Onondaga County Legislative District number (as of Dec 2024) Onondaga County Board of Elections

NYS_ASSEMB New York State Assembly District number (as of Dec 2024) Onondaga County Board of Elections

NYS_SENATE New York State Senate District number (as of Dec 2024) Onondaga County Board of Elections

US_CONGR United States Congressional District number Onondaga County Board of Elections

See full Data Guide here. Connecticut Parcels for Protected Open Space Mapping is a polygon feature-based layer that includes basic parcel-level information for some towns in Connecticut. This 2009 parcel layer includes information provided by individual municipalities. These parcel data are incomplete and out of date. The accuracy, currency and completeness of the data reflect the content of the data at the time DEEP acquired the data from the individual municipalities. Attribute information is comprised of values such as town name and map lot block number. These data are not updated by CT DEEP and should only be used as a general reference. Critical decisions involving parcel-level information should be based on more recently acquired information from the respective municipalities. These parcels are not to be considered legal boundaries such as boundaries determined from certain classified survey maps or deed descriptions. Parcel boundaries shown in this layer are based on information from municipalities used for property tax purposes. Largely due to differences in horizontal accuracy among various data layers, do not expect these parcel boundaries to line up exactly with or be properly postioned relative to features shown on other layers available from CT DEEP such as scanned USGS topography quadrangle maps, roads, hydrography, town boundaries, and even orthophotograpy. The data in the parcel layer was obtained from individual Connecticut municipalities. An effort was made to collect data once from each municipality. The data acquisition date for each set of municipally-supplied parcel data was not recorded and CT DEEP does not keep this information up-to-date. Consequently, these data are out-of-date, incomplete and do not reflect the current state of property ownership in these municipalities. These parcels are not to be considered legal boundaries such as boundaries determined from certain classified survey maps or deed descriptions. Parcel boundaries shown in this layer are based on information from municipalities used for property tax purposes. Parcel boundaries and attribute information have not been updated in this layer since the time the information was originally acquired by CT DEEP. For example, property boundaries are incorrect where subdivisions have occurred. Also, field attribute values are populated only if the information was supplied to CT DEEP. For example, parcels in some towns lack location (street name) information or possibly map lot block values. Therefore, field attributes are inconsistent, may include gaps, and do not represent complete sets of values among all towns. They should not be compared and analyzed across towns. It is emphasized that critical decisions involving parcel-level information be based on more recently obtained information from the respective municipalities. These data are only suitable for general reference purposes. Be cautious when using these data. Many Connecticut municipalities provide access to more up-to-date and more detailed property ownership information on the Internet. This dataset includes parcel information for the following towns: Andover, Ansonia, Ashford, Avon, Beacon Falls, Berlin, Bethany, Bethel, Bethlehem, Bloomfield, Bolton, Branford, Bridgewater, Brookfield, Brooklyn, Canaan, Canterbury, Canton, Chaplin, Cheshire, Chester, Clinton, Colchester, Colebrook, Columbia, Cornwall, Coventry, Cromwell, Danbury, Darien, Deep River, Derby, East Granby, East Haddam, East Hampton, East Hartford, East Lyme, East Windsor, Eastford, Ellington, Enfield, Essex, Farmington, Franklin, Glastonbury, Granby, Greenwich, Griswold, Groton, Guilford, Haddam, Hamden, Hartford, Hebron, Kent, Killingly, Killingworth, Lebanon, Ledyard, Lisbon, Litchfield, Lyme, Madison, Manchester, Mansfield, Marlborough, Meriden, Middlebury, Middlefield, Middletown, Milford,

Parcels and property data maintained and provided by Lee County Property Appraiser. This dataset includes condominium units. Property attribute data joined to parcel GIS layer by Lee County Government GIS.Projected coordinate system name: NAD_1983_StatePlane_Florida_West_FIPS_0902_FeetGeographic coordinate system name: GCS_North_American_1983

 Name
 Type
 Length
 Description


 STRAP
 String
 25
 17-digit Property ID (Section, Township, Range, Area, Block, Lot)


 BLOCK
 String
 10
 5-digit portion of STRAP (positions 9-13)


 LOT
 String
 8
 Last 4-digits of STRAP


 FOLIOID
 Double
 8
 Unique Property ID


 MAINTDATE
 Date
 8
 Date LeePA staff updated record


 MAINTWHO
 String
 20
 LeePA staff who updated record


 UPDATED
 Date
 8
 Data compilation date


 HIDE_STRAP
 String
 1
 Confidential parcel ownership


 TRSPARCEL
 String
 17
 Parcel ID sorted by Township, Range & Section


 DORCODE
 String
 2
 Department of Revenue property classification code


 CONDOTYPE
 String
 1
 Type of condominium: C (commercial) or R (residential)


 UNITOFMEAS
 String
 2
 Type of Unit of Measure (ex: AC=acre, LT=lot, FF=frontage in feet)


 NUMUNITS
 Double
 8
 Number of Land Units (units defined in UNITOFMEAS)


 FRONTAGE
 Integer
 4
 Road Frontage in Feet


 DEPTH
 Integer
 4
 Property Depth in Feet


 GISACRES
 Double
 8
 Total Computed Acres from GIS


 TAXINGDIST
 String
 3
 Taxing District of Property


 TAXDISTDES
 String
 60
 Taxing District Description


 FIREDIST
 String
 3
 Fire District of Property


 FIREDISTDE
 String
 60
 Fire District Description


 ZONING
 String
 10
 Zoning of Property


 ZONINGAREA
 String
 3
 Governing Area for Zoning


 LANDUSECOD
 SmallInteger
 2
 Land Use Code


 LANDUSEDES
 String
 60
 Land Use Description


 LANDISON
 String
 5
 BAY,CANAL,CREEK,GULF,LAKE,RIVER & GOLF


 SITEADDR
 String
 55
 Lee County Addressing/E911


 SITENUMBER
 String
 10
 Property Location - Street Number


 SITESTREET
 String
 40
 Street Name


 SITEUNIT
 String
 5
 Unit Number


 SITECITY
 String
 20
 City


 SITEZIP
 String
 5
 Zip Code


 JUST
 Double
 8
 Market Value


 ASSESSED
 Double
 8
 Building Value + Land Value


 TAXABLE
 Double
 8
 Taxable Value


 LAND
 Double
 8
 Land Value


 BUILDING
 Double
 8
 Building Value


 LXFV
 Double
 8
 Land Extra Feature Value


 BXFV
 Double
 8
 Building Extra Feature value


 NEWBUILT
 Double
 8
 New Construction Value


 AGAMOUNT
 Double
 8
 Agriculture Exemption Value


 DISAMOUNT
 Double
 8
 Disability Exemption Value


 HISTAMOUNT
 Double
 8
 Historical Exemption Value


 HSTDAMOUNT
 Double
 8
 Homestead Exemption Value


 SNRAMOUNT
 Double
 8
 Senior Exemption Value


 WHLYAMOUNT
 Double
 8
 Wholly Exemption Value


 WIDAMOUNT
 Double
 8
 Widow Exemption Value


 WIDRAMOUNT
 Double
 8
 Widower Exemption Value


 BLDGCOUNT
 SmallInteger
 2
 Total Number of Buildings on Parcel


 MINBUILTY
 SmallInteger
 2
 Oldest Building Built


 MAXBUILTY
 SmallInteger
 2
 Newest Building Built


 TOTALAREA
 Double
 8
 Total Building Area


 HEATEDAREA
 Double
 8
 Total Heated Area


 MAXSTORIES
 Double
 8
 Tallest Building on Parcel


 BEDROOMS
 Integer
 4
 Total Number of Bedrooms


 BATHROOMS
 Double
 8
 Total Number of Bathrooms / Not For Comm


 GARAGE
 String
 1
 Garage on Property 'Y'


 CARPORT
 String
 1
 Carport on Property 'Y'


 POOL
 String
 1
 Pool on Property 'Y'


 BOATDOCK
 String
 1
 Boat Dock on Property 'Y'


 SEAWALL
 String
 1
 Sea Wall on Property 'Y'


 NBLDGCOUNT
 SmallInteger
 2
 Total Number of New Buildings on ParcelTotal Number of New Buildings on Parcel


 NMINBUILTY
 SmallInteger
 2
 Oldest New Building Built


 NMAXBUILTY
 SmallInteger
 2
 Newest New Building Built


 NTOTALAREA
 Double
 8
 Total New Building Area


 NHEATEDARE
 Double
 8
 Total New Heated Area


 NMAXSTORIE
 Double
 8
 Tallest New Building on Parcel


 NBEDROOMS
 Integer
 4
 Total Number of New Bedrooms


 NBATHROOMS
 Double
 8
 Total Number of New Bathrooms/Not For Comm


 NGARAGE
 String
 1
 New Garage on Property 'Y'


 NCARPORT
 String
 1
 New Carport on Property 'Y'


 NPOOL
 String
 1
 New Pool on Property 'Y'


 NBOATDOCK
 String
 1
 New Boat Dock on Property 'Y'


 NSEAWALL
 String
 1
 New Sea Wall on Property 'Y'


 O_NAME
 String
 30
 Owner Name


 O_OTHERS
 String
 120
 Other Owners


 O_CAREOF
 String
 30
 In Care Of Line


 O_ADDR1
 String
 30
 Owner Mailing Address Line 1


 O_ADDR2
 String
 30
 Owner Mailing Address Line 2


 O_CITY
 String
 30
 Owner Mailing City


 O_STATE
 String
 2
 Owner Mailing State


 O_ZIP
 String
 9
 Owner Mailing Zip


 O_COUNTRY
 String
 30
 Owner Mailing Country


 S_1DATE
 Date
 8
 Most Current Sale Date > $100.00


 S_1AMOUNT
 Double
 8
 Sale Amount


 S_1VI
 String
 1
 Sale Vacant or Improved


 S_1TC
 String
 2
 Sale Transaction Code


 S_1TOC
 String
 2
 Sale Transaction Override Code


 S_1OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_2DATE
 Date
 8
 Previous Sale Date > $100.00


 S_2AMOUNT
 Double
 8
 Sale Amount


 S_2VI
 String
 1
 Sale Vacant or Improved


 S_2TC
 String
 2
 Sale Transaction Code


 S_2TOC
 String
 2
 Sale Transaction Override Code


 S_2OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_3DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_3AMOUNT
 Double
 8
 Sale Amount


 S_3VI
 String
 1
 Sale Vacant or Improved


 S_3TC
 String
 2
 Sale Transaction Code


 S_3TOC
 String
 2
 Sale Transaction Override Code


 S_3OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_4DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_4AMOUNT
 Double
 8
 Sale Amount


 S_4VI
 String
 1
 Sale Vacant or Improved


 S_4TC
 String
 2
 Sale Transaction Code


 S_4TOC
 String
 2
 Sale Transaction Override Code


 S_4OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 LEGAL
 String
 255
 Full Legal Description (On Deed)


 GARBDIST
 String
 3
 County Garbage Hauling Area


 GARBTYPE
 String
 1
 County Garbage Pick-up Type


 GARBCOMCAT
 String
 1
 County Garbage Commercial Category


 GARBHEADER
 String
 1
 Garbage Header Code


 GARBUNITS
 Double
 8
 Number of Garbage Units


 CREATEYEAR

Data Dictionary: AttributeLabelDefinitionSourceTAX_IDUnique 26 character property taxOnondaga County PlanningPRINTKEYAbbreviated tax identification number (section-block-lot)Onondaga County PlanningEASTGRIDEast grid coordinate of centroid in feetOnondaga County PlanningNORTHGRIDNorth grid coordinate of centroid in feetOnondaga 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_INDCity of Syracuse - AssessmentLUC_parcelNew York State property type classification code assigned by assessor during each roll. 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. City of Syracuse - Neighborhood and Business Developmentland_avLand valueCity of Syracuse - Assessmenttotal_avFull valueCity of Syracuse - AssessmentOwnerProperty owner name (First, Initial, Last, Suffix)City of Syracuse - AssessmentAdd1_OwnPOProperty owner mailing address (PO Box)City of Syracuse - AssessmentAdd2_OwnStProperty owner mailing address (street number, street name, street direction)City of Syracuse - AssessmentAdd3_OwnUnProperty owner mailing address unit info (unit name, unit number)City of Syracuse - AssessmentAdd4_OwnCiProperty 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 - AssessmentDEPTH_1Actual depth of rectangular shaped lots in feet (irregular lots are usually measured in acres or square feet)City of Syracuse - AssessmentACRES_1Number of acres (where values were 0, acreage calculated as FRONT*DEPTH)/43560)City of Syracuse - Assessmentyr_builtYear builtCity of Syracuse - AssessmentIPSVacantIs it a vacant structure? ("Commercial" or "Residential" = Yes; null = No)City of Syracuse - Neighborhood and Business DevelopmentIPS_ConditProperty Condition Score assigned to vacant properties by housing inspectors during routine vacant inspections (1 = Worst; 5 = Best)City of Syracuse - Neighborhood and Business DevelopmentNREligibleNational 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 NeighborhoodCity of Syracuse - Neighborhood and Business DevelopmentNRSAIs property located in Neighborhood Revitilization 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_Former zoning district codeCity of Syracuse - Neighborhood and Business DevelopmentREZONEReZone designation (adopted June 2023)City of Syracuse - Neighborhood and Business DevelopmentNew_CC_DISTCurrent Common Council District property is located inCity of Syracuse - Neighborhood and Business DevelopmentCTID_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)City of Syracuse - Neighborhood and Business DevelopmentInPDIs property located in preservation district? (1 = Yes; 0 or null = No)City of Syracuse - Neighborhood and Business DevelopmentPDNAMEPreservation District nameCity of Syracuse - Neighborhood and Business DevelopmentELECT_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 ElectionsDataset Contact InformationOrganization: Neighborhood & Business DevelopmentPosition:Data Program ManagerCity:Syracuse, NYE-Mail Address:opendata@syrgov.net

Web App. Use the tabs provided to discover information about map features and capabilities. Link to Metadata. A variety of searches can be performed to find the parcel of interest. Use the Query Tool to build searches. Click Apply button at the bottom of the tool.Query by Name (Last First) (e.g. Bond James)Query by Address (e.g. 41 S Central)Query by Locator number (e.g. 21J411046)Search results will be listed under the Results tab. Click on a parcel in the list to zoom to that parcel. Click on the parcel in the map and scroll through the pop-up to see more information about the parcel. Click the ellipse in the Results tab or in the pop-up to view information in a table. Attribute information can be exported to CSV file. Build a custom Filter to select and map properties by opening the Parcels attribute table:1. Click the arrow tab at the bottom middle of the map to expand the attribute table window2. Click on the Parcels tab3. Check off Filter by map extent4. Open Options>Filter5. Build expressions as needed to filter by owner name or other variables6. Select the needed records from the returned list7. Click Zoom to which will zoom to the selected recordsPlease note that as the map zooms out detailed layers, such as the parcel boundaries will not display.In addition to Search capabilities, the following tools are provided:MeasureThe measure tool provides the capabilities to draw a point, line, or polygon on the map and specify the unit of measurement.DrawThe draw tool provides the capabilities to draw a point, line, or polygon on the map as graphics. PrintThe print tool exports the map to either a PDF or image file. Click Settings button to configure map or remove legend.Map navigation using mouse and keyboard:Drag to panSHIFT + CTRL + Drag to zoom outMouse Scroll Forward to zoom inMouse Scroll Backward to zoom outUse Arrow keys to pan+ key to zoom in a level- key to zoom out a levelDouble Click to Zoom inFAQsHow to select a parcel: Click on a parcel in the map, or use Query Tool to search for parcel by owner, address or parcel id.How to select more than one parcel: Go to Select Tool and choose options on Select button.How to clear selected parcel(s): Go to Select Tool and click Clear.

Please note: this data is live (updated nightly) to reflect the latest changes in the City's systems of record.Overview of the Data:This dataset is a polygon feature layer with the boundaries of all tax parcels owned by the City of Rochester. This includes all public parks, and municipal buildings, as well as vacant land and structures currently owned by the City. The data includes fields with features about each property including property type, date of sale, land value, dimensions, and more.About City Owned Properties:The City's real estate inventory is managed by the Division of Real Estate in the Department of Neighborhood and Business Development. Properties like municipal buildings and parks are expected to be in long term ownership of the City. Properties such as vacant land and vacant structures are ones the City is actively seeking to reposition for redevelopment to increase the City's tax base and economic activity. The City acquires many of these properties through the tax foreclosure auction process when no private entity bids the minimum bid. Some of these properties stay in the City's ownership for years, while others are quickly sold to development partners. For more information please visit the City's webpage for the Division of Real Estate: https://www.cityofrochester.gov/realestate/Data Dictionary: SBL: The twenty-digit unique identifier assigned to a tax parcel. PRINTKEY: A unique identifier for a tax parcel, typically in the format of “Tax map section – Block – Lot". Street Number: The street number where the tax parcel is located. Street Name: The street name where the tax parcel is located. NAME: The street number and street name for the tax parcel. City: The city where the tax parcel is located. Property Class Code: The standardized code to identify the type and/or use of the tax parcel. For a full list of codes, view the NYS Real Property System (RPS) property classification codes guide. Property Class: The name of the property class associated with the property class code. Property Type: The type of property associated with the property class code. There are nine different types of property according to RPS: 100: Agricultural 200: Residential 300: Vacant Land 400: Commercial 500: Recreation & Entertainment 600: Community Services 700: Industrial 800: Public Services 900: Wild, forested, conservation lands and public parks First Owner Name: The name of the property owner of the vacant tax parcel. If there are multiple owners, then the first one is displayed. Postal Address: The USPS postal address for the vacant landowner. Postal City: The USPS postal city, state, and zip code for the vacant landowner. Lot Frontage: The length (in feet) of how wide the lot is across the street. Lot Depth: The length (in feet) of how far the lot goes back from the street. Stated Area: The area of the vacant tax parcel. Current Land Value: The current value (in USD) of the tax parcel. Current Total Assessed Value: The current value (in USD) assigned by a tax assessor, which takes into consideration both the land value, buildings on the land, etc. Current Taxable Value: The amount (in USD) of the assessed value that can be taxed. Tentative Land Value: The current value (in USD) of the land on the tax parcel, subject to change based on appeals, reassessments, and public review. Tentative Total Assessed Value: The preliminary estimate (in USD) of the tax parcel’s assessed value, which includes tentative land value and tentative improvement value. Tentative Taxable Value: The preliminary estimate (in USD) of the tax parcel’s value used to calculate property taxes. Sale Date: The date (MM/DD/YYYY) of when the vacant tax parcel was sold. Sale Price: The price (in USD) of what the vacant tax parcel was sold for. Book: The record book that the property deed or sale is recorded in. Page: The page in the record book where the property deed or sale is recorded in. Deed Type: The type of deed associated with the vacant tax parcel sale. RESCOM: Notes whether the vacant tax parcel is zoned for residential or commercial use. R: Residential C: Commercial BISZONING: Notes the zoning district the vacant tax parcel is in. For more information on zoning, visit the City’s Zoning District map. OWNERSHIPCODE: Code to note type of ownership (if applicable). Number of Residential Units: Notes how many residential units are available on the tax parcel (if applicable). LOW_STREET_NUM: The street number of the vacant tax parcel. HIGH_STREET_NUM: The street number of the vacant tax parcel. GISEXTDATE: The date and time when the data was last updated. SALE_DATE_datefield: The recorded date of sale of the vacant tax parcel (if available). Source: This data comes from the department of Neighborhood and Business Development, Bureau of Real Estate.

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 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)

An area depicting ownership parcels of the surface estate. Each surface ownership parcel is tied to a particular legal transaction. The same individual or organization may currently own many parcels that may or may not have been acquired through the same legal transaction. Therefore, they are captured as separate entities rather than merged together. This is in contrast to Basic Ownership, in which the surface ownership parcels having the same owner are merged together. Basic Ownership provides the general user with the Forest Service versus non-Forest Service view of land ownership within National Forest boundaries. Surface Ownership provides the land status user with a current snapshot of ownership within National Forest boundaries. MetadataThis record was taken from the USDA Enterprise Data Inventory that feeds into the https://data.gov catalog. Data for this record includes the following resources: ISO-19139 metadata ArcGIS Hub Dataset ArcGIS GeoService CSV Shapefile GeoJSON KML For complete information, please visit https://data.gov.

Dataset SummaryPlease note: this data is live (updated nightly) to reflect the latest changes in the City's systems of record.About this data:The operational purpose of the vacant land dataset is to facilitate the tracking and mapping of vacant land for the purposes of promoting redevelopment of lots to increase the City's tax base and spur increased economic activity. These properties are both City owned and privately owned. The vast majority of vacant lots are the result of a demolition of a structure that once stood on the property. Vacant lots are noted in the official tax parcel assessment records with a class code beginning with 3, which denotes the category vacant land.Related Resources:For a searchable interactive mapping application, please visit the City of Rochester's Property Information explorer tool. For further information about the city's property tax assessments, please contact the City of Rochester Assessment Bureau. To access the City's zoning code, please click here.Data Dictionary: SBL: The twenty-digit unique identifier assigned to a tax parcel. PRINTKEY: A unique identifier for a tax parcel, typically in the format of “Tax map section – Block – Lot". Street Number: The street number where the tax parcel is located. Street Name: The street name where the tax parcel is located. NAME: The street number and street name for the tax parcel. City: The city where the tax parcel is located. Property Class Code: The standardized code to identify the type and/or use of the tax parcel. For a full list of codes, view the NYS Real Property System (RPS) property classification codes guide. Property Class: The name of the property class associated with the property class code. Property Type: The type of property associated with the property class code. There are nine different types of property according to RPS: 100: Agricultural 200: Residential 300: Vacant Land 400: Commercial 500: Recreation & Entertainment 600: Community Services 700: Industrial 800: Public Services 900: Wild, forested, conservation lands and public parks First Owner Name: The name of the property owner of the vacant tax parcel. If there are multiple owners, then the first one is displayed. Postal Address: The USPS postal address for the vacant landowner. Postal City: The USPS postal city, state, and zip code for the vacant landowner. Lot Frontage: The length (in feet) of how wide the lot is across the street. Lot Depth: The length (in feet) of how far the lot goes back from the street. Stated Area: The area of the vacant tax parcel. Current Land Value: The current value (in USD) of the tax parcel. Current Total Assessed Value: The current value (in USD) assigned by a tax assessor, which takes into consideration both the land value, buildings on the land, etc. Current Taxable Value: The amount (in USD) of the assessed value that can be taxed. Tentative Land Value: The current value (in USD) of the land on the tax parcel, subject to change based on appeals, reassessments, and public review. Tentative Total Assessed Value: The preliminary estimate (in USD) of the tax parcel’s assessed value, which includes tentative land value and tentative improvement value. Tentative Taxable Value: The preliminary estimate (in USD) of the tax parcel’s value used to calculate property taxes. Sale Date: The date (MM/DD/YYYY) of when the vacant tax parcel was sold. Sale Price: The price (in USD) of what the vacant tax parcel was sold for. Book: The record book that the property deed or sale is recorded in. Page: The page in the record book where the property deed or sale is recorded in. Deed Type: The type of deed associated with the vacant tax parcel sale. RESCOM: Notes whether the vacant tax parcel is zoned for residential or commercial use. R: Residential C: Commercial BISZONING: Notes the zoning district the vacant tax parcel is in. For more information on zoning, visit the City’s Zoning District map. OWNERSHIPCODE: Code to note type of ownership (if applicable). Number of Residential Units: Notes how many residential units are available on the tax parcel (if applicable). LOW_STREET_NUM: The street number of the vacant tax parcel. HIGH_STREET_NUM: The street number of the vacant tax parcel. GISEXTDATE: The date and time when the data was last updated. SALE_DATE_datefield: The recorded date of sale of the vacant tax parcel (if available). Source: This data comes from the department of Neighborhood and Business Development, Bureau of Business and Zoning.

Parcels delineate the approximate boundaries of property ownership as described in Napa County deeds, filed maps, and other source documents. Parcel boundaries in GIS are created and maintained by the Assessor’s Division Mapping section and Information Technology Services. There are approximately 51,300 real property parcels in Napa County. Parcels delineate the approximate boundaries of property ownership as described in Napa County deeds, filed maps, and other source documents. GIS parcel boundaries are maintained by the Information Technology Services GIS team. Assessor Parcel Maps are created and maintained by the Assessor Division Mapping Section. Each parcel has an Assessor Parcel Number (APN) that is its unique identifier. The APN is the link to various Napa County databases containing information such as owner name, situs address, property value, land use, zoning, flood data, and other related information. Data for this map service is sourced from the Napa County Parcels dataset which is updated nightly with any recent changes made by the mapping team. There may at times be a delay between when a document is recorded and when the new parcel boundary configuration and corresponding information is available in the online GIS parcel viewer.From 1850 to early 1900s assessor staff wrote the name of the property owner and the property value on map pages. They began using larger maps, called “tank maps” because of the large steel cabinet they were kept in, organized by school district (before unification) on which names and values were written. In the 1920s, the assessor kept large books of maps by road district on which names were written. In the 1950s, most county assessors contracted with the State Board of Equalization for board staff to draw standardized 11x17 inch maps following the provisions of Assessor Handbook 215. Maps were originally drawn on linen. By the 1980’s Assessor maps were being drawn on mylar rather than linen. In the early 1990s Napa County transitioned from drawing on mylar to creating maps in AutoCAD. When GIS arrived in Napa County in the mid-1990s, the AutoCAD images were copied over into the GIS parcel layer. Sidwell, an independent consultant, was then contracted by the Assessor’s Office to convert these APN files into the current seamless ArcGIS parcel fabric for the entire County. Beginning with the 2024-2025 assessment roll, the maps are being drawn directly in the parcel fabric layer.Parcels in the GIS parcel fabric are drawn according to the legal description using coordinate geometry (COGO) drawing tools and various reference data such as Public Lands Survey section boundaries and road centerlines. The legal descriptions are not defined by the GIS parcel fabric. Any changes made in the GIS parcel fabric via official records, filed maps, and other source documents are uploaded overnight. There is always at least a 6-month delay between when a document is recorded and when the new parcel configuration and corresponding information is available in the online parcel viewer for search or download.Parcel boundary accuracy can vary significantly, with errors ranging from a few feet to several hundred feet. These distortions are caused by several factors such as: the map projection - the error derived when a spherical coordinate system model is projected into a planar coordinate system using the local projected coordinate system; and the ground to grid conversion - the distortion between ground survey measurements and the virtual grid measurements. The aim of the parcel fabric is to construct a visual interpretation that is adequate for basic geographic understanding. This digital data is intended for illustration and demonstration purposes only and is not considered a legal resource, nor legally authoritative.SFAP & CFAP DISCLAIMER: Per the California Code, RTC 606. some legal parcels may have been combined for assessment purposes (CFAP) or separated for assessment purposes (SFAP) into multiple parcels for a variety of tax assessment reasons. SFAP and CFAP parcels are assigned their own APN number and primarily result from a parcel being split by a tax rate area boundary, due to a recorded land use lease, or by request of the property owner. Assessor parcel (APN) maps reflect when parcels have been separated or combined for assessment purposes, and are one legal entity. The goal of the GIS parcel fabric data is to distinguish the SFAP and CFAP parcel configurations from the legal configurations, to convey the legal parcel configurations. This workflow is in progress. Please be advised that while we endeavor to restore SFAP and CFAP parcels back to their legal configurations in the primary parcel fabric layer, SFAP and CFAP parcels may be distributed throughout the dataset. Parcels that have been restored to their legal configurations, do not reflect the SFAP or CFAP parcel configurations that correspond to the current property tax delineations. We intend for parcel reports and parcel data to capture when a parcel has been separated or combined for assessment purposes, however in some cases, information may not be available in GIS for the SFAP/CFAP status of a parcel configuration shown. For help or questions regarding a parcel’s SFAP/CFAP status, or property survey data, please visit Napa County’s Surveying Services or Property Mapping Information. For more information you can visit our website: When a Parcel is Not a Parcel | Napa County, CA

Data last synced 08-29-2025 04:24. Data synced on a Weekly interval.

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)

This dataset contains files created, digitized, or georeferenced by Chris DeRolph for mapping the pre-urban renewal community within the boundaries of the Riverfront-Willow St. and Mountain View urban renewal projects in Knoxville TN. Detailed occupant information for properties within boundaries of these two urban renewal projects was extracted from the 1953 Knoxville City Directory. The year 1953 was chosen as a representative snapshot of the Black community before urban renewal projects were implemented. The first urban renewal project to be approved was the Riverfront-Willow Street project, which was approved in 1954 according to the University of Richmond Renewing Inequality project titled ‘Family Displacements through Urban Renewal, 1950-1966’ (link below in the 'Other shapefiles' section). For ArcGIS Online users, the shapefile and tiff layers are available in AGOL and can be found by clicking the ellipsis next to the layer name and selecting 'Show item details' for the layers in this webmap https://knoxatlas.maps.arcgis.com/apps/webappviewer/index.html?id=43a66c3cfcde4f5f8e7ab13af9bbcebecityDirectory1953 is a folder that contains:JPG images of 1953 City Directory for street segments within the urban renewal project boundaries; images collected at the McClung Historical CollectionTXT files of extracted text from each image that was used to join occupant information from directory to GIS address datashp is a folder that contains the following shapefiles:Residential:Black_owned_residential_1953.shp: residential entries in the 1953 City Directory identified as Black and property ownersBlack_rented_residential_1953.shp: residential entries in the 1953 City Directory identified as Black and non-owners of the propertyNon_Black_owned_residential_1953.shp: residential entries in the 1953 City Directory identified as property owners that were not listed as BlackNon_Black_rented_residential_1953.shp: residential entries in the 1953 City Directory not listed as Black or property ownersResidential shapefile attributes:cityDrctryString: full text string from 1953 City Directory entryfileName: name of TXT file that contains the information for the street segmentsOccupant: the name of the occupant listed in the City Directory, enclosed in square brackets []Number: the address number listed in the 1953 City DirectoryBlackOccpt: flag for whether the occupant was identified in the City Directory as Black, designated by the (c) or (e) character string in the cityDrctryString fieldOwnerOccpd: flag for whether the occupant was identified in the City Directory as the property owner, designated by the @ character in the cityDrctryString fieldUnit: unit if listed (e.g. Apt 1, 2d fl, b'ment, etc)streetName: street name in ~1953Lat: latitude coordinate in decimal degrees for the property locationLon: longitude coordinate in decimal degrees for the property locationrace_own: combines the BlackOccpt and OwnerOccpd fieldsmapLabel: combines the Number and Occupant fields for map labeling purposeslastName: occupant's last namelabelShort: combines the Number and lastName fields for map labeling purposesNon-residential:Black_nonResidential_1953.shp: non-residential entries in the 1953 City Directory listed as Black-occupiedNonBlack_nonResidential_1953.shp: non-residential entries in the 1953 City Directory not listed as Black-occupiedNon-residential shapefile attributes:cityDrctryString: full text string from 1953 City Directory entryfileName: name of TXT file that contains the information for the street segmentsOccupant: the name of the occupant listed in the City Directory, enclosed in square brackets []Number: the address number listed in the 1953 City DirectoryBlackOccpt: flag for whether the occupant was identified in the City Directory as Black, designated by the (c) or (e) character string in the cityDrctryString fieldOwnerOccpd: flag for whether the occupant was identified in the City Directory as the property owner, designated by the @ character in the cityDrctryString fieldUnit: unit if listed (e.g. Apt 1, 2d fl, b'ment, etc)streetName: street name in ~1953Lat: latitude coordinate in decimal degrees for the property locationLon: longitude coordinate in decimal degrees for the property locationNAICS6: 2022 North American Industry Classification System (NAICS) six-digit business code, designated by Chris DeRolph rapidly and without careful considerationNAICS6title: NAICS6 title/short descriptionNAICS3: 2022 North American Industry Classification System (NAICS) three-digit business code, designated by Chris DeRolph rapidly and without careful considerationNAICS3title: NAICS3 title/short descriptionflag: flags whether the occupant is part of the public sector or an NGO; a flag of '0' indicates the occupant is assumed to be a privately-owned businessrace_own: combines the BlackOccpt and OwnerOccpd fieldsmapLabel: combines the Number and Occupant fields for map labeling purposesOther shapefiles:razedArea_1972.shp: approximate area that appears to have been razed during urban renewal based on visual overlay of usgsImage_grayscale_1956.tif and usgsImage_colorinfrared_1972.tif; digitized by Chris DeRolphroadNetwork_preUrbanRenewal.shp: road network present in urban renewal area before razing occurred; removed attribute indicates whether road was removed or remains today; historically removed roads were digitized by Chris DeRolph; remaining roads sourced from TDOT GIS roads dataTheBottom.shp: the approximate extent of the razed neighborhood known as The Bottom; digitized by Chris DeRolphUrbanRenewalProjects.shp: boundaries of the East Knoxville urban renewal projects, as mapped by the University of Richmond's Digital Scholarship Lab https://dsl.richmond.edu/panorama/renewal/#view=0/0/1&viz=cartogram&city=knoxvilleTN&loc=15/35.9700/-83.9080tiff is a folder that contains the following images:streetMap_1952.tif: relevant section of 1952 map 'Knoxville Tennessee and Surrounding Area'; copyright by J.U.G. Rich and East Tenn Auto Club; drawn by R.G. Austin; full map accessed at McClung Historical Collection, 601 S Gay St, Knoxville, TN 37902; used as reference for street names in roadNetwork_preUrbanRenewal.shp; georeferenced by Chris DeRolphnewsSentinelRdMap_1958.tif: urban renewal area map from 1958 Knox News Sentinel article; used as reference for street names in roadNetwork_preUrbanRenewal.shp; georeferenced by Chris DeRolphusgsImage_grayscale_1956.tif: May 18, 1956 black-and-white USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/ARA550590030582/usgsImage_colorinfrared_1972.tif: April 18, 1972 color infrared USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/AR6197002600096/usgsImage_grayscale_1976.tif: November 8, 1976 black-and-white USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/AR1VDUT00390010/