Home » Countries » Ethiopia » Problem with dates in the Ethiopia datasets
|
|
| Re: Problem with dates in the Ethiopia datasets [message #67 is a reply to message #66] |
Wed, 20 February 2013 11:28   |
Bridgette-DHS
Messages: 3190
Registered: February 2013
|
Senior Member |
|
|
All standard date variables in the Ethiopia data file are in the Ethiopian calendar. In general the Ethiopian calendar is 92 months behind the Gregorian (western) calendar. The Ethiopian year runs from September 11 through September 10 and has 12 months of 30 days and 1 months of 5 days. Thus it is only possible to transfer the Ethiopian calendar into the Gregorian calendar when the exact date (day, month and year) is available. Therefore, in the file you will find additional variables indicating the Gregorian dates if they could be established.
Note that all standard variables based on calendar dates and century month codes are given in the Ethiopian Calendar. In general, the Ethiopian year consists of 365 days, divided into 12 months of 30 days and one month of 5 days (6 days in a leap year). Ethiopia's new year falls on September 11and ends the following September 10 according to the Gregorian calendar. From September 11 to December 31, the Ethiopian year runs seven years behind the Gregorian year, thereafter, the difference is eight years. Since the exact day is not available for most dates, it is not possible to convert the dates exactly, but only approximate it to the month. There is a difference of 92 months between the two date systems. The 13th month of the Ethiopian calendar falls in September. Thus, to keep the higher precision available in the Ethiopian calendar, these were used for all standard recode variables where applicable. In general, dates in the Gregorian calendar are provided as country specific variables. However, the calendar is transferred to the Gregorian calendar.
To explain somewhat further, the number of months in the CMC variables (even for Ethiopian dates) are computed as follows: each year has 12 months, but when the event was in the 13th month then 13 is added for the number of months. Thus e.g. a person was born in the 13th month of 1960 in the Ethiopian calendar, then the CMC is 60 * 12 + 13. Thus the 5 days in the 13th month really go to the following year when you recomputed the CMC back to years (with 12 months). But this will cause little bias. So just use the CMC as you would for other surveys (intervals should not be divided by 13, but by 12). However, know that on average the Ethiopian calendar lags 92 months behind our Gregorian system.
The Ethiopian calendar was kept as the standard variables, since not all dates (e.g. vaccination dates) could be transferred.
Here is a link that you can use to convert Ethiopian dates:
http://www.funaba.org/en/calendar-conversion.cgi
Attached is a little Stata script: "ETcalconvert", that you may find useful (written by DHS Data User: Keith Kranker).
I hope this helps.
Bridgette-DHS
[Updated on: Mon, 18 March 2013 09:14] Report message to a moderator |
|
|
|
| Re: Problem with dates in the Ethiopia datasets [message #8980 is a reply to message #67] |
Fri, 22 January 2016 12:02 |
lillo?S
Messages: 26
Registered: December 2015
|
Member |
|
|
Hello,
From what I can see in the DHS 2005 there are country-specific variables that define the dates in the Gregorian calendar, the same does not hold for DHS 2011.
In the 'Individual Recode Documentation' (p.8) I find this:
"Before the production of any indicators with these data the Ethiopian calendar was converted to the Gregorian calendar but conserving the Ethiopian year; however, the Ethiopian first month is considered in the logic as January, the 2nd as February, etc. For dates including year, month and day the conversion is precise since both calendars have 365 or 366 days; for dates including only year and month, the 13th month was included in December."
I understand that the months have already been converted, whereas the years have not.
When I go to the 'CSPRO Process Summary' file and look at v006, the months of interview range from 4 through 9. According what's written in the IRD word file, I should interpret this as 4=April and 9=September because the conversion is supposed to have been already done. However, in the website at http://dhsprogram.com/what-we-do/survey/survey-display-359.c fm I see that: Fieldwork: December 2010 - May 2011. These months do not match the ones above, whereas they could coincide if the conversion had not been done.
My questions are:
1- has the conversion been done or not?
2- how are the CMC variables given?
Thanking you in advance.
|
|
|
|
| Re: Problem with dates in the Ethiopia datasets [message #8981 is a reply to message #67] |
Fri, 22 January 2016 12:04 |
lillo?S
Messages: 26
Registered: December 2015
|
Member |
|
|
Hello,
From what I can see in the DHS 2005 there are country-specific variables that define the dates in the Gregorian calendar, the same does not hold for DHS 2011.
In the 'Individual Recode Documentation' (p.8) I find this:
"Before the production of any indicators with these data the Ethiopian calendar was converted to the Gregorian calendar but conserving the Ethiopian year; however, the Ethiopian first month is considered in the logic as January, the 2nd as February, etc. For dates including year, month and day the conversion is precise since both calendars have 365 or 366 days; for dates including only year and month, the 13th month was included in December."
I understand that the months have already been converted, whereas the years have not.
When I go to the 'CSPRO Process Summary' file and look at v006, the months of interview range from 4 through 9. According what's written in the IRD word file, I should interpret this as 4=April and 9=September because the conversion is supposed to have already been done. However, in the website at http://dhsprogram.com/what-we-do/survey/survey-display-359.c fm I see that: Fieldwork: December 2010 - May 2011. These months do not match the ones above, whereas they could coincide if the conversion had not been done.
My questions are:
1- has the conversion been done or not?
2- how are the CMC variables given?
Thanking you in advance.
|
|
|
|
| Re: Problem with dates in the Ethiopia datasets [message #9035 is a reply to message #8981] |
Fri, 29 January 2016 12:56 |
Bridgette-DHS
Messages: 3190
Registered: February 2013
|
Senior Member |
|
|
Following is a response from Senior DHS Stata Specialist, Tom Pullum:
In the 2011 survey, all dates are in the Ethiopian calendar rather than the Gregorian calendar. The cmc is also calculated consistently with the Ethiopian calendar. For example, you can confirm that v008=12(v007 1900) + v006. This consistency is found in all surveys, whether using the Gregorian, Ethiopian, or Nepalese calendars.
To convert to the Gregorian calendar, add 92 to the Ethiopian cmc. Then get the Ethiopian year and month from the Ethiopian cmc as follows, illustrated again for v006, v007, and v008:
gen v007=int((v008-1)/12)
gen v006=v008-12*v007
replace v007=v007+1900
|
|
|
|
| Re: Problem with dates in the Ethiopia datasets [message #9179 is a reply to message #9035] |
Fri, 19 February 2016 10:12 |
st89
Messages: 1
Registered: February 2016
|
Member |
|
|
A follow-up question about the dates in the 2011 survey (specifically the children's recode): variable h9d (day of month of measles vaccination, if known) takes on values from 1 to 31. However, my understanding is that all of the dates are in the Ethiopian calendar, which should have 12 months of 30 days + one month of 5 or 6 days. I'm unclear on how to use h9d values of 31 since it is not in the Ethiopian calendar, and am thus not able to convert the three variables h9y-h9m-h9d to Gregorian dates.
Thanks for your help!
|
|
|
|
| Re: Problem with dates in the Ethiopia datasets [message #9183 is a reply to message #9179] |
Fri, 19 February 2016 12:02 |
Bridgette-DHS
Messages: 3190
Registered: February 2013
|
Senior Member |
|
|
Another response from Tom Pullum:
I will start by repeating an answer I gave on the forum on January 29, but this time with a correction of a typo in the January 29, version, where in the second paragraph I said "Ethiopian" but meant "Gregorian"--sorry about that.
In the 2011 survey, all dates are in the Ethiopian calendar rather than the Gregorian calendar. The cmc is also calculated consistently with the Ethiopian calendar. For example, you can confirm that v008=12(v007 1900) + v006. This consistency is found in all surveys, whether using the Gregorian, Ethiopian, or Nepalese calendars.
To convert to the Gregorian calendar, add 92 to the Ethiopian cmc. Then get the Gregorian year and month from the Gregorian cmc as follows, illustrated again for v006, v007, and v008. I will use vg006, etc, to indicate that these are Gregorian versions of the original Ethiopian codes.
gen vg008=v008+92
gen vg007=int((vg008-1)/12)
gen vg006=vg008-12*v007
replace vg007=vg007+1900
Now to get to your question. Although you may be right that there is a 5-day month in the Ethiopian calendar, I think it must be absorbed in one or both of the adjacent months. If you go to the BR file and enter "tab h9m" or "tab b2", etc., you will see 12 numbered months, all with about the same number of cases. I recommend that you simply do the month and year conversion described above, but keep the day as h9d. I would look at how the days 29, 30, and 31 are converted to a day with "day=mdy(h9m,h9d,h9y)". You will find that certain combinations of year and month and day (even year, because of Leap Year) are rejected, and will produce "day=." because the specified Gregorian month has only 30 days, or in the case of February has only 28 days, except in a Leap Year, when it has 29! (Ten days from now we will have a Feb. 29!) Then I personally would recode h9d for all of the rejected values to 28, but you could go to more trouble and successively convert to 30, then to 29, then to 28, until all combinations of year, month, and day are accepted. The kind of error that will be incurred with this sort of adjustment will be trivial, especially compared with other reporting errors.
|
|
|
|
|
|
|
|
| Re: Problem with dates in the Ethiopia datasets [message #13747 is a reply to message #13746] |
Mon, 18 December 2017 13:21 |
kcaglaya@tulane.edu
Messages: 7
Registered: November 2017
|
Member |
|
|
Dear Ladys,
Thank you so much for your response. It helps a lot.
There is one more thing that I would like to be sure of, since the results of our analysis heavily depend on the day of birth.
1) b17 is identical with hw16 in 2016 survey. We are using hw16 since it is present in the data across all survey years. We pool the data from all survey years in our estimations. Height and weight are among our variables of interest, so we are using observations with height and weight variables available anyway.
2) The information you provided about 2016 survey in terms of birth day and birth month is very helpful and answers our question. However, we suspect that this might also be the case for 2011 survey; i.e. hw16 and b1 are also reported in Gregorian Calendar in 2011 survey. I base this on the fact that in 2011 survey data; hw16 varies between 1-31, the birth months with hw16=31 are the Gregorian months with 31 days and also birth months with hw16=30 or hw16=31 lack February as we would expect from Gregorian Calendar. So, I would greatly appreciate if you can confirm whether the following table regarding the way these dates are reported is correct or not. I also attach the table as a separate file.
B17 (Day of Birth) HW16 (Day of Birth) B1 (Month of Birth) B2 (Year of Birth)
2000 Survey - Ethiopian Ethiopian Ethiopian
2005 Survey - Ethiopian Ethiopian Ethiopian
2011 Survey - Gregorian Gregorian Ethiopian
2016 Survey Gregorian Gregorian Gregorian Ethiopian
Once again, thank you for your time and help.
Regards,
Koray
[Updated on: Mon, 18 December 2017 13:23] Report message to a moderator |
|
|
|
|
|
| Re: Problem with dates in the Ethiopia datasets [message #13754 is a reply to message #13748] |
Tue, 19 December 2017 14:31 |
Bridgette-DHS
Messages: 3190
Registered: February 2013
|
Senior Member |
|
|
Following is a response from Senior DHS Data Processing Manager, Albert Themme:
I checked the imputation and recode programs for 2000 and 2005. Both handled the construction of HW16, B1 and B2 in the same way.
As the recode documentation states all dates are in the Ethiopian calendar.
Thus in 2000 HW16 was derived from HC16, which is a copy of QHC29D as recorded on the questionnaire.
Similarly, in 2005 HW16 was derived from HC16, which is a copy of QC53D again as recorded on the questionnaire.
B1 and B2 are derived from B3 (CMC data of birth of child) with is a copy of Q215C. The computation of Q215C had one difference from our standard procedure. The Ethiopian month and year of birth were used, but when the month of birth was recorded as 13, then 13 months were added to the last year.
E.g. the child was born 13 1960, then the CMC is computed as 60 * 12 + 13.
When the year and month of birth are then returned from this CMC, then the 13th month is really added to the 1st month of the new year.
Let me know if this is not clear.
|
|
|
|
| Re: Problem with dates in the Ethiopia datasets [message #13755 is a reply to message #13754] |
Tue, 19 December 2017 14:50 |
kcaglaya@tulane.edu
Messages: 7
Registered: November 2017
|
Member |
|
|
Dear Bridgette, Ladys and Albert,
Thank you so much for your time and help. We greatly appreciate your kind effort.
We are very close to clarify this issue completely. I just need your help and expertise on one last thing. (at least for this project :))
Yesterday, Ladys confirmed that a child's day of birth (b17 or hw16) and month of birth (b1) are reported in Gregorian Calendar while the year of birth (b2) is reported in Ethiopian Calendar in 2016 survey data.
Today, Albert confirmed that a child's day (hw16), month (b1) and year (b2) of birth are all reported in the same way and in Ethiopian Calendar in 2000 and 2005 survey data.
If somebody can confirm the way these variables (i.e. hw16, b1, b2) are reported in 2011 survey data, we would be able to solve the problem completely.
I think, in 2011 these variables are reported as they are reported in 2016 (i.e. hw16 and b1 in Gregorian Calendar and b2 in Ethiopian Calendar) because of the reasons that I mentioned in previous posts. However, I would really appreciate a confirmation from you on this matter.
Once again, thank you very much.
Regards,
Koray
|
|
|
|
| Re: Problem with dates in the Ethiopia datasets [message #13757 is a reply to message #13755] |
Tue, 19 December 2017 16:31 |
Bridgette-DHS
Messages: 3190
Registered: February 2013
|
Senior Member |
|
|
Another response from Ladys Ortiz:
As recommended in my previous email, you should read the recode documentation that we usually post within the zipped dataset. The following is excerpted from the documentation mentioned earlier, and hopefully, this answers your question:
Quote:All standard variables are based on calendar dates and century month codes are given in the Ethiopian Calendar. The Ethiopian year consists of 365 days, divided into 12 months of 30 days and one month of 5 days (6 days in a leap year). Ethiopia's new year falls on September 11and ends the following September 10 according to the Gregorian calendar. Before the production of any indicators with these data the Ethiopian calendar was converted to the Gregorian calendar but conserving the Ethiopian year; however, the Ethiopian first month is considered in the logic as January, the 2nd as February, etc. For dates including year, month and day the conversion is precise since both calendars have 365 or 366 days; for dates including only year and month, the 13th month was included in December.
Thanks,
Ladys Ortiz
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Problem with dates in the Ethiopia datasets [message #16608 is a reply to message #16607] |
Wed, 06 February 2019 09:01 |
Ogriv
Messages: 16
Registered: March 2015
|
Member |
|
|
Hi there
I have now looked at a cross-tab of the converted birth month and birth year.
It looks like this:
child_birt | child_birthyear
hmonth | 2010 2011 2012 | Total
-----------+---------------------------------+----------
1 | 0 0 265 | 1,156
2 | 0 0 201 | 953
3 | 0 0 231 | 987
4 | 0 0 235 | 955
5 | 0 5 243 | 1,047
6 | 0 28 183 | 941
7 | 0 50 195 | 897
8 | 0 90 199 | 902
9 | 108 130 132 | 751
10 | 148 135 133 | 740
11 | 127 122 145 | 695
12 | 114 116 101 | 617
-----------+---------------------------------+----------
Total | 497 676 2,263 | 10,641
child_birt | child_birthyear
hmonth | 2013 2014 2015 | Total
-----------+---------------------------------+----------
1 | 247 219 209 | 1,156
2 | 168 192 184 | 953
3 | 200 190 181 | 987
4 | 207 172 169 | 955
5 | 218 177 209 | 1,047
6 | 186 231 179 | 941
7 | 167 170 206 | 897
8 | 180 184 182 | 902
9 | 139 179 56 | 751
10 | 145 178 1 | 740
11 | 121 180 0 | 695
12 | 120 166 0 | 617
-----------+---------------------------------+----------
Total | 2,098 2,238 1,576 | 10,641
| child_birt
child_birt | hyear
hmonth | 2016 | Total
-----------+-----------+----------
1 | 216 | 1,156
2 | 208 | 953
3 | 185 | 987
4 | 172 | 955
5 | 195 | 1,047
6 | 134 | 941
7 | 109 | 897
8 | 67 | 902
9 | 7 | 751
10 | 0 | 740
11 | 0 | 695
12 | 0 | 617
-----------+-----------+----------
Total | 1,293 | 10,641
From the EDHS 2016 report, interview data collection took place from January-June 2016.
If this is the case, then some of these birth months must be incorrect for 2016.
Also it looks like full data are only available for 2012-2014 from the table above.
Sandra
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Problem with dates in the Ethiopia datasets [message #17632 is a reply to message #66] |
Wed, 01 May 2019 01:56 |
Mark
Messages: 11
Registered: May 2017
Location: Ethiopia
|
Member |
|
|
Dear Sir/Madam,
I am using the 2016 EDHS IR dataset to calculate contraceptive method used prior to the most recent birth.
I am actually interested to calculate it for women who are eligible for birth interval variable (I dropped non-eligible respondents (keep if b11_01!=.)).
Even though I used the command (presented bellow) that should be used for calendar data using Stata software (after reading the 'DHS Contraceptive Calendar Tutorial), I got the highest number of missing data (30.31%) which is not common in DHS data. Is there anything I may miss in my program? May you check my program code, and provide me the right program code for this particular case the 2016 Ethiopian DHS please.
* Step 1.1
* length of full calendar string including leading blanks (80)
* actual length used according to v019 will be less
egen vcal_len = max(strlen(vcal_1))
* most calendars are 80 in length, but those without method use may be short, so use the max
label variable vcal_len "Length of calendar"
* Step 1.2
* position of last birth or terminated pregnancy in calendar
gen lb = strpos(vcal_1,"B")
gen lp = strpos(vcal_1,"T")
* update lp with position of last birth if there was no terminated pregnancy,
* or if the last birth was more recent than last terminated pregnancy
replace lp = lb if lp == 0 | (lb > 0 & lb < lp)
* e.g. if calendar is as below ("_" used to replace blank for display here):
* ____00000BPPPPPPPP000000555555500000TPP00000000000000BPPPPPP PP00000000
* ^
* lp would be 20
label variable lp "Position of last birth or terminated pregnancy in calendar"
label def lp 0 "No birth or terminated pregnancy in calendar"
label value lp lp
* get the type of birth or terminated pregnancy
* lp_type will be set to 1 if lp refers to a birth,
* and 2 if lp refers to a terminated pregnancy using the position in "BT" for the resulting code
gen lp_type = strpos("BT",substr(vcal_1,lp,1)) if lp > 0
label variable lp_type "Birth or terminated pregnancy in calendar"
label def lp_type 1 "Birth" 2 "Terminated pregnancy"
label value lp_type lp_type
list vcal_1 lp lp_type in 1/5
tab lp lp_type, m
* Step 1.3
* if there is a birth or terminated pregnancy in the calendar then calculate CMC
* of date of last birth or pregnancy by adding length of calendar to start CMC
* less the position of the birth or pregnancy
* calendar starts in CMC given in v017
* lp > 0 means there was a birth or terminated pregnancy in the calendar
gen cmc_lp = v017 + vcal_len - lp if lp > 0
label variable cmc_lp "Century month code of last pregnancy"
* e.g. if calendar is as below and cmc of beginning of calendar (V017) = 1321:
* ____00000BPPPPPPPP000000555555500000TPP00000000000000BPPPPPP PP00000000
* cmc_lp would be 1381, calculation as follows:
* 1321 + 80 - 20 (80 is the vcal_len, and 20 is the position of lp)
list v017 lp vcal_len cmc_lp in 1/5
* check the variables created.
tab lp
tab cmc_lp
* list cases where cmc_lp and b3_01 don't agree if the last pregnancy was a birth
list cmc_lp b3_01 if lp > 0 & lp == lb & cmc_lp != b3_01
* there shouldn't be any cases listed.
* Step 1.4
* get the duration of pregnancy and the position of the month prior to the pregnancy
* start from the position after the birth in the calendar string by creating a substring
* indexnot searches the substring for the first position that is not a "P" (pregnancy)
* piece is the piece of the calendar before the birth ("B") or termination ("T") code
gen piece = substr(vcal_1, lp+1, vcal_len-lp)
* find the length of the pregnancy
gen dur_preg = indexnot(piece, "P") if lp > 0
* dur_preg will be 0 if pregnant at the start of the calendar
label variable dur_preg "Duration of pregnancy"
* e.g. if calendar is as below:
* ____00000BPPPPPPPP000000555555500000TPP00000000000000BPPPPPP PP00000000
* |12345678^
* dur_preg would be 9 for the last pregnancy (1 B plus 8 Ps)
* if we find something other than a "P" then that is the month before the pregnancy
* if it returns 0 then the pregnancy is underway in the first month of the calendar
* now get the position in the calendar to reflect the full calendar
* not just the piece before the birth, by adding lp
* _bp means 'before pregnancy'. pos_bp means position before pregnancy
gen pos_bp = dur_preg + lp if dur_preg > 0
label variable pos_bp "Position before pregnancy"
label def pos_bp 0 "Pregnant in first month of calendar"
label val pos_bp pos_bp
* e.g. if calendar is as below:
* ____00000BPPPPPPPP000000555555500000TPP00000000000000BPPPPPP PP00000000
* ^
* pos_bp would be 29
list vcal_1 lp dur_preg pos_bp in 1/5
tab dur_preg lp_type, m
* Step 1.5
* find the last code that is not 0 before the pregnancy (using indexnot),
* searching in a substring of the calendar from the month before pregnancy and earlier,
* but not more than 5 years back
* lnz means 'last non-zero before the pregnancy'
gen lnz = indexnot(substr(vcal_1, pos_bp, vcal_len - pos_bp + 1),"0") ///
if inrange(pos_bp, 1, vcal_len)
* get the actual position in the calendar of the last non-zero before the last birth
gen pos_lnz = pos_bp + lnz - 1 if inrange(lnz, 1, vcal_len)
* if last non-zero is more than 5 years before interview, set position to 0
replace pos_lnz = 0 if lnz == 0 | (pos_lnz != . & pos_lnz > v018+59)
label variable pos_lnz "Position in calendar of last non-zero before pregnancy"
label def pos_lnz 0 "No non-zero preceding the pregnancy in the last 5 years"
label val pos_lnz pos_lnz
* list a few cases to check
list vcal_1 lp pos_bp pos_lnz in 1/5
* Step 1.6
* check if the respondent is using a method before the pregnancy but in the last 5 years
gen code_lnz = substr(vcal_1, pos_lnz, 1) if inrange(pos_lnz, v018, v018+92)
replace code_lnz = "0" if pos_lnz == 0
* if the code is NOT(!) a zero ("0"), a "B", "P" or "T" then the respondent was using a method
gen used_bp = !inlist(code_lnz, "0","B","P","T") if code_lnz != ""
label variable code_lnz "Last non-zero code before pregnancy"
label variable used_bp "Using a method before the last pregnancy"
label def used_bp 0 "No" 1 "Yes"
label val used_bp used_bp
* list a few cases to check
list vcal_1 lp pos_bp pos_lnz code_lnz used_bp in 1/5
* Step 1.7
* last method used before pregnancy, but may have been followed by a period of non-use
* converting the string variable to numeric, although it isn't really necessary for most analyses
* set up a list of codes used in the calendar, with each position matching the coding in V312
* use a tilde (~) to mark gaps in the coding that are not used for this survey
* e.g. Emergency contraception and Standard days method do not exist in this calendar
* note that some of the codes are survey specific so this list may need adjusting
scalar methodlist = "123456789WNALCF~M~"
gen method_bp = strpos(methodlist,code_lnz) if code_lnz != ""
* convert the missing code to 99
replace method_bp = 99 if code_lnz == "?"
* now check if there are any method codes that were not converted, and change these to -1
replace method_bp = -1 if method_bp == 0 & used_bp == 1
* alternatively,
* use the do file below to set up survey specific coding using scalar methodlist and label method
* and recode the method and/or reasons for discontinuation
* include the path to the do file if needed
*run "Calendar recoding.do" code_lnz method_bp
* and skip the value labeling in step 2.8 as the do file above includes the value labeling
* if no method was used, set method_bp to 0
replace method_bp = 0 if used_bp == 0
* Step 1.8
* label the method variable and codes
label variable method_bp "Method used before the last pregnancy (numeric)"
label def method ///
0 "No method used" ///
1 "Pill" ///
2 "IUD" ///
3 "Injectable" ///
4 "Diaphragm" ///
5 "Condom" ///
6 "Female sterilization" ///
7 "Male sterilization" ///
8 "Periodic abstinence/Rhythm" ///
9 "Withdrawal" ///
10 "Other traditional method" ///
11 "Norplant" ///
12 "Abstinence" ///
13 "Lactational amenorrhea method" ///
14 "Female condom" ///
15 "Foam and Jelly" ///
16 "Emergency contraception" ///
17 "Other modern method" ///
18 "Standard days method" ///
99 "Missing" ///
-1 "***Unknown code not recoded***"
label val method_bp method
tab method_bp
|
|
|
|
|
|
| Re: Problem with dates in the Ethiopia datasets [message #19105 is a reply to message #17676] |
Tue, 21 April 2020 16:19 |
kbhan89
Messages: 1
Registered: April 2020
|
Member |
|
|
Hi,
Sorry to bring up this issue again.
I'm currently working on the 2016 Ethiopia DHS data. I have deliberately read the discussions seen above and the recode documentation.
However, I still have some issues making me confused. I would be grateful if you could help me clarify the following points.
1) I wonder if v009 (respondent's month of birth) has already been converted to the Gregorian calendar or not. If I understood the recode and documentation the discussions above correctly, v009 should be the one based on the Ethiopian calendar since the information on a respondent's day of birth was not collected and then precise conversion cannot be done. If I compute v011 (date of birth - cmc) manually using v009 (respondent's month of birth) and v010 (respondent's year of birth - based on the Ethiopian calendar), I can get the same values of v011 in the dataset, leading me to guess that v009 is also from the Ethiopian calendar.
2) Thanks to the clear explanations done above, I have understood that b1(month of birth) has already been converted to the Gregorian calendar while b2(year of birth) has not. Then, could you let me know how b3 (date of birth - cmc) was computed? If I do the same computation as I did for v011 (i.e. b3=(b2-1900)*12+b1), I get the same values of b3 in the dataset. Does it mean that these cmc values are coming from the months by the Gregorian calendar and the years by the Ethiopian one? I need to convert b2 to the Gregorian one by using b3, but the values of b3 in the data file are a little confusing to me.
I might be missing something important. Please correct me if I have made wrong points.
Thank you very much for your help in advance.
[Updated on: Wed, 29 April 2020 13:18] Report message to a moderator |
|
|
|
| Re: Problem with dates in the Ethiopia datasets [message #19281 is a reply to message #19105] |
Wed, 20 May 2020 10:16 |
Trevor-DHS
Messages: 802
Registered: January 2013
|
Senior Member |
|
|
The dates in the Ethiopia surveys have not been converted to the Gregorian calendar but they have been "squeezed" from a 13 month calendar down to fit a 12 month calendar (comparable to other countries). In this "squeezing" process the years are unchanged and only the month and day are affected. For dates that only have month, but not day, the 13th month is recoded to the 12th month. For dates with month and day, the dates are squeezed by moving the dates back into 12 months, with some months having 31 days and some 30 days, similar to Gregorian months.
The century month codes are based on these squeezed Ethiopian dates.
For Gregorian dates, the simplest thing to do is to add 92 months to the CMC. This won't be perfect as it doesn't take into account the day of birth or interview, but you could adjust for that by subtracting 1 month from the CMC if the day was less than 12.
See the Guide to DHS Statistics and search in the PDF for Ethiopia for more information.
[Updated on: Wed, 20 May 2020 10:26] Report message to a moderator |
|
|
|
|
|
|
|
Goto Forum:
Current Time: Fri Nov 8 21:02:54 Coordinated Universal Time 2024
|
The DHS Program User Forum
Members
Search
Help
Register
Login
Home
