-
Notifications
You must be signed in to change notification settings - Fork 17
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
Revised Draft ML API. #517
base: ml
Are you sure you want to change the base?
Conversation
PondiB
commented
Jul 17, 2024
- Shifted from the STAC ML extension to MLM STAC extension
- Change from "predictor" and "target" to training_set and the "target" parameter can be a column name of the dependent variable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@PondiB The subtype doesn't need to follow the STAC naming, so it can still be ml-model instead of mlm-model.
Agreed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From this description, it is unclear to me how training data (predictors+labels) are passed into the process. The description on the two parameters needs to be clearer.
An alternative approach could be to include the training labels in the raster data cube. This would require a vector-to-raster conversion if training data exists as vector data.
Sure |
Co-authored-by: Matthias Mohr <[email protected]>
Co-authored-by: Matthias Mohr <[email protected]>
Co-authored-by: Matthias Mohr <[email protected]>
Co-authored-by: Matthias Mohr <[email protected]>