Input & output data formatting is horrible

thegooglecodearchive / geolocate-cli

Automatically exported from code.google.com/p/geolocate-cli

GNU General Public License v3.0

0 stars 0 forks source link

Input & output data formatting is horrible #8

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

Inputting data is currently horrible as the program expects json.  While
json is reasonable as an internal data exchange format, most humans are
more likely to write unlabeled comma-separated values.

Thus, we should make the program read and write csv.

Unfortunately, in order to specify the meanings of the columns we probably
need a new command line option.

Original issue reported on code.google.com by fmarkham@gmail.com on 30 Mar 2010 at 1:26

Blocking: #11
Blocked on: #10, #12

GoogleCodeExporter commented 9 years ago

Original comment by fmarkham@gmail.com on 30 Mar 2010 at 1:28

Changed title: Input & output data formatting is horrible

GoogleCodeExporter commented 9 years ago

Original comment by fmarkham@gmail.com on 30 Mar 2010 at 1:39

GoogleCodeExporter commented 9 years ago

Original comment by fmarkham@gmail.com on 30 Mar 2010 at 1:44

Added labels: Milestone-0.1

GoogleCodeExporter commented 9 years ago

In order for this to make sense, we need separate scripts so each can format 
their
own input/output.  Blocking on [ issue 10 ]

Original comment by fmarkham@gmail.com on 31 Mar 2010 at 2:26