From Cumulus Wiki
Name: ImportCumulusFile
Type: PHP
Author: David A Jamieson / Mark Crossley
Contact: 'DAJ' / 'mcrossley' via the forum
Last update: 11 September 2018
Version: 3.2

This is a PHP script designed to run on your webserver and import Cumulus log files into a MySQL database on your server.


The web server must have..

  • PHP
  • MySQL
  • A My SQL database, username and password
  • a Cumulus Log already uploaded


Version 2.0 changes the SQL table structures from version 1.x. If you are currently using version 1.x and wish to upgrade, then you should DROP the existing tables and let the version 2 script recreate them. If this is unacceptable DO NOT UPGRADE, stay with version 1.x

The new table formats use a combined date/time field instead of separate, this makes constructing queries much simpler, it is worth making the change.

Of course if you do change, then any existing queries you are using will also have to be rewritten - take this into account. It may be possible to create VIEWs of the new tables that mimic the old table format, and for you to use those views with your existing queries, that is an exercise for you!

You could of course run 1.x and 2.x in parallel whilst you made the switch over gradually. Just alter the table names in v2 of the script slightly to avoid name collisions.


  • Download the PHP script ... (right click, Save as) and then rename the .txt to .php
  • Save the file and edit it using a text editor -- there are five entries to be edited
servername, username, password, database and security key
these are documented in the file at the top.
There are three further variables to consider and may require editing. Look at the text file you are importing. How is each field separated/delimited? How is the date delimited? How is a decimal number shown? In the UK there is nothing else needs changed. If for example your delimiter is a semi-colon and a dash then change the lines $field_delimiter and $date_delimiter accordingly.
if your decimal separator is a comma this also needs to be changed in the file using the $decimal_separator variable
  • save the file as ImportCumulusFile.php or whatever name you prefer and upload it to your webserver.

Using the script

Currently you can import two file types from Cumulus -- the dayfile and the Monthly log files.

Firstly decide the table to be populated in your SQL database. If the table does not exist the script will create it. Typically you have one table for the dayfile, and one or more for the Monthly Logs. You could import every monthly log file into one large SQL table.

If you re-import existing data the script will update the data in the table so you can run the import every day on the same file, dayfile, for example

You must pass several options with your URL... (They can be in any order but the first one must start with ? other with &)

  • type=xxxx
this must be either the phrase dayfile, monthly or realtime
  • file=xxxxx
the location on your webserver, relative to this script location, of your Cumulus File
example file=dayfile.txt or file=../data/Jan10log.txt
  • table=xxxx
the table within SQL to import the data. If it does not exist the script will create it
  • key=xxxxx
A security key, unique to you, to pass as part of the URL. This stops others from running the script on your server if the do not know the key.

An example URL...

The result

If all goes well it will create or update the table with the relevant data and report back the word "Done". If the script fails there are a number of outputs it could return to explain the problem.

Further automation

Using the above script, in combination with the Toolbox you could set an automated FTP rule to upload the dayfile.txt from Cumulus each day at 00:15 and then run an HTTP remote command (this script) to import it into the SQL database

Version 2.0 of the script can also be invoked from a command line. So for example importing the realtime file from the command line would look like this:

 php importcumulusfilev2-0.php file=realtime.txt type=realtime key=secretKey retainVal=7 retainUnit=day

This allows you to run the script as cron job on a Linux server, or as a scheduled task on a Windows server.

Version Control

  • 3.2 - 11 September 2018 [Download]
    • Fixed inserting of WindbearingSym and CurrWindBearingSym
  • 3.1 - 1 March 2018 [Download]
    • Fix variable typos in realtime table creation status messages
    • Remove some HTTP headers that were causing problems on some servers
  • 3.0 - 6 November 2016 [Download]
    • Converted to use prepared statements - more efficient for bulk inserts (the main use for script with CumulusMX?)
    • SQL injection protection improved - requires the table names to be defined in this script
  • 2.8 - 27 April 2015 [Download]
    • Added addtional configuration parameter $rainUnit, default is 'mm'
    • Added 'rain since midnight' to the monthly log file table
    • This version is REQUIRED to support CumulusMX direct inserts
    • Altered layout the SQL statements to make finding/fixing stuff easier!
    • To updated existing monthly tables use the following SQL command [if you use 'mm' for rain change (4,2) to (4,1)]:
  • 2.7 - 23 February 2015 [Download]
    • Fixed realtime/monthly/day tables creates, to make rainfall 2dp to allow for inches
    • Fixed monthly table create, to make evapotrans 2 dp
    • Converted from depreciated mysql to mysqli
  • 2.6 - 02 April 2014, Mark Crossley [Download]
    • Fixed a PHP vulnerability that could reveal your passcode
  • 2.5 - 03 December 2013 (uploaded 02 Feb 2014), Mark Crossley [Download]
    • Changed day file HighSolarRad from varchar(5) to decimal(5,1)
      • To alter an existing table...
      • ALTER TABLE `dayfile` CHANGE `HighSolarRad` `HighSolarRad` DECIMAL(5,1) NULL DEFAULT NULL
  • 2.4 - 23 October 2013, Mark crossley [Download]
    • Changed day file humidity fields from varchar(3) to decimal(4,1)
  • 2.3 - 05 June 2013, Mark Crossley [Download]
    • Fixed dayfile & monthfile table column HoursSun was decimal(2,1) to decimal(3,1)
  • 2.2 - 21 April 2013, Mark Crossley
    • Made dayfile UV a decimal(3,1) field rather than varchar(4)
  • 2.1 - 29 March 2013, Mark Crossley [Download]
    • Fixed typo in day file table field name LowDewPint -> LowDewPoint
  • 2.0 - 13 March 2013, Mark Crossley [Download]
    • Change monthly and realtime tables to use combined date/time columns rather than separate
    • Added optional retention time for realtime table. Records older than the specified age will be deleted. retainVal=NNN retainUnit=XXXX
    • Added checking to allow running of the script from a command line as well as via http
    • Added 'extra' columns to record wind directions as compass points where they are only provided as bearings:
Dayfile:  Added the following columns:- HWindGBearSym, DomWindDirSym
Monthly:  Added the following columns:- WindbearingSym, CurrWindBearingSym
  • 1.4a - 3 December 2012, Mark Crossley. Fixes syntax errors in 1.4, adds parameter presence checking. [Download]
  • 1.4 - 3 December 2012, Mark Crossley. Added ability to create and log data to a 'realtime' table.
  • 1.3b - 30 Nov 2012, Mark Crossley, changed so ALL missing values from the dayfile are entered into the table as NULL. If you have used the Cumulus editor, then they will be present in the file as blank fields. [Download]
  • 1.3a - 30 Nov 2012, Mark Crossley, added line breaks to output text [Download]
  • 1.3 - 27 Nov 2012, Mark Crossley, updated for Cumulus b1050 [Download]
  • 1.2 - 6 May 2011, Mark Crossley, updated for Cumulus 1.9.1
  • 1.1c Small modification to code to handle date delimiter with a dot [Download]
  • 1.1b Added a variable to consider decimal separator
  • 1.1a Added date delimiter
  • 1.1 Added the facility to identify the delimiter used on the import file
  • 1.0 First Release