Merge Aquius

This tool merges Aquius dataset files into a single file. The tool cannot understand these files beyond their technical structure, so the files should be produced in a similar manner:

• Files must not duplicate one another's service count - else service totals will erroneously double.
• Files must all share the same or very similiar service filters - the filter indices and definitions are blindly assumed comparable.
• Files should use (if any) the same place/demographic data - the original boundaries are not present, so no assessment can be made of overlaps.

An optional config.json may also be added to the selection, which contains bespoke criteria for generating the output.

Nodes and places are grouped by shared coordinates - the number of decimal places can be set as configuration key coordinatePrecision. Products are grouped on name - all translations must be identical. Meta, option and translation content will be copied, but cannot always be merged - configuration keys can be used to supply definitions.

See documentation for configuration details and how to use of the output file. For routine or repeat usage, the merge script can incorporated into a bespoke application which imports the javascript and calls the function mergeAquius.merge(input, options), as documented.