Not really a duplicate, though they are different sides of the same coin. In this case, if a node has a location attached to it, when the tweet gets sent out, it should optionally have its location on Twitter set as well. In the other issue, it's the other way around (i.e. when pulling from Twitter, if a Tweet has a location, then store it in the Drupal database).
The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.
Comments
Comment #1
sirkitree commentedmarking as duplicate of #644954: Store tweet location
Comment #2
sillygwailoNot really a duplicate, though they are different sides of the same coin. In this case, if a node has a location attached to it, when the tweet gets sent out, it should optionally have its location on Twitter set as well. In the other issue, it's the other way around (i.e. when pulling from Twitter, if a Tweet has a location, then store it in the Drupal database).
Comment #3
sirkitree commentedAh ok, thanks for clarifying! I've clarified the title a little.
Comment #4
jamesJonas commentedTwitter Geotagging API (Nov 2009)
General Announcement: http://blog.twitter.com/2009/11/think-globally-tweet-locally.html
FAQ: http://help.twitter.com/forums/10711/entries/78525
Best Practices: http://apiwiki.twitter.com/Geotagging-API-Best-Practices
Hope this helps
Comment #5
eiland commentedsubscribe
Comment #6
pribeh commentedBump.
Comment #7
mrf commentedThis is a duplicate of #644954: Store tweet location
Comment #8
sillygwailoNo, not a duplicate. It's the reverse of that issue. See #2.
Comment #9
dddave commentedComment #10
damienmckennaComment #11
damienmckenna