Notes on Location Normalization and Status

Chapter 1: Coordinates Of Location

• Normalization Process

  • Triggered when a client adds a location and clicks save.
  • Validates the address to retrieve coordinates.
  • Occurs on initial save and any subsequent updates to the location.
  • If a location has been cleansed before, its data will override normalization results.

• Geocoding API

  • Normalization starts with Google Geocoding API to obtain coordinates.
  • If it fails, the process falls back to Google Autocomplete API.
  • If both fail, normalization is considered unsuccessful, leading to a review process.

• Cleansing Team Review

  • If normalization fails, clients or the cleansing team need to evaluate the location manually.

Chapter 2: Status On Location

• Viewing Normalization Status

  • Information about normalization is visible in ABE (location management system).
  • Normalization status and source can be found under the cleansing status for each location.
  • Details, including pins related to a location, are also accessible.

• Types of Pins

  • Auto PIN: Automatically assigned by the system based on retrieved coordinates.
  • User PIN: Assigned if the user's input differs from the coordinates determined by the system.
  • Admin PIN: Set by an admin through the backend of ABE.

Chapter 3: Generated Pin

• Reviewing Pin Details

  • Users can view current auto or user PINs and assess discrepancies between them.
  • Important for resolving address conflicts (differences in city, address, etc.).

• Needs Review Item

  • If the normalization fails, a needs review item is generated, sending the location for cleansing.
  • Prevents the location from syncing with any directory until resolved.

• Questions and Clarifications

  • Participants are encouraged to ask for clarification on the normalization process and its implications.