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. were derived from the NVC. NatureServe developed a preliminary list of potential vegetation types. These data were combined with existing plot data (Cully 2002) to derive an initial list of potential types. Additional data and information were gleaned from a field visit and incorporated into the final list of map units. Because of the park’s small size and the large amount of field data, the map units are equivalent to existing vegetation associations or local associations/descriptions (e.g., Prairie Dog Colony). In addition to vegetation type, vegetation structures were described using three attributes: height, coverage density, and coverage pattern. In addition to vegetation structure and context, a number of attributes for each polygon were stored in the associated table within the GIS database. Many of these attributes were derived from the photointerpretation; others were calculated or crosswalked from other classifications. Table 2.7.2 shows all of the attributes and their sources. Anderson Level 1 and 2 codes are also included (Anderson et al. 1976). These codes should allow for a more regional perspective on the vegetation types. Look-up tables for the names associated with the codes is included within the geodatabase and in Appendix D. The look-up tables contain all the NVC formation information as well as alliance names, unique IDs, and the ecological system codes (El_Code) for the associations. These El_Codes often represent a one-to-many relationship; that is, one association may be related to more than one ecological system. The NatureServe conservation status is included as a separate item. Finally, slope (degrees), aspect, and elevation were calculated for each polygon label point using a digital elevation model and an ArcView script. The slope figure will vary if one uses a TIN (triangulated irregular network) versus a GRID (grid-referenced information display) for the calculation (Jenness 2005). A grid was used for the slope figure in this dataset. Acres and hectares were calculated using XTools Pro for ArcGIS Desktop.

View metadata for key information about this dataset.The arc layer contains street name attributes for labeling the outside of the polygons. Certain arcs in the arc layer contain data signifying information relating it to the polygon layer. It can tell you if both sides of the arc belong to one of the bounding polygons. All the arcs, including those with no boundary info, have naming attributes for labeling the polygon borders. Contact the Streets GIS unit for public consumption.See also the related polygon layer for Leaf Collection Areas.For questions about this dataset, contact max.steinbrenner@phila.gov. For technical assistance, email maps@phila.gov.

(Link to Metadata) Generated from exact latitude-longitude coordinates and projected from Geographic coordinates (Lat/Long) NAD83 into State Plane Meters NAD83. The Arc/Info GENERATE command was used with the following parameters; generate BoundaryTile_QUAD83 fishnet no labels -73.500,42.625 -73.500,42.725 0.125,0.125 20,17 The Arc/Info project command was then used to re-project from Geographic (DD)NAD83 into Vermont State Plane Meters (NAD83). Extraneous polygons where removed. Polygon label points where transfered from the QUAD coverage into the new coverage, resulting in duplicate attribute items. The tics in this data layer should only be used for digitizing if your source data is in NAD83! Use BoundaryTile_QUAD27 if your source data is in NAD27. In both cases you should re-project this coverage into UTM before digitizing. When you've completed your digitizing work re-project the data back into Vermont State Plane Meters NAD83.

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

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. Spatial data from field observation points and quantitative plots were used to edit the formation-level maps of Colonial National Historical Park to better reflect vegetation classes. Using ArcView 3.3, polygon boundaries were revised onscreen over leaf-off photography. Units used to label polygons on the map (i.e. map classes) are equivalent to one or more vegetation classes from the regional vegetation classification, or to a land-use class from the Anderson (Anderson et al. 1976) Level II classification system. Each polygon on the Colonial National Historical Park map was assigned to one of forty map classes based on plot data, field observations, aerial photography signatures, and topographic maps. The mapping boundary was based on park boundary data obtained Colonial National Historical Park in May 2003. The mapping boundary includes lands under a scenic easement at Swanns Point and it excludes the Cheatham Annex, an area that returned to US Navy ownership in February 2004. The vegetation map was clipped at the park boundary because areas outside the park were not surveyed or included in the accuracy assessment.

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. Spatial data from field observation points and quantitative plots were used to edit the formation-level maps of Petersburg National Battlefield to better reflect vegetation classes. Using ArcView 3.3, polygon boundaries were revised onscreen over leaf-off photography. Units used to label polygons on the map (i.e. map classes) are equivalent to one or more vegetation classes from the regional vegetation classification, or to a land-use class from the Anderson (Anderson et al. 1976) Level II classification system. Each polygon on the Petersburg National Battlefield map was assigned to one of twenty map classes based on plot data, field observations, aerial photography signatures, and topographic maps. The mapping boundary was based on park boundary data obtained from Petersburg National Battlefield in May 2006. Spatial data depicting the locations of earthworks was obtained from the park and used to identify polygons of the cultural map classes Open Earthworks and Forested Earthworks. One map class used to attribute polygons combines two similar associations that, in some circumstances, are difficult to distinguish in the field. The vegetation map was clipped at the park boundary because areas outside the park were not surveyed or included in the accuracy assessment. Twenty map classes were used in the vegetation map for Petersburg National Battlefield. Map classes are equivalent to one or more vegetation classes from the regional vegetation classification, or to a land-use class from the Anderson (Anderson et al. 1976) Level II classification system.

Connecticut and Vicinity 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.)

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.

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

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.

Spatial data from observation points and quantitative plots were used to edit the formation-level maps of George Washington Birthplace National Monument to better reflect homogeneous vegetation classes. Using Arcview 3.3, polygon boundaries were revised onscreen over leaf-off photography. Units used to label polygons on the map (i.e. map classes) are equivalent to one or more vegetation classes from the regional vegetation classification, or to a land-use class from the Anderson Level II classification system. Each polygon on the George Washington Birthplace National Monument map was assigned to one of 19 map classes based on plot data, field observations, aerial photography signatures, and topographic maps.

This data represents the State of Oregon city limit boundaries. Each city limit is defined as 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).

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.

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

Polygons used to label the Zoning Map Height Limit.

For a file geodatabase (.gdb) Click Here (includes files used to create data).For the final report, full documentation, and metadata Click Here.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 ArcPro 2.6.3 with Sentinel 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.AttributesLanduse– A general land cover classification differentiating how the land is usedAgriculture: Land managed for crop or livestock purposesOther: A broad classification of wildlandRiparian/Wetland: Wildland influenced by a high water table, often close to surface waterUrban: 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 cropDry 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 plotNone: 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 areaAcres– Calculated acreage of the polygon. State– State where the polygons are found. County– County 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.SURV_YEAR– Indicates which year/growing season the data represents.

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. The transfer process for the CHCU vegetation mapping project involved taking the interpreted line work and rendering it into a comprehensive digital network of attributed polygons. To accomplish this, we created an ArcInfo© GIS database using in-house protocols. The protocols consist of a shell (master file) of Arc Macro Language (AML) scripts and menus (nearly 100 files) that automate the transfer process, thus insuring that all spatial and attribute data are consistent and stored properly. The actual transfer of information from the interpreted orthophotos to a digital, geo-referenced format involved scanning, rasterizing, vectorizing, cleaning, building topology, and labeling each polygon.

Yukon Bedrock Geology Map This update of the Yukon bedrock geology map builds upon the previous compilation by Gordey and Makepeace (1999, 2001). It includes new, detailed bedrock geology maps and regional compilations that have been published by the Yukon Geological Survey and the Geological Survey of Canada between 1999 and 2015, as well as some recent thesis works. A few of these maps were partially integrated into the digital dataset by Gordey and Makepeace (2003), but only as overlay to the 1999 compilation. A number of errors and omissions from the 1999 compilation of Gordey and Makepeace were also noted and corrected during compilation of this version of the map. The Yukon bedrock geology GIS dataset is regularly updated and can be downloaded from the Yukon Geological Survey ' s website: https://yukon.ca/en/science-and-natural-resources/geology . Users are advised to consult the website regularly to ensure they are working with the latest version of the geodatabase or shape files. This update of the GIS dataset includes an expanded attribute structure (compared to the 1999 dataset) that facilitates searching of the geodatabase. This dataset requires the gscGeology font in order to properly label the bedrock polygons. This font file is packaged with the dataset when downloaded from https://yukon.ca/maps or https://yukon.ca/en/science-and-natural-resources/geology . The Yukon Geological Survey aims to provide users with the best available geoscience data for Yukon. Any revisions or additional geological information known to the user would be welcomed by the Yukon Geological Survey. Distributed from GeoYukon by the Government of Yukon . Discover more digital map data and interactive maps from Yukon's digital map data collection. For more information: geomatics.help@yukon.ca

This dataset is one of a number of datasets containing geomorphological data relating to the Windmill Islands, Wilkes Land, Antarctica. The dataset comprises of a digital polygon/point coverage of lakes and ponds identified from documented field observations compiled by Dr Ian D Goodwin from his own field notes as well as topographic and surface lake features identified and interpreted on aerial photographs taken by AUSLIG (now Geoscience Australia) in the 1993-94 field season. Each lake/pond is represented as a polygon with a central point label which is linked to a separate digital database (ie attribute tables) containing additional information. Sediment samples collected predominantly along the shoreline of these lakes represent a chronology of glacial events/influences on these lakes. Sediment samples taken as a profiled sequence or core can be dated using radiocarbon dating to provide a chronological picture and age occurance of deglaciation and glaciation cycles within the Windmill Islands.

Maine County Boundary Polygons Dissolved contains county boundary polygons for all sixteen counties in Maine, mapped at the 1:24,000 scale. "Dissolved" means that counties with multiple disconnected entities (ex. islands) are grouped as multipart polygons in a single geometry with the appropriate county label and attribute data. This approach reduces the number of labels required and improves layer drawing performance for low-bandwidth environments. The data layer has polygon topology and was originally created in ArcInfo using METWP24P with a selection on arcs coded "TYPE = state, county, and coastline".

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.