RIS Based Hand Gesture Recognition Dataset

Open data API in a single place

Provided by Zenodo

Get early access to RIS Based Hand Gesture Recognition Dataset API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2024.09.12 00:00
Created
2024.01.01
Available languages
English
Keywords
Quality scoring

Dataset description

RIS Based Hand Gesture Recognition Dataset Overview This dataset contains images for gesture recognition, divided into two main sets: dataset0608 and data_synthetic_variab. The data was collected using a wooden hand.      dataset0608 This dataset consists of two modes: ris_random and ris_optimized. The main difference between the two subfolders is the configuration of the RIS (random or optimized).   This dataset consists of four subfolders: ris_random, ris_random2, ris_optimized, and ris_optimized2. The main difference between the subfolders is the format of the data: - ris_random and ris_optimized: Data is stored in individual files for each frame, named as 'frame_{i}{posture}{n_med}'  - ris_random2 and ris_optimized2: Data has already been processed and combined into single files for all frames using the compact_files_frames.txt function, named as 'all_frames_{posture}_{n_med}'    For each gestures = {close, two, open}, we have n_med values from 0 to 114 and 10 frames. Therefore, the ris_random and ris_optimized folders contain 10 frames × 115 measurements × 3 gestures = 3450 files, while the ris_random2 and ris_optimized2 folders contain 1 × 115 measurements × 3 gestures = 345 files.   data_synthetic_variab This dataset consists of two modes: ris_random and ris_optimized. The main difference between the two subfolders is the configuration of the RIS (random or optimized).    This dataset consists of four subfolders: ris_random, ris_random2, ris_optimized, and ris_optimized2. The main difference between the subfolders is the format of the data: - ris_random and ris_optimized: Data is stored in individual files for each frame, named as 'frame_{i}{posture}{n_med}'  - ris_random2 and ris_optimized2: Data has already been processed and combined into single files for all frames using the compact_files_frames.txt function, named as 'all_frames_{posture}_{n_med}'    For each gestures = {close, two, open},  we have n_med values from 0 to 8 and 10 frames. This dataset provides additional synthetic data with variations in hand position to increase the dataset's diversity. Each gesture is represented by 8 different ways, where the hand position was slightly modified between each sample. These real data were used as a basis for generating synthetic data. By using the functions in the files "multiply_files.txt" and "add_gaussian_noise.txt," the dataset was expanded and made more realistic by adding Gaussian noise to the images.   Therefore, the ris_random and ris_optimized folders contain 10 frames × 8 measurements × 3 gestures = 240 files, while the ris_random2 and ris_optimized2 folders contain 1 × 8 measurements × 3 gestures = 24 files.   Functions * **add_gaussian_noise.txt:** This script adds Gaussian noise to the images to simulate real-world conditions and improve the robustness of the model. * **compact_files_frames.txt:** This script combines multiple frames into a single image, which can be useful for certain types of analysis.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks