-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Add information about the original URL for an image if it is known #728
Comments
Hi @sankhakarfa , Do you think the issue cover your request? #152 In the future we are going to add import/export an annotation task feature. Thus you will be able to export original data together with annotations. |
@nmanovic It is similar but I want the original link to be the in the annotation xml instead of just the image names to avoid collision of images with similar names. |
I think my issue is somewhat mentioned in #204 But I want to add to that the annotation file should have original link of the files. |
@sankhakarfa , what is the original link to a file in case of "local", "share" sources? |
@nmanovic Need it when using Remote files like S3. As it is hard to trace back images with just basename. |
Hi, it seems we are also interested in something similar (ill just leave it here as an additional usecase and expression of interest of this feature :) ): We are working with a detection dataset that has been automatically labelled. |
In some cases we now where the original file is located (e.g. list of URLs, AWS S3, Azure). Probably it can be a good idea to have the information in dataset formats, which can store such meta information. |
Hi,
It will be nice to have the link of the original images given while task creation to remain in the Annotation XML.
Else a way to retrieve the images used in the task.
Also it will be easier instead of downloading images to the server use the links given to retrieve the frames/images while annotating.
Any direction towards where to look to get the task dataset will be helpful..
The text was updated successfully, but these errors were encountered: