-
Notifications
You must be signed in to change notification settings - Fork 45
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
Import custom LC dataset not working properly #862
Comments
@gdaldegan can you share the Bahamas layer, so I can test and figure out the underlying issue, thanks. |
@gdaldegan does the below screenshot show the expected import workflow and output? |
thanks @Samweli! Yes, this is the expected output after importing a custom land cover layer. What was preventing it to be correctly imported? |
@gdaldegan I haven't changed anything in the plugin code yet, I just restored the plugin land cover classes to their default state and ran the process. Can you share the screenshot/steps of you getting the error? |
@gdaldegan what are the available LC classes in the settings and the land cover classes aggregation definition you are using when importing?
|
The land cover pixel values are as follows: |
Thanks @gdaldegan, can you take a screenshot of these classes as defined in the plugin settings and the aggregation land cover definition tool and share them. If not, can we schedule a meeting so we can look at these classes definitions together. |
@Samweli here's the screenshot. Just went through the steps again, now resetting to default, and the imported dataset still showing only 3 classes. |
Only a subset of land cover classes is correctly imported when importing custom land cover datasets developed locally. For instance, tried to import a LC layer for the Bahamas originally containing 8 classes, but only 2 are shown after importing this layer into Trends.Earth using the function.
The text was updated successfully, but these errors were encountered: