The search API is different. The documentation for streaming (https://dev.twitter.com/streaming/overview/request-parameters#locations) states: "The streaming API uses the following heuristic to determine whether a given Tweet falls within a bounding box:
If the coordinates field is populated, the values there will be tested against the bounding box."
That’s not the behavior I’m seeing which is mostly wrong or null coordinates. Here are a few examples below with the same coordinates as above in my “locations” request parameters :
id_str : coordinates
878760228015058944 : null
878760236416479234 : {
coordinates = (
"-123.01178221",
“37.69956642"”