Do you work with historical Indian data and Stata?
Tracking Indian administrative regions over time is tedious.
Check out indiabridge: dynamic, fuzzy matching agnostic to name and boundary changes over time.
https://t.co/iiPJfzuEVp
(A long due update to v1)
@stelifanie@Stata a workaround I use is making a tempfile at the beginning and moving it around to save 'checkpoints' after blocks of commands. Saves a lot of runtime!
@kiranlimaye My guess is that a centralised platform like Dream11 is in the government's interest for tax revenue and transparency
But if the intention is purely to curb individual gambling then this is irrelevant
@sanjana_m5 if the objective is to demonstrate understanding, A is very precise on its argument.
B communicates that infinity is approached as a limit (which is the more important step in evaluating this integral).
C is ambiguous about this idea so it can be seen as 'wrong' or partial info
On the to-do list:
- allow processing multiple years at once (right now, the year is a constant numeric input)
- track changes beyond 2011.
This crosswalk tracks all changes until 640 districts in 2011 - there are currently 748 districts in India.
#EconTwitter - I have been working on building datasets using the Indian Census from 1951-now.
To make merging and tracking units easy, I wrote a few scripts to assign district identifiers. I'm sharing these as Stata ado programs with india-bridge.
https://t.co/xIst7CHOBF
A full crosswalk of district changes year-on-year is available as a Stata dta and Excel spreadsheet.
Preparing these scripts was a big timesink, but it has saved me countless hours since.
I hope this makes working with district-level data in India easier!