Looking beyond the documentation?
Check out our help articles
posted on 03 March 2015 by Jim Moffitt
Storing Metadata Arrays Twitter data is dynamic in nature, and includes several types of metadata that are in arrays of variable length. For example, tweets can consist of multiple hashtags, urls, user mentions, and photographs. For example the tweet below contains four hashtags: #Boulder, #boulderflood, #cuboulder and #cowx Flash Flood Warning for #Boulder extended to 4:15AM. #boulderflood #cuboulder #cowx— CU-Boulder Police (@CUBoulderPolice) September 12, 2013 JSON readily supports arrays of data with simple notation, while relational database schemas are static in nature. The concept of having a database field ‘grow’ to store dynamic array lengths of data does not exist... keep reading
Storing Twitter Data in Relational Databases - Part 1
An introduction to Storing Twitter Data in Relational Databases
25 February 2015
Visualizing Twitter Geo Data
Describes the processes involved in plotting geotagged Tweets on a map built in d3, useful in web based visualization.
03 December 2014
Consuming, Parsing, and Processing Tweets with Python
Explores a Python script that performs a simple but complete parsing of JSON-formatted social media data, such as would be streamed or downloaded from a Gnip API endpoint.
27 October 2014
Building your app?
Get going quickly with our code examples
Connect to the PowerTrack and Firehose streams.
Add, delete, and list rules on the PowerTrack Rules API.
Create and manage Historical PowerTrack jobs.
Send Search and Counts requests to the Search API.
Request Tweets via the Rehydration API.