This MS Excel spreadsheet implements the procedure for calculating the CIELAB perceptually-uniform color attributes and color differences from the primary-defined RGB color coordinates. It may be used by map designers to obtain specific map legends comprising a large number of colors - all reliably-distinguishable from one another. The spreadsheet contains a starting list of 63 such colors – the Romanian color standard for soil type map legends (color-ordered, including lightness/chroma degrees, one color in a row).

The CIELAB color attributes, color attribute differences and overall color difference are those defined by the CIELAB color model/space (CIE S 014-4:2007. Colorimetry - Part 4: CIE 1976 L*a*b* Colour space). This model/space represents a color by using three abstract coordinates (orthogonal axes): L* has values between 0 (black) and 100 (white), indicating the color lightness; a* has positive values indicating amounts of red, negative values indicating the amounts of green and the value zero indicating neutral grey; b* has positive values indicating amounts of yellow, negative values indicating the amounts of blue and the value zero indicating neutral grey. From these three coordinates, other important perceptually-uniform color attributes can be easily calculated: CIELAB chroma (C*ab), CIELAB hue angle (hab), CIELAB attribute differences (DL*, Da*, Db*, DC*ab, Dhab) and overall CIELAB color difference (DE*ab).

The color differences calculated regarding a color are those between that color and the immediately-preceding color in the list. The list being color-ordered, the adjacent colors are normally the closest colors in the list, thus the color differences between them may be easily checked. Different other colors that appear as close in the list may be duplicated near others to see the color differences between them.

The implemented calculation procedure consists of the following steps: (i) transformation of RGB coordinates to CIEXYZ coordinates, (ii) transformation of CIEXYZ coordinates to CIELAB coordinates (perceptually-uniform) and calculation of other CIELAB color attributes, and (iii) calculation of CIELAB color differences (perceptually-uniform).

In order to obtain color lists (legends) appropriate for specific requirements, by using the "trial and error" method, the RGB coordinates (integer numbers between zero and 255) of the list colors can be easily modified/adjusted to define other colors that are reliably-distinguishable from one another, and/or new colors can be inserted into the list in an appropriate place (order). Usually, a color difference threshold of 10 DE*ab units ensures acceptably-distinguishable colors, but, naturally, this threshold may be increased. The “Recolor” button refreshes the colors in the “Colors” column of the spreadsheet, after RGB coordinates have been modified.

Abstract

This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied. The polygons in this dataset are a digital representation of the distribution or extent of geological units within the area. Polygons have a range of attributes including unit name, age, lithological description and an abbreviated symbol for use in labelling the polygons. These have been extracted from the Rock Units Table held in the Department of Natural Resources, Mines and Energy Merlin Database.

Purpose

To display the geology polygons which define the extent of rock units.

Dataset History

Supplemental_Information:

Data captured at 1:40 000 scale. The data set is sourced from the Department's Geoscience and Resources Database (GRDB), a component of the Mineral and Energy Resources Location and Information Network (MERLIN) corporate database.(GRDB), a component of the Mineral and Energy Resources Location and Information Network (MERLIN) corporate database.



NOTE: GEOLDATA was in most cases compiled based on Datum AGD66. The map tile coverages so compiled have now been projected to geographics based on Datum GDA94. Consequently the boundaries for these map tiles will not conform to the Latitude and Longitude graticule based on Datum GDA94.

Entity_and_Attribute_Information:

