Northeastern United States County Boundary data are intended for geographic display of state and county boundaries at statewide and regional levels. Use it to map and label counties on a map. These data are derived from Northeastern United States Political Boundary Master layer. This information should be displayed and analyzed at scales appropriate for 1:24,000-scale data. The State of Connecticut, Department of Environmental Protection (CTDEP) assembled this regional data layer using data from other states in order to create a single, seamless representation of political boundaries within the vicinity of Connecticut that could be easily incorporated into mapping applications as background information. More accurate and up-to-date information may be available from individual State government Geographic Information System (GIS) offices. Not intended for maps printed at map scales greater or more detailed than 1:24,000 scale (1 inch = 2,000 feet.)

Connecticut and Vicinity Town Boundary data are intended for geographic display of state, county and town (municipal) boundaries at statewide and regional levels. Use it to map and label towns on a map. These data are derived from Northeastern United States Political Boundary Master layer. This information should be displayed and analyzed at scales appropriate for 1:24,000-scale data. The State of Connecticut, Department of Environmental Protection (CTDEP) assembled this regional data layer using data from other states in order to create a single, seamless representation of political boundaries within the vicinity of Connecticut that could be easily incorporated into mapping applications as background information. More accurate and up-to-date information may be available from individual State government Geographic Information System (GIS) offices. Not intended for maps printed at map scales greater or more detailed than 1:24,000 scale (1 inch = 2,000 feet.)

Soil map units are the basic geographic unit of the Soil Survey Geographic Database (SSURGO). The SSURGO dataset is a compilation of soils information collected over the last century by the Natural Resources Conservation Service (NRCS). Map units delineate the extent of different soils. Data for each map unit contains descriptions of the soil’s components, productivity, unique properties, and suitability interpretations. Each soil type has a unique combination of physical, chemical, nutrient and moisture properties. Soil type has ramifications for engineering and construction activities, natural hazards such as landslides, agricultural productivity, the distribution of native plant and animal life and hydrologic and other physical processes. Soil types in the context of climate and terrain can be used as a general indicator of engineering constraints, agriculture suitability, biological productivity and the natural distribution of plants and animals. Data from thegSSURGO databasewas used to create this layer. To download ready-to-use project packages of useful soil data derived from the SSURGO dataset, please visit the USA SSURGO Downloader app. Dataset Summary Phenomenon Mapped:Soils of the United States and associated territoriesGeographic Extent:The 50 United States, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American SamoaCoordinate System:Web Mercator Auxiliary SphereVisible Scale:1:144,000 to 1:1,000Source:USDA Natural Resources Conservation Service Update Frequency:AnnualPublication Date:December 2024 What can you do with this layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS Online Add this layer to a map in the map viewer. The layer is limited to scales of approximately 1:144,000 or larger but avector tile layercreated from the same data can be used at smaller scales to produce awebmapthat displays across the full scale range. The layer or a map containing it can be used in an application.Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections and apply filters. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Change the layer’s style and filter the data. For example, you could set a filter forFarmland Class= "All areas are prime farmland" to create a map of only prime farmland.Add labels and set their propertiesCustomize the pop-upArcGIS Pro Add this layer to a 2d or 3d map. The same scale limit as Online applies in ProUse as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class.Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of theLiving Atlas of the Worldthat provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics. Data DictionaryAttributesKey fields from nine commonly used SSURGO tables were compiled to create the 173 attribute fields in this layer. Some fields were joined directly to the SSURGO Map Unit polygon feature class while others required summarization and other processing to create a 1:1 relationship between the attributes and polygons prior to joining the tables. Attributes of this layer are listed below in their order of occurrence in the attribute table and are organized by the SSURGO table they originated from and the processing methods used on them. Map Unit Polygon Feature Class Attribute TableThe fields in this table are from the attribute table of the Map Unit polygon feature class which provides the geographic extent of the map units. Area SymbolSpatial VersionMap Unit Symbol Map Unit TableThe fields in this table have a 1:1 relationship with the map unit polygons and were joined to the table using the Map Unit Key field. Map Unit NameMap Unit KindFarmland ClassInterpretive FocusIntensity of MappingIowa Corn Suitability Rating Legend TableThis table has 1:1 relationship with the Map Unit table and was joined using the Legend Key field. Project Scale Survey Area Catalog TableThe fields in this table have a 1:1 relationship with the polygons and were joined to the Map Unit table using the Survey Area Catalog Key and Legend Key fields. Survey Area VersionTabular Version Map Unit Aggregated Attribute TableThe fields in this table have a 1:1 relationship with the map unit polygons and were joined to the Map Unit attribute table using the Map Unit Key field. Slope Gradient - Dominant ComponentSlope Gradient - Weighted AverageBedrock Depth - MinimumWater Table Depth - Annual MinimumWater Table Depth - April to June MinimumFlooding Frequency - Dominant ConditionFlooding Frequency - MaximumPonding Frequency - PresenceAvailable Water Storage 0-25 cm - Weighted AverageAvailable Water Storage 0-50 cm - Weighted AverageAvailable Water Storage 0-100 cm - Weighted AverageAvailable Water Storage 0-150 cm - Weighted AverageDrainage Class - Dominant ConditionDrainage Class - WettestHydrologic Group - Dominant ConditionIrrigated Capability Class - Dominant ConditionIrrigated Capability Class - Proportion of Mapunit with Dominant ConditionNon-Irrigated Capability Class - Dominant ConditionNon-Irrigated Capability Class - Proportion of Mapunit with Dominant ConditionRating for Buildings without Basements - Dominant ConditionRating for Buildings with Basements - Dominant ConditionRating for Buildings with Basements - Least LimitingRating for Buildings with Basements - Most LimitingRating for Septic Tank Absorption Fields - Dominant ConditionRating for Septic Tank Absorption Fields - Least LimitingRating for Septic Tank Absorption Fields - Most LimitingRating for Sewage Lagoons - Dominant ConditionRating for Sewage Lagoons - Dominant ComponentRating for Roads and Streets - Dominant ConditionRating for Sand Source - Dominant ConditionRating for Sand Source - Most ProbableRating for Paths and Trails - Dominant ConditionRating for Paths and Trails - Weighted AverageErosion Hazard of Forest Roads and Trails - Dominant ComponentHydric Classification - Presence Rating for Manure and Food Processing Waste - Weighted Average Component Table – Dominant ComponentMap units have one or more components. To create a 1:1 join component data must be summarized by map unit. For these fields a custom script was used to select the component with the highest value for the Component Percentage Representative Value field (comppct_r). Ties were broken with the Slope Representative Value field (slope_r). Components with lower average slope were selected as dominant. If both soil order and slope were tied, the first value in the table was selected. Component Percentage - Low ValueComponent Percentage - Representative ValueComponent Percentage - High ValueComponent NameComponent KindOther Criteria Used to Identify ComponentsCriteria Used to Identify Components at the Local LevelRunoff ClassSoil loss tolerance factorWind Erodibility IndexWind Erodibility GroupErosion ClassEarth Cover 1Earth Cover 2Hydric ConditionHydric RatingAspect Range - Counter Clockwise LimitAspect - Representative ValueAspect Range - Clockwise LimitGeomorphic DescriptionNon-Irrigated Capability SubclassNon-Irrigated Unit Capability ClassIrrigated Capability SubclassIrrigated Unit Capability ClassConservation Tree Shrub GroupGrain Wildlife HabitatGrass Wildlife HabitatHerbaceous Wildlife HabitatShrub Wildlife HabitatConifer Wildlife HabitatHardwood Wildlife HabitatWetland Wildlife HabitatShallow Water Wildlife HabitatRangeland Wildlife HabitatOpenland Wildlife HabitatWoodland Wildlife HabitatWetland Wildlife HabitatSoil Slip PotentialSusceptibility to Frost HeavingConcrete CorrosionSteel CorrosionTaxonomic ClassTaxonomic OrderTaxonomic SuborderGreat GroupSubgroupParticle SizeParticle Size ModCation Exchange Activity ClassCarbonate ReactionTemperature ClassMoist SubclassSoil Temperature RegimeEdition of Keys to Soil Taxonomy Used to Classify SoilCalifornia Storie IndexComponent Key Component Table – Weighted AverageMap units may have one or more soil components. To create a 1:1 join, data from the Component table must be summarized by map unit. For these fields a custom script was used to calculate an average value for each map unit weighted by the Component Percentage Representative Value field (comppct_r). Slope Gradient - Low ValueSlope Gradient - Representative ValueSlope Gradient - High ValueSlope Length USLE - Low ValueSlope Length USLE - Representative ValueSlope Length USLE - High ValueElevation - Low ValueElevation - Representative ValueElevation - High ValueAlbedo - Low ValueAlbedo - Representative ValueAlbedo - High ValueMean Annual Air Temperature - Low ValueMean Annual Air Temperature - Representative ValueMean Annual Air Temperature - High ValueMean Annual Precipitation - Low ValueMean Annual Precipitation - Representative ValueMean Annual Precipitation - High ValueRelative Effective Annual Precipitation - Low ValueRelative Effective Annual Precipitation - Representative ValueRelative Effective Annual Precipitation - High ValueDays between Last and First Frost - Low ValueDays between Last and First Frost - Representative ValueDays between Last and First Frost - High ValueRange Forage Annual Potential Production - Low ValueRange Forage Annual Potential Production - Representative ValueRange Forage Annual Potential Production - High ValueInitial Subsidence - Low ValueInitial Subsidence - Representative ValueInitial Subsidence -

