Natural Earth is a public domain map dataset available at 1:10m, 1:50m, and 1:110 million scales. Featuring tightly integrated vector and raster data, with Natural Earth you can make a variety of visually pleasing, well-crafted maps with cartography or GIS software.

Natural Earth was built through a collaboration of many volunteers and is supported by NACIS (North American Cartographic Information Society).

Natural Earth Vector comes in ESRI shapefile format, the de facto standard for vector geodata. Character encoding is Windows-1252.

Natural Earth Vector includes features corresponding to the following:

Cultural Vector Data Thremes:

• Countries: matched boundary lines and polygons with names attributes for countries and sovereign states. Includes dependencies (French Polynesia), map units (U.S. Pacific Island Territories) and sub-national map subunits (Corsica versus mainland Metropolitan France).
• Disputed areas and breakaway regions - From Kashmir to the Elemi Triangle, Northern Cyprus to Western Sahara.
• First order admin (provinces, departments, states, etc.): internal boundaries and polygons for all but a few tiny island nations. Includes names attributes and some statistical groupings of the same for smaller countries.
• Populated places: point symbols with name attributes. Includes capitals, major cities and towns, plus significant smaller towns in sparsely inhabited regions. We favor regional significance over population census in determining rankings.
• Urban polygons: derived from 2002-2003 MODIS satellite data.
• Parks and protected areas: US National Park Service units.
• Pacific nation groupings: boxes for keeping these far-flung islands tidy.
• Water boundary indicators: partial selection of key 200-mile nautical limits, plus some disputed, treaty, and median lines.

Physical Vector Data Themes:

• Coastline: ocean coastline, including major islands. Coastline is matched to land and water polygons.
• Land: Land polygons including major islands
• Ocean: Ocean polygon split into contiguous pieces.
• Minor Islands: additional small ocean islands ranked to two levels of relative importance.
• Reefs: major coral reefs from WDB2.
• Physical region features: polygon and point labels of major physical features.
• Rivers and Lake Centerlines: ranked by relative importance. Includes name and line width attributes. Don’t want minor lakes? Turn on their centerlines to avoid unseemly data gaps.
• Lakes: ranked by relative importance, coordinating with river ranking. Includes name attributes.
• Glaciated areas: polygons derived from DCW, except for Antarctica derived from MOA. Includes name attributes for major polar glaciers.
• Antarctic ice shelves: derived from 2003-2004 MOA. Reflects recent ice shelf collapses.
• Bathymetry: nested polygons at 0, -200, -1,000, -2,000, -3,000, -4,000, -5,000, -6,000, -7,000, -8,000, -9,000,and -10,000 meters. Created from SRTM Plus.
• Geographic lines: Polar circles, tropical circles, equator, and International Date Line.
• Graticules: 1-, 5-, 10-, 15-, 20-, and 30-degree increments. Includes WGS84 bounding box.

This is a vector tile service with labels for the fine scale vegetation and habitat map, to be used in web maps and GIS software packages. Labels appear at scales greater than 1:5,000 and show the full Latin name or vegetation group name. At scales smaller than 1:5,000 the abbreviated vegetation class name is displayed. This service is mean to be used in conjunction with the vector tile services of the veg map polygons (either the solid symbology service or the hollow symbology service). The key to map class abbreviations can be found here. The Sonoma County fine scale vegetation and habitat map is an 82-class vegetation map of Sonoma County with 212,391 polygons. The fine scale vegetation and habitat map represents the state of the landscape in 2013 and adheres to the National Vegetation Classification System (NVC). The map was designed to be used at scales of 1:5,000 and smaller. The full datasheet for this product is available here: https://sonomaopenspace.egnyte.com/dl/qOm3JEb3tD The final report for the fine scale vegetation map, containing methods and an accuracy assessment, is available here: https://sonomaopenspace.egnyte.com/dl/1SWyCSirE9Class definitions, as well as a dichotomous key for the map classes, can be found in the Sonoma Vegetation and Habitat Map Key (https://sonomaopenspace.egnyte.com/dl/xObbaG6lF8) The fine scale vegetation and habitat map was created using semi-automated methods that include field work, computer-based machine learning, and manual aerial photo interpretation. The vegetation and habitat map was developed by first creating a lifeform map, an 18-class map that served as a foundation for the fine-scale map. The lifeform map was created using “expert systems” rulesets in Trimble Ecognition. These rulesets combine automated image segmentation (stand delineation) with object based image classification techniques. In contrast with machine learning approaches, expert systems rulesets are developed heuristically based on the knowledge of experienced image analysts. Key data sets used in the expert systems rulesets for lifeform included: orthophotography (’11 and ’13), the LiDAR derived Canopy Height Model (CHM), and other LiDAR derived landscape metrics. After it was produced using Ecognition, the preliminary lifeform map product was manually edited by photo interpreters. Manual editing corrected errors where the automated methods produced incorrect results. Edits were made to correct two types of errors: 1) unsatisfactory polygon (stand) delineations and 2) incorrect polygon labels. The mapping team used the lifeform map as the foundation for the finer scale and more floristically detailed Fine Scale Vegetation and Habitat map. For example, a single polygon mapped in the lifeform map as forest might be divided into four polygons in the in the fine scale map including redwood forest, Douglas-fir forest, Oregon white oak forest, and bay forest. The fine scale vegetation and habitat map was developed using a semi-automated approach. The approach combines Ecognition segmentation, extensive field data collection, machine learning, manual editing, and expert review. Ecognition segmentation results in a refinement of the lifeform polygons. Field data collection results in a large number of training polygons labeled with their field-validated map class. Machine learning relies on the field collected data as training data and a stack of GIS datasets as predictor variables. The resulting model is used to create automated fine-scale labels countywide. Machine learning algorithms for this project included both Random Forests and Support Vector Machines (SVMs). Machine learning is followed by extensive manual editing, which is used to 1) edit segment (polygon) labels when they are incorrect and 2) edit segment (polygon) shape when necessary. The map classes in the fine scale vegetation and habitat map generally correspond to the alliance level of the National Vegetation Classification, but some map classes - especially riparian vegetation and herbaceous types - correspond to higher levels of the hierarchy (such as group or macrogroup).

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.

Seamless and topologically robust derivative of VMap0 -Ed5 polygonal Ocean/Sea data layers. The OCSEA_PY shapefile data layer is comprised of 25 derivative vector framework library features derived based on 1:1 000 000 data originally from VMap0, 5th Edition. The layer provides nominal analytical/mapping at 1:1 000 000. Data processing complete globally, this is an African subset. Acronyms and Abbreviations: VMap0 - Vector Map for Level 0.

This vector dataset provides polygons that represent significant golf course facility locations in Suffolk County. These courses can be publicly (State, County, Town, Village) or privately owned. This dataset can be linked with the GolfCoursePoint feature class by the FACILITYID field. In some cases, there may be multiple Golf Course Points for a single Golf Course Polygon. These data are organized for consumption in desktop and web applications.

Seamless and topologically robust derivative of VMap0 - Ed5 data layers. The PPL_PY shapefile data layer is comprised of 1505 derivative vector framework library features derived based on 1:1 000 000 data originally from VMap0, 5th Edition. The layer provides nominal analytical/mapping at 1:1 000 000. Data processing complete globally, this is an African subset. Acronyms and Abbreviations: VMap0 - Vector Map for Level 0.

The Millennium Coral Reef Mapping Project provides thematic maps of coral reefs worldwide at geomorphological scale. Maps were created by photo-interpretation of Landsat 7 and Landsat 8 satellite images. Maps are provided as standard Shapefiles usable in GIS software. The geomorphological classification scheme is hierarchical and includes 5 levels. The GIS products include for each polygon a number of attributes. The 5 level geomorphological attributes are provided (numerical codes or text). The Level 1 corresponds to the differentiation between oceanic and continental reefs. Then from Levels 2 to 5, the higher the level, the more detailed the thematic classification is. Other binary attributes specify for each polygon if it belongs to terrestrial area (LAND attribute), and sedimentary or hard-bottom reef areas (REEF attribute). Examples and more details on the attributes are provided in the references cited. The products distributed here were created by IRD, in their last version. Shapefiles for 11 atolls of the Caribbean and Atlantic Ocean as mapped by the Global coral reef mapping project at geomorphological scale using LANDSAT satellite data (L7 and L8). The data set provides one zip file per country or region of interest. Global coral reef mapping project at geomorphological scale using LANDSAT satellite data (L7 and L8). Funded by National Aeronautics and Space Administration, NASA grants NAG5-10908 (University of South Florida, PIs: Franck Muller-Karger and Serge Andréfouët) and CARBON-0000-0257 (NASA, PI: Julie Robinson) from 2001 to 2007. Funded by IRD since 2003 (in kind, PI: Serge Andréfouët).

This dataset contains the common Map Unit attributes for each polygon within the gSSURGO database plus NRCS derived attributes from a data summary table called the National Valu Added Look Up (valu) Table #1. It is comprised of 57 pre-summarized or "ready to map" derived soil survey geographic database attributes including soil organic carbon, available water storage, crop productivity indices, crop root zone depths, available water storage within crop root zone depths, drought vulnerable soil landscapes, and potential wetland soil landscapes. Related metadata values for themes are included. These attribute data are pre-summarized to the map unit level using best practice generalization methods intended to meet the needs of most users. The generalization methods include map unit component weighted averages and percent of the map unit meeting a given criteria. These themes were prepared to better meet the mapping needs of users of soil survey information and can be used with both SSURGO and Gridded SSURGO (gSSURGO) datasets. Gridded SSURGO (gSSURGO) Database is derived from the official Soil Survey Geographic (SSURGO) Database. SSURGO is generally the most detailed level of soil geographic data developed by the National Cooperative Soil Survey (NCSS) in accordance with NCSS mapping standards. The tabular data represent the soil attributes, and are derived from properties and characteristics stored in the National Soil Information System (NASIS). The gSSURGO data were prepared by merging traditional SSURGO digital vector map and tabular data into State-wide extents, and adding a State-wide gridded map layer derived from the vector, plus a new value added look up (valu) table containing "ready to map" attributes. The gridded map layer is offered in an ArcGIS file geodatabase raster format. The raster and vector map data have a State-wide extent. The raster map data have a 10 meter cell size that approximates the vector polygons in an Albers Equal Area projection. Each cell (and polygon) is linked to a map unit identifier called the map unit key. A unique map unit key is used to link to raster cells and polygons to attribute tables, including the new value added look up (valu) table that contains additional derived data.VALU Table Content:The map unit average Soil Organic Carbon (SOC) values are given in units of g C per square meter for eleven standard layer or zone depths. The average thickness of soil map unit component horizons used in these layer/zone calcuations is also included. The standard layers include: 0-5cm, 5-20cm, 20-50cm, 50-100cm, 100-150cm, and 150-150+cm (maximum reported soil depth). The standard zones include: 0-5cm (also a standard layer), o-20cm, 0-30cm, 0-100cm, and 0-150+cm (full reported soil depth). Zero cm represents the soil surface.The map unit average Available Water Storage (AWS) values are given in units of millimeters for eleven standard layer or zone depths. The average thickness of soil map unit component horizons used in these layer/zone calcuations is also included. The standard layers include: 0-5cm, 5-20cm, 20-50cm, 50-100cm, 100-150cm, and 150-150+cm (maximum reported soil depth). The standard zones include: 0-5cm (also a standard layer), 0-20cm, 0-30cm, 0-100cm, and 0-150+cm (full reported soil depth). Zero cm represents the soil surface.The map unit average National Commodity Crop Productivity Index (NCCPI) values (low index values indicate low productivity and high index values indicate high productivity) are provided for major earthy components. NCCPI values are included for corn/soybeans, small grains, and cotton crops. Of these crops, the highest overall NCCPI value is also identified. Earthy components are those soil series or higher level taxa components that can support crop growth. Major components are those soil components where the majorcompflag = 'Yes' in the SSURGO component table. A map unit percent composition for earthy major components is provided. See Dobos, R. R., H. R. Sinclair, Jr, and M. P. Robotham. 2012. National Commodity Crop Productivity Index (NCCPI) User Guide, Version 2. USDA-NRCS. Available at: ftp://ftp-fc.sc.egov.usda.gov/NSSC/NCCPI/NCCPI_user_guide.pdfThe map unit average root zone depth values for commodity crops are given in centimeters for major earthy components. Criteria for root-limiting soil depth include: presence of hard bedrock, soft bedrock, a fragipan, a duripan, sulfuric material, a dense layer, a layer having a pH of less than 3.5, or a layer having an electrical conductivity of more than 12 within the component soil profile. If no root-restricting zone is identified, a depth of 150 cm is used to approximate the root zone depth (Dobos et al., 2012). The map unit average available water storage within the root zone depth for major earthy components value is given in millimeters.Drought vulnerable soil landscapes comprise those map units that have available water storage within the root zone for commodity crops that is less than or equal to 6 inches (152 mm) expressed as "1" for a drought vulnerable soil landscape map unit or "0" for a nondroughty soil landscape map unit or NULL for miscellaneous areas (includes water bodies).The potential wetland soil landscapes (PWSL version 1) information is given as the percentage of the map unit (all components) that meet the criteria for a potential wetland soil landscape. See table column (field) description for criteria details. If water was determined to account for 80 or greater percent of a map unit, a value of 999 was used to indicate a water body. This is not a perfect solution, but is helpful to identifying a general water body class for mapping.The map unit sum of the component percentage representative values is also provided as useful metadata. For all valu table columns, NULL values are presented where data are incomplete or not available. How NoData or NULL values and incomplete data were handled during VALU table SOC and AWS calculations:The gSSURGO calculations for SOC and AWS as reported in the VALU table use the following data checking and summarization rules. The guiding principle was to only use the official data in the SSURGO database, and not to make assumptions in case there were some data entry errors. However, there were a few exceptions to this principle if there was a good reason for a Null value in a critical variable, or to accommodate the data coding conventions used in some soil surveys.Horizon depths considerations:If the depth to the top of the surface horizon was missing, but otherwise the horizon depths were all okay, then the depth to the top of the surface horizon (hzdept_r) was set to zero.If the depth to the bottom of the last horizon was missing, and the horizon represented bedrock or had missing bulk density, the depth to the bottom was set to equal to the depth to the top of the same horizon (hzdepb_r = hzdept_r), effectively giving the horizon zero thickness (and thus zero SOC or AWS), but not blocking calculation of other horizons in the profile due to horizon depth errors.Other types of horizon depth errors were considered uncorrectable, and led to all horizon depths for the component being set to a NoData value, effectively eliminating the component from the analysis. The errors included gaps or overlaps in the horizon depths of the soil profile, other cases of missing data for horizon depths, including missing data for the bottom depth of the last horizon if the soil texture information did not indicate bedrock and a bulk density value was coded. The SOC or AWS values were effectively set to zero for components eliminated in this way, so the values at the map unit level could be an underestimate for some soils.Horizon rock fragment considerations:Part of the algorithm for calculating the SOC requires finding the volume of soil that is not rock. This requires three SSURGO variables that indicate rock fragments (fraggt10_r, frag3to10_r, and sieveno10_r). If the soil is not organic, and any of these are missing, then the ratio of the volume of soil fines to the total soil volume was set to “NoData†, and the SOC results were coded as “NoData†and effectively set to zero for the horizon. If the soil is organic, then it may be logical that no measurement of rock fragments was made, and default values for the “zero rock†situation was assumed for these variables (i.e., fraggt10_r = 0, frag3to10_r = 0, sieveno10_r = 100). Organic soils were identified by an “O†in the horizon designator or the texture code represented “Peat†, “Muck†or “Decomposed Plant Material†. If all three of the fragment variables were present, but indicated more than 100% rock, then 100% rock was assumed (zero volume of soil and thus zero for SOC). The rock fragment variables do not influence the AWS calculation because rock content is already accounted for in the available water capacity (awc_r) variable at the horizon level.Horizon to component summary:To summarize data from the horizon level to the component level, the evaluation proceeded downward from the surface. If a valid value for AWS could not be calculated for any horizon, then the result for that horizon and all deeper horizons was set to NoData. The same rule was separately applied to the SOC calculation, so it was possible to have results for SOC but not AWS, or vice versa.Component to mapunit summary:To summarize data from the component level to the map unit level, the component percentages must be valid. There are tests both of the individual component percentage (comppct_r) data, and also of the sum of the component percentages at the map unit level (mu_sum_comppct_r). For the gSSURGO VALU table, the following rules were applied for the individual components: 1) The comppct_r must be in the range from 0 to 100, inclusive. 2) Individual components with a comppct_r that was Null (nothing coded) were ignored. A zero comppct_r value excludes

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. We converted the photointerpreted data into a GIS-usable format employing three fundamental processes; (1) orthorectify, (2) digitize, and (3) database enhancement. All digital map automation was projected in Universal Transverse Mercator (UTM) projection, Zone 12, using North American Datum of 1983 (NAD83). To produce a polygon vector coverage for use in GIS, we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format using ArcInfo (Version 8.0.2, Environmental Systems Research Institute, Redlands, California). In ArcTools, we used the ArcScan utility to trace the polygon data and produce ArcInfo vector-based coverages. We digitally assigned map attribute codes (both map class codes and physiognomic modifier codes) to the polygons, and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the 78 individual coverages into a seamless map coverage of GNP and immediate environs. We synchronized polygons and attributes along the boundary between the GNP and WLNP map coverages. Although GNP and WLNP are two separate map coverages, they are seamless in the sense they edge tie perfectly in both polygon location and map attribute.

