A collection of KML files containing all the Geology feature classes available for download.

For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.The Boundary layer consists of lines representing the boundaries of Parcels and Legal Descriptions. (See the metadata for those two layers.) Boundary lines are the places that are surveyed in order to delimit the extent of Parcels and Legal Descriptions. The character and accuracy of Boundary locations is held in the attributes of the Points that are at the ends of Boundary lines. All the boundaries of Parcels and Legal Descriptions are covered by a Boundary line. Currently the Boundary layer has little functionality. The only distinction it makes is between upland boundaries and shorelines. In the future Boundary lines will have a richer set of attributes in order to accommodate cartographic needs to distinguish between types of boundaries.WA Boundaries Metadata

Geospatial Services Land management within the US Forest Service and on the 900,000+ acre Monongahela National Forest (NF) is driven by a wide mix of resource and societal demands that prove a challenge in fulfilling the Forest Service’s mission of “Caring for the Land and Serving the People.” Programmatically, the 2006 Land and Resource Management Plan guide natural resource management activities on lands administered by the Monongahela National Forest. The Forest Plan describes management direction and practices, resource protection methods and monitoring, desired resource conditions, and the availability and suitability of lands for resource management. Technology enables staff to address these land management issues and Forest Plan direction by using a science-based approach to facilitate effective decisions. Monongahela NF geospatial services, using enabling-technologies, incorporate key tools such as Environmental Systems Research Institute’s ArcGIS desktop suite and Trimble’s global positioning system (GPS) units to meet program and Forest needs. Geospatial Datasets The Forest has a broad set of geospatial datasets that capture geographic features across the eastern West Virginia landscape. Many of these datasets are available to the public through our download site. Selected geospatial data that encompass the Monongahela National Forest are available for download from this page. A link to the FGDC-compliant metadata is provided for each dataset. All data are in zipped format (or available from the specified source), in one of two spatial data formats, and in the following coordinate system: Coordinate System: Universal Transverse Mercator Zone: 17 Units: Meters Datum: NAD 1983 Spheroid: GRS 1980 Map files – All map files are in pdf format. These maps illustrate the correlated geospatial data. All maps are under 1 MB unless otherwise noted. Metadata file – This FGDC-compliant metadata file contains information pertaining to the specific geospatial dataset. Shapefile – This downloadable zipped file is in ESRI’s shapefile format. KML file – This downloadable zipped file is in Google Earth’s KML format. Resources in this dataset:Resource Title: Monongahela National Forest Geospatial Data. File Name: Web Page, url: https://www.fs.usda.gov/detail/mnf/landmanagement/gis/?cid=stelprdb5108081 Selected geospatial data that encompass the Monongahela National Forest are available for download from this page.

To download the surficial geology polygons click the download options button on the right. To download associated files click on the 'more' button below to expand this description and scroll down to the end, select your file and then click on the download options button. This surficial geology map is the Minnesota Geological Survey's D-01 Surficial Geology, a database that is continuously updated. The original D-01 Surficial Geology started with the S-23 Geologic Map of Minnesota - Quaternary Geology but the data has now been updated to the D-01 Surficial Geology. The D-01 Surficial geology is a product of compiled and edge-matched mapping from 1:100,000 scale MGS Quaternary maps. The data is stored at MGS as a database of lines, labels and polygons. This dataset will be updated as new MGS mapping becomes available. The polygon file and the associated layers in the database is available to the general public and can be downloaded and new maps produced online, but is not editable. To download the surficial geology GIS data go to D-01 Surficial Geology and click on the download button. You will be allowed to save the file as a KML or Shapefile. To download the layer file that is associated with the Surficial Geology click for layer here and select the Open in ArcGIS Desktop. Then pick your platform and the file will download to your computer.

For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.Abstract:The FP_GIS_FPA_ shapefiles represents Forest Practices Application/Notification (FPA/N) harvest unit boundaries, FPA/N specific tabular data, FPA/N specific Office Checklist tabular data and FPA/N specific stakeholder tabular data. An FPA/N may include harvest activity, forest road activity and aerial chemical spray activity. FPA/N harvest units include timber harvest and salvage sites. FPA/N harvest unit polygons are captured from FPA/N Activity Maps. Attribute data is captured from the FPA/N and associated documents, and may be compiled from many sources.Supplemental_Information: From July 1996 through October 2002, FPSPOLY data was collected in Oracle using the Mapping and Planning System (MAPS). From October 28, 2002 to July 10, 2009, data was collected in Oracle using the Forest Practices Application Review System (FPARS). From July 13, 2009, to the present data is collected in dotNET using FPARSv3.Washington State is divided into two State Plane Zones, north and south. For this data set, north zone data coordinates have been converted to south zone coordinates.

The North Carolina State and County Boundary vector polygon data provides location information for North Carolina State and County Boundary lines derived from the best available survey and/or Geographic Information System (GIS) data. Sources for information are the North Carolina Geodetic Survey (NCGS), NC Department of Transportation (NCDOT), United States Geological Survey (USGS), and field surveys conducted by licensed surveyors in North Carolina and neighboring states that have been approved and recorded in their respective counties. North Carolina Geodetic Survey assists counties on a cooperative basis (NC General Statute 153A-18) in defining and monumenting the location of uncertain or disputed boundaries as established by law. Some counties have completed boundary surveys for at least a portion of their county boundary. However, the majority of county boundaries have not been surveyed and are represented by the best currently available data from GIS sources, including NCDOT county maps (which originally came from the USGS) and updated county parcel maps.

DVRPC counts bicyclists and pedestrians because count data helps us understand and plan for the role bicyclists and pedestrians play in our transportation network. Similar to how planners use vehicular traffic counts to analyze roadway facilities, our bicycle and pedestrian counting program allows planners to measure existing levels of bicycling and walking, monitor travel trends, plan for new or improved facilities and measure outcomes of bicycle and pedestrian related projects. Our counting program consists of four types of counts: Project Counts, Cyclical Counts, Screenline Counts and Permanent Counts.

This layer presents the Universal Transverse Mercator (UTM) zones of the world. The layer symbolizes the 6-degree wide zones employed for UTM projection.To download the data for this layer as a layer package for use in ArcGIS desktop applications, refer to World UTM Zones Grid.

For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.General DescriptionThis layer shows only Active Roads on DNR Lands in black. This does not include abandoned, orphaned, decommisioned, or closed roads on DNR lands. Roads not on DNR Lands are of unknown status are shown in grey. Roads not on DNR lands and of unknown status may not be drivable. IncludesThe ROAD feature class stores the spatial location and attributes of the State of Washington, Department of Natural Resources’ (DNR) forest roads and of other DNR, public and selected private roads in the state. Other elements of the transportation network such as ferries, railroads, and trails are not included. ContactWashington State Department of Natural Resources (WA DNR) Engineering DivisionAlexandra WashburnAlexandra.Washburn@dnr.wa.gov Updating EffortsUpdating and editing efforts are primarily focused on roads in DNR managed state lands, adjunct roads or in areas that are covered by a published map that is undergoing an update. The original road lines were entered primarily by digitizing from paper maps, scanning by machine, or derived stereoscopically from black and white photo imagery. They are currently updated and corrected as needed, in most cases using on-line, geo-referenced orthophotography, stereo color imagery, GPS or field survey.Roads on DNR Lands should be edited frequently by division staff.Roads outside of DNR Lands are probably edited much less frequently. The group in mapping that did this, does not do it anymore.AttributesThe ROAD layer includes basic attributes that are linked to the intersection-based road segments. These attributes store information about route id, road name, road number, control, responsibility, status, access, surface, classification, and abandonment.PurposeThis layer is used to help in road infrastructure planning and maintenance, Forest Practices and Road Maintenance and Abandonment Planning (RMAP) compliance reporting, forest management, timber sales planning, and is the basis for the ROAD_ROUTE_FT layer and associated event tables that currently record these maintenance activities and road easements. It is widely used as a layer in cartographic presentations and published maps.

