You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Single byte is enough. Data is available as numeric values initially, before storage. It’s a limited subset like [0-255] so same strings repeatedly.
You said 100x100? I'd just store that as 10kB binary blob in a database table. (But let's ask someone who really knows this stuff. @MarkusWinand: Is this a good idea? I guess his first question will be which database you are using.. :)
MySQL. Awaiting bashing from hell now, but that’s what I got here in the environment I’m using - alternatives are only: SQLite, MongoDB, Redis - all require at least one person month more.
MySQL isn't that bad. I'd go for blobs or vectors/arrays of (var)char.
Oh, so it's at most 100 MB data? That's not too wild.. If you know you don't need to scale beyond that then you can even keep the entire DB in memory. What language are you using? Even a 100x100x10000 numpy array would possibly do the trick..https://twitter.com/JuleRiede/status/1042812032859480064 …
Not using python here.
What it really depends on is what is meant by "efficient"? Is it about storage space? Is it about getting querying the whole matrix at once? Is it about getting single values at once? Is it about changing single/all values? Is it about finding matrices that have some property?
Storage space, but first priority access (rw). Individual access to matrices (one matrix per user at a given time only). Search within matrix space is not critical at all (not enabled on user level).
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
