Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.1.0
-
Component/s: None
-
Labels:None
Description
There will be a case which a status contains an empty <geo/> element even the use enabled geo feature.
http://groups.google.com/group/twitter-api-announce/browse_thread/thread/dfbd0b3a9d2aba3?hl=en
Status class should implement isGeoIncluded() method to test whether the tweet contains geo location or not.
http://groups.google.com/group/twitter4j/browse_thread/thread/8958a27dec303660
http://groups.google.com/group/twitter-api-announce/browse_thread/thread/dfbd0b3a9d2aba3?hl=en
Status class should implement isGeoIncluded() method to test whether the tweet contains geo location or not.
http://groups.google.com/group/twitter4j/browse_thread/thread/8958a27dec303660
> How about using a GeoLocation instance containing longitude and
> latitude? getGeoLocation could then return null if it's not available.
>
> Joern