The second edition of the Antarctic Digital Database (ADD) coastline polygon dataset. A compilation of source data from eleven national mapping agencies at data scales no larger than 1:200,000/1:250:000. Polygon dataset was originally published on CD-ROM in 1998, in tiled Coverage format. Data has since been converted and merged to a single dataset and exported to shapefile and geopackage formats. Scale0 is the highest resolution that was produced. Each polygon has a surface attribute (CST00SRF) indicating the type of feature it represents, ie. ice shelf, ice tongue, land, ocean and rumple. For information on the source of polygon delineations, refer to coincident features in the polyline dataset, Scale0 vector polylines of the Antarctic coastline v2.0. ADD Version 2.0 contained many amendments to the original data. Most corrections were made in Quadrant 4, which covers the Antarctic Peninsula, parts of Ellsworth Land and Coats Land. A few features, such as Doake Ice Rumples, were inadvertently omitted from ADD Version 1.0, so were included in this version for the first time. Data for the Ronne and Filchner ice shelves were also upgraded. A new map of James Ross Island was incorporated, and the positions of ice fronts of the northern Larsen Ice Shelf, Wordie Ice Shelf and Wilkins Ice Shelf were also amended using the latest available information. Other minor changes were also made and documented in the ADD Manual: https://nora.nerc.ac.uk/id/eprint/536533/. The UK Consortium behind the ADD Version 1.0 passed the ongoing maintenance and revision of the ADD to British Antarctic Survey (BAS) for Version 2.0. For full details on the dataset, please refer to the ADD Manual v2.0: https://nora.nerc.ac.uk/id/eprint/536533/

