This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

The Digital Geologic-GIS Map of Richmond National Battlefield Park and Vicinity, Virginia is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (rich_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (rich_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (rich_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (rich_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (rich_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (rich_geology_metadata_faq.pdf). Please read the rich_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Virginia Division of Geology and Mineral Resources. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (rich_geology_metadata.txt or rich_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

These data provide an accurate high-resolution shoreline compiled from imagery of Port of Richmond, VA . This vector shoreline data is based on an office interpretation of imagery that may be suitable as a geographic information system (GIS) data layer. This metadata describes information for both the line and point shapefiles. The NGS attribution scheme 'Coastal Cartographic Object Attribute...

City of Richmond Neighborhoods.

These data were automated to provide an accurate high-resolution historical shoreline of Richmond, VA suitable as a geographic information system (GIS) data layer. These data are derived from shoreline maps that were produced by the NOAA National Ocean Service including its predecessor agencies which were based on an office interpretation of imagery and/or field survey. The NGS attribution scheme 'Coastal Cartographic Object Attribute Source Table (C-COAST)' was developed to conform the attribution of various sources of shoreline data into one attribution catalog. C-COAST is not a recognized standard, but was influenced by the International Hydrographic Organization's S-57 Object-Attribute standard so the data would be more accurately translated into S-57. This resource is a member of https://inport.nmfs.noaa.gov/inport/item/39808

Represents 2020 Census Tracts. It is the larger of the geographical units (Blocks, Block Groups, Tracts) for which the bureau publishes sample data, i.e data which is only collected from a fraction of all households.Original source TIGER file data was adjusted largely along the James River to better fit the City's GIS basemapping, and along creeks and other places where the Census had essentially done a poor job of following observable features. This is a clean version of census geography and will map nicely as compared to match earlier decades' census layers that are also in the City's GIS and were "adjusted" from their earlier TIGER files.

This data archive is a collection of GIS files and FGDC metadata prepared in 1995 for the Northampton County Planning Office by the Virginia Coast Reserve LTER project at the University of Virginia with support from the Virginia Department of Environmental Quality (DEQ) and the National Science Foundation (NSF). Original data sources include: 1:100,000-scale USGS digital line graph (DLG) hydrography and transportation data; 1:6,000-scale boundary, road, and railroad data for the town of Cape Charles from VDOT; 1:190,000-scale county-wide general soil map data and 1:15,540-scale detailed soil data for the Cape Charles area digitized from printed USDA soil survey maps; a land use and vegetation cover dataset (30 m. resolution) created by the VCRLTER derived from a 1993 Landsat Thematic Mapper satellite image; 1:20,000-scale plant association maps for 10 seaside barrier and marsh islands between Hog and Smith Islands, inclusive, prepared by Cheryl McCaffrey for TNC in 1975 and published in the Virginia Journal of Science in 1990; and 1993 colonial bird nesting site data collected by The Center for Conservation Biology (with partners The Nature Conservancy, College of William and Mary, University of Virginia, USFWS, VA-DCR, and VA-DGIF). Contents: HYDROGRAPHY Based on USGS 1:100,000 Digital Line Graph (DLG) data. Files: h100k_arc_u84 (streams, shorelines, etc.) and h100k_poly_u84 (marshes, mudflats, etc.). Note that the hydrographic data has been superseded by the more recent and more detailed USGS National Hydrography Dataset, available for the entire state of Virginia at "ftp://nhdftp.usgs.gov/DataSets/Staged/States/FileGDB/HighResolution/NHDH_VA_931v210.zip" (see http://nhd.usgs.gov/data.html for more information). A static 2013 version of the NHD data that includes shapefiles extracted from the original ESRI geodatabase format data and covering just the watersheds of the Eastern Shore of VA can also be found in the VCRLTER Data Catalog (dataset VCR14223). TRANSPORTATION Based on USGS 1:100,000 Digital Line Graph (DLG) data for the full county, and 1:6,000 VDOT data for the Cape Charles township. Files: 1:100k Transportation (lines) from USGS DLG data: rtf100k_arc_u84 (roads), rrf100k_arc_u84 (railroads), and mtf100k_arc_u84 (airports and utility transmission lines). Files: 1:6000 street, boundary, and rail line data for the town of Cape Charles, 1984, prepared by Virginia Department of Highways and Transportation Information Services (Division 1221 East Broad Street, Richmond, Virginia 23219). Streets correct through December 31,1983. Georeferencing corrected in 2014 for shapefiles only, using same methodology described for VCR14218 dataset. File : town_u84_adj (town_arc_u84old is the older unadjusted data). Note that the transportation data has been superseded by more recent and more detailed data contained in dataset VCR14222 of the VCRLTER Data Catalog. The VCR14222 data contains 2013 U.S. Census Bureau TIGER/Line road and airfield data supplemented by railroad and transmission lines digitized from high resolution VGIN-VBMP 2013 aerial imagery and additionally has boat launch locations not available here. SOILS General soil map for Northampton county (1:190k), and detailed soil map for Cape Charles and Cheriton areas (1:15,540) from published the USDA Soil Conservation Service's 1989 "Soil Survey of Northampton County, Virginia" digitized at UVA by Ray Dukes Smith: soilorig_poly_u84 (uses original shorelines from source maps), soil_poly_u84 (substitutes shorelines from 1993 landcover classification data), and cc_soil_poly_u84 (Cape Charles & Cheriton detailed data, map sheets 13 and 14). Note that the soil data has been superseded by more recent and more detailed SSURGO soil data from the USDA's Natural Resources Conservation Service (NRCS), which has seamless soil data from the 1:15,540 map series in tabular and GIS formats for the full county, as well as for all counties in VA and other states. A static 2013 version of the SSURGO data that contains merged data for Accomack and Northampton Counties can be found in the VCRLTER Data Catalog (dataset VCR14220). LANDUSE/LANDCOVER VCR Landuse and Vegetation Cover, 1993, created by Guofan Shao (VCRLTER) based on 30m resolution Landsat Thematic Mapper (TM) satellite imagery taken on July 28, 1993. Cropped to include just Northampton County. Landcover is divided into 5 classifications: (1) Forest or shrub, (2) Bare Land or Sand, (3) Planted Cropland, Grassland, or Upland Marsh, (4) Open Water, and (5) Low Salt Marsh. File = nhtm93s3_poly_u84. No spatial adjustments necessary. An outline of the county showing the shorelines based on the above 1993 TM classification is included as the shapefile:outline_poly_u84; however, no spatial adjustment has been applied. Note that a similar landuse/landcover classification based on the same... Visit https://dataone.org/datasets/knb-lter-vcr.223.2 for complete metadata about this dataset.

As part of the construction review and permitting process, Soil types convey information about their erodibility and potential erosion problems. Soils information is used in GIS mapping and geospatial analyses.

base_StreamPolygon originated from DPU's stm_StreamShape feature class. A copy of it was placed into the Basemap dataset for the purpose of supporting basic base map map service(s). The data is not dynamic, as streams do not change. Base mapping sources can be more isolated and not be dependent upon or interfer with DPU stormwater activities.base_StreamPolygon was also cleaned-up of extra fields established by DPU that serve no purpose for supporting base mapping: LifeCycleStatus, InstallDate, InstallContractor, ConstructionInspector, WorkOrderNumber, OracleInquiryNumber, DPUDrawingNumber, ProjectNumber, and ProjectName,

The purpose of this data set is to provide a geographic representation of the location of each state mile marker sign in the Commonwealth, and is to be used in a number of other products and projects. The locations of state mile marker signs on interstates and primary routes are important sources for various traffic studies as well as information for travelers. This GIS layer displays the locations and corresponding information of state mile marker signs. The signs may have been placed close but not exactly at the mile point due to geographic restrictions.Attribute NameContentsFIDInternal Feature NumberShapeFeature GeometryHTRISDEFHTRIS Definition in the Roadway InventoryROADSIDELocations of Mile Marker Posts (Right, Left, or Median)LATITUDEGPS latitude for each Mile Marker point in decimal degreesLONGITUDEGPS longitude for each Mile Marker point in decimal degreesSIGNSTYLE0: Small & Non-MUTCD Compliant, 1: MUTCD Standard (D10-1, D10-2 or D10-3), 2: MUTCD Enhanced (D10-4 or D10-5)SIGNVALUENumeric Value from the Sign Text except NULL, -1, and -2 valuesSIGNTEXTFull Sign TextM_JURISDICMaintenance Jurisdiction Code

Used to map the shared City boundaries with Henrico County to the north and Chesterfield County to the south. All thematic GIS areas are to adhere to this commonly used boundary.Edited by GIS professionals in the city's Assessor's Office.

These data were automated to provide an accurate high-resolution historical shoreline of James River, Southeast Richmond, Virginia suitable as a geographic information system (GIS) data layer. These data are derived from shoreline maps that were produced by the NOAA National Ocean Service including its predecessor agencies which were based on an office interpretation of imagery and/or field...

THIS MAP SHOWS THE FOLLOWING:Designated Highways on the state-maintained system. The National Network and Virginia Qualifying Highways include all interstates and certain other highways respectively, with one road-mile of access permissible off these routes to access terminals, fuel, food, rest, and repairs (except in cities and towns, or in Henrico and Arlington Counties where permission is required from those localities). The Virginia Access portion includes certain other primary and secondary routes where no access is allowed off the system. LIMITATIONS & EXCLUSIONS REGARDING TRUCK ROUTES & RESTRICTIONS PROVIDED ON THIS MAP1. The information presented applies only to the highway systems maintained by the Virginia Department of Transportation (VDOT). Additional STAA access or restrictions may apply in incorporated cities and towns, and on secondary roads (numbered 600 or higher) in Henrico and Arlington Counties.2. Access to, or restrictions on, the indicated routes for the specified vehicles is applicable unless other restrictions or limitations apply due to weight, height, or width; incidents or construction; or as otherwise indicated by signs on the highway.3. To the best of our knowledge the information provided is updated on a weekly basis or as received from Districts. It is the responsibility of the highway user to ensure their information is current and correct.A permit for additional access off the state maintained system may be requested by contacting the Department of Motor Vehicles at (804) 497-7135. For additional access in cities and towns and in Henrico and Arlington Counties contact officials in those localities.

Urban heat islands are small areas where temperatures are unnaturally high - usually due to dense buildings, expansive hard surfaces, or a lack of tree cover or greenspace. People living in these communities are exposed to more dangerous conditions, especially as daytime high and nighttime low temperatures increase over time. NOAA Climate Program Office and CAPA Strategies have partnered with cities around the United States to map urban heat islands. Using Sentinel-2 satellite thermal data along with on-the-ground sensors, air temperature and heat indexes are calculated for morning, afternoon, and evening time periods. The NOAA Visualization Lab, part of the NOAA Satellite and Information Service, has made the original heat mapping data available as dynamic image services.Dataset SummaryPhenomenon Mapped: heat indexUnits: degrees Fahrenheit Cell Size: 30 metersPixel Type: 32 bit floating pointData Coordinate Systems: WGS84 Mosaic Projection: WGS84 Extent: cities within the United StatesSource: NOAA and CAPA StrategiesPublication Date: September 20, 2021What can you do with this layer?This imagery layer supports communities' UHI spatial analysis and mapping capabilities. The symbology can be manually changed, or a processing template applied to the layer will provide a custom rendering. Each city can be queried.Related layers include Morning Heat Index and Evening Heat Index. Cities IncludedBoulder, CO Brooklyn, NY Greenwich Village, NY Columbia, SC Columbia, MO Columbus, OH Knoxville, TN Jacksonville, FL Las Vegas, NV Milwaukee, WI Nashville, TN Omaha, NE Philadelphia, PA Rockville, MD Gaithersburg, MD Takoma Park, MD San Francisco, CA Spokane, WA Abingdon, VA Albuquerque, NM Arlington, MA Woburn, MA Arlington, VA Atlanta, GA Charleston, SC Charlottesville, VA Clarksville, IN Farmville, VA Gresham, OR Harrisonburg, VA Kansas City, MO Lynchburg, VA Manhattan, NY Bronx, NY Newark, NJ Jersey City, NJ Elizabeth, NJ Petersburg, VA Raleigh, NC Durham, NC Richmond, VA Richmond, IN Salem, VA San Diego, CA Virginia Beach, VA Winchester, VA Austin, TX Burlington, VT Cincinnati, OH Detroit, MI El Paso, TX Houston, TX Jackson, MS Las Cruces, NM Miami, FL New Orleans, LA Providence, RI Roanoke, VA San Jose, CA Seattle, WA Vancouver, BC Canada Boston, MA Fort Lauderdale, FL Honolulu, HI Boise, ID Nampa, ID Los Angeles, CA Yonkers, NY Oakland, CA Berkeley, CA San Juan, PR Sacramento, CA San Bernardino, CA Victorville, CA West Palm Beach, FL Worcester, MA Washington, D.C. Baltimore, MD Portland, ORCities may apply to be a part of the Heat Watch program through the CAPA Strategies website. Attribute Table Informationcity_name: Afternoon Heat Index Observations in Floating-Point (°F)

Represents civic organization boundaries in the city of Richmond, Virginia.

Hospitals in the city of Richmond, Virginia. Originally derived from the ldmk_PointOfInterest feature class maintained by DIT-GIS.

This web map represents the time-line of City of Richmond annexed areas. From its origination in 1742 to 1970.

The City’s GIS reflects the DFIRM maps from 2009 and the 2013 revision. In 2013, there was a revision to the DFIRM maps, which mainly affected the Reedy Creek corridor and an area downtown. The City GIS floodplains depict both the original 2009 DFIRM information and where FEMA specified, the DFIRM 2013 revision areas were updated. 500 Year Floodplain areas are used in the City's permitting processes, as Federal regulations and local floodplain management ordinances can effect development activities in these areas. These GIS layers could be used to flag properties (hence addresses) as to whether or not they are in a 500 Year Floodplain for use in the City's data warehousing and central address systems; currently these layers are not used in the GIS summary process.

Represents the Art District in the City of Richmond, Virginia.

All active City of Richmond addresses. The schema is a combination of the primary Parcel Address (addr_ParcelAddress) and subunits (addr_Subaddress).The schema definition of the feature class is as follows:AddressID - City-created and managed unique ID values for addresses. Referred to legacy Central Address system "ADDRID" field. Still used by various city systems to reference Address records.AddressLabel - Full value of the actual address. All values include a concatenation of Building Number, Street Direction, Street Name, and Street Type. If the address is an extension (ExtensionWithUnit) or a Subaddress (UnitType and UnitValue), then this information is also concatenated.BuildingNumber - A numeric value used to position the location along the thoroughfare. These values correspond to building numbers where structures exist and are either interpolated or assigned from nearby streets where there are no structures.StreetDirection - Compass direction of the street. Street directions are only used when a street crosses a N/S or E/W dividing road-line.StreetName - Name of the street. Street names are managed by the right-of-way administrators in the Department of Public Works.StreetType - Type of Street. Utilizes the nomenclatures established by the legacy Central Address system. These abbreviations are also recognized/usable standards by the USPS.ExtensionWithUnit - Subaddress value that corresponds to Condominiums, Rear parcels, and special meter locations for the Department of Public Utilities. These addresses will have their own individual property ownership records (PINs).UnitType and UnitValue - Subaddress value that corresponds to Apartments and various other subunits. These Addresses do not have an individual property ownership record (PIN).ZipCode - USPS Zip Code value. These values are generated by an intersection of Zip Code polygon features when the address was created.Mailable - Whether it can be reasonably expected that postal deliveries can be made to an addressed location.StatePlaneX and StatePlaneY - XY Coordinate values in the native NAD83 State Plane VA South projection system.Latitude and Longitude - Lat/Long values.