Working with JSON data MySQL
Do not have 4100 identical tables.  There are so many issues with such, and it is repeatedly panned in this and other forums.

4100 "stations", each with, say 10 readings, per hour?  41000 is about 12/second (average), which is not very much if you had one row per datapoint per station.  One table with 3 columns: hour (or datetime), station_id, reading.  And batch the 10 rows in a single INSERT statement for a little more efficiency.

How you can fetch the data in a variety of ways -- "just temperatures at 6am on weekends" becomes a simple, and somewhat efficient query.

Alternatively, have one table with 12 columns:  hour/datetime, station_id, and 10 specific readings.  This is likely to be more efficient in all ways.  This also has the advantage that the readings can have specific datatypes for each measurement.  Temperature or humidity:  TINYINT SIGNED is 1 byte and allows -128..127 or DECIMAL(5.2) (3 bytes) for +/-999.99 instead of a generic FLOAT (4 bytes).

The alternatives probably take a similar amount of disk space.  This database will be rather big after a year; you should probably estimate the future size and think ahead about indexing, and other issues.