determining the location of a deal (specfically in the case of travel deals)

29 views
Skip to first unread message

Dan

unread,
Apr 11, 2013, 6:26:07 PM4/11/13
to yipi...@googlegroups.com
I'd like to identify the location of a travel deal accurately but don't know which attribute to rely on. When I look at the JSON in the response I notice the location in the following locations

division -> name
business -> location -> smart_locality
business -> location -> locality

The three are often identical but there are a few cases where the locality attribute is more precise. For example locality reads Sedona (and corresponds with the zip code) while the name attribute reads AZ.

There are a few cases where locality and smart_locality are empty while the name attribute has a value.

Which is the most accurate and reliable attribute for determining location of a deal?

cheers

Dave Tomback

unread,
Apr 12, 2013, 1:55:40 PM4/12/13
to yipi...@googlegroups.com
In terms of breadth, division is best. Not every deal will have a business location associated with it. 



--
You received this message because you are subscribed to the Google Groups "Yipit API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to yipit-api+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Dan

unread,
Apr 12, 2013, 10:29:44 PM4/12/13
to yipi...@googlegroups.com
thanks. What the API definition for those fields - when all three exist but are different is one considered the most precise?

One other question. Are there any plans to expose the fine print for travel deals in the API? I am specifically interested in extracting things like blackout dates and so on?

cheers
You received this message because you are subscribed to a topic in the Google Groups "Yipit API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/yipit-api/aLwp1A39vb8/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to yipit-api+...@googlegroups.com.

Dave Tomback

unread,
Apr 22, 2013, 3:58:59 PM4/22/13
to yipi...@googlegroups.com
No current plans to add fine print. However, I've added this to a list of requests. We typically prioritize these based on how often these features/additions are requested.
Reply all
Reply to author
Forward
0 new messages