-
-
Notifications
You must be signed in to change notification settings - Fork 233
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
Labelbox2YOLO Json.load issue #102
Comments
@gruberanthony thank you for reporting this issue. Please ensure you are using the latest version of the package. If the problem persists, could you share a minimal example of the JSON file causing the error? This will help us diagnose the issue more effectively. |
So it appears that the dataset I am using exports as a ndjson file but keeps the '.json' tag when using the sdk export options. However, after converting the file to .json I am able to get past the json.load issue and instead will have to change everything associated with the paths to the image url and the associated labels for the bounding box etc. I have added a shortened example of my json file from Labelbox as an example. |
I updated the conversion for anyone that may have similar JSON as myself. The only additional thing is simply running the .ndjson through the additional file I have attached. Let me know if this is a one off occurrence as I found this really odd. |
@gruberanthony thank you for sharing your solution and the updated conversion file. It's possible that the issue is specific to certain Labelbox exports. If others encounter similar problems, your contribution will be valuable. If you have any further questions or run into additional issues, feel free to reach out. |
There appears to be an issue with the json.load for the labelbox conversion as each time I attempt to run the conversion using the raw json file that is downloaded via the sdk method from labelbox I get the following error:
"JSONDecodeError: Extra data: line 2 column 1 (char 4075)". Any assistance would be appreciated.
The text was updated successfully, but these errors were encountered: