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.
13
datasets available to search
ShareScore release 0.9.0
Dataset results
13 results for “traffic simulation”
The data that support the findings of a review paper "From urban data to city-scale models: A review of traffic simulation case studies"
<p>This dataset contains the data that were used in a review paper "From urban data to city-scale models: A review of traffic simulation case studies". It contains the following files:</p> <ul> <li>keywords with counts.txt - list of keywords and their counts in the considered corpus of traffic simulation case studies. The data were used to produce Figure 2 and Figure 3 in the paper.</li> <li>Papers analysis.xlsx - Excel file containing the data on the reviewed studies. The document has the following sheets: <ul> <li> Appendix A - contains a table short reference, location, simulation period, spatial scale, simulated units and marked categories for a paper;</li> <li>Geography - contains data on geographical distribution of simulated areas between world regions and countries, these data were used to produce Figure 4 in the paper;</li> <li>Software tools - contains data on simulation tools used in the studies. </li> <li>Journals and conferences - contains data on where the reviewed papers were published.</li> </ul> </li> </ul>
Benchmark for deterministic traffic simulator - parameter space exploration (Prague, Jun 6 2021)
<p>The benchmark is meant for deterministic traffic simulator for optimising traffic flow within a city. The simulator is one part of a traffic modeling framework for intelligent transportation in smart cities. In contrast to standard navigation systems where the navigation is optimised for drivers, we aim to optimise a distribution of the global traffic flow. We utilise HPC resources for the simulator’s parameters exploration for which EVEREST SDK is used.</p> <p>The traffic simulator is available at: <a href="https://github.com/It4innovations/ruth">github.com/It4innovations/ruth</a><strong>.</strong></p> <p><br> The benchmark contains input data, routing map, and skript to run it with HyperQueue. Simulator v1.0 was used.</p>
Simulated application load on a Kubernetes system based on Human traffic pattern
<p>Contained here is the dataset generated using the tool based on the report 'A Dynamic Kubernetes Load Generation Solution Mimicking Human Traffic Pattern'. The tool was created to fill in the gap of having to generate artificial load within Kubernetes infrastructure. This tool could then be used as a stable testing framework to determine whether the Autoscaling solutions in place can handle the expected load pattern or not. It can also be used as a standard benchmarking tool to test various algorithms that aim to improve the already existing autoscaling solutions. The tool is primarily for IaaS (Infrastructure As A Service) providers, who have to deal with applications as a black box and are unaware of the scaling needs of the application. Some of the data generated in this dataset were made in reference to existing datasets obtained from Google Dataset of different containers. The reference dataset will also be uploaded in the near future. </p> <p>The dataset contains CSV files, which have the name of the pod, average CPU usage, average memory usage, and the timestamp of when the data was collected. These measurements were taken directly from the Prometheus service which uses using Kubernetes metrics server to scrape the data from the pods. <br>The `avg_cpu_usage` is the average CPU percent of the total CPU available the application utilized over a 1-minute interval window. While the `avg_memory_usage` is the average memory utilized in bytes over 1 1-minute interval window. The CSV file names also mention the period of time from when the measurements were taken. Any date and time within the dataset are in the CEST timezone. All of the CSV files in the dataset have the same layout. </p> <p>The datasets were collected from a Kubernetes node in a VM, with the following specifications,<br>- Intel core (Broadwell, no TSX, IBRS), 2 cores @ 2.594 GHzkb<br>- 4GiB of memory<br>- Ubuntu 22.04.4 LTS x86_64<br>- Kernel: 5.15.0-105-generic</p> <p>The names of the file itself specify the type of application load generated. The file names can be divided into segments separated by `__`. The last two segments signify the start time of the measurement data, and the end time of the measurement data respectively. The optional segment before the mentioned two segments signifies the container from the original input dataset that was used as a reference to produce the given data.</p> <p>Similarly, there is an optional tag of `CPU`, `mem`, or `test` at the beginning of the file name. This signifies the type of application load that was used to generate the data. `CPU` would mean the application was created by using options on the tool that used CPU stressing algorithms from `ng-stress`. This was used to better mimic a CPU-intensive application. Similarly, `mem` primarily makes use of a test algorithm that stresses memory. `test` is a special option making use of a combination of tests to have a balanced outcome. </p> <p>In the real world, the applications are never static, and between each run, with the same parameters, the application will always show some variations. To account for these variations, we added some inherent randomness in the number of concurrent connections and the amount of time a virtual user waits to make a request. There are some measurements where these measurements were frozen, which makes the class,<br>- fixed-load_fixed-sleep <br>- random-load_fixed-sleep<br>- fixed-load_random-sleep</p> <p>measurements.<br>The default class of (random-load_random-sleep) is every other measurement not marked by these tags in their name.</p> <p>The dataset itself was collected over a period of 3 days, from 25-03-2024 to 28-03-2024. Each dataset generally contains 34 min of simulation data, with the first and last 2 minutes without any traffic being directed to stabilize the system. The actual 30 min of data corresponds to the daily behavioral pattern as shown in a 30-day period.</p>
Urban Traffic Simulation Data from Real Fusion Estimates
<p>The datasets contain vehicle data from the simulation of the city center of Guimarães. The simulation was created using data collected from real sensor data, thus, providing an accurate view of the traffic flows. The data contains route information, fuel consumption, emissions, driving distance, and the amount of time each vehicle is stopped.</p>
An urban traffic dataset composed of visible images and their semantic segmentation generated by the CARLA simulator
<p><strong>If you use this dataset please cite this paper: Rosende, S.B.; Gavilán, D.S.J.; Fernández-Andrés, J.; Sánchez-Soriano, J. An Urban Traffic Dataset Composed of Visible Images and Their Semantic Segmentation Generated by the CARLA Simulator. <em>Data</em> 2024, <em>9</em>, 4. <a href="https://doi.org/10.3390/data9010004">https://doi.org/10.3390/data9010004</a></strong></p> <p>A dataset of aerial urban traffic images and their semantic segmentation is presented to be used to train computer vision algorithms, among which those based on convolutional neural networks stand out. The images have been generated using the CARLA simulator (but would be like those that could be obtained with fixed aerial cameras or by using AUVs) in the field of intelligent transportation management. The presented dataset is available and accessible to improve the performance of vision and road traffic management systems, especially for the detection of incorrect or dangerous maneuvers.</p>
Traffic forecasting with Virtual Induction Loops - SUMO simulation dataset
<p>This repository is associated with my doctoral dissertation titled, "<strong>Smartphone based applications for Road Traffic Telematics</strong>". In particular this repository serves as the basis of Chapter 7 titled, "<strong>Traffic forecasting with Virtual Induction Loops (VIL)</strong>". The basic idea is to validate a traffic forecasting system which uses machine learning techniques on the simulation of real traffic flows on a real intersection in the City of Turin. This dataset contains simulation output from SUMO software for 56 real days between the months of October-2017 to April-2018. Details about these days are available in my thesis. For each day, 3 output files are available. Here is the description and naming convention:</p> <ol> <li>M1_100seed_100pr_dump.csv (This is the data dump file from SUMO. It contains flows of every single vehicle that was simulated. Naming convention is day_seed_vilPenetrationRate_dump.csv)</li> <li>M1_100seed_ilNorth_100pr.xml (This is the output from a simulated induction loop for Northbound traffic. Naming convention is day_seed_ilNorth_vilPenetrationRate.xml)</li> <li>M1_100seed_ilSouth_100pr.xml (This is the output from a simulated induction loop for Southbound traffic. Naming convention is day_seed_ilSouth_vilPenetrationRate.xml)</li> </ol> <p>For further details, please refer to my thesis.</p>
Swiss Dwellings: A large dataset of apartment models including aggregated geolocation-based simulation results covering viewshed, natural light, traffic noise, centrality and geometric analysis
<p><strong>Introduction</strong></p> <p>This dataset contains detailed data on over 45,000 apartments (370,000 rooms) in ~3,100 buildings including their geometries, room typology as well as their visual, acoustical, topological, and daylight characteristics. Additionally, we have included location-specific characteristics for the buildings, including climatic data and points of interest within walking distance.</p> <p><strong>Changelog</strong></p> <ul> <li><strong>v3.0.0 (2023-03-31):</strong> <ul> <li>Updated the dataset increasing the total number of apartments to 45176 and incorporating fixes to some of the sites. The update includes re-digitized apartments and thus alters some ID values.</li> </ul> </li> <li><strong>v2.2.1 (2023-03-10):</strong> <ul> <li>A file, <code>location_ratings.csv</code>, has been included to provide ratings of the locations in which the buildings are situated. The ratings, provided by <a href="https://en.fpre.ch/">Fahrländer Partner AG</a>, give insights into the living situation at the buildings' addresses. Details for the different dimensions are provided below.</li> <li>The file <code>location.csv</code> has been updated to include the minimum and maximum temperatures for the locations in which the buildings are situated.</li> </ul> </li> <li><strong>v2.1.0 (2022-12-23)</strong>: <ul> <li>A file, <code>locations.csv</code>, has been included to provide information on the climatic and infrastructural characteristics of the locations in which each building is situated</li> </ul> </li> <li><strong>v2.0.0 (2022-10-17):</strong> <ul> <li>Additional to the residential units, we also include the commercial and public parts (such as staircases) of the models. The field <code>unit_usage</code> describes whether an area belongs to a commercial, residential, janitor or public part of the building</li> <li>Added the fields <code>elevation</code> and <code>height</code> to <em>geometries.csv</em> to describe the elevation above the terrain surface and the height of objects.</li> <li>Added the field <code>plan_id</code> which allows identifying which floors are based on the same floor plan (in some cases multiple floors of a building share the same floor plan</li> <li>Improved the ordering of fields in the CSV files (instead of alphabetic order)</li> <li>Minor changes to individual sites</li> </ul> </li> </ul> <p><strong>Procurement</strong></p> <p>The data is sourced from commercial clients of <a href="https://www.archilyse.com/">Archilyse AG</a> specializing on the digitization and analysis of buildings. The existing building plans of clients are converted into a geo-referenced, semantically annotated representation and undergo a manual Q/A process to ensure the accuracy of the data and to ensure a maximum 5%-deviation in the apartments' areas (validated with a median deviation of 1.2%).</p> <p><strong>Geometries</strong></p> <p>The dataset contains a file <code>geometries.csv</code> which contains the geometries of all areas, walls, railings, columns, windows, doors and features (sinks, bathtubs, etc.) of an apartment.</p> <p>In total, the datasets contain the 2D geometry of ~1.7 million separators (walls, railings), ~715,000 openings (windows, doors), ca. 520,000 areas (rooms, bathrooms, kitchens, etc.), and ~315,000 features (sinks, toilets, bathtubs, etc.).</p> <p>Each row contains:</p> <ul> <li><code>apartment_id</code>: The ID of the apartment (for features, areas), <em>note</em>: an apartment id is only unique per site</li> <li><code>site_id</code>: The ID of the site</li> <li><code>building_id</code>: The ID of the building</li> <li><code>floor_id</code>: The ID of the floor</li> <li><code>plan_id</code>: The ID of the plan on which the floor is based, multiple floors of a building might be based on the same plan</li> <li><code>unit_id</code>: The ID of the unit in which the element is spatially contained (for features, areas)</li> <li><code>area_id</code>: The ID of the area in which the element is spatially contained (for features)</li> <li><code>unit_usage</code>: The usage of the unit, possible values are: RESIDENTIAL, COMMERCIAL, PUBLIC, JANITOR</li> <li><code>entity_type</code>: The entity type (<em>area, separator, opening, feature</em>)</li> <li><code>entity_subtype</code>: The entity’s sub-type (e.g. <em>WALL</em>)</li> <li><code>geometry</code>: The element’s geometry as a <a href="https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry">WKT</a> geometry in meters. The geometry is given in the site’s local coordinate system. I.e. the position between elements of the same site are correct in respect to each other. The +y direction points northwards, the +x direction points eastwards.</li> <li><code>elevation</code>: The object's elevation above the terrain surface in meters. We assume one terrain baseline per building, thus all walls in a given floor share the same elevation value. However, windows in particular might start at different elevations and have differing heights.</li> <li><code>height</code>: The height of the entity in meters, <em>note</em>: In many cases, a default height is assumed</li> </ul> <p>An example:</p> <table> <thead> <tr> <th scope="col">column</th> <th scope="col"> </th> </tr> </thead> <tbody> <tr> <td>apartment_id</td> <td> <p>d4438f2129b30290845ce7eef98a5ba7</p> </td> </tr> <tr> <td>site_id</td> <td>127</td> </tr> <tr> <td>building_id</td> <td>164</td> </tr> <tr> <td>plan_id</td> <td>492</td> </tr> <tr> <td>floor_id</td> <td>861</td> </tr> <tr> <td>unit_id</td> <td>63777</td> </tr> <tr> <td>area_id</td> <td>767676</td> </tr> <tr> <td>unit_usage</td> <td>RESIDENTIAL</td> </tr> <tr> <td>entity_type</td> <td>area</td> </tr> <tr> <td>entity_subtype</td> <td>LIVING_ROOM</td> </tr> <tr> <td>geometry</td> <td> <p>POLYGON ((-6.1501158933490139 -4.8490786654693...</p> </td> </tr> <tr> <td>elevation</td> <td>0</td> </tr> <tr> <td>height</td> <td>2.6</td> </tr> </tbody> </table> <p><strong>Simulations</strong></p> <p>Besides the geometrical model, we also provide simulation data on the visual, acoustic, solar, layout, and connectivity-related characteristics of the apartments. The file <code>simulations.csv</code> contains the simulation data aggregated on a per-area basis. Each row contains the identifier columns <code>area_id</code>, <code>unit_id</code>, <code>apartment_id</code>, <code>floor_id</code>, <code>building_id</code>, <code>site_id</code> as defined above as well as 367 simulation columns. Each simulation column is formatted as:</p> <pre><code><simulation_category>_<simulation_dimensions>_<aggregation_function></code></pre> <p>For instance. the column <code>view_buildings_median</code> describes the amount of building surface that can be seen from any point in a given room. The aggregation methods vary per simulation category and are described in detail below.</p> <p><strong>Layout</strong></p> <p>The <em>layout</em> features represent simple features based on the geometry and composition of a room, the dataset provides the following information in an unaggregated form.</p> <p>Area Basics / Geometry</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>layout_area_type</td> <td>The area’s area type</td> </tr> <tr> <td>layout_net_area</td> <td>The area’s share of the apartment’s net area (e.g. 0 for a balcony)</td> </tr> <tr> <td>layout_area</td> <td>The area’s actual area</td> </tr> <tr> <td>layout_perimeter</td> <td>The area’s perimeter</td> </tr> <tr> <td>layout_compactness</td> <td>The area’s compactness (the Polsby–Popper score)</td> </tr> <tr> <td>layout_room_count</td> <td>The area’s share to the apartment’s room count</td> </tr> <tr> <td>layout_is_navigable</td> <td>True if the area is navigable by a wheelchair</td> </tr> </tbody> </table> <p>Area Features</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>layout_has_sink</td> <td>True if the area has a sink</td> </tr> <tr> <td>layout_has_shower</td> <td>True if the area has a shower</td> </tr> <tr> <td>layout_has_bathtub</td> <td>True if the area has a bathtub</td> </tr> <tr> <td>layout_has_toilet</td> <td>True if the area has a toilet</td> </tr> <tr> <td>layout_has_stairs</td> <td>True if the area has stairs</td> </tr> <tr> <td>layout_has_entrance_door</td> <td>True if the area is directly leading to an exit of the apartment</td> </tr> </tbody> </table> <p>Area Windows / Doors</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>layout_number_of_doors</td> <td>The number of doors directly leading to the area</td> </tr> <tr> <td>layout_number_of_windows</td> <td>The number of windows of the area</td> </tr> <tr> <td>layout_door_perimeter</td> <td>The sum of all door lengths directly leading to the area</td> </tr> <tr> <td>layout_window_perimeter</td> <td>The sum of all window lengths of the area</td> </tr> </tbody> </table> <p>Area Walls / Railings</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>layout_open_perimeter</td> <td>The sum of all of the boundaries of the area that are neither walls nor railings</td> </tr> <tr> <td>layout_railing_perimeter</td> <td>The sum of all of the boundaries of the area that are railings</td> </tr> <tr> <td>layout_mean_walllengths</td> <td>The mean length of the area’s sides</td> </tr> <tr> <td>layout_std_walllengths</td> <td>The standard deviation of the lengths of the area’s sides</td> </tr> </tbody> </table> <p>Area Adjacency</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>layout_connects_to_bathroom</td> <td>True if the area connects to a bathroom</td> </tr> <tr> <td>layout_connects_to_private_outdoor</td> <td>True if the area connects to an outside area that is private to the apartment</td> </tr> </tbody> </table> <p><strong>View</strong></p> <p>The views from an object help to understand the impact of the surroundings on the object. The view simulation calculates the visible amount of buildings, greenery, water, etc. on each individual hexagon from the analyzed object. The values are expressed in steradians (sr) and represent the amount a particular object category occupies in the spherical field of view.</p> <p>Each of the following dimensions is provided using the room-wise aggregations' <em>min</em>, <em>max</em>, <em>mean</em>, <em>std</em>, <em>median</em>, <em>p20,</em> and <em>p80</em>. For instance, the column <code>view_greenery_p20</code> describes the amount of greenery that can be seen from at least 20% of the positions in the area.</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>view_buildings</td> <td>The amount of visible buildings</td> </tr> <tr> <td>view_greenery</td> <td>The amount of visible greenery</td> </tr> <tr> <td>view_ground</td> <td>The amount of visible ground</td> </tr> <tr> <td>view_isovist</td> <td>The amount of visible isovist</td> </tr> <tr> <td>view_mountains_class_2</td> <td>The amount of visible mountains of UN mountain class 2</td> </tr> <tr> <td>view_mountains_class_3</td> <td>The amount of visible mountains of UN mountain class 3</td> </tr> <tr> <td>view_mountains_class_4</td> <td>The amount of visible mountains of UN mountain class 4</td> </tr> <tr> <td>view_mountains_class_5</td> <td>The amount of visible mountains of UN mountain class 5</td> </tr> <tr> <td>view_mountains_class_6</td> <td>The amount of visible mountains of UN mountain class 6</td> </tr> <tr> <td>view_railway_tracks</td> <td>The amount of visible railway_tracks</td> </tr> <tr> <td>view_site</td> <td>The amount of visible site</td> </tr> <tr> <td>view_sky</td> <td>The amount of visible sky</td> </tr> <tr> <td>view_tertiary_streets</td> <td>The amount of visible tertiary_streets</td> </tr> <tr> <td>view_secondary_streets</td> <td>The amount of visible secondary_streets</td> </tr> <tr> <td>view_primary_streets</td> <td>The amount of visible primary_streets</td> </tr> <tr> <td>view_pedestrians</td> <td>The amount of visible pedestrians</td> </tr> <tr> <td>view_highways</td> <td>The amount of visible highways</td> </tr> <tr> <td>view_water</td> <td>The amount of visible water</td> </tr> </tbody> </table> <p><strong>Sun</strong></p> <p>Sun simulations help to understand the impact of solar radiation on the object. The outcome of the sun simulations helps to identify surfaces that have great solar potential. Sun simulations are defined by the amount of solar radiation on each individual hexagon from the analyzed object. The sun simulation not only includes direct sun but also considers scattered light. The sun simulation values are given in Kilolux (klx). Simulations are performed for the days of the summer solstice, winter solstice, and the vernal equinox.</p> <p>Each of the following dimensions is provided using the room-wise aggregations' <em>min</em>, <em>max</em>, <em>mean</em>, <em>std</em>, <em>median</em>, <em>p20,</em> and <em>p80</em>. For instance, column <code>sun_201806211200_median</code> describes the median amount of direct daylight received on the positions in the area.</p> <p>Vernal Equinox</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>sun_201803210800</td> <td>Daylight at 08:00 on 21st of March</td> </tr> <tr> <td>sun_201803211000</td> <td>Daylight at 10:00 on 21st of March</td> </tr> <tr> <td>sun_201803211200</td> <td>Daylight at 12:00 on 21st of March</td> </tr> <tr> <td>sun_201803211400</td> <td>Daylight at 14:00 on 21st of March</td> </tr> <tr> <td>sun_201803211600</td> <td>Daylight at 16:00 on 21st of March</td> </tr> <tr> <td>sun_201803211800</td> <td>Daylight at 18:00 on 21st of March</td> </tr> </tbody> </table> <p>Summer Solstice</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>sun_201806210600</td> <td>Daylight at 06:00 on 21st of June</td> </tr> <tr> <td>sun_201806210800</td> <td>Daylight at 08:00 on 21st of June</td> </tr> <tr> <td>sun_201806211000</td> <td>Daylight at 10:00 on 21st of June</td> </tr> <tr> <td>sun_201806211200</td> <td>Daylight at 12:00 on 21st of June</td> </tr> <tr> <td>sun_201806211400</td> <td>Daylight at 14:00 on 21st of June</td> </tr> <tr> <td>sun_201806211600</td> <td>Daylight at 16:00 on 21st of June</td> </tr> <tr> <td>sun_201806211800</td> <td>Daylight at 18:00 on 21st of June</td> </tr> <tr> <td>sun_201806212000</td> <td>Daylight at 20:00 on 21st of June</td> </tr> </tbody> </table> <p>Winter Solstice</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>sun_201812211000</td> <td>Daylight at 10:00 on 21st of December</td> </tr> <tr> <td>sun_201812211200</td> <td>Daylight at 12:00 on 21st of December</td> </tr> <tr> <td>sun_201812211400</td> <td>Daylight at 14:00 on 21st of December</td> </tr> <tr> <td>sun_201812211600</td> <td>Daylight at 16:00 on 21st of December</td> </tr> </tbody> </table> <p><strong>Noise / Window Noise</strong></p> <p>Noise level and the distribution of elements from an area help to understand how an object is exposed to the acoustics of this area. The acoustic simulation calculates the noise intensity on each individual hexagon from the analyzed object considering traffic and train noise datasets. Adjacent buildings are considered noise-blocking elements. The values are expressed in dBA (decibels).</p> <p>Window Noise</p> <p>The noise per window of a given area is aggregated via <code>min</code> and <code>max</code>. For instance, <code>window_noise_train_day_max</code> represents the maximum amount of noise received on any window of the area.</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>window_noise_traffic_day</td> <td>The amount of noise received on the area’s windows from daytime car traffic</td> </tr> <tr> <td>window_noise_traffic_night</td> <td>The amount of noise received on the area’s windows from night-time car traffic</td> </tr> <tr> <td>window_noise_train_day</td> <td>The amount of noise received on the area’s windows from daytime train traffic</td> </tr> <tr> <td>window_noise_train_night</td> <td>The amount of noise received on the area’s windows from night-time train traffic</td> </tr> </tbody> </table> <p>Area-Wise Noise</p> <p>The area-wise noise describes the amount of noise received from a noise source aggregated over the whole area in an unaggregated form. For instance, <code>noise_traffic_night</code> describes the dBA of noise received in the area from car traffic at night when propagating noise from all windows.</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>noise_traffic_day</td> <td>The amount of noise received in the area from daytime car traffic</td> </tr> <tr> <td>noise_traffic_night</td> <td>The amount of noise received in the area from night-time car traffic</td> </tr> <tr> <td>noise_train_day</td> <td>The amount of noise received in the area from daytime train traffic</td> </tr> <tr> <td>noise_train_night</td> <td>The amount of noise received in the area from night-time train traffic</td> </tr> </tbody> </table> <p><br> <strong>Connectivity</strong></p> <p>Centrality simulations help to analyze a floor plan, whether it’s a shopping mall and you want to identify prominent areas in order to select the most prominent spot or it’s an interior design circulation path and you want to determine open floor plan areas. Centrality simulations are done using topological measures that score grid cells by their importance as a part of a grid cell network.</p> <p>The distances and centralities are aggregated via <em>min</em>, <em>max</em>, <em>mean</em>, <em>std</em>, <em>median</em>, <em>p20,</em> and <em>p80</em>. For instance, <code>connectivity_balcony_distance_min</code> describes the shortest distance to the next balcony from the point closest to the balcony in the area.</p> <p>Distances</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>connectivity_room_distance</td> <td>Distance to the next area of type ROOM</td> </tr> <tr> <td>connectivity_living_dining_distance</td> <td>Distance to the next area of type LIVING_DINING</td> </tr> <tr> <td>connectivity_bathroom_distance</td> <td>Distance to the next area of type BATHROOM</td> </tr> <tr> <td>connectivity_kitchen_distance</td> <td>Distance to the next area of type KITCHEN</td> </tr> <tr> <td>connectivity_balcony_distance</td> <td>Distance to the next area of type BALCONY</td> </tr> <tr> <td>connectivity_loggia_distance</td> <td>Distance to the next area of type LOGGIA</td> </tr> <tr> <td>connectivity_entrance_door_distance</td> <td>Distance to the next apartment exit</td> </tr> </tbody> </table> <p>Centralities</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>connectivity_eigen_centrality</td> <td>The Eigen-Centrality value</td> </tr> <tr> <td>connectivity_betweenness_centrality</td> <td>The Betweenness-Centrality value</td> </tr> <tr> <td>connectivity_closeness_centrality</td> <td>The Closeness-Centrality value</td> </tr> </tbody> </table> <p><strong>Location Properties</strong></p> <p>In addition to the apartment-related data, we also provide simulation data on the climatic, and infrastructural characteristics of the locations. The file <code>locations.csv</code> contains the simulation data aggregated on a per-building basis. Each row contains the identifier <code>building_id</code> corresponding to the building ids referenced in <code>geometries.csv</code> and <code>simulations.csv</code>.</p> <p><strong>Climate</strong></p> <p>The climate features represent 39 simple features based on the spatial climate analysis of Meteo Swiss as derived from <a href="https://www.meteoswiss.admin.ch/climate/the-climate-of-switzerland/spatial-climate-analyses.html.">MeteoSwiss</a>. Each column is formatted as <code>climate_<category>_<period>. </code>For instance, the column <code>climate_tnorm_january</code> describes the monthly mean temperature in degrees Celsius (from the norm period of 1991-2020) at the location of the building. The aggregation methods vary per simulation category and are described in detail below.</p> <p>Temperature Normals</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>climate_tnorm_year</td> <td>The yearly mean temperature in degrees Celsius of the current norm period from 1991 to 2020 (TnormY9120)</td> </tr> <tr> <td>climate_tnorm_january</td> <td>The monthly mean temperature in January in degrees Celsius of the current norm period from 1991 to 2020 (TnormM9120)</td> </tr> <tr> <td>climate_tnorm_februry</td> <td>The monthly mean temperature in February in degrees Celsius of the current norm period from 1991 to 2020 (TnormM9120)</td> </tr> <tr> <td>...</td> <td>...</td> </tr> <tr> <td>climate_tnorm_december</td> <td>The monthly mean temperature in December in degrees Celsius of the current norm period from 1991 to 2020 (TnormM9120)</td> </tr> <tr> <td>climate_tminnorm_january</td> <td>The monthly minimum temperature in January in degrees Celsius of the current norm period from 1991 to 2020 (TminnormM9120)</td> </tr> <tr> <td>...</td> <td> </td> </tr> <tr> <td>climate_tminnorm_december</td> <td>The monthly minimum temperature in December in degrees Celsius of the current norm period from 1991 to 2020 (TnormM9120)</td> </tr> <tr> <td>climate_tmaxnorm_january</td> <td>The monthly maximum temperature in January in degrees Celcius of the current norm period from 1991 to 2020 (TnormM9120)</td> </tr> <tr> <td>...</td> <td> </td> </tr> <tr> <td>climate_tmaxnorm_december</td> <td>The monthly maximum temperature in December in degrees Celcius of the current norm period from 1991 to 2020 (TnormM9120)</td> </tr> </tbody> </table> <p>Sunshine Duration Normals</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>climate_snorm_year</td> <td>The yearly mean relative sunshine duration in percent of the current norm period from 1991 to 2020 (SnormY9120). Relative sunshine duration (RSD) is the ratio between the effective sunshine duration and the duration maximally possible if no clouds were covering the sun. A period with sunshine is defined as a period when the direct solar irradiance exceeds 200 W/m²</td> </tr> <tr> <td>climate_snorm_january</td> <td>The monthly mean relative sunshine duration for January in percent of the current norm period</td> </tr> <tr> <td>climate_snorm_februry</td> <td>The monthly mean relative sunshine duration for February in percent of the current norm period</td> </tr> <tr> <td>...</td> <td>...</td> </tr> <tr> <td>climate_snorm_december</td> <td>The monthly mean relative sunshine duration for December in percent of the current norm period</td> </tr> </tbody> </table> <p>Precipitation Normals</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>climate_rnorm_year</td> <td>The yearly mean precipitation in mm of the current norm period (RnormY9120)</td> </tr> <tr> <td>climate_rnorm_january</td> <td>The monthly mean precipitation for January in mm of the current norm period (RnormM9120)</td> </tr> <tr> <td>climate_rnorm_februry</td> <td>The monthly mean precipitation for February in mm of the current norm period (RnormM9120)</td> </tr> <tr> <td>...</td> <td>...</td> </tr> <tr> <td>climate_rnorm_december</td> <td>The monthly mean precipitation for December mm of the current norm period (RnormM9120)</td> </tr> </tbody> </table> <p><strong>10-Minute Walkshed Infrastructure</strong></p> <p>Based on OpenStreetMap data and its tagging system we counted all 465 tags (key and value tuples as listed here: https://wiki.openstreetmap.org/wiki/Map_features) which can be reached within a 10-minute walk from the location of the building. Each column is formatted as <code>walkshed_<poi_category>_<poi_type>. </code>For instance, the column <code>walkshed_shop_coffee</code> describes the number of coffee shops located within 10 minutes of walking from the building.</p> <p>The following is an excerpt of support categories and their corresponding types.</p> <ul> <li><code>shop: antique, art, ...</code></li> <li><code>amenity: art, atm, ...</code></li> <li><code>tourism: alpine, attraction, ...</code></li> <li><code>leisure: amusement, beach, ...</code></li> <li><code>healthcare: clinic, dentist, ...</code></li> <li><code>historic: archaeological, battlefield, ...</code></li> <li><code>ariaelway: station</code></li> </ul> <p><strong>Location Ratings</strong></p> <p>The location ratings, provided by <a href="https://en.fpre.ch/">Fahrländer Partner AG</a>, give insights into the living situation at locations in which the buildings are situated. The file location_ratings.csv provides the following information:</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>location_rating_MIKRAT_W</td> <td>Living situation - Overall (1.0=worst, 5.0=best)</td> </tr> <tr> <td>location_rating_IMAGE_W</td> <td>Living situation - Image (1.0=worst, 5.0=best)</td> </tr> <tr> <td>location_rating_DL_W</td> <td>Living situation - Service Quality (1.0=worst, 5.0=best)</td> </tr> <tr> <td>location_rating_FZ_W</td> <td> <p>Living situation - Leisure Quality (1.0=worst, 5.0=best)</p> </td> </tr> <tr> <td>location_rating_NASE_W_DOM</td> <td>The most dominant segment of demand:<br> <br> 1 Rural-traditional<br> 2 Modern worker<br> 3 Transitional-alternative<br> 4 Traditional middle class<br> 5 Liberal middle class<br> 6 Established alternative<br> 7 Upper middle class<br> 8 Professional elite<br> 9 Urban elite<br> 10 Unknown<br> <br> <a href="https://en.fpre.ch/marktdaten/nachfragersegmente/nachfragersegmente-im-wohnungsmarkt/">More Information</a></td> </tr> <tr> <td>location_rating_FGFRQZ</td> <td> <p>The mean number of pedestrians per hour throughout a day between 7 am and 8 pm of an average working day.<br> <br> 1 <50<br> 2 50-100<br> 3 100-200<br> 4 200-500<br> 5 >500</p> </td> </tr> </tbody> </table>
Required data for simulating a typical large-scale urban traffic network
Open the record for dataset details and reuse information.
Ruth Traffic Simulator - Input for Prague, Boston
<p>Input data for simulations of 10 000 and 60 000 vehicles in Prague and 300 000 vehicles in Boston.<br>The map file should be included in "./data" folder, in working directory.</p> <p>Prague:<br>vehicles - prague-10K.parquet or prague-60K.parquet<br>map - 50_200432299999996-14_1755692-49_9151047-14_7526108_2024-02-13T00-00-00.graphml</p> <p>Boston:<br>vehicles - boston-300K.parquet<br>map - 42_47641909231966--71_27465474058792-42_14946390799415--70_90361558027409_2024-02-13T00-00-00.graphml</p> <p> </p>
Leveraging IoT Data Stream for Near-Real-Time Calibration of City-Scale Microscopic Traffic Simulation
<p>This repository includes input and output data of the methodology presented in the <a href="https://arxiv.org/abs/2210.17315">paper</a> for generating a calibrated dynamic microscopic traffic simulation.</p> <ul> <li>The input data includes the network, initial normalized origin-destination matrix, and hourly traffic counts from stationary city sensors.</li> <li>The output is a 24-hour calibrated microscopic traffic simulation for the city of Tartu, Estonia.</li> </ul> <p>All source codes are available at <a href="https://github.com/Khoshkhah/NRTCalib">https://github.com/Khoshkhah/NRTCalib</a>.<br> </p>
Simulated performance data: MILC, LAMMPS, and uniform random traffic patterns on 72-ndoe dragonfly network
<p>Data generated from an old, private fork of the CODES simulation toolkit: https://github.com/codes-org/codes</p> <p>Data dictionary: https://github.com/kevinabrown/codes/wiki/Dragonfly-Dally-DEBUG-Metrics</p>
Road traffic simulator using the Intelligent Driver Model
<p>Road traffic simulator using the Intelligent Driver Model</p>
Collection, treatment and analysis of air traffic data within Brazil boundaries focused on simulation scenarios.
Open the record for dataset details and reuse information.
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.