The North American Rail Network (NARN) Rail Lines dataset was created in 2016 and was updated on April 09, 2025 from the Federal Railroad Administration (FRA) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The NARN Rail Lines dataset is a database that provides ownership, trackage rights, type, passenger, STRACNET, and geographic reference for North America's railway system at 1:24,000 or better within the United States. The data set covers all 50 States, the District of Columbia, Mexico, and Canada. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1528950

For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.Information for SOILS data layer was derived from the Private Forest Land Grading system (PFLG) and subsequent soil surveys. PFLG was a five-year mapping program completed in 1980 for the purpose of forestland taxation. It was funded by the Washington State Department of Revenue. The Department of Natural Resources, Soil Conservation Service (now known as the Natural Resources Conservation Service or NRCS), USDA Forest Service and Washington State University conducted soil mapping cooperatively following national soil survey standards. Private lands having the potential of supporting commercial forests were surveyed along with interspersed small areas of State lands, Indian tribal lands, and federal lands. Because this was a cooperative soil survey project, agricultural and non-commercial forestlands were included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soil map unit delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were later added and are now available through associated lookup tables. SCS (NRCS) soils data on agricultural lands also have been subsequently added to this data layer. The SOILS data layer includes approximately 1,100 townships with wholly or partially digitized soils data. State and private lands which have the potential of supporting commercial forest stands were surveyed. Some Indian tribal and federal lands were surveyed. Because this was a cooperative soils survey project, agricultural and non-commercial forestlands were also included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soils delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were added at a later time and are now available through associated lookup tables. SCS soils data on agricultural lands also have subsequently been added to this data layer. This layer includes approximately 1, 100 townships with wholly or partially digitized soils data (2,101 townships would provide complete coverage of the state of Washington).-

The soils_sv resolves one to many relationships and as such is one of those special "DNR" spatial views ( ie. is implemented similar to a feature class). Column names may not match between SOILS_SV and the originating datasets. Use limitations

This Spatial View is available to Washingotn DNR users and those with access to the Washington State Uplands IMS site.

The following cautions only apply to one-to-many and many-to-many spatial views! Use these in the metadata only if the SV is one-to-many or many-to-many.

CAUTIONS: Area and Length Calculations: Use care when summarizing or totaling area or length calculations from spatial views with one-to-many or many-to-many relationships. One-to-many or many-to-many relationships between tabular and spatial data create multiple features in the same geometry. In other words, if there are two or more records in the table that correspond to the same feature (a single polygon, line or point), the spatial view will contain an identical copy of that feature's geometry for every corresponding record in the table. Area and length calculations should be performed carefully, to ensure they are not being exaggerated by including copies of the same feature's geometry.

Symbolizing Spatial Features:
Use care when symbolizing data in one-to-many or many-to-many spatial views. If there are multiple attributes tied to the same feature, symbolizing with a solid fill may mask other important features within the spatial view. This can be most commonly seen when symbolizing features based on a field with multiple table records.

Labeling Spatial Features: Spatial views with one-to-many or many-to-many relationships may present duplicate labels for those features with multiple table records. This is because there are multiple features in the same geometry, and each one receives a label.Soils Metadata

New political and administrative boundaries Shapefile of Nepal. Downloaded and republished from the Survey Department website.

Click to downloadClick for metadataService URL: https://gis.dnr.wa.gov/site2/rest/services/Public_Forest_Practices/WADNR_PUBLIC_FP_Water_Type/MapServer/4For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.The DNR Forest Practices Wetlands Geographic Information System (GIS) Layer is based on the National Wetlands Inventory (NWI). In cooperation with the Washington State Department of Ecology, DNR Forest Practices developed a systematic reclassification of the original USFWS wetlands codes into WAC 222-16-035 types. The reclassification was done in 1995 according to the Forest Practice Rules in place at the time. The WAC's for defining wetlands are 222-16-035 and 222-16-050.The DNR Forest Practices Wetlands Geographic Information System (GIS) Layer is based on the National Wetlands Inventory (NWI). In cooperation with the Washington State Department of Ecology, DNR Forest Practices developed a systematic reclassification of the original USFWS wetlands codes into WAC 222-16-035 types. The reclassification was done in 1995 according to the Forest Practice Rules in place at the time. The WAC's for defining wetlands are 222-16-035 and 222-16-050.It is intended that these data be only a first step in determining whether or not wetland issues have been or need to be addressed in an area. The DNR Forest Practices Division and the Department of Ecology strongly supports the additional use of hydric soils (from the GIS soils layer) to add weight to the call of 'wetland'. Reports from the Department of Ecology indicate that these data may substantially underestimate the extent of forested wetlands. Various studies show the NWI data is 25-80% accurate in forested areas. Most of these data were collected from stereopaired aerial photos at a scale of 1:58,000. The stated accuracy is that of a 1:24,000 map, or plus or minus 40 feet. In addition, some parts of the state have data that are 30 years old and only a small percentage have been field checked. Thus, for regulatory purposes, the user should not rely solely on these data. On-the-ground checking must accompany any regulatory call based on these data.The reclassification is based on the USFWS FWS_CODE. The FWS_CODE is a concatenation of three subcomponents: Wetland system, class, and water regime. Forest Practices further divided the components into system, subsystem, class, subclass, water regime, special modifiers, xclass, subxclass, and xsystem. The last three items (xsomething) are for wetland areas which do not easily lend themselves to one class alone. The resulting classification system uses two fields: WLND_CLASS and WLND_TYPE. WLND_CLASS indicates whether the polygon is a forested wetland (F), open water (O), or a vegetated wetland (W). WLND_TYPE, indicates whether the wetland is a type A (1), type B (2), or a generic wetland (3) that doesn't fit the categories for A or B type wetlands. WLND_TYPE = 0 (zero) is used where WLND_CLASS = O (letter "O").

The wetland polygon is classified as F, forested wetland; O, open water; or W, vegetated wetland depending on the following FWS_CODE categories: F O W --------------------------------------------------- Forested Open Vegetated Wetland Water Wetland --------------------------------------------PFO* POW PUB5 E2FO PRB* PML2 PUB1-4 PEM* PAB* L2US5 PUS1-4 L2EM2 PFL* PSS* L1RB* PML1 L1UB*
L1AB* L1OW L2RB* L2UB* L2AB* L2RS* L2US1-4 L2OW

• indicates inclusion of the subcategory (ie. PEM* includes PEM1F, PEM1FB, etc.).

DNR FOREST PRACTICES WETLANDS DATASET ON FPARS Internet Mapping Website: The FPARS Resource Map and Water Type Map display Forested, Type A, Type B, and "other" wetlands. Open water polygons are not displayed on the FPARS Resource Map and Water Type Map in an attempt to minimize clutter. The following code combinations are found in the DNR Forest Practices wetlands dataset:

WLND_CLASS WLND_TYPE wetland polygon classification F 3 Forested wetland as defined in WAC 222-16-035 O 0 *NWI open water (not displayed on FPARS Resource or Water Type Maps) W 1 Type A Wetland as defined in WAC 222-16-035 W 2 Type B Wetland as defined in WAC 222-16-035 W 3 other wetland

• NWI open water polygons are indicated by WLND_CLASS = O and WLND_TYPE = 0. Open water is used in the USFWS and WAC 222-16-035 classification system. These open water polygons are not included in the FPARS Resource Map and Water Type Map views of this dataset in an attempt to minimize clutter on the FPARS maps.

The California Department of Forestry and Fire Protection's Fire and Resource Assessment Program (FRAP) annually maintains and distributes an historical wildland fire perimeter dataset from across public and private lands in California. The GIS data is developed with the cooperation of the United States Forest Service Region 5, the Bureau of Land Management, California State Parks, National Park Service and the United States Fish and Wildlife Service and is released in the spring with added data from the previous calendar year. Although the dataset represents the most complete digital record of fire perimeters in California, it is still incomplete, and users should be cautious when drawing conclusions based on the data.

