Adds support in augmentation for keypoints

Short Description

I am interested to use RandAugment for object detection with keypoints. Instead of re-doing everything on my own, I would like to add support for keypoints in the augmentation present in this repo.

Papers

None I know off

Existing Implementations

Already have some PR

Other Information

I would propose to:

• Add BaseImageAugmentationLayer.augment_keypoints(self,keypoints,transformation,**kwargs) method
• Modify BaseImageAugmentationLayer._augment() to augment keypoints if passed as a dict.
• Modify BaseImageAugmentationLayer.get_random_transformation() to accept keypoints as an argument
• Makes sures all augmentations in RandAugment do implement augment_keypoints and augment_bounding_boxes. This will require to re-implement by compositon RandomContrast,RandomBrightness,RandomTranslation

[atuleu]

Following the discussion in #519, here are the tasks to perform in single PR from atuleu/keras-cv@dev/keypoints:

• create a PR adding support for keypoint formats & utilities (discard out of image, converters, etc) -> #585
• update the BaseImageAugmentationLayer in a PR -> #586
• add ALL of the no-op augmentations in a single PR; so all of the ones that just return keypoints -> #588
• Adds a function to generalize how bounding boxes should be augmented -> #599
• Add augmentation logic to RandomTranslation (with demonstration)
• Refactor and add augmentation logic to RandomRotation (with demonstration)
• Imports and add augmentation logic to RandomContrast
• Imports and add augmentation logic to RandomBrightness
• Add augmentation logic to RandomResizedCrop
• Add augmentation logic to RandomShear (with demonstration)

[atuleu]

@atuleu

I think bounding box augmentation is erroneous for shear and rotation transform. This will lead to larger bounding boxes than the bounding box covering the sheared/rotated object. Shouldn’t the library show some kind of warning if approximative bounding boxes augmentation are made ?

Bounding boxes should be clipped in that cases and same goes to keypoint type as well. Isn’t it take in account by already in shear transformation? Mentioning @pranavjadhav001 to comment on this as he’s working on it now.

@innat

So there was no augment_bounding_box() for RandomShear ( I added it here aa4a178a60bbdccfb9c4881409a652363c51e45b ). There was last week some augment_bounding_box() for RandomRotation , but no clipping.

@LukeWood I think we should go for a reduced amount of format of ‘xy’ and ‘rel_xy’. Then if more format are needed, they could always be added afterwards. Should I go forward and add this to #519 ?