This dataset is called the Gridded SSURGO (gSSURGO) Database and is derived from the Soil Survey Geographic (SSURGO) Database. SSURGO is generally the most detailed level of soil geographic data developed by the National Cooperative Soil Survey (NCSS) in accordance with NCSS mapping standards. The tabular data represent the soil attributes, and are derived from properties and characteristics stored in the National Soil Information System (NASIS). The gSSURGO data were prepared by merging traditional SSURGO digital vector map and tabular data into a Conterminous US-wide extent, and adding a Conterminous US-wide gridded map layer derived from the vector, plus a new value added look up (valu) table containing "ready to map" attributes. The gridded map layer is offered in an ArcGIS file geodatabase raster format.

The raster and vector map data have a Conterminous US-wide extent. The raster map data have a 10 meter cell size that approximates the vector polygons in an Albers Equal Area projection. Each cell (and polygon) is linked to a map unit identifier called the map unit key. A unique map unit key is used to link to raster cells and polygons to attribute tables, including the new value added look up (valu) table that contains additional derived data.

The value added look up (valu) table contains attribute data summarized to the map unit level using best practice generalization methods intended to meet the needs of most users. The generalization methods include map unit component weighted averages and percent of the map unit meeting a given criteria.

The Gridded SSURGO dataset was created for use in national, regional, and state-wide resource planning and analysis of soils data. The raster map layer data can be readily combined with other national, regional, and local raster layers, e.g., National Land Cover Database (NLCD), the National Agricultural Statistics Service (NASS) Crop Data Layer, or the National Elevation Dataset (NED).