Eelgrass Beds Historic Set:

Historic Eelgrass Points is a 1:24,000-scale, point feature-based layer that depicts the locations of historic eelgrass beds (Zostera marina) in Long Island Sound, the Connecticut River, the Quinnipiac River and other bays, harbors and waterbodies in Connecticut's coastal area. It also includes several points located along the north shore of Long Island. There are a total of 131 point features, the majority of which are located east of the Connecticut River. Point features in this layer are compiled from two major sources: 1) the polygon feature label points in the Historic Eelgrass Beds polygon layer representing sources with a mapping component; and 2) additional points that were based on historic literature review that had no mapping component. Source information including source description and collection date for each point is described in the layer's table data. Feature locations are inexact. Because of the variety of source maps and methods used for their automation, this coverage should be considered to have limited spatial accuracy and is appropriate for general uses only. Actual data collection ranged from 1873 through 1996. This layer was published in 1997 and is not updated. It does not represent current conditions.

Historic Eelgrass Bed Polygons is a 1:24,000-scale, polygon feature-based layer that depicts the locations of historic eelgrass beds (Zostera marina) in Long Island Sound and the Niantic River, as well as in other bays, harbors and waterbodies in Connecticut's coastal area. It also includes several points located along the north shore of Long Island. There are a total of 52 polygon features, all of which (except the Long Island points), are located within or east of the Niantic River. This layer can be used with Historic Eelgrass Points. This layer does not represent current conditions. Rather, it depicts historic eelgrass bed locations that were observed and defined either cartographically or narratively over the course of many years and from various sources. The dates of each source's data collection are noted in the attribute table. Feature locations are inexact. Because of the variety of source maps and methods used for their automation, this information should be considered to have limited spatial accuracy and is appropriate for general uses only. The data was taken from maps of various scales and projections that were drawn between 1905 and 1996. These maps were reduced to approximately 1:24,000 scale and adjusted for best fit; eelgrass areas were redrafted onto USGS Topographic Quadrangle maps for digitizing. In order to create a single polygon coverage, areas were considered to represent a maximum extent of eelgrass beds. This layer was published in 1997 and is not updated.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. Instrumental to the photo interpretive effort was the use of the GPS located vegetation plots collected by the field crew. These plots provided an idea of what the signatures of the individual map units should look like. In addition to the tablular data associated with each vegetation plot were five photographs collected at each plot. These photographs helped not only in identifying the immediate area but also provided us with a “look” at the areas surrounding the vegetation plot which might be a different map unit. These photographs may be “hyperlinked” within ArcMap to the salient vegetation observation point for a better concept of on the ground conditions.All interpreted mylar layers were scanned at 300 dpi. Each scanned mylar was then rectified to the NAIP base layer using recognizable ground features as registration points. The resulting scan produced a raster image that was subsequently vectorized. Each vectorized output was then extensively edited to produce clean digital vector lines. From the digitized vectors we created polygons by building topology in the GIS program. Finally, we created labels for each polygon and used these to add the attribute information. Attribution for all the polygons at CHIC included information pertaining to map units, NVC associations, Anderson land-use classes, and other relevant data. Attribute data were taken directly from the interpreted photos or were added later using the orthophotos as a guide.

Contains legal data from CADASTRAL.LEGAL_FDS, LEGAL, CADASTRAL.LEGAL_RW_ADJSTMNT and CADASTRAL.LEGAL_PLAT. Data is symbolized on the value from L_FEA_SYM. Scale range set to not display at a scale greater than 1:9600. Labels are based on the attribute L_FEA_SYM and do not display when zoomed out beyond 1:2400. Refreshed weekly.

