We proposed a new methodology for reducing multiple types of rasterization errors to simultaneously preserve the spatial properties of area, shape, and topology in polygon-to-raster conversion. By reassigning cells of the rasterized outcome, the method first compensates for the loss in shape properties. Topological changes are then corrected by comparing the topological relations of raster regions and their corresponding polygons. Finally, the areas between pairs of neighboring regions are coordinated to maintain area properties.

Geographic Information System (GIS) analyses are an essential part of natural resource management and research. Calculating and summarizing data within intersecting GIS layers is common practice for analysts and researchers. However, the various tools and steps required to complete this process are slow and tedious, requiring many tools iterating over hundreds, or even thousands of datasets. USGS scientists will combine a series of ArcGIS geoprocessing capabilities with custom scripts to create tools that will calculate, summarize, and organize large amounts of data that can span many temporal and spatial scales with minimal user input. The tools work with polygons, lines, points, and rasters to calculate relevant summary data and combine them into a single output table that can be easily incorporated into statistical analyses. These tools are useful for anyone interested in using an automated script to quickly compile summary information within all areas of interest in a GIS dataset

A clip of impervious surfaces to only include what is within the Yukon River Drainage. Original data was pulled from the impervious surface index, and was clipped to the extent of the drainage, then converted from a raster to polygon.

This packaged data collection contains all of the outputs from our primary model, including the following data layers: Habitat Cores (vector polygons) Least-cost Paths (vector lines) Least-cost Corridors (raster) Least-cost Corridors (vector polygon interpretation) Modeling Extent (vector polygon) Please refer to the embedded spatial metadata and the information in our full report for details on the development of these data layers. Packaged data are available in two formats: Geodatabase (.gdb): A related set of file geodatabase rasters and feature classes, packaged in an ESRI file geodatabase. ArcGIS Pro Map Package (.mpkx): The same data included in the geodatabase, presented as fully-symbolized layers in a map. Note that you must have ArcGIS Pro version 2.0 or greater to view. See Cross-References for links to individual datasets, which can be downloaded in shapefile (.shp) or raster GeoTIFF (.tif) formats.

