Hi Kim, Thanks for following up - I did think you were referring to the place coordinates not the status coordinates.
In the status object there is a geo block and a coordinates block. Both contain the same information but one is in human readable form (the geo block -- lat,lon) whilst the other is in geojson form (the coordinates block -- lon, lat). The reason for both fields is historical and due to us wanting to keep backwards compatibility. When developing you should use the coordinates block as this is the geojson friendly format. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Tue, Oct 26, 2010 at 12:36 PM, Kim <kimdhamil...@gmail.com> wrote: > Hi Matt, > I'm probably missing something, but that thread seems to be describing > the difference between place coordinates, as opposed to the > coordinates field that's at the status level (same level as geo, as > shown in my example above). Those coordinates appear to be redundant > with geo. > > Thanks, > Kim > > On Oct 26, 12:07 pm, Matt Harris <thematthar...@twitter.com> wrote: > > Hi Kim, > > > > This was discussed in another thread in the group: > > > > http://groups.google.com/group/twitter-development-talk/browse_thread... > > > > You should find the answer your question there. > > > > Best > > @themattharris > > Developer Advocate, Twitterhttp://twitter.com/themattharris > > > > > > > > > > > > > > > > On Tue, Oct 26, 2010 at 10:34 AM, Kim <kimdhamil...@gmail.com> wrote: > > > Hi, > > > Apologies if this has been answered before, but I couldn't find the > > > answer anywhere. > > > > > I'm using the Streaming API and, based on the data I've seen so far, > > > the coordinates and geo fields appear to contain duplicate info. If a > > > status contains 1 of these fields, then it contains both, and the only > > > difference is the order of lat and lon. I've included an example > > > below. > > > > > Is this correct? Is one of these fields legacy, and if so, which one? > > > > > { > > > ... > > > "coordinates": { > > > "type": "Point", > > > "coordinates": [ > > > -74.147244, > > > 40.638104 > > > ] > > > }, > > > ... > > > "geo": { > > > "type": "Point", > > > "coordinates": [ > > > 40.638104, > > > -74.147244 > > > ] > > > }, > > > } > > > > > Thanks! > > > Kim > > > > > -- > > > Twitter developer documentation and resources: > http://dev.twitter.com/doc > > > API updates via Twitter:http://twitter.com/twitterapi > > > Issues/Enhancements Tracker: > > >http://code.google.com/p/twitter-api/issues/list > > > Change your membership to this group: > > >http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
