4 datasets found
  1. g

    Sentinel-2 UTM Tiling Grid (ESA) | gimi9.com

    • gimi9.com
    Updated Oct 20, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2020). Sentinel-2 UTM Tiling Grid (ESA) | gimi9.com [Dataset]. https://gimi9.com/dataset/au_sentinel-2-utm-tiling-grid-esa/
    Explore at:
    Dataset updated
    Oct 20, 2020
    Description

    This dataset shows the tiling grid and their IDs for Sentinel 2 satellite imagery. The tiling grid IDs are useful for selecting imagery of an area of interest. Sentinel 2 is an Earth observation satellite developed and operated by the European Space Agency (ESA). Its imagery has 13 bands in the visible, near infrared and short wave infrared part of the spectrum. It has a spatial resolution of 10 m, 20 m and 60 m depending on the spectral band. Sentinel-2 has a 290 km field of view when capturing its imagery. This imagery is then projected on to a UTM grid and made available publicly on 100x100 km2 tiles. Each tile has a unique ID. This ID scheme allows all imagery for a given tile to be located. Provenance: The ESA make the tiling grid available as a KML file (see links). We were, however, unable to convert this KML into a shapefile for deployment on the eAtlas. The shapefile used for this layer was sourced from the Git repository developed by Justin Meyers (https://github.com/justinelliotmeyers/Sentinel-2-Shapefile-Index). Why is this dataset in the eAtlas?: Sentinel 2 imagery is very useful for the studying and mapping of reef systems. Selecting imagery for study often requires knowing what the tile grid IDs are for the area of interest. This dataset is intended as a reference layer. The eAtlas is not a custodian of this dataset and copies of the data should be obtained from the original sources. Data Dictionary: Name: UTM code associated with each tile. For example 55KDV

  2. a

    Data from: Tree Canopy

    • gisdata-townoflaplata.opendata.arcgis.com
    • hub.arcgis.com
    Updated Oct 10, 2018
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Bstahl (2018). Tree Canopy [Dataset]. https://gisdata-townoflaplata.opendata.arcgis.com/datasets/ca4469cfde4b4179aa2cea405c48a10b
    Explore at:
    Dataset updated
    Oct 10, 2018
    Dataset authored and provided by
    Bstahl
    Area covered
    Description

    Tree Canopy polygon data was derived using Maryland LiDAR Charles County - DEM Meters, and boundary corrections/updates based on 2017 six inch orthoimageryLiDAR Description: Survey National Geospatial Program Base LiDAR Specification, Version 1. The data was developed based on a horizontal projection/datum of UTM Zone 18 North, NAD83, meters and vertical datum of NAVD1988 (GEOID12A), meters. LiDAR data was delivered in RAW flight line swath format, processed to create Classified LAS 1.2 Files formatted to 2283 individual 1500m x 1500m tiles, and corresponding Intensity Images and Bare Earth DEMs tiled to the same 1500m x 1500m schema, and Breaklines in ESRI Shapefile format. The data was then converted to a horizontal projection/datum of NAD83 Maryland State Plane Coordinate System, Feet. LiDAR was delivered in Classified LAS 1.2 Files formatted to 1927 individual 4000' x 6000' tiles, and corresponding Intensity Images and Bare Earth DEMs tiled to the same 4000' x 6000' schema, and Breaklines in ESRI Shapefile format. Ground Conditions: LiDAR was collected in Winter 2014, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications, Quantum Spatial established a total of 59 QA control points and 95 Land Cover control points that were used to calibrate the LiDAR to known ground locations established throughout the SANDY_Restoration_VA_MD_DC_QL2 project area.

  3. r

    Keppel Islands Regional Maps (satellite imagery, habitat mapping and A0...

    • researchdata.edu.au
    Updated Apr 8, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Lawrey, Eric (2020). Keppel Islands Regional Maps (satellite imagery, habitat mapping and A0 maps) (AIMS) [Dataset]. http://doi.org/10.26274/MXKA-2B41
    Explore at:
    Dataset updated
    Apr 8, 2020
    Dataset provided by
    Australian Ocean Data Network
    Authors
    Lawrey, Eric
    License

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

    Time period covered
    May 27, 2016 - Jul 17, 2019
    Area covered
    Description

    This dataset collection contains A0 maps of the Keppel Island region based on satellite imagery and fine-scale habitat mapping of the islands and marine environment. This collection provides the source satellite imagery used to produce these maps and the habitat mapping data.

    The imagery used to produce these maps was developed by blending high-resolution imagery (1 m) from ArcGIS Online with a clear-sky composite derived from Sentinel 2 imagery (10 m). The Sentinel 2 imagery was used to achieve full coverage of the entire region, while the high-resolution was used to provide detail around island areas.

    The blended imagery is a derivative product of the Sentinel 2 imagery and ArcGIS Online imagery, using Photoshop to to manually blend the best portions of each imagery into the final product. The imagery is provided for the sole purpose of reproducing the A0 maps.

    Methods:

    The high resolution satellite composite composite was developed by manual masking and blending of a Sentinel 2 composite image and high resolution imagery from ArcGIS Online World Imagery (2019).

    The Sentinel 2 composite was produced by statistically combining the clearest 10 images from 2016 - 2019. These images were manually chosen based on their very low cloud cover, lack of sun glint and clear water conditions. These images were then combined together to remove clouds and reduce the noise in the image.

    The processing of the images was performed using a script in Google Earth Engine. The script combines the manually chosen imagery to estimate the clearest imagery. The dates of the images were chosen using the EOBrowser (https://www.sentinel-hub.com/explore/eobrowser) to preview all the Sentinel 2 imagery from 2015-2019. The images that were mostly free of clouds, with little or no sun glint, were recorded. Each of these dates was then viewed in Google Earth Engine with high contrast settings to identify images that had high water surface noise due to algal blooms, waves, or re-suspension. These were excluded from the list. All the images were then combined by applying a histogram analysis of each pixel, with the final image using the 40th percentile of the time series of the brightness of each pixel. This approach helps exclude effects from clouds.

    The contrast of the image was stretched to highlight the marine features, whilst retaining detail in the land features. This was done by choosing a black point for each channel that would provide a dark setting for deep clear water. Gamma correction was then used to lighten up the dark water features, whilst not ove- exposing the brighter shallow areas.

    Both the high resolution satellite imagery and Sentinel 2 imagery was combined at 1 m pixel resolution. The resolution of the Sentinel 2 tiles was up sampled to match the resolution of the high-resolution imagery. These two sets of imagery were then layered in Photoshop. The brightness of the high-resolution satellite imagery was then adjusting to match the Sentinel 2 imagery. A mask was then used to retain and blend the imagery that showed the best detail of each area. The blended tiles were then merged with the overall area imagery by performing a GDAL merge, resulting in an upscaling of the Sentinel 2 imagery to 1 m resolution.


    Habitat Mapping:

    A 5 m resolution habitat mapping was developed based on the satellite imagery, aerial imagery available, and monitoring site information. This habitat mapping was developed to help with monitoring site selection and for the mapping workshop with the Woppaburra TOs on North Keppel Island in Dec 2019.

    The habitat maps should be considered as draft as they don't consider all available in water observations. They are primarily based on aerial and satellite images.

    The habitat mapping includes: Asphalt, Buildings, Mangrove, Cabbage-tree palm, Sheoak, Other vegetation, Grass, Salt Flat, Rock, Beach Rock, Gravel, Coral, Sparse coral, Unknown not rock (macroalgae on rubble), Marine feature (rock).

    This assumed layers allowed the digitisation of these features to be sped up, so for example, if there was coral growing over a marine feature then the boundary of the marine feature would need to be digitised, then the coral feature, but not the boundary between the marine feature and the coral. We knew that the coral was going to cut out from the marine feature because the coral is on top of the marine feature, saving us time in digitising this boundary. Digitisation was performed on an iPad using Procreate software and an Apple pencil to draw the features as layers in a drawing. Due to memory limitations of the iPad the region was digitised using 6000x6000 pixel tiles. The raster images were converted back to polygons and the tiles merged together.

    A python script was then used to clip the layer sandwich so that there is no overlap between feature types.

    Habitat Validation:

    Only limited validation was performed on the habitat map. To assist in the development of the habitat mapping, nearly every YouTube video available, at the time of development (2019), on the Keppel Islands was reviewed and, where possible, georeferenced to provide a better understanding of the local habitats at the scale of the mapping, prior to the mapping being conducted. Several validation points were observed during the workshop. The map should be considered as largely unvalidated.

    data/coastline/Keppels_AIMS_Coastline_2017.shp:
    The coastline dataset was produced by starting with the Queensland coastline dataset by DNRME (Downloaded from http://qldspatial.information.qld.gov.au/catalogue/custom/detail.page?fid={369DF13C-1BF3-45EA-9B2B-0FA785397B34} on 31 Aug 2019). This was then edited to work at a scale of 1:5000, using the aerial imagery from Queensland Globe as a reference and a high-tide satellite image from 22 Feb 2015 from Google Earth Pro. The perimeter of each island was redrawn. This line feature was then converted to a polygon using the "Lines to Polygon" QGIS tool. The Keppel island features were then saved to a shapefile by exporting with a limited extent.

    data/labels/Keppel-Is-Map-Labels.shp:
    This contains 70 named places in the Keppel island region. These names were sourced from literature and existing maps. Unfortunately, no provenance of the names was recorded. These names are not official. This includes the following attributes:
    - Name: Name of the location. Examples Bald, Bluff
    - NameSuffix: End of the name which is often a description of the feature type: Examples: Rock, Point
    - TradName: Traditional name of the location
    - Scale: Map scale where the label should be displayed.

    data/lat/Keppel-Is-Sentinel2-2016-19_B4-LAT_Poly3m_V3.shp:
    This corresponds to a rough estimate of the LAT contours around the Keppel Islands. LAT was estimated from tidal differences in Sentinel-2 imagery and light penetration in the red channel. Note this is not very calibrated and should be used as a rough guide. Only one rough in-situ validation was performed at low tide on Ko-no-mie at the edge of the reef near the education centre. This indicated that the LAT estimate was within a depth error range of about +-0.5 m.

    data/habitat/Keppels_AIMS_Habitat-mapping_2019.shp:
    This shapefile contains the mapped land and marine habitats. The classification type is recorded in the Type attribute.

    Format:

    GeoTiff (Internal JPEG format - 538 MB)
    PDF (A0 regional maps - ~30MB each)
    Shapefile (Habitat map, Coastline, Labels, LAT estimate)

    Data Location:

    This dataset is filed in the eAtlas enduring data repository at: data\custodian\2020-2029-AIMS\Keppels_AIMS_Regional-maps

  4. m

    Maryland LiDAR Charles County - Slope

    • data.imap.maryland.gov
    • hub.arcgis.com
    Updated Jan 1, 2014
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    ArcGIS Online for Maryland (2014). Maryland LiDAR Charles County - Slope [Dataset]. https://data.imap.maryland.gov/datasets/b5400308f8664a048bcc073bb728e9f8
    Explore at:
    Dataset updated
    Jan 1, 2014
    Dataset authored and provided by
    ArcGIS Online for Maryland
    Area covered
    Description

    Geographic Extent: SANDY_Restoration_VA_MD_DC_QL2 Area of Interest covers approximately 2,002 square miles. Lot #5 contains the full project area Dataset Description: The SANDY_Restoration_VA_MD_DC_QL2 project called for the Planning, Acquisition, processing and derivative products of LiDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 1. The data was developed based on a horizontal projection/datum of UTM Zone 18 North, NAD83, meters and vertical datum of NAVD1988 (GEOID12A), meters. LiDAR data was delivered in RAW flight line swath format, processed to create Classified LAS 1.2 Files formatted to 2283 individual 1500m x 1500m tiles, and corresponding Intensity Images and Bare Earth DEMs tiled to the same 1500m x 1500m schema, and Breaklines in ESRI Shapefile format. The data was then converted to a horizontal projection/datum of NAD83 Maryland State Plane Coordinate System, Feet. LiDAR was delivered in Classified LAS 1.2 Files formatted to 1927 individual 4000' x 6000' tiles, and corresponding Intensity Images and Bare Earth DEMs tiled to the same 4000' x 6000' schema, and Breaklines in ESRI Shapefile format. Ground Conditions: LiDAR was collected in Winter 2014, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications, Quantum Spatial established a total of 59 QA control points and 95 Land Cover control points that were used to calibrate the LiDAR to known ground locations established throughout the SANDY_Restoration_VA_MD_DC_QL2 project area.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/Charles/MD_charles_slope_m/ImageServer

  5. Not seeing a result you expected?
    Learn how you can add new datasets to our index.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
(2020). Sentinel-2 UTM Tiling Grid (ESA) | gimi9.com [Dataset]. https://gimi9.com/dataset/au_sentinel-2-utm-tiling-grid-esa/

Sentinel-2 UTM Tiling Grid (ESA) | gimi9.com

Explore at:
Dataset updated
Oct 20, 2020
Description

This dataset shows the tiling grid and their IDs for Sentinel 2 satellite imagery. The tiling grid IDs are useful for selecting imagery of an area of interest. Sentinel 2 is an Earth observation satellite developed and operated by the European Space Agency (ESA). Its imagery has 13 bands in the visible, near infrared and short wave infrared part of the spectrum. It has a spatial resolution of 10 m, 20 m and 60 m depending on the spectral band. Sentinel-2 has a 290 km field of view when capturing its imagery. This imagery is then projected on to a UTM grid and made available publicly on 100x100 km2 tiles. Each tile has a unique ID. This ID scheme allows all imagery for a given tile to be located. Provenance: The ESA make the tiling grid available as a KML file (see links). We were, however, unable to convert this KML into a shapefile for deployment on the eAtlas. The shapefile used for this layer was sourced from the Git repository developed by Justin Meyers (https://github.com/justinelliotmeyers/Sentinel-2-Shapefile-Index). Why is this dataset in the eAtlas?: Sentinel 2 imagery is very useful for the studying and mapping of reef systems. Selecting imagery for study often requires knowing what the tile grid IDs are for the area of interest. This dataset is intended as a reference layer. The eAtlas is not a custodian of this dataset and copies of the data should be obtained from the original sources. Data Dictionary: Name: UTM code associated with each tile. For example 55KDV

Search
Clear search
Close search
Google apps
Main menu