2023: Week 14 - World Trade Data

Created by: Alfred Chan

We've got a guest contributor this week! Alfred is part of DS28 at the Data School.

In this week's Preppin’ Data Challenge you are required to examine and compile a report on all countries’ trading data. The report should contain information of the import and export data. 

Another request is to make sure the import and export can be visualised on a map so some additional spatial data is needed.

We are going to use a public data from the World Integrated Trade Solutions to examine the trade data across countries.

Link to the website: https://wits.worldbank.org/datadownload.aspx?lang=en  

Inputs

  1. World Trade Data, one csv file for each country 

  2. Countries Geographic Data (original data from here)

Requirements

  • Input the world trade data, pull in all countries’ files
    • Make sure Prep reads the first line of the file as header
  • Update the data role of the Reporter and Partner fields from string to Country/ Region (some countries will not be recognised, but we will keep them in)
  • Get the country code for each country from the file path
    • E.g AFG for Afghanistan 
  • Keep Import and Export data only
    • Remove “World”, “European Union”, “"Occ.Pal.Terr" and "Other Asia, nes" in the Reporter column as they are not countries
    • Remove “…”, “Special Category” and “World” in the Partner column
  • Remove file path
  • Make sure all years are in the same column
    • Name it “Year” and change data type to date 
  • Change the pivoted value to number (decimal) and pivot them up as column
  • Input the Countries geo data
  • Remove unnecessary columns
  • Get the latitude and longitude from the “geo_point_2d” column 
    • First coordinate as Latitude, second as Longitude
    • Make sure the data type is number(decimal)
  • Join the countries geo data to the trade data
    • Make sure no record from the trade data is lost from the join
    • Remove countries name and code fields from the geo data
  • After getting the latitude and longitude for the reporting country, we now need to get the same for partner countries as well
    • Get the country code for the partner country and join with geo data again to get the coordinates for the partner countries
    • Add suffix “_Partner” to the latitude and longitude of partners
  • Output the data

Output

  • 15 fields
    • Year
    • Reporter
    • Country Code
    • Latitude
    • Longitude
    • Partner 
    • Country Code_Partner
    • Latitude_Partner
    • Longitude_Partner
    • Product Categories
    • Indicator Type
    • Trade (US$ Mil)-Top 5 Export Partner
    • Trade (US$ Mil)-Top 5 Import Partner
    • Partner share(%)-Top 5 Export Partner
    • Partner share(%)-Top 5 Import Partner
  • 43,898 rows (43,899 including headers)
You can download all the output from here

After you finish the challenge make sure to fill in the participation tracker, then share your solution on Twitter using #PreppinData and tagging @Datajedininja, @JennyMartinDS14 & @TomProwse1

You can also post your solution on the Tableau Forum where we have a Preppin' Data community page. Post your solutions and ask questions if you need any help! 

Popular posts from this blog

2024: Week 1 - Prep Air's Flow Card

Image
Created by: Carl Allchin Welcome to a New Year of Preppin' Data challenges. For anyone new to the challenges then let us give you an overview how the weekly challenge works.  Each Wednesday the Preppin' crew (Jenny, myself or a guest contributor) drop a data set(s) that requires some reshaping and/or cleaning to get it ready for analysis.  You can use any tool or language you want to do the reshaping (we build the challenges in Tableau Prep but love seeing different tools being learnt / tried). Share your solution on LinkedIn, Twitter/X, GitHub or the Tableau Forums Fill out our tracker so you can monitor your progress and involvement The following Tuesday we will post a written solution in Tableau Prep (thanks Tom) and a video walkthrough too (thanks Jenny) As with each January for the last few years, we'll set a number of challenges aimed at beginners. This is a great way to learn a number of fundamental data preparation skills or a chance to learn a new tool — New Year&
Read more

2023: Week 1 The Data Source Bank

Image
 Created by: Carl Allchin Welcome to a New Year of Preppin' Data. These are weekly exercises to help you learn and develop data preparation skills. We publish the challenges on a Wednesday and share a solution the following Tuesday. You can take the challenges whenever you want and we love to see your solutions. With data preparation, there is never just one way to complete the tasks so sharing your solutions will help others learn too. Share on Twitter, LinkedIn, the Tableau Forums or wherever you want to too. Tag Jenny Martin, Tom Prowse or myself or just use the #PreppinData to share your solutions.  The challenges are designed for learning Tableau Prep but we have a broad community who complete the challenges in R, Python, SQL, DBT, EasyMorph and many other tools. We love seeing people learn new tools so feel free to use whatever tools you want to complete the challenges.  A New Year means we start afresh so January's challenges will be focused on beginners. We will use dif
Read more

How to...Handle Free Text

Image
Free isn't always a good thing. In data, Free text is the example to state when proving that statements correct. However, lots of benefit can be gained from understanding data that has been entered in Free Text fields. What do we mean by Free Text? Free Text is the string based data that comes from allowing people to type answers in to systems and forms. The resulting data is normally stored within one column, with one answer per cell. As Free Text means the answer could be anything, this is what you get - absolutely anything. From expletives to slang, the words you will find in the data may be a challenge to interpret but the text is the closest way to collect the voice of your customer / employee. The Free Text field is likely to contain long, rambling sentences that can simply be analysed. If you count these fields, you are likely to have one of each entry each. Therefore, simply counting the entries will not provide anything meaningful to your analysis. The value is in
Read more