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.
392
datasets available to search
ShareScore release 0.9.0
Dataset results
392 results for “streets”
Environmental Data for Soil, Leaf, and Root samples Boston Street Trees and Massachusetts Rural and Urban Forests in Summer 2021
This dataset provides detailed environmental and tree-level data and metadata for over 850 samples collected from 91 trees across an urban-to-rural gradient in Massachusetts. The dataset captures key variables characterizing urban environmental gradients, including soil moisture, pH, temperature, and nitrogen availability. Tree-level attributes include species identification, diameter at breast height (DBH), and growth rate based on previous tree census data. Geographic coordinates and site-specific context (urban forest, rural forest, street tree, forest edge, forest interior) are included to enable spatial analyses. The microbial sequence data associated with this environmental metadata can be found in the NCBI SRA under BioProject accession number PRJNA1297772.
Data from: Investigating the impact of street lighting changes on garden moth communities
<p>This data package accompanies:<br><em>Plummer et al (2016). Investigating the impact of street lighting changes on garden moth communities. Journal of Urban Ecology. DOI 10.1093/jue/juw004</em></p> <p>It contains a copy of the two derived datasets used to complete the analyses presented in the paper. File details:</p> <p><strong>1. ReadMe.txt: </strong>Includes a description of the variables included in each dataset.</p> <p><strong>2. Plummer_JUrbanEcol_2016_BACI_dataset.csv: </strong>A .csv file including two years (2011 & 2013) of macro-moth community data (abundance, richness, diversity) for 18 garden locations in Birmingham, UK. Data are summarised per garden and year, together with data for proximity to street lamp replacement.</p> <p><strong>3. Plummer_JUrbanEcol_2016_light_composition_dataset.csv:</strong> A .csv file including one year (2013) of garden moth community data (abundance, richness, diversity; including macro- and micro-moths) for 18 garden locations in Birmingham, UK. Data are summarised per trapping event, together with associated street lighting and habitat characteristics for each garden. </p> <p>We would also greatly appreciate if you could fill out <a href="https://forms.gle/DCc58VXpdmqnTmTk8" target="_blank" rel="noopener">this very short form</a> to tell us how you intend to use these data. Thanks in advance!</p>
# Replication code and data for: Tracking green space along streets of world cities
<p># Replication code and data for: Tracking green space along streets of world cities<br>Falchetta, G., & Hammad, A. T. (2025). Tracking green space along streets of world cities. Environmental Research: Infrastructure and Sustainability. https://doi.org/10.1088/2634-4505/add9c4 </p> <p>The file "gvi_358cities_2016_2023_yearly_falchetta_hammad.csv" contains<strong> output data</strong>, reporting sampling-point level data on the yearly (2016-2023) values of the Green View Index for the 190 cities covered in the paper AND an additional number of world cities (for a total of 358 cities). The "README_gvi_358cities_2016_2023_yearly_falchetta_hammad.txt" file contains a dictionary of each column name and units. </p> <p>____<br><br></p> <p>To replicate the analysis, the results, and the figures of the paper:</p> <ul> <li>Download input data from this Zenodo repository and code from Github https://github.com/giacfalk/urban_green_space_mapping_and_tracking</li> <li><em>*Optional data extraction steps* </em>(processed output data are already available in the Zenodo repository):<br> <ul> <li>Adjust your working directory</li> <li>Run [lines 4-11] of workflow/sourcer.R</li> <li>Run the Javascript scripts written by the string_generator_training.R and string_generator_prediction.R files in Google Earth Engine (https://code.earthengine.google.com) and complete the export to Drive tasks to generate the output .csv files</li> </ul> </li> <li>Run workflow/sourcer.R [lines 15-46] to train the ML model and make predictions (including figures and tables replication)</li> </ul> <div> <div> <div> </div> <div> <div> <div> </div> <div> <p dir="auto"> </p> <p dir="auto"> </p> </div> </div> </div> </div> </div> <div> <div> <div> </div> <div> <div> <div> </div> <div> <p dir="auto"> </p> <p dir="auto"> </p> </div> </div> </div> </div> </div>
Longitudinal urban form dataset of Midtown Manhattan: Measuring urban form evolution via quantitative descriptions of plots, buildings and streets from 1890 to the present
<p>This dataset contains data described and used in the research article <strong>"The impact of urban form on physical change: A quantitative and diachronic analysis of urban form evolution in Midtown Manhattan"</strong>. </p> <p>The longitudinal dataset contains urban form data on nearly 17,000 individual plots (parcels) in Midtown Manhattan, documented through four subsequent time frames: 1890, 1920, 1956 and 2021. The data was compiled from historical cartographic resources and open-access geospatial datasets listed in the ReadMe file. </p> <p>The dataset includes an array of quantitative descriptions of plots, buildings and streets central to the field of urban morphology, and the binary information of physical change (1: change, 0: no change) identified via diachronic comparison of each time frame at the scale of plots.</p> <p> </p> <p><strong>Acknowledgements</strong></p> <p>The dataset presented in this repository has been generated as part of a PhD research conducted at the University of Melbourne, Faculty of Architecture, Building and Planning and funded by the University of Melbourne - Melbourne Research Scholarship: </p> <p><strong>Tümtürk, O</strong>. (2024). <strong>A data-driven investigation on urban form evolution: Methodological and empirical support for unravelling the relation between urban form and spatial dynamics</strong>. Unpublished PhD Thesis. The University of Melbourne, Australia. </p>
Density Layers of selected Points of Interest from Open Street Map
<p>This dataset contains a raster layer of 100*100m resolution showing the density of selected amenities from Open Street Map. The amenities are selected as points of interest, where electric vehicles owners are likely to stop for a moment and recharge their vehicles. This dataset covers Europe and was obtained with the Overpass API. This dataset can be used to identify possible charging location for electric vehicles or any other purpose requiring to quantify the number of amenities in an area.</p> <p> </p> <p>This dataset shows densities of a selection of Points of Interest in Europe from Open Street Map [1].</p> <p>Included countries are:</p> <p> </p> <p><em><strong>country_codes</strong> = ['AT', 'BE', 'BG', 'HR', 'CY', 'CZ', 'DK', 'EE', 'FI', 'FR', 'DE', 'GR', 'HU', 'IE', 'IT','LV', 'LT', 'LU', 'MT', 'NL', 'PL', 'PT', 'RO', 'SK', 'SI', 'ES', 'SE', 'AL', 'AD', 'AM', 'BY', 'BA', 'FO', 'GE', 'GI', 'IS', 'IM', 'XK', 'LI', 'MK', 'MD', 'MC', 'ME', 'NO', 'SM', 'RS', 'CH', 'TR', 'UA', 'GB', 'VA']</em></p> <p> </p> <p>The requests of Points of Interest have been performed with the Overpass API [2] (free of charge).</p> <p> </p> <p>The codes included in each density are listed below :</p> <p> </p> <p><strong><em>'highway'</em></strong><em> = ['"highway"="motorway"', '"highway"="rest_area"'];</em></p> <p><strong><em>'parkings'</em></strong><em> = ['"parking"="surface"', '"parking"="multi-storey"', '"parking"="street_side"', '"parking"="underground"' , '"park_ride"' ];</em></p> <p><strong><em>'school'</em></strong><em> = ['"amenity"="college"', '"building"="college"', '"building"="university"', '"amenity"="university"', '"amenity"="school"' , '"amenity"="school"', '"amenity"="kindergarten"', '"amenity"="library"'];</em></p> <p><strong><em>'health'</em></strong><em>= ['"amenity"="clinic"', '"amenity"="dentist"', '"amenity"="school"' , '"amenity"="doctors"', '"amenity"="hospital"', '"amenity"="pharmacy"','"amenity"="veterinary"']; </em></p> <p><strong><em>'cafe'</em></strong><em>= ['"amenity"="cafe"','"amenity"="ice_cream"', '"amenity"="internet_cafe"']; </em></p> <p><strong><em>'supermarket'</em></strong><em> = ['"shop"="supermarket"', '"shop"="mall"', '"shop"= "department_store"', '"shop"= "convenience"'];</em></p> <p><strong><em>'restaurant'</em></strong><em>= ['"amenity"="restaurant"'];</em></p> <p><strong><em>'fastfood'</em></strong><em> = ['"amenity"="fast_food"'];</em></p> <p><strong><em>'sport'</em></strong><em>= ['"sport"']; </em></p> <p><strong><em>'hotel'</em></strong><em> = ['"tourism"="hotel"', '"building"="hotel"', '"tourism"="guest_house"','"tourism"="apartment"','"tourism"="hostel"','"tourism"="motel"','"tourism"="camp_site"']; </em></p> <p><strong><em>'pubs'</em></strong><em> = ['"amenity"="bar"','"amenity"="pub"', '"amenity"="biergarten"'];</em></p> <p><em>'theatre'= ['"amenity"="theatre"', '"amenity"="cinema"', '"amenity"="music_venue"', '"leisure"="stadium"' ]; </em></p> <p><strong><em>'night'</em></strong><em> = ['"amenity"="nightclub"', '"amenity"="casino"','"amenity"="gambling"','"amenity"="stripclub"']; </em></p> <p><strong><em>'socio'</em></strong><em>= ['"amenity"="arts_centre"', '"amenity"="community_centre"', '"amenity"="social_centre"', '"amenity"="music_school"', '"amenity"="language_school"']; </em></p> <p><strong><em>'shop'</em></strong><em> = ['"shop"'];</em></p> <p><strong><em>'tourism'</em></strong><em> = ['"amenity"="exhibition_centre"', '"tourism"="attraction"','"tourism"="viewpoint"','"tourism"="aquarium "','"leisure"="beach_resort "','"tourism"="gallery"','"tourism"="museum"','"tourism"="theme_park"','"tourism"="zoo"','"tourism"="artwork"'];</em></p> <p> </p> <p>The pixel values are the sum of the number of POIs of each type located in the pixel.</p> <p> </p> <p><em>Limitations of the dataset</em></p> <p>- The dataset provides densities of only a selection of points of interests, regardless of its type. The complete list of amenity codes can be found on the OSM Wiki [3].</p> <p>- Ways are only considered through their centre points.</p> <p> </p> <p>[1] “Open Street Map.” <a href="https://www.openstreetmap.org/">https://www.openstreetmap.org/</a> (accessed Sep. 05, 2023).</p> <p>[2] “Overpass API.” <a href="https://wiki.openstreetmap.org/wiki/Overpass_API">https://wiki.openstreetmap.org/wiki/Overpass_API</a> (accessed Sep. 05, 2023).</p> <p>[3] “Open Street Map Wiki.” <a href="https://wiki.openstreetmap.org/wiki/Key:amenity#Sustenance">https://wiki.openstreetmap.org/wiki/Key:amenity#Sustenance</a> (accessed Sep. 05, 2023).</p>
StreetSurfaceVis: a dataset of street-level imagery with annotations of road surface type and quality
<h1>StreetSurfaceVis</h1> <p><em>StreetSurfaceVis</em> is an image dataset containing <strong>9,122 street-level images from Germany</strong> with labels on <strong>road surface type and quality.</strong> The CSV file <code>streetSurfaceVis_v1_0.csv</code> contains all image metadata and four folders contain the image files. All images are available in four different sizes, based on the image width, in 256px, 1024px, 2048px and the original size.<br>Folders containing the images are named according to the respective image size. Image files are named based on the <code>mapillary_image_id</code>.</p> <p>You can find the corresponding publication here: <a href="https://www.nature.com/articles/s41597-024-04295-9#citeas">StreetSurfaceVis: a dataset of crowdsourced street-level imagery with semi-automated annotations of road surface type and quality</a></p> <p> </p> <h3>Image metadata</h3> <p>Each CSV record contains information about one street-level image with the following attributes:</p> <ul> <li><code>mapillary_image_id</code>: ID provided by Mapillary (see information below on Mapillary)</li> <li><code>user_id</code>: Mapillary user ID of contributor</li> <li><code>user_name</code>: Mapillary user name of contributor</li> <li><code>captured_at</code>: timestamp, capture time of image</li> <li><code>longitude</code>, <code>latitude</code>: location the image was taken at</li> <li><code>train</code>: Suggestion to split train and test data. `True` for train data and `False` for test data. Test data contains data from 5 cities which are excluded in the training data.</li> <li><code>surface_type</code>: Surface type of the road in the focal area (the center of the lower image half) of the image. Possible values: asphalt, concrete, paving_stones, sett, unpaved</li> <li><code>surface_quality</code>: Surface quality of the road in the focal area of the image. Possible values: (1) excellent, (2) good, (3) intermediate, (4) bad, (5) very bad (see the attached <strong>Labeling Guide document</strong> for details)</li> </ul> <p> </p> <h3>Image source</h3> <p>Images are obtained from <a href="https://www.mapillary.com/">Mapillary</a>, a crowd-sourcing plattform for street-level imagery. More metadata about each image can be obtained via the <a href="https://www.mapillary.com/developer/api-documentation">Mapillary API . </a>User-generated images are shared by Mapillary under the <a href="https://creativecommons.org/licenses/by-sa/4.0/">CC-BY-SA</a> License.</p> <p>For each image, the dataset contains the <code>mapillary_image_id</code> and <code>user_name</code>. <br>You can access user information on the Mapillary website by <code>https://www.mapillary.com/app/user/<USER_NAME> </code><br>and image information by <code>https://www.mapillary.com/app/?focus=photo&pKey=<MAPILLARY_IMAGE_ID></code></p> <p>If you use the provided images, please adhere to the <a href="https://www.mapillary.com/terms">terms of use of Mapillary.</a></p> <p> </p> <h3>Instances per class</h3> <p>Total number of images: 9,122</p> <table> <tbody> <tr> <td> </td> <td><strong>excellent</strong></td> <td><strong>good</strong></td> <td><strong>intermediate</strong></td> <td><strong>bad</strong></td> <td><strong>very bad</strong></td> </tr> <tr> <td><strong>asphalt</strong></td> <td>971</td> <td>1697</td> <td>821</td> <td>246</td> <td>-</td> </tr> <tr> <td><strong>concrete</strong></td> <td>314</td> <td>350</td> <td>250</td> <td>58</td> <td>-</td> </tr> <tr> <td><strong>paving stones</strong></td> <td>385</td> <td>1063</td> <td>519</td> <td>70</td> <td>-</td> </tr> <tr> <td><strong>sett</strong></td> <td>-</td> <td>129</td> <td>694</td> <td>540</td> <td>-</td> </tr> <tr> <td><strong>unpaved</strong></td> <td>-</td> <td>-</td> <td>326</td> <td>387</td> <td>303</td> </tr> </tbody> </table> <p> </p> <p>For modeling, we recommend using a train-test split where the test data includes geospatially distinct areas, thereby ensuring the model's ability to generalize to unseen regions is tested. We propose five cities varying in population size and from different regions in Germany for testing - images are tagged accordingly.</p> <p>Number of test images (train-test split): 776</p> <h3>Inter-rater-reliablility</h3> <p>Three annotators labeled the dataset, such that each image was annotated by one person. Annotators were encouraged to consult each other for a second opinion when uncertain.<br>1,800 images were annotated by all three annotators, resulting in a <em>Krippendorff's alpha</em> of 0.96 for surface type and 0.74 for surface quality.</p> <h3>Recommended image preprocessing</h3> <p>As the focal road located in the bottom center of the street-level image is labeled, it is recommended to crop images to their lower and middle half prior using for classification tasks.</p> <p>This is an exemplary code for recommended image preprocessing in <strong>Python</strong>:</p> <pre><code>from PIL import Image<br></code><code>img = Image.open(image_path)</code><br><code>width, height = img.size</code><br><code>img_cropped = img.crop((0.25 * width, 0.5 * height, 0.75 * width, height))</code></pre> <h3><br><strong>License</strong></h3> <p><a href="https://creativecommons.org/licenses/by-sa/4.0/">CC-BY-SA</a></p> <p> </p> <h3><strong>Citation</strong></h3> <p>If you use this dataset, please cite as: </p> <p> </p> <p>Kapp, A., Hoffmann, E., Weigmann, E. <em>et al.</em> StreetSurfaceVis: a dataset of crowdsourced street-level imagery annotated by road surface type and quality. <em>Sci Data</em> <strong>12</strong>, 92 (2025). https://doi.org/10.1038/s41597-024-04295-9</p> <p> </p> <p><code>@article{kapp_streetsurfacevis_2025,<br> title = {{StreetSurfaceVis}: a dataset of crowdsourced street-level imagery annotated by road surface type and quality},<br> volume = {12},<br> issn = {2052-4463},<br> url = {https://doi.org/10.1038/s41597-024-04295-9},<br> doi = {10.1038/s41597-024-04295-9},<br> pages = {92},<br> number = {1},<br> journaltitle = {Scientific Data},<br> shortjournal = {Scientific Data},<br> author = {Kapp, Alexandra and Hoffmann, Edith and Weigmann, Esther and Mihaljević, Helena},<br> date = {2025-01-16},<br>}</code></p> <p> </p> <p>-----------------------------------------------------------------------------------------------------------------------------------------------------------</p> <p>This is part of the SurfaceAI project at the University of Applied Sciences, HTW Berlin.</p> <p><br>- Prof. Dr. Helena Mihajlević<br>- Alexandra Kapp<br>- Edith Hoffmann<br>- Esther Weigmann</p> <p>Contact: surface-ai@htw-berlin.de</p> <p>https://surfaceai.github.io/surfaceai/</p> <p><strong>Funding</strong>: SurfaceAI is a mFund project funded by the Federal Ministry for Digital and Transportation Germany.</p> <p> </p>
Bounding box coordinates of von Karman vortex street
<p>Those files contain bounding box coordinates of von Karman vortex street annotated by VoTT. The von Karman vortex street is annotated as one object in vortex_street.tar.gz, while each vortex in the von Karman vortex street is annotated as one object in vortices.tar.gz. The original video file is from https://doi.org/10.1063/1.4921683.1 to 1.4921683.9. See also the reference.</p>
Capturing land cover and land use with street level imagery
<p>This dataset, collected in September 2018, contains street-level photographs captured by three cameras fixed on the roof of car. A field survey was focused in the Vojvodina, Serbia to more closely examine land cover/land use within croplands monitored by LandSense citizen scientists (March-September 2018).</p> <p>The dataset has the following characteristics:</p> <ul> <li>Time period of data collection: Sep 2018</li> <li>Total number of photographs: 26759</li> <li>Region of interest: Vojvodina - Ruma municipality (Serbia)</li> </ul> <p>Associated files: Serbia Streetlevelimagery2018 – Attributes.txt, Serbia Streetlevelimagery2018.csv, Serbia Streetlevelimagery2018.zip</p> <p>This dataset is licensed under a Creative Commons Attribution 4.0 International. It is attributed to the <a href="https://landsense.eu/">LandSense Citizen Observatory</a>, <a href="https://ec.europa.eu/jrc/en">Joint Research Centre</a> and <a href="https://inosens.rs/">InoSens</a>.</p> <p>This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement no 689812.</p>
NYU FloodSense street sign mounted distance sensor
<p>Ultrasonic distance data in mm from a sensor mounted on a street sign post at the corner of 5th Street and Hoyt, Brooklyn, NY (40.676640, -73.994595). The sensor is designed to detect flood water that fills the street and blocks vehicle and pedestrian traffic, as well as depositing micro-organisms on the street.</p> <p>The sensor transmits its data via LoRaWAN and is equipped with a solar panel for continuous operation.</p> <p>Data is collected at ~5min intervals. Time fields are in local time (New York).</p> <p>Two types of erroneous data has been observed:</p> <ul> <li>Large spikes in distance that always manifest at 5000mm - can be excluded</li> <li>There are ~1% rises in distance measures on days with sun which suggests that the distance sensor is affected by direct sunlight</li> </ul> <p>This data is prelimary and is for prototyping purposes. Not to be used as a reliable data source as it is.</p> <p>This dataset will be updated when more data is collected.</p> <p>Please see our github org for sensor information and build instructions: <a href="https://github.com/floodsense">github.com/floodsense</a></p>
NYU FloodSense street sign mounted flood depth sensor
<p>Water depth level in mm from a sensor mounted on a street sign post at the corner of 5th Street and Hoyt, Brooklyn, NY (40.676640, -73.994595). The sensor is designed to detect flood water that fills the street and blocks vehicle and pedestrian traffic, as well as depositing micro-organisms on the street. Ultrasonic technology is used to detect flood water depth.</p> <p>The sensor transmits its data via LoRaWAN and is equipped with a solar panel for continuous operation.</p> <p>Depth data is collected at ~5min intervals. Time fields are in local time (New York). Date format is: 2020-10-04 20:11:45.742594232-04:00</p> <p>Two flood events have been observed in this dataset between these date ranges:</p> <ol> <li> <p>"2020-11-15 19:37:00.000000000-05:00" to "2020-11-16 00:30:00.000000000-05:00"</p> </li> <li> <p>"2020-11-30 10:20:00.000000000-05:00" to "2020-11-30 13:30:00.000000000-05:00"</p> </li> </ol> <p>Erroneous data has been observed:</p> <ul> <li>There are ~1% decreases in depth measures on days with sun which suggests that the distance sensor is affected by direct sunlight</li> </ul> <p>This data is preliminary and is for prototyping purposes. </p> <p>This dataset will be updated when more data is collected.</p> <p>Please see our github org for sensor information and build instructions: <a href="https://github.com/floodsense">github.com/floodsense</a></p>
Dataset for the project "Evaluation of the effects of trace elements from street dust under urban – industrial conditions on the ecophysiology of Acer platanoides L. and Tilia cordata Mill.
<p>Description of the project: The rapid growth of cities, industry and transport has significantly deteriorated environmental quality, especially in areas with the highest population densities. It applies to water, soil, and air, especially in urban areas. Air pollutants include particulate matter (PM), which harms human health. According to WHO reports (2021), PM pollution is the cause of cardiovascular and respiratory diseases, leading to 4.2 million premature deaths worldwide in 2016. Although improving every year, the situation in Poland is still worse than in many European countries. The particulate matter also includes heavy metals, which have a toxic effect on plants. Plants in urban areas are particularly vulnerable, especially trees, which perform several vital functions, including mitigating climate change, filtering pollutants, and improving air quality. The aim of the project was to determine and compare the morphological and physiological responses of selected tree species to particulate pollution stress under urban conditions. Tree leaves are an essential barrier to atmospheric dust by trapping it on their surface. However, this may come at the cost of reduced light absorption, increased leaf temperature, damage to leaf blades and consequently impaired photosynthesis and plant productivity. However, the ability to absorb dust varies between tree species. It depends on the leaf surface structure, and the response may be due to the species' sensitivity to pollutants. Investigations were conducted in the Upper Silesian Industrial Area around various emission sources, such as heavy metal smelters, combined heat and power plants, and busy streets. The research focused on two tree species common in urban areas, the Norway maple (<i>Acer platanoides</i>) and the small-leaved lime (<i>Tilia cordata</i>). It included measurement of heavy metal concentrations in leaf blades and dust collected on their surface, analysis of concentrations of selected pigments and ascorbic acid as markers of environmental stress. The study provided a preliminary assessment of the impact of particulate pollution on tree function under harsh urban conditions and determined the potential of the studied species to reduce atmospheric dust.</p>
Dollar street 10 - 64x64x3
<p>The MLCommons Dollar Street Dataset is a collection of images of everyday household items from homes around the world that visually captures socioeconomic diversity of traditionally underrepresented populations. It consists of public domain data, licensed for academic, commercial and non-commercial usage, under CC-BY and CC-BY-SA 4.0. The dataset was developed because similar datasets lack socioeconomic metadata and are not representative of global diversity.</p> <p>This is a subset of the original dataset that can be used for multiclass classification with 10 categories. It is designed to be used in teaching, similar to the widely used, but unlicensed CIFAR-10 dataset.</p> <p>These are the preprocessing steps that were performed:</p> <ol> <li>Only take examples with one imagenet_synonym label</li> <li>Use only examples with the 10 most frequently occuring labels</li> <li>Downscale images to 64 x 64 pixels</li> <li>Split data in train and test</li> <li>Store as numpy array</li> </ol> <p>This is the label mapping:</p> <table> <tbody> <tr> <td><strong>Category</strong></td> <td><strong>label</strong></td> </tr> <tr> <td>day bed</td> <td>0</td> </tr> <tr> <td>dishrag</td> <td>1</td> </tr> <tr> <td>plate</td> <td>2</td> </tr> <tr> <td>running shoe</td> <td>3</td> </tr> <tr> <td>soap dispenser</td> <td>4</td> </tr> <tr> <td>street sign</td> <td>5</td> </tr> <tr> <td>table lamp</td> <td>6</td> </tr> <tr> <td>tile roof</td> <td>7</td> </tr> <tr> <td>toilet seat</td> <td>8</td> </tr> <tr> <td>washing machine</td> <td>9</td> </tr> </tbody> </table> <p>Checkout <a title="data preparation notebook" href="https://github.com/carpentries-lab/deep-learning-intro/blob/main/instructors/prepare-dollar-street-data.ipynb" target="_blank" rel="noopener">this notebook</a> to see how the subset was created.</p> <p>The original dataset was downloaded from https://www.kaggle.com/datasets/mlcommons/the-dollar-street-dataset. See https://mlcommons.org/datasets/dollar-street/ for more information.</p>
Analysis of a complex role of trees in street canyon using LES model (experiment: Terronska)
<h1>README</h1> <p>This is a companion dataset to the paper <em>Analysis of a complex role of trees in street canyon using LES</em> model by <em>Řezníček et al.</em>, to be submitted to <em><span>Quarterly</span> <span>Journal</span> of the Royal Meteorological Society</em>. All the supplementary data needed for the reproduction of the experiment described in the manuscript are provided on this ZENODO repository. The supplementary data includes the following:</p> <p>1. <em>01_palm_source_code.zip</em> contains the source code for the current version of the PALM model used for this experiment</p> <p>2. <em>02_inputs-configs.zip</em> which contains:</p> <ul> <li>static driver files (for cases 01 = full-trees, 02 = half-trees, 03 = no-strees)</li> <li>dynamic driver files (for different winds directions W = west, SW = southwest, S = south and stratifications C = convective, N = neutral + stable)</li> <li>configuration files for the first PALM run (p3d), and the configuration files for the restart runs (p3dr) for each of the performed simulations</li> <li>the files with N02 are apllied for child domain</li> </ul> <p>3. 03_maps-GIS contains maps in gis or png format with one hour averages outputs: </p> <ul> <li>the cases are terC/N_W/SW/S_01/02/03 for the stratifications, wind direcrions and trees-scenario (see the legend above)</li> <li>abs for absolute values, diff for differences from no-tree scenario, 01h = 1 hour average</li> <li>variables are bio_UTCI - universal thermal climate index [deg C], kc_PM10 = PM10 concentration in 2m or 10m height [<span>μ</span>/m^3], theta_2m = temperature in 2m [deg C], wspeed_10m = wind-speed in 10m, tsurf = surface temperature [deg C], rad_sw_in = incoming shortwave radiation flux [W/m^2] and rad_lw_out = outgoing longwave radiation flux [W/m^2]</li> </ul> <p>4. 04_cuts contains svg and png plots with vertical and horizontal (xy) cuts </p> <ul> <li>the cases are terC/N_W_01/02/03 for the stratifications and trees-scenario (see the legend above) and west winds</li> <li>jugp-ciirc = the vertical cut for (JugP) street (near the ciirc-CTU building), terr-street = the vertical cut for (Terr) street</li> </ul> <h1>PALM MODEL INSTALLATION AND USAGE GUIDE</h1> <h2>A. Installation</h2> <p>1. First, make sure to satisfy the Software Requirements. On Debian-based Linux Distributions, this can be achieved by the following command:</p> <p><code>sudo apt-get install gfortran g++ make cmake coreutils libopenmpi-dev openmpi-bin libnetcdff-dev netcdf-bin libfftw3-dev python3-pip python3-pyqt5 flex bison ncl-ncarg</code></p> <p>2. Also, some additional python dependencies are needed, which can be installed using pip. In case you want to use a virtual environment for these dependencies, please make sure to create one first. Afterwards, you can install the python dependencies by executing the following command:</p> <p><code>python3 -m pip install -r requirements.txt</code></p> <p>3. Now the PALM model system can be installed with the following commands (please replace with the desired installation directory):</p> <p><code>export install_prefix=""</code><br><code>bash install -p ${install_prefix}</code><br><code>export PATH=${install_prefix}/bin:${PATH}</code></p> <p>4. The following optional command permanently adds this installation to your bash environment:</p> <p><code>echo "export PATH=${install_prefix}/bin:\${PATH}" >> ~/.bashrc</code></p> <p>5. Type <code>bash install -h</code> to get all available options of the install script. During installation, the script calls the respective install script of all packages in this repository and installs them to the chosen directory. Therefore, it is not necessary to manually install any of the packages.</p> <p>You can test your installation with the following commands:</p> <p><code>palmtest --cases urban_environment_restart --cores 4</code></p> <h2>B. Usage</h2> <p>After a successful installation, the executables for all packages have been linked into the directory <code>/bin</code> and a default PALM configuration file can be found at <code>/.palm.config.default</code>. In case you have installed the python dependencies inside a virtual environment, that environment needs to be active whenever you wand to use PALM. For usage of each of the packages, please refer to their individual documentation. Next, you need to create your first PALM setup in order to start a simulation. To get a simple preconfigured setup and start your first PALM simulation, please execute the following sequence of commands:</p> <p><code>mkdir -p "${install_prefix}/JOBS/example_cbl/INPUT"</code><br><code>cp "packages/palm/model/tests/cases/example_cbl/INPUT/example_cbl_p3d" "${install_prefix}/JOBS/example_cbl/INPUT/"</code><br><code>cd ${install_prefix}</code><br><code>palmrun -r example_cbl -c default -a "d3#" -X 4 -v -z</code></p> <h1>ACKNOWLEDGEMENT</h1> <p>This research was supported by the Johannes Amos Comenius Programme (OP JAC), project No. CZ.02.01.01/00/22_008/0004605, Natural and anthropogenic<br>georisks.</p> <p>The dataset is published under the Creative Commons Attribution 4.0 International License (CC-BY-4.0). This license allows others to distribute, remix, adapt, and build upon the dataset for any purpose, even commercially, as long as they give appropriate credit to the original creator(s).</p>
First Street Foundation Property Level Flood Risk Statistics V1.3
<p>The property level flood risk statistics generated by the First Street Foundation Flood Model Version 1.3 come in CSV format. The data that is included in the CSV includes:</p> <ul> <li> <p>An FSID; a First Street ID (FSID) is a unique identifier assigned to each location.</p> </li> <li> <p>The latitude and longitude of a parcel as well as the zip code, census block group, census tract, county, congressional district, and state of a given parcel.</p> </li> <li> <p>The property’s Flood Factor as well as data on economic loss.</p> </li> <li> <p>The flood depth in centimeters at the low, medium, and high CMIP 4.5 climate scenarios for the 2, 5, 20, 100, and 500 year storms in 2021, 2036, and 2051.</p> </li> <li> <p>Data on the cumulative probability of a flood event exceeding the 0cm, 15cm, and 30cm threshold depth is provided at the low, medium, and high climate scenarios for years 2021, 2036, and 2051.</p> </li> <li> <p>Information on historical events and flood adaptation, such as ID and name.</p> </li> </ul> <p>You can download a sample of the property level flood risk statistics generated by First Street's Flood Model on this page. You can purchase the property level data for areas within the contiguous United States on the First Street website <a href="https://firststreet.org/data-access/paid-access/?utm_source=Property_Statistics&utm_medium=Purchase_Data&utm_campaign=Zenodo#pricing-component">here</a>. You can find the data dictionary which breaks down the data that is available with each property-level data purchase <a href="https://firststreet.org/data-access/getting-started-with-first-street-data/data-dictionary/?utm_source=Property_Statistics&utm_medium=Data_Dictionary&utm_campaign=Zenodo">here</a>. If you are also interested in the hazard layers, you can find more information <a href="https://firststreet.org/data-access/getting-started-with-first-street-data/documentation-hazard-dictionary/?utm_source=Property_Statistics&utm_medium=Hazard_Dictionary&utm_campaign=Zenodo">here</a>.</p>
Impact of Meteorological Factors on the Mesoscale Morphology of Cloud Streets during a Cold Air Outbreak over the western North Atlantic
<ul> <li>Supporting datasets for paper "Impact of Meteorological Factors on the Mesoscale Morphology of Cloud Streets during a Cold Air Outbreak over the western North Atlantic". </li> <li>Those are a subset of the (analyzed) datasets from WRF control simulation "ERA5" in netcdf format. See manuscript for more details. <ul> <li>cld_size.nc: cloud object size</li> <li>cld_ort_2020-03-01_15_00_00.nc: cloud object at 15:00 UTC</li> <li>hydro-02-2020-03-01_15/00/00.nc: water path sample data at 15:00 UTC</li> <li>wrfout_d02_2020-03-01_15/00/00: wrf output sample data at 15:00 UTC</li> </ul> </li> </ul>
First Street Foundation Property Level Flood Risk Statistics V2.0
<p>The property level flood risk statistics generated by the First Street Foundation Flood Model Version 2.0 come in CSV format. </p> <p>The data that is included in the CSV includes:</p> <ul> <li> <p>An FSID; a First Street ID (FSID) is a unique identifier assigned to each location.</p> </li> <li> <p>The latitude and longitude of a parcel as well as the zip code, census block group, census tract, county, congressional district, and state of a given parcel.</p> </li> <li> <p>The property’s Flood Factor as well as data on economic loss.</p> </li> <li> <p>The flood depth in centimeters at the low, medium, and high CMIP 4.5 climate scenarios for the 2, 5, 20, 100, and 500 year storms this year and in 30 years.</p> </li> <li> <p>Data on the cumulative probability of a flood event exceeding the 0cm, 15cm, and 30cm threshold depth is provided at the low, medium, and high climate scenarios for this year and in 30 years.</p> </li> <li> <p>Information on historical events and flood adaptation, such as ID and name.</p> </li> </ul> <p> </p> <p>This dataset includes <a href="https://firststreet.org/">First Street</a>'s aggregated flood risk summary statistics. The data is available in CSV format and is aggregated at the congressional district, county, and zip code level. The data allows you to compare FSF data with FEMA data. You can also view aggregated flood risk statistics for various modeled return periods (5-, 100-, and 500-year) and see how risk changes due to climate change (compare FSF 2020 and 2050 data). There are various <a href="https://floodfactor.com/">Flood Factor</a> risk score aggregations available including the average risk score for all properties (flood factor risk scores 1-10) and the average risk score for properties with risk (i.e. flood factor risk scores of 2 or greater). This is version 2.0 of the data and it covers the 50 United States and Puerto Rico. There will be updated versions to follow.</p> <p>If you are interested in acquiring First Street flood data, you can request to access the data <a href="https://firststreet.org/data-access/paid-access/?utm_source=Summary_Statistics_v1.3&utm_medium=Purchase_Data&utm_campaign=Zenodo#pricing-component">here</a>. More information on First Street's flood risk statistics can be found <a href="https://firststreet.org/data-access/getting-started-with-first-street-data/documentation-data-dictionaryv2/">here</a> and information on First Street's hazards can be found <a href="https://firststreet.org/data-access/getting-started-with-first-street-data/documentation-hazard-dictionary/?utm_source=Summary_Statistics_v1.3&utm_medium=Hazard_Dictionary&utm_campaign=Zenodo">here</a>.</p> <p>The data dictionary for the parcel-level data is below.</p> <table> <tbody> <tr> <td> <p><strong>Field Name</strong></p> </td> <td> <p><strong>Type</strong></p> </td> <td> <p><strong>Description</strong></p> </td> </tr> <tr> <td> <p>fsid</p> </td> <td> <p>int</p> </td> <td> <p>First Street ID (FSID) is a unique identifier assigned to each location</p> </td> </tr> <tr> <td> <p>long</p> </td> <td> <p>float</p> </td> <td> <p>Longitude</p> </td> </tr> <tr> <td> <p>lat</p> </td> <td> <p>float</p> </td> <td> <p>Latitude</p> </td> </tr> <tr> <td> <p>zcta</p> </td> <td> <p>int</p> </td> <td> <p>ZIP code tabulation area as provided by the US Census Bureau</p> </td> </tr> <tr> <td> <p>blkgrp_fips</p> </td> <td> <p>int</p> </td> <td> <p>US Census Block Group FIPS Code</p> </td> </tr> <tr> <td> <p>tract_fips</p> </td> <td> <p>int</p> </td> <td> <p>US Census Tract FIPS Code</p> </td> </tr> <tr> <td> <p>county_fips</p> </td> <td> <p>int</p> </td> <td> <p>County FIPS Code</p> </td> </tr> <tr> <td> <p>cd_fips</p> </td> <td> <p>int</p> </td> <td> <p>Congressional District FIPS Code for the 116th Congress</p> </td> </tr> <tr> <td> <p>state_fips</p> </td> <td> <p>int</p> </td> <td> <p>State FIPS Code</p> </td> </tr> <tr> <td> <p>floodfactor</p> </td> <td> <p>int</p> </td> <td> <p>The property's Flood Factor, a numeric integer from 1-10 (where 1 = minimal and 10 = extreme) based on flooding risk to the building footprint. Flood risk is defined as a combination of cumulative risk over 30 years and flood depth. Flood depth is calculated at the lowest elevation of the building footprint (largest if more than 1 exists, or property centroid where footprint does not exist)</p> </td> </tr> <tr> <td> <p>CS_depth_RP_YY</p> </td> <td> <p>int</p> </td> <td> <p>Climate Scenario (low, medium or high) by Flood depth (in cm) for the Return Period (2, 5, 20, 100 or 500) and Year (today or 30 years in the future). Today as year00 and 30 years as year30. ex: low_depth_002_year00</p> </td> </tr> <tr> <td> <p>CS_chance_flood_YY</p> </td> <td> <p>float</p> </td> <td> <p>Climate Scenario (low, medium or high) by Cumulative probability (percent) of at least one flooding event that exceeds the threshold at a threshold flooding depth in cm (0, 15, 30) for the year (today or 30 years in the future). Today as year00 and 30 years as year30. ex: low_chance_00_year00</p> </td> </tr> <tr> <td> <p>aal_YY_CS</p> </td> <td> <p>int</p> </td> <td> <p>The annualized economic damage estimate to the building structure from flooding by Year (today or 30 years in the future) by Climate Scenario (low, medium, high). Today as year00 and 30 years as year30. ex: aal_year00_low</p> </td> </tr> <tr> <td> <p>hist1_id</p> </td> <td> <p>int</p> </td> <td> <p>A unique First Street identifier assigned to a historic storm event modeled by First Street</p> </td> </tr> <tr> <td> <p>hist1_event</p> </td> <td> <p>string</p> </td> <td> <p>Short name of the modeled historic event</p> </td> </tr> <tr> <td> <p>hist1_year</p> </td> <td> <p>int</p> </td> <td> <p>Year the modeled historic event occurred</p> </td> </tr> <tr> <td> <p>hist1_depth</p> </td> <td> <p>int</p> </td> <td> <p>Depth (in cm) of flooding to the building from this historic event</p> </td> </tr> <tr> <td> <p>hist2_id</p> </td> <td> <p>int</p> </td> <td> <p>A unique First Street identifier assigned to a historic storm event modeled by First Street</p> </td> </tr> <tr> <td> <p>hist2_event</p> </td> <td> <p>string</p> </td> <td> <p>Short name of the modeled historic event</p> </td> </tr> <tr> <td> <p>hist2_year</p> </td> <td> <p>int</p> </td> <td> <p>Year the modeled historic event occurred</p> </td> </tr> <tr> <td> <p>hist2_depth</p> </td> <td> <p>int</p> </td> <td> <p>Depth (in cm) of flooding to the building from this historic event</p> </td> </tr> <tr> <td> <p>adapt_id</p> </td> <td> <p>int</p> </td> <td> <p>A unique First Street identifier assigned to each adaptation project</p> </td> </tr> <tr> <td> <p>adapt_name</p> </td> <td> <p>string</p> </td> <td> <p>Name of adaptation project</p> </td> </tr> <tr> <td> <p>adapt_rp</p> </td> <td> <p>int</p> </td> <td> <p>Return period of flood event structure provides protection for when applicable</p> </td> </tr> <tr> <td> <p>adapt_type</p> </td> <td> <p>string</p> </td> <td> <p>Specific flood adaptation structure type (can be one of many structures associated with a project)</p> </td> </tr> <tr> <td> <p>fema_zone</p> </td> <td> <p>string</p> </td> <td> <p>Specific FEMA zone categorization of the property ex: A, AE, V. Zones beginning with "A" or "V" are inside the Special Flood Hazard Area which indicates high risk and flood insurance is required for structures with mortgages from federally regulated or insured lenders</p> </td> </tr> <tr> <td> <p>footprint_flag</p> </td> <td> <p>int</p> </td> <td> <p>Statistics for the property are calculated at the centroid of the building footprint (1) or at the centroid of the parcel (0)</p> </td> </tr> </tbody> </table> <p> </p>
FloodSense street sign mounted flood depth sensor
<p><strong>Flood Depth Data (FDD)</strong> collected by a fleet of sensors deployed across 5 boroughs of New York City with a resolution of half an inch or less. The metadata for the sensors is included in the metadata.csv to identify the deployment coordinates of sensors, each with a unique <strong><em>deployment_id</em></strong>. </p> <p>The depth data is collected at least every five minutes and every minute in some locations depending on the ability to harvest solar energy at that deployment location. </p> <p>The final depth data field is <strong><em>depth_proc_mm</em></strong>, and the raw data is <strong><em>dist_mm</em></strong>. </p> <p>The raw measurement values received from the sensor are distance measurements (dist_mm), which are simply distance measurements collected from a ranging ultrasonic-based sensor. These distance measurements are converted to depths using <strong><em>night_median_dist_mm</em></strong> which is a daily calculated median of nighttime sensor readings. Direct sunlight affects ranging measurements due to high variance in the air column between the sensor and the concrete surface that it is mounted over. Additionally, the housing internally heats up when under direct sunlight, which affects the sensor readings and appears as if the surface dips with the daily increase and decrease in temperature during the daytime.</p> <p>After converting to raw depth values, a simple range filter is applied to the data removing any anomalies that lie below 10 millimeters and above unrealistic depth values (for example a person - between 5ft to 6ft), which is named <strong><em>depth_filt_mm</em></strong>.</p> <p>Further, this filtered depth value is processed through data filters eliminating blips, any pulse chains, or a flat line due to garbage or a car parked underneath the sensor. The output of these filters is labeled <strong><em>depth_proc_mm</em></strong>. </p> <p>This data is intended for use by communities, researchers, and New York City government agencies to better understand the frequency, severity, and impacts of flooding in New York City. </p> <p>Here is the live dashboard for these sensors deployed: <a href="https://dataviz.floodnet.nyc/">FloodNet Data Dashboard</a></p> <p>More about this project at <a href="https://www.floodnet.nyc/">FloodNet.NYC</a></p> <p>This is an open-source project and for more information on the sensors and build manuals see the <a href="https://github.com/floodnet-nyc/flood-sensor">FloodNet FloodSensor GitHub page</a></p>
RAKSILA 3D. Laser scanning survey of the street fronts and green areas in Raksila, Oulu (FINLAND)
<p>The video shows the preliminary results of the laser scanner survey of Raksila district in Oulu, Finland. Raksila is an important historical trace in the development of the urban planning of the city of Oulu. The district of Raksila is mainly a well-preserved residential Neighborhood characterized by a strong typicality.The general plan consists of a regular structure and a system of street fronts on the road are ordered and in an homogeneous profile. Despite this, Raksila still has no detailed and updated guidelines capable of managing all different types of interventions allowed (renovation, restoration, repair actions, possible modifications). For this reason, a laser scanner survey and detailed documentation have been created, through which all the elements and characteristics of the place have been defined and collected in sort of atlas and inventory reports. This new documentation is going to constitute the base for the definition of new guidelines, a practical support and analysis for future interventions that can be carried out in total respect of this heritage. This topic is inserted as case study for developing the Research Project n. 746215 entitled "Preserving Wooden Heritage". The project is financed by the European Commission with an Individual Marie S. Curie Fellowship assigned to PostDoctoral Researcher Sara Porzilli, who is working at the University of Oulu - Finland.</p>
Ouagadougou land use map at street block level
<p>This datatset contains a land use classification of Ouagadougou (Burkina Faso) at the street block level. It was created following the methodology presented in [1].</p> <p>Description of the files:</p> <ul> <li>"Ouagadougou_landuse.gpkg" : GeoPackage with two layers: (1) layer of the street blocks extracted from OpenStreetMap using [2] with classification results in the attribute table. (2) layer with manual correction made by GEORGANOS Stefanos (sgeorganos@ulb.ac.be).</li> <li>"Ouagadougou_landuse_style_QGIS.zip" : Files for style for rendering in QGIS.</li> </ul> <p>Attribute table content:</p> <ul> <li>"CAT", "GID" : ID of the street block</li> <li>"PROB_ACS" : Probability to belong to class ACS</li> <li>"PROB_BARE" : Probability to belong to class BARE</li> <li>"PROB_PLAN" : Probability to belong to class PLAN</li> <li>"PROB_UNPLA" : Probability to belong to class UNPLAN</li> <li>"PROB_VEG" : Probability to belong to class VEG</li> <li>"FIRST_LABE" : Class with the highest classification probability</li> <li>"SEC_LABEL" : Class with the second highest classification probability</li> <li>"FIRST_PROB" : Value of the highest classification probability</li> <li>"SEC_PROB" : Value of the second highest classification probability</li> <li>"UNCERTAIN" : Difference between "FIRST_PROB" and "SEC_PROB"</li> <li>"BUILT_PERC" : Percentage of the street blocks covered by built-up (from land cover map)</li> <li>"MAP_LABEL" : Final classification label with uncertainty and different density classes. Depending on the layer, the label is with or without manual corrections</li> </ul> <p>Legend classes label:</p> <ul> <li>"VEG" : Vegetation</li> <li>"BARE" : Bare soils</li> <li>"ACS" : Non-residential built-up (administrative, commercial, services, etc.)</li> <li>"PLAN" : Planned residential built-up</li> <li>"PLAN_LD" : Planned residential low density built-up</li> <li>"UNPLAN" : Unplanned residential built-up</li> <li>"UNPLAN_LD" : Unplanned residential low density built-up</li> <li>"UNCERT" : Uncertain classification</li> <li>"WET" : Wetlands</li> <li>"AGRI" : Agricultural land</li> </ul> <p>References:</p> <p>[1] Grippa, Tais, 2018, "Mapping urban land use at street block level using OpenStreetMap, remote sensing data and spatial metrics", <em>ISPRS Int. J. Geo-Inf.</em> <strong>2018</strong>, <em>7</em>(7), 246. <a href="https://doi.org/10.3390/ijgi7070246">https://doi.org/10.3390/ijgi7070246</a> </p> <p>[2] Grippa, Tais. 2018. “Osm Street Blocks Extraction.” Zenodo. <a href="https://doi.org/10.5281/zenodo.1290637">https://doi.org/10.5281/zenodo.1290637</a>.</p> <p>Funding: </p> <p>This dataset was produced in the frame of two research project : MAUPP (<a href="http://maupp.ulb.ac.be">http://maupp.ulb.ac.be</a>) and REACT (<a href="http://react.ulb.be">http://react.ulb.be</a>), funded by the Belgian Federal Science Policy Office (<a href="http://eo.belspo.be/About/Stereo3.aspx">BELSPO</a>).</p>
Nairobi_Street_Trees_Distribution_Diversity
<p>Input data and code to accompany the paper:</p> <p>Alice Gerow, Vivian Kathambi, Dexter Locke, Mark Ashton, Craig Brodersen. Street tree communities reflect socioeconomic inequalities and legacy effects of colonial planning in Nairobi, Kenya. Urban Forestry & Urban Greening. <a href="https://doi.org/10.1016/j.ufug.2024.128530">https://doi.org/10.1016/j.ufug.2024.128530</a></p> <p>The input data consists in street tree observations collected during a field survey conducted between June and August 2023 in Nairobi, Kenya. The code includes descriptive tables and plots, statistical tests, and alpha and beta diversity metrics and visualizations used to compare ecological communities across social groups.</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.