Reason for SelectionProtected natural areas in urban environments provide urban residents a nearby place to connect with nature and offer refugia for some species. They help foster a conservation ethic by providing opportunities for people to connect with nature, and also support ecosystem services like offsetting heat island effects (Greene and Millward 2017, Simpson 1998), water filtration, stormwater retention, and more (Hoover and Hopton 2019). In addition, parks, greenspace, and greenways can help improve physical and psychological health in communities (Gies 2006). Urban park size complements the equitable access to potential parks indicator by capturing the value of existing parks.Input DataSoutheast Blueprint 2024 extentFWS National Realty Tracts, accessed 12-13-2023Protected Areas Database of the United States(PAD-US):PAD-US 3.0national geodatabase -Combined Proclamation Marine Fee Designation Easement, accessed 12-6-20232020 Census Urban Areas from the Census Bureau’s urban-rural classification; download the data, read more about how urban areas were redefined following the 2020 censusOpenStreetMap data “multipolygons” layer, accessed 12-5-2023A polygon from this dataset is considered a beach if the value in the “natural” tag attribute is “beach”. Data for coastal states (VA, NC, SC, GA, FL, AL, MS, LA, TX) were downloaded in .pbf format and translated to an ESRI shapefile using R code. OpenStreetMap® is open data, licensed under theOpen Data Commons Open Database License (ODbL) by theOpenStreetMap Foundation (OSMF). Additional credit to OSM contributors. Read more onthe OSM copyright page.2021 National Land Cover Database (NLCD): Percentdevelopedimperviousness2023NOAA coastal relief model: volumes 2 (Southeast Atlantic), 3 (Florida and East Gulf of America), 4 (Central Gulf of America), and 5 (Western Gulf of America), accessed 3-27-2024Mapping StepsCreate a seamless vector layer to constrain the extent of the urban park size indicator to inland and nearshore marine areas <10 m in depth. The deep offshore areas of marine parks do not meet the intent of this indicator to capture nearby opportunities for urban residents to connect with nature. Shallow areas are more accessible for recreational activities like snorkeling, which typically has a maximum recommended depth of 12-15 meters. This step mirrors the approach taken in the Caribbean version of this indicator.Merge all coastal relief model rasters (.nc format) together using QGIS “create virtual raster”.Save merged raster to .tif and import into ArcPro.Reclassify the NOAA coastal relief model data to assign areas with an elevation of land to -10 m a value of 1. Assign all other areas (deep marine) a value of 0.Convert the raster produced above to vector using the “RasterToPolygon” tool.Clip to 2024 subregions using “Pairwise Clip” tool.Break apart multipart polygons using “Multipart to single parts” tool.Hand-edit to remove deep marine polygon.Dissolve the resulting data layer.This produces a seamless polygon defining land and shallow marine areas.Clip the Census urban area layer to the bounding box of NoData surrounding the extent of Southeast Blueprint 2024.Clip PAD-US 3.0 to the bounding box of NoData surrounding the extent of Southeast Blueprint 2024.Remove the following areas from PAD-US 3.0, which are outside the scope of this indicator to represent parks:All School Trust Lands in Oklahoma and Mississippi (Loc Des = “School Lands” or “School Trust Lands”). These extensive lands are leased out and are not open to the public.All tribal and military lands (“Des_Tp” = "TRIBL" or “Des_Tp” = "MIL"). Generally, these lands are not intended for public recreational use.All BOEM marine lease blocks (“Own_Name” = "BOEM"). These Outer Continental Shelf lease blocks do not represent actively protected marine parks, but serve as the “legal definition for BOEM offshore boundary coordinates...for leasing and administrative purposes” (BOEM).All lands designated as “proclamation” (“Des_Tp” = "PROC"). These typically represent the approved boundary of public lands, within which land protection is authorized to occur, but not all lands within the proclamation boundary are necessarily currently in a conserved status.Retain only selected attribute fields from PAD-US to get rid of irrelevant attributes.Merged the filtered PAD-US layer produced above with the OSM beaches and FWS National Realty Tracts to produce a combined protected areas dataset.The resulting merged data layer contains overlapping polygons. To remove overlapping polygons, use the Dissolve function.Clip the resulting data layer to the inland and nearshore extent.Process all multipart polygons (e.g., separate parcels within a National Wildlife Refuge) to single parts (referred to in Arc software as an “explode”).Select all polygons that intersect the Census urban extent within 0.5 miles. We chose 0.5 miles to represent a reasonable walking distance based on input and feedback from park access experts. Assuming a moderate intensity walking pace of 3 miles per hour, as defined by the U.S. Department of Health and Human Service’s physical activity guidelines, the 0.5 mi distance also corresponds to the 10-minute walk threshold used in the equitable access to potential parks indicator.Dissolve all the park polygons that were selected in the previous step.Process all multipart polygons to single parts (“explode”) again.Add a unique ID to the selected parks. This value will be used in a later step to join the parks to their buffers.Create a 0.5 mi (805 m) buffer ring around each park using the multiring plugin in QGIS. Ensure that “dissolve buffers” is disabled so that a single 0.5 mi buffer is created for each park.Assess the amount of overlap between the buffered park and the Census urban area using “overlap analysis”. This step is necessary to identify parks that do not intersect the urban area, but which lie within an urban matrix (e.g., Umstead Park in Raleigh, NC and Davidson-Arabia Mountain Nature Preserve in Atlanta, GA). This step creates a table that is joined back to the park polygons using the UniqueID.Remove parks that had ≤10% overlap with the urban areas when buffered. This excludes mostly non-urban parks that do not meet the intent of this indicator to capture parks that provide nearby access for urban residents. Note: The 10% threshold is a judgement call based on testing which known urban parks and urban National Wildlife Refuges are captured at different overlap cutoffs and is intended to be as inclusive as possible.Calculate the GIS acres of each remaining park unit using the Add Geometry Attributes function.Buffer the selected parks by 15 m. Buffering prevents very small and narrow parks from being left out of the indicator when the polygons are converted to raster.Reclassify the parks based on their area into the 7 classes seen in the final indicator values below. These thresholds were informed by park classification guidelines from the National Recreation and Park Association, which classify neighborhood parks as 5-10 acres, community parks as 30-50 acres, and large urban parks as optimally 75+ acres (Mertes and Hall 1995).Assess the impervious surface composition of each park using the NLCD 2021 impervious layer and the Zonal Statistics “MEAN” function. Retain only the mean percent impervious value for each park.Extract only parks with a mean impervious pixel value <80%. This step excludes parks that do not meet the intent of the indicator to capture opportunities to connect with nature and offer refugia for species (e.g., the Superdome in New Orleans, LA, the Astrodome in Houston, TX, and City Plaza in Raleigh, NC).Extract again to the inland and nearshore extent.Export the final vector file to a shapefile and import to ArcGIS Pro.Convert the resulting polygons to raster using the ArcPy Feature to Raster function and the area class field.Assign a value of 0 to all other pixels in the Southeast Blueprint 2024 extent not already identified as an urban park in the mapping steps above. Zero values are intended to help users better understand the extent of this indicator and make it perform better in online tools.Use the land and shallow marine layer and “extract by mask” tool to save the final version of this indicator.Add color and legend to raster attribute table.As a final step, clip to the spatial extent of Southeast Blueprint 2024.Note: For more details on the mapping steps, code used to create this layer is available in theSoutheast Blueprint Data Downloadunder > 6_Code.Final indicator valuesIndicator values are assigned as follows:6= 75+ acre urban park5= 50 to <75 acre urban park4= 30 to <50 acre urban park3= 10 to <30 acre urban park2=5 to <10acreurbanpark1 = <5 acre urban park0 = Not identified as an urban parkKnown IssuesThis indicator does not include park amenities that influence how well the park serves people and should not be the only tool used for parks and recreation planning. Park standards should be determined at a local level to account for various community issues, values, needs, and available resources.This indicator includes some protected areas that are not open to the public and not typically thought of as “parks”, like mitigation lands, private easements, and private golf courses. While we experimented with excluding them using the public access attribute in PAD, due to numerous inaccuracies, this inadvertently removed protected lands that are known to be publicly accessible. As a result, we erred on the side of including the non-publicly accessible lands.The NLCD percent impervious layer contains classification inaccuracies. As a result, this indicator may exclude parks that are mostly natural because they are misclassified as mostly impervious. Conversely, this indicator may include parks that are mostly impervious because they are misclassified as mostly

