Deepomatic Platform
  • Overview
  • Release notes
    • January 2025
    • November 21, 2024
    • October 17, 2024
    • September 19, 2024
    • July 18, 2024
    • June 27, 2024
    • May 23, 2024
    • April 18, 2024
    • March 21, 2024
    • February 22, 2024
    • January 18, 2024
    • December 13, 2023
    • October 26, 2023
    • July 20, 2023
    • June 29, 2023
    • May 29, 2023
    • April 27, 2023
    • March 30, 2023
    • February 17, 2023
    • January 19, 2023
    • December 22, 2022
    • November 18, 2022
    • October 19, 2022
    • September 19, 2022
    • July 27, 2022
    • June 26, 2022
    • May 17, 2022
    • April 13, 2022
    • March 17, 2022
    • February 10, 2022
    • December 21, 2021
    • October 26, 2021
  • Getting started
  • ADMIN & USER MANAGEMENT
    • Invite and manage users
      • Invite group of users at once
      • SSO
        • Azure Active Directory
  • Deepomatic Engage
    • Integrate applications
      • Deepomatic vocabulary
      • Deepomatic connectors
        • Set-up
        • Camera Connector
        • Work Order Connector
      • API integration
        • Authentication
        • Errors
        • API reference
          • Work order management
          • Analysis
            • Guide field workers
            • Perform an analysis
            • Correct an analysis
          • Data retrieval
          • Endpoints' list
      • Batch processing
        • Format
        • Naming conventions
        • Processing
        • Batch status & errors
      • Data export
    • Use the mobile application
      • Configure a mobile application
      • Create & visualize work orders
      • Complete work orders
      • Offline experience
    • Manage your business operations with customisable solutions
      • Roles
      • Alerting
      • Field services
        • Reviewing work orders
        • Exploring work orders
        • Grouping work orders
        • Monitoring assets performance
      • Insights
  • Security
    • Security
    • Data Protection
Powered by GitBook
On this page
  • Create a new View
  • View Homepage

Was this helpful?

  1. Deepomatic Drive
  2. Adding and managing data
  3. Managing projects & views

Creating & organising views

KEY TERMS

Concepts are the way to decompose and describe your visual universe. The term is actually a shortcut, as you should think more about visual concepts, i.e. concepts that have a visual unity of their own.

A View is a subset of a project. It is defined by logical conditions on inherited concepts and in turn defines its own set of concepts, thus giving rise to a hierarchical visual ontology.

A Root View corresponds to the first level of the hierarchy without any condition. A Root View then applies to all images of a project.

Parent and Child Views are linked together, the Child View being defined from conditions on the concepts of the Parent view. A Child View thus applies to a subset of the images of the Parent View.

Create a new View

Root View

To create a root view, you need to click on Add a root view if it's your first root view, or on Create a root view if you have already created one. You then need to choose a name for it.

A root view concerns all the images that have been added to the project.

Child View

To create a child view, there are two possibilities:

  • you can click on Create a view at the bottom of a column, this will create a new child view with the same parent view as the other views of the column.

  • you can click directly on the + button of a given view. This given view will automatically be the parent view of the view you create.

View Sources

When you create a child view, you must specify conditions based on the concepts of the parent view to select the images that will be added to the view you are creating.

  • when the parent view is a detection or tagging view, then you can use AND or OR conditions, and choose the concepts on which you want to filter.

View Type

You then need to select the type of view you want to create:

  • Classification: each image is labelled with exactly one concept and all concepts are then exclusive.

  • Tagging: each image is labelled positively or negatively for all concepts. A single image can then validate several concepts (or none).

  • Detection: concepts are localised in the image with bounding boxes. The information is then much richer as you can get several instances of a same concept in the image.

Concepts

You need to specify the concepts that you want to recognize. You can do so by clicking on New concept and by giving a name to your new concept. Don't worry, you can add more concepts and/or edit them after you have ended the project creation process.

View Homepage

When entering a view, you access a screen where you can navigate through your Views and understand the hierarchy between all the Views.

Was this helpful?

For more information on the different kinds of views, see our or .

You can also use existing concepts by importing a JSON file in which the concepts and images are defined. To do so, you must precise the field "tags" in the JSON. Check the to know more about the JSON format accepted.

Guidebook on how to build your custom AI
our blog post series "AI for Dummies"
The child view applies to images that have been annotated in the parent detection view with both snowboard and traffic light concepts..
JSON Upload page