My favorites | Sign in
Project Home Wiki Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 30: Empty Location data in response
8 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  ----
Closed:  Jan 2012


Sign in to add a comment
 
Reported by bengal...@gmail.com, Nov 3, 2011
What steps will reproduce the problem?
1. make an Oauth 1.0 or 2.0 request for locations

What is the expected output? What do you see instead?
I expect location information in my response and I get empty json

{"data":{"kind":"latitude#locationFeed","items": 
[{"kind":"latitude#location"},{"kind":"latitude#location"}, 
{"kind":"latitude#location"}]}} 

What version of the product are you using? On what operating system?

Please provide any additional information below.

I have been using Google Latitude for the past 3 months and my application was receiving the typical json response with location data. My application did not change and now I received empty location data. I have refreshed my oauth token and tried oauth 1.0 and 2.0 with the same results. If I am making a faulty request I should be receiving an error not empty json data.
Nov 9, 2011
#1 ad...@worldtravelblog.com
I have tried through the google oauth playground at http://googlecodesamples.com/oauth_playground/index.php with the same result.
Nov 15, 2011
#2 b...@eorgainc.com
Here the same problem. I wonder, that nobody responds since it's a important part of the latitude project. Working on a website which would use the latitude app to track dog walks. Anybody with german language skills welcome to take part in the public beta. http://doggy.heroku.com
Nov 26, 2011
#3 regis.de...@gmail.com
This is also what the Google API explorer returns https://code.google.com/apis/explorer/#_s=latitude&_v=v1&_m=location.list

Nov 28, 2011
#4 ddewa...@gmail.com
When working with the playground, are you providing a granularity in your request ? I noticed that the playground ALWAYS returns empty location objects in its feed when no granularity is provided.

On the other hand, when a granularity is provided, some Google accounts still return empty locations (together with valid locations) in their feed.

ex: There is one Google account that returns the following (also in the playground). Obviously the 4th location is invalid and Google Latitude should never return that.


{"kind":"latitude#location","timestampMs":"1322502196000","latitude":52.5206645,"longitude":13.4473211,"accuracy":50,"speed":0,"altitude":84},{"kind":"latitude#location","timestampMs":"1322502137000","latitude":52.5210218,"longitude":13.4471918,"accuracy":50,"speed":1,"altitude":86,"altitudeAccuracy":0},{"kind":"latitude#location","timestampMs":"1322502124439","latitude":52.5210914,"longitude":13.4468245,"accuracy":31},
{"kind":"latitude#location"},
{"kind":"latitude#location","timestampMs":"1322502045194","latitude":52.5217483,"longitude":13.4480523,"accuracy":124},
{"kind":"latitude#location","timestampMs":"1322501981638","latitude":52.5220849,"longitude":13.4500731,"accuracy":28},
{"kind":"latitude#location","timestampMs":"1322501921680","latitude":52.5220303,"longitude":13.450057,"accuracy":56},

Nov 28, 2011
#5 ddewa...@gmail.com
It might also be worthwhile for the Latitude team to check how these empty locations got added in the first place ? I would imagine that a latitude/longitude and timestamp are mandatory fields.
Nov 28, 2011
Project Member #6 jli...@google.com
(No comment was entered for this change.)
Labels: Internal-5679564
Nov 30, 2011
Project Member #7 jli...@google.com
Thanks for pointing out this issue.  Currently, when the user sets their location to hidden, or the developer is requesting city level location but the reverse geocode to get city level location failed, we will return this type of empty response.  

We've got an internal bug filed to fix this behavior so that in the future we will not return empty responses, but in the meantime please insure you code defensively to check whether the location response includes all the properties required for your app.
Labels: Internal-5682800
Nov 30, 2011
#8 ddewa...@gmail.com
The reverse geocoding for city level is that an internal thing ? Latitude API does not expose addresses in any of its calls right (only coordinates) ?
Nov 30, 2011
Project Member #9 jli...@google.com
Yes this is an internal request we make to generalize the location when a more course [city level] granularity is requested (or authorized), and is basically what you get if you were to run a set of coordinates through the reverse geocoder described at https://code.google.com/apis/maps/documentation/geocoding/#ReverseGeocoding

In this case the latitude and longitude of the city, rather than the actual most detailed location, is returned.  

However in some cases certain locations may not have an appropriate city level response, and in this case we cannot return appropriately generalized coordinates.
Status: Confirmed
Nov 30, 2011
#10 bengal...@gmail.com
When I created the ticket I was receiving empty location data for best & city granularity. I just checked and now I am getting location data for granularity=best but the location data is still empty for granularity=city. 

thanks
Nov 30, 2011
#11 ddewa...@gmail.com
FYI, I'm doing all test with granularity=best, and noticed that some locations in the feed can potentially be empty. I've changed my code to deal with those "empty" locations.
Dec 7, 2011
Project Member #12 jli...@google.com
Bengals45:  are you getting only/all empty responses for city level, or a mix, with some empty responses? 
Dec 7, 2011
#13 bengal...@gmail.com
currently:

for granularity=city: 
{"data":{"kind":"latitude#locationFeed"}}
- thats all i am getting without a limitation on results, just 1 empty results

for granularity=best:
- I am getting the correct number of locations with data
Dec 7, 2011
#14 ddewa...@gmail.com
On certain google accounts, using granularity=best I'm experiencing a mix of empty locations and "normal locations". Using the java API client, I can workaround it, but at first glance using the objective-C library it crashes and there's no way to properly check for these empty locations.
Jan 26, 2012
Project Member #15 kjlef...@google.com
The issue of stub locations returning for granularity=city is fixed and should be rolling out over the next couple weeks. Sorry for the long delay in responding to this issue.
Status: Fixed
Sign in to add a comment

Powered by Google Project Hosting