[IO-1661][external] Error messages were not clear to customers

[owencjones]

Problem

COCO iscrowd error messages were not clear to customers.

Solution

Have changed the messages to explain more verbosely what the issue is with a crowd import.

Changelog

coco.py now uses logger, and the message is more verbose

[linear]

IO-1661 Request: Improve error message for COCO import

Product Request Form submission from Moe

Is this a V1 or V2 issue, or both?
V2

​What is your request?
Hey team, we’ve had some cases of customers messaging us when attempting to import complex polygons in COCO format. When doing so, they receive this error message - "Warning, unsupported RLE, skipping". I know that this error message is correct in this instance since they have iscrowd set to 1, however, it sometimes misleads customers into thinking that we support RLE encoding for COCO.
Is it possible to make the error message more candid so that customers don’t misunderstand? If so, I think a message like - "Warning, RLE encoding is not supported, skipping".

​What are the acceptance criteria?
This change is made in some way (i.e. the error message is more candid).

​Which product area is this request is applicable to (specify a team if known)?
IO

How important is this request?
High - not vital, but adds significant financial or customer value

Do you have any deadline for this request (if deadline applicable, specify why)?
Sooner rather than later would be nice.

Any additional info / Specify why Urgent or High:
This error message has caused several customers to misunderstand our support for complex polygons so we've had to spend additional time and resources helping them understand that complex polygons are not supported in COCO, for example. From there, we usually have to spend time assisting them with a workaround of some kind, if possible.

[Nathanjp91]

One thing to consider

[NPatel1980]

QA passed, paired with Owen and observed the new message.