Statuses/filter.json NEVER returns coordinates nor place

[farolfo91]

Hey there !
I’m working with the /statuses API of the v1.1 API, but I’m never getting the coordinates field populated, and the place field is only populated in a 1% amount of the total streamed tweets.
I’m using /statuses/filter.json and /statuses/sample.json, but still never get geolocated data.

What would you recommend for me if I need to get tweets in real time based on locations? I’d like to get the coordinates and place fields in a non-null format if possible.

Thanks !

[andypiper]

That’s an accurate expectation. Only about 1-2% of users choose to explicitly add location data to their Tweets, and the statuses/filter endpoint is capped to 1% of the firehose, so you’re looking at a very small number of Tweets that might match your filter and receive those fields.

You can read more about when and why these fields are populated here.

For higher fidelity on volume, you’d need to look at enterprise PowerTrack, but even then, the limitation on the number of Tweets that carry location information remains.

[system]

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.