GoodocRotatedBoundingBox

AI Overview😉

  • The potential purpose of this module is to help Google's algorithm understand the layout and structure of a webpage by identifying and analyzing the position, size, and orientation of elements on the page, such as images, text blocks, or other content. This can help the algorithm better comprehend the content and relevance of a page.
  • This module could impact search results by allowing Google to more accurately assess the relevance and importance of page elements, potentially leading to more accurate rankings and a better user experience. For example, if a webpage has a key image or piece of text that is not aligned with the page's grid, this module could help Google understand its significance and weight its importance accordingly.
  • To be more favorable for this function, a website could ensure that its page structure and element layout are clean, organized, and easy to parse. This could involve using clear and consistent HTML and CSS, avoiding complex or nested layouts, and using descriptive and semantic markup to help Google's algorithm understand the purpose and importance of different page elements. Additionally, optimizing images and other media to have clear and descriptive metadata could also help Google better understand the content and relevance of a page.

Interesting Module? Vote 👇

Voting helps other researchers find interesting modules.

Current Votes: 0

GoogleApi.ContentWarehouse.V1.Model.GoodocRotatedBoundingBox (google_api_content_warehouse v0.4.0)

Similar to goodoc.BoundingBox, but containing an angle of rotation, thus able to represent non-axis-aligned boxes. RotatedBoundingBox can be used in combination with BoundingBox to better represent non-axis-aligned page structural elements. In such case, two bounding boxes can be used per element. A RotatedBoundingBox that is rotated to tightly encompass the element; embedded (as tightly as possible) inside an axis-aligned BoundingBox. Note that there is some amount of ambiguity regarding what angle and vertex to use. Consider a square with axis-aligned diagonals: B / \ A C \ / D This can either be represented as a -45 degree rotation around A, a 45 degree rotation around B, a 135 degree rotation around C, or a -135 degree rotation around D. Which one you use depends on your use case, but one recommendation is to use the vertex that would be top left if the reader was reading it in the 'natural' orientation.

Attributes

  • Angle (type: number(), default: nil) - Angle of rotation of the original non-rotated box around the top left corner of the original non-rotated box, in clockwise degrees from the horizontal.
  • Height (type: integer(), default: nil) -
  • Left (type: integer(), default: nil) - Coordinates and sizes are expressed in pixels, where the top-left pixel is (0, 0). The coordinates refer to the corner of the top-left vertex of the unrotated version of the box.
  • Top (type: integer(), default: nil) -
  • Width (type: integer(), default: nil) -

Summary

Types

t()

Functions

decode(value, options)

Unwrap a decoded JSON object into its complex fields.

Types

Link to this type

t()

@type t() :: %GoogleApi.ContentWarehouse.V1.Model.GoodocRotatedBoundingBox{
  Angle: number() | nil,
  Height: integer() | nil,
  Left: integer() | nil,
  Top: integer() | nil,
  Width: integer() | nil
}

Functions

Link to this function

decode(value, options)

@spec decode(struct(), keyword()) :: struct()

Unwrap a decoded JSON object into its complex fields.