I’ve recently started to move over our image annotation system to prodigy with good results. I’m currently using a personal license to get started, with the intent to update to a commercial license once we verify that everything is workable.
However! I’ve run into some limitations that I’m not sure how to work around, and I’m hoping I can get some assistance.
We’re annotating industry specific images in natural environments. As part of this, we’re extracting the polygon boundary of target objects with high precision requirements. This is a set of tasks where we first determine if we need to annotate an image, then split the annotation into drawing polygons, then labeling them in a separate task, and finally verifying the annotated images are of acceptable quality in a third task.
We can’t efficiently zoom and reduce line thickness and/or opacity so that we can precisely select an object boundary. This is blocking our transition right now and the issue I’m most keen on getting fixed.
Attempting to zoom (e.g. in Chrome) increases the size of the accept/deny buttons to quickly cover the whole screen. Is there a way to ensure those buttons are always below the task card even if it forces scrolling for large tasks, or keep them at a consistent size using max-width or some other property?
As you see from the background, we have a few different task types, primarily image_manual and choice. For choice with auto accept on, the accept/deny/skip-UI is causing problems.
We want to be able to hide the footer with CSS for only this task type, e.g. by specifying a CSS file in the task configuration. It does not seem to be possible currently, but would make the editor easier to work with, and possibly allow us to solve some of the other problems on our own. Is there a way forward on this you could point me at?
I’ve read about some solutions using greasemonkey, but we’re not necessarily in control of the end-user browser.
We have an interest in a masking tool, where we can paint pixels that belong to specific classes, as some of our annotations are unsuitable to mark with polygons due to the complexity of the object. This is less of a priority, but would be useful.
Looking forward to hearing back from you. Thanks!