Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Triply Use Case 9: Interaction affordances for 3D data #591

Open
wouterbeek opened this issue Nov 5, 2024 · 0 comments
Open

Triply Use Case 9: Interaction affordances for 3D data #591

wouterbeek opened this issue Nov 5, 2024 · 0 comments

Comments

@wouterbeek
Copy link

Triply Use Case 9: Interaction affordances for 3D data

Description

When I have a 3D object in GeoSPARQL, I want to be able to interact with parts of the object. For example:

  • For asset management purposes, I want to be able to see the maintenance status of individual pillars underneath a bridge. This allows me to perform a virtual inspection of the bridge.
  • For training purposes, I want to be able to interact with individual pipes and switches in the model of a 3D factory. Each pipe and switch has its own metadata.
  • For performing a building inspection, I want to be able to 'open' a 3D building and look at the different floors. Within each floor, I want to be able to look at the different rooms.

The GeoSPARQL standard provides properties that act as affordances for navigating and interacting with 3D data. (This is similar to how SKOS contains affordances for setting human-readable labels, and to how SHACL contains affordances for ordering fields in forms.)

Actor

  • An asset manager, who performs some inspections of bridges in a virtual environment.
  • A trainee, who learns how a factory works.
  • A building inspector.

Preconditions

  • I have a 3D object that consists of multiple components.
  • I have information that applies to specific components.

Postconditions

  • I have integrated the information with each corresponding 3D component.

Steps

  1. I have loaded 3D objects from a couple of IFC files.
  2. These 3D objects have components with their own identifiers.
  3. I have a linked dataset with metadata and information, which is aligned with specific identifiers.
  4. Based on the common identifiers, I was able to relate metadata and information to 3D components. The GeoSPARQL standard gave me affordances that I could use to this effect.
  5. When I navigate the 3D data, I can meaningfully interact with 3D components and I can meaningfully 'open' components to reveal their containing components.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant