-
Notifications
You must be signed in to change notification settings - Fork 62
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
Interpretation of 06_classify_image.py outputs (again) #6
Comments
Unfortunately, it's hard to give any useful advice based on your comment. In our tests the classification was fine (even so, not good as segmentation approaches). What do you mean by
Normally you should have one label per pixel. Have you tested our pretrained models? Maybe something went wrong during training. |
Please also check, that the data you intend to classify, has the same preprocessing as the EuroSAT dataset. We already had this problem in a previous issue |
Thanks @jensleitloff for those suggestions. Yes I downloaded your models a few months ago so can try those and will check that the Sentinel data is prepared the same way as described in that issue. |
Are you on the latest version of the repository, @tonyboston-au ? Please do a
since in e956484 we fixed a bug. |
okay will do - thanks @felixriese |
@jensleitloff I'm having trouble interpreting the classes created by a model in the label.tif file. 02_train_rgb_finetuning.py outputs the classes as:
Found 18900 images belonging to 10 classes.
{'AnnualCrop': 0, 'Forest': 1, 'HerbaceousVegetation': 2, 'Highway': 3, 'Industrial': 4, 'Pasture': 5, 'PermanentCrop': 6, 'Residential': 7, 'River': 8, 'SeaLake': 9}
Found 8100 images belonging to 10 classes.
...
When I review the grayscale TIF image created by 06_classify_image.py, the classes don't make sense. For example, the forest class (identified by overlaying the Sentinel-2 satellite image) is displayed as class #9 #090909, which according to the above legend should be the class 'SeaLake'. I must be doing something wrong!
Any advice is really appreciated.
The text was updated successfully, but these errors were encountered: