Hi Kim,

This was discussed in another thread in the group:

http://groups.google.com/group/twitter-development-talk/browse_thread/thread/a18c496eb59e8560/8d563ed353e533eb?lnk=gst&q=coordinates#8d563ed353e533eb

You should find the answer your question there.

Best
@themattharris
Developer Advocate, Twitter
http://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

Reply via email to