10 datasets found
  1. a

    Parcel Line

    • richmond-geo-hub-cor.hub.arcgis.com
    • office-of-the-assessor-of-real-estate-cor.hub.arcgis.com
    Updated Mar 25, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Richmond, VA (2020). Parcel Line [Dataset]. https://richmond-geo-hub-cor.hub.arcgis.com/maps/parcel-line
    Explore at:
    Dataset updated
    Mar 25, 2020
    Dataset authored and provided by
    City of Richmond, VA
    Area covered
    Description

    This is the parcel lines used to build the parcel polygons.The shape length is the distance of the drawn line.The Legal Length is the distance of the known length from a deed or plat.Often these two do not agree because this GIS mapping is not legal surveys but mapping for tax assessments.

  2. n

    NYS Tax Parcels Public

    • data.gis.ny.gov
    • opdgig.dos.ny.gov
    • +1more
    Updated Dec 20, 2022
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    ShareGIS NY (2022). NYS Tax Parcels Public [Dataset]. https://data.gis.ny.gov/datasets/nys-tax-parcels-public-1
    Explore at:
    Dataset updated
    Dec 20, 2022
    Dataset authored and provided by
    ShareGIS NY
    Area covered
    Description

    Publication Date: April 2025. This polygon layer is updated annually.

    This layer contains 2024 parcel data only for NY State counties which gave NYS ITs Geospatatial Services permission to share this data with the public. Work to obtain parcel data from additional counties, as well as permission to share the data, is ongoing. To date, 36 counties have provided the Geospatial Services permission to share their parcel data with the public. Parcel data for counties which do not allow the Geospatial Services to redistribute their data must be obtained directly from those counties. Geospatial Services' goal is to eventually include parcel data for all counties in New York State.

    Parcel geometry was incorporated as received from County Real Property Departments. No attempt was made to edge-match parcels along adjacent counties. County attribute values were populated using 2024 Assessment Roll tabular data Geospatial Services obtained from the NYS Department of Tax and Finance’s Office of Real Property Tax Services (ORPTS). Tabular assessment data was joined to the county provided parcel geometry using the SWIS & SBL or SWIS & PRINT KEY unique identifier for each parcel.

    Detailed information about assessment attributes can be found in the ORPTS Assessor’s Manuals available here: https://www.tax.ny.gov/research/property/assess/manuals/assersmanual.htm. New York City data comes from NYC MapPluto which can be found here: https://www1.nyc.gov/site/planning/data-maps/open-data/dwn-pluto-mappluto.page.

    This layer displays when zoomed in below 1:37,051-scale.

    This map service is available to the public.

    Geometry accuracy varies by contributing county.

    Thanks to the following counties that specifically authorized Geospatial Services to share their GIS tax parcel data with the public: Albany, Cayuga, Chautauqua, Cortland, Erie, Genesee, Greene, Hamilton, Lewis, Livingston, Montgomery, New York City (Bronx, Kings, New York, Queens, Richmond), Oneida, Onondaga, Ontario, Orange, Oswego, Otsego, Putnam, Rensselaer, Rockland, Schuyler, Steuben, St Lawrence, Suffolk, Sullivan, Tioga, Tompkins, Ulster, Warren, Wayne, and Westchester.

    The State of New York, acting through the New York State Office of Information Technology Services, makes no representations or warranties, express or implied, with respect to the use of or reliance on the Data provided. The User accepts the Data provided “as is” with no guarantees that it is error free, complete, accurate, current or fit for any particular purpose and assumes all risks associated with its use. The State disclaims any responsibility or legal liability to Users for damages of any kind, relating to the providing of the Data or the use of it. Users should be aware that temporal changes may have occurred since this Data was created.

  3. a

    Parcels

    • office-of-the-assessor-of-real-estate-cor.hub.arcgis.com
    • richmond-geo-hub-cor.hub.arcgis.com
    Updated Apr 12, 2018
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Richmond, VA (2018). Parcels [Dataset]. https://office-of-the-assessor-of-real-estate-cor.hub.arcgis.com/datasets/parcels-1
    Explore at:
    Dataset updated
    Apr 12, 2018
    Dataset authored and provided by
    City of Richmond, VA
    Area covered
    Description

    This feature class combines Parcel geography information with land ownership data from the city's Computer Aided Mass Appraisal (CAMA) system. In instances of multiple ownership records (PINs) for one parcel feature, each parcel will be duplicated or "stacked."Nomenclature:cads_- short for "cadastral" - the prefix used to identify GIS data related to property and property assessment.Parcel- each geometry is a single parcel feature.Asr- short for Assessor.View- This feature class is generated from a SQL spatial view of property records and parcel geometry.The schema definition of the feature class is as follows:ParcelID - UniqueID for a Parcel.PIN - Property Identification Number.CountOfPIN - Number of PIN values per parcel.OwnerName - Name of the property owner.AsrLocationBldgNo - Address number of the property.MailAddress - Property Owner mailing address.MailCity - Property Owner mailing address city.MailState - Property Owner mailing address state.MailZip - Property Owner mailing address Zip Code.AssessmentDate - Date of the last property assessment.LandValue - Total valuation of the land.DwellingValue - Total valuation of the dwelling.TotalValue - LandValue + DwellingValue. Total value of the property.LandSqFt - Square footage of the land.ProvalAsmtNhood - The "Assessment Neighborhood" code that city of Richmond property assessors use to identify distinct neighborhoods. Proval is the name of the city's CAMA system.TaxExemptCode - Tax-exempt property code, if applicable.PropertyClassID - City property class code.PropertyClass - City property class name. Corresponds to PropertyClassID.LandUse - Land use.

  4. o

    Whistling Arrow Court Cross Street Data in Richmond, VA

    • ownerly.com
    Updated May 24, 2022
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Ownerly (2022). Whistling Arrow Court Cross Street Data in Richmond, VA [Dataset]. https://www.ownerly.com/va/richmond/whistling-arrow-ct-home-details
    Explore at:
    Dataset updated
    May 24, 2022
    Dataset authored and provided by
    Ownerly
    Area covered
    Virginia, Richmond, Whistling Arrow Court
    Description

    This dataset provides information about the number of properties, residents, and average property values for Whistling Arrow Court cross streets in Richmond, VA.

  5. Knoxville TN Urban Renewal Mapping Data

    • figshare.com
    zip
    Updated Feb 16, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Chris DeRolph (2024). Knoxville TN Urban Renewal Mapping Data [Dataset]. http://doi.org/10.6084/m9.figshare.25199849.v3
    Explore at:
    zipAvailable download formats
    Dataset updated
    Feb 16, 2024
    Dataset provided by
    Figsharehttp://figshare.com/
    Authors
    Chris DeRolph
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    Knoxville
    Description

    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/

  6. a

    StreetFrontagePriorityStreet

    • richmond-geo-hub-cor.hub.arcgis.com
    Updated Mar 4, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Richmond, VA (2020). StreetFrontagePriorityStreet [Dataset]. https://richmond-geo-hub-cor.hub.arcgis.com/datasets/streetfrontageprioritystreet
    Explore at:
    Dataset updated
    Mar 4, 2020
    Dataset authored and provided by
    City of Richmond, VA
    Area covered
    Description

    Street Frontage uses linear features which are digitized along the inner edge of sidewalks, coincident with the frontage of either parcel properties or building footprints. Instead of creating two separate feature classes, the Street Frontage features contain a “Frontage Type” attribute field, which is used to identify the street frontage zoning for the feature; Street-Oriented Commercial Frontage, or Priority Street. While a single linear feature cannot be attributed as both zoning types, two separate street frontage features may be overlapping (duplicated features with alternate FrontageType attributes), such that locations will show/map both zoning types exists along a street frontage. GIS mapping that shows only one of the two FrontageTypes exists means that there are not coincident features. Street-Oriented Commercial Frontage: Buildings on streets that are designated as Street-Oriented Commercial must have ground floor commercial uses, which activate the street edge and work toward creating a more walkable environment. Streets which are significant to a given property and the larger neighborhood, where buildings are required to face and engage with the street through fenestration and siting requirements.

  7. a

    SAD - Special Assessment Districts

    • richmond-geo-hub-cor.hub.arcgis.com
    • office-of-the-assessor-of-real-estate-cor.hub.arcgis.com
    Updated Oct 26, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Richmond, VA (2020). SAD - Special Assessment Districts [Dataset]. https://richmond-geo-hub-cor.hub.arcgis.com/maps/94857b9e19eb4ae3b03d0421e920b88d
    Explore at:
    Dataset updated
    Oct 26, 2020
    Dataset authored and provided by
    City of Richmond, VA
    Area covered
    Description

    Special Assessment DistrictsSpecial Assessment Districts provide services or infrastructure improvements which benefit a limited area. Venture Richmond is the administrator of these districts for the city of Richmond. The districts include:General DistrictConsumer Broad DistrictConsumer Shockoe DistrictRiverfront Overlay DistrictRiverfront Manufacturing Overlay DistrictRiverfront Pre-development Overlay DistrictRiverfront Developing Properties Overlay DistrictRiverfront Completed Properties Overlay DistrictIf you have a question about the amount of taxes applied for a property being in one of the Special Assessment Districts, please contact the Department of Finance.If you have a question about the Special Assessment Districts themselves or to find out if if a parcel is in one of the Districts, please contact the Assessor's office.

  8. a

    FEMA Flood Hazard Areas

    • richmond-geo-hub-cor.hub.arcgis.com
    Updated Jun 20, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Richmond, VA (2025). FEMA Flood Hazard Areas [Dataset]. https://richmond-geo-hub-cor.hub.arcgis.com/datasets/fema-flood-hazard-areas
    Explore at:
    Dataset updated
    Jun 20, 2025
    Dataset authored and provided by
    City of Richmond, VA
    Area covered
    Description

    The FIRM is the basis for floodplain management, mitigation, and insurance activities for the National Flood Insurance Program (NFIP). Insurance applications include enforcement of the mandatory purchase requirement of the Flood Disaster Protection Act, which "... requires the purchase of flood insurance by property owners who are being assisted by Federal programs or by Federally supervised, regulated or insured agencies or institutions in the acquisition or improvement of land facilities located or to be located in identified areas having special flood hazards," Section 2 (b) (4) of the Flood Disaster Protection Act of 1973. In addition to the identification of Special Flood Hazard Areas (SFHAs), the risk zones shown on the FIRMs are the basis for the establishment of premium rates for flood coverage offered through the NFIP. The DFIRM Database presents the flood risk information depicted on the FIRM in a digital format suitable for use in electronic mapping applications. The DFIRM database is a subset of the Digital FIS database that serves to archive the information collected during the FIS.The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth"s surface using the UTM projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12000.

  9. a

    FEMA DFIRM

    • richmond-geo-hub-cor.hub.arcgis.com
    Updated Dec 16, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Richmond, VA (2019). FEMA DFIRM [Dataset]. https://richmond-geo-hub-cor.hub.arcgis.com/datasets/cor::fema-dfirm/about
    Explore at:
    Dataset updated
    Dec 16, 2019
    Dataset authored and provided by
    City of Richmond, VA
    Area covered
    Description

    This layer will no longer be the authoritative on July 8, 2025.The FIRM is the basis for floodplain management, mitigation, and insurance activities for the National Flood Insurance Program (NFIP). Insurance applications include enforcement of the mandatory purchase requirement of the Flood Disaster Protection Act, which "... requires the purchase of flood insurance by property owners who are being assisted by Federal programs or by Federally supervised, regulated or insured agencies or institutions in the acquisition or improvement of land facilities located or to be located in identified areas having special flood hazards," Section 2 (b) (4) of the Flood Disaster Protection Act of 1973. In addition to the identification of Special Flood Hazard Areas (SFHAs), the risk zones shown on the FIRMs are the basis for the establishment of premium rates for flood coverage offered through the NFIP. The DFIRM Database presents the flood risk information depicted on the FIRM in a digital format suitable for use in electronic mapping applications. The DFIRM database is a subset of the Digital FIS database that serves to archive the information collected during the FIS.The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the UTM projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12000.

  10. a

    Flood Hazard Areas, Cross Sections, and BFE

    • richmond-geo-hub-cor.hub.arcgis.com
    Updated Jun 20, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Flood Hazard Areas, Cross Sections, and BFE [Dataset]. https://richmond-geo-hub-cor.hub.arcgis.com/items/996945205caf496e853d625e9992f673
    Explore at:
    Dataset updated
    Jun 20, 2025
    Dataset authored and provided by
    City of Richmond, VA
    Area covered
    Description

    The FIRM is the basis for floodplain management, mitigation, and insurance activities for the National Flood Insurance Program (NFIP). Insurance applications include enforcement of the mandatory purchase requirement of the Flood Disaster Protection Act, which "... requires the purchase of flood insurance by property owners who are being assisted by Federal programs or by Federally supervised, regulated or insured agencies or institutions in the acquisition or improvement of land facilities located or to be located in identified areas having special flood hazards," Section 2 (b) (4) of the Flood Disaster Protection Act of 1973. In addition to the identification of Special Flood Hazard Areas (SFHAs), the risk zones shown on the FIRMs are the basis for the establishment of premium rates for flood coverage offered through the NFIP. The DFIRM Database presents the flood risk information depicted on the FIRM in a digital format suitable for use in electronic mapping applications. The DFIRM database is a subset of the Digital FIS database that serves to archive the information collected during the FIS.The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth"s surface using the UTM projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12000.

  11. Not seeing a result you expected?
    Learn how you can add new datasets to our index.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
City of Richmond, VA (2020). Parcel Line [Dataset]. https://richmond-geo-hub-cor.hub.arcgis.com/maps/parcel-line

Parcel Line

Explore at:
Dataset updated
Mar 25, 2020
Dataset authored and provided by
City of Richmond, VA
Area covered
Description

This is the parcel lines used to build the parcel polygons.The shape length is the distance of the drawn line.The Legal Length is the distance of the known length from a deed or plat.Often these two do not agree because this GIS mapping is not legal surveys but mapping for tax assessments.

Search
Clear search
Close search
Google apps
Main menu