Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Google Vision returns paragraph vertices in text-relative order. Vertices 0 and 2 are therefore not necessarily the upper-left and lower-right corners in image coordinates. Using only those vertices crops diagonally rotated text and reverses the bounds of 180-degree text.
Construct the axis-aligned region from the minimum and maximum x/y over all vertices, retaining the existing text and source metadata. The provider documents the rotation-dependent vertex order in its bounding-box contract.
Validation
TextRegionsconstruction.Draft pending the full repository test gate.
Checklist