This feature layer provides access to OpenStreetMap (OSM) buildings data for Africa, which is updated every 1 minute with the latest edits. This hosted feature layer view is referencing a hosted feature layer of OSM polygon (closed way) data in ArcGIS Online that is updated with minutely diffs from the OSM planet file. This feature layer view includes building features defined as a query against the hosted feature layer (i.e. building is not blank).In OSM, a building is a man-made structure with a roof, standing more or less permanently in one place. These features are identified with a building tag. There are thousands of different tag values for building used in the OSM database. In this feature layer, unique symbols are used for several of the most popular building types, while lesser used types are grouped in an "other" category.Zoom in to large scales (e.g. Streets level or 1:10k scale) to see the building features display. You can click on a feature to get the name of the building (if available). The name of the building will display by default at large scales (e.g. Street level of 1:5k scale). Labels can be turned off in your map if you prefer.Create New LayerIf you would like to create a more focused version of this buildings layer displaying just one or two building types, you can do that easily! Just add the layer to a map, copy the layer in the content window, add a filter to the new layer (e.g. building is apartments), rename the layer as appropriate, and save layer. You can also change the layer symbols or popup if you like. Esri may publish a few such layers (e.g. parks) that are ready to use, but not for every type of building.Important Note: if you do create a new layer, it should be provided under the same Terms of Use and include the same Credits as this layer. You can copy and paste the Terms of Use and Credits info below in the new Item page as needed.

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE. A spatial representation of subdivision lots and site condominium units. Individual lot and unit boundaries are compiled for subdivision and site condominium developments. Site condominium plans may include building envelopes, general common elements, and limited common elements. Oakland County delineates limited common elements and labels these polygons with the appropriate tax number. For units without a limited common element, the building envelopes are mapped and labeled with the appropriate tax number. By contrast, building condominium plans have an associated set of building plans and the units that are delineated by the building plans are not mapped. For building condominiums, only the exterior boundary of the condominium plan is compiled. In all cases, general common elements are mapped and coded accordingly, unless it is also road, in which case it is coded as road.

Feature Classes are loaded onto tablet PCs and Field crews are sent to label the crop or land cover type and irrigation method for a subset of select fields or polygons. Each tablet PC is attached to a GPS unit for real-time tracking to continuously update the field crew’s location during the field labeling process.Digitizing is done as Geodatabase feature classes using ArcMap 10.X with NAIP or Google imagery as a background with other layers added for reference. Updates to existing field boundaries of individual agricultural fields, urban areas and more are precisely digitized. Changes in irrigation type and land use are noted during this process.Cropland Data Layer (CDL) rasters from the United States Department of Agriculture (USDA) National Agricultural Statistics Service (NASS) are downloaded for the appropriate year. https://nassgeodata.gmu.edu/CropScape/Zonal Statistics geoprocessing tools are used to attribute the polygons with updated crop types from the CDL. The data is then run through several stages of comparison to historical inventories and quality checking in order to determine and produce the final attributes.LUID - Unique ID number for each polygon in the final dataset, not consistent between yearly datasets.Landuse - A general land cover classification differentiating how the land is used.Agriculture: Land managed for crop or livestock purposes.Other: A broad classification of wildland.Riparian/Wetland: Wildland influenced by a high water table, often close to surface water.Urban: Developed areas, includes urban greenspace such as parks.Water: Surface water such as wet flats, streams, and lakes.CropGroup - Groupings of broader crop categories to allow easy access to or query of all orchard or grain types etc.Description - Attribute that describes/indicates the various crop types and land use types determined by the GIS process.IRR_Method - Crop Irrigation Method carried over from statewide field surveys ending in 2015 and updated based on imagery and yearly field checks.Drip: Water is applied through lines that slowly release water onto the surface or subsurface of the crop.Dry Crop: No irrigation method is applied to this agricultural land, the crop is irrigated via natural processes.Flood: Water is diverted from ditches or pipes upland from the crop in sufficient quantities to flood the irrigated plot.None: Associated with non-agricultural landSprinkler: Water is applied above the crop via sprinklers that generally move across the field.Sub-irrigated: This land does not have irrigation water applied, but due to a high water table receives more water, and is generally closely associated with a riparian area.Acres - Calculated acreage of the polygon.State - State where the polygons are found.Basin - The hydrologic basin where the polygons are found, closely related to HUC 6. These basin boundaries were created by DWRe to include portions of other basins that have inter-basin flows for management purposes.SubArea - The subarea where the polygons are found, closely related to the HUC 8. Subareas are subdivisions of the larger hydrologic basins created by DWRe.Label_Class - Combination of Label and Class_Name fields created during processing that indicates the specific crop, irrigation, and whether the CDL classified the land as a similar crop or an “Other” crop.LABEL - A shorthand descriptive label for each crop description and irrigation type.Class_Name - The majority pixel value from the USDA CDL Cropscape raster layer within the polygon, may differ from final crop determination (Description).OldLanduse - Similar to Landuse, but splits the agricultural land further depending on irrigation. Pre-2017 datasets defined this as Landuse.LU_Group - These codes represent some in-house groupings that are useful for symbology and other summarizing.Field_Check - Indicates the year the polygon was last field checked. *New for 2019SURV_YEAR - Indicates which year/growing season the data represents.

