-
Notifications
You must be signed in to change notification settings - Fork 147
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
Generated image IDs are non-unique #3
Comments
@msnidal I will also check this problem. |
@msnidal can you please show us your hacky solution? |
@davidhuangal , this code works on assumption that your file names are according to serial integer. like image1,image2,image3 or any_name1,any_name2... , so if you're having file which is like a_1.jpg,b_1.jpg then reges used in the code assigns the same id. so if you want to solve it then you can use this method:
replace
|
Yeah having the same issue.
And for each filename ("X_Y_Z.png") it assumes the id is always X. |
Is there any solution for this? |
Yeah. I'm seeing the same here. My test image IDs are J073-xxxxxxxxxx. This fix works 95: |
I see that the issue is still open, which I encountered as well. I share a quite simple solution, which seems to do the job. Adding a simple count generates unique ids. `
` If you guys encounter another issue, let me know so we can take a look. |
I have the same issue here. I fixed this issue in my forked repository. |
Firstly, thanks for creating this script, it was a great help to me.
When I first ran it, it worked almost perfectly, but with one problem - the COCO format image IDs were all over the place, many non-unique (many 0s for example) which breaks the COCO format. I saw how you're generating them as a function of the filename, and given the image IDs have no VOC equivalent, I think it would make more sense to do a strict ordering per image.
I did a hacky solution for now, I'm leaving this issue open so I can come back to it later and open a PR with a fix. If anybody else is having this problem, look for img_id and you can try incrementing it manually for the moment.
The text was updated successfully, but these errors were encountered: