Location coordinates returned by Answers

Search
1

Hello,

I am using Answers Headless with some location entities and I want to display the locations as map markers on a custom Mapbox map. I see that I have a bunch of different coordinate fields to choose from and for this particular location, all the coordinates are the same:

            "cityCoordinate": {
              "latitude": 32.735599517822266,
              "longitude": -97.10771942138672
            },
            "geocodedCoordinate": {
              "latitude": 32.747594,
              "longitude": -97.082073
            },
            "isoRegionCode": "TX",
            "timezone": "America/Chicago",
            "yextDisplayCoordinate": {
              "latitude": 32.747594,
              "longitude": -97.082073
            },
            "yextRoutableCoordinate": {
              "latitude": 32.747424,
              "longitude": -97.0816864
            },

Are these values ever different than one another and which should I use for my map markers?

2

Great question @Aaron_Pavlick!

Yext has a very robust set of lat/lngs that are returned via our APIs to help build great map experiences.

TLDR: In most cases, when using our APIs to build out a map with a map marker you’ll want to use the yextDisplayCoordinate which is the most precise rooftop pinpoint for a location.

In Yext, you can store several different types of geocodes, including:

  • Display - This should reflect the center point of your location.
  • Dropoff - This lets you set where ride services or taxis should dropoff a visitor to your location
  • Pickup - This lets you set where ride services or taxis should pickup a visitor to your location
  • Routable - This lets you set where a GPS should guide a visitor with driving directions
  • City - this is automatically set based on your city/region to the center point of the city, best used for service area businesses

You can update any of these by clicking into the Map on Entity Edit and placing the pin for each type. Or, you can update these via our Entities API, Connectors, or Entity Upload.

image
image1920×1186 210 KB

In the API response, we provide all of the possible lat/lngs stored for that location. The fields with the “yext” prefix are our best recommended geocode but we also provide the output of our automated algorithms (the coordinates without the “yext” prefix).