This feature layer provides access to OpenStreetMap (OSM) leisure areas data for Africa, which is updated every 15 minutes with the latest edits. This hosted feature layer view is referencing a hosted feature layer of OSM polygon (closed way) data in ArcGIS Online that is updated with minutely diffs from the OSM planet file. This feature layer view includes leisure features defined as a query against the hosted feature layer (i.e. leisure is not blank).In OSM, a leisure area is a place where people go in their spare time. These features are identified with a leisure tag. There are thousands of different tag values for leisure used in the OSM database. In this feature layer, unique symbols are used for several of the most popular leisure types, while lesser used types are grouped in an "other" category.Zoom in to large scales (e.g. City level or 1:80k scale) to see the leisure area features display. You can click on a feature to get the name of the leisure area (if available). The name of the leisure area will display by default at large scales (e.g. Street level of 1:5k scale). Labels can be turned off in your map if you prefer.Create New LayerIf you would like to create a more focused version of this leisure areas layer displaying just one or two leisure types, you can do that easily! Just add the layer to a map, copy the layer in the content window, add a filter to the new layer (e.g. leisure is stadium), rename the layer as appropriate, and save layer. You can also change the layer symbols or popup if you like. Esri may publish a few such layers (e.g. parks) that are ready to use, but not for every type of leisure area.Important Note: if you do create a new layer, it should be provided under the same Terms of Use and include the same Credits as this layer. You can copy and paste the Terms of Use and Credits info below in the new Item page as needed.

This feature layer provides access to OpenStreetMap (OSM) buildings data for Central America and Caribbean, which is updated every 1 minute with the latest edits. This hosted feature layer view is referencing a hosted feature layer of OSM polygon (closed way) data in ArcGIS Online that is updated with minutely diffs from the OSM planet file. This feature layer view includes building features defined as a query against the hosted feature layer (i.e. building is not blank).In OSM, a building is a man-made structure with a roof, standing more or less permanently in one place. These features are identified with a building tag. There are thousands of different tag values for building used in the OSM database. In this feature layer, unique symbols are used for several of the most popular building types, while lesser used types are grouped in an "other" category.Zoom in to large scales (e.g. Streets level or 1:10k scale) to see the building features display. You can click on a feature to get the name of the building (if available). The name of the building will display by default at large scales (e.g. Street level of 1:5k scale). Labels can be turned off in your map if you prefer.Create New LayerIf you would like to create a more focused version of this buildings layer displaying just one or two building types, you can do that easily! Just add the layer to a map, copy the layer in the content window, add a filter to the new layer (e.g. building is apartments), rename the layer as appropriate, and save layer. You can also change the layer symbols or popup if you like. Esri may publish a few such layers (e.g. parks) that are ready to use, but not for every type of building.Important Note: if you do create a new layer, it should be provided under the same Terms of Use and include the same Credits as this layer. You can copy and paste the Terms of Use and Credits info below in the new Item page as needed.

Feature Classes are loaded onto tablet PCs and Field crews are sent to label the crop or land cover type and irrigation method for a subset of select fields or polygons. Each tablet PC is attached to a GPS unit for real-time tracking to continuously update the field crew’s location during the field labeling process.Digitizing is done as Geodatabase feature classes using ArcMap 10.X with NAIP or Google imagery as a background with other layers added for reference. Updates to existing field boundaries of individual agricultural fields, urban areas and more are precisely digitized. Changes in irrigation type and land use are noted during this process.Cropland Data Layer (CDL) rasters from the United States Department of Agriculture (USDA) National Agricultural Statistics Service (NASS) are downloaded for the appropriate year. https://nassgeodata.gmu.edu/CropScape/Zonal Statistics geoprocessing tools are used to attribute the polygons with updated crop types from the CDL. The data is then run through several stages of comparison to historical inventories and quality checking in order to determine and produce the final attributes.2018 marked the first year a comparison could be made using the CDL methodology. The comparison between 2017 and 2018 showed a large change in agricultural land use to other land use. It was determined this shift was due to crop land being allowed to sit fallow for a season and did not represent a shift away from agricultural land. The following code amended the data:*************************************************************************************************************************************####On 02/07/2020 this dataset was amended with the following R script to better reflect agricultural land changes:require(arcgisbinding)arc.check_product()####Bring in layersLU17<-arc.open("Path to data")LU17<-arc.select(LU17)#####Amend dataLU17$Landuse[LU17$Class_Name=='Fallow/Idle Cropland' & LU17$Description== 'Dry Land/Other']<-"Agricultural"LU17$CropGroup[LU17$Class_Name=='Fallow/Idle Cropland' & LU17$Description== 'Dry Land/Other']<-"Fallow/Idle"LU17$IRR_Method[LU17$Class_Name=='Fallow/Idle Cropland' & LU17$Description== 'Dry Land/Other']<-"Dry Crop"arc.write("Path to data", LU17)*************************************************************************************************************************************LUID -Unique ID number for each polygon in the final dataset, matches object.Landuse - Land use type, similar to land cover and represents our own categories of how the land is used.CropGroup - Groupings of broader crop categories to allow easy access to or query of all orchard or grain types etc.Description - Attribute that describes/indicates the various crop types and land use types determined by the GIS process.IRR_Method - Crop Irrigation Methods.Acres - Calculated acreage of the polygon.State - Spatial intersection identifying the State where the polygons are found.County - Spatial intersection identifying the County where the polygons are found.Basin - Spatial intersection identifying the Basin where the polygons are found. Basins, or Utah Hydrologic Basins are large watersheds created by DWRe.SubArea - Spatial intersection identifying the Subarea where the polygons are found. Subareas are subdivisions of the larger hydrologic basins created by DWRe.Label_Class - Combination of Label and Class_Name fields created during processing that indicates specific cover and use types.LABEL - Old shorthand descriptive label for each crop and irrigation type or land use type.Class_Name - Zonal Statistics majority value derived from the USDA CDL Cropscape raster layer, may differ from final crop determination.OldLanduse - This is the old short code found under landuse in past datasets and is kept to maintain connectivity with historical data.LU_Group - These codes represent some in-house groupings that are useful for symbology and other summarizing.SURV_YEAR - Indicates which year/growing season the data represents. Is useful when comparing to past layers.

World Continents represents the boundaries for the continents of the world.This layer is best viewed out beyond a maximum scale (zoomed in) of 1:3,000,000. The sources of this dataset are Esri, Global Mapping International (GMI), U.S. Central Intelligence Agency (The World Factbook), and Garmin. It is updated as country boundaries coincident to continental boundaries change. To download the data for this layer as a layer package for use in ArcGIS desktop applications, refer to World Continents.

A continuous area within the statutory boundary of an incorporated city, which is the smallest subdivision of an annexed area. It is represented as spatial data (polygon with label point). The use of city limits information was identified as a need for general planning purposes within ODOT. It was determined that this would be a frequently used data set that needed to be both spatially referenced and attributed in a GIS base layer. The decision was made to create a statewide coverage of the boundary outlining the city limits for each of the 240 incorporated cities. An incorporated city may have multiple areas that are not contiguous. Each such area is represented separately with its own polygon. The area of the city limits will be calculated from the polygons created.

This feature layer provides access to OpenStreetMap (OSM) landuse areas data for Africa, which is updated every 15 minutes with the latest edits. This hosted feature layer view is referencing a hosted feature layer of OSM polygon (closed way) data in ArcGIS Online that is updated with minutely diffs from the OSM planet file. This feature layer view includes landuse features defined as a query against the hosted feature layer (i.e. landuse is not blank).In OSM, landuse describes the primary use of land by humans. These features are identified with a landuse tag. There are thousands of different tag values for landuse used in the OSM database. In this feature layer, unique symbols are used for several of the most popular landuse types, while lesser used types are grouped in an "other" category.Zoom in to large scales (e.g. City level or 1:80k scale) to see the landuse area features display. You can click on a feature to get the name of the landuse area (if available). The name of the landuse area will display by default at large scales (e.g. Street level of 1:5k scale). Labels can be turned off in your map if you prefer.Create New LayerIf you would like to create a more focused version of this landuse areas layer displaying just one or two landuse types, you can do that easily! Just add the layer to a map, copy the layer in the content window, add a filter to the new layer (e.g. landuse is commercial), rename the layer as appropriate, and save layer. You can also change the layer symbols or popup if you like. Esri may publish a few such layers (e.g. residential, forest) that are ready to use, but not for every type of landuse area.Important Note: if you do create a new layer, it should be provided under the same Terms of Use and include the same Credits as this layer. You can copy and paste the Terms of Use and Credits info below in the new Item page as needed.

