We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is it better to have one file for each herb in flora?
Currently, the flora is defined in a single json file.
Use separate files for herbs.
Copy dataherb.json to workdir/{id}/dataherb.json or {id}.json will work.
dataherb.json
workdir/{id}/dataherb.json
{id}.json
Build the flora from all these files.
Implement this new structure.
In this way, we can put up a repo for open datasets easily and allow users to add more easily.
Possible creating process
Create package directly on GitHub by uploading the dataherb.json file.
Setup a demo repo as demo flora.
The text was updated successfully, but these errors were encountered:
emptymalei
Successfully merging a pull request may close this issue.
Is it better to have one file for each herb in flora?
Situition
Currently, the flora is defined in a single json file.
Solution
Use separate files for herbs.
Simply Copy dataherb.json
Copy
dataherb.json
toworkdir/{id}/dataherb.json
or{id}.json
will work.Build the flora from all these files.
Implement this new structure.
Ready for a Demo repo of flora
In this way, we can put up a repo for open datasets easily and allow users to add more easily.
Possible creating process
Create package directly on GitHub by uploading the dataherb.json file.
Setup a demo repo as demo flora.
The text was updated successfully, but these errors were encountered: