Skip to content
This repository has been archived by the owner on Apr 28, 2018. It is now read-only.

Improve location disambiguation beyond purely GPS coordinates #83

Open
liuche opened this issue Dec 20, 2016 · 1 comment
Open

Improve location disambiguation beyond purely GPS coordinates #83

liuche opened this issue Dec 20, 2016 · 1 comment

Comments

@liuche
Copy link
Contributor

liuche commented Dec 20, 2016

Before Hawaii, we made the decision to switch to GPS coordinate matching only (discarding location name) because the Yelp location search was made worse by adding the location name. Now that we've finished that trial, we should find ways to improve that matching (e.g., through fuzzy name matching, etc)

@jhugman
Copy link
Contributor

jhugman commented Dec 21, 2016

For reference – 

  1. neither Yelp nor Eventful's location data are especially accurate (e.g. up to a mile between a venue's location as found in Eventful versus Google Places).
  2. yelp's name + location search often returns nothing.
  3. Google Places API sometimes returns good results, but not others.
  4. Factual Crosswalk provides Eventful IDs, but not much Yelp data.

This is a generalized problem, and worthy of discussion with the Context Graph server team.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants