-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decide whether to use Flatterer or Flatten Tool for converting from JSON to CSV format #14
Comments
The number one question for me is what is the CSV use case? Perhaps if the records are capturing the kilometre length of links, it would be useful to open in a spreadsheet. Other scenarios? |
Edit: @stevesong, since your question is about the CSV format in general, rather than conversion tooling, I've copied it to the discussion on publication formats and moved my reply there. |
Noting here that this is also dependent on any decision made in #17. |
@kindly if we were to use Flatterer's output as the CSV format for OFDS data, how much work would it be to author a conversion script so that CSV data could be converted to JSON format for validation in CoVE? If it's a lot of work, could we instead use Flatterer to generate a |
@duncandewhurst flatterer is really intended for just flattening as it creates Nonetheless recently flatterer has a feature called |
Thanks, @kindly Would using a data package schema be an alternative to unflattering for CSV validation?
|
For the Alpha at least, we've decided to use Flatten Tool because it offers support for round-tripping and has better organisational support. I've opened an issue about support for streaming in Flatten Tool: OpenDataServices/flatten-tool#399 |
We've not heard any further feedback on this issue so I'm going to close it for now. |
We need to decide whether to use Flatterer or Flatten Tool for converting from JSON to CSV format.
Some things to consider:
The text was updated successfully, but these errors were encountered: