GeostoreBoundingMarkerProto

AI Overview😉

  • The potential purpose of this module is to help Google understand the physical location and boundaries of a specific place or area, such as a lane or lane connection, by associating it with geographical markers and features. This module seems to be focused on understanding the spatial relationships between different geographical entities.
  • This module could impact search results by influencing the ranking of local search results, particularly those related to navigation, directions, or location-based queries. It may also affect the accuracy of Google Maps and other location-based services. By better understanding the physical boundaries and relationships between different geographical features, Google can provide more accurate and relevant results to users.
  • A website may improve its chances of being favored by this module by ensuring that its location-based data is accurate, up-to-date, and properly structured. This could include providing clear and consistent naming conventions for geographical features, using standardized formats for location data, and ensuring that location-based metadata is easily accessible to search engines. Additionally, websites that provide high-quality, location-specific content may be more likely to be associated with relevant geographical markers and features, which could improve their visibility in local search results.

Interesting Module? Vote 👇

Voting helps other researchers find interesting modules.

Current Votes: 0

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

NOTE: BoundingMarkerProto could be compared against one another by canonicalizing them via GetCanonicalBoundingMarker() in google3/geostore/base/internal/lane.cc. Any fields that don't contribute to the definition of a bounding marker in the real world should be bundled with the annotative fields near the bottom and excluded in GetCanonicalBoundingMarker(). LINT.IfChange

Attributes

  • boundingMarker (type: GoogleApi.ContentWarehouse.V1.Model.GeostoreFeatureIdProto.t, default: nil) - References to any gcid:physical_lane_marker features that bound this lane or lane connection.
  • boundingMarkerToken (type: String.t, default: nil) - A token that can be used to identify the version of the data about this bounding marker.
  • flowlineAdjacencyBeginFraction (type: float(), default: nil) - Which part of the flowline does this association refer to? These should be between 0 and 1. These are optionally set, but can be approximated geometrically if they aren’t set. NOTE: These refer to the geometry of this feature.
  • flowlineAdjacencyEndFraction (type: float(), default: nil) -
  • markerAdjacencyBeginFraction (type: float(), default: nil) - Which part of the marker track does this association refer to? These should be between 0 and 1. These are optionally set, but can be approximated geometrically if they aren’t set. NOTE: These refer to the geometry of the marker feature.
  • markerAdjacencyEndFraction (type: float(), default: nil) -
  • side (type: String.t, default: nil) - Which side of the flowline does the marker occur on.

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.GeostoreBoundingMarkerProto{
  boundingMarker:
    GoogleApi.ContentWarehouse.V1.Model.GeostoreFeatureIdProto.t() | nil,
  boundingMarkerToken: String.t() | nil,
  flowlineAdjacencyBeginFraction: float() | nil,
  flowlineAdjacencyEndFraction: float() | nil,
  markerAdjacencyBeginFraction: float() | nil,
  markerAdjacencyEndFraction: float() | nil,
  side: String.t() | nil
}

Functions

Link to this function

decode(value, options)

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

Unwrap a decoded JSON object into its complex fields.