2023: Week 16 - Solution


Solution by Tom Prowse and you can download the workflow here.


Following from looking at Easter Sunday dates last week, we are now going to look why there is so much variation with Easter dates and how the moon reflects this.

Step 1 - Tidy Full Moon Input

First, we want to input the Full_Moon table and rename the fields: 

- Day = Full Moon Day
- Date = Full Moon Date (make sure this is a Date field type)

We can then clean the Time field to match the requirements. First we want to remove all the Numbers and Letters from the field so we are left with only the symbols that represent the different types of moons.


Then we want to replace the symbols with the corresponding type of moon as given in the requirements. As a result we should now have the 4 different types of moons in our table: 


Step 2 - Include Easter Sunday

We can now include the dates for Easter Sunday by joining the Easters table using an inner join where Full Moon Date <= Easter Sunday: 


Now we have both tables together we can calculate the Days between the full moon and Easter: 

Days Between 
DATEDIFF('day',[Full Moon Date],[Easter Sunday])

Then we can calculate the closest (minimum) days for each Easter Sunday by using a Fixed LOD calculation: 


Then we can filter where [Days Between Full Moon & Easter Sunday]=[Days between] and this will get us a row for each Easter Sunday and the closest Full Moon Date for each.

As Easter only occurs once a year, we can convert the both of the dates to a Year



Step 3 - Aggregate for No. Days Between

To highlight some of the interesting facts about the different number of days between Easter and the Full Moons, we want to aggregate the data. 

For this we want to group by Days Between Full Moon & Easter Sunday, and then sum Number of Rows, Max Full Moon Notes, Min Full Moon Date, Max Easter Sunday


After the aggregation we can rename the following fields: 

- Full Moon Notes = Most Interesting Event
- Number of Rows = Number of Occurrences
- Full Moon Date = Min Year
- Easter Sunday = Max Year

Then we can sort the table using a Rank calculation where we rank the Days Between field: 



We can then hide the Sort field and are ready to output our data: 



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

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

2023: Week 2 - International Bank Account Numbers

Image
Challenge By: Jenny Martin For week 2 of our beginner month, Data Source Bank has a requirement to construct International Bank Account Numbers (IBANs), even for Transactions taking place in the UK. We have all the information in separate fields, we just need to put it altogether in the following order: Inputs A list of the transactions, with information about the receiving bank account  A lookup table for the SWIFT Bank Codes  Requirements Input the data In the Transactions table, there is a Sort Code field which contains dashes. We need to remove these so just have a 6 digit string ( hint ) Use the SWIFT Bank Code lookup table to bring in additional information about the SWIFT code and Check Digits of the receiving bank account ( hint ) Add a field for the Country Code ( hint ) Hint: all these transactions take place in the UK so the Country Code should be GB Create the IBAN as above ( hint ) Hint: watch out for trying to combine sting fields with numeric fields - check data types Re
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