January 17th, 2024

Changelog (v2.146.0)

New

• [Labeling] We are introducing a new project setting that locks annotations in the labeling editor. This feature will give more control over pre-annotations by preventing accidental changes to their positions while allowing for flexible adjustments such as editing sub-jobs or doing a change class.
  As a project admin, you can enable this option by setting the “lockObjects” attribute to true in the JSON interface, available from the “Labeling jobs” menu, like in the example below.

{
  "lockObjects": true,
  "jobs": {
    "OBJECT_DETECTION_JOB": {
      "content": {
        "categories": {
          "CATEGORY_A": {
            "children": [],
            "color": "#472CED",
            "name": "CategoryA",
            "id": "category74"
          },
          "CATEGORY_B": {
            "children": [],
            "name": "CategoryB",
            "color": "#5CE7B7",
            "id": "category75"
          }
        },
        "input": "radio"
      },
      "instruction": "",
      "mlTask": "OBJECT_DETECTION",
      "required": 0,
      "tools": [
        "rectangle"
      ],
      "isChild": false,
      "isNew": false
    }
  }
}

Change

• [Labeling] We now support NITF and JP2 files, commonly used for processing geospatial data.
• [Labeling] Improvements have been made to the PDF editor to offer a smoother labeling experience when handling large documents with over 8000 annotations.

Fix

• [Labeling] When using the Pose estimation tool right after a Clear all action, extra annotations were sometimes added. We've fixed that issue.
• [Labeling] We’ve significantly reduced the response time following a submit action.
• [Labeling] Rotated geospatial images were showing in the editor with a black background, which caused display issues when using them in multi-layer mode. We’ve fixed that issue.