Open mheadd opened 9 years ago
Cool - I haven't used qj before. We tend to stick with CSV files as they are smaller, more common, and support streaming (which really helps with the big stuff).
Still, this may just be because we haven't had to do much work ingesting JSON data. Feel free to add something on jq via a PR!
Will do.
My typical use case with jq is pulling JSON from a CKAN API and converting to CSV. Here's an example of doing that for data that is formatted to conform to the LIVES standard (in this case, for the City of Evanston).
I'd suggest adding a tool like jq to the standard toolkit for working with JSON. Its my go to utility for working with JSON and getting data from APIs that I need to load into another system or tool.
Fits in very nicely to my command line toolset.