0

Place ID vs WOE ID vs Location ID

Yahoo seems to change it's location identification systems more often than I change my socks...

Is the Place ID unique to Upcoming? Is there a way to use the new Yahoo Where on Earth ID instead? What about the old Yahoo Location ID?

How do you look up the Place ID, possibly based on the WOE ID or Location ID? (example would be helpful)

Thanks.

by
6 Replies
  • Hi,

    I believe place_id is unique to Upcoming and Flickr. We've partially migrated our API to WOE IDs (e.g., event.search supports 'woeid' as a parameter), but there are still remnants of place_id that we should deprecate over time. Can you let me know which API you would like to see woeid support for?

    For now, if you need to find a place_id, the easiest way is to go to http://upcoming.yahoo.com/place/, run a search, get the place_id from the URL you are sent to (e.g., http://upcoming.yahoo.com/place/63v7zaqQCZxX). Upcoming does not offer a place_id "search" API, but you might be able to use Flickr's places.find method: http://www.flickr.com/services/api/flickr.places.find.html.

    Thanks,
    Greg
    0
  • QUOTE (Greg @ Apr 12 2010, 08:20 AM) <{POST_SNAPBACK}>
    Hi,

    I believe place_id is unique to Upcoming and Flickr. We've partially migrated our API to WOE IDs (e.g., event.search supports 'woeid' as a parameter), but there are still remnants of place_id that we should deprecate over time. Can you let me know which API you would like to see woeid support for?

    For now, if you need to find a place_id, the easiest way is to go to http://upcoming.yahoo.com/place/, run a search, get the place_id from the URL you are sent to (e.g., http://upcoming.yahoo.com/place/63v7zaqQCZxX). Upcoming does not offer a place_id "search" API, but you might be able to use Flickr's places.find method: http://www.flickr.com/services/api/flickr.places.find.html.

    Thanks,
    Greg


    Thanks... Yes I'm interested in Upcoming. The application I'm using already has a place for users to enter their WOE ID. It seems rather silly for them to need to enter another one. It's also strange that there is no place_id search API. Thanks for the suggestion about Flickr, I'll look into it.
    0
  • QUOTE (Greg @ Apr 12 2010, 08:20 AM) <{POST_SNAPBACK}>
    We've partially migrated our API to WOE IDs (e.g., event.search supports 'woeid' as a parameter)


    Is that documented? I don't see that here:

    http://upcoming.yahoo.com/services/api/event.search.php

    If not, can you please give me an example?
    0
  • QUOTE (Son ofR @ Apr 12 2010, 09:49 AM) <{POST_SNAPBACK}>
    Is that documented? I don't see that here:

    http://upcoming.yahoo.com/services/api/event.search.php

    If not, can you please give me an example?


    Jeez... sorry i must be sleepy. I see it now. Unfortunately I can't seem to edit or delete previous posts, so sorry for the hat trick.
    0
  • The event.search method documentation does not specify whether searching by WOEID respects the radius parameter. It appears it does not? Can you confirm this?

    I say "appears" because an event search by WOEID for my city only returns 6 results (without additional parameters), while the web page lists 5 pages of events! That's also puzzling me.

    I'm using this:

    CODE
    curl -G  --d api_key=<key> -d method=event.search -d woeid=12778594 -d radius=50 http://upcoming.yahooapis.com/services/rest/
    0
  • QUOTE (Loren @ Apr 21 2010, 05:55 AM) <{POST_SNAPBACK}>
    The event.search method documentation does not specify whether searching by WOEID respects the radius parameter. It appears it does not? Can you confirm this?

    I say "appears" because an event search by WOEID for my city only returns 6 results (without additional parameters), while the web page lists 5 pages of events! That's also puzzling me.

    I'm using this:

    CODE
    curl -G  --d api_key=<key> -d method=event.search -d woeid=12778594 -d radius=50 http://upcoming.yahooapis.com/services/rest/


    That's correct -- searching by woeid is the same as searching by place_id in that events are picked from the exact boundaries of the region, and ignores any radius specified. (I'll make a request for our engineers to update the documentation for a future release.)

    Also, to clarify, when you do an event search on the Upcoming website, the default is a radius search. If you specify the placeid directly for a boundary search, you also get 6 events: http://upcoming.yahoo.com/search/?type=&am...cqYA5tnqlnoJA-- (11 total, actually, if you count the repeating events separately).
    0
This forum is locked.

Recent Posts

in Upcoming API - General Questions