How to design a database in the subject area "Weather"?

Question

Database

I am doing a coursework on databases. My subject area is Weather Forecast. Three entities are given: weather, forecasts and reports.
Help, please, at least to estimate the model of this database: what attributes the tables should have and what types of relationships between tables to make.

Answer 1

Here at least you need to get into the subject area a little and answer yourself the following questions (up to tables and fields):
- what is "weather", how it is measured, what characteristics it has, whether there are tabular data: such as binding to the area (city, district etc.), comfort tables (not very comfortable, not comfortable) or humidity (dry, wet, wet, etc.)?
- we write the same thing for the forecast.
- now according to reports, what types of reports are planned (per day by terrain, bearing by forecast, etc.).
As far as reports are concerned, they are (usually) of two types.
Some are formed by a simple selection from a database with aggregation - these are simple aggregated reports (average temperature per hour, or minimum / maximum for a period by area). For such reports, it is usually not necessary to create tables and store intermediate data, unless for speedy provision and for archiving purposes (for example, calculating and storing the average day/night temperature daily after the end of the day).
The second is analytical. For example, the average error in forecasts for the same periods for localities. These are the reports that require the aggregation of several samples, here you have to create intermediate tables with the results of the samples, and already generate output data from them (like finding the second and third derivatives of functions).
In general, first describe in WORDS what you have at the entrance in terms of weather and temperature, and what reports you would like to receive. And already from this you make a data model for simple reports, and at the very end you are engaged in analytics. Also, immediately take care of the amount of data, suddenly they will have to be sharded, archived, etc.
I asked leading questions. Answer, let's move on.