24 datasets found
  1. Large Scale International Boundaries

    • catalog.data.gov
    • geodata.state.gov
    • +1more
    Updated Aug 30, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Department of State (Point of Contact) (2025). Large Scale International Boundaries [Dataset]. https://catalog.data.gov/dataset/large-scale-international-boundaries
    Explore at:
    Dataset updated
    Aug 30, 2025
    Dataset provided by
    United States Department of Statehttp://state.gov/
    Description

    Overview The Office of the Geographer and Global Issues at the U.S. Department of State produces the Large Scale International Boundaries (LSIB) dataset. The current edition is version 11.4 (published 24 February 2025). The 11.4 release contains updated boundary lines and data refinements designed to extend the functionality of the dataset. These data and generalized derivatives are the only international boundary lines approved for U.S. Government use. The contents of this dataset reflect U.S. Government policy on international boundary alignment, political recognition, and dispute status. They do not necessarily reflect de facto limits of control. National Geospatial Data Asset This dataset is a National Geospatial Data Asset (NGDAID 194) managed by the Department of State. It is a part of the International Boundaries Theme created by the Federal Geographic Data Committee. Dataset Source Details Sources for these data include treaties, relevant maps, and data from boundary commissions, as well as national mapping agencies. Where available and applicable, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery process includes analysis of satellite imagery and elevation data. Due to the limitations of source materials and processing techniques, most lines are within 100 meters of their true position on the ground. Cartographic Visualization The LSIB is a geospatial dataset that, when used for cartographic purposes, requires additional styling. The LSIB download package contains example style files for commonly used software applications. The attribute table also contains embedded information to guide the cartographic representation. Additional discussion of these considerations can be found in the Use of Core Attributes in Cartographic Visualization section below. Additional cartographic information pertaining to the depiction and description of international boundaries or areas of special sovereignty can be found in Guidance Bulletins published by the Office of the Geographer and Global Issues: https://data.geodata.state.gov/guidance/index.html Contact Direct inquiries to internationalboundaries@state.gov. Direct download: https://data.geodata.state.gov/LSIB.zip Attribute Structure The dataset uses the following attributes divided into two categories: ATTRIBUTE NAME | ATTRIBUTE STATUS CC1 | Core CC1_GENC3 | Extension CC1_WPID | Extension COUNTRY1 | Core CC2 | Core CC2_GENC3 | Extension CC2_WPID | Extension COUNTRY2 | Core RANK | Core LABEL | Core STATUS | Core NOTES | Core LSIB_ID | Extension ANTECIDS | Extension PREVIDS | Extension PARENTID | Extension PARENTSEG | Extension These attributes have external data sources that update separately from the LSIB: ATTRIBUTE NAME | ATTRIBUTE STATUS CC1 | GENC CC1_GENC3 | GENC CC1_WPID | World Polygons COUNTRY1 | DoS Lists CC2 | GENC CC2_GENC3 | GENC CC2_WPID | World Polygons COUNTRY2 | DoS Lists LSIB_ID | BASE ANTECIDS | BASE PREVIDS | BASE PARENTID | BASE PARENTSEG | BASE The core attributes listed above describe the boundary lines contained within the LSIB dataset. Removal of core attributes from the dataset will change the meaning of the lines. An attribute status of “Extension” represents a field containing data interoperability information. Other attributes not listed above include “FID”, “Shape_length” and “Shape.” These are components of the shapefile format and do not form an intrinsic part of the LSIB. Core Attributes The eight core attributes listed above contain unique information which, when combined with the line geometry, comprise the LSIB dataset. These Core Attributes are further divided into Country Code and Name Fields and Descriptive Fields. County Code and Country Name Fields “CC1” and “CC2” fields are machine readable fields that contain political entity codes. These are two-character codes derived from the Geopolitical Entities, Names, and Codes Standard (GENC), Edition 3 Update 18. “CC1_GENC3” and “CC2_GENC3” fields contain the corresponding three-character GENC codes and are extension attributes discussed below. The codes “Q2” or “QX2” denote a line in the LSIB representing a boundary associated with areas not contained within the GENC standard. The “COUNTRY1” and “COUNTRY2” fields contain the names of corresponding political entities. These fields contain names approved by the U.S. Board on Geographic Names (BGN) as incorporated in the ‘"Independent States in the World" and "Dependencies and Areas of Special Sovereignty" lists maintained by the Department of State. To ensure maximum compatibility, names are presented without diacritics and certain names are rendered using common cartographic abbreviations. Names for lines associated with the code "Q2" are descriptive and not necessarily BGN-approved. Names rendered in all CAPITAL LETTERS denote independent states. Names rendered in normal text represent dependencies, areas of special sovereignty, or are otherwise presented for the convenience of the user. Descriptive Fields The following text fields are a part of the core attributes of the LSIB dataset and do not update from external sources. They provide additional information about each of the lines and are as follows: ATTRIBUTE NAME | CONTAINS NULLS RANK | No STATUS | No LABEL | Yes NOTES | Yes Neither the "RANK" nor "STATUS" fields contain null values; the "LABEL" and "NOTES" fields do. The "RANK" field is a numeric expression of the "STATUS" field. Combined with the line geometry, these fields encode the views of the United States Government on the political status of the boundary line. ATTRIBUTE NAME | | VALUE | RANK | 1 | 2 | 3 STATUS | International Boundary | Other Line of International Separation | Special Line A value of “1” in the “RANK” field corresponds to an "International Boundary" value in the “STATUS” field. Values of ”2” and “3” correspond to “Other Line of International Separation” and “Special Line,” respectively. The “LABEL” field contains required text to describe the line segment on all finished cartographic products, including but not limited to print and interactive maps. The “NOTES” field contains an explanation of special circumstances modifying the lines. This information can pertain to the origins of the boundary lines, limitations regarding the purpose of the lines, or the original source of the line. Use of Core Attributes in Cartographic Visualization Several of the Core Attributes provide information required for the proper cartographic representation of the LSIB dataset. The cartographic usage of the LSIB requires a visual differentiation between the three categories of boundary lines. Specifically, this differentiation must be between: International Boundaries (Rank 1); Other Lines of International Separation (Rank 2); and Special Lines (Rank 3). Rank 1 lines must be the most visually prominent. Rank 2 lines must be less visually prominent than Rank 1 lines. Rank 3 lines must be shown in a manner visually subordinate to Ranks 1 and 2. Where scale permits, Rank 2 and 3 lines must be labeled in accordance with the “Label” field. Data marked with a Rank 2 or 3 designation does not necessarily correspond to a disputed boundary. Please consult the style files in the download package for examples of this depiction. The requirement to incorporate the contents of the "LABEL" field on cartographic products is scale dependent. If a label is legible at the scale of a given static product, a proper use of this dataset would encourage the application of that label. Using the contents of the "COUNTRY1" and "COUNTRY2" fields in the generation of a line segment label is not required. The "STATUS" field contains the preferred description for the three LSIB line types when they are incorporated into a map legend but is otherwise not to be used for labeling. Use of the “CC1,” “CC1_GENC3,” “CC2,” “CC2_GENC3,” “RANK,” or “NOTES” fields for cartographic labeling purposes is prohibited. Extension Attributes Certain elements of the attributes within the LSIB dataset extend data functionality to make the data more interoperable or to provide clearer linkages to other datasets. The fields “CC1_GENC3” and “CC2_GENC” contain the corresponding three-character GENC code to the “CC1” and “CC2” attributes. The code “QX2” is the three-character counterpart of the code “Q2,” which denotes a line in the LSIB representing a boundary associated with a geographic area not contained within the GENC standard. To allow for linkage between individual lines in the LSIB and World Polygons dataset, the “CC1_WPID” and “CC2_WPID” fields contain a Universally Unique Identifier (UUID), version 4, which provides a stable description of each geographic entity in a boundary pair relationship. Each UUID corresponds to a geographic entity listed in the World Polygons dataset. These fields allow for linkage between individual lines in the LSIB and the overall World Polygons dataset. Five additional fields in the LSIB expand on the UUID concept and either describe features that have changed across space and time or indicate relationships between previous versions of the feature. The “LSIB_ID” attribute is a UUID value that defines a specific instance of a feature. Any change to the feature in a lineset requires a new “LSIB_ID.” The “ANTECIDS,” or antecedent ID, is a UUID that references line geometries from which a given line is descended in time. It is used when there is a feature that is entirely new, not when there is a new version of a previous feature. This is generally used to reference countries that have dissolved. The “PREVIDS,” or Previous ID, is a UUID field that contains old versions of a line. This is an additive field, that houses all Previous IDs. A new version of a feature is defined by any change to the

  2. Z

    Data from: 3DHD CityScenes: High-Definition Maps in High-Density Point...

    • data.niaid.nih.gov
    • zenodo.org
    • +1more
    Updated Jul 16, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Plachetka, Christopher; Sertolli, Benjamin; Fricke, Jenny; Klingner, Marvin; Fingscheidt, Tim (2024). 3DHD CityScenes: High-Definition Maps in High-Density Point Clouds [Dataset]. https://data.niaid.nih.gov/resources?id=zenodo_7085089
    Explore at:
    Dataset updated
    Jul 16, 2024
    Dataset provided by
    TU Braunschweig
    Volkswagen AG
    Authors
    Plachetka, Christopher; Sertolli, Benjamin; Fricke, Jenny; Klingner, Marvin; Fingscheidt, Tim
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    Overview

    3DHD CityScenes is the most comprehensive, large-scale high-definition (HD) map dataset to date, annotated in the three spatial dimensions of globally referenced, high-density LiDAR point clouds collected in urban domains. Our HD map covers 127 km of road sections of the inner city of Hamburg, Germany including 467 km of individual lanes. In total, our map comprises 266,762 individual items.

    Our corresponding paper (published at ITSC 2022) is available here. Further, we have applied 3DHD CityScenes to map deviation detection here.

    Moreover, we release code to facilitate the application of our dataset and the reproducibility of our research. Specifically, our 3DHD_DevKit comprises:

    Python tools to read, generate, and visualize the dataset,

    3DHDNet deep learning pipeline (training, inference, evaluation) for map deviation detection and 3D object detection.

    The DevKit is available here:

    https://github.com/volkswagen/3DHD_devkit.

    The dataset and DevKit have been created by Christopher Plachetka as project lead during his PhD period at Volkswagen Group, Germany.

    When using our dataset, you are welcome to cite:

    @INPROCEEDINGS{9921866, author={Plachetka, Christopher and Sertolli, Benjamin and Fricke, Jenny and Klingner, Marvin and Fingscheidt, Tim}, booktitle={2022 IEEE 25th International Conference on Intelligent Transportation Systems (ITSC)}, title={3DHD CityScenes: High-Definition Maps in High-Density Point Clouds}, year={2022}, pages={627-634}}

    Acknowledgements

    We thank the following interns for their exceptional contributions to our work.

    Benjamin Sertolli: Major contributions to our DevKit during his master thesis

    Niels Maier: Measurement campaign for data collection and data preparation

    The European large-scale project Hi-Drive (www.Hi-Drive.eu) supports the publication of 3DHD CityScenes and encourages the general publication of information and databases facilitating the development of automated driving technologies.

    The Dataset

    After downloading, the 3DHD_CityScenes folder provides five subdirectories, which are explained briefly in the following.

    1. Dataset

    This directory contains the training, validation, and test set definition (train.json, val.json, test.json) used in our publications. Respective files contain samples that define a geolocation and the orientation of the ego vehicle in global coordinates on the map.

    During dataset generation (done by our DevKit), samples are used to take crops from the larger point cloud. Also, map elements in reach of a sample are collected. Both modalities can then be used, e.g., as input to a neural network such as our 3DHDNet.

    To read any JSON-encoded data provided by 3DHD CityScenes in Python, you can use the following code snipped as an example.

    import json

    json_path = r"E:\3DHD_CityScenes\Dataset\train.json" with open(json_path) as jf: data = json.load(jf) print(data)

    1. HD_Map

    Map items are stored as lists of items in JSON format. In particular, we provide:

    traffic signs,

    traffic lights,

    pole-like objects,

    construction site locations,

    construction site obstacles (point-like such as cones, and line-like such as fences),

    line-shaped markings (solid, dashed, etc.),

    polygon-shaped markings (arrows, stop lines, symbols, etc.),

    lanes (ordinary and temporary),

    relations between elements (only for construction sites, e.g., sign to lane association).

    1. HD_Map_MetaData

    Our high-density point cloud used as basis for annotating the HD map is split in 648 tiles. This directory contains the geolocation for each tile as polygon on the map. You can view the respective tile definition using QGIS. Alternatively, we also provide respective polygons as lists of UTM coordinates in JSON.

    Files with the ending .dbf, .prj, .qpj, .shp, and .shx belong to the tile definition as “shape file” (commonly used in geodesy) that can be viewed using QGIS. The JSON file contains the same information provided in a different format used in our Python API.

    1. HD_PointCloud_Tiles

    The high-density point cloud tiles are provided in global UTM32N coordinates and are encoded in a proprietary binary format. The first 4 bytes (integer) encode the number of points contained in that file. Subsequently, all point cloud values are provided as arrays. First all x-values, then all y-values, and so on. Specifically, the arrays are encoded as follows.

    x-coordinates: 4 byte integer

    y-coordinates: 4 byte integer

    z-coordinates: 4 byte integer

    intensity of reflected beams: 2 byte unsigned integer

    ground classification flag: 1 byte unsigned integer

    After reading, respective values have to be unnormalized. As an example, you can use the following code snipped to read the point cloud data. For visualization, you can use the pptk package, for instance.

    import numpy as np import pptk

    file_path = r"E:\3DHD_CityScenes\HD_PointCloud_Tiles\HH_001.bin" pc_dict = {} key_list = ['x', 'y', 'z', 'intensity', 'is_ground'] type_list = ['

  3. Data from: Watershed Boundary Dataset (WBD)

    • agdatacommons.nal.usda.gov
    bin
    Updated Nov 21, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Subcommittee on Spatial Water Data (2025). Watershed Boundary Dataset (WBD) [Dataset]. https://agdatacommons.nal.usda.gov/articles/dataset/Watershed_Boundary_Dataset_WBD_/24661371
    Explore at:
    binAvailable download formats
    Dataset updated
    Nov 21, 2025
    Dataset provided by
    United States Department of Agriculturehttp://usda.gov/
    Natural Resources Conservation Servicehttp://www.nrcs.usda.gov/
    United States Geological Surveyhttp://www.usgs.gov/
    Authors
    Subcommittee on Spatial Water Data
    License

    U.S. Government Workshttps://www.usa.gov/government-works
    License information was derived automatically

    Description

    The Watershed Boundary Dataset (WBD) from The National Map (TNM) defines the perimeter of drainage areas formed by the terrain and other landscape characteristics. The drainage areas are nested within each other so that a large drainage area, such as the Upper Mississippi River, is composed of multiple smaller drainage areas, such as the Wisconsin River. Each of these smaller areas can further be subdivided into smaller and smaller drainage areas. The WBD uses six different levels in this hierarchy, with the smallest averaging about 30,000 acres. The WBD is made up of polygons nested into six levels of data respectively defined by Regions, Subregions, Basins, Subbasins, Watersheds, and Subwatersheds. For additional information on the WBD, go to https://nhd.usgs.gov/wbd.html. The USGS National Hydrography Dataset (NHD) service is a companion dataset to the WBD. The NHD is a comprehensive set of digital spatial data that encodes information about naturally occurring and constructed bodies of surface water (lakes, ponds, and reservoirs), paths through which water flows (canals, ditches, streams, and rivers), and related entities such as point features (springs, wells, stream gages, and dams). The information encoded about these features includes classification and other characteristics, delineation, geographic name, position and related measures, a "reach code" through which other information can be related to the NHD, and the direction of water flow. The network of reach codes delineating water and transported material flow allows users to trace movement in upstream and downstream directions. In addition to this geographic information, the dataset contains metadata that supports the exchange of future updates and improvements to the data. The NHD is available nationwide in two seamless datasets, one based on 1:24,000-scale maps and referred to as high resolution NHD, and the other based on 1:100,000-scale maps and referred to as medium resolution NHD. Additional selected areas in the United States are available based on larger scales, such as 1:5,000-scale or greater, and referred to as local resolution NHD. For more information on the NHD, go to https://nhd.usgs.gov/index.html. Hydrography data from The National Map supports many applications, such as making maps, geocoding observations, flow modeling, data maintenance, and stewardship. Hydrography data is commonly combined with other data themes, such as boundaries, elevation, structures, and transportation, to produce general reference base maps. The National Map viewer allows free downloads of public domain WBD and NHD data in either Esri File or Personal Geodatabase, or Shapefile formats. The Watershed Boundary Dataset is being developed under the leadership of the Subcommittee on Spatial Water Data, which is part of the Advisory Committee on Water Information (ACWI) and the Federal Geographic Data Committee (FGDC). The USDA Natural Resources Conservation Service (NRCS), along with many other federal agencies and national associations, have representatives on the Subcommittee on Spatial Water Data. As watershed boundary geographic information systems (GIS) coverages are completed, statewide and national data layers will be made available via the Geospatial Data Gateway to everyone, including federal, state, local government agencies, researchers, private companies, utilities, environmental groups, and concerned citizens. The database will assist in planning and describing water use and related land use activities. Resources in this dataset:Resource Title: Watershed Boundary Dataset (WBD). File Name: Web Page, url: https://www.nrcs.usda.gov/wps/portal/nrcs/detail/national/water/watersheds/dataset/?cid=nrcs143_021630 Web site for the Watershed Boundary Dataset (WBD), including links to:

    Review Data Availability (Status Maps) Obtain Data by State, County, or Other Area Obtain Seamless National Data offsite link image
    Geospatial Data Tools National Technical and State Coordinators Information about WBD dataset

  4. d

    Street Network Database SND

    • catalog.data.gov
    • data.seattle.gov
    • +2more
    Updated Oct 4, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Seattle ArcGIS Online (2025). Street Network Database SND [Dataset]. https://catalog.data.gov/dataset/street-network-database-snd-1712b
    Explore at:
    Dataset updated
    Oct 4, 2025
    Dataset provided by
    City of Seattle ArcGIS Online
    Description

    The pathway representation consists of segments and intersection elements. A segment is a linear graphic element that represents a continuous physical travel path terminated by path end (dead end) or physical intersection with other travel paths. Segments have one street name, one address range and one set of segment characteristics. A segment may have none or multiple alias street names. Segment types included are Freeways, Highways, Streets, Alleys (named only), Railroads, Walkways, and Bike lanes. SNDSEG_PV is a linear feature class representing the SND Segment Feature, with attributes for Street name, Address Range, Alias Street name and segment Characteristics objects. Part of the Address Range and all of Street name objects are logically shared with the Discrete Address Point-Master Address File layer. Appropriate uses include: Cartography - Used to depict the City's transportation network location and connections, typically on smaller scaled maps or images where a single line representation is appropriate. Used to depict specific classifications of roadway use, also typically at smaller scales. Used to label transportation network feature names typically on larger scaled maps. Used to label address ranges with associated transportation network features typically on larger scaled maps. Geocode reference - Used as a source for derived reference data for address validation and theoretical address location Address Range data repository - This data store is the City's address range repository defining address ranges in association with transportation network features. Polygon boundary reference - Used to define various area boundaries is other feature classes where coincident with the transportation network. Does not contain polygon features. Address based extracts - Used to create flat-file extracts typically indexed by address with reference to business data typically associated with transportation network features. Thematic linear location reference - By providing unique, stable identifiers for each linear feature, thematic data is associated to specific transportation network features via these identifiers. Thematic intersection location reference - By providing unique, stable identifiers for each intersection feature, thematic data is associated to specific transportation network features via these identifiers. Network route tracing - Used as source for derived reference data used to determine point to point travel paths or determine optimal stop allocation along a travel path. Topological connections with segments - Used to provide a specific definition of location for each transportation network feature. Also provides a specific definition of connection between each transportation network feature. (defines where the streets are and the relationship between them ie. 4th Ave is west of 5th Ave and 4th Ave does intersect with Cherry St) Event location reference - Used as source for derived reference data used to locate event and linear referencing.Data source is TRANSPO.SNDSEG_PV. Updated weekly.

  5. g

    USGS Hydrography (NHD) Overlay Map Service from The National Map - National...

    • data.globalchange.gov
    • datadiscoverystudio.org
    Updated Dec 31, 2009
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2009). USGS Hydrography (NHD) Overlay Map Service from The National Map - National Geospatial Data Asset (NGDA) National Hydrography Dataset (NHD) [Dataset]. https://data.globalchange.gov/dataset/usgs-hydrography-nhd-overlay-map-service-from-the-national-map-national-geospatial-data-asset-
    Explore at:
    Dataset updated
    Dec 31, 2009
    Description

    The USGS National Hydrography Dataset (NHD) service from The National Map (TNM) is a comprehensive set of digital spatial data that encodes information about naturally occurring and constructed bodies of surface water (lakes, ponds, and reservoirs), paths through which water flows (canals, ditches, streams, and rivers), and related entities such as point features (springs, wells, stream gages, and dams). The information encoded about these features includes classification and other characteristics, delineation, geographic name, position and related measures, a "reach code" through which other information can be related to the NHD, and the direction of water flow. The network of reach codes delineating water and transported material flow allows users to trace movement in upstream and downstream directions. In addition to this geographic information, the dataset contains metadata that supports the exchange of future updates and improvements to the data. The NHD is available nationwide in two seamless datasets, one based on 1:24,000-scale maps and referred to as high resolution NHD, and the other based on 1:100,000-scale maps and referred to as medium resolution NHD. Additional selected areas in the United States are available based on larger scales, such as 1:5,000-scale or greater, and referred to as local resolution NHD. The NHD from The National Map supports many applications, such as making maps, geocoding observations, flow modeling, data maintenance, and stewardship. For additional information on the NHD, go to http://nhd.usgs.gov/index.html. The Watershed Boundary Dataset (WBD) is a companion dataset to the NHD. It defines the perimeter of drainage areas formed by the terrain and other landscape characteristics. The drainage areas are nested within each other so that a large drainage area, such as the Upper Mississippi River, will be composed of multiple smaller drainage areas, such as the Wisconsin River. Each of these smaller areas can further be subdivided into smaller and smaller drainage areas. The WBD uses six different levels in this hierarchy, with the smallest averaging about 30,000 acres. The WBD is made up of polygons nested into six levels of data respectively defined by Regions, Subregions, Basins, Subbasins, Watersheds, and Subwatersheds. For additional information on the WBD, go to http://nhd.usgs.gov/wbd.html. The National Map hydrography data is commonly combined with other data themes, such as boundaries, elevation, structures, and transportation, to produce general reference base maps. The National Map viewer allows free downloads of public domain NHD and WBD data in either Esri File or Personal Geodatabase, or Shapefile formats.

  6. p

    Data from: World Terrestrial Ecosystems

    • pacificgeoportal.com
    • cacgeoportal.com
    • +4more
    Updated Apr 2, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Esri (2020). World Terrestrial Ecosystems [Dataset]. https://www.pacificgeoportal.com/datasets/926a206393ec40a590d8caf29ae9a93e
    Explore at:
    Dataset updated
    Apr 2, 2020
    Dataset authored and provided by
    Esri
    Area covered
    World,
    Description

    The World Terrestrial Ecosystems map classifies the world into areas of similar climate, landform, and land cover, which form the basic components of any terrestrial ecosystem structure. This map is important because it uses objectively derived and globally consistent data to characterize the ecosystems at a much finer spatial resolution (250-m) than existing ecoregionalizations, and a much finer thematic resolution (431 classes) than existing global land cover products. This item was updated on Apr 14, 2023 to distinguish between Boreal and Polar climate regions in the terrestrial ecosystems. Cell Size: 250-meter Source Type: ThematicPixel Type: 16 Bit UnsignedData Projection: GCS WGS84Extent: GlobalSource: USGS, The Nature Conservancy, EsriUpdate Cycle: NoneAnalysis: Optimized for analysis What can you do with this layer?This map allows you to query the land surface pixels and returns the values of all the input parameters (landform type, landcover/vegetation type, climate region) and the name of the terrestrial ecosystem at that location. This layer can be used in analysis at global and local regions. However, for large scale spatial analysis, we have also provided an ArcGIS Pro Package that contains the original raster data with multiple table attributes. For simple mapping applications, there is also a raster tile layer. This layer can be combined with the World Protected Areas Database to assess the types of ecosystems that are protected, and progress towards meeting conservation goals. The WDPA layer updates monthly from the United Nations Environment Programme. Optimized for analysis means this layer does not have size constraints for analysis and it is recommended for multisource analysis with other layers optimized for analysis. See the Living Atlas Imagery Layers Optimized for Analysis Group for a complete list of imagery layers optimized for analysis. Developing the World Terrestrial EcosystemsWorld Terrestrial Ecosystems map was produced by adopting and modifying the Intergovernmental Panel on Climate Change (IPCC) approach on the definition of Terrestrial Ecosystems and development of standardized global climate regions using the values of environmental moisture regime and temperature regime. We then combined the values of Global Climate Regions, Landforms and matrix-forming vegetation assemblage or land use, using the ArcGIS Combine tool (Spatial Analyst) to produce World Ecosystems Dataset. This combination resulted of 431 World Ecosystems classes. Each combination was assigned a color using an algorithm that blended traditional color schemes for each of the three components. Every pixel in this map is symbolized by a combination of values for each of these fields. The work from this collaboration is documented in the publication:Sayre et al. 2020. An assessment of the representation of ecosystems in global protected areas using new maps of World Climate Regions and World Ecosystems - Global Ecology and Conservation More information about World Terrestrial Ecosystems can be found in this Story Map.

  7. c

    Comprehensive Planning Areas

    • opendata.cityofboise.org
    • hub.arcgis.com
    • +1more
    Updated Oct 17, 2018
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Boise, Idaho (2018). Comprehensive Planning Areas [Dataset]. https://opendata.cityofboise.org/maps/comprehensive-planning-areas
    Explore at:
    Dataset updated
    Oct 17, 2018
    Dataset authored and provided by
    City of Boise, Idaho
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Area covered
    Description

    This is a polygon data set depicting the current comprehensive planning areas for Boise City. A comprehensive planning area is defined in Chapter 4-1, page 171, of Blueprint Boise, the current Boise City Comprehensive Plan as, "On the largest scale, the entire area (area of impact) for which the City has authority to prepare comprehensive plans. On a smaller scale, planning area refers to the various sub-areas (i.e. West Bench, Central Bench, Southwest, etc,) which the City has defined as making up the larger planning area. These sub-areas are defined by physical barriers and/or the character of existing developments within them, and may each have specific planning objectives and policies articulated in the Comprehensive Plan." Each polygon in this data set is a specific smaller scale (sub-area) planning area. Collectively, the polygons represent the geography for the Boise City large scale comprehensive planning area.This data set is a critical component of the official Land Use Map within the Boise City Comprehensive Plan. It is used to identify specific areas within Boise City and the Boise Area of Impact to which specific land use designations and policies are applied. The data set is used to assist Boise City staff to identify specific planning areas and manage the growth of those areas to be consistent with the policies and intentions set out in the Boise City Comprehensive Plan.The dataset is generally coincident with the Boise Area of Impact; and is updated through City Council approval when the Boise Area of Impact changes. The data is current to the date the data set was published.For more information, please visit City of Boise Planning & Development.

  8. g

    Solar Footprints in California | gimi9.com

    • gimi9.com
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Solar Footprints in California | gimi9.com [Dataset]. https://gimi9.com/dataset/california_solar-footprints-in-california/
    Explore at:
    Area covered
    California
    Description

    This GIS dataset consists of polygons that represent the footprints of solar powered electric generation facilities and related infrastructure in California called Solar Footprints. The location of solar footprints was identified using other existing solar footprint datasets from various sources along with imagery interpretation. CEC staff reviewed footprints identified with imagery and digitized polygons to match the visual extent of each facility. Previous datasets of existing solar footprints used to locate solar facilities include: GIS Layers: (1) California Solar Footprints, (2) UC Berkeley Solar Points, (3) Kruitwagen et al. 2021, (4) BLM Renewable Project Facilities, (5) Quarterly Fuel and Energy Report (QFER)Imagery Datasets: Esri World Imagery, USGS National Agriculture Imagery Program (NAIP), 2020 SENTINEL 2 Satellite Imagery, 2023Solar facilities with large footprints such as parking lot solar, large rooftop solar, and ground solar were included in the solar footprint dataset. Small scale solar (approximately less than 0.5 acre) and residential footprints were not included. No other data was used in the production of these shapes. Definitions for the solar facilities identified via imagery are subjective and described as follows: Rooftop Solar: Solar arrays located on rooftops of large buildings. Parking lot Solar: Solar panels on parking lots roughly larger than 1 acre, or clusters of solar panels in adjacent parking lots. Ground Solar: Solar panels located on ground roughly larger than 1 acre, or large clusters of smaller scale footprints. Once all footprints identified by the above criteria were digitized for all California counties, the features were visually classified into ground, parking and rooftop categories. The features were also classified into rural and urban types using the 42 U.S. Code § 1490 definition for rural. In addition, the distance to the closest substation and the percentile category of this distance (e.g. 0-25th percentile, 25th-50th percentile) was also calculated. The coverage provided by this data set should not be assumed to be a complete accounting of solar footprints in California. Rather, this dataset represents an attempt to improve upon existing solar feature datasets and to update the inventory of "large" solar footprints via imagery, especially in recent years since previous datasets were published. This procedure produced a total solar project footprint of 150,250 acres. Attempts to classify these footprints and isolate the large utility-scale projects from the smaller rooftop solar projects identified in the data set is difficult. The data was gathered based on imagery, and project information that could link multiple adjacent solar footprints under one larger project is not known. However, partitioning all solar footprints that are at least partly outside of the techno-economic exclusions and greater than 7 acres yields a total footprint size of 133,493 acres. These can be approximated as utility-scale footprints. Metadata: (1) CBI Solar FootprintsAbstract: Conservation Biology Institute (CBI) created this dataset of solar footprints in California after it was found that no such dataset was publicly available at the time (Dec 2015-Jan 2016). This dataset is used to help identify where current ground based, mostly utility scale, solar facilities are being constructed and will be used in a larger landscape intactness model to help guide future development of renewable energy projects. The process of digitizing these footprints first began by utilizing an excel file from the California Energy Commission with lat/long coordinates of some of the older and bigger locations. After projecting those points and locating the facilities utilizing NAIP 2014 imagery, the developed area around each facility was digitized. While interpreting imagery, there were some instances where a fenced perimeter was clearly seen and was slightly larger than the actual footprint. For those cases the footprint followed the fenced perimeter since it limits wildlife movement through the area. In other instances, it was clear that the top soil had been scraped of any vegetation, even outside of the primary facility footprint. These footprints included the areas that were scraped within the fencing since, especially in desert systems, it has been near permanently altered. Other sources that guided the search for solar facilities included the Energy Justice Map, developed by the Energy Justice Network which can be found here:https://www.energyjustice.net/map/searchobject.php?gsMapsize=large&giCurrentpageiFacilityid;=1&gsTable;=facility&gsSearchtype;=advancedThe Solar Energy Industries Association’s “Project Location Map” which can be found here: https://www.seia.org/map/majorprojectsmap.phpalso assisted in locating newer facilities along with the "Power Plants" shapefile, updated in December 16th, 2015, downloaded from the U.S. Energy Information Administration located here:https://www.eia.gov/maps/layer_info-m.cfmThere were some facilities that were stumbled upon while searching for others, most of these are smaller scale sites located near farm infrastructure. Other sites were located by contacting counties that had solar developments within the county. Still, others were located by sleuthing around for proposals and company websites that had images of the completed facility. These helped to locate the most recently developed sites and these sites were digitized based on landmarks such as ditches, trees, roads and other permanent structures.Metadata: (2) UC Berkeley Solar PointsUC Berkeley report containing point location for energy facilities across the United States.2022_utility-scale_solar_data_update.xlsm (live.com)Metadata: (3) Kruitwagen et al. 2021Abstract: Photovoltaic (PV) solar energy generating capacity has grown by 41 per cent per year since 2009. Energy system projections that mitigate climate change and aid universal energy access show a nearly ten-fold increase in PV solar energy generating capacity by 2040. Geospatial data describing the energy system are required to manage generation intermittency, mitigate climate change risks, and identify trade-offs with biodiversity, conservation and land protection priorities caused by the land-use and land-cover change necessary for PV deployment. Currently available inventories of solar generating capacity cannot fully address these needs. Here we provide a global inventory of commercial-, industrial- and utility-scale PV installations (that is, PV generating stations in excess of 10 kilowatts nameplate capacity) by using a longitudinal corpus of remote sensing imagery, machine learning and a large cloud computation infrastructure. We locate and verify 68,661 facilities, an increase of 432 per cent (in number of facilities) on previously available asset-level data. With the help of a hand-labelled test set, we estimate global installed generating capacity to be 423 gigawatts (−75/+77 gigawatts) at the end of 2018. Enrichment of our dataset with estimates of facility installation date, historic land-cover classification and proximity to vulnerable areas allows us to show that most of the PV solar energy facilities are sited on cropland, followed by arid lands and grassland. Our inventory could aid PV delivery aligned with the Sustainable Development GoalsEnergy Resource Land Use Planning - Kruitwagen_etal_Nature.pdf - All Documents (sharepoint.com)Metadata: (4) BLM Renewable ProjectTo identify renewable energy approved and pending lease areas on BLM administered lands. To provide information about solar and wind energy applications and completed projects within the State of California for analysis and display internally and externally. This feature class denotes "verified" renewable energy projects at the California State BLM Office, displayed in GIS. The term "Verified" refers to the GIS data being constructed at the California State Office, using the actual application/maps with legal descriptions obtained from the renewable energy company. https://www.blm.gov/wo/st/en/prog/energy/renewable_energy

  9. Shoreline Management Plan Mapping - Dataset - data.gov.uk

    • ckan.publishing.service.gov.uk
    Updated Sep 30, 2015
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    ckan.publishing.service.gov.uk (2015). Shoreline Management Plan Mapping - Dataset - data.gov.uk [Dataset]. https://ckan.publishing.service.gov.uk/dataset/shoreline-management-plan-mapping1
    Explore at:
    Dataset updated
    Sep 30, 2015
    Dataset provided by
    CKANhttps://ckan.org/
    Description

    This record is for Approval for Access product AfA196. This dataset identifies which second generation Shoreline Management Plan is applicable to a particular stretch of coastline. It also identifies the policies which are applicable. It is a polyline, spatial data layer. A Shoreline Management Plan (SMP) is a large-scale assessment of the risks associated with coastal processes and helps reduce these risks to people and the developed, historic and natural environments. Coastal processes include tidal patterns, wave height, wave direction and the movement of beach and seabed materials. The SMPs provide a ‘route map’ for local authorities and other decision makers to move from the present situation towards meeting our future needs, and will identify the most sustainable approaches to managing the risks to the coast in the short term (0-20 years), medium term (20-50 years) and long term (50-100 years). INFORMATION WARNING This dataset was created for the purposes of creating a strategic overview map; as a consequence it was created at a notional scale of 1:250,000, this means that the definition of the breakpoints and the accuracy to which the SMP lengths reflect the 'coastline' is suitable for strategic level use only. Consideration should be given as to whether it should be replaced by a more accurate representation. More detailed representations of the SMP boundaries may be available at Local/Regional level. Costing information is at a broad scale and indicative only. It not appropriate for any detailed costings work, or for identifying planned capital expenditure. This dataset contains hyperlinks to websites operated by other parties. We do not control such websites and we take no responsibility for, and will not incur any liability in respect of, their content. Our inclusion of hyperlinks to such websites does not imply any endorsement of views, statements or information contained in such websites. Attribution statement: © Environment Agency copyright and/or database right 2015. All rights reserved.

  10. g

    Geomorphic Map Malakoff Diggins State Historic Park, California | gimi9.com

    • gimi9.com
    Updated Dec 15, 2017
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2017). Geomorphic Map Malakoff Diggins State Historic Park, California | gimi9.com [Dataset]. https://gimi9.com/dataset/data-gov_geomorphic-map-malakoff-diggins-state-historic-park-california/
    Explore at:
    Dataset updated
    Dec 15, 2017
    Area covered
    California
    Description

    One of the largest hydraulic mines (1.6 km2) is located in California’s Sierra Nevada within the Humbug Creek watershed and Malakoff Diggins State Historic Park (MDSHP). MDSHP’s denuded and dissected landscape is composed of weathered Eocene auriferous sediments susceptible to chronic rill and gully erosion whereas block failures and debris flows occur in more cohesive terrain. This data release includes a 2014 digital elevation model (DEM), a study area boundary, and a geomorphic map. The 2014 DEM was derived from an available aerial LiDAR dataset collected in 2014 by the California Department of Conservation. The geomorphic map was derived for the study area from using a multi-scale spatial analysis. A topographic position index (TPI) was created using focal statistics to compare the elevations across the study area. We calculated a fine-scale TPI using a circular neighborhood with a radius of 25-meters and large-scale TPI using a circular neighborhood with a radius of 100-meters. In the resulting raster positive TPI values are assigned to cells with elevations higher than the surrounding area and negative TPI values are assigned to cells with elevations lower than the surrounding area. The geomorphic map was then created using a nested conditional statement to apply classification thresholds on the basis the fine and large-scale TPI rasters and a slope raster. Ten geomorphic feature classes were defined and the map can be symbolized by feature class. The geomorphic map includes both channel and hillslope features and can be used to assess erosional and depositional processes at the landscape scale.

  11. g

    Geomorphic Mapping for the lower Middle Fork Willamette River, Oregon in...

    • gimi9.com
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Geomorphic Mapping for the lower Middle Fork Willamette River, Oregon in 2018 and 2020 | gimi9.com [Dataset]. https://gimi9.com/dataset/data-gov_geomorphic-mapping-for-the-lower-middle-fork-willamette-river-oregon-in-2018-and-2020/
    Explore at:
    Area covered
    Willamette River, Middle Fork Willamette River, Oregon
    Description

    Since 2008, large-scale restoration programs have been implemented along the Willamette River, Oregon, to address historical losses of floodplain habitats for native fish. For much of the Willamette River floodplain, direct enhancement of floodplain habitats through restoration activities is needed because the underlying hydrologic, geomorphic, and vegetation processes that historically created and sustained complex floodplain habitats have been fundamentally altered by dam construction, bank protection, large wood removal, land conversion, and other influences (for example, Hulse and others, 2002; Wallick and others, 2013). For gravel-bed rivers like the Willamette River, planimetric changes (defined here as geomorphic changes related to horizontal adjustments independent of elevation and that can be observed using aerial photographs and other two-dimensional maps) include changes in channel position, gravel bars, and side channels. Restoration activities likely to cause planimetric changes in channel features include revetment removal, construction of off-channels features, modifications to floodplain topography, and gravel pit enhancements. Repeat planimetric mapping, provides a basis for quantifying channel changes and relating those changes to restoration projects or other natural or anthropogenic influences affecting geomorphic processes. Repeat mapping also can be used to quantify planimetric changes resulting directly from implementation of restoration projects, as well as subsequent geomorphic evolution of those features. In this study, repeat geomorphic mapping was completed for 2018 and 2020 along the lower 6.8 kilometers of the Middle Fork Willamette River (river mile 187.5 to 191.5 on USGS topographic maps) to support an assessment of geomorphic changes resulting from restoration activities implemented from 2014 to 2017. These datasets can be combined with previously published mapping (Keith and Gordon, 2019) in which the lower 11.6 km of Fall Creek and lower 27.3 km of Middle Fork Willamette were mapped for six periods (1936, 2005, 2011, 2012, 2014, and 2016). The 2018 and 2020 mapping was completed in the vicinity of large-scale restoration projects at the Willamette Confluence Preserve where gravel ponds and revetments were modified to improve floodplain habitats. The repeat mapping datasets include GIS layers defining the landforms and water features, as well as the types of cover and vegetation density on landforms, and types of secondary channel features mapped throughout the active channel. For this study, the active channel was defined as area typically inundated during annual high flows and includes the low-flow channel as well as side channels and gravel bars. Floodplain islands that have a substantial area surrounded by active channel features in the mapping were also included.

  12. n

    Watershed Boundary HUC 10

    • opdgig.dos.ny.gov
    Updated Nov 8, 2022
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    New York State Department of State (2022). Watershed Boundary HUC 10 [Dataset]. https://opdgig.dos.ny.gov/datasets/watershed-boundary-huc-10/about
    Explore at:
    Dataset updated
    Nov 8, 2022
    Dataset authored and provided by
    New York State Department of State
    Area covered
    Description

    The United States is divided and sub-divided into successively smaller hydrologic units which are classified into four levels: regions, subregions, accounting units, and cataloging units. The hydrologic units are arranged or nested within each other, from the largest geographic area (regions) to the smallest geographic area (cataloging units). Each hydrologic unit is identified by a unique hydrologic unit code (HUC) consisting of two to eight digits based on the four levels of classification in the hydrologic unit system. The intent of defining Hydrologic Units (HU) within the Watershed Boundary Dataset is to establish a base-line drainage boundary framework, accounting for all land and surface areas. Hydrologic units are intended to be used as a tool for water-resource management and planning activities particularly for site-specific and localized studies requiring a level of detail provided by large-scale map information. The WBD complements the National Hydrography Dataset (NHD) and supports numerous programmatic missions and activities including: watershed management, rehabilitation and enhancement, aquatic species conservation strategies, flood plain management and flood prevention, water-quality initiatives and programs, dam safety programs, fire assessment and management, resource inventory and assessment, water data analysis and water census. The Watershed Boundary Dataset (WBD) is a comprehensive aggregated collection of hydrologic unit data consistent with the national criteria for delineation and resolution. It defines the areal extent of surface water drainage to a point except in coastal or lake front areas where there could be multiple outlets as stated by the "Federal Standards and Procedures for the National Watershed Boundary Dataset (WBD)" "Standard" (http://pubs.usgs.gov/tm/11/a3/). Watershed boundaries are determined solely upon science-based hydrologic principles, not favoring any administrative boundaries or special projects, nor particular program or agency. This dataset represents the hydrologic unit boundaries to the 12-digit (6th level) for the entire United States. Some areas may also include additional subdivisions representing the 14- and 16-digit hydrologic unit (HU). At a minimum, the HUs are delineated at 1:24,000-scale in the conterminous United States, 1:25,000-scale in Hawaii, Pacific basin and the Caribbean, and 1:63,360-scale in Alaska, meeting the National Map Accuracy Standards (NMAS). Higher resolution boundaries are being developed where partners and data exist and will be incorporated back into the WBD. WBD data are delivered as a dataset of polygons and corresponding lines that define the boundary of the polygon. WBD polygon attributes include hydrologic unit codes (HUC), size (in the form of acres and square kilometers), name, downstream hydrologic unit code, type of watershed, non-contributing areas, and flow modifications. The HUC describes where the unit is in the country and the level of the unit. WBD line attributes contain the highest level of hydrologic unit for each boundary, line source information and flow modifications.View Dataset on the Gateway

  13. Data from: Georgia Railroads

    • gisdata.fultoncountyga.gov
    • hub.arcgis.com
    Updated Oct 9, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Georgia Association of Regional Commissions (2024). Georgia Railroads [Dataset]. https://gisdata.fultoncountyga.gov/datasets/GARC::georgia-railroads
    Explore at:
    Dataset updated
    Oct 9, 2024
    Dataset provided by
    The Georgia Association of Regional Commissions
    Authors
    Georgia Association of Regional Commissions
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    Description

    This layer was developed by the Research & Analytics Division of the Atlanta Regional Commission and contains railway features including railroads, rail yards, and public transit rail lines. Features were originally captured from the Georgia Department of Transportation's General Highway Base Map. They have been updated and photo-revised using 1993 digital orthophoto quarter quadrangles (DOQQs) at 1:12,000-scale. This dataset was developed as part of Georgia's statewide core base map through a coordinated, multi-agency effort to produce large-scale data for transportation, hydrography, wetlands and boundaries. Attributes:COUNTY_FIP = Standard 3-digit County FIPS codes. (Definition source is from Federal Information Processing Standard (FIPS), National Institute of Standards & Technology (NIST))NAME = Full name of owner/operator companyMILES = Length of track segment in milesSOURCE = Name of original data source for segment Shape.STLength() = Length of track segment in feetSource: GA Dept. of Transportation (GDOT), Atlanta Regional CommissionDate: 1996For additional information, please visit the Atlanta Regional Commission at www.atlantaregional.com

  14. c

    Military Bases

    • geodata.colorado.gov
    • s.cnmilf.com
    • +4more
    Updated Jun 30, 2010
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Department of Transportation: ArcGIS Online (2010). Military Bases [Dataset]. https://geodata.colorado.gov/maps/usdot::military-bases
    Explore at:
    Dataset updated
    Jun 30, 2010
    Dataset authored and provided by
    U.S. Department of Transportation: ArcGIS Online
    Area covered
    Description

    The Military Bases dataset was last updated on November 11, 2025 and are defined by Fiscal Year 2024 data, from the Office of the Assistant Secretary of Defense for Energy, Installations, and Environment and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The dataset depicts the authoritative locations of the most commonly known Department of Defense (DoD) sites, installations, ranges, and training areas world-wide. These sites encompass land which is federally owned or otherwise managed. This dataset was created from source data provided by the four Military Service Component headquarters and was compiled by the Defense Installation Spatial Data Infrastructure (DISDI) Program within the Office of the Assistant Secretary of Defense for Energy, Installations, and Environment. Only sites reported in the BSR or released in a map supplementing the Foreign Investment Risk Review Modernization Act of 2018 (FIRRMA) Real Estate Regulation (31 CFR Part 802) were considered for inclusion. This list does not necessarily represent a comprehensive collection of all Department of Defense facilities. For inventory purposes, installations are comprised of sites, where a site is defined as a specific geographic location of federally owned or managed land and is assigned to military installation. DoD installations are commonly referred to as a base, camp, post, station, yard, center, homeport facility for any ship, or other activity under the jurisdiction, custody, control of the DoD.

    While every attempt has been made to provide the best available data quality, this data set is intended for use at mapping scales between 1:50,000 and 1:3,000,000. For this reason, boundaries in this data set may not perfectly align with DoD site boundaries depicted in other federal data sources. Maps produced at a scale of 1:50,000 or smaller which otherwise comply with National Map Accuracy Standards, will remain compliant when this data is incorporated. Boundary data is most suitable for larger scale maps; point locations are better suited for mapping scales between 1:250,000 and 1:3,000,000.

    If a site is part of a Joint Base (effective/designated on 1 October, 2010) as established under the 2005 Base Realignment and Closure process, it is attributed with the name of the Joint Base. All sites comprising a Joint Base are also attributed to the responsible DoD Component, which is not necessarily the pre-2005 Component responsible for the site. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529039

  15. t

    Broad typology for rivers and lakes in Europe for large scale analysis -...

    • service.tib.eu
    Updated Nov 30, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2024). Broad typology for rivers and lakes in Europe for large scale analysis - Vdataset - LDM [Dataset]. https://service.tib.eu/ldmservice/dataset/png-doi-10-1594-pangaea-908578
    Explore at:
    Dataset updated
    Nov 30, 2024
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    Europe
    Description

    Typology of waters is defined as a group of water bodies having common natural ecological conditions in terms of geo-morphological, hydrological, physico-chemical, and biological characteristics. The type descriptors are permanent characteristics that do not respond to human activities and represent the fixed abiotic conditions that explain natural variability. For the need of large-scale analysis of ecological status, multiple pressures on rivers and lakes, linkages of water body types to habitat types and for comparison of type-specific limit values for nutrients and other quality elements across countries in Europe, a broad river and lake typology was developed. Descriptors categories are dominant geology, region, river catchment, river altitude, river flow, lake size and mean lake depth. The ranges of descriptors largely follow the system A of Water Framework Directive (WFD) (EC, 2000) and are described in Lyche Solheim et al. (2019). Various European data sources were used for spatial allocation of rivers and lakes broad types. The starting point was the European Catchments and Rivers Network System (Ecrins) (EEA, 2012), which is organised into sets of spatial thematic layers: lake polygons, river segments (drains), nodes representing intersection of river and catchments and almost 180,000 “Functional Elementary Catchments (FECs)”. Catchments include “main drains” (connecting together the FECs) and “secondary drains” (internal within a FEC). We assigned one broad type to all segments belonging to “main drain” of each FEC and named them “river segment". The catchment size of river segments in each FEC is defined as the sum of the upstream drainage area and FEC surface area. The upstream drainage area has been derived using data in “Code Arbo” in Ecrins database (Globevnik et al., 2017). The altitude of the lower end points of river segments in each FEC is available in Ecrins river database. Lake surface area is obtained from Ecrins lake area attribute “Area”. Data on mean lake depth were obtained from Waterbase – Water Quality database (EEA, 2016) or estimated from terrain data. The basic map of five geological (geochemical) categories was produced from two thematic maps: bedrock map “International Hydrogeological Map of Europe (IHME 1500_v11)” (Dutcher et al, 2015) and the soil map of the European Union “SGDBE4” (JRC, 2016). The dominant geology for lakes was derived from this map with the overlay procedure. For each FEC we then defined dominant catchment geology (geochemistry) and assigned this geology type to all river segments forming the FEC's main drain. Spatial extent of the Mediterranean region is obtained from spatial layer 'Biogeographical regions of Europe» (EEA, 2019). More details on methodology are in Lyche Solheim et al. (2019).

  16. d

    California State Waters Map Series--Offshore of Point Conception Web...

    • catalog.data.gov
    • data.usgs.gov
    • +1more
    Updated Nov 26, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Geological Survey (2025). California State Waters Map Series--Offshore of Point Conception Web Services [Dataset]. https://catalog.data.gov/dataset/california-state-waters-map-series-offshore-of-point-conception-web-services
    Explore at:
    Dataset updated
    Nov 26, 2025
    Dataset provided by
    United States Geological Surveyhttp://www.usgs.gov/
    Area covered
    Point Conception, California
    Description

    In 2007, the California Ocean Protection Council initiated the California Seafloor Mapping Program (CSMP), designed to create a comprehensive seafloor map of high-resolution bathymetry, marine benthic habitats, and geology within California’s State Waters. The program supports a large number of coastal-zone- and ocean-management issues, including the California Marine Life Protection Act (MLPA) (California Department of Fish and Wildlife, 2008), which requires information about the distribution of ecosystems as part of the design and proposal process for the establishment of Marine Protected Areas. A focus of CSMP is to map California’s State Waters with consistent methods at a consistent scale. The CSMP approach is to create highly detailed seafloor maps through collection, integration, interpretation, and visualization of swath sonar data (the undersea equivalent of satellite remote-sensing data in terrestrial mapping), acoustic backscatter, seafloor video, seafloor photography, high-resolution seismic-reflection profiles, and bottom-sediment sampling data. The map products display seafloor morphology and character, identify potential marine benthic habitats, and illustrate both the surficial seafloor geology and shallow (to about 100 m) subsurface geology. It is emphasized that the more interpretive habitat and geology data rely on the integration of multiple, new high-resolution datasets and that mapping at small scales would not be possible without such data. This approach and CSMP planning is based in part on recommendations of the Marine Mapping Planning Workshop (Kvitek and others, 2006), attended by coastal and marine managers and scientists from around the state. That workshop established geographic priorities for a coastal mapping project and identified the need for coverage of “lands” from the shore strand line (defined as Mean Higher High Water; MHHW) out to the 3-nautical-mile (5.6-km) limit of California’s State Waters. Unfortunately, surveying the zone from MHHW out to 10-m water depth is not consistently possible using ship-based surveying methods, owing to sea state (for example, waves, wind, or currents), kelp coverage, and shallow rock outcrops. Accordingly, some of the data presented in this series commonly do not cover the zone from the shore out to 10-m depth. This data is part of a series of online U.S. Geological Survey (USGS) publications, each of which includes several map sheets, some explanatory text, and a descriptive pamphlet. Each map sheet is published as a PDF file. Geographic information system (GIS) files that contain both ESRI ArcGIS raster grids (for example, bathymetry, seafloor character) and geotiffs (for example, shaded relief) are also included for each publication. For those who do not own the full suite of ESRI GIS and mapping software, the data can be read using ESRI ArcReader, a free viewer that is available at http://www.esri.com/software/arcgis/arcreader/index.html (last accessed September 20, 2013). The California Seafloor Mapping Program is a collaborative venture between numerous different federal and state agencies, academia, and the private sector. CSMP partners include the California Coastal Conservancy, the California Ocean Protection Council, the California Department of Fish and Wildlife, the California Geological Survey, California State University at Monterey Bay’s Seafloor Mapping Lab, Moss Landing Marine Laboratories Center for Habitat Studies, Fugro Pelagos, Pacific Gas and Electric Company, National Oceanic and Atmospheric Administration (NOAA, including National Ocean Service–Office of Coast Surveys, National Marine Sanctuaries, and National Marine Fisheries Service), U.S. Army Corps of Engineers, the Bureau of Ocean Energy Management, the National Park Service, and the U.S. Geological Survey. These web services for the Offshore of Point Conception map area includes data layers that are associated to GIS and map sheets available from the USGS CSMP web page at https://walrus.wr.usgs.gov/mapping/csmp/index.html. Each published CSMP map area includes a data catalog of geographic information system (GIS) files; map sheets that contain explanatory text; and an associated descriptive pamphlet. This web service represents the available data layers for this map area. Data was combined from different sonar surveys to generate a comprehensive high-resolution bathymetry and acoustic-backscatter coverage of the map area. These data reveal a range of physiographic including exposed bedrock outcrops, large fields of sand waves, as well as many human impacts on the seafloor. To validate geological and biological interpretations of the sonar data, the U.S. Geological Survey towed a camera sled over specific offshore locations, collecting both video and photographic imagery; these “ground-truth” surveying data are available from the CSMP Video and Photograph Portal at https://doi.org/10.5066/F7J1015K. The “seafloor character” data layer shows classifications of the seafloor on the basis of depth, slope, rugosity (ruggedness), and backscatter intensity and which is further informed by the ground-truth-survey imagery. The “potential habitats” polygons are delineated on the basis of substrate type, geomorphology, seafloor process, or other attributes that may provide a habitat for a specific species or assemblage of organisms. Representative seismic-reflection profile data from the map area is also include and provides information on the subsurface stratigraphy and structure of the map area. The distribution and thickness of young sediment (deposited over the past about 21,000 years, during the most recent sea-level rise) is interpreted on the basis of the seismic-reflection data. The geologic polygons merge onshore geologic mapping (compiled from existing maps by the California Geological Survey) and new offshore geologic mapping that is based on integration of high-resolution bathymetry and backscatter imagery seafloor-sediment and rock samplesdigital camera and video imagery, and high-resolution seismic-reflection profiles. The information provided by the map sheets, pamphlet, and data catalog has a broad range of applications. High-resolution bathymetry, acoustic backscatter, ground-truth-surveying imagery, and habitat mapping all contribute to habitat characterization and ecosystem-based management by providing essential data for delineation of marine protected areas and ecosystem restoration. Many of the maps provide high-resolution baselines that will be critical for monitoring environmental change associated with climate change, coastal development, or other forcings. High-resolution bathymetry is a critical component for modeling coastal flooding caused by storms and tsunamis, as well as inundation associated with longer term sea-level rise. Seismic-reflection and bathymetric data help characterize earthquake and tsunami sources, critical for natural-hazard assessments of coastal zones. Information on sediment distribution and thickness is essential to the understanding of local and regional sediment transport, as well as the development of regional sediment-management plans. In addition, siting of any new offshore infrastructure (for example, pipelines, cables, or renewable-energy facilities) will depend on high-resolution mapping. Finally, this mapping will both stimulate and enable new scientific research and also raise public awareness of, and education about, coastal environments and issues. Web services were created using an ArcGIS service definition file. The ArcGIS REST service and OGC WMS service include all Offshore of Point Conception map area data layers. Data layers are symbolized as shown on the associated map sheets.

  17. d

    Data from: High-resolution maps of big sagebrush plant community biomass...

    • datasets.ai
    • catalog.data.gov
    0, 55
    Updated Jun 1, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Department of the Interior (2023). High-resolution maps of big sagebrush plant community biomass using multivariate matching algorithms [Dataset]. https://datasets.ai/datasets/high-resolution-maps-of-big-sagebrush-plant-community-biomass-using-multivariate-matching--9b1e1
    Explore at:
    0, 55Available download formats
    Dataset updated
    Jun 1, 2023
    Dataset authored and provided by
    Department of the Interior
    Description

    These GeoTIFF data were compiled to investigate how a new multivariate matching algorithm transfers simulated plant functional biomass of big sagebrush plant communities from 200 sites to a gridded product with 30-arcsec spatial resolution. Objectives of our study were to (1) describe how climate change will alter the biomass and composition of key plant functional types; (2) quantify the impacts of climate change on future functional type biomass and composition along climatic gradients; (3) identify if and which geographic locations will be relatively unaffected by climate change while others experience large effects; and (4) determine if there is consistency in climate change impacts on plant communities among a representative set of climate scenarios. These data represent geographic patterns in simulated plant functional biomass of big sagebrush plant communities (cheatgrass, perennial forbs, C3 perennial grasses, C4 perennial grasses, perennial grasses, big sagebrush) as across-year averages of under historical ("current"; years 1980-2010) climate and differences ("change") between projected future climates (years 2030-2060 and 2070-2100) derived as medians across 13 Global Climate Models (GCMs) that participated in CMIP5 for representative concentration pathways RCP4.5 and RCP8.5 and historical values. These data were created in 2020 and 2021 for the area of the sagebrush region in the western United States to describe geographic patterns in simulated plant functional biomass of big sagebrush plant communities under historical and projected future climate conditions at a 30-arcsec spatial resolution. These data can be used to confirm the results of the study identified as the ‘Larger Work Citation’ including the high resolution matching of projected declines in big sagebrush, perennial C3 grass and perennial forb biomass in warm, dry sites; no projected change or increases in functional type biomass in cold, moist sites; and widespread projected increases in perennial C4 grasses across sagebrush plant communities in the sagebrush region of the western United States as defined by Palmquist et al. (2021) and within the scope as defined by the study. These data may also be used to evaluate the potential impact of changing climate conditions on geographic patterns in simulated plant functional biomass of big sagebrush plant communities within the scope defined by the study. In particular, these data can be useful for informing the design of long-term landscape conservation efforts to maintain and expand wildlife habitat across the sagebrush biome.

  18. a

    National Forest Inventory GB 2014

    • data-forestry.opendata.arcgis.com
    • dtechtive.com
    • +2more
    Updated Oct 2, 2018
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    mapping.geodata_forestry (2018). National Forest Inventory GB 2014 [Dataset]. https://data-forestry.opendata.arcgis.com/items/f18ce64eec874b5287a62b20adcffaad
    Explore at:
    Dataset updated
    Oct 2, 2018
    Dataset authored and provided by
    mapping.geodata_forestry
    Description

    The NFI definition of woodland is a minimum area of 0.5 hectares under stands of trees with, or with the potentialto achieve, tree crown cover of more than 20% of the ground.Areas of young trees, which have the potential to achieve a canopy cover of more than 20%, will also beinterpreted as woodland and mapped. The minimum width for woodland is 20 m, although where woodlands areconnected by a narrow neck of woodland less than 20 m wide, the break may be disregarded if less than 20 m inextent.Intervening land classes such as Roads - all 'tarmac' roads should be excluded from the woodland area, butinternal forest tracks, farmers tracks, rides etc. will be included as part of the woodland if < 20m wide.Rivers - where the gap in woodland is 20m then rivers will be excluded from the woodland area.Power lines etc. - where the gap in woodland is 20m then power lines will be excluded from the woodland area.Railways - all normal gauge railways should be excluded from woodland Scrubby vegetation" is included within this survey where low woody growth seems to dominate a likely woodland site. The definition of an open area is any open area that is 20m wide and 0.5 ha in extent and is completely surrounded by woodland.The woodland boundaries have been interpreted from colour aerial orthophotographic imagery. For the base map,photographic images aimed to be no older than 3 years at the time of mapping (i.e. areas mapped in 2007 wouldbe based on photographs that were ideally taken no earlier than 2004). As the map is be the basis for a longerrolling programme of sample field surveys it has been necessary to develop procedures to update the map to thedate of the field survey, currently 2011, for the purpose of reporting on the current phase.The map is continually updated on an annual basis. These updates will are achieved by a combination of remotesensing and updated aerial imagery analysis for changes in the woodland structure and with reference toavailable new planting information from grant schemes and the FE sub-compartment database.Ordnance Survey MasterMap® (OSMM) features have been used as a reference for capturing the woodlandboundaries. OSMM is the most up to date large-scale digital map of GB providing a seamless database for1:1250, 1:2500 and 1:10000 survey data.All woodland (both urban and rural, regardless of ownership) which is 0.5ha or greater in extent, with theexception of Assumed woodland or Low density areas that can be 0.1ha or greater in extend, as been mappedWoodland that is less than 0.5ha in extent will not be described within the dataset but will be included in aseparate sample survey of small woodland and tree features.The primary objective is to create a new digital map of all woodland in Great Britain using O.S.MasterMap features as boundaries where appropriate. The map shows the extent of all woodland of 0.5 ha.Woodland categories are defined by IFT (Interpreted Forest Type) values. Detailed Woodland categories are:BroadleavedConiferFelledGround Prepared for New PlantingMixed - predominantly BroadleavedMixed - predominantly ConiferYoung TreesCoppiceCoppice with StandardsShrub LandUncertainCloud or ShadowLow DensityAssumed woodlandFailedWindthrow/WindblowNon woodland categories are defined by the IOA (Interpreted Open Area) values. Detailed Non woodland categories are:Agriculture landBare areaGrassOpen waterOther vegetationPower lineQuarryRiverRoadUrbanWindfarm

  19. c

    Regional Drainage Basin Lines

    • geodata.ct.gov
    • data.ct.gov
    • +4more
    Updated Oct 28, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Department of Energy & Environmental Protection (2019). Regional Drainage Basin Lines [Dataset]. https://geodata.ct.gov/maps/CTDEEP::regional-drainage-basin-lines
    Explore at:
    Dataset updated
    Oct 28, 2019
    Dataset authored and provided by
    Department of Energy & Environmental Protection
    License

    CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
    License information was derived automatically

    Area covered
    Description

    See full Data Guide here. Regional Drainage Basin Set:

    Connecticut Regional Drainage Basins is 1:24,000-scale, polygon and line feature data that define Regional drainage basin areas in Connecticut. These large basins mostly range from 40 to 400 square miles in size and make up the even larger major drainage basin areas. Connecticut Regional Drainage Basins includes drainage areas for all Connecticut rivers, streams, brooks, lakes, reservoirs and ponds published on 1:24,000-scale 7.5 minute topographic quadrangle maps prepared by the USGS between 1969 and 1984. Data is compiled at 1:24,000 scale (1 inch = 2,000 feet). This information is not updated. Polygon and line features represent drainage basin areas and boundaries, respectively. Each basin area (polygon) feature is outlined by one or more major and regional basin boundary (line) feature. These data include 85 regional basin area (polygon) features and 529 regional basin boundary (line) features. Regional Basin area (polygon) attributes include major and regional basin number, and feature size in acres and square miles. The regional basin number (RBAS_NO) uniquely identifies individual basins and is 2 characters in length. There are 44 unique regional basin numbers. Examples include 43, 60 and 61. The first digit (column 1) designates the major basin and the first two digits (columns 1-2) designate the regional basin. Note, there are slightly more regional basin polygon features (85) than unique regional basin numbers (44) due to coastal regional basins defined by series of polygon features located along the Connecticut shoreline. Regional basin boundary (line) attributes include a drainage divide type attribute (DIVIDE) used to cartographically represent the hierarchical drainage basin system. This divide type attribute is used to assign different line symbology to individual major and regional drainage basin divides. For example, major basin drainage divides are more pronounced and shown with a wider line symbol than regional basin drainage divides. Connecticut Regional Drainage Basin polygon and line feature data are derived from the geometry and attributes of the Connecticut Drainage Basins data. Purpose: The polygon features define the contributing drainage area for individual reservoirs, lakes, ponds and river and stream reaches in Connecticut. These are hydrologic land units where precipitation is collected. Rain falling in a basin may take two courses. It may both run over the land and quickly enter surface watercourses, or it may soak into the ground moving through the earth until it surfaces at a wetland or stream. In an undisturbed natural drainage basin, the surface and ground water arrive as precipitation and leave either by evaporation or as surface runoff at the basin's outlet. A basin is a self-contained hydrologic system, with a clearly defined water budget and cycle. The amount of water that flows into the basins equals the amount that leaves. A drainage divide is the topographic barrier along a ridge or line of hilltops separating adjacent drainage basins. For example, rain or snow melt draining down one side of a hill generally will flow into a different basin and stream than water draining down the other side of the hill. These hillsides are separated by a drainage divided that follows nearby hilltops and ridge lines. Use these basin data to identify where rainfall flows over land and downstream to a particular watercourse. Use these data to categorize and tabulate information according to drainage basin by identifying the local basin number for individual reservoir, lake, pond, stream reach, or location of interest. Due to the hierarchical nature of the basin numbering system, a database that records the 2-digit regional basin number for individual geographic locations of interest will support tabulations by major and regional basin as well as document the unique 2-digit regional basin identification number. To identify either all upstream basins draining to a particular location or all downstream basins flowing from a particular location, refer to the Gazetteer of Drainage Basin Areas of Connecticut, Nosal, 1977, CT DEP Water Resources Bulletin 45, for the hydrologic sequence, headwater to outfall, of drainage basins available at http://cteco.uconn.edu/docs/wrb/wrb45_gazetteer_of_drainage_areas_of_connecticut.pdf Not intended for maps printed at map scales greater or more detailed than 1:24,000 scale (1 inch = 2,000 feet.). Not intended for analysis with other digital data compiled at scales greater than or more detailed than 1:24,000 scale. Use these data with 1:24,000-scale hydrography data also available from the State of Connecticut, Department of Environmental Protection.

    Connecticut Regional Drainage Basins is 1:24,000-scale, polygon and line feature data that define Regional drainage basin areas in Connecticut. These large basins mostly range from 40 to 400 square miles in size and make up the even larger major drainage basin areas. Connecticut Regional Drainage Basins includes drainage areas for all Connecticut rivers, streams, brooks, lakes, reservoirs and ponds published on 1:24,000-scale 7.5 minute topographic quadrangle maps prepared by the USGS between 1969 and 1984. Data is compiled at 1:24,000 scale (1 inch = 2,000 feet). This information is not updated. Polygon and line features represent drainage basin areas and boundaries, respectively. Each basin area (polygon) feature is outlined by one or more major and regional basin boundary (line) feature. These data include 85 regional basin area (polygon) features and 529 regional basin boundary (line) features. Regional Basin area (polygon) attributes include major and regional basin number, and feature size in acres and square miles. The regional basin number (RBAS_NO) uniquely identifies individual basins and is 2 characters in length. There are 44 unique regional basin numbers. Examples include 43, 60 and 61. The first digit (column 1) designates the major basin and the first two digits (columns 1-2) designate the regional basin. Note, there are slightly more regional basin polygon features (85) than unique regional basin numbers (44) due to coastal regional basins defined by series of polygon features located along the Connecticut shoreline. Regional basin boundary (line) attributes include a drainage divide type attribute (DIVIDE) used to cartographically represent the hierarchical drainage basin system. This divide type attribute is used to assign different line symbology to individual major and regional drainage basin divides. For example, major basin drainage divides are more pronounced and shown with a wider line symbol than regional basin drainage divides. Connecticut Regional Drainage Basin polygon and line feature data are derived from the geometry and attributes of the Connecticut Drainage Basins data.

  20. a

    Utah Black Bear Habitat

    • dwr-data-utahdnr.hub.arcgis.com
    • opendata.gis.utah.gov
    • +2more
    Updated May 29, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Utah DNR Online Maps (2020). Utah Black Bear Habitat [Dataset]. https://dwr-data-utahdnr.hub.arcgis.com/datasets/utah-black-bear-habitat
    Explore at:
    Dataset updated
    May 29, 2020
    Dataset authored and provided by
    Utah DNR Online Maps
    Area covered
    Description

    Black bear distribution, season of habitat use, and habitat values are determined by local wildlife biologist relying on observations, surveys, and radio/satellite data. For use in large-scale planning and reporting.Habitat definitions:Crucial value - habitat on which the local population of a wildlife species depends for survival because there are no alternative ranges or habitats available. Crucial value habitat is essential to the life history requirements of a wildlife species. Degradation or unavailability of crucial habitat will lead to significant declines in carrying capacity and/or numbers of wildlife species in question.Substantial value - habitat used by a wildlife species but is not crucial for population survival. Degradation or unavailability of substantial value habitat will not lead to significant declines in carrying capacity and/or numbers of the wildlife species in question.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
U.S. Department of State (Point of Contact) (2025). Large Scale International Boundaries [Dataset]. https://catalog.data.gov/dataset/large-scale-international-boundaries
Organization logo

Large Scale International Boundaries

Explore at:
33 scholarly articles cite this dataset (View in Google Scholar)
Dataset updated
Aug 30, 2025
Dataset provided by
United States Department of Statehttp://state.gov/
Description

Overview The Office of the Geographer and Global Issues at the U.S. Department of State produces the Large Scale International Boundaries (LSIB) dataset. The current edition is version 11.4 (published 24 February 2025). The 11.4 release contains updated boundary lines and data refinements designed to extend the functionality of the dataset. These data and generalized derivatives are the only international boundary lines approved for U.S. Government use. The contents of this dataset reflect U.S. Government policy on international boundary alignment, political recognition, and dispute status. They do not necessarily reflect de facto limits of control. National Geospatial Data Asset This dataset is a National Geospatial Data Asset (NGDAID 194) managed by the Department of State. It is a part of the International Boundaries Theme created by the Federal Geographic Data Committee. Dataset Source Details Sources for these data include treaties, relevant maps, and data from boundary commissions, as well as national mapping agencies. Where available and applicable, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery process includes analysis of satellite imagery and elevation data. Due to the limitations of source materials and processing techniques, most lines are within 100 meters of their true position on the ground. Cartographic Visualization The LSIB is a geospatial dataset that, when used for cartographic purposes, requires additional styling. The LSIB download package contains example style files for commonly used software applications. The attribute table also contains embedded information to guide the cartographic representation. Additional discussion of these considerations can be found in the Use of Core Attributes in Cartographic Visualization section below. Additional cartographic information pertaining to the depiction and description of international boundaries or areas of special sovereignty can be found in Guidance Bulletins published by the Office of the Geographer and Global Issues: https://data.geodata.state.gov/guidance/index.html Contact Direct inquiries to internationalboundaries@state.gov. Direct download: https://data.geodata.state.gov/LSIB.zip Attribute Structure The dataset uses the following attributes divided into two categories: ATTRIBUTE NAME | ATTRIBUTE STATUS CC1 | Core CC1_GENC3 | Extension CC1_WPID | Extension COUNTRY1 | Core CC2 | Core CC2_GENC3 | Extension CC2_WPID | Extension COUNTRY2 | Core RANK | Core LABEL | Core STATUS | Core NOTES | Core LSIB_ID | Extension ANTECIDS | Extension PREVIDS | Extension PARENTID | Extension PARENTSEG | Extension These attributes have external data sources that update separately from the LSIB: ATTRIBUTE NAME | ATTRIBUTE STATUS CC1 | GENC CC1_GENC3 | GENC CC1_WPID | World Polygons COUNTRY1 | DoS Lists CC2 | GENC CC2_GENC3 | GENC CC2_WPID | World Polygons COUNTRY2 | DoS Lists LSIB_ID | BASE ANTECIDS | BASE PREVIDS | BASE PARENTID | BASE PARENTSEG | BASE The core attributes listed above describe the boundary lines contained within the LSIB dataset. Removal of core attributes from the dataset will change the meaning of the lines. An attribute status of “Extension” represents a field containing data interoperability information. Other attributes not listed above include “FID”, “Shape_length” and “Shape.” These are components of the shapefile format and do not form an intrinsic part of the LSIB. Core Attributes The eight core attributes listed above contain unique information which, when combined with the line geometry, comprise the LSIB dataset. These Core Attributes are further divided into Country Code and Name Fields and Descriptive Fields. County Code and Country Name Fields “CC1” and “CC2” fields are machine readable fields that contain political entity codes. These are two-character codes derived from the Geopolitical Entities, Names, and Codes Standard (GENC), Edition 3 Update 18. “CC1_GENC3” and “CC2_GENC3” fields contain the corresponding three-character GENC codes and are extension attributes discussed below. The codes “Q2” or “QX2” denote a line in the LSIB representing a boundary associated with areas not contained within the GENC standard. The “COUNTRY1” and “COUNTRY2” fields contain the names of corresponding political entities. These fields contain names approved by the U.S. Board on Geographic Names (BGN) as incorporated in the ‘"Independent States in the World" and "Dependencies and Areas of Special Sovereignty" lists maintained by the Department of State. To ensure maximum compatibility, names are presented without diacritics and certain names are rendered using common cartographic abbreviations. Names for lines associated with the code "Q2" are descriptive and not necessarily BGN-approved. Names rendered in all CAPITAL LETTERS denote independent states. Names rendered in normal text represent dependencies, areas of special sovereignty, or are otherwise presented for the convenience of the user. Descriptive Fields The following text fields are a part of the core attributes of the LSIB dataset and do not update from external sources. They provide additional information about each of the lines and are as follows: ATTRIBUTE NAME | CONTAINS NULLS RANK | No STATUS | No LABEL | Yes NOTES | Yes Neither the "RANK" nor "STATUS" fields contain null values; the "LABEL" and "NOTES" fields do. The "RANK" field is a numeric expression of the "STATUS" field. Combined with the line geometry, these fields encode the views of the United States Government on the political status of the boundary line. ATTRIBUTE NAME | | VALUE | RANK | 1 | 2 | 3 STATUS | International Boundary | Other Line of International Separation | Special Line A value of “1” in the “RANK” field corresponds to an "International Boundary" value in the “STATUS” field. Values of ”2” and “3” correspond to “Other Line of International Separation” and “Special Line,” respectively. The “LABEL” field contains required text to describe the line segment on all finished cartographic products, including but not limited to print and interactive maps. The “NOTES” field contains an explanation of special circumstances modifying the lines. This information can pertain to the origins of the boundary lines, limitations regarding the purpose of the lines, or the original source of the line. Use of Core Attributes in Cartographic Visualization Several of the Core Attributes provide information required for the proper cartographic representation of the LSIB dataset. The cartographic usage of the LSIB requires a visual differentiation between the three categories of boundary lines. Specifically, this differentiation must be between: International Boundaries (Rank 1); Other Lines of International Separation (Rank 2); and Special Lines (Rank 3). Rank 1 lines must be the most visually prominent. Rank 2 lines must be less visually prominent than Rank 1 lines. Rank 3 lines must be shown in a manner visually subordinate to Ranks 1 and 2. Where scale permits, Rank 2 and 3 lines must be labeled in accordance with the “Label” field. Data marked with a Rank 2 or 3 designation does not necessarily correspond to a disputed boundary. Please consult the style files in the download package for examples of this depiction. The requirement to incorporate the contents of the "LABEL" field on cartographic products is scale dependent. If a label is legible at the scale of a given static product, a proper use of this dataset would encourage the application of that label. Using the contents of the "COUNTRY1" and "COUNTRY2" fields in the generation of a line segment label is not required. The "STATUS" field contains the preferred description for the three LSIB line types when they are incorporated into a map legend but is otherwise not to be used for labeling. Use of the “CC1,” “CC1_GENC3,” “CC2,” “CC2_GENC3,” “RANK,” or “NOTES” fields for cartographic labeling purposes is prohibited. Extension Attributes Certain elements of the attributes within the LSIB dataset extend data functionality to make the data more interoperable or to provide clearer linkages to other datasets. The fields “CC1_GENC3” and “CC2_GENC” contain the corresponding three-character GENC code to the “CC1” and “CC2” attributes. The code “QX2” is the three-character counterpart of the code “Q2,” which denotes a line in the LSIB representing a boundary associated with a geographic area not contained within the GENC standard. To allow for linkage between individual lines in the LSIB and World Polygons dataset, the “CC1_WPID” and “CC2_WPID” fields contain a Universally Unique Identifier (UUID), version 4, which provides a stable description of each geographic entity in a boundary pair relationship. Each UUID corresponds to a geographic entity listed in the World Polygons dataset. These fields allow for linkage between individual lines in the LSIB and the overall World Polygons dataset. Five additional fields in the LSIB expand on the UUID concept and either describe features that have changed across space and time or indicate relationships between previous versions of the feature. The “LSIB_ID” attribute is a UUID value that defines a specific instance of a feature. Any change to the feature in a lineset requires a new “LSIB_ID.” The “ANTECIDS,” or antecedent ID, is a UUID that references line geometries from which a given line is descended in time. It is used when there is a feature that is entirely new, not when there is a new version of a previous feature. This is generally used to reference countries that have dissolved. The “PREVIDS,” or Previous ID, is a UUID field that contains old versions of a line. This is an additive field, that houses all Previous IDs. A new version of a feature is defined by any change to the

Search
Clear search
Close search
Google apps
Main menu