🏃♂️ Cardio Calorie Burner
This Notion database determines calories burned after performing the following cardio activities: walking, jogging, running, hiking, biking, stair climbing, boxing and sprinting. Using the MET score, I was able to find how many calories are burned in relation to an individual’s weight. This calorie aid will fit nicely inside any workout dashboard.
Let me give you a tour of how I set up the calorie burner calculator. Firstly, I utilized the link database¹ function to separate my database into three views.
The Calculator
Change the calculator properties as needed (ie. for weight fluctuations).
The Calendar
The calendar view is set up to provide a quick reference for the week’s progress. For example, I use it to determine if I have achieved 3 days of cardio every week. Properties shown here are Activity and Calories Burned.
The Log
Here is where I input every circuit (workout). The following properties need to be manually updated for the calculator to return a result:
Activity
Intensity
Stopwatch (Include End Date and Time)
Week (Inside Circuit entry): This property is for those that want to calculate calories burned weekly.
Tip: Calculate calories burned for a particular week by filtering this view by "Week :: Is :: __" and calculate the sum below the Calories Burned Column.
Formulas
Weight to Kg:
round(100 * prop("Weight lbs") * 0.453592 / 100)Calories Burned:
round(100 * prop("Weight to Kg") * prop("MET Score") * dateBetween(end(prop("Stopwatch")), start(prop("Stopwatch")), "minutes") / 60) / 100MET Score (example of one string for “run” activity):
if(prop("Activity") == "Run" and prop("Intensity") == "Leisure" or prop("Activity") == "Run" and prop("Intensity") == "Medium", 9, if(prop("Activity") == "Run" and prop("Intensity") == "Intense", 11Footnotes
Link Database: (trigger: /link database) Use this function to place a copy of your database inside another page or area. The properties and data within a linked databases can be altered, however, the original database will change as well. This acts as a mirror rather than a duplication. The only altercations that can be made without changing the original database are sort, filter, property arrangement and database view.