Sorry me again (and happy new year).
I'm not sure I will be able to compare 2012 and 2018 CIR imagery accurately with spatial models. It seems the results are too inconsistent between the two years. I have use machine learning for 2012, even with a good few thousand sample points and there are still too many holes. It still picks up edges of shadows even though I have sample points for shadows. Perhaps there are trees being picked up with a similar pixel value.
What would be the best solution in this case? Do I add a lot many more sample points for 2012? And since I am not doing machine learning for 2018 the results are quite different. I tested the machine learning on the 2018 imagery with the same miz file but it isn't capturing enough tree canopy.
I don't know if it helps but I have attached the miz and spatial models for you.
ndvi_with_color_table_2018.gmdx is what I used for the 2018 CIR imagery
machine_learning_tree.gmdx uses the shapefile of sample points for 2012 which consists of
- trees (1776)
- buildings (5)
- grass (1406)
- shadow (443)
- Water (33)
as well as a few other points.
I then ran the spatial model tree_output_2012.gmdx which uses the miz from the previous model.
Regards,
Josh
Hi Josh,
By intensity do you mean the colorspace Intensity when converting RGB to Intensity, Hue, Saturation? If so then yes, you'll need to use the RGB to IHS operator to convert three input bands (representing the R, G and B wavelength bands) into IHS and then take just the I. Or actually I think there's a dedicated RGB to Intensity operator if all you want is Intensity.
You'll need to use the Band Selection operator (three of them) to select the R, G and B bands to send to the appropriate ports on the Intensity operators.
On any moving-window operators such as Variance Texture the Focus input port wants a MAtrix to define the moving window extent. E.g. a 3x3 matrix populated with all 1s would be a 3x3 moving window around each pixel being analysed. So use a Custom Matrix Input operator and hook it up to the Focus port. Double-click the Custom Matrix Input operator to bring up the Matrix Source dialog. This let's you define the size, shape and other characteristics of the moving window. Larger extents let you start doing useful things like clipping the corners to form circular windows:
Cheers
Hi Josh,
By intensity do you mean the colorspace Intensity when converting RGB to Intensity, Hue, Saturation? If so then yes, you'll need to use the RGB to IHS operator to convert three input bands (representing the R, G and B wavelength bands) into IHS and then take just the I. Or actually I think there's a dedicated RGB to Intensity operator if all you want is Intensity.
You'll need to use the Band Selection operator (three of them) to select the R, G and B bands to send to the appropriate ports on the Intensity operators.
On any moving-window operators such as Variance Texture the Focus input port wants a MAtrix to define the moving window extent. E.g. a 3x3 matrix populated with all 1s would be a 3x3 moving window around each pixel being analysed. So use a Custom Matrix Input operator and hook it up to the Focus port. Double-click the Custom Matrix Input operator to bring up the Matrix Source dialog. This let's you define the size, shape and other characteristics of the moving window. Larger extents let you start doing useful things like clipping the corners to form circular windows:
Cheers