I'm trying to design some tables, functions, etc. for weather data that will allow me to create routines that will identify extremes, averages, and such. At the same time I hope to learn much more about Alpha than I currently do.
Is there anyone out there already using Alpha for a weather database? I'm struggling to come up with a general design plan and I'd appreciate any tips regarding efficient design, function/index usage, etc.
I currently have more than a half-million 10-minute records representing 11 years of weather data from my home weather station imported into both yearly tables and a single (all data) table. I'm guessing I'll want to work with the ever-growing single table to write routines to identify various statistics.
I'm thinking initially it might be best to create two more tables to post daily and monthly statistics to. For example: the daily table would be populated with stats for each MM/DD such as high/low/average Temp/Wind/Rain/Barometer/etc. This would answer questions like what is the normal high/low/ave for each element for a particular month/day. The same would be done for monthly statistics (i.e. for the month of MM).
It seems this type of database would be a little different from the more common Invoice, Inventory, or Contact Management databases, or maybe it's more similar than I'm thinking. I hope I can get some good, efficient ideas, tips, etc. for getting this thing going, and/or finding someone who's already started working on something similar.
Thanks for any replies!!!
Is there anyone out there already using Alpha for a weather database? I'm struggling to come up with a general design plan and I'd appreciate any tips regarding efficient design, function/index usage, etc.
I currently have more than a half-million 10-minute records representing 11 years of weather data from my home weather station imported into both yearly tables and a single (all data) table. I'm guessing I'll want to work with the ever-growing single table to write routines to identify various statistics.
I'm thinking initially it might be best to create two more tables to post daily and monthly statistics to. For example: the daily table would be populated with stats for each MM/DD such as high/low/average Temp/Wind/Rain/Barometer/etc. This would answer questions like what is the normal high/low/ave for each element for a particular month/day. The same would be done for monthly statistics (i.e. for the month of MM).
It seems this type of database would be a little different from the more common Invoice, Inventory, or Contact Management databases, or maybe it's more similar than I'm thinking. I hope I can get some good, efficient ideas, tips, etc. for getting this thing going, and/or finding someone who's already started working on something similar.
Thanks for any replies!!!
Comment