Biogeoclimatic Ecosystem Classification (BEC) has been applied extensively in characterizing forested ecosystems in British Columbia. With a lack of qualified vectorization method used for BEC data transformation, the main goal of this research is to polygonize discontinuous BEC raster classes into vector map with better overall effectiveness and efficiency especially regarding the linear areas. The original data input for analysis is a machine-learning BEC zone raster map of Deception Study Area located in middle BC near Telkwa, with a resolution of 5m*5m. A comprehensive comparison between vectorization algorithms in GIS applications was conducted, including different filtering, simplifying and smoothing algorithms. Since we have the original predicted BEC raster map as the performance measurement, accuracy was directly measured as the percentage of correctly classified pixels when rasterizing the polygons. The evaluation criteria include visual effect, number of polygons, linear patches accuracy processing time. We found an appropriate vectorization routine to polygonize the classification raster maps. The polygonal map using Scenario D has overall satisfactory effectiveness and efficiency with a 46% linear patch accuracy and 62,014 polygons. The method also provides good approximations of the areas with moderate processing time. This is partly because we allow vertices to be located anywhere and not just exactly on the boundary of the original raster zones. We can promote this polygonization method in future predicted ecosystem mapping (PEM) product with similar linear and discontinuous areas. Priority of several key BEC zone classification with importance level regarding to the ecosystem condition related to endangered species can be further explored and added to the algorithms to better polygonize those areas in future studies.

Coastwide vegetation surveys have been conducted multiple times over the past 50 years (e.g., Chabreck and Linscombe 1968, 1978, 1988, 1997, 2001, and 2013) by the Louisiana Department of Wildlife and Fisheries (LDWF) in support of coastal management activities. The last survey was conducted in 2013 and was funded by the Louisiana Coastal Protection and Restoration Authority (CPRA) and the U.S. Geological Survey (USGS) as a part of the Coastal Wetlands Planning, Protection, and Restoration Act (CWPPRA) monitoring program. These surveys provide important data that have been utilized by federal, state, and local resource managers. The surveys provide information on the condition of Louisiana’s coastal marshes by mapping plant species composition and vegetation change through time. During the summer of 2021, the U.S. Geological Survey, Louisiana State University, and the Louisiana Department of Wildlife and Fisheries jointly completed a helicopter survey to collect data on 2021 vegetation types using the same field methodology at previously sampled data points. Plant species were identified and their abundance classified at each point. Based on species composition and abundance, each marsh sampling station was assigned a marsh type: fresh, intermediate, brackish, or saline marsh. The field point data were interpolated to classify marsh vegetation into polygons and map the distribution of vegetation types. We then used the 2021 polygons with additional remote sensing data to create the final raster dataset. We used the polygon marsh type zones (available in this data release), as well as National Land Cover Database (NLCD; https://www.usgs.gov/centers/eros/science/national-land-cover-database) and NOAA Coastal Change Analysis Program (CCAP; https://coast.noaa.gov/digitalcoast/data/ccapregional.html) datasets to create a composite raster dataset. The composite raster was created to provide more detail, particularly with regard to “Other”, “Swamp”, and “Water” categories, than is available in the polygon dataset. The overall boundary of the raster product was extended beyond past surveys to better inform swamp, water, and other boundaries across the coast. A majority of NLCD and CCAP classification during a 2010-2019 period was used, rather than creating a raster classification specific to 2021, as there was a desire to use published datasets. Users are cautioned that the raster dataset is generalized but more specific than the polygon dataset. This data release includes 3 datasets: the point field data collected by the helicopter survey team, the polygon data developed from the point data, and the raster data developed from the polygon data plus additional remote sensing data as described above.

This dataset is available for download from: Wetlands (File Geodatabase).Wetlands in California are protected by several federal and state laws, regulations, and policies. This layer was extracted from the broader land cover raster from the CA Nature project which was recently enhanced to include a more comprehensive definition of wetland. This wetlands dataset is used as an exclusion as part of the biological planning priorities in the CEC 2023 Land-Use Screens.This layer is featured in the CEC 2023 Land-Use Screens for Electric System Planning data viewer.For more information about this layer and its use in electric system planning, please refer to the Land Use Screens Staff Report in the CEC Energy Planning Library. Change LogVersion 1.1 (January 26, 2023)Full resolution of wetlands replaced a coarser resolution version that was previously shared. Also, file type changed from polygon to raster (feature service to tile layer service).

This zip file contains geodatabases with raster mosaic datasets. The raster mosaic datasets consist of georeferenced tiff images of mineral potential maps, their associated metadata, and descriptive information about the images. These images are duplicates of the images found in the georeferenced tiff images zip file. There are four geodatabases containing the raster mosaic datasets, one for each of the four SaMiRA report areas: North-Central Montana; North-Central Idaho; Southwestern and South-Central Wyoming and Bear River Watershed; and Nevada Borderlands. The georeferenced images were clipped to the extent of the map and all explanatory text, gathered from map explanations or report text was imported into the raster mosaic dataset database as ‘Footprint’ layer attributes. The data compiled into the 'Footprint' layer tables contains the figure caption from the original map, online linkage to the source report when available, and information on the assessed commodities according to the legal definition of mineral resources—metallic, non-metallic, leasable non-fuel, leasable fuel, geothermal, paleontological, and saleable. To use the raster mosaic datasets in ArcMap, click on “add data”, double click on the [filename].gdb, and add the item titled [filename]_raster_mosaic. This will add all of the images within the geodatabase as part of the raster mosaic dataset. Once added to ArcMap, the raster mosaic dataset appears as a group of three layers under the mosaic dataset. The first item in the group is the ‘Boundary’, which contains a single polygon representing the extent of all images in the dataset. The second item is the ‘Footprint’, which contains polygons representing the extent of each individual image in the dataset. The ‘Footprint’ layer also contains the attribute table data associated with each of the images. The third item is the ‘Image’ layer and contains the images in the dataset. The images are overlapping and must be selected and locked, or queried in order to be viewed one at a time. Images can be selected from the attribute table, or can be selected using the direct select tool. When using the direct select tool, you will need to deselect the ‘overviews’ after clicking on an image or group of images. To do this, right click on the ‘Footprint’ layer and hover over ‘Selection’, then click ‘Reselect Only Primary Rasters’. To lock a selected image after selecting it, right-click on the ‘Footprint’ layer in the table of contents window and hover over ‘Selection’, then click ‘Lock To Selected Rasters’. Another way to view a single image is to run a definition query on the image. This is done by right clicking on the raster mosaic in the table of contents and opening the layer properties box. Then click on the ‘Definition Query’ tab and create a query for the desired image.

scripts.zip

arcgisTools.atbx: terrainDerivatives: make terrain derivatives from digital terrain model (Band 1 = TPI (50 m radius circle), Band 2 = square root of slope, Band 3 = TPI (annulus), Band 4 = hillshade, Band 5 = multidirectional hillshades, Band 6 = slopeshade). rasterizeFeatures: convert vector polygons to raster masks (1 = feature, 0 = background).

makeChips.R: R function to break terrain derivatives and chips into image chips of a defined size. makeTerrainDerivatives.R: R function to generated 6-band terrain derivatives from digital terrain data (same as ArcGIS Pro tool). merge_logs.R: R script to merge training logs into a single file. predictToExtents.ipynb: Python notebook to use trained model to predict to new data. trainExperiments.ipynb: Python notebook used to train semantic segmentation models using PyTorch and the Segmentation Models package. assessmentExperiments.ipynb: Python code to generate assessment metrics using PyTorch and the torchmetrics library. graphs_results.R: R code to make graphs with ggplot2 to summarize results. makeChipsList.R: R code to generate lists of chips in a directory. makeMasks.R: R function to make raster masks from vector data (same as rasterizeFeatures ArcGIS Pro tool).

terraceDL.zip

dems: LiDAR DTM data partitioned into training, testing, and validation datasets based on HUC8 watershed boundaries. Original DTM data were provided by the Iowa BMP mapping project: https://www.gis.iastate.edu/BMPs. extents: extents of the training, testing, and validation areas as defined by HUC 8 watershed boundaries. vectors: vector features representing agricultural terraces and partitioned into separate training, testing, and validation datasets. Original digitized features were provided by the Iowa BMP Mapping Project: https://www.gis.iastate.edu/BMPs.

This data shows areas where merged survey bathymetry and backscatter data exists and allows you to download the data. The data was collected between 2001 and 2021.Bathymetry is the measurement of how deep is the sea. Bathymetry is the study of the shape and features of the seabed. The name comes from Greek words meaning "deep" and “measure". Bathymetry is collected on board boats working at sea and airplanes over land and coastline. The boats use special equipment called a multibeam echosounder. A multibeam echosounder is a type of sonar that is used to map the seabed. Sound waves are emitted in a fan shape beneath the boat. The amount of time it takes for the sound waves to bounce off the bottom of the sea and return to a receiver is used to determine water depth. The strength of the sound wave is used to determine how hard the bottom of the sea is. In other words, backscatter is the measure of sound that is reflected by the seafloor and received by the sonar. A strong sound wave indicates a hard surface (rocks, gravel), and a weak return signal indicates a soft surface (silt, mud).LiDAR is another way to map the seabed, using airplanes. Two laser light beams are emitted from a sensor on-board an airplane. The red beam reaches the water surface and bounces back; while the green beam penetrates the water hits the seabed and bounces back. The difference in time between the two beams returning allows the water depth to be calculated. LiDAR is only suitable for shallow waters (up to 30m depth).This data shows areas which have data available for download in Irish waters. These are areas where several surveys have been merged together.It is a vector dataset. Vector data portray the world using points, lines, and polygons (areas).This data is shown as polygons. Each polygon holds information on the data type (bathymetry or backscatter), format of data available for download (GEOTIFF, ESRI GRID), its resolution, projection, last update and provides links to download the data.The data available for download are raster datasets. Raster data is another name for gridded data. Raster data stores information in pixels (grid cells). Each raster grid makes up a matrix of cells (or pixels) organised into rows and columns.This data was collected using a boat or plane. Data is output in xyz format. X and Y are the location and Z is the depth or backscatter value. A software package converts it into gridded data. The grid cell size varies. Most of this data is available at 10m resolution. Each grid cell size is 10 meter by 10 meter. This means that each cell (pixel) represents an area of 10 meter squared.ESRI GRID datasets contain the depth value. This means you can click on a location and get its depth.GEOTIFFS are images of the data and only record colour values. We use software to create a 3D effect of what the seabed looks like. By using vertical exaggeration, artificial sun-shading (mostly as if there is a light source in the northwest) and colouring the depths using colour maps, it is possible to highlight the subtle relief of the seabed. The darker shading represents a deeper depths and lighter shading represents shallower depths.This data shows areas that have been surveyed. There are plans to fill in the missing areas between 2020 and 2026. The deeper offshore waters were mapped as part of the Irish National Seabed Survey (INSS) between 1999 and 2005. INtegrated Mapping FOr the Sustainable Development of Ireland's MArine Resource (INFOMAR) is mapping the inshore areas. (2006 - 2026).

This resource contains the test data for the GeoServer OGC Web Services tutorials for various GIS applications including ArcGIS Pro, ArcMap, ArcGIS Story Maps, and QGIS. The contents of the data include a polygon shapefile, a polyline shapefile, a point shapefile, and a raster dataset; all of which pertain to the state of Utah, USA. The polygon shapefile is of every county in the state of Utah. The polyline is of every trail in the state of Utah. The point shapefile is the current list of GNIS place names in the state of Utah. The raster dataset covers a region in the center of the state of Utah. All datasets are projected to NAD 1983 Zone 12N.

The raster_runif data source covers the Flanders and Brussels region and has a resolution of 32 meters. The raster cells with non-missing values match the value-cells of the GRTSmaster_habitats data source with a small buffer added. Every raster cell has a random value between 0 and 1 according to the uniform distribution.

An example usage of this raster is its combination with the GRTSmaster_habitats and habitatmap_stdized data sources in order to draw an equal probability sample of habitat types in Flanders. Habitatmap_stdized contains polygons that are partially or fully covered by habitat types. The proportion of a certain type within a polygon is provided by the phab value. We can draw an equal probability sample size n for a certain habitat type as follows:

select all raster cells of GRTSmaster_habitats that overlap with the sampling frame of the target habitat type

keep the raster cells for which the raster_runif value is lower than the phab value of the habitat type within the polygon

finally select the n raster cells with the lowest GRTS ranking number.

The R-code for creating the raster_runif data source can be found in the GitHub repository 'n2khab-preprocessing' at commit ede43a4.

A reading function to return the data source in a standardized way into the R environment is provided by the R-package n2khab.

PI: Terry Pavlis, University of New Orleans. The survey area consists of two polygons along the Gulf of Alaska. The western polygon was partially flown on September 2, 2005 (2 flights) and completed on September 8, 2005 (2 flights). This area is located approximately 56 miles southeast of Cordova, Alaska. The eastern polygon over the Sullivan Anticline is located about 140 miles southeast of Cordova, AK. The Sullivan Anticline was surveyed with 5 flights over a period of 8 days from September 3, 2005 through September 10, 2005. Low clouds and a substantial amount of rain precluded the completion of this polygon, but all lines except four were flown.

Publications associated with this dataset can be found at NCALM's Data Tracking Center

This resource contains the test data for the GeoServer OGC Web Services IpyLeaflet tutorial. The contents of the data include a polygon shapefile, a polyline shapefile, a point shapefile, and a raster dataset; all of which pertain to the state of Utah, USA. The polygon shapefile is of Utah county in the state of Utah. The polyline is of every major stream within Utah County. The point shapefile is the current list of summit GNIS place names within Utah County. The raster dataset covers a region in the center of the state of Utah. All datasets are projected to NAD 1983 Zone 12N.

NCALM Seeds. PIs: Nicholas Legg, Oregon State University and Scott Anderson, University of Colorado, Boulder. The requested survey area consisted of two separate polygons within the boundary of Mount Rainier National Park in Washington on the southwestern flank of the volcano. Their close proximity enabled the two surveys to be flown most efficiently as a single polygon. The eastern polygon (Legg) covers the Kautz Creek watershed and was collected to investigate landscape response to debris flows in order to implicate hazards in Mt. Rainier National Park. The western polygon (Anderson) covers the Tahoma Creek watershed and was collected to assess climatically-driven aggradation in a mountain stream. The total area for the combined survey including the area between the requested polygons and the additional coverage in the northwest corner is approximately 123 square kilometers. The survey required 4 flights which took place from August 28, 2012 - September 1, 2012.

Publications associated with this dataset can be found at NCALM's Data Tracking Center

This dataset consists of the 25m raster version of the Land Cover Map 1990 (LCM1990) for Great Britain. The 25m raster product consists of three bands: Band 1 - raster representation of the majority (dominant) class per polygon for 21 target classes; Band 2 - mean per polygon probability as reported by the Random Forest classifier (see supporting information); Band 3 - percentage of the polygon covered by the majority class. The 21 target classes are based on the Joint Nature Conservation Committee (JNCC) Broad Habitats, which encompass the entire range of UK habitats. This dataset is derived from the vector version of the Land Cover Map, which contains individual parcels of land cover and is the highest available spatial resolution. The 25m raster is the most detailed of the LCM1990 raster products both thematically and spatially, and it is used to derive the 1km products. LCM1990 is a land cover map of the UK which was produced at the UK Centre for Ecology & Hydrology by classifying satellite images (mainly from 1989 and 1990) into 21 Broad Habitat-based classes. It is the first in a series of land cover maps for the UK, which also includes maps for 2000, 2007, 2015, 2017, 2018 and 2019. LCM1990 consists of a range of raster and vector products and users should familiarise themselves with the full range (see related records, the UKCEH web site and the LCM1990 Dataset documentation) to select the product most suited to their needs. This work was supported by the Natural Environment Research Council award number NE/R016429/1 as part of the UK-SCAPE programme delivering National Capability.

This ESRI geodatabase consists of 5 feature datsets with 23 individual polygon feature classes and two raster datasets. A master campsite polygon feature class represents the boundaries of campsites identified in the 1973, 1984, and 1991 campsite inventories of the Colorado River corridor in Grand Canyon, Arizona. The other polygon feature classes represent camp locations along the Colorado River corridor in Grand Canyon, Arizona during different survey periods using different surveying techniques. The raster datasets represent sub-aerial and sub-surface sandbar surfaces at 37 long term-monitoring sites between Lees Ferry and Diamond Creek, Arizona in Grand Canyon National Park, measured in September and October of 2002 and 2009 at sites where campsite areas were also surveyed and measured.

Spatially Linked-data, built using the Discrete Global Grid System (DGGS) as a tool. These functions provide statistical cross-referencing between features of dissimilar geographic layers, to expresses statistical relationships between them. Can be applied to point, line, polygon and raster datasets (including Digital Earth Australia - DEA data).

This API is located at https://api.dggs.ga.gov.au/docs and contains several functions the user can access. The data drill function is the most commonly used for determining the features at a specific location.

Where appropriate, these tools calculate the apportionment figure which calculates the percentage that one feature is spatially within a comparison features from another geography. ABS, GA and other agencies use this sort of information to apportion data from one geography to another (e.g. to attribute Local Government Areas (LGA) polygons with data collected on ABS SA2 polygons).

There are many other use-cases. For example, tell me how many residential addresses are with in a wildfire burn area. Which LGA is the fire is within, which State Electorate, which suburbs, and which postcodes.

All this information is available from AusPIX web user interfaces, without the need to open a GIS package.

This AusPIX DGGS solution is built into a fast-API web interface (known also as a swagger interface) and resides inside Geoscience Australia (GA) infrastructure (on AWS). The fast-API is a modern method to share information through a user web-interface, providing secure access in both human and machine readable forms. This is F.A.I.R technology.

Humans can web-click through the API to find and copy the information they need. Machines can also query the API to consume the information for any higher level dashboards and other APIs.

This API is available at https://api.dggs.ga.gov.au/docs and has received an average of 100 hits (invocations or uses) per month over the last 6 months, which is quite good considering it is still waiting to be advertised in eCat. The most used function at the moment is the dataDrill function. Users input a Latitude/Longitude location and receive back a useful set of information about that location. Other functions are available and several potential ones identified.

Hyperlinks in the data also provide the landing pages to provide mapped features, geometry, and metadata from the GA/ABS semantically linked datasets and their APIs.

A feature of how the system is built is the ability to cross-reference any combination required, without the need to wait for re-calculation. The AusPIX system has this flexibility because its base-geography is equal area DGGS cells provisioned as a intelligent raster. This raster is provided as a rather simple SQL table for any APIs to query. All this technology is hidden from the end-user.

Because the DGGS cells and their attributed values are pre-calculated, the system works at high speed.

AusPIX provides a unique service beyond map data. Rather AusPIX focuses on the individual features and their relationships to features in other datasets. The benefit is that much of the difficult map interpretation or analysis is provided in completed form for the user. Rather than providing just data, AusPIX automates the provision of the next level up - information and statistics.

NCALM Seed. PI: Seul Gi Moon, Stanford University. The survey area consisted of two separate polygons shown with red outlines below in Figure 1. The North polygon is located approximately 35 km West of Garberville, California and the South polygon is located approximately 42 km South of Garberville, California. The total area for the 2 polygons is approximately 47 km². The survey took place on July 05, 2012.

Publications associated with this dataset can be found at NCALM's Data Tracking Center