Dynamic Weather Loot,

Skip to content

Avast ye! This be a machine-translated text, an’ it may contain errors, aye!

‘Bout the Task

Ye be tasked wi’ creatin’ a service that fetches weather information from the web an’ presents it in a useful manner. The task be
deliberately open – ye choose yer own technology, platform, an’ approach.

Examples o’ technologies

  • 🌐 Webpage wi’ HTML/CSS/JS
  • 🖥️ Command-line tool (fer example, in a Python console)
  • 🤖 Discord chatbot
  • 🪟 tkinter dashboard

🌤️ Main Quest Medium

Part 1 – Fetch Weather Data

Yer service be needin’ to fetch weather data for a given location. Ye be findin’ a source o’ yer own, an’ how to retrieve structured data from it programmatically.

Søketips

Feel free to hunt for terms like “weather API”, “free weather data”, or services forged for exactly this purpose.

Part 2 – Display the Booty

Once ye’ve hauled in the data, ye must present it in a clear and user-friendly manner.

  • Consider what the user truly needs to know
  • The display should be shipshape – be it a dashboard, a table, a view in the terminal, or the like

CLI-tips

Be buildin’ a command-line tool, matey? Check out the rich library – it makes it easy to craft fine tables, colors, and layouts right in the terminal.

⭐ Sub-task 1 – Smart Recommendations Medium

Expand yer service to answer questions based on the weather booty.

Examples o’ questions the service can answer:

  • Be I needin’ an umbrella?
  • Do I be needin’ a jacket?
  • Should I have winter tires on me vessel?
  • Be I needin’ sunblock?
  • Be it slippery out there?

These answers shall be based on actual values from the weather data – not just static scrolls.

Tip

Consider which values (temperature, precipitation, wind speed, etc.) are relevant to each question. How ye present the answers be up to ye – it could be a text field where ye enter the question, fixed icons/indicators in yer dashboard, or a separate command in the CLI (chatbot).

⭐ Part 2 – Automatic Location Detection Hard

If the user does not provide a location, the service shall automatically determine where it be runnin’ and use that location.

  • Discover how ye can determine position without the user scribblin’ anythin’ down
  • This should function as a “fallback” – the location can still be overridden manually

Husk

There be no single map to how this should look, aye. Focus on makin’ sure the service actually works and be useful to use.