Detailed_Description:



  Entity_Type:



    Entity_Type_Label: 9341_r

    Entity_Type_Definition:

      Polygons have a range of attributes including unit name, age, lithological description and an abbreviated symbol for use in labelling the polygons. 

    Entity_Type_Definition_Source:

      The Rock Units Table held in the Department of Natural Resources, Mines and Energy Merlin Database. 



  Attribute:



    Attribute_Label: FID

    Attribute_Definition: Internal feature number.

    Attribute_Definition_Source: ESRI

    Attribute_Domain_Values:



      Unrepresentable_Domain:

        Sequential unique whole numbers that are automatically generated. 



    Beginning_Date_of_Attribute_Values: March 2004



  Attribute:



    Attribute_Label: Shape

    Attribute_Definition: Feature geometry.

    Attribute_Definition_Source: ESRI

    Attribute_Domain_Values:



      Unrepresentable_Domain: Coordinates defining the features.



  Attribute:



    Attribute_Label: KEY

    Attribute_Definition: Unique polygon identifier and relate item for poygon attributes



  Attribute:



    Attribute_Label: ROCK_U_NAM

    Attribute_Definition:

      The Map Unit Name of the polygon. In the case of named units it comprises of the standard binomial name. Unnamed subdivisions of named units include the binomial name with a letter symbol as a suffix. Unnamed units are represented by a letter symbol, usually in combination with a map sheet number. 



  Attribute:



    Attribute_Label: AGE

    Attribute_Definition: Geological age of unit



  Attribute:



    Attribute_Label: LITH_SUMMA

    Attribute_Definition:

      Provides a brief description of the map units as they have been described in the course of the project work, or as has appeared on relevant hard copy map legends. 



  Attribute:



    Attribute_Label: ROCK_U_TYP

    Attribute_Definition:

      Provides a means of separating map units, eg for constructing a map reference. This item will contain one of the following: STRAT- Stratigraphic unit, including sedimentary, volcanic and metamorphic rock units. INTRU- Intrusive rock units; COMPST- Compound unit where the polygon includes two or more rock units, either stratigraphic, intrusive or both; COMPST- Compound unit, as above where the dominant or topmost unit is of the STRAT type; COMPIN- Compound unit, as above, where the dominant unit is of the INTRU type; WATER- Water bodies- Large dams, lakes, waterholes. 



  Attribute:



    Attribute_Label: SEQUENCE_N

    Attribute_Definition:

      A numeric field to allow sorting of the rock units in approximate stratigraphic order as they would appear on a map legend. 



  Attribute:



    Attribute_Label: DOMINANT_R

    Attribute_Definition:

      A simplified lithological description to allow generation of thematic maps based on broad rock types. 



  Attribute:



    Attribute_Label: MAP_SYMBOL

    Attribute_Definition:

      Provides an abbreviated label for polygons. Mostly based on the letter symbols as they appear on published maps or the original hard copy compilation sheets. These are not unique across the State, but should be unique within a single map tile, and usually adjacent tiles. 



  Attribute:



    Attribute_Label: NAME_100K

    Attribute_Definition: Name of 1:100 000 map sheet coincident with the data extent.



Overview_Description:



  Entity_and_Attribute_Overview:

    Polygon Attribute information includes Polygon Key, Rock Unit Name, Age, Lithology, Rock Unit Type, Map Symbol and 1:100 000 sheet name.

Dataset Citation

"Queensland Department of Natural Resources, Mines and Energy" (2014) Qld 100k mapsheets - Warwick. Bioregional Assessment Source Dataset. Viewed 28 September 2017, http://data.bioregionalassessments.gov.au/dataset/3e2fa307-1f06-4873-96d3-5c3e5638894a.

Author: J. Cain, educator, Minnesota Alliance for Geographic EducationGrade/Audience: grade 4Resource type: lessonSubject topic(s): mapsRegion: united statesStandards: Minnesota Social Studies Standards

Standard 2: People use geographic representations and geospatial technologies to acquire, process and report information within a spatial context. Objectives: Students will be able to:

1. Explore a variety of maps.

2. Become acquainted with the elements of maps referred to as TODALS:

3. Title

4. Orientation

5. Date

6. Author

7. Legend (Key)

8. Scale

9. Locate and interpret TODALS from a variety of maps.

10. Compare and contrast elements of given maps while looking for bias.

11. Reflect on the importance of knowing TODALS when understanding and interpreting maps. Summary: Basic mapping terminology is essential for understanding and interpreting various types of maps. Knowing where to find these essential elements, and interpreting their meaning, are critical to the development of a 4th grader’s knowledge of geography.

The Lithofacial Map of the Quaternary 1 : 50,000 (LKQ 50) is a map series of the GDR covering nearly the whole former state territory besides the South of Saxony and Thuringia. The series consists of 123 map sheets, each of which encompassing several horizon maps mostly complemented by about five cross sections. Specifications concerning map content and structure provides Cepek (1999). The data of the LKQ 50 map sheet 1669 Brüssow provided here were digitised in frame of the Geo3D-Oder project of the German Federal Institute for Geosciences and Natural Resources (BGR). The data include elements of the six horizon maps 1669-2, 1669-3, 1669-4, 1669-5, 1669-6 and 1669-7. The topics of these maps are defined in a general legend (version 3). Furthermore, the legends of the single horizon maps provide a stratigraphic and genetic classification of the depicted strata. For each horizon map the digitised elements comprise several polygon shapefiles of the single layers, a polyline shapefile of isohypses related to layer bases, a point shapefile of lithological profiles and a polygon shapefile of additional information concerning areas of heavy strata deformation and insufficient investigation. Non-numeric contents of the attribute tables are encoded by numbers and are translated in full text by means of key tables. The key table Normalprofil allows the stratigraphic and genetic classification of horizons displayed in horizon maps by code numbers of the column N_ID. Detailed descriptions concerning the data structure are provided in the attachments. Reference: Cepek, A. G. (1999): Die Lithofazieskarte Quartär 1 : 50.000 (LKQ 50) – Eine Erläuterung des Kartenkonzepts mit Hinweisen zum Gebrauch. - Brandenburgisch. Geowiss. Beitr. 6, 2: 3-38, 3 Abb., 2 Tab.; Kleinmachnow

The objective of this study is the production of an Alpine Permafrost Index Map (APIM) covering the entire European Alps. A unified statistical model that is based on Alpine-wide permafrost observations is used for debris and bedrock surfaces across the entire Alps. The explanatory variables of the model are mean annual air temperatures, potential incoming solar radiation and precipitation. Offset terms were applied to make model predictions for topographic and geomorphic conditions that differ from the terrain features used for model fitting. These offsets are based on literature review and involve some degree of subjective choice during model building. The assessment of the APIM is challenging because limited independent test data are available for comparison and these observations represent point information in a spatially highly variable topography. The APIM provides an index that describes the spatial distribution of permafrost and comes together with an interpretation key that helps to assess map uncertainties and to relate map contents to their actual expression in terrain. The map can be used as a first resource to estimate permafrost conditions at any given location in the European Alps in a variety of contexts such as research and spatial planning.Results show that Switzerland likely is the country with the largest permafrost area in the Alps, followed by Italy, Austria, France and Germany. Slovenia and Liechtenstein may have marginal permafrost areas. In all countries the permafrost area is expected to be larger than the glacier-covered area. The "zip"-file (available via the "Download dataset" link) contains the APIM and a surface cover map for the entire European Alps (43°-49° N, 4°-16° E), both spatially subdivided into twelve tiles. The legend for both maps is provided in a "pdf"-file (legend.pdf).The GIS-Layers are provided in the ".png" format, which supports RGB colors and transparency. For each "png"-file, a "world file" (".pgw") for geo-referencing the image is provided. The world file defines the spatial resolution, the rotation of the axes and the coordinates of the upper left pixel. The spatial reference for all tiles is Geographic coordinate system WGS1984 that is defined in the ".xml"-file. Depending on the GIS environment, the coordinate system has to be defined by the user manually in the project file of a GIS. The spatial arrangement of the tiles is described in a "pdf"-file (tiles.pdf).

Contained within 3rd Edition (1957) of the Atlas of Canada is a map that shows the division of Canada into climatic regions according to the classification of the climates of the world developed by W. Koppen. Koppen first divided the world into five major divisions to which he assigned the letters A, B, C, D, and E. The letters represent the range of divisions from tropical climate (A) to polar climate (E). There are no A climates in Canada. The descriptions of the four remaining major divisions are given in the map legend. Koppen then divided the large divisions into a number of climatic types in accordance with temperature differences and variations in the amounts and distribution of precipitation, on the basis of which he added certain letters to the initial letter denoting the major division. The definitions of the additional letters which apply in Canada are also given when they first appear in the map legend. Thus b is defined under Csb and the definition is, therefore, not repeated under Cfb, Dfb or Dsb. For this map, the temperature and precipitation criteria established by Koppen have been applied to Canadian data for a standard thirty year period (1921 to 1950 inclusive).

Various authors, working with different geobotanical traditions, have divided the Arctic into bioclimatic regions using a variety of terminologies. The origins of these different terms and approaches have been reviewed by the Panarctic Flora (PAF) initiative (Elvebakk 1999). The PAF and CAVM accepted a five-subzone version of the Russian zonal approach. The subzone boundaries are somewhat modified from the phytogeographic subzones of Yurtsev (1994). Subzone A is the coldest subzone whereas Subzone E is warmest. Warmer summer temperatures cause the size, horizontal cover, abundance, productivity and variety of plants to increase. In Alaska, woody plants occur as hemiprostrate dwarf shrubs (<15 cm tall) in Subzone C (mean July temperatures about 5-7 C, erect dwarf shrubs (<40 cm tall) in Subzone D (mean July temperature about 7-9 C), and low shrubs (40-200 cm tall) in Subzone E (mean July temperature about 9-12 C. At treeline, where the mean July temperatures are between 10 and 12 C, woody shrubs up to 2 meters tall are abundant. Back to Alaska Arctic Tundra Vegetation Map Go to Website Link:: Toolik Arctic Geobotanical Atlas below for details on legend units, photos of map units and plant species, glossary, bibliography and links to ground data. Map Themes AVHRR NDVI, Bioclimate Subzone, Elevation, False Color-Infrared, Floristic Province, Lake Cover, Landscape, Substrate Chemistry, Vegetation References Elvebakk, A. 1999. Bioclimate delimitation and subdivisions of the Arctic. Pages 81-112 in I. Nordal and V. Y. Razzhivin, editors. The Species Concept in the High North - A Panarctic Flora Initiative. The Norwegian Academy of Science and Letters, Oslo. Yurtsev, B. A. 1994. Floristic divisions of the Arctic. Journal of Vegetation Science 5:765-776.

The soil overview map 1:200,000 (BÜK200) is compiled by the Federal Institute for Geosciences and Natural Resources (BGR) in cooperation with the State Geological Services (SGD) of the federal states in the sheet section of the topographical overview map 1:200,000 (TÜK200) and published in 55 individual map sheets. The digital, non-cutting data storage forms a detailed, nationwide uniform and comprehensive information basis for cross-border statements on land use and soil protection. The BGR's website on the subject of soil provides information on the current processing status of the map book. The distribution and socialization of the soils in the area of this map sheet is described by means of 80 legend units (divided by soil regions and large soil landscapes). Each legend unit contains soil systematic information (soil subtype) and information on the soil source rock for both the guide soils and their companions. Includes sheet CC1542 Sassnitz and sheet CC2350 Ueckermünde. In the course of the processing of the BÜK200 neighbor sheet Neubrandenburg, the LBG data set of Stralsund at the southern edge of the sheet was changed in parts (as of 25 July 2007).

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

DescriptionThis is a vector tile layer built from the same data as the Jurisdictional Units Public feature service located here: https://nifc.maps.arcgis.com/home/item.html?id=4107b5d1debf4305ba00e929b7e5971a. This service can be used alone as a fast-drawing background layer, or used in combination with the feature service when Identify and Copy Feature capabilities are needed. At fine zoom levels, the feature service will be needed.OverviewThe Jurisdictional Units dataset outlines wildland fire jurisdictional boundaries for federal, state, and local government entities on a national scale and is used within multiple wildland fire systems including the Wildland Fire Decision Support System (WFDSS), the Interior Fuels and Post-Fire Reporting System (IFPRS), the Interagency Fuels Treatment Decision Support System (IFTDSS), the Interagency Fire Occurrence Reporting Modules (InFORM), the Interagency Reporting of Wildland Fire Information System (IRWIN), and the Wildland Computer-Aided Dispatch Enterprise System (WildCAD-E).In this dataset, agency and unit names are an indication of the primary manager’s name and unit name, respectively, recognizing that:There may be multiple owner names.Jurisdiction may be held jointly by agencies at different levels of government (ie State and Local), especially on private lands, Some owner names may be blocked for security reasons.Some jurisdictions may not allow the distribution of owner names. Private ownerships are shown in this layer with JurisdictionalUnitIID=null, JurisdictionalKind=null, and LandownerKind="Private", LandownerCategory="Private". All land inside the US country boundary is covered by a polygon.Jurisdiction for privately owned land varies widely depending on state, county, or local laws and ordinances, fire workload, and other factors, and is not available in a national dataset in most cases.For publicly held lands the agency name is the surface managing agency, such as Bureau of Land Management, United States Forest Service, etc. The unit name refers to the descriptive name of the polygon (i.e. Northern California District, Boise National Forest, etc.).AttributesField NameDefinitionGeometryIDPrimary key for linking geospatial objects with other database systems. Required for every feature. Not populated for Census Block Groups.JurisdictionalUnitIDWhere it could be determined, this is the NWCG Unit Identifier (Unit ID). Where it is unknown, the value is ‘Null’. Null Unit IDs can occur because a unit may not have a Unit ID, or because one could not be reliably determined from the source data. Not every land ownership has an NWCG Unit ID. Unit ID assignment rules are available in the Unit ID standard.JurisdictionalUnitID_sansUSNWCG Unit ID with the "US" characters removed from the beginning. Provided for backwards compatibility.JurisdictionalUnitNameThe name of the Jurisdictional Unit. Where an NWCG Unit ID exists for a polygon, this is the name used in the Name field from the NWCG Unit ID database. Where no NWCG Unit ID exists, this is the “Unit Name” or other specific, descriptive unit name field from the source dataset. A value is populated for all polygons except for Census Blocks Group and for PAD-US polygons that did not have an associated name.LocalNameLocal name for the polygon provided from agency authoritative data, PAD-US, or other source.JurisdictionalKindDescribes the type of unit jurisdiction using the NWCG Landowner Kind data standard. There are two valid values: Federal, Other, and Private. A value is not populated for Census Block Groups.JurisdictionalCategoryDescribes the type of unit jurisdiction using the NWCG Landowner Category data standard. Valid values include: BIA, BLM, BOR, DOD, DOE, NPS, USFS, USFWS, Foreign, Tribal, City, County, State, OtherLoc (other local, not in the standard), Private, and ANCSA. A value is not populated for Census Block Groups.LandownerKindThe landowner kind value associated with the polygon. May be inferred from jurisdictional agency, or by lack of a jurisdictional agency. Legal values align with the NWCG Landowner Kind data standard. A value is populated for all polygons.LandownerCategoryThe landowner category value associated with the polygon. May be inferred from jurisdictional agency, or by lack of a jurisdictional agency. Legal values align with the NWCG Landowner Category data standard. A value is populated for all polygons.LandownerDepartmentFederal department information that aligns with a unit’s landownerCategory information. Legal values include: Department of Agriculture, Department of Interior, Department of Defense, and Department of Energy. A value is not populated for all polygons.DataSourceThe database from which the polygon originated. An effort is made to be as specific as possible (i.e. identify the geodatabase name and feature class in which the polygon originated).SecondaryDataSourceIf the DataSource field is an aggregation from other sources, use this field to specify the source that supplied data to the aggregation. For example, if DataSource is "PAD-US 4.0", then for a TNC polygon, the SecondaryDataSource would be " TNC_PADUS2_0_SA2015_Public_gdb ".SourceUniqueIDIdentifier (GUID or ObjectID) in the data source. Used to trace the polygon back to its authoritative source.DataSourceYearYear that the source data for the polygon were acquired.MapMethodControlled vocabulary to define how the geospatial feature was derived. MapMethod will be Mixed Methods by default for this layer as the data are from mixed sources. Valid Values include: GPS-Driven; GPS-Flight; GPS-Walked; GPS-Walked/Driven; GPS-Unknown Travel Method; Hand Sketch; Digitized-Image; DigitizedTopo; Digitized-Other; Image Interpretation; Infrared Image; Modeled; Mixed Methods; Remote Sensing Derived; Survey/GCDB/Cadastral; Vector; Phone/Tablet; Other.DateCurrentThe last edit, update, of this GIS record. Date should follow the assigned NWCG Date Time data standard, using the 24-hour clock, YYYY-MM-DDhh.mm.ssZ, ISO8601 Standard.CommentsAdditional information describing the feature.JoinMethodAdditional information on how the polygon was matched to information in the NWCG Unit ID database.LegendJurisdictionalCategoryJurisdictionalCategory values grouped for more intuitive use in a map legend or summary table. Census Block Groups are classified as “No Unit”.LegendLandownerCategoryLandownerCategory values grouped for more intuitive use in a map legend or summary table.Other Relevant NWCG Definition StandardsUnitA generic term that represents an organizational entity that only has meaning when it is contextualized by a descriptor, e.g. jurisdictional.Definition Extension: When referring to an organizational entity, a unit refers to the smallest area or lowest level. Higher levels of an organization (region, agency, department, etc.) can be derived from a unit based on organization hierarchy.Unit, JurisdictionalThe governmental entity having overall land and resource management responsibility for a specific geographical area as provided by law.Definition Extension: 1) Ultimately responsible for the fire report to account for statistical fire occurrence; 2) Responsible for setting fire management objectives; 3) Jurisdiction cannot be re-assigned by agreement; 4) The nature and extent of the incident determines jurisdiction (for example, Wildfire vs. All Hazard); 5) Responsible for signing a Delegation of Authority to the Incident Commander.See also: Protecting Unit; LandownerData SourcesThis dataset is an aggregation of multiple spatial data sources: • Authoritative land ownership records from BIA, BLM, NPS, USFS, USFWS, and the Alaska Fire Service/State of Alaska• The Protected Areas Database US (PAD-US 4.0)• Census Block-Group Geometry BIA and Tribal Data:BIA and Tribal land management data were aggregated from BIA regional offices. These data date from 2012 and were reviewed/updated in 2024. Indian Trust Land affiliated with Tribes, Reservations, or BIA Agencies: These data are not considered the system of record and are not intended to be used as such. The Bureau of Indian Affairs (BIA), Branch of Wildland Fire Management (BWFM) is not the originator of these data. The spatial data coverage is a consolidation of the best available records/data received from each of the 12 BIA Regional Offices. The data are no better than the original sources from which they were derived. Care was taken when consolidating these files. However, BWFM cannot accept any responsibility for errors, omissions, or positional accuracy in the original digital data. The information contained in these data is dynamic and is continually changing. Updates to these data will be made whenever such data are received from a Regional Office. The BWFM gives no guarantee, expressed, written, or implied, regarding the accuracy, reliability, or completeness of these data.Alaska:The state of Alaska and Alaska Fire Service (BLM) co-manage a process to aggregate authoritative land ownership, management, and jurisdictional boundary data, based on Master Title Plats. Data ProcessingTo compile this dataset, the authoritative land ownership records and the PAD-US data mentioned above were crosswalked into the Jurisdictional Unit Polygon schema and aggregated through a series of python scripts and FME models. Once aggregated, steps were taken to reduce overlaps within the data. All overlap areas larger than 300 acres were manually examined and removed with the assistance of fire management SMEs. Once overlaps were removed, Census Block Group geometry were crosswalked to the Jurisdictional Unit Polygon schema and appended in areas in which no jurisdictional boundaries were recorded within the authoritative land ownership records and the PAD-US data. Census Block Group geometries represent areas of unknown Landowner Kind/Category and Jurisdictional Kind/Category and were assigned LandownerKind and LandownerCategory values of "Private".Update

Definition of symbols and acronyms.

The Lithofacial Map of the Quaternary 1 : 50,000 (LKQ 50) is a map series of the GDR covering nearly the whole former state territory besides the South of Saxony and Thuringia. The series consists of 123 map sheets, each of which encompassing several horizon maps mostly complemented by about five cross sections. Specifications concerning map content and structure provides Cepek (1999). The data of the LKQ 50 map sheet 1970/2070 Gorgast/Frankfurt (Oder) provided here were digitised in frame of the Geo3D-Oder project of the German Federal Institute for Geosciences and Natural Resources (BGR). This twin map sheet consists of the northern section of 1970 Gorgast and the southern section of 2070 Frankfurt (Oder). The data include elements of the four horizon maps 1970-2, 1970-3, 1970-4 and 1970-5, which combine both sheet sections. Additionally, there are two cross sections concerning sheet part 1970 Gorgast and five cross sections concerning sheet part 2070 Frankfurt (Oder). The topics of these maps and cross sections are defined in a general legend (version 3). Furthermore, the legends of the single horizon maps provide a stratigraphic and genetic classification of the depicted strata. For each horizon map the digitised elements comprise several polygon shapefiles of the single layers, a polyline shapefile of isohypses related to layer bases, a point shapefile of lithological profiles and a polygon shapefile of additional information concerning areas of heavy strata deformation and insufficient investigation. The data of each cross section includes a polygon shapefile of the horizon section areas, a polygon shapefile of the section areas concerning regions with heavy layer deformation or insufficient investigation and a shapefile showing the transect line to locate the cross section. Non-numeric contents of the attribute tables are encoded by numbers and are translated in full text by means of key tables. The key table Normalprofil allows the stratigraphic and genetic classification of horizons displayed in horizon maps by code numbers of the column N_ID. Detailed descriptions concerning the data structure are provided in the attachments. Reference: Cepek, A. G. (1999): Die Lithofazieskarte Quartär 1 : 50.000 (LKQ 50) – Eine Erläuterung des Kartenkonzepts mit Hinweisen zum Gebrauch. - Brandenburgisch. Geowiss. Beitr. 6, 2: 3-38, 3 Abb., 2 Tab.; Kleinmachnow