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

move object into upper or below layer #3942

Open
CaRRotOne opened this issue Nov 23, 2021 · 7 comments
Open

move object into upper or below layer #3942

CaRRotOne opened this issue Nov 23, 2021 · 7 comments
Labels
enhancement New feature or request

Comments

@CaRRotOne
Copy link

Dear all:
I know using +/- or "To background"/"To Foreground" can move object to the bottom layer or top layer. If the top z_order layer is 6th, the current z_order of object is 3th, how could I do to move the object from 3th z_order to 4th z_order?

@bsekachev
Copy link
Member

Hi, no way. You can change z_order only to the toppest + 1, to the lowest - 1 levels.

@bsekachev bsekachev added the question Further information is requested label Nov 23, 2021
@CaRRotOne
Copy link
Author

Hi, no way. You can change z_order only to the toppest + 1, to the lowest - 1 levels.

I think design in this way must have a reason. could you explain to me? appreciate.
In my opinion, the method mentioned in my question could be more efficient in some scenarios, the annotator with less experience could easily make annotation if they could edit the z_order layer

@bsekachev
Copy link
Member

The main reason I would say is do not overcomplicate. In the most of cases these two keys are enough (at least I do not remember others such requests for years).
Just annotate image from "furthest" to "closest" objects and you do not need to change zOrder postfact.
If you realized, that the layer of an object is incorrect, you can up or down the object. In case of several layers usually it is very simple.

But I agree, that in case of huge number of layers with a lot of intersections you might need to up/down different objects lots of times. And I wouldn't say that up/down 1 level solves the problem, because you anyway need to up/down the object several times in general. The workaround here is to copy the object, go to necessary layer and past it there.

@nmanovic nmanovic added enhancement New feature or request and removed question Further information is requested labels Nov 23, 2021
@nmanovic
Copy link
Contributor

@CaRRotOne , @bsekachev , probably it is a good idea to look at different approach and see how to improve UX of the feature.

@CaRRotOne
Copy link
Author

CaRRotOne commented Nov 24, 2021

@bsekachev thanks for the explanation. I had discussed with annotators with rich experience, they aggre with your opinion.For beginners, I still think 'up/down 1 level' function is more friendly. @nmanovic we will use cvat frequently these days,I will post some special case if found, I know it is easy to implement technically, but for UX designer, maybe it is not a little change.

@zwfcrazy
Copy link
Contributor

zwfcrazy commented Apr 7, 2022

I also need an easier way to change the layer of an object, because I want to label the relationship such as A is occluded by B and B is occluded by C. The current UX allows us to create an object in a specific layer but it is difficult to change the layer of an existing object, which is, for example, created by auto-annotation.
My requirement can also be achieved by adding an extra attribute to an object. So maybe you can add the function of adding arbitrary user-defined attribute to an object.

@xjf17
Copy link

xjf17 commented Jun 4, 2024

I also need to change the z-order manually. I am working on a building material segmentation dataset. I often have dozens of layers. If I labeled one thing in the wrong layer, I would spend a long time to correct it. If you can add this function, I will be more than delighted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants