Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
81
datasets available to search
ShareScore release 0.9.0
Dataset results
81 results for “Sentinel 2”
Sentinel-5P Methane Density at 2 km from 2021-12 to 2023-11 Monthly Aggregation Time-series Reconstructed
<p><strong>General Description</strong></p><p>The <i>monthly aggregated Methane Volume Mixing Ratio </i>dataset is derived from Sentinel-5P to generate a time-series reconstructed monthly aggregated map. The dataset time spans from December 2021 to November 2023 and provides data that covers the entire globe. The mission is still underway and expected to update periodically.</p><p>For more info about the s5p Methane product see: <a href="">https://maps.s5p-pal.com/ch4/</a>.</p><p>The dataset can be used in many applications like emission tracing, livestock monitor, and greenhouse gas monitor.</p><ul><li><strong>Monthly time-series:</strong></li></ul><p>Methane monthly average value December 2021 – November 2023. Derived using the <a href="https://eumap.readthedocs.io/en/latest/">eumap</a> and <a href="https://github.com/openlandmap/scikit-map">scikitmap</a> package in Python . We derived three standard statistics: (1) 10th percentile (p10), median (p50), and 90th percentile (p90).</p><p><strong>Data Details</strong></p><ul><li><strong>Time period:</strong> December 2021 – November 2023</li><li><strong>Type of data:</strong> Methane Volume Mixing Ratio (Unit: ppbv)</li><li><strong>How the data was collected or derived:</strong> Derived from 2km Sentinel-5P Menthane using Python running in a local HPC. The time-series analysis were computed using the <a href="https://github.com/scikit-map/scikit-map">Scikit-map</a> and <a href="https://eumap.readthedocs.io/en/latest/">eumap </a>Python package.</li><li><strong>Statistical methods used:</strong> percentiles 10, 50, and 90.</li><li><strong>Limitations or exclusions in the data:</strong> The dataset is not completed gap-filled. Certain areas have no data in the whole time series</li><li><strong>Coordinate reference system:</strong> EPSG:4326</li><li><strong>Bounding box (Xmin, Ymin, Xmax, Ymax):</strong> (-180.00000, -61.9966697, 180.0000072, 87.37000)</li><li><strong>Spatial resolution:</strong> 1/60 d.d. = 0.016666667 (2km)</li><li><strong>Image size:</strong> 21,600 x 8,962</li><li><strong>File format:</strong> Cloud Optimized Geotiff (COG) format.</li></ul><p><strong>Support</strong></p><p>If you discover a bug, artifact or inconsistency, or if you have a question please use some of the following channels:</p><ul><li>Technical issues and questions about the code: <a href="https://gitlab.com/openlandmap/global-layers/-/issues">https://gitlab.com/openlandmap/global-layers/-/issues</a></li><li>General questions and comments: <a href="https://disqus.com/home/forums/landgis/">https://disqus.com/home/forums/landgis/</a></li></ul><p><strong>Name convention</strong></p><p>To ensure consistency and ease of use across and within the projects, we follow the standard Open-Earth-Monitor file-naming convention. The convention works with 10 fields that describes important properties of the data. In this way users can search files, prepare data analysis etc, without needing to open files. The fields are:</p><ol><li><strong>generic variable name:</strong> ch4.vmr = methane density methane volume mixing ratio</li><li><strong>variable procedure combination:</strong> m.seacov = monthly aggregated and gap filled by seasonal convolution</li><li><strong>Position in the probability distribution / variable type:</strong> p10/p50/p90 = 10th/50th/90th percentile</li><li><strong>Spatial support:</strong> 2km</li><li><strong>Depth reference:</strong> a = above surface</li><li><strong>Time reference begin time:</strong> 20211201 = 2021-12-01</li><li><strong>Time reference end time:</strong> 20231131 = 2023-11-31</li><li><strong>Bounding box:</strong> go = global (without Antarctica)</li><li><strong>EPSG code:</strong> epsg.4326 = EPSG:4326</li><li><strong>Version code:</strong> v20230628 = 2023-12-08 (creation date)</li></ol>
Dataset for marine vessel detection from Sentinel 2 images in the Finnish coast
<p>This dataset contains annotated marine vessels from 15 different Sentinel-2 product, used for training object detection models for marine vessel detection. The vessels are annotated as bounding boxes, covering also some amount of the wake, if present.</p> <h2>Source data</h2> <div> <div>Individual products used to generate annotations are shown in the following table:</div> </div> <div> </div> <div> <table style="width: 58.034%; height: 411.47px;"> <tbody> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"><strong>Location</strong></td> <td style="width: 79.3617%; height: 19.5938px;"><strong>Product name</strong></td> </tr> <tr style="height: 39.1875px;"> <td style="width: 16.0296%; height: 39.1875px;">Archipelago sea</td> <td style="width: 79.3617%; height: 39.1875px;">S2A_MSIL1C_20220515T100031_N0510_R122_T34VEM_20240617T162344.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL1C_20220619T100029_N0510_R122_T34VEM_20240627T204751.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL1C_20220721T095041_N0510_R079_T34VEM_20240712T224506.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL1C_20220813T095601_N0510_R122_T34VEM_20240717T115958.SAFE</td> </tr> <tr style="height: 39.1875px;"> <td style="width: 16.0296%; height: 39.1875px;">Gulf of Finland</td> <td style="width: 79.3617%; height: 39.1875px;">S2B_MSIL1C_20220606T095029_N0510_R079_T35VLG_20240619T111429.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL1C_20220626T095039_N0510_R079_T35VLG_20240620T013500.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL1C_20220703T094039_N0510_R036_T35VLG_20240702T075354.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL1C_20220721T095041_N0510_R079_T35VLG_20240712T224506.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;">Bothnian Bay</td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL1C_20220627T100611_N0510_R022_T34WFT_20240628T041908.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL1C_20220712T100559_N0510_R022_T34WFT_20240718T033027.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL1C_20220828T095549_N0510_R122_T34WFT_20240708T035231.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;">Bothnian Sea</td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL1C_20210714T100029_N0500_R122_T34VEN_20230224T120043.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL1C_20220619T100029_N0510_R122_T34VEN_20240627T204751.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL1C_20220624T100041_N0510_R122_T34VEN_20240714T110124.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL1C_20220813T095601_N0510_R122_T34VEN_20240717T115958.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;">Kvarken</td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL1C_20220617T100611_N0510_R022_T34VER_20240627T094433.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL1C_20220712T100559_N0510_R022_T34VER_20240718T033027.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL1C_20220826T100611_N0510_R022_T34VER_20240705T062429.SAFE</td> </tr> </tbody> </table> </div> <div> <div> </div> <div>Even though the reference data IDs are for L1C products, L2A products from the same acquisition dates can be used along with the annotations. However, Sen2Cor has been known to produce incorrect reflectance values for water bodies.</div> <div> </div> <div>The corresponding L2A product identifiers are:</div> </div> <div> </div> <div> <table style="width: 58.034%; height: 411.47px;"> <tbody> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"><strong>Location</strong></td> <td style="width: 79.3617%; height: 19.5938px;"><strong>Product name</strong></td> </tr> <tr style="height: 39.1875px;"> <td style="width: 16.0296%; height: 39.1875px;">Archipelago sea</td> <td style="width: 79.3617%; height: 39.1875px;">S2A_MSIL2A_20220515T100031_N0400_R122_T34VEM_20220515T141508.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL2A_20220619T100029_N0510_R122_T34VEM_20240628T011619.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL2A_20220721T095041_N0510_R079_T34VEM_20240713T035445.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL2A_20220813T095601_N0510_R122_T34VEM_20240717T165127.SAFE</td> </tr> <tr style="height: 39.1875px;"> <td style="width: 16.0296%; height: 39.1875px;">Gulf of Finland</td> <td style="width: 79.3617%; height: 39.1875px;">S2B_MSIL2A_20220606T095029_N0510_R079_T35VLG_20240619T162121.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL2A_20220626T095039_N0510_R079_T35VLG_20240620T063951.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL2A_20220703T094039_N0510_R036_T35VLG_20240702T130032.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL2A_20220721T095041_N0510_R079_T35VLG_20240713T035445.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;">Bothnian Bay</td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL2A_20220627T100611_N0510_R022_T34WFT_20240628T095704.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL2A_20220712T100559_N0510_R022_T34WFT_20240718T063657.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL2A_20220828T095549_N0510_R122_T34WFT_20240708T091048.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;">Bothnian Sea</td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL2A_20210714T100029_N0500_R122_T34VEN_20230224T182455.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL2A_20220619T100029_N0510_R122_T34VEN_20240628T011619.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL2A_20220624T100041_N0510_R122_T34VEN_20240714T162313.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL2A_20220813T095601_N0510_R122_T34VEN_20240717T165127.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;">Kvarken</td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL2A_20220617T100611_N0510_R022_T34VER_20240627T130404.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2B_MSIL2A_20220712T100559_N0510_R022_T34VER_20240718T063657.SAFE</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 16.0296%; height: 19.5938px;"> </td> <td style="width: 79.3617%; height: 19.5938px;">S2A_MSIL2A_20220826T100611_N0510_R022_T34VER_20240705T120522.SAFE</td> </tr> </tbody> </table> </div> <div><br> <div>The raw products can be acquired from <a href="https://dataspace.copernicus.eu" target="_blank" rel="noopener">Copernicus Data Space Ecosystem.</a> The products listed above can be unavailable due to e.g. processing level updates and old versions being deleted. In those cases, try searching with the tile identifier and acquisition date in order to get the correct product ID.</div> <br> <h2>Annotations</h2> <br> <div>The annotations are bounding boxes drawn around marine vessels so that some amount of their wakes, if present, are also contained within the boxes. The data are distributed as geopackage files, so that one geopackage corresponds to a single Sentinel-2 tile, and each package has separate layers for individual products as shown below:</div> <br> <blockquote> <div>T34VEM</div> <div>|-20220515</div> <div>|-20220619</div> <div>|-20220721</div> <div>|-20220813</div> </blockquote> <br> <div>All layers have a column <strong>id</strong>, which has the value <strong>b</strong><strong>oat</strong> for all annotations.</div> <br> <div>CRS is EPSG:32634 for all products except for the Gulf of Finland (35VLG), which is in EPSG:32635. This is done in order to have the bounding boxes to be aligned with the pixels in the imagery.</div> <br> <div>As tiles 34VEM and 34VEN have an overlap of 9.5x100 km, 34VEN is not annotated from the overlapping part to prevent data leakage between splits.</div> <br> <h3>Annotation process</h3> The minimum size for an object to be considered as a potential marine vessel was set to 2x2 pixels. Three separate acquisitions for each location were used to detect smallest objects, so that if an object was located at the same place in all images, then it was left unannotated. The data were annotated by two experts. <div> </div> <table style="width: 63.327%; height: 391.876px;"> <tbody> <tr style="height: 39.1875px;"> <td style="width: 72.7285%; height: 39.1875px;"><strong>Product name</strong></td> <td style="width: 23.0224%; height: 39.1875px;"><strong>Number of annotations</strong></td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2A_MSIL1C_20220515T100031_N0510_R122_T34VEM_20240617T162344.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">183</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2B_MSIL1C_20220619T100029_N0510_R122_T34VEM_20240627T204751.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">519</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2A_MSIL1C_20220721T095041_N0510_R079_T34VEM_20240712T224506.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">1518</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2A_MSIL1C_20220813T095601_N0510_R122_T34VEM_20240717T115958.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">1371</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2B_MSIL1C_20220606T095029_N0510_R079_T35VLG_20240619T111429.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">277</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2B_MSIL1C_20220626T095039_N0510_R079_T35VLG_20240620T013500.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">1205</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2B_MSIL1C_20220703T094039_N0510_R036_T35VLG_20240702T075354.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">746</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2A_MSIL1C_20220721T095041_N0510_R079_T35VLG_20240712T224506.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">971</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2A_MSIL1C_20220627T100611_N0510_R022_T34WFT_20240628T041908.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">122</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2B_MSIL1C_20220712T100559_N0510_R022_T34WFT_20240718T033027.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">162</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2B_MSIL1C_20220828T095549_N0510_R122_T34WFT_20240708T035231.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">98</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2B_MSIL1C_20210714T100029_N0500_R122_T34VEN_20230224T120043.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">450</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2B_MSIL1C_20220619T100029_N0510_R122_T34VEN_20240627T204751.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">66</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2A_MSIL1C_20220624T100041_N0510_R122_T34VEN_20240714T110124.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">424</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2A_MSIL1C_20220813T095601_N0510_R122_T34VEN_20240717T115958.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">399</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2A_MSIL1C_20220617T100611_N0510_R022_T34VER_20240627T094433.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">83</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;"> <div> <div>S2B_MSIL1C_20220712T100559_N0510_R022_T34VER_20240718T033027.SAFE</div> </div> </td> <td style="width: 23.0224%; height: 19.5938px;">184</td> </tr> <tr style="height: 19.5938px;"> <td style="width: 72.7285%; height: 19.5938px;">S2A_MSIL1C_20220826T100611_N0510_R022_T34VER_20240705T062429.SAFE</td> <td style="width: 23.0224%; height: 19.5938px;">88</td> </tr> </tbody> </table> <br><br> <h3>Annotation statistics</h3> <br>Sentinel-2 images have spatial resolution of 10 m, so below statistics can be converted to pixel sizes by dividing them by 10 (diameter) or 100 (area).</div> <div> <table> <tbody> <tr> <td> </td> <td><strong>mean</strong></td> <td><strong>min</strong></td> <td><strong>25%</strong></td> <td><strong>50%</strong></td> <td><strong>75%</strong></td> <td><strong>max</strong></td> </tr> <tr> <td><strong>Area (m²)</strong></td> <td>5305.7</td> <td>567.9</td> <td>1629.9</td> <td>2328.2</td> <td>5176.3</td> <td>414795.7</td> </tr> <tr> <td><strong>Diameter (m)</strong></td> <td>92.5</td> <td>33.9</td> <td>57.9</td> <td>69.4</td> <td>108.3</td> <td>913.9</td> </tr> </tbody> </table> <br><br> <div>As most of the annotations cover also most of the wake of the marine vessel, the bounding boxes are significantly larger than a typical boat. There are a few annotations larger than 100 000 m², which are either cruise or cargo ships that are travelling along ordinal directions instead of cardinal directions, instead of e.g. smaller leisure boats.</div> <br> <div>Annotations typically have diameter less than 100 meters, and the largest diameters correspond to similar instances than the largest bounding box areas.</div> <br> <h3>Train-test-split</h3> <br> <div>We used tiles 34VEN and 34VER as the test dataset. For validation, we split the other three tile areas into 5x5 equal sized grid, and used 20 % of the area (i.e 5 cells) for the validation. The same split also makes it possible to do cross-validation.</div> <div> </div> <div> </div> <div> </div> </div> <div> <h3>Post-processing</h3> </div> <div><br> <div>Before evaluating, the predictions for the test set are cleaned using the following steps:</div> <br> <div>1. All prediction whose centroid points are not located on water are discarded. The water mask used contains layers `jarvi` (Lakes), `meri` (Sea) and `virtavesialue` (Rivers as polygon geometry) from the Topographical database by the National Land Survey of Finland. Unfortunately this also discards all points not within the Finnish borders.</div> <div>2. All predictions whose centroid points are located on water rock areas are discarded. The mask is the layer `vesikivikko` (Water rock areas) from the Topographical database.</div> <div>3. All predictions that contain an above water rock within the bounding box are discarded. The mask contains classes `38511`, `38512`, `38513` from the layer `vesikivi` in the Topographical database.</div> <div>4. All predictions that contain a lighthouse or a sector light within the bounding box are discarded. Lighthouses and sector lights come from Väylävirasto data, `ty_njr` class ids are 1, 2, 3, 4, 5, 8</div> <div>5. All predictions that are wind turbines, found in Topographical database layer `tuulivoimalat`</div> <div>6. All predictions that are obviously too large are discarded. The prediction is defined to be "too large" if either of its edges is longer than 750 meters.</div> </div> <div> </div> <div>Model checkpoint for the best performing model is available on Hugging Face platform: <a href="https://huggingface.co/mayrajeo/marine-vessel-detection-yolov8">https://huggingface.co/mayrajeo/marine-vessel-detection-yolo</a><br> <h2>Usage</h2> The simplest way to chip the rasters into suitable format and convert the data to COCO or YOLO formats is to use <a href="https://github.com/mayrajeo/geo2ml">geo2ml</a>. First download the raw mosaics and convert them into GeoTiff files and then use the following to generate the datasets. <div> </div> To generate COCO format dataset run</div> <div> </div> <div> <pre><code>from geo2ml.scripts.data import create_coco_dataset raster_path = '<path_to_raster>' outpath = '<path_to_save_the_dataset>' poly_path = '<path_to_gpkg>' layer = '<date_of_raster>' create_coco_dataset(raster_path=raster_path, polygon_path=poly_path, target_column='id', gpkg_layer=layer, outpath=outpath, save_grid=False, dataset_name='<name_of_dataset>', gridsize_x=320, gridsize_y=320, ann_format='box', min_bbox_area=0)</code></pre> </div> <div><br> <div>To generate YOLO format dataset run</div> <div> <pre><code>from geo2ml.scripts.data import create_yolo_dataset raster_path = '<path_to_raster>' outpath = '<path_to_save_the_dataset>' poly_path = '<path_to_gpkg>' layer = '<date_of_raster>' create_yolo_dataset(raster_path=raster_path, polygon_path=poly_path, target_column='id', gpkg_layer=layer, outpath=outpath, save_grid=False, gridsize_x=320, gridsize_y=320, ann_format='box', min_bbox_area=0)</code></pre> </div> </div>
MEaSUREs ITS_LIVE Sentinel-1 Image-Pair Glacier and Ice Sheet Surface Velocities: Version 2 (Greenland Sample Products)
<p>We provide 21 sample products of MEaSUREs ITS_LIVE Sentinel-1 Image-Pair Glacier and Ice Sheet Surface Velocities: Version 2 in three test regions of Greenland Ice Sheet. The full archive of version 2 ITS_LIVE products (including image pair maps, data cubes and mosaics) from Sentinel-1 as well as other optical sensors (Landsat-4/5/6/7/8 and Sentinel-2) can be found at the ITS_LIVE project website: <a href="https://its-live.jpl.nasa.gov/">https://its-live.jpl.nasa.gov</a>.</p> <p><strong>Sensor</strong>: Sentinel-1A/B</p> <p><strong>Processor</strong>: <a href="https://github.com/isce-framework/isce2">ISCE</a>v2.4.1 (topsApp -> <a href="https://github.com/leiyangleon/Geogrid">Geogrid</a>v1.4.0 -> <a href="https://github.com/nasa-jpl/autoRIFT">autoRIFT</a>v1.4.0)</p> <p><strong>Project</strong>: NASA MEaSUREs project <a href="https://its-live.jpl.nasa.gov">ITS_LIVE</a></p> <p><strong>Region 1</strong> (69.13N, 50.88W; Jakobshavn Isbræ Glacier): 7 ascending image pairs</p> <p><strong>Region 2</strong> (77.61N, 42.79W; central north of interior Greenland): 3 ascending image pairs</p> <p><strong>Region 3</strong> (72.48N, 35.87W; central south of interior Greenland): 10 descending image pairs and 1 ascending image pair</p> <p>This serves as a supplementary dataset for the companion journal article submitted to Earth System Science Data (to appear).</p> <p> </p> <p><strong>Acknowledgement</strong>: This effort was funded by the NASA MEaSUREs program in contribution to the Inter-mission Time Series of Land Ice Velocity and Elevation (ITS_LIVE) project (<a href="https://its-live.jpl.nasa.gov/">https://its-live.jpl.nasa.gov/</a>) and through Alex Gardner’s participation in the NASA NISAR Science Team.</p>
Paired Sentinel-1 and Sentinel-2 Images for 2 Locations in Scotland and India for 2019 and 2020
<p>The dataset contains two years of coverage (2019 and 2020) for two distant geographical areas in India and in Scotland.</p> <p>If using this dataset, please cite the paper where it has been introduced:</p> <pre><code>@article{rs14061342, author = {Czerkawski, Mikolaj and Upadhyay, Priti and Davison, Christopher and Werkmeister, Astrid and Cardona, Javier and Atkinson, Robert and Michie, Craig and Andonovic, Ivan and Macdonald, Malcolm and Tachtatzis, Christos}, title = {Deep Internal Learning for Inpainting of Cloud-Affected Regions in Satellite Imagery}, journal = {Remote Sensing}, volume = {14}, year = {2022}, number = {6}, article-number = {1342}, url = {https://www.mdpi.com/2072-4292/14/6/1342}, ISSN = {2072-4292}, DOI = {10.3390/rs14061342} }</code></pre> <p> </p>
waldmonitoring.ch: NDVI difference rasters for annual forest change in Switzerland (Sentinel 2 based): 2016 - 2023
<p><strong>NDVI difference rasters for annual forest change in Switzerland (Sentinel 2 based): 2016 - 2023<br></strong></p> <p><em><strong>Date format:</strong></em> GeoTIFF<br><em><strong>Data type: </strong></em>Int16 - Sixteen bit signed integer*<br><em><strong>Spatial Resolution</strong></em>: 10 x 10 m<br><em><strong>Spatial Extent: </strong></em>Switzerland and Liechtenstein, masked with swisstopo swissTLM3D Forest Mask (2021) <br><em><strong>Coordinate Reference System</strong></em>: EPSG:2056 - CH1903+ / LV95, Swiss. Obl. Mercator<br><br>*:<em> NDVI Difference Values (-1 to 1) are multiplied by 10'000 to allow using Integer 16 bit vs. Float 32 bit while maintaining a precision of 5 digits. The values have to be interpreted accordingly: -10'000 means an NDVI difference of -1, +10'000 an NDVI difference of +0.<br><br></em></p> <p>The NDVI difference rasters for annual forest change in Switzerland are created by using Sentinel 2 based NDVI composites (Normalized Difference Vegetation Index). The code for the generating method can be found in the <a href="https://github.com/HAFL-WWI/Digital-Forest-Monitoring/tree/main/methods/use-case1">waldmonitoring-repository</a>, the method itself is also described and translated in further detail in the <a href="https://wiki.waldmonitoring.ch/index.php/Use_Case_1_-_J%C3%A4hrliche_Waldver%C3%A4nderungen">corresponding waldmonitoring-wiki</a>: For the automatic detection of areas of change, the differences between two years were examined using the NDVI. In order to automatically filter out cloudy images, the maximum NDVI value of all available images of the summer months (June - August) was used for each pixel (10 x 10 m). During this time, practically all the vegetation is green. This results in almost cloud-free, annual raster images with the maximum NDVI ("NDVI maximum composite"). The difference between two years is formed from these composites. The difference values accordingly reflect the strength of the change. </p> <p>As an example for interpretation, values of -0.1 or smaller (closer to -1.0) indicate strong forest changes (e.g. clearing), whereas positive values indicate vegetation regeneration or re-greening of previously unvegetated areas. Using a threshold value (we suggest -0.06 for forest applications), areas with considerable negative change can be separated out and be vectorized (converted to polygons) to create a dataset that can be queried.</p>
Images and 2-class labels for semantic segmentation of Sentinel-2 and Landsat RGB satellite images of coasts (water, other)
<p><em><strong>Images and 2-class labels for semantic segmentation of Sentinel-2 and Landsat RGB satellite images of coasts (water, other)</strong></em></p> <p>Images and 2-class labels for semantic segmentation of Sentinel-2 and Landsat RGB satellite images of coasts (water, other)</p> <p><strong>Description</strong></p> <p>4088 images and 4088 associated labels for semantic segmentation of Sentinel-2 and Landsat RGB satellite images of coasts. The 2 classes are 1=water, 0=other. Imagery are a mixture of 10-m Sentinel-2 and 15-m pansharpened Landsat 7, 8, and 9 visible-band imagery of various sizes. Red, Green, Blue bands only</p> <p>These images and labels could be used within numerous Machine Learning frameworks for image segmentation, but have specifically been made for use with the Doodleverse software package, Segmentation Gym**.</p> <p>Two data sources have been combined</p> <p><strong>Dataset 1</strong></p> <ul> <li>1018 image-label pairs from the following data release**** https://doi.org/10.5281/zenodo.7335647</li> <li>Labels have been reclassified from 4 classes to 2 classes.</li> <li>Some (422) of these images and labels were originally included in the Coast Train*** data release, and have been modified from their original by reclassifying from the original classes to the present 2 classes.</li> <li>These images and labels have been made using the Doodleverse software package, Doodler*.</li> </ul> <p><strong>Dataset 2</strong></p> <ul> <li>3070 image-label pairs from the Sentinel-2 Water Edges Dataset (SWED)***** dataset, https://openmldata.ukho.gov.uk/, described by Seale et al. (2022)******</li> <li>A subset of the original SWED imagery (256 x 256 x 12) and labels (256 x 256 x 1) have been chosen, based on the criteria of more than 2.5% of the pixels represent water</li> </ul> <p><strong>File descriptions</strong></p> <ul> <li> classes.txt, a file containing the class names</li> <li> images.zip, a zipped folder containing the 3-band RGB images of varying sizes and extents</li> <li> labels.zip, a zipped folder containing the 1-band label images</li> <li> overlays.zip, a zipped folder containing a semi-transparent overlay of the color-coded label on the image (red=1=water, bllue=0=other)</li> <li> resized_images.zip, RGB images resized to 512x512x3 pixels</li> <li> resized_labels.zip, label images resized to 512x512x1 pixels</li> </ul> <p><strong>References</strong></p> <p>*Doodler: Buscombe, D., Goldstein, E.B., Sherwood, C.R., Bodine, C., Brown, J.A., Favela, J., Fitzpatrick, S., Kranenburg, C.J., Over, J.R., Ritchie, A.C. and Warrick, J.A., 2021. Human‐in‐the‐Loop Segmentation of Earth Surface Imagery. Earth and Space Science, p.e2021EA002085https://doi.org/10.1029/2021EA002085. See https://github.com/Doodleverse/dash_doodler.</p> <p>**Segmentation Gym: Buscombe, D., & Goldstein, E. B. (2022). A reproducible and reusable pipeline for segmentation of geoscientific imagery. Earth and Space Science, 9, e2022EA002332. https://doi.org/10.1029/2022EA002332 See: https://github.com/Doodleverse/segmentation_gym</p> <p>***Coast Train data release: Wernette, P.A., Buscombe, D.D., Favela, J., Fitzpatrick, S., and Goldstein E., 2022, Coast Train--Labeled imagery for training and evaluation of data-driven models for image segmentation: U.S. Geological Survey data release, https://doi.org/10.5066/P91NP87I. See https://coasttrain.github.io/CoastTrain/ for more information</p> <p>****Buscombe, Daniel, Goldstein, Evan, Bernier, Julie, Bosse, Stephen, Colacicco, Rosa, Corak, Nick, Fitzpatrick, Sharon, del Jesús González Guillén, Anais, Ku, Venus, Paprocki, Julie, Platt, Lindsay, Steele, Bethel, Wright, Kyle, & Yasin, Brandon. (2022). Images and 4-class labels for semantic segmentation of Sentinel-2 and Landsat RGB satellite images of coasts (water, whitewater, sediment, other) (v1.0) [Data set]. Zenodo. https://doi.org/10.5281/zenodo.7335647</p> <p>*****Seale, C., Redfern, T., Chatfield, P. 2022. Sentinel-2 Water Edges Dataset (SWED) https://openmldata.ukho.gov.uk/</p> <p>******Seale, C., Redfern, T., Chatfield, P., Luo, C. and Dempsey, K., 2022. Coastline detection in satellite imagery: A deep learning approach on new benchmark data. Remote Sensing of Environment, 278, p.113044.</p>
Doodleverse/Segmentation Zoo Res-UNet models for 2-class (water, other) segmentation of Sentinel-2 and Landsat-7/8 3-band (RGB) images of coasts.
<p><em><strong>Doodleverse/Segmentation Zoo Res-UNet models for 2-class (water, other) segmentation of Sentinel-2 and Landsat-7/8 3-band (RGB) images of coasts.</strong></em></p> <p>These Residual-UNet model data are based on RGB (red, green, and blue) images of coasts and associated labels.</p> <p>Models have been created using Segmentation Gym* using the following dataset**: <a href="https://doi.org/10.5281/zenodo.7384242">https://doi.org/10.5281/zenodo.7384242</a></p> <p>Classes: {0=other, 1=water}</p> <p><strong>File descriptions</strong></p> <p>For each model, there are 5 files with the same root name:</p> <p>1. <strong>'.json' </strong>config file: this is the file that was used by Segmentation Gym* to create the weights file. It contains instructions for how to make the model and the data it used, as well as instructions for how to use the model for prediction. It is a handy wee thing and mastering it means mastering the entire Doodleverse.</p> <p>2.<strong> '.h5'</strong> weights file: this is the file that was created by the Segmentation Gym* function `train_model.py`. It contains the trained model's parameter weights. It can called by the Segmentation Gym* function `seg_images_in_folder.py`. Models may be ensembled.</p> <p>3.<strong> '_modelcard.json'</strong> model card file: this is a json file containing fields that collectively describe the model origins, training choices, and dataset that the model is based upon. There is some redundancy between this file and the `config` file (described above) that contains the instructions for the model training and implementation. The model card file is not used by the program but is important metadata so it is important to keep with the other files that collectively make the model and is such is considered part of the model</p> <p>4. <strong> '_model_history.npz'</strong> model training history file: this numpy archive file contains numpy arrays describing the training and validation losses and metrics. It is created by the Segmentation Gym function `train_model.py`</p> <p>5. <strong> '.png'</strong> model training loss and mean IoU plot: this png file contains plots of training and validation losses and mean IoU scores during model training. A subset of data inside the .npz file. It is created by the Segmentation Gym function `train_model.py`</p> <p>Additionally, BEST_MODEL.txt contains the name of the model with the best validation loss and mean IoU</p> <p> </p> <p><strong>References</strong></p> <p>*Segmentation Gym: Buscombe, D., & Goldstein, E. B. (2022). A reproducible and reusable pipeline for segmentation of geoscientific imagery. Earth and Space Science, 9, e2022EA002332. <a href="https://doi.org/10.1029/2022EA002332">https://doi.org/10.1029/2022EA002332</a> See: <a href="https://github.com/Doodleverse/segmentation_gym">https://github.com/Doodleverse/segmentation_gym</a></p> <p>** Buscombe, D. (2022). Images and 2-class labels for semantic segmentation of Sentinel-2 and Landsat RGB satellite images of coasts (water, other) (v1.0) [Data set]. Zenodo. <a href="https://doi.org/10.5281/zenodo.7384242">https://doi.org/10.5281/zenodo.7384242</a></p>
Sentinel-5P Tropospheric Nitrogen Dioxide Density at 2 km from 2018-05 to 2022-11 Monthly Aggregation
<p>Layers include: Tropospheric Nitrogen Dioxide Density monthly median value May 2018 – November 2022. Derived using the <a href="https://eumap.readthedocs.io/en/latest/index.html#">eumap package in Python</a>. We derived three standard statistics: (1) 10th percentile (p10), median (m), and 90th percentile (p10).</p> <p>Band info</p> <table> <tbody> <tr> <td>Name</td> <td>Units</td> <td>Scale</td> <td> <p>Description</p> </td> </tr> <tr> <td>NO<sub>2</sub></td> <td>(µmol m<sup>-</sup><sup>2</sup>)</td> <td>0.1</td> <td>tropospheric nitrogen dioxide density</td> </tr> </tbody> </table> <p>Warning:</p> <p>Original data have the different range of latitude among months. In December, there are no data above N 58°, where is approximately between Iceland and Scotland. Therefore, when it comes to monthly aggregation, there is a strip across N 58° as an artifact. It is not suggested to use this dataset in the region above N 58°.</p> <p>For more info about the s5p NO<sub>2</sub> product see: <a href="https://maps.s5p-pal.com"><strong>https://maps.s5p-pal.com/</strong></a>. Antarctica is not included.</p> <p>To access and visualize maps use: <a href="http://www.openlandmap.org/">OpenLandMap.org</a></p> <p>If you discover a bug, artifact or inconsistency, or if you have a question please use some of the following channels:</p> <ul> <li>Technical issues and questions about the code: <a href="https://gitlab.com/openlandmap/global-layers/-/issues">https://gitlab.com/openlandmap/global-layers/-/issues</a> </li> <li>General questions and comments: <a href="https://disqus.com/home/forums/landgis/">https://disqus.com/home/forums/landgis/</a></li> </ul> <p>All files internally compressed using "COMPRESS=DEFLATE" creation option in GDAL in Cloud Optimised GeoTiff (COG). File naming convention:</p> <ul> <li>no2 = variable: nitrogen dioxide (µmol m<sup>-</sup><sup>2</sup>),</li> <li>s5p.l3.trop.tmwm= determination method: Copernicus Sentinel-5P product, level 3, tropospheric, temporal moving window median</li> <li>p10/p50/p90 = aggregation/statistics method: 10th/50th/90th percentile,</li> <li>2km = spatial resolution / block support: 2 km,</li> <li>a = vertical reference: above ground,</li> <li>start date_end date (i.e. 20180501_20180531) = time reference: from start date to end date</li> <li>go = bounding box: global land without Antarctica</li> <li>epsg.4326 = ESPG code: epsg.4326</li> <li>v20221219 = version code: creation date 20221219</li> </ul>
Doodleverse/Segmentation Zoo Res-UNet models for 2-class (water, other) segmentation of Sentinel-2 and Landsat-7/8 1-band NDWI images of coasts.
<p><em><strong>Doodleverse/Segmentation Zoo Res-UNet models for 2-class (water, other) segmentation of Sentinel-2 and Landsat-7/8 1-band NDWI images of coasts.</strong></em></p> <p>These Residual-UNet model data are based on NDWI images of coasts and associated labels.</p> <p>Models have been created using Segmentation Gym* using the following dataset**: <a href="https://doi.org/10.5281/zenodo.7384263">https://doi.org/10.5281/zenodo.7384263 </a></p> <p>Classes: {0=other, 1=water}</p> <p><strong>File descriptions</strong></p> <p>For each model, there are 5 files with the same root name:</p> <p>1. <strong>'.json' </strong>config file: this is the file that was used by Segmentation Gym* to create the weights file. It contains instructions for how to make the model and the data it used, as well as instructions for how to use the model for prediction. It is a handy wee thing and mastering it means mastering the entire Doodleverse.</p> <p>2.<strong> '.h5'</strong> weights file: this is the file that was created by the Segmentation Gym* function `train_model.py`. It contains the trained model's parameter weights. It can called by the Segmentation Gym* function `seg_images_in_folder.py`. Models may be ensembled.</p> <p>3.<strong> '_modelcard.json'</strong> model card file: this is a json file containing fields that collectively describe the model origins, training choices, and dataset that the model is based upon. There is some redundancy between this file and the `config` file (described above) that contains the instructions for the model training and implementation. The model card file is not used by the program but is important metadata so it is important to keep with the other files that collectively make the model and is such is considered part of the model</p> <p>4. <strong> '_model_history.npz'</strong> model training history file: this numpy archive file contains numpy arrays describing the training and validation losses and metrics. It is created by the Segmentation Gym function `train_model.py`</p> <p>5. <strong> '.png'</strong> model training loss and mean IoU plot: this png file contains plots of training and validation losses and mean IoU scores during model training. A subset of data inside the .npz file. It is created by the Segmentation Gym function `train_model.py`</p> <p>Additionally, BEST_MODEL.txt contains the name of the model with the best validation loss and mean IoU</p> <p> </p> <p><strong>References</strong></p> <p>*Segmentation Gym: Buscombe, D., & Goldstein, E. B. (2022). A reproducible and reusable pipeline for segmentation of geoscientific imagery. Earth and Space Science, 9, e2022EA002332. <a href="https://doi.org/10.1029/2022EA002332">https://doi.org/10.1029/2022EA002332</a> See: <a href="https://github.com/Doodleverse/segmentation_gym">https://github.com/Doodleverse/segmentation_gym</a></p> <p>** Buscombe, Daniel. (2022). Images and 2-class labels for semantic segmentation of Sentinel-2 and Landsat RGB, NIR, and SWIR satellite images of coasts (water, other) (v1.0) [Data set]. Zenodo. <a href="https://doi.org/10.5281/zenodo.7384263">https://doi.org/10.5281/zenodo.7384263 </a></p>
Doodleverse/Segmentation Zoo Res-UNet models for 2-class (water, other) segmentation of Sentinel-2 and Landsat-7/8 1-band MNDWI images of coasts.
<p><em><strong>Doodleverse/Segmentation Zoo Res-UNet models for 2-class (water, other) segmentation of Sentinel-2 and Landsat-7/8 1-band MNDWI images of coasts.</strong></em></p> <p>These Residual-UNet model data are based on MNDWI images of coasts and associated labels.</p> <p>Models have been created using Segmentation Gym* using the following dataset**: <a href="https://doi.org/10.5281/zenodo.7384263">https://doi.org/10.5281/zenodo.7384263 </a></p> <p>Classes: {0=other, 1=water}</p> <p><strong>File descriptions</strong></p> <p>For each model, there are 5 files with the same root name:</p> <p>1. <strong>'.json' </strong>config file: this is the file that was used by Segmentation Gym* to create the weights file. It contains instructions for how to make the model and the data it used, as well as instructions for how to use the model for prediction. It is a handy wee thing and mastering it means mastering the entire Doodleverse.</p> <p>2.<strong> '.h5'</strong> weights file: this is the file that was created by the Segmentation Gym* function `train_model.py`. It contains the trained model's parameter weights. It can called by the Segmentation Gym* function `seg_images_in_folder.py`. Models may be ensembled.</p> <p>3.<strong> '_modelcard.json'</strong> model card file: this is a json file containing fields that collectively describe the model origins, training choices, and dataset that the model is based upon. There is some redundancy between this file and the `config` file (described above) that contains the instructions for the model training and implementation. The model card file is not used by the program but is important metadata so it is important to keep with the other files that collectively make the model and is such is considered part of the model</p> <p>4. <strong> '_model_history.npz'</strong> model training history file: this numpy archive file contains numpy arrays describing the training and validation losses and metrics. It is created by the Segmentation Gym function `train_model.py`</p> <p>5. <strong> '.png'</strong> model training loss and mean IoU plot: this png file contains plots of training and validation losses and mean IoU scores during model training. A subset of data inside the .npz file. It is created by the Segmentation Gym function `train_model.py`</p> <p>Additionally, BEST_MODEL.txt contains the name of the model with the best validation loss and mean IoU</p> <p> </p> <p><strong>References</strong></p> <p>*Segmentation Gym: Buscombe, D., & Goldstein, E. B. (2022). A reproducible and reusable pipeline for segmentation of geoscientific imagery. Earth and Space Science, 9, e2022EA002332. <a href="https://doi.org/10.1029/2022EA002332">https://doi.org/10.1029/2022EA002332</a> See: <a href="https://github.com/Doodleverse/segmentation_gym">https://github.com/Doodleverse/segmentation_gym</a></p> <p>** Buscombe, Daniel. (2022). Images and 2-class labels for semantic segmentation of Sentinel-2 and Landsat RGB, NIR, and SWIR satellite images of coasts (water, other) (v1.0) [Data set]. Zenodo. <a href="https://doi.org/10.5281/zenodo.7384263">https://doi.org/10.5281/zenodo.7384263 </a></p>
Doodleverse/Segmentation Zoo Res-UNet models for 2-class (water, other) segmentation of Sentinel-2 and Landsat-7/8 3-band (RGB) images of coasts.
<p><em><strong>Doodleverse/Segmentation Zoo Res-UNet models for 2-class (water, other) segmentation of Sentinel-2 and Landsat-7/8 3-band (RGB) images of coasts.</strong></em></p> <p><em><strong>Version 3: Updated 2023-04-25</strong></em></p> <p>These Residual-UNet model data are based on RGB (red, green, and blue) images of coasts and associated labels.</p> <p>Models have been created using Segmentation Gym* using the following dataset**: <a href="https://doi.org/10.5281/zenodo.7384242">https://doi.org/10.5281/zenodo.7384242</a></p> <p>Classes: {0=other, 1=water}</p> <p><strong>File descriptions</strong></p> <p>For each model, there are 5 files with the same root name:</p> <p>1. <strong>'.json' </strong>config file: this is the file that was used by Segmentation Gym* to create the weights file. It contains instructions for how to make the model and the data it used, as well as instructions for how to use the model for prediction. It is a handy wee thing and mastering it means mastering the entire Doodleverse.</p> <p>2.<strong> '.h5'</strong> weights file: this is the file that was created by the Segmentation Gym* function `train_model.py`. It contains the trained model's parameter weights. It can called by the Segmentation Gym* function `seg_images_in_folder.py`. Models may be ensembled.</p> <p>3.<strong> '_modelcard.json'</strong> model card file: this is a json file containing fields that collectively describe the model origins, training choices, and dataset that the model is based upon. There is some redundancy between this file and the `config` file (described above) that contains the instructions for the model training and implementation. The model card file is not used by the program but is important metadata so it is important to keep with the other files that collectively make the model and is such is considered part of the model</p> <p>4. <strong> '_model_history.npz'</strong> model training history file: this numpy archive file contains numpy arrays describing the training and validation losses and metrics. It is created by the Segmentation Gym function `train_model.py`</p> <p>5. <strong> '.png'</strong> model training loss and mean IoU plot: this png file contains plots of training and validation losses and mean IoU scores during model training. A subset of data inside the .npz file. It is created by the Segmentation Gym function `train_model.py`</p> <p>Additionally, BEST_MODEL.txt contains the name of the model with the best validation loss and mean IoU</p> <p> </p> <p><strong>References</strong></p> <p>*Segmentation Gym: Buscombe, D., & Goldstein, E. B. (2022). A reproducible and reusable pipeline for segmentation of geoscientific imagery. Earth and Space Science, 9, e2022EA002332. <a href="https://doi.org/10.1029/2022EA002332">https://doi.org/10.1029/2022EA002332</a> See: <a href="https://github.com/Doodleverse/segmentation_gym">https://github.com/Doodleverse/segmentation_gym</a></p> <p>** Buscombe, D. (2022). Images and 2-class labels for semantic segmentation of Sentinel-2 and Landsat RGB satellite images of coasts (water, other) (v1.0) [Data set]. Zenodo. <a href="https://doi.org/10.5281/zenodo.7384242">https://doi.org/10.5281/zenodo.7384242</a></p>
Harmonized Chlorophyll-a dataset from Landsat-8/9 OLI and Sentinel 2 MSI in lakes of the Yunnan-guizhou Plateau, China
<p>We generated a harmonized Chl-a dataset for the lakes in the Yunnan–Guizhou Plateau in China from 2013 to 2022 by the Landsat 8/9 and Sentinel-2A/B virtual constellation. Here, we shared the mean chlorophyll-a in nine major lakes in studied area. </p><p>These dataset were aggregated from MSI- and OLI-derived Chl-a images and were subseted using the boundary of each lake. Data format is Geo-Tiff (*.tif) and zero values are INVALID values. More details on Chl-a retrievals can be found in: </p><p>Z. Cao et al., "Harmonized Chlorophyll-a Retrievals in Inland Lakes From Landsat-8/9 and Sentinel 2A/B Virtual Constellation Through Machine Learning," in IEEE Transactions on Geoscience and Remote Sensing, vol. 60, pp. 1-16, 2022, Art no. 4209916, doi: 10.1109/TGRS.2022.3207345.</p>
Central and Eastern Himalaya glacier velocities 2017-2019 (Sentinel 2)
<p> </p> <p>This dataset contains the median glacier surface velocity for the Central and Eastern Himalaya glacier velocities 2017-2019 (Sentinel 2). The velocities have been obtained by feature-tracking of November Sentinel 2 images spaced 1 year apart.</p> <p>The folder contains the following fields at 80 m resolution in GeoTiff format:</p> <ul> <li>the velocity magnitude 'vel' (meters per year)</li> <li>the x/y velocity components x_vel/y_vel (meters per year)</li> <li>the associated errors err, x_err, y_err (meters per year)</li> <li>the median absolute deviation of all the merged velocities 'MAD' (meters per year)</li> <li>the number of image pairs that have been merged in the median</li> </ul> <p>I recommend filtering data with error larger than 5 m/yr.</p> <p> </p> <table> <caption>Metadata Properties</caption> <tbody> <tr> <td>CRS</td> <td>EPSG:32645 - WGS 84 / UTM zone 45N - Projected</td> </tr> <tr> <td>Extent</td> <td>9425.6070999999992637,3045085.1858000000938773 : 883803.9936000000452623,3368628.0986000001430511</td> </tr> <tr> <td>Unit</td> <td>meters</td> </tr> <tr> <td>Width</td> <td>11192</td> </tr> <tr> <td>Height</td> <td>3981</td> </tr> <tr> <td>Data type</td> <td>Float32 - Thirty two bit floating point</td> </tr> </tbody> </table> <p> </p>
Sentinel 2 meltpond volume
<p>Melt pond volumes based on the threshold-based method for lake detection/volume of Moussavi et al., 2020, to 19213 Sentinel-1 Level-1C top-of-atmosphere reflectance granules with less than 30% cloud cover and solar elevation angles above 25 degrees over all Antarctic ice shelves and the surrounding ice sheet. Each granule is processed in the Google Earth Engine at 100 m resampled resolution and converted into lake presence and lake depth. The depth observations were subsequently converted into total accumulated meltwater volumes per lake (in meter water equivalent) by integrating the derived lake depths per pixel over all granules. The resulting melt pond volume dataset (this repository) is then aggregated on the 27 km RACMO2.3p2 grid, accumulating the melt ponds that fall within one model grid cell.</p> <p>Original lake volumes per pixel are available through https://code.earthengine.google.com/?asset=projects/ee-earthmapps/assets/S2_LakesAntarctica_v3</p>
Subset of 300 out of 3000 Prepared Sentinel 2 Scenes for Transfer Learning and Super-sampling.
<p>This dataset contains a random subset of 300 out of 3000 Sentinel 2 scenes prepared for Transfer Learning and Super-sampling. It comes in the form of zipped NumPy arrays in the npz format. The files have are named in the following fashion:</p> <p>latutide+latitude_decimals_longitude+longitude_decimals_month_of_the_year_for_mosaic. </p> <p>Each file contains:</p> <p>bands.npy: The Sentinel 2 bands in 10m resolution uint10: B02, B03, B04, B08, B05, B06, B07, B8A, B11, B12. The 20m bands have been resampled using bilinear resampling.</p> <p>nir.npy: B08 Resampled to 20m using average resampling and then resampled to 10m using bilinear. Useful for training super-sampling models.</p> <p>scl.npy: The Sentinel 2 Scene Classification file. Contains information on cloud cover and land cover.</p> <p>sincos.npy: Contains the latitude, longitude, and time of capture for each pixel encoded to sine and cosine waves in the [0,1] interval. The is useful when training a model to predict where on the globe an image was captured.</p> <p>The images can be processed to patches using the buteo toolbox: </p> <p>`pip install buteo --upgrade</p> <p>`import buteo as beo`</p> <p>`beo.get_patches(beo.raster_to_array("path_to_bands"))`</p> <p> </p>
Figure 4. A - Sentinel 2 in Perception of Amazonian fishers regarding environmental changes as causes of drastic events of fish mortality
Figure 4. A - Sentinel 2 satellite image of Lago do Rei on 20th November 2018. B - Sentinel 2 satellite image of the Lago do Rei on 20th June 2018. C - Sentinel 2 satellite image of the Lago do Rei on 15th November 2019. D - Sentinel 2 satellite image of Lago do Rei on 6th January 2020.
Fig. 2 in Monitoring the establishment and flight phenology of parasitoids of emerald ash borer (Coleoptera: Buprestidae) in Michigan by using sentinel eggs and larvae
Fig. 2. Percentage of parasitism by Tetrastichus planipennisi of emerald ash borer larvae in larval sentinel logs (pooled by sample date, i.e., the date that larval sentinel logs were collected) in Nancy Moore and Burchfield Parks, Michigan, in (A) 2011, (C) 2012, and (E) 2013, and by Atanycolus spp. in (B) 2011, (D) 2012, and (F) 2013. The secondary Y-axis is growing degree day base 10 °C (GDD10) using the Baskerville–Emin method.
Fig. 2 in Exposure of yellow-legged gulls to Toxoplasma gondii along the Western Mediterranean coasts: Tales from a sentinel
Fig. 2. Limited temporal variations of the prevalence of anti-T. gondii antibody in yellow-legged gull egg yolk samples between 2009 and 2016 in three colonies: Frioul, Gruissan and Medes Islands. Curves correspond to cubic splined fitted to the yearly prevalences for visualisation purposes only. Bars indicate 95% Clopper-Pearson confidence intervals. (For interpretation of the references to colour in this figure legend, the reader is referred to the Web version of this article.)
Fig. 2 in Wild pigs as sentinels for hard ticks: A case study from south-central Florida
Fig. 2. Mean intensity of infestation of adult ticks collected from wild pigs from May 22, 2015 to May 09, 2017. Ticks which could not be identified to species were excluded from this figure. Values of zero indicate that wild pigs were sampled during that month, but no adults of the indicated species were collected.
Subpixel offsets of Copernicus Sentinel 2 data, related to the displacement field of the Sulawesi Earthquake (2018, Mw 7.5)
<p><a href="https://en.wikipedia.org/wiki/Sulawesi">Sulawesi</a> lies within a complex fault system located between the <a href="https://en.wikipedia.org/wiki/Australian_Plate">Australian</a>, <a href="https://en.wikipedia.org/wiki/Pacific_Plate">Pacific</a>, <a href="https://en.wikipedia.org/wiki/Philippine_Sea_Plate">Philippine</a> and <a href="https://en.wikipedia.org/wiki/Sunda_Plate">Sunda Plates</a>. The main active structure onshore at the western part of Central Sulawesi is the left-lateral NNW-SSE trending <a href="https://en.wikipedia.org/wiki/Palu-Koro_fault">Palu-Koro</a> <a href="https://en.wikipedia.org/wiki/Strike-slip_Fault">strike-slip fault</a> that forms the boundary between the North Sula and Makassar blocks. On 28 September 2018, a large tsunamigenic <a href="https://en.wikipedia.org/wiki/Earthquake">earthquake</a> (Mw 7.5) struck the <a href="https://en.wikipedia.org/wiki/Minahasa_Peninsula">Minahasa Peninsula</a>, Indonesia. The earthquake caused massive damages near Palu city, including onshore gravitational instabilities and a tsunami.</p> <p>These data are the result of subpixel image correlation on Copernicus Sentinel-2 data (17 September 2018 and 2 October 2018) to derive the two-dimensional (East-West and North-South) horizontal co-seismic displacement field. In these data, the displacement field is expressed in meters. These results show a dominant senextral strike-slip motion on the onshore part of the Palu-Koro fault. Maximum displacement at the surface reached more than 8 meters at the location of Palu city. Processing is performed with COSI-CORR (Leprince et al., 2007). Data value higher than | 10 | meters should be considered as noise and disregarded. I used a correlation window size of 32 pixels with a sampling step of 16 pixels. A ramp has been removed from (separately) the North-South offsets and from the East-West offsets. The files are rasters of floating point values, served with a header file readable by ENVI software.</p> <p>Sign conventions:</p> <p>-North-South offsets: positive values to the North.</p> <p>- East-West offsets: positive values to the West.</p> <p> </p> <p><a href="http://www.esa.int/spaceinimages/Images/2018/10/Indonesia_earthquake_displacement_data">http://www.esa.int/spaceinimages/Images/2018/10/Indonesia_earthquake_displacement_data</a></p> <p><strong>Copyright:</strong> Contains modified Copernicus Sentinel data (2018), processed at the French Geological Survey (BRGM)</p> <p> </p> <p> </p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.