Click to downloadClick for metadataService URL: https://gis.dnr.wa.gov/site2/rest/services/Public_Forest_Practices/WADNR_PUBLIC_FP_Unstable_Slopes/MapServer/3The siteclass data layer was created for use in implementing Forest Practices' Riparian Management Rules. (See WAC 222-30-021 and 222-30-022.)

The siteclass data layer was derived from the DNR soils data layer's site index codes and major tree species codes for western and eastern Washington soils contained in the layer's Soils-Main table and Soils-Pflg (private forest land grade) table. Site index ranges in the Soils_PFLG took precedence over site index ranges in the Soils-Main table where data existed.The siteclass data layer was created for use in implementing new ForestPractices' Riparian Management Rules. (See WAC 222-30-021 and 222-30-022.) The siteclass information was derived from the DNR soils data layer's site indexcodes and major tree species codes for western and eastern Washington soilscontained in the layer's Soils-Main table and Soils-Pflg (private forest landgrade) table. Site index ranges in the Soils_PFLG took precedence over siteindex ranges in the Soils-Main table where data existed.Siteclass codes as derived from the soil survey:For Western Washington, the 50 year site index is used SITECLASS SITE INDEX RANGE I 137+ II 119-136 III 97-118 IV 76-96 V 1-75For Eastern Washington, the 100 year site index is used SITECLASS SITE INDEX RANGE I 120+ II 101-120 III 81-100 IV 61-80 V 1-60In addition to the coding scheme above, the following codes were added forrule compliance: SITECLASS DESCRIPTION 6 (Red Alder) The soils major species code indicated Red Alder 7 (ND/GP) No data), NA, or gravel pit 8 (NC/MFP) Non-commercial or marginal commercial forest land 9 (WAT) Water body(Rule note: If the site index does not exist or indicates red alder,noncommercial, or marginally commercial species, the following apply:If the whole RMZ width is within those categories, use site class V.If those categories occupy only a portion of the RMZ width, then use thesite index for conifer in the adjacent soil polygon.)WADNR SOILS LAYER INFORMATION LAYER: SOILS GEN.SOURCE: State soils mapping program CODE DOCUMENT: State soil surveys CONTACT: NA COVER TYPE: Spatial polygon coverage DATA TYPE: Primary data Information for the 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 forest land taxation. It was funded by the Washington State Department of Revenue in cooperation with the Department of Natural Resources, Soil Conservation Service (SCS), USDA Forest Service and Washington State University. State and private lands which had the potential of supporting commercial forest stands were surveyed. Some Indian tribal and federal lands were surveyed. Because this was a cooperative soil survey project, agricultural and non- commercial forest lands 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. Approximately 1100 townships wholly or partially contain digitized soils data (2101 townships would provide complete coverage of the state of Washington). SOILS data are currently stored in the Polygon Attribute Table (.PAT) and INFO expansion files. COORDINATE SYSTEM: WA State Plane South Zone (5626) (N. zone converted to S. zone) COORDINATE UNITS: Feet HORIZONTAL DATUM: NAD27 PROJECTION NAME: Lambert Conformal Conic **** MAJOR CODES USED FOR SITECLASS DATA*****PFLG DATA: ITEM: PFLG.MAJ.SPEC TITLE: Potential major tree species for given soil FORMAT: INPUT OUTPUT DATA DECIMAL ARRAY ARRAY WIDTH WIDTH TYPE PLACES OCCUR. INDEX ------------------------------------------------- 3 3 C 0 0 0 CODE TABLE OR VALUE RANGE: SOIL.MAJ.SPEC.CODE DESCRIPTION: Potentially major tree species for a given soil type. The data carried by this item describes a major commercial tree species that could potentially grow on a specific soil type as identified in the Private Forest Land Grading program (PFLG). Non-tree codes are also included to map non-soil ground cover, e.g. water, gravel pits. ITEM: PFLG.SITE.INDEX TITLE: Mean site index calc.from trees on given soil FORMAT: INPUT OUTPUT DATA DECIMAL ARRAY ARRAY WIDTH WIDTH TYPE PLACES OCCUR. INDEX ------------------------------------------------- 3 3 I 0 0 0 CODE TABLE OR VALUE RANGE: 0-200 DESCRIPTION: Site index data collected for the Private Forest Land Grading soils program (PFLG). It is a designation of the quality of a forest site based on the height of of the tallest trees (dominant and co-dominant trees) in a stand at an arbitrarily chosen age. Usually the age chosen is 50 or 100 years. For example, if the average height attained by the tallest trees in a fully stocked stand at the age of 50 years is 75 feet, the site index is 75 feet. Westside site conditions are estimated by using an index age of 50 years, while eastside site conditions are estimated by using an index age of 100 years.--------------------------------------------------------------------SOILS-MAIN DATA: CODE TABLE NAME: SOIL.MAJ.SPEC.CODE ----------------------------------------------------------------------------- CODE MAP/REPORT MAP CODE DESCRIPTION LABEL SYMB --------- ------------ ---- -------------------------------------------------- AF ALPINE FIR 0 Subalpine fir DF DOUGLAS FIR 0 Douglas fir GF GRAND FIR 0 Grand fir GP GRAVEL PIT 0 Gravel pit LP LODGEPOLE PN 0 Lodgepole pine MFP MAR FOR PROD 0 Marginal forest productivity NA N/A 0 Not applicable NC NON-COMMERC 0 Non-commercial ND NO DATA 0 No data PP PONDEROSA PN 0 Ponderosa pine RA RED ALDER 0 Red alder WAT WATER 0 Water WH W HEMLOCK 0 Western hemlock WL W LARCH 0 Western larch WP W WHITE PINE 0 Western white pine ITEM: SITE.INDEX.SIDE TITLE: Indicates 100 yr or 50 yr soil site index FORMAT: INPUT OUTPUT DATA DECIMAL ARRAY ARRAY WIDTH WIDTH TYPE PLACES OCCUR. INDEX ------------------------------------------------- 1 1 C 0 0 0 CODE FILE OR VALUE RANGE: SITE.INDEX.SIDE.CODE DESCRIPTION: Code used to indicate whether 100 year or 50 year site index tables are used to calculate the site index of a soil type. Note that some site indexes for "eastside" soils are based on the 50 year index table. SITE.INDEX.SIDE Indicates 100 yr or 50 yr soil site index CODE FILE SITE.INDEX.SIDE.CODE IS NOT USED BY OTHER ITEMS CODE MAP/REPORT MAP CODE DESCRIPTION LABEL SYMB --------- ------------ ---- -------------------------------------------------- E 100 YR SITE 0 Soil site index based on 100 year table W 50 YR SITE 0 Soil site index based on 50 year table------------------------------------------------------------------

The FacilitySitePoint feature class is used to label Community maps Landmarks polygon features and other significant features that are too small to create polygons for (ex. Bakersfield Arch).

METWP24PD depicts dissolved political boundaries for all Organized Towns and Unorganized Territories in Maine at 1:24,000 scale. "Dissolved" means that municipalities or townships with multiple disconnected entities (ex. islands) are grouped as multipart polygons in a single geometry with the appropriate municipality or township label and attribute data. This approach reduces the number of labels required and improves layer drawing performance for low-bandwidth environments. Example: a town has 430 distinct island entities that are all labeled as "town" in addition to the municipality itself. When dissolved, it has only one geometry that includes all 430 entities' combined area and attributes with the municipality, and one label of "town". METWP24PD includes common town names and authoritative geocodes in its attribute information. The layer was created using the USGS 7.5-minute map series and the Maine GIS base layer COAST, which contains Maine's coastal Mean High Water (MHW) mark and Maine islands. To correct mapping errors and reflect changes to Minor Civil Division (MCD) boundaries, arcs and polygons were added or updated using the following data sources: photorevised USGS data; Maine GIS base layer coincident features; legal descriptions; GPS data; and Maine Department of Transportation (MEDOT) engineering plans. METWP24P also contains USGS 1:100,000-scale data and U.S. Department of Commerce Census Bureau TIGER Line Files from 1990 and 2000 where these provide a more correct or best available representation of a feature in question.

Northeastern United States Town Boundary data are intended for geographic display of state, county and town (municipal) boundaries at statewide and regional levels. Use it to map and label towns on a map. These data are derived from Northeastern United States Political Boundary Master layer. This information should be displayed and analyzed at scales appropriate for 1:24,000-scale data. The State of Connecticut, Department of Environmental Protection (CTDEP) assembled this regional data layer using data from other states in order to create a single, seamless representation of political boundaries within the vicinity of Connecticut that could be easily incorporated into mapping applications as background information. More accurate and up-to-date information may be available from individual State government Geographic Information System (GIS) offices. Not intended for maps printed at map scales greater or more detailed than 1:24,000 scale (1 inch = 2,000 feet.)