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
@dylanbeaudette
Following on the ideas posted in /misc in 8771db5
/misc
Can this idea be extended to include more comprehensive lists of features and multiple sources of the assignment of what is related to what?
I think we need to devise a plan for versioning this type of stuff, and figuring out what the source is.
e.g. Can we assign similar SFF linkages for all feature names from https://github.com/ncss-tech/SoilKnowledgeBase/blob/main/inst/extdata/KST/2014_KST_EN_featurelist.json? If we were to do that, how would we document what was from Bockheim and what was added after or changed?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
@dylanbeaudette
Following on the ideas posted in
/misc
in 8771db5Can this idea be extended to include more comprehensive lists of features and multiple sources of the assignment of what is related to what?
I think we need to devise a plan for versioning this type of stuff, and figuring out what the source is.
e.g. Can we assign similar SFF linkages for all feature names from https://github.com/ncss-tech/SoilKnowledgeBase/blob/main/inst/extdata/KST/2014_KST_EN_featurelist.json? If we were to do that, how would we document what was from Bockheim and what was added after or changed?
The text was updated successfully, but these errors were encountered: