Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Abstract : The search for the most appropriate GIS data model to integrate, manipulate and analyse spatio-temporal data raises several research questions about the conceptualisation of geographic spaces. Although there is now a general consensus that many environmental phenomena require field and object conceptualisations to provide a comprehensive GIS representation, there is still a need for better integration of these dual representations of space within a formal spatio-temporal database. The research presented in this paper introduces a hybrid and formal dual data model for the representation of spatio-temporal data. The whole approach has been fully implemented in PostgreSQL and its spatial extension PostGIS, where the SQL language is extended by a series of data type constructions and manipulation functions to support hybrid queries. The potential of the approach is illustrated by an application to underwater geomorphological dynamics oriented towards the monitoring of the evolution of seabed changes. A series of performance and scalability experiments are also reported to demonstrate the computational performance of the model.Data Description : The data set used in our research is a set of bathymetric surveys recorded over three years from 2009 to 2011 as Digital Terrain Models (DTM) with 2m grid spacing. The first survey was carried out in February 2009 by the French hydrographic office, the second one was recorded on August-September 2010 and the third in July 2011, both by the “Institut Universitaire Européen de la Mer”.
The Geospatial Fabric is a dataset of spatial modeling units for use within the National Hydrologic Model that covers the conterminous United States (CONUS), Alaska, and most major river basins that flow in from Canada. This U.S. Geological Survey (USGS) data release consists of the geospatial fabric features and other related datasets created to expand the National Hydrologic Model to Hawaii. This page contains data and information related to the GIS features of the Geospaital Fabric for National Hydrologic Model, Hawaii domain. An Open Geospatial Consortium geopackage (GF_20.gpkg) contains 4 feature layers (layer names in parentheses): points of interest (poi), a stream network (nsegment), aggregated catchments (catchment), and hydrologic repsonse units (nhru). Features were derived from NHDPlus, version 2.0, and several hydroclimatic datasets representing domain-specific processes and key drainage basins within the Hawaii. All data cover the National Hydrologic Model's (NHM) Hawaiin domain. The NHM is a modeling infrastructure consisting of three main parts: 1) an underlying geospatial fabric of modeling units (hydrologic response units and stream segments) with an associated parameter database, 2) a model input data archive, and 3) a repository of the physical model simulation code bases (Regan and others, 2014). The pois represent hydro locations and points on the network. Segments are connected by the pois and are used to route streamflow and characterize upstream watershed conditions. The HRUs represent the spatial modeling units at which most of the physical processes (such as precipitation, runoff, evapotranspiration, and infiltration) are simulated. Some HRUs are connected to a corresponding segment, and may represent left and right-bank areas of each stream segment. See Regan and others (2018) and entities and attributes for more information.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The dataset and the validation are fully described in a Nature Scientific Data Descriptor https://www.nature.com/articles/s41597-019-0265-5
If you want to use this dataset in an interactive environment, then use this link https://mybinder.org/v2/gh/GeographerAtLarge/TravelTime/HEAD
The following text is a summary of the information in the above Data Descriptor.
The dataset is a suite of global travel-time accessibility indicators for the year 2015, at approximately one-kilometre spatial resolution for the entire globe. The indicators show an estimated (and validated), land-based travel time to the nearest city and nearest port for a range of city and port sizes.
The datasets are in GeoTIFF format and are suitable for use in Geographic Information Systems and statistical packages for mapping access to cities and ports and for spatial and statistical analysis of the inequalities in access by different segments of the population.
These maps represent a unique global representation of physical access to essential services offered by cities and ports.
The datasets travel_time_to_cities_x.tif (where x has values from 1 to 12) The value of each pixel is the estimated travel time in minutes to the nearest urban area in 2015. There are 12 data layers based on different sets of urban areas, defined by their population in year 2015 (see PDF report).
travel_time_to_ports_x (x ranges from 1 to 5)
The value of each pixel is the estimated travel time to the nearest port in 2015. There are 5 data layers based on different port sizes.
Format Raster Dataset, GeoTIFF, LZW compressed Unit Minutes
Data type Byte (16 bit Unsigned Integer)
No data value 65535
Flags None
Spatial resolution 30 arc seconds
Spatial extent
Upper left -180, 85
Lower left -180, -60 Upper right 180, 85 Lower right 180, -60 Spatial Reference System (SRS) EPSG:4326 - WGS84 - Geographic Coordinate System (lat/long)
Temporal resolution 2015
Temporal extent Updates may follow for future years, but these are dependent on the availability of updated inputs on travel times and city locations and populations.
Methodology Travel time to the nearest city or port was estimated using an accumulated cost function (accCost) in the gdistance R package (van Etten, 2018). This function requires two input datasets: (i) a set of locations to estimate travel time to and (ii) a transition matrix that represents the cost or time to travel across a surface.
The set of locations were based on populated urban areas in the 2016 version of the Joint Research Centre’s Global Human Settlement Layers (GHSL) datasets (Pesaresi and Freire, 2016) that represent low density (LDC) urban clusters and high density (HDC) urban areas (https://ghsl.jrc.ec.europa.eu/datasets.php). These urban areas were represented by points, spaced at 1km distance around the perimeter of each urban area.
Marine ports were extracted from the 26th edition of the World Port Index (NGA, 2017) which contains the location and physical characteristics of approximately 3,700 major ports and terminals. Ports are represented as single points
The transition matrix was based on the friction surface (https://map.ox.ac.uk/research-project/accessibility_to_cities) from the 2015 global accessibility map (Weiss et al, 2018).
Code The R code used to generate the 12 travel time maps is included in the zip file that can be downloaded with these data layers. The processing zones are also available.
Validation The underlying friction surface was validated by comparing travel times between 47,893 pairs of locations against journey times from a Google API. Our estimated journey times were generally shorter than those from the Google API. Across the tiles, the median journey time from our estimates was 88 minutes within an interquartile range of 48 to 143 minutes while the median journey time estimated by the Google API was 106 minutes within an interquartile range of 61 to 167 minutes. Across all tiles, the differences were skewed to the left and our travel time estimates were shorter than those reported by the Google API in 72% of the tiles. The median difference was −13.7 minutes within an interquartile range of −35.5 to 2.0 minutes while the absolute difference was 30 minutes or less for 60% of the tiles and 60 minutes or less for 80% of the tiles. The median percentage difference was −16.9% within an interquartile range of −30.6% to 2.7% while the absolute percentage difference was 20% or less in 43% of the tiles and 40% or less in 80% of the tiles.
This process and results are included in the validation zip file.
Usage Notes The accessibility layers can be visualised and analysed in many Geographic Information Systems or remote sensing software such as QGIS, GRASS, ENVI, ERDAS or ArcMap, and also by statistical and modelling packages such as R or MATLAB. They can also be used in cloud-based tools for geospatial analysis such as Google Earth Engine.
The nine layers represent travel times to human settlements of different population ranges. Two or more layers can be combined into one layer by recording the minimum pixel value across the layers. For example, a map of travel time to the nearest settlement of 5,000 to 50,000 people could be generated by taking the minimum of the three layers that represent the travel time to settlements with populations between 5,000 and 10,000, 10,000 and 20,000 and, 20,000 and 50,000 people.
The accessibility layers also permit user-defined hierarchies that go beyond computing the minimum pixel value across layers. A user-defined complete hierarchy can be generated when the union of all categories adds up to the global population, and the intersection of any two categories is empty. Everything else is up to the user in terms of logical consistency with the problem at hand.
The accessibility layers are relative measures of the ease of access from a given location to the nearest target. While the validation demonstrates that they do correspond to typical journey times, they cannot be taken to represent actual travel times. Errors in the friction surface will be accumulated as part of the accumulative cost function and it is likely that locations that are further away from targets will have greater a divergence from a plausible travel time than those that are closer to the targets. Care should be taken when referring to travel time to the larger cities when the locations of interest are extremely remote, although they will still be plausible representations of relative accessibility. Furthermore, a key assumption of the model is that all journeys will use the fastest mode of transport and take the shortest path.
This dataset represents a unique compiled environmental data set for the circumpolar Arctic ocean region 45N to 90N region. It consists of 170 layers (mostly marine, some terrestrial) in ArcGIS 10 format to be used with a Geographic Information System (GIS) and which are listed below in detail. Most layers are long-term average raster GRIDs for the summer season, often by ocean depth, and represent value-added products easy to use. The sources of the data are manifold such as the World Ocean Atlas 2009 (WOA09), International Bathimetric Chart of the Arctic Ocean (IBCAO), Canadian Earth System Model 2 (CanESM2) data (the newest generation of models available) and data sources such as plankton databases and OBIS. Ocean layers were modeled and predicted into the future and zooplankton species were modeled based on future data: Calanus hyperboreus (AphiaID104467), Metridia longa (AphiaID 104632), M. pacifica (AphiaID 196784) and Thysanoessa raschii (AphiaID 110711). Some layers are derived within ArcGIS. Layers have pixel sizes between 1215.819573 meters and 25257.72929 meters for the best pooled model, and between 224881.2644 and 672240.4095 meters for future climate data. Data was then reprojected into North Pole Stereographic projection in meters (WGS84 as the geographic datum). Also, future layers are included as a selected subset of proposed future climate layers from the Canadian CanESM2 for the next 100 years (scenario runs rcp26 and rcp85). The following layer groups are available: bathymetry (depth, derived slope and aspect); proximity layers (to,glaciers,sea ice, protected areas, wetlands, shelf edge); dissolved oxygen, apparent oxygen, percent oxygen, nitrogen, phosphate, salinity, silicate (all for August and for 9 depth classes); runoff (proximity, annual and August); sea surface temperature; waterbody temperature (12 depth classes); modeled ocean boundary layers (H1, H2, H3 and Wx).This dataset is used for a M.Sc. thesis by the author, and freely available upon request. For questions and details we suggest contacting the authors. Process_Description: Please contact Moritz Schmid for the thesis and detailed explanations. Short version: We model predicted here for the first time ocean layers in the Arctic Ocean based on a unique dataset of physical oceanography. Moreover, we developed presence/random absence models that indicate where the studied zooplankton species are most likely to be present in the Arctic Ocean. Apart from that, we develop the first spatially explicit models known to science that describe the depth in which the studied zooplankton species are most likely to be at, as well as their distribution of life stages. We do not only do this for one present day scenario. We modeled five different scenarios and for future climate data. First, we model predicted ocean layers using the most up to date data from various open access sources, referred here as best-pooled model data. We decided to model this set of stratification layers after discussions and input of expert knowledge by Professor Igor Polyakov from the International Arctic Research Center at the University of Alaska Fairbanks. We predicted those stratification layers because those are the boundaries and layers that the plankton has to cross for diel vertical migration and a change in those would most likely affect the migration. I assigned 4 variables to the stratification layers. H1, H2, H3 and Wx. H1 is the lower boundary of the mixed layer depth. Above this layer a lot of atmospheric disturbance is causing mixing of the water, giving the mixed layer its name. H2, the middle of the halocline is important because in this part of the ocean a strong gradient in salinity and temperature separates water layers. H3, the isotherm is important, because beneath it flows denser and colder Atlantic water. Wx summarizes the overall width of the described water column. Ocean layers were predicted using machine learning algorithms (TreeNet, Salford Systems). Second, ocean layers were included as predictors and used to predict the presence/random absence, most likely depth and life stage layers for the zooplankton species: Calanus hyperboreus, Metridia longa, Metridia pacifica and Thysanoessa raschii, This process was repeated for future predictions based on the CanESM2 data (see in the data section). For zooplankton species the following layers were developed and for the future. C. hyperboreus: Best-pooled model as well as future predictions (rcp26 including ocean layer(also excluding), rcp85 including oocean layers (also excluding) for 2010 and 2100.For parameters: Presence/random absence, most likely depth and life stage layers M. longa: Best-pooled model as well as future predictions (rcp26 including ocean layer(also excluding), rcp85 including oocean layers (also excluding) for 2010 and 2100. For parameters: Presence/rand... Visit https://dataone.org/datasets/f63d0f6c-7d53-46ce-b755-42a368007601 for complete metadata about this dataset.
Attribution-NonCommercial 4.0 (CC BY-NC 4.0)https://creativecommons.org/licenses/by-nc/4.0/
License information was derived automatically
Today, deep neural networks are widely used in many computer vision problems, also for geographic information systems (GIS) data. This type of data is commonly used for urban analyzes and spatial planning. We used orthophotographic images of two residential districts from Kielce, Poland for research including urban sprawl automatic analysis with Transformer-based neural network application.Orthophotomaps were obtained from Kielce GIS portal. Then, the map was manually masked into building and building surroundings classes. Finally, the ortophotomap and corresponding classification mask were simultaneously divided into small tiles. This approach is common in image data preprocessing for machine learning algorithms learning phase. Data contains two original orthophotomaps from Wietrznia and Pod Telegrafem residential districts with corresponding masks and also their tiled version, ready to provide as a training data for machine learning models.Transformed-based neural network has undergone a training process on the Wietrznia dataset, targeted for semantic segmentation of the tiles into buildings and surroundings classes. After that, inference of the models was used to test model's generalization ability on the Pod Telegrafem dataset. The efficiency of the model was satisfying, so it can be used in automatic semantic building segmentation. Then, the process of dividing the images can be reversed and complete classification mask retrieved. This mask can be used for area of the buildings calculations and urban sprawl monitoring, if the research would be repeated for GIS data from wider time horizon.Since the dataset was collected from Kielce GIS portal, as the part of the Polish Main Office of Geodesy and Cartography data resource, it may be used only for non-profit and non-commertial purposes, in private or scientific applications, under the law "Ustawa z dnia 4 lutego 1994 r. o prawie autorskim i prawach pokrewnych (Dz.U. z 2006 r. nr 90 poz 631 z późn. zm.)". There are no other legal or ethical considerations in reuse potential.Data information is presented below.wietrznia_2019.jpg - orthophotomap of Wietrznia districtmodel's - used for training, as an explanatory imagewietrznia_2019.png - classification mask of Wietrznia district - used for model's training, as a target imagewietrznia_2019_validation.jpg - one image from Wietrznia district - used for model's validation during training phasepod_telegrafem_2019.jpg - orthophotomap of Pod Telegrafem district - used for model's evaluation after training phasewietrznia_2019 - folder with wietrznia_2019.jpg (image) and wietrznia_2019.png (annotation) images, divided into 810 tiles (512 x 512 pixels each), tiles with no information were manually removed, so the training data would contain only informative tilestiles presented - used for the model during training (images and annotations for fitting the model to the data)wietrznia_2019_vaidation - folder with wietrznia_2019_validation.jpg image divided into 16 tiles (256 x 256 pixels each) - tiles were presented to the model during training (images for validation model's efficiency); it was not the part of the training datapod_telegrafem_2019 - folder with pod_telegrafem.jpg image divided into 196 tiles (256 x 265 pixels each) - tiles were presented to the model during inference (images for evaluation model's robustness)Dataset was created as described below.Firstly, the orthophotomaps were collected from Kielce Geoportal (https://gis.kielce.eu). Kielce Geoportal offers a .pst recent map from April 2019. It is an orthophotomap with a resolution of 5 x 5 pixels, constructed from a plane flight at 700 meters over ground height, taken with a camera for vertical photos. Downloading was done by WMS in open-source QGIS software (https://www.qgis.org), as a 1:500 scale map, then converted to a 1200 dpi PNG image.Secondly, the map from Wietrznia residential district was manually labelled, also in QGIS, in the same scope, as the orthophotomap. Annotation based on land cover map information was also obtained from Kielce Geoportal. There are two classes - residential building and surrounding. Second map, from Pod Telegrafem district was not annotated, since it was used in the testing phase and imitates situation, where there is no annotation for the new data presented to the model.Next, the images was converted to an RGB JPG images, and the annotation map was converted to 8-bit GRAY PNG image.Finally, Wietrznia data files were tiled to 512 x 512 pixels tiles, in Python PIL library. Tiles with no information or a relatively small amount of information (only white background or mostly white background) were manually removed. So, from the 29113 x 15938 pixels orthophotomap, only 810 tiles with corresponding annotations were left, ready to train the machine learning model for the semantic segmentation task. Pod Telegrafem orthophotomap was tiled with no manual removing, so from the 7168 x 7168 pixels ortophotomap were created 197 tiles with 256 x 256 pixels resolution. There was also image of one residential building, used for model's validation during training phase, it was not the part of the training data, but was a part of Wietrznia residential area. It was 2048 x 2048 pixel ortophotomap, tiled to 16 tiles 256 x 265 pixels each.
These geospatial data and their accompanying report outline many areas of coal in the United States beneath more than 3,000 ft of overburden. Based on depth, these areas may be targets for injection and storage of supercritical carbon dioxide. Additional areas where coal exists beneath more than 1,000 ft of overburden are also outlined; these may be targets for geologic storage of carbon dioxide in conjunction with enhanced coalbed methane production. These areas of deep coal were compiled as polygons into a shapefile for use in a geographic information system (GIS). The coal-bearing formation names, coal basin or field names, geographic provinces, coal ranks, coal geologic ages, and estimated individual coalbed thicknesses (if known) of the coal-bearing formations were included. An additional point shapefile, coal_co2_projects.shp, contains the locations of pilot projects for carbon dioxide injection into coalbeds. This report is not a comprehensive study of deep coal in the United States. Some areas of deep coal were excluded based on geologic or data-quality criteria, while others may be absent from the literature and still others may have been overlooked by the authors.
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
The Surface Management Agency (SMA) Geographic Information System (GIS) dataset depicts Federal land for the United States and classifies this land by its active Federal surface managing agency. The SMA feature class covers the continental United States, Alaska, Hawaii, Puerto Rico, Guam, American Samoa and the Virgin Islands. A Federal SMA agency refers to a Federal agency with administrative jurisdiction over the surface of Federal lands. Jurisdiction over the land is defined when the land is either: Withdrawn by some administrative or legislative action, or Acquired or Exchanged by a Federal Agency. This layer is a dynamic assembly of spatial data layers maintained at various federal and local government offices. The GIS data contained in this dataset represents the polygon features that show the boundaries for Surface Management Agency and the surface extent of each Federal agency’s surface administrative jurisdiction. SMA data depicts current withdrawn areas for a particular agency and (when appropriate) includes land that was acquired or exchanged and is located outside of a withdrawal area for that agency. The SMA data do not illustrate land status ownership pattern boundaries or contain land ownership attribute details. The SMA Withdrawals feature class covers the continental United States, Alaska, Hawaii, Puerto Rico, Guam, American Samoa and the Virgin Islands. A Federal SMA Withdrawal is defined by formal actions that set aside, withhold, or reserve Federal land by statute or administrative order for public purposes. A withdrawal creates a title encumbrance on the land. Withdrawals must accomplish one or more of the following: A. Transfer total or partial jurisdiction of Federal land between Federal agencies. B. Close (segregate) Federal land to operation of all or some of the public land laws and/or mineral laws. C. Dedicate Federal land to a specific public purpose. There are four major categories of formal withdrawals: (1) Administrative, (2) Presidential Proclamations, (3) Congressional, and (4) Federal Power Act (FPA) or Federal Energy Regulatory Commission (FERC) Withdrawals. These SMA Withdrawals will include the present total extent of withdrawn areas rather than all of the individual withdrawal actions that created them over time. A Federal SMA agency refers to a Federal agency with administrative jurisdiction over the surface of Federal lands. Jurisdiction over the land is defined when the land is either: Withdrawn by some administrative or legislative action, or Acquired or Exchanged by a Federal Agency. This layer is a dynamic assembly of spatial data layers maintained at various federal and local government offices. The GIS data contained in this dataset represents the polygon features that show the boundaries for Surface Management Agency and the surface extent of each Federal agency’s surface administrative jurisdiction. SMA data depicts current withdrawn areas for a particular agency and (when appropriate) includes land that was acquired or exchanged and is located outside of a withdrawal area for that agency. The SMA data do not illustrate land status ownership pattern boundaries or contain land ownership attribute details.
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:
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
This dataset is a compilation of county parcel data from Minnesota counties that have opted-in for their parcel data to be included in this dataset.
It includes the following 55 counties that have opted-in as of the publication date of this dataset: Aitkin, Anoka, Becker, Benton, Big Stone, Carlton, Carver, Cass, Chippewa, Chisago, Clay, Clearwater, Cook, Crow Wing, Dakota, Douglas, Fillmore, Grant, Hennepin, Houston, Isanti, Itasca, Jackson, Koochiching, Lac qui Parle, Lake, Lyon, Marshall, McLeod, Mille Lacs, Morrison, Mower, Murray, Norman, Olmsted, Otter Tail, Pennington, Pipestone, Polk, Pope, Ramsey, Renville, Rice, Saint Louis, Scott, Sherburne, Stearns, Stevens, Traverse, Waseca, Washington, Wilkin, Winona, Wright, and Yellow Medicine.
If you represent a county not included in this dataset and would like to opt-in, please contact Heather Albrecht (Heather.Albrecht@hennepin.us), co-chair of the Minnesota Geospatial Advisory Council (GAC)’s Parcels and Land Records Committee's Open Data Subcommittee. County parcel data does not need to be in the GAC parcel data standard to be included. MnGeo will map the county fields to the GAC standard.
County parcel data records have been assembled into a single dataset with a common coordinate system (UTM Zone 15) and common attribute schema. The county parcel data attributes have been mapped to the GAC parcel data standard for Minnesota: https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html
This compiled parcel dataset was created using Python code developed by Minnesota state agency GIS professionals, and represents a best effort to map individual county source file attributes into the common attribute schema of the GAC parcel data standard. The attributes from counties are mapped to the most appropriate destination column. In some cases, the county source files included attributes that were not mapped to the GAC standard. Additionally, some county attribute fields were parsed and mapped to multiple GAC standard fields, such as a single line address. Each quarter, MnGeo provides a text file to counties that shows how county fields are mapped to the GAC standard. Additionally, this text file shows the fields that are not mapped to the standard and those that are parsed. If a county shares changes to how their data should be mapped, MnGeo updates the compilation. If you represent a county and would like to update how MnGeo is mapping your county attribute fields to this compiled dataset, please contact us.
This dataset is a snapshot of parcel data, and the source date of the county data may vary. Users should consult County websites to see the most up-to-date and complete parcel data.
There have been recent changes in date/time fields, and their processing, introduced by our software vendor. In some cases, this has resulted in date fields being empty. We are aware of the issue and are working to correct it for future parcel data releases.
The State of Minnesota makes no representation or warranties, express or implied, with respect to the use or reuse of data provided herewith, regardless of its format or the means of its transmission. THE DATA IS PROVIDED “AS IS” WITH NO GUARANTEE OR REPRESENTATION ABOUT THE ACCURACY, CURRENCY, SUITABILITY, PERFORMANCE, MECHANTABILITY, RELIABILITY OR FITINESS OF THIS DATA FOR ANY PARTICULAR PURPOSE. This dataset is NOT suitable for accurate boundary determination. Contact a licensed land surveyor if you have questions about boundary determinations.
DOWNLOAD NOTES: This dataset is only provided in Esri File Geodatabase and OGC GeoPackage formats. A shapefile is not available because the size of the dataset exceeds the limit for that format. The distribution version of the fgdb is compressed to help reduce the data footprint. QGIS users should consider using the Geopackage format for better results.
Dataset representing vegetation mapping performed by the U.S. Forest Service for the South Coast region of California. This dataset, commonly referred to as CALVEG, provides comprehensive spatial and tabular data for existing vegetation. Map attributes consist of vegetation types using the CALVEG classification system and forest structural characteristics such as tree and shrub canopy cover and tree stem diameters. Two vegetation classifications are referenced within CALVEG, “vegetation alliances,” the most detailed classification thatemphasizes species composition, and “wildlife habitat relationships” (WHR), which emphasizes vegetation structure characteristics. CITY-OWNED DATAEvery reasonable effort has been made to assure the accuracy of the data provided; nevertheless, some information may not be accurate. The City of Los Angeles assumes no responsibility arising from use of this information. THE MAPS AND ASSOCIATED DATA ARE PROVIDED WITHOUT WARRANTY OF ANY KIND, either expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. INVASIVE PLANT DATAUse limitationsThe USDA Forest Service makes no warranty, expressed or implied, including the warranties of merchantability and fitness for a particular purpose, nor assumes any legal liability or responsibility for the accuracy, reliability, completeness or utility of these geospatial data, or for the improper or incorrect use of these geospatial data. These geospatial data and related maps or graphics are not legal documents and are not intended to be used as such. The data and maps may not be used to determine title, ownership, legal descriptions or boundaries, legal jurisdiction, or restrictions that may be in place on either public or private land. Natural hazards may or may not be depicted on the data and maps, and users should exercise due caution. The data are dynamic and may change over time. The user is responsible to verify the limitations of the geospatial data and to use the data accordingly.EXISTING VEGETATION DATAUse limitationsThis product is reproduced from geospatial information prepared by the U.S. Department of Agriculture, Forest Service. By removing the contents of this package or taking receipt of these files via electronic file transfer methods, you understand that the data stored on this media is in draft condition. Represented features may not be in an accurate geographic location. The Forest Service makes no expressed or implied warranty, including warranty of merchantability and fitness, with respect to the character, function, or capabilities of the data or their appropriateness for any user's purposes. The Forest Service reserves the right to correct, update, modify, or replace this geospatial information without notification. For more information, contact the Remote Sensing Lab, 916-640-1256.The Forest Service uses the most current and complete data available. GIS data and product accuracy may vary. They may be developed from sources of differing accuracy; accurate only at certain scales; based on modeling or interpretation; incomplete while being created or revised; etc. Using GIS products for purposes other than those for which they were created, may yield inaccurate or misleading results. The Forest Service reserves the right to correct, update, modify or replace GIS products without notification.TERM OF USECALVEG DATADisclaimer: The U.S. Department of Agriculture, Forest Service, has prepared this geospatial information. By taking receipt of these files via electronic file transfer methods, you understand that the data stored on this media is in draft condition. Represented features may not be in an accurate geographic location. The Forest Service makes no expressed or implied warranty, including warranty of merchantability and fitness, with respect to the character, function, or capabilities of the data or their appropriateness for any user's purposes. The Forest Service reserves the right to correct, update, modify, or replace this geospatial information without notification. For more information, contact the Regional Geospatial Data Manager, (707) 562-9106.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
PLSSQuarterSections_GCDB is the third level of a hierarchical breakdown of the Public Land Survey System Rectangular surveys. This data is Version 2.3 2020 of the Utah PLSS Fabric. This data set represents the GIS Version of the Public Land Survey System. Updates are expected annually as horizontal control positions from published sources and global positioning system (GPS) observations are added. The primary source for the data is cadastral survey records housed by the BLM supplemented with local records and geographic control coordinates from states, counties as well as other federal agencies such as the USGS and USFS. This data was originally published on 1/3/2017. This is no longer a standard and is now published as a Reference layer. This data is derived from the Second Division of the PLSS which includes quarter, quarter-quarter, sixteenth or government lot division of the PLSS.Updates were made to Quarter Sections in Utah County to add quarter sections to areas that were not broken down less than the Section level. They were added using information from points collected by county surveyors, that is in the data and extrapolating information from adjoining sections wherever possible. They are still areas that could not be interpreted well enough and they were left empty, beyond the section level.Quarter Sections were consolidated from the Quarter Quarter Sections to better represent the four quarters in all Aliquot Part areas. Areas with Lots or Special Surveys remain as is. Updated 4/8/2022
https://research.csiro.au/dap/licences/csiro-data-licence/https://research.csiro.au/dap/licences/csiro-data-licence/
This dataset is a series of digital map-posters accompanying the AdaptNRM Guide: Helping Biodiversity Adapt: supporting climate adaptation planning using a community-level modelling approach.
These represent supporting materials and information about the community-level biodiversity models applied to climate change. Map posters are organised by four biological groups (vascular plants, mammals, reptiles and amphibians), two climate change scenario (1990-2050 MIROC5 and CanESM2 for RCP8.5), and five measures of change in biodiversity.
The map-posters present the nationally consistent data at locally relevant resolutions in eight parts – representing broad groupings of NRM regions based on the cluster boundaries used for climate adaptation planning (http://www.environment.gov.au/climate-change/adaptation) and also Nationally.
Map-posters are provided in PNG image format at moderate resolution (300dpi) to suit A0 printing. The posters were designed to meet A0 print size and digital viewing resolution of map detail. An additional set in PDF image format has been created for ease of download for initial exploration and printing on A3 paper. Some text elements and map features may be fuzzy at this resolution.
Each map-poster contains four dataset images coloured using standard legends encompassing the potential range of the measure, even if that range is not represented in the dataset itself or across the map extent.
Most map series are provided in two parts: part 1 shows the two climate scenarios for vascular plants and mammals and part 2 shows reptiles and amphibians. Eight cluster maps for each series have a different colour theme and map extent. A national series is also provided. Annotation briefly outlines the topics presented in the Guide so that each poster stands alone for quick reference.
An additional 77 National maps presenting the probability distributions of each of 77 vegetation types – NVIS 4.1 major vegetation subgroups (NVIS subgroups) - are currently in preparation.
Example citations:
Williams KJ, Raisbeck-Brown N, Prober S, Harwood T (2015) Generalised projected distribution of vegetation types – NVIS 4.1 major vegetation subgroups (1990 and 2050), A0 map-poster 8.1 - East Coast NRM regions. CSIRO Land and Water Flagship, Canberra. Available online at www.AdaptNRM.org and https://data.csiro.au/dap/.
Williams KJ, Raisbeck-Brown N, Harwood T, Prober S (2015) Revegetation benefit (cleared natural areas) for vascular plants and mammals (1990-2050), A0 map-poster 9.1 - East Coast NRM regions. CSIRO Land and Water Flagship, Canberra. Available online at www.AdaptNRM.org and https://data.csiro.au/dap/.
This dataset has been delivered incrementally. Please check that you are accessing the latest version of the dataset. Lineage: The map posters show case the scientific data. The data layers have been developed at approximately 250m resolution (9 second) across the Australian continent to incorporate the interaction between climate and topography, and are best viewed using a geographic information system (GIS). Each data layers is 1Gb, and inaccessible to non-GIS users. The map posters provide easy access to the scientific data, enabling the outputs to be viewed at high resolution with geographical context information provided.
Maps were generated using layout and drawing tools in ArcGIS 10.2.2
A check list of map posters and datasets is provided with the collection.
Map Series: 7.(1-77) National probability distribution of vegetation type – NVIS 4.1 major vegetation subgroup pre-1750 #0x
8.1 Generalised projected distribution of vegetation types (NVIS subgroups) (1990 and 2050)
9.1 Revegetation benefit (cleared natural areas) for plants and mammals (1990-2050)
9.2 Revegetation benefit (cleared natural areas) for reptiles and amphibians (1990-2050)
10.1 Need for assisted dispersal for vascular plants and mammals (1990-2050)
10.2 Need for assisted dispersal for reptiles and amphibians (1990-2050)
11.1 Refugial potential for vascular plants and mammals (1990-2050)
11.1 Refugial potential for reptiles and amphibians (1990-2050)
12.1 Climate-driven future revegetation benefit for vascular plants and mammals (1990-2050)
12.2 Climate-driven future revegetation benefit for vascular reptiles and amphibians (1990-2050)
Jurisdictional Unit, 2022-05-21. For use with WFDSS, IFTDSS, IRWIN, and InFORM.This is a feature service which provides Identify and Copy Feature capabilities. If fast-drawing at coarse zoom levels is a requirement, consider using the tile (map) service layer located at https://nifc.maps.arcgis.com/home/item.html?id=3b2c5daad00742cd9f9b676c09d03d13.OverviewThe Jurisdictional Agencies dataset is developed as a national land management geospatial layer, focused on representing wildland fire jurisdictional responsibility, for interagency wildland fire applications, including WFDSS (Wildland Fire Decision Support System), IFTDSS (Interagency Fuels Treatment Decision Support System), IRWIN (Interagency Reporting of Wildland Fire Information), and InFORM (Interagency Fire Occurrence Reporting Modules). It is intended to provide federal wildland fire jurisdictional boundaries on a national scale. The agency and unit names are an indication of the primary manager 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 JurisdictionalUnitIdentifier=null,JurisdictionalUnitAgency=null, JurisdictionalUnitKind=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.).These data are used to automatically populate fields on the WFDSS Incident Information page.This data layer implements the NWCG Jurisdictional Unit Polygon Geospatial Data Layer Standard.Relevant NWCG Definitions and StandardsUnit2. A 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: Unit, Protecting; LandownerUnit IdentifierThis data standard specifies the standard format and rules for Unit Identifier, a code used within the wildland fire community to uniquely identify a particular government organizational unit.Landowner Kind & CategoryThis data standard provides a two-tier classification (kind and category) of landownership. Attribute Fields JurisdictionalAgencyKind Describes the type of unit Jurisdiction using the NWCG Landowner Kind data standard. There are two valid values: Federal, and Other. A value may not be populated for all polygons.JurisdictionalAgencyCategoryDescribes the type of unit Jurisdiction using the NWCG Landowner Category data standard. Valid values include: ANCSA, BIA, BLM, BOR, DOD, DOE, NPS, USFS, USFWS, Foreign, Tribal, City, County, OtherLoc (other local, not in the standard), State. A value may not be populated for all polygons.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.JurisdictionalUnitIDWhere it could be determined, this is the NWCG Standard 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 from the Unit ID standard, linked above.LandownerKindThe landowner category value associated with the polygon. May be inferred from jurisdictional agency, or by lack of a jurisdictional agency. A value is populated for all polygons. There are three valid values: Federal, Private, or Other.LandownerCategoryThe landowner kind value associated with the polygon. May be inferred from jurisdictional agency, or by lack of a jurisdictional agency. A value is populated for all polygons. Valid values include: ANCSA, BIA, BLM, BOR, DOD, DOE, NPS, USFS, USFWS, Foreign, Tribal, City, County, OtherLoc (other local, not in the standard), State, Private.DataSourceThe database from which the polygon originated. Be as specific as possible, identify the geodatabase name and feature class in which the polygon originated.SecondaryDataSourceIf the Data Source is an aggregation from other sources, use this field to specify the source that supplied data to the aggregation. For example, if Data Source is "PAD-US 2.1", then for a USDA Forest Service polygon, the Secondary Data Source would be "USDA FS Automated Lands Program (ALP)". For a BLM polygon in the same dataset, Secondary Source would be "Surface Management Agency (SMA)."SourceUniqueIDIdentifier (GUID or ObjectID) in the data source. Used to trace the polygon back to its authoritative source.MapMethod:Controlled vocabulary to define how the geospatial feature was derived. Map method may help define data quality. MapMethod will be Mixed Method 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; OtherDateCurrentThe last edit, update, of this GIS record. Date should follow the assigned NWCG Date Time data standard, using 24 hour clock, YYYY-MM-DDhh.mm.ssZ, ISO8601 Standard.CommentsAdditional information describing the feature. GeometryIDPrimary key for linking geospatial objects with other database systems. Required for every feature. This field may be renamed for each standard to fit the feature.JurisdictionalUnitID_sansUSNWCG Unit ID with the "US" characters removed from the beginning. Provided for backwards compatibility.JoinMethodAdditional information on how the polygon was matched information in the NWCG Unit ID database.LocalNameLocalName for the polygon provided from PADUS or other source.LegendJurisdictionalAgencyJurisdictional Agency but smaller landholding agencies, or agencies of indeterminate status are grouped for more intuitive use in a map legend or summary table.LegendLandownerAgencyLandowner Agency but smaller landholding agencies, or agencies of indeterminate status are grouped for more intuitive use in a map legend or summary table.DataSourceYearYear that the source data for the polygon were acquired.Data InputThis dataset is based on an aggregation of 4 spatial data sources: Protected Areas Database US (PAD-US 2.1), data from Bureau of Indian Affairs regional offices, the BLM Alaska Fire Service/State of Alaska, and Census Block-Group Geometry. NWCG Unit ID and Agency Kind/Category data are tabular and sourced from UnitIDActive.txt, in the WFMI Unit ID application (https://wfmi.nifc.gov/unit_id/Publish.html). Areas of with unknown Landowner Kind/Category and Jurisdictional Agency Kind/Category are assigned LandownerKind and LandownerCategory values of "Private" by use of the non-water polygons from the Census Block-Group geometry.PAD-US 2.1:This dataset is based in large part on the USGS Protected Areas Database of the United States - PAD-US 2.`. PAD-US is a compilation of authoritative protected areas data between agencies and organizations that ultimately results in a comprehensive and accurate inventory of protected areas for the United States to meet a variety of needs (e.g. conservation, recreation, public health, transportation, energy siting, ecological, or watershed assessments and planning). Extensive documentation on PAD-US processes and data sources is available.How these data were aggregated:Boundaries, and their descriptors, available in spatial databases (i.e. shapefiles or geodatabase feature classes) from land management agencies are the desired and primary data sources in PAD-US. If these authoritative sources are unavailable, or the agency recommends another source, data may be incorporated by other aggregators such as non-governmental organizations. Data sources are tracked for each record in the PAD-US geodatabase (see below).BIA and Tribal Data:BIA and Tribal land management data are not available in PAD-US. As such, data were aggregated from BIA regional offices. These data date from 2012 and were substantially updated in 2022. 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
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Download .zipThis data set represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular surveys. The metadata describes the lineage, sources and production methods for the data content. The definitions and structure of this data is compliant with FGDC Cadastral Data Content Standards and Guidelines for publication. This coverage was originally created for the accurate location of the oil and gas wells in the state of Ohio. The original data set was developed as an ArcInfo coverage containing the original land subdivision boundaries for Ohio. Ohio has had a long and varied history of its land subdivisions that has led to the use of several subdivision strategies being applied. In general, these different schemes are composed of the Public Land Surveying System (PLSS) subdivisions and the irregular land subdivisions. The PLSS subdivisions contain townships, ranges, and sections. They are found in the following major land subdivisions: Old Seven Ranges, Between the Miamis (parts of which are known as the Symmes Purchase), Congress Lands East of Scioto River, Congress Lands North of Old Seven Ranges, Congress Lands West of Miami River, North and East of the First Principal Meridian, South and East of the First Principal Meridian, and the Michigan Meridian Survey. The irregular subdivisions include the Virginia Military District, the Ohio Company Purchase, the U.S. Military District, the Connecticut Western Reserve, the Twelve-Mile Square Reservation, the Two-Mile Square Reservation, the Refugee Lands, the French Grants, and the Donation Tract. This data set represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular surveys. The primary source for the data is local records and geographic control coordinates from states, counties as well as federal agencies such as the BLM, USGS and USFS. The data has been converted from source documents to digital form and transferred into a GIS format that is compliant with FGDC Cadastral Data Content Standards and Guidelines for publication. This data is optimized for data publication and sharing rather than for specific "production" or operation and maintenance. This data set includes the following: PLSS Fully Intersected (all of the PLSS feature at the atomic or smallest polygon level), PLSS Townships, First Divisions and Second Divisions (the hierarchical break down of the PLSS Rectangular surveys) PLSS Special surveys (non rectangular components of the PLSS) Meandered Water, Corners and Conflicted Areas (known areas of gaps or overlaps between Townships or state boundaries). The Entity-Attribute section of this metadata describes these components in greater detail.This data set is optimized for data publication and sharing rather than for specific "production" or operation and maintenance. This data set includes the following: PLSS Fully Intersected (all of the PLSS feature at the atomic or smallest polygon level), PLSS Townships, First Divisions and Second Divisions (the hierarchical break down of the PLSS Rectangular surveys) PLSS Special surveys (non rectangular components of the PLSS) Meandered Water, Corners and Conflicted Areas (known areas of gaps or overlaps between Townships or state boundaries). The Entity-Attribute section of this metadata describes these components in greater detail.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesOffice of Information TechnologyGIS Records2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov
Attribution 3.0 (CC BY 3.0)https://creativecommons.org/licenses/by/3.0/
License information was derived automatically
Heard Island and McDonald Islands, vegetation layer.
This is a polygon dataset stored in the Geographical Information System (GIS).
The data represents approximately the areas of vegetation cover on these islands.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Last Update: 08/29/2024The statewide roads dataset is a multi-purpose statewide roads dataset for cartography and range based-address location. This dataset is also used as the base geometry for deriving the GIS-representation of UDOT's highway linear referencing system (LRS). A network analysis dataset for route-finding can also be derived from this dataset. This dataset utilizes a data model based on Next-Generation 911 standards and the Federal Highway Administration's All Roads Network Of Linear-referenced Data (ARNOLD) reporting requirements for state DOTs. UGRC adopted this data model on September 13th, 2017.The statewide roads dataset is maintained by UGRC in partnership with local governments, the Utah 911 Committee, and UDOT. This dataset is updated monthly with Davis, Salt Lake, Utah, Washington and Weber represented every month, along with additional counties based on an annual update schedule. UGRC obtains the data from the authoritative data source (typically county agencies), projects the data and attributes into the current data model, spatially assigns polygon-based fields based on the appropriate SGID boundary, and then standardizes the attribute values to ensure statewide consistency. UGRC also generates a UNIQUE_ID field based on the segment's location in the US National Grid, with the street name then tacked on. The UNIQUE_ID field is static and is UGRC's current, ad hoc solution to a persistent global id. More information about the data model can be found here: https://docs.google.com/spreadsheets/d/1jQ_JuRIEtzxj60F0FAGmdu5JrFpfYBbSt3YzzCjxpfI/edit#gid=811360546 More information about the data model transition can be found here: https://gis.utah.gov/major-updates-coming-to-roads-data-model/We are currently working with US Forest Service to improve the Forest Service roads in this dataset, however, for the most up-to-date and complete set of USFS roads, please visit their data portal where you can download the "National Forest System Roads" dataset.More information can be found on the UGRC data page for this layer:https://gis.utah.gov/data/transportation/roads-system/
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Last Update: 02/04/2025The statewide roads dataset is a multi-purpose statewide roads dataset for cartography and range based-address location. This dataset is also used as the base geometry for deriving the GIS-representation of UDOT's highway linear referencing system (LRS). A network analysis dataset for route-finding can also be derived from this dataset. This dataset utilizes a data model based on Next-Generation 911 standards and the Federal Highway Administration's All Roads Network Of Linear-referenced Data (ARNOLD) reporting requirements for state DOTs. UGRC adopted this data model on September 13th, 2017.The statewide roads dataset is maintained by UGRC in partnership with local governments, the Utah 911 Committee, and UDOT. This dataset is updated monthly with Davis, Salt Lake, Utah, Washington and Weber represented every month, along with additional counties based on an annual update schedule. UGRC obtains the data from the authoritative data source (typically county agencies), projects the data and attributes into the current data model, spatially assigns polygon-based fields based on the appropriate SGID boundary, and then standardizes the attribute values to ensure statewide consistency. UGRC also generates a UNIQUE_ID field based on the segment's location in the US National Grid, with the street name then tacked on. The UNIQUE_ID field is static and is UGRC's current, ad hoc solution to a persistent global id. More information about the data model can be found here: https://docs.google.com/spreadsheets/d/1jQ_JuRIEtzxj60F0FAGmdu5JrFpfYBbSt3YzzCjxpfI/edit#gid=811360546 More information about the data model transition can be found here: https://gis.utah.gov/major-updates-coming-to-roads-data-model/We are currently working with US Forest Service to improve the Forest Service roads in this dataset, however, for the most up-to-date and complete set of USFS roads, please visit their data portal where you can download the "National Forest System Roads" dataset.More information can be found on the UGRC data page for this layer:https://gis.utah.gov/data/transportation/roads-system/
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This data-set is a supplementary material related to the generation of synthetic images of a corridor in the University of Melbourne, Australia from a building information model (BIM). This data-set was generated to check the ability of deep learning algorithms to learn task of indoor localisation from synthetic images, when being tested on real images. =============================================================================The following is the name convention used for the data-sets. The brackets show the number of images in the data-set.REAL DATAReal
---------------------> Real images (949 images)
Gradmag-Real -------> Gradmag of real data
(949 images)SYNTHETIC DATASyn-Car
----------------> Cartoonish images (2500 images)
Syn-pho-real ----------> Synthetic photo-realistic images (2500 images)
Syn-pho-real-tex -----> Synthetic photo-realistic textured (2500 images)
Syn-Edge --------------> Edge render images (2500 images)
Gradmag-Syn-Car ---> Gradmag of Cartoonish images (2500 images)=============================================================================Each folder contains the images and their respective groundtruth poses in the following format [ImageName X Y Z w p q r].To generate the synthetic data-set, we define a trajectory in the 3D indoor model. The points in the trajectory serve as the ground truth poses of the synthetic images. The height of the trajectory was kept in the range of 1.5–1.8 m from the floor, which is the usual height of holding a camera in hand. Artificial point light sources were placed to illuminate the corridor (except for Edge render images). The length of the trajectory was approximately 30 m. A virtual camera was moved along the trajectory to render four different sets of synthetic images in Blender*. The intrinsic parameters of the virtual camera were kept identical to the real camera (VGA resolution, focal length of 3.5 mm, no distortion modeled). We have rendered images along the trajectory at 0.05 m interval and ± 10° tilt.The main difference between the cartoonish (Syn-car) and photo-realistic images (Syn-pho-real) is the model of rendering. Photo-realistic rendering is a physics-based model that traces the path of light rays in the scene, which is similar to the real world, whereas the cartoonish rendering roughly traces the path of light rays. The photorealistic textured images (Syn-pho-real-tex) were rendered by adding repeating synthetic textures to the 3D indoor model, such as the textures of brick, carpet and wooden ceiling. The realism of the photo-realistic rendering comes at the cost of rendering times. However, the rendering times of the photo-realistic data-sets were considerably reduced with the help of a GPU. Note that the naming convention used for the data-sets (e.g. Cartoonish) is according to Blender terminology.An additional data-set (Gradmag-Syn-car) was derived from the cartoonish images by taking the edge gradient magnitude of the images and suppressing weak edges below a threshold. The edge rendered images (Syn-edge) were generated by rendering only the edges of the 3D indoor model, without taking into account the lighting conditions. This data-set is similar to the Gradmag-Syn-car data-set, however, does not contain the effect of illumination of the scene, such as reflections and shadows.*Blender is an open-source 3D computer graphics software and finds its applications in video games, animated films, simulation and visual art. For more information please visit: http://www.blender.orgPlease cite the papers if you use the data-set:1) Acharya, D., Khoshelham, K., and Winter, S., 2019. BIM-PoseNet: Indoor camera localisation using a 3D indoor model and deep learning from synthetic images. ISPRS Journal of Photogrammetry and Remote Sensing. 150: 245-258.2) Acharya, D., Singha Roy, S., Khoshelham, K. and Winter, S. 2019. Modelling uncertainty of single image indoor localisation using a 3D model and deep learning. In ISPRS Annals of Photogrammetry, Remote Sensing & Spatial Information Sciences, IV-2/W5, pages 247-254.
The purpose of the American Indian and Alaska Native Land Area Representation (AIAN-LAR) Geographic Information System (GIS) dataset is to depict the external extent of federal Indian reservations and the external extent of associated land held in “trust” by the United States, “restricted fee” or “mixed ownership” status for federally recognized tribes and individual Indians. This dataset includes other land area types such as Public Domain Allotments, Dependent Indian Communities and Homesteads. This GIS Dataset is prepared strictly for illustrative and reference purposes only and should not be used, and is not intended for legal, survey, engineering or navigation purposes.No warranty is made by the Bureau of Indian Affairs (BIA) for the use of the data for purposes not intended by the BIA. This GIS Dataset may contain errors. There is no impact on the legal status of the land areas depicted herein and no impact on land ownership. No legal inference can or should be made from the information in this GIS Dataset. The GIS Dataset is to be used solely for illustrative, reference and statistical purposes and may be used for government to government Tribal consultation. Reservation boundary data is limited in authority to those areas where there has been settled Congressional definition or final judicial interpretation of the boundary. Absent settled Congressional definition or final judicial interpretation of a reservation boundary, the BIA recommends consultation with the appropriate Tribe and then the BIA to obtain interpretations of the reservation boundary.The land areas and their representations are compilations defined by the official land title records of the Bureau of Indian Affairs (BIA) which include treaties, statutes, Acts of Congress, agreements, executive orders, proclamations, deeds and other land title documents. The trust, restricted, and mixed ownership land area shown here, are suitable only for general spatial reference and do not represent the federal government’s position on the jurisdictional status of Indian country. Ownership and jurisdictional status is subject to change and must be verified with plat books, patents, and deeds in the appropriate federal and state offices.Included in this dataset are the exterior extent of off reservation trust, restricted fee tracts and mixed tracts of land including Public Domain allotments, Dependent Indian Communities, Homesteads and government administered lands and those set aside for schools and dormitories. There are also land areas where there is more than one tribe having an interest in or authority over a tract of land but this information is not specified in the AIAN-LAR dataset. The dataset includes both surface and subsurface tracts of land (tribal and individually held) “off reservation” tracts and not simply off reservation “allotments” as land has in many cases been subsequently acquired in trust.These data are public information and may be used by various organizations, agencies, units of government (i.e., Federal, state, county, and city), and other entities according to the restrictions on appropriate use. It is strongly recommended that these data be acquired directly from the BIA and not indirectly through some other source, which may have altered or integrated the data for another purpose for which they may not have been intended. Integrating land areas into another dataset and attempting to resolve boundary differences between other entities may produce inaccurate results. It is also strongly recommended that careful attention be paid to the content of the metadata file associated with these data. Users are cautioned that digital enlargement of these data to scales greater than those at which they were originally mapped can cause misinterpretation.The BIA AIAN-LAR dataset’s spatial accuracy and attribute information are continuously being updated, improved and is used as the single authoritative land area boundary data for the BIA mission. These data are available through the Bureau of Indian Affairs, Office of Trust Services, Division of Land Titles and Records, Branch of Geospatial Support.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The Open Government Data portals (OGD) thanks to the presence of thousands of geo-referenced datasets, containing spatial information, are of extreme interest for any analysis or process relating to the territory. For this to happen, users must be enabled to access these datasets and reuse them. An element often considered hindering the full dissemination of OGD data is the quality of their metadata. Starting from an experimental investigation conducted on over 160,000 geospatial datasets belonging to six national and international OGD portals, this work has as its first objective to provide an overview of the usage of these portals measured in terms of datasets views and downloads. Furthermore, to assess the possible influence of the quality of the metadata on the use of geospatial datasets, an assessment of the metadata for each dataset was carried out, and the correlation between these two variables was measured. The results obtained showed a significant underutilization of geospatial datasets and a generally poor quality of their metadata. Besides, a weak correlation was found between the use and quality of the metadata, not such as to assert with certainty that the latter is a determining factor of the former.
The dataset consists of six zipped CSV files, containing the collected datasets' usage data, full metadata, and computed quality values, for about 160,000 geospatial datasets belonging to the three national and three international portals considered in the study, i.e. US (catalog.data.gov), Colombia (datos.gov.co), Ireland (data.gov.ie), HDX (data.humdata.org), EUODP (data.europa.eu), and NASA (data.nasa.gov).
Data collection occurred in the period: 2019-12-19 -- 2019-12-23.
The header for each CSV file is:
[ ,portalid,id,downloaddate,metadata,overallq,qvalues,assessdate,dviews,downloads,engine,admindomain]
where for each row (a portal's dataset) the following fields are defined as follows:
[1] Neumaier, S.; Umbrich, J.; Polleres, A. Automated Quality Assessment of Metadata Across Open Data Portals.J. Data and Information Quality2016,8, 2:1–2:29. doi:10.1145/2964909
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Abstract : The search for the most appropriate GIS data model to integrate, manipulate and analyse spatio-temporal data raises several research questions about the conceptualisation of geographic spaces. Although there is now a general consensus that many environmental phenomena require field and object conceptualisations to provide a comprehensive GIS representation, there is still a need for better integration of these dual representations of space within a formal spatio-temporal database. The research presented in this paper introduces a hybrid and formal dual data model for the representation of spatio-temporal data. The whole approach has been fully implemented in PostgreSQL and its spatial extension PostGIS, where the SQL language is extended by a series of data type constructions and manipulation functions to support hybrid queries. The potential of the approach is illustrated by an application to underwater geomorphological dynamics oriented towards the monitoring of the evolution of seabed changes. A series of performance and scalability experiments are also reported to demonstrate the computational performance of the model.Data Description : The data set used in our research is a set of bathymetric surveys recorded over three years from 2009 to 2011 as Digital Terrain Models (DTM) with 2m grid spacing. The first survey was carried out in February 2009 by the French hydrographic office, the second one was recorded on August-September 2010 and the third in July 2011, both by the “Institut Universitaire Européen de la Mer”.