Add JSON file to Cityscapes 1.0 format

[aldyhelnawan]

My actions before raising this issue

• [✓ ] Read/searched the docs
• [✓] Searched past issues #

  Context

Greetings,

So I've tried CVAT for quite some time. And I decided to try to create a custom dataset with the cityscapes format dataset using CVAT on https://app.cvat.ai/ for my next project. The datasets provided from https://cityscapes-dataset.com included the polygon .JSON file for each annotated image (as in the picture below),

.

But when I tried to export my task into Cityscapes 1.0 format on cvat.ai, it doesn't show the .json file.

Is it the way cityscapes-dataset format worked for custom datasets, or is there something else that I missed? I appreciate any assistance. Thank you know advance.

August 25th, 2022.

Best Regards, Aldy.

#

My Environment

• Git hash commit (git log -1):

  ~/cvat$ git log -1 commit d7560bbd39fec68f944515c2591dda74f3764b90 (HEAD -> develop, origin/develop, origin/HEAD) Merge: ba4175bf b7dba6aa Author: Nico Galoppo nico.galoppo@intel.com Date: Tue May 17 11:25:58 2022 -0500

  Merge pull request #4639 from openvinotoolkit/ncgalopp/fix-build

• Docker version docker version (e.g. Docker 17.0.05):

  $ docker version Client: Docker Engine - Community Version: 20.10.17 API version: 1.41 Go version: go1.17.11 Git commit: 100c701 Built: Mon Jun 6 23:02:57 2022 OS/Arch: linux/amd64 Context: default Experimental: true

  Server: Docker Engine - Community Engine: Version: 20.10.17 API version: 1.41 (minimum version 1.12) Go version: go1.17.11 Git commit: a89b842 Built: Mon Jun 6 23:01:03 2022 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.7 GitCommit: 0197261a30bf81f1ee8e6a4dd2dea0ef95d67ccb runc: Version: 1.1.3 GitCommit: v1.1.3-0-g6724737 docker-init: Version: 0.19.0 GitCommit: de40ad0

• Operating System and version (e.g. Linux, Windows, MacOS): Linux Ubuntu 20.04

  $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.4 LTS Release: 20.04 Codename: focal

• For docker ps:

  
  CONTAINER ID   IMAGE                                                           COMMAND                  CREATED        STATUS                 PORTS                                                                                          NAMES
  9a620ab58edb   alpine:3.11                                                     "/bin/sh -c '/bin/sl…"   2 hours ago    Up 2 hours                                                                                                            nuclio-local-storage-reader
  9a3bff829525   cvat/openvino.omz.public.faster_rcnn_inception_v2_coco:latest   "processor"              3 months ago   Up 8 hours (healthy)   0.0.0.0:49153->8080/tcp, :::49153->8080/tcp                                                    nuclio-nuclio-openvino-omz-public-faster_rcnn_inception_v2_coco
  c721c275f029   cvat/openvino.omz.intel.face-detection-0205:latest              "processor"              3 months ago   Up 8 hours (healthy)   0.0.0.0:49156->8080/tcp, :::49156->8080/tcp                                                    nuclio-nuclio-openvino-omz-face-detection-0205
  f1b0d2ae2180   cvat/openvino.omz.public.yolo-v3-tf:latest                      "processor"              3 months ago   Up 8 hours (healthy)   0.0.0.0:49155->8080/tcp, :::49155->8080/tcp                                                    nuclio-nuclio-openvino-omz-public-yolo-v3-tf
  45125bd4e11d   cvat/openvino.dextr:latest                                      "processor"              3 months ago   Up 8 hours (healthy)   0.0.0.0:49154->8080/tcp, :::49154->8080/tcp                                                    nuclio-nuclio-openvino-dextr
  e0a3438b756d   openvino/cvat_server                                            "/usr/bin/supervisord"   3 months ago   Up 8 hours             8080/tcp                                                                                       cvat
  f66b97a9054d   quay.io/nuclio/dashboard:1.5.16-amd64                           "/docker-entrypoint.…"   3 months ago   Up 8 hours (healthy)   80/tcp, 0.0.0.0:8070->8070/tcp, :::8070->8070/tcp                                              nuclio
  b9f7776ff248   openvino/cvat_ui                                                "/docker-entrypoint.…"   3 months ago   Up 8 hours             80/tcp                                                                                         cvat_ui
  de8d1300138e   redis:4.0-alpine                                                "docker-entrypoint.s…"   3 months ago   Up 8 hours             6379/tcp                                                                                       cvat_redis
  5f01468d8353   postgres:10-alpine                                              "docker-entrypoint.s…"   3 months ago   Up 8 hours             5432/tcp                                                                                       cvat_db
  b411595ca475   traefik:v2.4                                                    "/entrypoint.sh --pr…"   3 months ago   Up 8 hours             0.0.0.0:8080->8080/tcp, :::8080->8080/tcp, 80/tcp, 0.0.0.0:8090->8090/tcp, :::8090->8090/tcp   traefik
  b8674fcac7b7   openpolicyagent/opa:0.34.2-rootless                             "/opa run --server -…"   3 months ago   Up 8 hours             0.0.0.0:8181->8181/tcp, :::8181->8181/tcp                                                      cvat_opa

[bsekachev]

@zhiltsov-max Does Cityscapes format have the .json file?

[zhiltsov-max]

Hi. Yes, I see, there are also polygon jsons in Cityscapes, but our implementation only supports images in this format. As a workaround, please check if you can use COCO jsons with polygons.

[aldyhelnawan]

Hi, thank you for your assistance. I see. I will try to use the COCO JSONs for the polygons, see will it fit for my current project. Will the JSON polygon file on cityscapes format be available in CVAT in the future? Thank you in advance.

August 26th, 2022. Best regards, Aldy.

[zhiltsov-max]

Glad to help. I can't make promises on the future plans, but if this problem with Cityscapes is important for our community, we can prioritize it for future releases, and fix it. We are also open for community PR on this topic.