Hi Willis,
No, I have not found a place to buy it, and I got a similar answer similar to the one from Meterologica from Ambient. So nowadays I use CSVed to excerpt a day of records from the dbase.csv and use a script in MySQL WorkBench to get it into MariaDB. This is a temporary solution so I have no automatic way of getting triggered procedures to produce new statistic calculations on the fly. I my case I am also moving south in a few months or half a year or so, as soon as I've sold my house, and on the new location I will move from VWS altogether since I am not happy with the longint (if I recall correctly) datetime used by VWSql to get data into MySQL/MariaDB. So the Oasen table within WeatherData database has a trigger procedure that converts the most recent record from VWSql in Oasen into a new record in my Osterasen table with data in more appropriate intrinsic MariaDB/MySQL data date types, which really makes them easier to produce better statistics from in the long run of things.
From this current location I have almost 5 million minute records and and made a few statistic methods in SciLab, but SciLab doesn't have a working 64-bit database connection to Maria/My from Windows so I will convert these procedures to Octave once I decided on what to replace VWS with, only thing is that it has to be readable from WxSim/WxSimate to produce forecasts.
In my Osterasen (moved records) I also have added more indexes improve speed and it really helps - this was neccesary to do because VWSql hade problems with my new intrinsic datatypes.
And Davis and the new fields added to VWS a decade ago are not added by VWSql, so those are additional reasons to move from VWS...VWSql combination. It starts getting to hairy...
Well, I had hoped that VWS/Ambient would buy out the code from Meterologica and insert it into VWS itself perhaps with some conversion tools I could provide to directly make it insert My/Maria intrincic date values.
Here you have the procedure to get one days data from dbase.csv into the WeatherData database and the Oasen table. Easy to change their names and cahnge to parameterized infile on the call of the procedure.
I found an old PHP script somewhere to read dbase.csv and get data into MySQL but that code was rather badly structured and it would have been a real pain to get it into modern versions of PHP I use a PHP version a couple of years old do do some other work, and including automated translations of WxSim forecasts.
Sorry to be so pesimistic about the future of VWS, but without a great database interface it has no future in my eyes. So I am looking for something that has MariaDB (the way to go) integration and something that also is readable from WxSim.
Regards,
IngemarS
This is a USE weatherdata;
LOAD DATA LOCAL INFILE 'C:\\vws\\data\\dbase20150717.csv'
INTO TABLE oasen
CHARACTER SET utf8
FIELDS TERMINATED BY ','
LINES TERMINATED BY '\n'
(RecDate, WindDir, WindSpeed, WindGust, IndoorHumidity,
OutdoorHumidity, IndoorTemperature, OutdoorTemperature, BarometricPressure, TotalRain,
CH1Temperature, CH1Humidity, CH2Temperature, CH2Humidity, CH3Temperature,
CH3Humidity, Evapotranspiration, UVindex, SolarRadiation, WindChill,
IndoorHeatIndex, OutdoorHeatIndex, DewPoint, SealevelPressure, PressureAltitude,
CloudBase, AirDensity, VirtualTemperature, VaporPressure, WindDirRate,
WindSpeedRate, WindGustRate, IndoorHumidityRate, OutdoorHumidityRate, IndoorTemperatureRate,
OutdoorTemperatureRate, BarometricPressureRate, TotalRainRate, CH1TemperatureRate, CH1HumidityRate,
CH2TemperatureRate, CH2HumidityRate, CH3TemperatureRate, CH3HumidityRate, EvapotranspirationRate,
UVindexRate, SolarRadiationRate, WindChillRate, IndoorHeatIndexRate, OutdoorHeatIndexRate,
DewPointRate, SeaLevelPressureRate, RainDaily, RainHourly, Last24HrRain,
RainRate, WindRunDaily, DegDaysHeatingDaily, DegDaysCoolingDaily, MoonPhase,
MonthlyRain, DegDaysHeatingMonthly, DegDaysCoolingMonthly, WindRunMonthly, DegDaysHeatingYearly,
DegDaysCoolingYearly, WindRunYearly, @disregard, @disregard, @disregard,
@disregard, @disregard, @disregard, @disregard, @disregard,
@disregard, @disregard, @disregard, @disregard, @disregard,
@disregard, @disregard, @disregard, @disregard, @disregard,
@disregard, @disregard, @disregard, @disregard, @disregard,
@disregard, @disregard, @disregard, @disregard, @disregard,
@disregard, @disregard, @disregard, @disregard, @disregard,
@disregard, @disregard, @disregard
);
