Spector Vision
  • Home
  • Getting started
    • Install
    • Device pairing
  • Features
    • 🔬NDT
      • Measurement mesh
      • Measurement display
    • 🗜️Laminate repair tool
    • 📐Space aware positioning
      • Origin manipulation
    • 📹Video capture
    • 🪄Detection
      • Streaming
    • Advanced use
      • Changing API Environment in Spector
  • UI elements
    • 🎛️Defect panel
    • 📍Origin handler
  • API
    • Overview
    • Startup [Admin API]
    • Device [Content API]
      • Main
      • Marker manipulations
    • Documents [Content API]
      • View documents
    • LRT [Detection API]
    • Defect dimensions [Detection API]
    • Space settings
      • Endpoints
  • Releases
    • 1.2
    • 1.1
    • 1.0
    • Pilot 1.8
      • 🥽Fixes
      • 🥽Alignment marker along z-axis
      • 🥽Nodes rotation
    • Pilot 1.7
      • 🥽Status bar and header
      • 🥽Defect description
      • 🥽Defect codes relations
      • 🥽Disposition: select number of plies
      • 🥽Disposition: all plies table
      • 📡Disposition API: get all plies
      • 📡Disposition API: get selected plies
      • 🥽Disposition: selected plies table
      • 🥽Disposition: display layup image
      • 📡Disposition API: Get image layup
      • 📡Disposition API: Update LRT data
      • 🥽Handler (Scene Origin) Rotation
      • 🖥️Portal laminate repair tool
      • 📡Detection API: Defect dimensions
    • Pilot 1.6
    • Pilot 1.5
    • Pilot 1.4
    • Pilot 1.3
    • Pilot 1.1-2
    • 🔵Pilot 1.0
    • Pilot 0.3
    • Pilot 0.2
    • Pilot 0.1
    • 🟢Demo 1.0
    • Demo 0.3
    • Demo 0.2
    • Demo 0.1
  • Identity
    • Spector logo
Powered by GitBook
On this page

Was this helpful?

  1. Releases
  2. Pilot 1.7

Disposition: all plies table

Last updated 1 year ago

Was this helpful?

  1. Feature Overview:

    • The Disposition feature allows users to obtain details about specific areas within a 3D space related to defects. This is done by making an API call that retrieves data based on marker nodes defined by X and Z coordinates.

  2. Defining Coordinates:

    • Users can specify the area of interest by setting start and end points along the X and Z axes, referred to as X_START, X_END, Z_START, and Z_END.

  3. Making an API Call:

    • With the coordinates defined, the system makes a GET request to the API endpoint, structured as GET API_BASE/dispositions?zstart={Z_START}&zend={Z_END}&xstart={X_START}&xend={X_END}.

  4. Understanding the Response:

    • The API responds with a JSON object containing details of the area, including its name, description, repair method, and types of repairs required. An example of a response includes fields like areaName, areaDesc, repairMethod, repairType, and a list of plies.

  5. Interactive Interface:

    • The user interface interacts with the API seamlessly, displaying the relevant data such as Glass repair method and the list of plies in a clear and concise manner.

  6. Best Practices:

    • Users should ensure that the coordinates entered are within the valid range and pertain to the area of interest to retrieve accurate information.

    • Familiarize oneself with the 3D space layout to input correct coordinates corresponding to the desired location for repair.

  7. Notes:

    • The interface's response display is designed to be user-friendly, providing essential information at a glance.

    • Users are encouraged to consult the API documentation for more details on response structure and potential error handling.

Getting dimensions

{
  "color": {"fa": Number, "r": Number, "g": Number, "b": Number},
  "defectDimensions": {
    "LEFT": Number,
    "LENGTH": Number,
    "RIGHT": Number,
    "ROOT": Number,
    "TIP": Number,
    "WIDTH": Number
  },
  "location": {"x": Number, "y": Number, "z": Number},
  "markerIndex": "String",
  ... // Additional properties as needed
}

The xstart and xend are calculated based on the LEFT and WIDTH properties, while zstart and zend are based on the ROOT and LENGTH, respectively.

🥽