According to
https://support.twitter.com/articles/78525# - it looks like Twitter is handling geolocation information differently.
Twitter for iOS version 6.26 or later, and on Twitter for Android version 5.55 or later -- looks like it has explicit shares for "precise" geolocation vs. general geolocation.
How does that data fit into the
140dev.com database? It seems like I'm not getting anything in most tweets (even those I've tested with geolocation turned on).
Is there a change to the system that needs to happen?