The commandline option --api none was designed to allow users to run just the preprocessing portion of the tool without calling a (potentially costly) API or in "offline mode".
This task involves ensuring that it can also be used to run just the postprocessing portion of the tool against results previously obtained with out. The documentation should also be updated to reflect this usage.
For example, if you run geocoding for a set of addresses, you will have a spreadsheet with both SOURCE_ and RESULT_ columns, but unless you specify it at the time, none of the MATCH_ columns will appear. Using --api none should allow you to after-the-fact add these to an already geocoded spreadsheet without needing to hit the API again.
The commandline option
--api nonewas designed to allow users to run just the preprocessing portion of the tool without calling a (potentially costly) API or in "offline mode".This task involves ensuring that it can also be used to run just the postprocessing portion of the tool against results previously obtained with out. The documentation should also be updated to reflect this usage.
For example, if you run geocoding for a set of addresses, you will have a spreadsheet with both SOURCE_ and RESULT_ columns, but unless you specify it at the time, none of the MATCH_ columns will appear. Using
--api noneshould allow you to after-the-fact add these to an already geocoded spreadsheet without needing to hit the API again.