I have a project that requires polygons start at a particular location on the object and also be in CCW (counter clockwise) order. Functionality is already built in to LS to view the start point, but requires the polygon is selected. As for winding order, I don't think there is quick way to check this in the current version (1.9.0) of LS.
One possible solution might be to add the ability to set a different stroke width for the first polygon edge. Also, adding a toggle to show (or not show) the start point and first edge without having to actually select a polygon, would allow users to verify polygons much faster, especially when checking images with many polygons. The image below is a good example for this use case.
The first point must always start on the nose, and the winding order must be CCW order... Check.
I don't have a workaround for checking the polygon start point other than just clicking each polygon one by one. As for the winding order, I can get the labels via API GET request, fix any problems, and then PATCH, but this is starting to affect negatively the flow of our downstream labeling pipeline.
I have a project that requires polygons start at a particular location on the object and also be in CCW (counter clockwise) order. Functionality is already built in to LS to view the start point, but requires the polygon is selected. As for winding order, I don't think there is quick way to check this in the current version (1.9.0) of LS.
One possible solution might be to add the ability to set a different stroke width for the first polygon edge. Also, adding a toggle to show (or not show) the start point and first edge without having to actually select a polygon, would allow users to verify polygons much faster, especially when checking images with many polygons. The image below is a good example for this use case.
The first point must always start on the nose, and the winding order must be CCW order... Check.
I don't have a workaround for checking the polygon start point other than just clicking each polygon one by one. As for the winding order, I can get the labels via API GET request, fix any problems, and then PATCH, but this is starting to affect negatively the flow of our downstream labeling pipeline.