This data should be used carefully for statistical analysis and reporting due to missing perimeters (see Use Limitation in metadata). Some fires are missing because historical records were lost or damaged, were too small for the minimum cutoffs, had inadequate documentation or have not yet been incorporated into the database. Other errors with the fire perimeter database include duplicate fires and over-generalization. Additionally, over-generalization, particularly with large old fires, may show unburned "islands" within the final perimeter as burned. Users of the fire perimeter database must exercise caution in application of the data. Careful use of the fire perimeter database will prevent users from drawing inaccurate or erroneous conclusions from the data. This data is updated annually in the spring with fire perimeters from the previous fire season. This dataset may differ in California compared to that available from the National Interagency Fire Center (NIFC) due to different requirements between the two datasets. The data covers fires back to 1878. As of May 2025, it represents fire24_1.

Please help improve this dataset by filling out this survey with feedback:

Historic Fire Perimeter Dataset Feedback (arcgis.com)

Current criteria for data collection are as follows:

CAL FIRE (including contract counties) submit perimeters ≥10 acres in timber, ≥50 acres in brush, or ≥300 acres in grass, and/or ≥3 impacted residential or commercial structures, and/or caused ≥1 fatality.

All cooperating agencies submit perimeters ≥10 acres.

Version update:

Firep24_1 was released in April 2025. Five hundred forty-eight fires from the 2024 fire season were added to the database (2 from BIA, 56 from BLM, 197 from CAL FIRE, 193 from Contract Counties, 27 from LRA, 8 from NPS, 55 from USFS and 8 from USFW). Six perimeters were added from the 2025 fire season (as a special case due to an unusual January fire siege). Five duplicate fires were removed, and the 2023 Sage was replaced with a more accurate perimeter. There were 900 perimeters that received updated attribution (705 removed “FIRE” from the end of Fire Name field and 148 replaced Complex IRWIN ID with Complex local incident number for COMPLEX_ID field). The following fires were identified as meeting our collection criteria but are not included in this version and will hopefully be added in a future update: Addie (2024-CACND-002119), Alpaugh (2024-CACND-001715), South (2024-CATIA-001375). One perimeter is missing containment date that will be updated in the next release.

Cross checking CALFIRS reporting for new CAL FIRE submissions to ensure accuracy with cause class was added to the compilation process. The cause class domain description for “Powerline” was updated to “Electrical Power” to be more inclusive of cause reports.

Includes separate layers filtered by criteria as follows:

California Fire Perimeters (All): Unfiltered. The entire collection of wildfire perimeters in the database. It is scale dependent and starts displaying at the country level scale.

Recent Large Fire Perimeters (≥5000 acres): Filtered for wildfires greater or equal to 5,000 acres for the last 5 years of fires (2020-January 2025), symbolized with color by year and is scale dependent and starts displaying at the country level scale. Year-only labels for recent large fires.

California Fire Perimeters (1950+): Filtered for wildfires that started in 1950-January 2025. Symbolized by decade, and display starting at country level scale.

Detailed metadata is included in the following documents:

Wildland Fire Perimeters (Firep24_1) Metadata

For any questions, please contact the data steward:

Kim Wallin, GIS Specialist

CAL FIRE, Fire & Resource Assessment Program (FRAP)

kimberly.wallin@fire.ca.gov

To download the surficial geology polygons click the download options button on the right. To download associated files click on the 'more' button below to expand this description and scroll down to the end, select your file and then click on the download options button. This surficial geology map is the Minnesota Geological Survey's D-1 Surficial Geology, a database that is continuously updated. The original D-1 Surficial Geology started with the S-23 Geologic Map of Minnesota - Quaternary Geology but the data has now been updated to the D-1 Surficial Geology. The D-1 Surficial geology is a product of compiled and edge-matched mapping from 1:100,000 scale MGS Quaternary maps. The data is stored at MGS as a database of lines, labels and polygons. This dataset will be updated as new MGS mapping becomes available. The polygon file and the associated layers in the database is available to the general public and can be downloaded and new maps produced online, but is not editable. To download the surficial geology GIS data go to D-1 Surficial Geology and click on the download button. You will be allowed to save the file as a KML or Shapefile. To download the layer file that is associated with the Surficial Geology click for layer here and select the Open in ArcGIS Desktop. Then pick your platform and the file will download to your computer.For the other associated files please click on the following:Geomorphic Line Symbols from S-23SSURGO Histosols (2012)DNR NHD HydrologyHolocene Lake SedimentBedrock OutcropsPeat from S-23Glacial Lakes

*This dataset is authored by the Washington Department of Natural Resources and is being shared as a direct link by Pend Oreille County. This is a primary reference soils dataset used by our organization for building, planning, and permitting purposes.This data can be used for determining a variety of soils information that was derived from the Private Forest Land Grading system and subsequent soil surveys. See Description and Metadata for more information.For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.Information for SOILS data layer was derived from the Private Forest Land Grading system (PFLG) and subsequent soil surveys. PFLG was a five-year mapping program completed in 1980 for the purpose of forestland taxation. It was funded by the Washington State Department of Revenue. The Department of Natural Resources, Soil Conservation Service (now known as the Natural Resources Conservation Service or NRCS), USDA Forest Service and Washington State University conducted soil mapping cooperatively following national soil survey standards. Private lands having the potential of supporting commercial forests were surveyed along with interspersed small areas of State lands, Indian tribal lands, and federal lands. Because this was a cooperative soil survey project, agricultural and non-commercial forestlands were included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soil map unit delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were later added and are now available through associated lookup tables. SCS (NRCS) soils data on agricultural lands also have been subsequently added to this data layer. The SOILS data layer includes approximately 1,100 townships with wholly or partially digitized soils data. State and private lands which have the potential of supporting commercial forest stands were surveyed. Some Indian tribal and federal lands were surveyed. Because this was a cooperative soils survey project, agricultural and non-commercial forestlands were also included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soils delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were added at a later time and are now available through associated lookup tables. SCS soils data on agricultural lands also have subsequently been added to this data layer. This layer includes approximately 1, 100 townships with wholly or partially digitized soils data (2,101 townships would provide complete coverage of the state of Washington).- The soils_sv resolves one to many relationships and as such is one of those special "DNR" spatial views ( ie. is implemented similar to a feature class). Column names may not match between SOILS_SV and the originating datasets. Use limitations This Spatial View is available to Washingotn DNR users and those with access to the Washington State Uplands IMS site. The following cautions only apply to one-to-many and many-to-many spatial views! Use these in the metadata only if the SV is one-to-many or many-to-many. CAUTIONS: Area and Length Calculations: Use care when summarizing or totaling area or length calculations from spatial views with one-to-many or many-to-many relationships. One-to-many or many-to-many relationships between tabular and spatial data create multiple features in the same geometry. In other words, if there are two or more records in the table that correspond to the same feature (a single polygon, line or point), the spatial view will contain an identical copy of that feature's geometry for every corresponding record in the table. Area and length calculations should be performed carefully, to ensure they are not being exaggerated by including copies of the same feature's geometry. Symbolizing Spatial Features: Use care when symbolizing data in one-to-many or many-to-many spatial views. If there are multiple attributes tied to the same feature, symbolizing with a solid fill may mask other important features within the spatial view. This can be most commonly seen when symbolizing features based on a field with multiple table records. Labeling Spatial Features: Spatial views with one-to-many or many-to-many relationships may present duplicate labels for those features with multiple table records. This is because there are multiple features in the same geometry, and each one receives a label.Soils Metadata

This is the shapefile for 2010 Census Block Group Number. You can download it in the formats of Spreadsheet, KML, Shapefile in Zip file, or Full Dataset. It was created by the GIS Team in the Division of Information Technology Service at Texas Education Agency and data was based on the Census Bureau with website, https://www.census.gov/geo/maps-data/data/cbf/cbf_blkgrp.html with ESRI ArcGIS Tool (www.arcgis.com).