CLI translation front-end

[wsp-mbuckley]

Add a __main__.py entry point script which can provide a simple command-line interface. Initially I think it would be good to add a translation sub-command which allows people to run zone translations in as simple a way as possible.

• [x] Create __main__.py with argparser setup to handle sub-commands
• [x] Add 'translate' sub-command in argparser to run zone translations

Translate sub-command would need the following parameters:

• data file: CSV file containing data to be translated
• translation file: path to CSV containing translation
• output: path to output file
• zone column: name of column containing zone ID, default 'zone_id'
• from column: name of column in translation containing from zone id, default 'from_id'
• to column: name of column in translation containing to zone id, default 'to_id'
• factor column: name of column in translation containing split factors, default 'split_factor'
• matrix: boolean flag for whether data file should be considered a matrix (if true zone column should be 2 values), default False

Given the number of parameters it might make more sense to have those be a config and just pass the path to a config as the argument? Also it might make sense to split the sub-command into 2 separate ones one for vector translate and one for matrix translate, because matrix translate might want a format parameter to handle both wide and long formats.

[BenTaylor-TfN]

I'm all for this idea - would make ad-hoc translations much easier to do.

I think we'd like the option for both config and CLI args. If the args defaulted to whatever CAF.space chucks out, and the output location defaults to the current working directory then you could get away with:

• data file
• translation file