Skip to content

Commit 479007e

Browse files
authored
Update Tasks register report
1 parent 8392dac commit 479007e

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

Tasks register report

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
#FIRST WEEK REPORT. From Monday 6th June to Friday 10th June.
22
- Where from
3-
Hypothesis to validate: relation between GDP growth and some social and economical indicators.
3+
Hypothesis to validate: relationship between GDP growth and social and economical indicators.
44
Python language.
55
"Our World in Data" as database.
66
- Objective of the code
7-
Being able to take the data from the database files, perform statistical computations on them and make qualitative conclusions.
8-
- Developed:
7+
Being able to take the data from the database files, perform statistical computations on them and get useful numerical and visual results to make conclusions.
8+
- Development:
99
As we were not experts through Python, we started learning the fundamentals and basic functions throughout some videos: one recorded internally by Capgemini and the other ones mainly from Pluralsight courses, such as Python for Data Analysts, Pandas Fundamentals and Finding Relationships in Data.
1010
At the same time, we began programming the initial functions to open the files and have an overview of the data. Through this inspection of data, we observed that:
11-
- Data was not normalized.
12-
- Depending on the indicator, its corresponding file was ordered in a different way.
11+
- Data was not normalized.
12+
- Depending on the indicator, its corresponding file was ordered in a different way.
1313
Having in mind that these two observations implied a "problem" for us, we realized that the files (CSVs) available in the webpage Our World in Data were being extracted from other sources, mainly FAO. So, we decided to extract directly the data
14-
from there getting the benefits of having data normalized and unified.
15-
We had 68 files that could be related to GDP growth. In each one, the information cointained categories of country, year, units, value and others (consider not relevant for our study).
14+
from there, getting the benefits of having data normalized and unified.
15+
We had 68 files that could be related to GDP growth. In each one, the information cointained categories of country, year, units, value and others (these last ones considered not relevant for our study).
1616
Therefore, what we made was putting all the files in the same table, joining data basing on the conditions of same country and year. So, what we got was a table containing the value of each indicator in each year and region.
1717
It is important to note that indicators´files were not all same size, some registering more ancient historical values or more in depth data by region than others.
1818

0 commit comments

Comments
 (0)