Initial Sample of Emotional Bodily Expressions for the NAO Robot

Open data API in a single place

Provided by Universitätsbibliothek Würzburg

Get early access to Initial Sample of Emotional Bodily Expressions for the NAO Robot API!

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

Dataset information

Catalog

Universitätsbibliothek Würzburg catalog

Country of origin

Germany

Updated

2025.11.20 00:00

Created

2024.01.01

Available languages

English

Keywords

social-robots, body-language, emotions

Datasource

Official portal for European data link

Quality scoring

Dataset description

Abstract: To investigate human-robot interaction with the NAO robot using emotional body language, we used this sample of photographed expressions to validate bodily expressions reflecting the 24 subemotions from Plutchik’s wheel of emotions. For each of the subemotions, we created two to three different expressions based on related works using Choregraphe version 2.8.10. Each expression was photographed twice: with neutral (white) eye LEDs and with colored eye LEDs matching the colors in the Wheel of emotions. In total, 112 pictures were shot using constant lighting, angle, and background. Participants assigned emotion labels to the freeze frames of the social robot NAO V6 included in this repository. For further information please refer to our works referenced in the metadata.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

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.

api.store Built by Apitalks

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

About api.storePrivacy Terms of Service