A missing date in the meter mappings will now halt processing of load. This is a change from previous behaviour where it would log an error for every meter,
and store its values with an ID that would be left unaggregated. The previous behaviour would ultimately take a long time, and produce no usable output, so it
was deemed aborting was a better outcome.
Added the following configuration options (see documentation for details):
meterFilePattern - the regex pattern used to match CSV meter reading files.
meterJsonPattern - the regex pattern used to match JSON meter reading files.
companyMapping - reference to a file providing a mapping between the company values in the network (from meter mappings) and the meter readings csv's
(from file name) if they differ.
Stopped logging all instances of a meter ID being found instead of a meter number. The total found is still recorded in the summary for comparison.
Added the reading date to the unmapped meter warning. Previously you couldn't tell which date the mapping was missing for if there were multiple date values
in a single meter readings CSV.
To enable logging messages for files which failed to process, add the required syslog options in the config file. Refer to configuration for more info.