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.
17
datasets available to search
ShareScore release 0.9.0
Dataset results
17 results for “street level”
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>
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>
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>
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>
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>
Outsourcing asylum reception Street-level organizations and the privatization of state action in Switzerland
<p>By approaching outsourcing through an ethnographic lens,we focus on the policies that enable public authorities to deal with the many uncertainties of refugee reception. We investigate how cantonal (subnational) governments in Switzerland remodel these uncertainties by implementing the policy of reception through private intermediaries, namely actors, instruments, and rationalities from the private sphere.</p> <p>Codebook along DDI standard in pdf and xml formats.</p>
Mapillary Annotated Street Level Images
<p>This dataset contains street-level images from the Mapillary platform, for the year of 2017, in the <a href="https://zenodo.org/api/files/e945988e-2c3d-4cc6-9cd2-ee7761a2f15a/mapillary.zip?versionId=86c5f856-324c-45a6-aa9d-03a0f661a0b2">mapillary.zip</a> file. These images have been matched with crop type labels from the freely available Land Parcel Identification System (LPIS) of the Netherlands. The name of each .jpf file corresponds to a unique identifier.</p> <p>Supported by the CALLISTO (No. v) project, which has been funded by EU Horizon 2020 programs.</p>
Dakar land use map at street block level
<p>This datatset contains a land use classification of Dakar (Senegal) at the street block level. It was created following the methodology presented in [1].</p> <p>Description of the files:</p> <ul> <li>"Dakar_landuse_shapefile.zip" : Shapefile of the street blocks extracted from OpenStreetMap using [2] with classification results in the attribute table.</li> <li>"Dakar_landuse_style.zip" : Files for style of the shapefile.</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_AGRI" : Probability to belong to class AGRI</li> <li>"PROB_BARE" : Probability to belong to class BARE</li> <li>"PROB_DEPR" : Probability to belong to class DEPR</li> <li>"PROB_PLAN" : Probability to belong to class PLAN</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</li> </ul> <p>Legend classes label:</p> <ul> <li>"AGRI" : Agricultural vegetation</li> <li>"VEG" : Natural 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>"DEPR" : Deprived residential built-up</li> <li>"UNCERT" : Uncertain classification</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>
Mapillary POI-Neighborhood Street-Level Images (MPOINSLI)
<p><em><strong>Dataset Name:</strong></em> MPOINSLI Mapillary POI-Neighborhood Street-Level Images </p> <blockquote> <p>This is a repository of Mapillary street-view images of New York City that include any portion of POIs in their field of view. The repository is the outcome of a paper, the abstract of which is provided below. Please use the below citatin for using this dataset:</p> <p> </p> </blockquote> <p><strong>Citation: </strong></p> <p>N. Zarbakhsh and G. McArdle, "Points-of-Interest from Mapillary Street-level Imagery: A Dataset For Neighborhood Analytics," 2023 IEEE 39th International Conference on Data Engineering Workshops (ICDEW), Anaheim, CA, USA, 2023, pp. 154-161, doi: 10.1109/ICDEW58674.2023.00030.</p> <p><strong>Abstract: </strong></p> <p>The Sustainable Development Goals of the United Nations promote sustainable urban development to make cities more economically and socially liveable. Points of Interest (POIs) such as commercial properties and healthcare facilities are significant markers for these goals. Street-view images are becoming increasingly important for capturing cities' streetscapes. Existing studies provide city-level images, while there are few studies that provide images in the vicinity of certain POIs. Therefore, this paper develops a framework for filtering images so that a portion of a given POI is visible in their field of view (FOV). We contribute with Mapillary POI-Neighborhood Street-Level Images (MPOINSLI) dataset, a large street-view image of POIs and their neighborhood in New York City. First, all the images within a 35-meter radius of certain POIs are filtered. Then, the intersection technique is utilized to determine if the cameras' FOV triangular polygons intersect the POIs' polygons. Using 11,126 POIs from SafeGraph's Geometry and Place datasets in conjunction with 875,592 Mapillary images, we demonstrate the effectiveness of our approach. MPOINSLI contains 167,743 Mapillary street-view images of 6,732 unique POIs, defined by the standard identifiers (Placekeys) which are further classified into 23 general functionalities categories (top-categories) and 67 more specific categories (sub-categories) of the POIs. MPOINSLI provides an open-source repository that contains metadata such as raw and post-processed camera-related parameters, the Harvesian distance between the camera and the POI's coordinates, and the intersection area. MPOINSLI could provide promising future applications for both smart cities and computer vision, including scene recognition across POI neighborhoods and fine-grained land-use classification.</p>
pLitterStreet - Street Level Plastic Litter Detection Dataset
<p><strong>pLitterStreet</strong> dataset comprises of more than <em>13,000 images</em>. These images were captured using <em>vehicle-mounted cameras</em> that were strategically positioned to focus on the sides of streets. The primary objective of this dataset is to facilitate research related to street litter and its impact on the environment.</p> <p>Annotations for the images are provided in the widely-used Microsoft COCO JSON format. Image in the dataset is fully annotated, enabling the identification and categorization of various types of litter found along urban and rural streets. These annotations include precise labeling of litter items, making the dataset an invaluable resource for developing and evaluating object detection and image recognition models.</p>
Private vehicles greenhouse gas emissions at street level for Berlin based on open data
<p>We estimated the annual average daily GHG emissions from individual motor traffic for the OSM road network in Berlin by combining the estimated Annual Average Daily Traffic Volume (AADTV) with respective emission factors. The AADTV was calculated by simulating car trips with the open routing engine Openrouteservice, weighted by activity functions based on statistics of the German Mobility Panel.</p>
StreetScouting dataset: A Street-Level Image dataset for finetuning and applying custom object detectors for urban feature selection
<p>The dataset consists of two .zip files.</p> <p>The first .zip file named "annotated dataset" contains a folder named “annotated dataset" with annotated street images. It consists of the folder “images” that has 763 image files. The image format is PNG. 432 images have dimensions of 1080 x 2160 and 331 have dimensions of 866 x 2400. The filenames are random uuids. The “annotated dataset” folder also contains the annotations in the file “coco_annotations.json”. Annotations are provided in COCO format. Table 1 shows the total number of annotated objects per class.</p> <table align="center" summary="Total number of annotated objects per class"> <caption><em>Table 1. Total number of annotated objects per class</em></caption> <thead> <tr> <th scope="col"><strong><em>Class</em></strong></th> <th scope="col"><strong><em>Annotated Objects</em></strong></th> </tr> </thead> <tbody> <tr> <td><em>Tree</em></td> <td>1922</td> </tr> <tr> <td><em>Waste Bin</em></td> <td><em>223</em></td> </tr> <tr> <td><em>Recycling Bin</em></td> <td>181</td> </tr> <tr> <td><em>Lighting Pole</em></td> <td><em>716</em></td> </tr> <tr> <td><em>Shop Storefront</em></td> <td><em>628</em></td> </tr> </tbody> </table> <p>The second .zip file is named "routes" and contains a folder named “routes” with consecutive frames of four different driving routes in the city of Thessaloniki and their corresponding GPS signal. So the folder “routes” contains 4 folders in the following format “VID_<YYYYMMDD>_<HHmmSS>” where Y denotes digits for year, M denotes digits for month, D denotes digits for day, H denotes digits for hour, m denotes digits for minutes and S denotes digits for seconds. Not the filename represents the start of the collection sequence. All street data was collected in 2022. Each route folder has the “images” folder which contains the consecutive street image data. Image data in this folder is in JPEG format. Each filename in ‘images’ has the frame_<id>.jpg format where id denotes the order of the frame. Table 2 shows more details regarding the number of frames and frame dimension of the driving routes.</p> <table align="center" summary="Total number of annotated objects per class"> <caption><em>Table 2. Total number frames and frame dimensions for each of the routes</em></caption> <thead> <tr> <th scope="col"><strong><em>Route Name</em></strong></th> <th scope="col"><strong><em>Frames Number</em></strong></th> <th scope="col"><strong><em>Frame Dimension</em></strong></th> <th scope="col"><strong><em>Route duration</em></strong></th> </tr> </thead> <tbody> <tr> <td><em>VID_20220617_111456</em></td> <td><em>41,650</em></td> <td><em>1080 x 2160</em></td> <td>1h, 9m, 26s</td> </tr> <tr> <td><em>VID_20220210_112926</em></td> <td><em>23.035</em></td> <td><em>866 x 2400</em></td> <td>38m, 26s</td> </tr> <tr> <td><em>VID_20220209_114831</em></td> <td><em>18.000</em></td> <td><em>1080 x 2160</em></td> <td>30m, 3s</td> </tr> <tr> <td><em>VID_20220209_123323</em></td> <td><em>18.273</em></td> <td><em>1080 x 2160</em></td> <td>30m, 30s</td> </tr> </tbody> </table> <p>Each route folder contains a “gps.json” file which contains latitude and longitude information for each frame. This file is essentially a JSON list of objects that each object contains the “frame_name” attribute and the corresponding “coordinates” object which contains the “latitude” and "longitude" attributes.</p>
Input data for article "Large eddy simulation of the optimal street-tree layout for pedestrian-level aerosol particle concentrations"
<p>Input dataset used when performing LES simulations for journal article "Large eddy simulation of the optimal street-tree layout for pedestrian-level aerosol particle concentrations" (Karttunen et al., in preparation). The dataset was used with the PALM model system revision 3698 and most likely it won't work on older or newer versions.</p> <p>Instructions for use:<br> A precursor run must be run first. Output data (BINOUT) of it should be linked into a BININ directory of the actual scenario runs. You'll most likely have to tweak the CPU grid settings in ENVPAR and PARIN files in order to fit them to your computational resources. For more information on usage please refer to the PALM model documentation available online in <a href="https://palm.muk.uni-hannover.de/trac/wiki/doc">https://palm.muk.uni-hannover.de/trac/wiki/doc</a>.</p>
Leonardo Da Vinci Fraud Exposed - Worlds First Street Level Maps are from Armenian Kingdom of Cilicia in ancient Anatolia
<p>Leonardo Da Vinci Fraud Exposed - Worlds First Street Level Maps are from Armenian Kingdom of Cilicia in ancient Anatolia.</p> <p>There are few maps in possession of The Royal Collection Trust in England, which are attributed to Leonardo Da Vinci ( These maps have made up city names for the past 500 years, written on the original scripted words ), which are in fact maps of ancient Anatolia showing Burdur, Antalya, Isparta and Mersin provinces from 800 + years ago. For the last 500 years these have been classified as showing Tuscany valley in Italy, but after careful diligent research I have come to clear conclusion that these maps show provinces in Turkey and were a labor of multiple years to produce these maps, within Armenian Kingdom of Cilicia</p> <p>There are 2 main maps.</p> <ol> <li>“World of Castles”</li> <li>“Map of a Valley and a Lake”</li> </ol> <p>“<strong>World of Castles map</strong>” - Redefines history, Is of Armenian Kingdom of Cilicia in Anatolia. Present day Turkey. A map 250 years before Leonardo Da Vinci, Wrongly credited to him. This particular map (“World of Castles map”) took 3 + years to make, and is a work of team of around 3 map makers who travelled the vast Cilician empire in 12<sup>th</sup> Century AD, Mersin Province, Anatolia, present day Turkey. The Rubenids (Armenian: Ռուբինեաններ) were an Armenian dynasty who dominated parts of Cilicia, and who established the Armenian Kingdom of Cilicia.</p> <ul> <li>Maps were created before 1199 - 12<sup>th</sup> century AD as some castles after 1200 AD don’t show up in the maps. Queen Isabella, Queen of Armenia ruled till 1252 - 1219–1252, maps were still in Anatolian Cilicia, Armenian Kingdom of Cilicia. The Hethumids, ruled till 1373 AD, the maps were still in Anatolian Cilicia, Armenian Kingdom of Cilicia. War between the Ottoman sultan Bayezid I and Kadi Burhan al-Din, ruler of northeastern Anatolia occurred sometime in late 14<sup>th</sup> century, around that period these valuables from Rubenids Empire made its way to Cyprus, which was under Venetian rule. Greek merchants carried these maps for the next 75 + years.</li> <li>Leonardo was born in 1452, 250 Years had passed between his birth and the birth of these maps. All these valuable scientific material Codex’s, Maps originated at some point of time in ancient Anatolia and ended up in front of Leonardo Da Vinci, who never published these as he had no clue about the Armenian merchant script, nor does many researchers till this date. That’s the main reason why just guess work ended up wrongly crediting these maps for the last 500 plus years. </li> <li>The map shows Castles, Streets, Rivers, Swamps, wherever necessary for the map makers. Whatever the map makers saw in front of them was noted down in individual place maps, drawn and location/direction marked. These individual maps, about 100 of them, considering the vast regions and in depth travels were then combined to make the main map. The map of ‘World of Castles” roughly covers 4200 Sq. Km and is a street level map, showing trails in the area The team had to roam around all that area in order to note down the Castles, prior to 1199 AD. The language is Armenian Merchant Script. These maps were likely ordered by the rulers and facilitated Collection of taxes from merchants crisscrossing the lands.</li> <li>“<strong>Map of a Valley and a Lake</strong>” -The map shows village boundaries, Streets, Tree lines wherever necessary for the map makers. Castles are shown, rivers, mountains, lakes and trails. Whatever the map makers saw in front of them was noted down, drawn and location/direction marked. These individual maps, about 500 of them, considering the vast regions and in depth travels were then combined to make the main map. The map covers almost approximately 14500 Sq. miles / 37500 Sq. km. The language is Armenian Merchant Script. These maps were likely ordered by the rulers and facilitated Collection of taxes from merchants crisscrossing the lands. It would take almost 9 + years to just get the data including Individual places and about 6 months to just combine the individual places into one map.</li> <li>How this map ended up with Leonardo Da Vinci – Generations of Armenian merchants and Greek traders in Kingdom of Cilicia crisscrossed the land for trade and moved to Cyprus during forced migrations, running away from invaders, from there many generations sold and bought valuables including Oil Paintings, precious books, ornaments and special food products unique to their area. Many of these Greek merchants travelled to Italy to sell their products and thus the huge repository of Codex’s in Armenian merchant script along with the maps ended up in Italy. Wealthy people like Leonardo Da Vinci just obtained them even though not understanding the script or maps. </li> <li>The maps show Limnombria/Polydorion Lost city which became Burdur City later on.</li> <li>It shows city of Bucak, How it was 800 + years ago.</li> </ul> <p>Thank You</p> <p>Sukhwant Singh</p> <p>USA - Copyrighted</p>
Augmented Street-Level Imagery with Points of Interest (Data and Resources Track)
<p>Augmented Street-Level Imagery with Points of Interest (Data and Resources Track)</p>
COPD at a Street Level
ClinicalTrials.gov study NCT05660460. IPD Sharing: NO. Countries: 1. Publications: 0.
Determining the Effect of Street Play Intervention on Children's Play Tendencies and Social Problem Solving Levels
ClinicalTrials.gov study NCT05724017. IPD Sharing: YES. Countries: 1. Publications: 0.
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.