GeostoreLogicalBorderProto

AI Overview😉

  • Potential purpose of module: This module, GeostoreLogicalBorderProto, appears to be responsible for grouping and modeling geographical borders between regions. It helps to identify and categorize borders based on their attributes, such as disputed or undisputed status, and associates them with specific regions.
  • Impact on search results: This module could impact search results by influencing the relevance and accuracy of location-based searches. For example, if a user searches for information about a specific border or region, the search results may be more accurate and relevant if the algorithm can understand the complexities of the border, including its disputed or undisputed status. This could also affect the ranking of results, with more accurate and relevant results appearing higher in the search results.
  • Optimization for this function: To optimize for this function, a website may want to ensure that its content accurately and clearly identifies geographical borders and regions. This could include using precise and consistent naming conventions for borders and regions, as well as providing clear and accurate information about the status of each border (e.g., disputed or undisputed). Additionally, the website may want to use structured data and schema markup to help search engines understand the relationships between different geographical entities.

Interesting Module? Vote 👇

Voting helps other researchers find interesting modules.

Current Votes: 0

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

A logical border is a grouping of border features, which together model a divide between two regions. The borders within this grouping share common attributes, such as the regions they divide, and may represent a conceptual group of borders, of which may be wholly disputed, wholly undisputed, or a mixture of disputed and undisputed. Note that any borders within this group may be part of multiple logical borders. A logical border is required to have a name describing what the grouping represents (e.g. "US - Mexico Border", "Kosovo - Serbia Border (Disputed)").

Attributes

  • borderSegment (type: list(GoogleApi.ContentWarehouse.V1.Model.GeostoreFeatureIdProto.t), default: nil) - All the border segments which make up this logical border. Border segments must be TYPE_BORDER features which have the same left/right features. This is a many-to-many bidirectional relationship, so any border segment within this list might be part of another logical border.
  • status (type: String.t, default: nil) - The logical border status identifies its legal status. This is similar to the BorderStatus present within border segments, but applies to the group as a whole.

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.GeostoreLogicalBorderProto{
  borderSegment:
    [GoogleApi.ContentWarehouse.V1.Model.GeostoreFeatureIdProto.t()] | nil,
  status: 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.