Wall polygon features in Easton, Massachusetts. Compiled from 2017 vector mapping project conducted by WSP. The aerial photographic mission was carried out on April 12, 2017. The vector data was collected at scale of 1"= 40'.

The Gridded SSURGO dataset was created for use in national, regional, and statewide resource planning and analysis of soils data.The gSSURGO Database is derived from the official Soil Survey Geographic (SSURGO) Database. SSURGO generally has the most detailed level of soil geographic data developed by the National Cooperative Soil Survey (NCSS) in accordance with NCSS mapping standards. The tabular data represent the soil attributes and are derived from properties and characteristics stored in the National Soil Information System (NASIS). The gSSURGO data were prepared by merging the traditional vector-based SSURGO digital map data and tabular data into statewide extents, adding a statewide gridded map layer derived from the vector layer, and adding a new value-added look up table (valu) containing “ready to map” attributes. The gridded map layer is in an ArcGIS file geodatabase in raster format. The raster and vector map data have a statewide extent. The raster map data have a 10-meter cell size that approximates the vector polygons in an Albers Equal Area projection. Each cell (and polygon) is linked to a map unit identifier called the map unit key. A unique map unit key is used to link the raster cells and polygons to attribute tables.Other Documents to Reference:gSSURGO FactsheetgSSURGO User Guide ArcMap version 2.4Soil Data Development Toolbox User Guide v5 for ArcMapgSSURGO Mapping Detailed GuidegSSURGO Valu1 table column descriptions

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. We converted the photointerpreted data into a GIS-usable format employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM) projection, Zone 16, using North American Datum of 1983 (NAD83). To produce a polygon vector layer for use in ArcGIS, we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format using ArcGIS (Version 9.2, © 2006 Environmental Systems Research Institute, Redlands, California). In ArcGIS, we used the ArcScan extension to trace the raster data and produce ESRI shapefiles. We digitally assigned map attribute codes (both map class codes and physiognomic modifier codes) to the polygons, and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the individual layers into a seamless layer of INDU and immediate environs. At this stage, the map layer has only map attribute codes assigned to each polygon. To assign meaningful information to each polygon (e.g., map class names, physiognomic definitions, link to NVC association and alliance codes), we produced a feature class table along with other supportive tables and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature class layers produced from this project, including vegetation sample plots, accuracy assessment sites, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.

Land cover has been interpreted from Satellite images and field checked, other information has been digitized from topographic maps

 Members informations:
 Attached Vector(s):
  MemberID: 1
 Vector Name: Land use
 Source Map Name: SPOT Pan
 Source Map Scale: 50000
 Source Map Date: 1989/90
 Projection: Polyconic on Modified Everest Ellipsoid
 Feature_type: polygon
 Vector 
 Land use maps, interpreted from SPOT panchromatic imagery and field
 checked (18 classes)

 Members informations:
 Attached Vector(s):
  MemberID: 2
 Vector Name: Administrative boundaries
 Source Map Name: topo sheets
 Source Map Scale: 50000
 Source Map Date: ?
 Feature_type: polygon
 Vector 
 Dzongkhags (Districts) and Gewogs

 Members informations:
 Attached Vector(s):
  MemberID: 3
 Vector Name: Roads
 Source Map Name: topo sheets
 Source Map Scale: 50000
 Source Map Date: ?
 Feature_type: lines
 Vector 
 Road network

 Attached Report(s)
 Member ID: 4
 Report Name: Atlas of Bhutan
 Report Authors: Land use planning section
 Report Publisher: Ministry of Agriculture, Thimpu
 Report Date: 1997-06-01
 Report 
 Land cover (1:250000) and area statistics of 20 Dzongkhags

This is the land parcels (polygon) dataset for the UKCEH Land Cover Map of 2019 (LCM2019) representing Northern Ireland. It describes Northern Ireland's land cover in 2019 using UKCEH Land Cover Classes, which are based on UK Biodiversity Action Plan broad habitats. This dataset was derived from the corresponding LCM2019 20m classified pixels dataset. All further LCM2019 datasets for Northern Ireland are derived from this land parcel product. A range of land parcel attributes are provided. These include the dominant UKCEH Land Cover Class given as an integer value and a range of per-parcel pixel statistics to help assess classification confidence and accuracy; for a full explanation please refer to the dataset documentation. LCM2019 represents a suite of geospatial land cover datasets (raster and polygon) describing the UK land surface in 2019. These were produced at the UK Centre for Ecology & Hydrology by classifying satellite images from 2019. LCM2019 was simultaneously released with LCM2017 and LCM2018. These are the latest in a series of UKCEH land cover maps, which began with the 1990 Land Cover Map of Great Britain (now usually referred to as LCM1990) followed by UK-wide land cover maps LCM2000, LCM2007 and LCM2015. This work was supported by the Natural Environment Research Council award number NE/R016429/1 as part of the UK-SCAPE programme delivering National Capability.

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 mapping component of the NABR project used a combination of methods to interpret and delineate vegetation polygons. A trained interpreter visually examined the 9 x 9-inch photographs in stereo to identify vegetation polygons. Polygons were drawn on Mylar overlays that were later scanned, or digitally on a computer screen. Digitizing was performed using vector editing in ArcGIS. Each vegetation and land use polygon so produced was given map class and other descriptive attributes. The Monument and an area of environs surrounding it were interpreted and mapped to the same level of detail. Each polygon was assigned a map class number, alpha code and name, Anderson land use class, and vegetation density, pattern, and height attributes. In order to improve the utility of the map and related data, the spatial database was moved into a geodatabase format. This format allows text and image information to be incorporated and linked to spatial coordinates. Twenty map classes were developed to describe the NABR vegetation mapping project area. Of these, 17 are vegetation map classes and 3 are non-vegetated land-use map classes. Of the 17 vegetation map classes, one is represented by points only, one is a single polygon, and three represent single NVC plant associations. The remaining 12 vegetation map classes contain multiple plant associations.

The mission of the Humanitarian Information Unit (HIU) is to serve as a U.S. Government interagency center to identify, collect, analyze, and disseminate all-source information critical to U.S. Government decision-makers and partners in preparation for and response to humanitarian emergencies worldwide, and to promote innovative technologies and best practices for humanitarian information management.

Coastline for Antarctica created from various mapping and remote sensing sources, consisting of the following coast types: ice coastline, rock coastline, grounding line, ice shelf and front, ice rumple, and rock against ice shelf. Covering all land and ice shelves south of 60°S. Suitable for topographic mapping and analysis. High resolution versions of ADD data are suitable for scales larger than 1:1,000,000. The largest suitable scale is changeable and dependent on the region.

Major changes in v7.5 include updates to ice shelf fronts in the following regions: Seal Nunataks and Scar Inlet region, the Ronne-Filchner Ice Shelf, between the Brunt Ice Shelf and Riiser-Larsen Peninsula, the Shackleton and Conger ice shelves, and Crosson, Thwaites and Pine Island. Small areas of grounding line and ice coastlines were also updated in some of these regions as needed.

Data compiled, managed and distributed by the Mapping and Geographic Information Centre and the UK Polar Data Centre, British Antarctic Survey on behalf of the Scientific Committee on Antarctic Research.

Further information and useful links

Map projection: WGS84 Antarctic Polar Stereographic, EPSG 3031. Note: by default, opening this layer in the Map Viewer will display the data in Web Mercator. To display this layer in its native projection use an Antarctic basemap.

The currency of this dataset is May 2022 and will be reviewed every 6 months. This feature layer will always reflect the most recent version.

For more information on, and access to other Antarctic Digital Database (ADD) datasets, refer to the SCAR ADD data catalogue.

A related medium resolution dataset is also published via Living Atlas, as well medium and high resolution polygon datasets.

For background information on the ADD project, please see the British Antarctic Survey ADD project page.

Lineage

Dataset compiled from a variety of Antarctic map and satellite image sources. The dataset was created using ArcGIS and QGIS GIS software programmes and has been checked for basic topography and geometry checks, but does not contain strict topology. Quality varies across the dataset and certain areas where high resolution source data were available are suitable for large scale maps whereas other areas are only suitable for smaller scales. Each line has attributes detailing the source which can give the user further indications of its suitability for specific uses. Attributes also give information including 'surface' (e.g. grounding line, ice coastline, ice shelf front) and revision date. Compiled from sources ranging in time from 1990s-2022 - individual lines contain exact source dates.

description: This dataset is called the Gridded SSURGO (gSSURGO) Database and is derived from the Soil Survey Geographic (SSURGO) Database. SSURGO is generally the most detailed level of soil geographic data developed by the National Cooperative Soil Survey (NCSS) in accordance with NCSS mapping standards. The tabular data represent the soil attributes, and are derived from properties and characteristics stored in the National Soil Information System (NASIS). The gSSURGO data were prepared by merging traditional SSURGO digital vector map and tabular data into a Conterminous US-wide extent, and adding a Conterminous US-wide gridded map layer derived from the vector, plus a new value added look up (valu) table containing "ready to map" attributes. The gridded map layer is offered in an ArcGIS file geodatabase raster format. The raster and vector map data have a Conterminous US-wide extent. The raster map data have a 30 meter cell size. Each cell (and polygon) is linked to a map unit identifier called the map unit key. A unique map unit key is used to link to raster cells and polygons to attribute tables, including the new value added look up (valu) table that contains additional derived data. The value added look up (valu) table contains attribute data summarized to the map unit level using best practice generalization methods intended to meet the needs of most users. The generalization methods include map unit component weighted averages and percent of the map unit meeting a given criteria. The Gridded SSURGO dataset was created for use in national, regional, and state-wide resource planning and analysis of soils data. The raster map layer data can be readily combined with other national, regional, and local raster layers, e.g., National Land Cover Database (NLCD), the National Agricultural Statistics Service (NASS) Crop Data Layer, or the National Elevation Dataset (NED).; abstract: This dataset is called the Gridded SSURGO (gSSURGO) Database and is derived from the Soil Survey Geographic (SSURGO) Database. SSURGO is generally the most detailed level of soil geographic data developed by the National Cooperative Soil Survey (NCSS) in accordance with NCSS mapping standards. The tabular data represent the soil attributes, and are derived from properties and characteristics stored in the National Soil Information System (NASIS). The gSSURGO data were prepared by merging traditional SSURGO digital vector map and tabular data into a Conterminous US-wide extent, and adding a Conterminous US-wide gridded map layer derived from the vector, plus a new value added look up (valu) table containing "ready to map" attributes. The gridded map layer is offered in an ArcGIS file geodatabase raster format. The raster and vector map data have a Conterminous US-wide extent. The raster map data have a 30 meter cell size. Each cell (and polygon) is linked to a map unit identifier called the map unit key. A unique map unit key is used to link to raster cells and polygons to attribute tables, including the new value added look up (valu) table that contains additional derived data. The value added look up (valu) table contains attribute data summarized to the map unit level using best practice generalization methods intended to meet the needs of most users. The generalization methods include map unit component weighted averages and percent of the map unit meeting a given criteria. The Gridded SSURGO dataset was created for use in national, regional, and state-wide resource planning and analysis of soils data. The raster map layer data can be readily combined with other national, regional, and local raster layers, e.g., National Land Cover Database (NLCD), the National Agricultural Statistics Service (NASS) Crop Data Layer, or the National Elevation Dataset (NED).