You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be convenient to have a machine-readable schema describing which files exist, their keys, and the types (at least string/integer/double), to make it easier to write data loaders that could pull in and merge specified files and convert numeric types to the appropriate native types without hard-coding the field lists into the data loader.
This information is all available in the tables in README.md, so I'm just asking that you consider mirroring that data into a JSON file or some other machine-readable format that is also published with the data files.
Thanks for this great data source!
The text was updated successfully, but these errors were encountered:
This is a great idea. We were planning on automating some of the documentation aspects, so we needed to do this anyway and it's good to keep other use-cases in mind for that metadata.
Do you have any examples or references for a machine-readable schema similar to what you propose that would be useful to you?
It'd be convenient to have a machine-readable schema describing which files exist, their keys, and the types (at least string/integer/double), to make it easier to write data loaders that could pull in and merge specified files and convert numeric types to the appropriate native types without hard-coding the field lists into the data loader.
This information is all available in the tables in
README.md
, so I'm just asking that you consider mirroring that data into a JSON file or some other machine-readable format that is also published with the data files.Thanks for this great data source!
The text was updated successfully, but these errors were encountered: