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
Currently, observed and predicted category names must match.
E.g. use this setup to reproduce the problem:
It is proposed to soften this restriction a bit, and to also allow category matching by order, if the number of categies is equal.
The text was updated successfully, but these errors were encountered:
@jakimowb any remarks from your side?
Sorry, something went wrong.
resolved #845
5f4dbb9
It need to be cristal clear which class matching. By now it seems to be on class names only.
Optimally the processing algorithm should support the following options:
The final report needs to show this as well, i.e. which used class names + numbers were compared.
Thanks @jakimowb, I will add a description to the docs and add the matching to the report.
FYI @jakimowb, done:
Class matching is shown in a table:
For classes that can't be matched by name, a warning is logged:
Improved algo doc:
adressed #845
4d7ae55
Merge pull request #846 from EnMAP-Box/845-classification-layer-accur…
50f06ff
…acy-and-area-report-add-support-for-non-matching-category-names resolved #845
janzandr
Successfully merging a pull request may close this issue.
Currently, observed and predicted category names must match.
E.g. use this setup to reproduce the problem:
It is proposed to soften this restriction a bit, and to also allow category matching by order, if the number of categies is equal.
The text was updated successfully, but these errors were encountered: