0

[BUG] Query for * with latitude and longitude returns no results

According to the Local Search Documentation:

QUOTE
Using a query of "*" returns all values that match other criteria in the search (category, radius, and so on).

This works fine if I provide a location, but if I perform a query based on latitude and longitude no results are returned:

Local Search API: query=*&longitude=-122.900614&latitude=47.038755 (requires an App ID to test)

YQL Console: select * from local.search(0,20) where query="*" and longitude="-122.900614" and latitude="47.038755"

This behavior is unexpected, undesirable, and undocumented.


Adding a radius has no effect:

YQL Console: select * from local.search(0,20) where query="*" and longitude="-122.900614" and latitude="47.038755" and radius="2"


Changing the query from the "*" wildcard to something specific, like "food" causes it to work correctly:

YQL Console: select * from local.search(0,20) where query="food" and longitude="-122.900614" and latitude="47.038755"


Changing the query to use a location, like "Olympia, WA" causes it to work correctly, even with the "*" wildcard:

YQL Console: select * from local.search(0,20) where query="*" and location="Olympia, WA"


This last query that uses a location might provide a work-around for me, but it is not preferable. I would like to be able to return a list of businesses near the center of a Yahoo! map in the same way that Yahoo! Local does. I could reverse geocode the latitude and longitude, and then pass that in as a location, but that seems incredibly wasteful and silly.


To give some background: I am working on a prototype of a public application that is meant to help people with disabilities to find work in the State of Washington. We hope to be able to show a list of businesses that are near a person's home. Being able to show all business, without providing a specific category or search term, is a business requirement.

I have already implemented a prototype using Google's services but the Yahoo! services, in particular YQL, seem more flexible for achieving our goals.

Thank you for your time!

-Josh

by
15 Replies
  • QUOTE (Joshua @ May 19 2010, 11:37 AM) <{POST_SNAPBACK}>
    According to the Local Search Documentation:


    This works fine if I provide a location, but if I perform a query based on latitude and longitude no results are returned:

    Local Search API: query=*&longitude=-122.900614&latitude=47.038755 (requires an App ID to test)

    YQL Console: select * from local.search(0,20) where query="*" and longitude="-122.900614" and latitude="47.038755"

    This behavior is unexpected, undesirable, and undocumented.


    Adding a radius has no effect:

    YQL Console: select * from local.search(0,20) where query="*" and longitude="-122.900614" and latitude="47.038755" and radius="2"


    Changing the query from the "*" wildcard to something specific, like "food" causes it to work correctly:

    YQL Console: select * from local.search(0,20) where query="food" and longitude="-122.900614" and latitude="47.038755"


    Changing the query to use a location, like "Olympia, WA" causes it to work correctly, even with the "*" wildcard:

    YQL Console: select * from local.search(0,20) where query="*" and location="Olympia, WA"


    This last query that uses a location might provide a work-around for me, but it is not preferable. I would like to be able to return a list of businesses near the center of a Yahoo! map in the same way that Yahoo! Local does. I could reverse geocode the latitude and longitude, and then pass that in as a location, but that seems incredibly wasteful and silly.


    To give some background: I am working on a prototype of a public application that is meant to help people with disabilities to find work in the State of Washington. We hope to be able to show a list of businesses that are near a person's home. Being able to show all business, without providing a specific category or search term, is a business requirement.

    I have already implemented a prototype using Google's services but the Yahoo! services, in particular YQL, seem more flexible for achieving our goals.

    Thank you for your time!

    -Josh


    I can confirm I'm seeing the same. This was working earlier in the week but now doesn't seem to be working.

    Any help would be appreciated.
    Thanks
    0
  • QUOTE (jeffivans@... @ May 20 2010, 06:44 AM) <{POST_SNAPBACK}>
    I can confirm I'm seeing the same. This was working earlier in the week but now doesn't seem to be working.

    Any help would be appreciated.
    Thanks


    I'm seeing the exact same thing. It would be great if someone could look into this.

    Thanks,
    Rudro.
    0
  • QUOTE (SexyAngel92 @ May 21 2010, 09:33 AM) <{POST_SNAPBACK}>
    I'm seeing the exact same thing. It would be great if someone could look into this.

    Thanks,
    Rudro.


    Any word on this issue? I'm seeing the same as of tonight, May 22 about 1230a PDT. It worked and now it doesn't.

    Rob
    0
  • Can this be done in Google? Not seeing any response so I'm wondering if these services are be depreciated.
    0
  • QUOTE (jeffivans@... @ May 23 2010, 05:40 PM) <{POST_SNAPBACK}>
    Can this be done in Google? Not seeing any response so I'm wondering if these services are be depreciated.


    This can be done in Google. You can set the center point of a google.search.LocalSearch object, execute("*"), and then iterate through the result pages. At this time Google is limited to "a maximum of 32 total results", which is one of the reasons that I am interested in switching to Yahoo!.
    0
  • QUOTE (Rob @ May 21 2010, 11:30 PM) <{POST_SNAPBACK}>
    Any word on this issue? I'm seeing the same as of tonight, May 22 about 1230a PDT. It worked and now it doesn't.

    Rob


    I still haven't heard anything. I have checked every couple of days since I filed the bug report and the bug still exists. I suspect that this forum isn't monitored or that the staff simply are too busy with other things.

    I personally can't delay implementation any longer so I have to go with the Google Local Search API, despite its limitations.

    -Josh
    0
  • QUOTE (Joshua @ Jun 8 2010, 01:35 PM) <{POST_SNAPBACK}>
    I still haven't heard anything. I have checked every couple of days since I filed the bug report and the bug still exists. I suspect that this forum isn't monitored or that the staff simply are too busy with other things.

    I personally can't delay implementation any longer so I have to go with the Google Local Search API, despite its limitations.

    -Josh


    Change * to ? :-)
    0
  • QUOTE (melman101 @ Jul 4 2010, 10:34 AM) <{POST_SNAPBACK}>
    Change * to ? :-)


    Using a question mark instead of a star doesn't seem to help queries based on longitude and latitude:

    Local Search API: query=?&longitude=-122.900614&latitude=47.038755&start=0&results=20 (requires an App ID to test)

    YQL Console: select * from local.search(0,20) where query="?" and longitude="-122.900614" and latitude="47.038755"
    0
  • QUOTE (Joshua @ Jul 6 2010, 02:16 PM) <{POST_SNAPBACK}>
    Using a question mark instead of a star doesn't seem to help queries based on longitude and latitude:


    Correction: The question mark doesn't help queries without a category. Using the question mark in combination with a longitude, latitude, and category does produce results:

    YQL Console: select * from local.search(0,20) where query="?" and longitude="-122.900614" and latitude="47.038755" and category="96926236"
    0
  • In case anyone is wondering: this bug still persists; I am still interested in a fix for it.

    -Josh
    0
  • QUOTE (Joshua @ Aug 24 2010, 12:06 PM) <{POST_SNAPBACK}>
    In case anyone is wondering: this bug still persists; I am still interested in a fix for it.

    -Josh


    Hi Josh,

    I am a Yahoo! Local Engineer we are looking into the problem. Sorry for the delay. We are trying to track down the problem and fix it for you. Thanks for using YDN!

    Rick
    0
  • QUOTE (Rick @ Aug 27 2010, 09:38 AM) <{POST_SNAPBACK}>
    Hi Josh,

    I am a Yahoo! Local Engineer we are looking into the problem. Sorry for the delay. We are trying to track down the problem and fix it for you. Thanks for using YDN!

    Rick


    Thank you Rick; best of luck to you!

    -Josh
    0
  • QUOTE (Rick @ Aug 27 2010, 09:38 AM) <{POST_SNAPBACK}>
    Hi Josh,

    I am a Yahoo! Local Engineer we are looking into the problem. Sorry for the delay. We are trying to track down the problem and fix it for you. Thanks for using YDN!

    Rick


    Any update on this bug as it is affecting me as well?
    0
  • Is there any update on the fix? I am still having this problem now.
    0
  • It looks like the patch to fix this is live now, so these queries should be working again.

    Brian Cantoni
    Yahoo! Developer Network
    0
This forum is locked.

Recent Posts

in Local API - General Questions