**geo-affine » R**, and kindly contributed to R-bloggers)

The main question when using remote sensed raster data, as we do, is the question of NaN-treatment. Many R functions are able to use an option like rm.NaN=TRUE to treat these missing values. In our case the kmeans function in R is not capable to use such a parameter. After reading the tif-files and creating of a layer stack we will go on with a work-around to solve the missing values problem of the non-covered areas of a landsat picture.

**First: get the data**

In the part one we have already described where to get the data. As the used dataset contains surface reflectance values and the calculation of these values results in additional missing values inside the taken Landsat picture we will go with the original digital numbers by Landsat: Download and unzip the bands one to five and seven from this location.

**Second: prepare the data**

Now stick with the mentioned tutorial:

setwd("~/wd_r/ETM") library("raster") A <- stack(c("p134r027_7t20010820_z48_nn10.tif","p134r027_7t20010820_z48_nn20.tif","p134r027_7t20010820_z48_nn30.tif","p134r027_7t20010820_z48_nn40.tif","p134r027_7t20010820_z48_nn50.tif", "p134r027_7t20010820_z48_nn70.tif"))

Now we will create a rectangular subset of our desired region using a plot of the Landsat image and an interactive method to obtain the extent. Please be aware to take only the covered region!!!:

plotRGB(A, 3,2,1) ext <- drawExtent() #draw a box by clicking upper left and lower right corner in the plot C <- crop(A, ext)

**Third: classify the data**

The classification itself will be done on a corresponding dataframe:

DF <- as.data.frame(C) summary(C) # to make sure you don't have any NA's E <- kmeans(DF, 12, iter.max = 100, nstart = 10)

We have chosen 12 classes because it is much easier to merge classes after classification than to split classes. 12 classes will be detailed enough but still fast to get a result for the given area in Mongolia. It could be possible to start with another number for your desired area. If you have a lot of different possible land covers you should increase this number. We will set the number of maximal iterations to 100 to make sure that less then 5% of the pixels are changing their class after one step.

The main problem in R seems to be the availability of R. My system is build up by Intel Centrino 2 Dual Core 2.53Ghz with 8GB of RAM and a SSD. But the classification of 14 million objects of a dataframe had taken much longer than I was used from ArcGIS or Erdas Imagine. (If you see improvement mail me please!!!)

Here’s how to create a raster from the resulting kmeans object:

DF[,7] <- E$cluster EM <- matrix(DF[,7], [email protected],[email protected], byrow=TRUE) E.raster <- raster(EM,[email protected], [email protected]@xmin, [email protected]@ymin, [email protected]@xmax, [email protected]@ymax) writeRaster(E.raster,"12_classes.tif", overwrite=TRUE)

And here is the result in QGIS:

**leave a comment**for the author, please follow the link and comment on their blog:

**geo-affine » R**.

R-bloggers.com offers

**daily e-mail updates**about R news and tutorials on topics such as: Data science, Big Data, R jobs, visualization (ggplot2, Boxplots, maps, animation), programming (RStudio, Sweave, LaTeX, SQL, Eclipse, git, hadoop, Web Scraping) statistics (regression, PCA, time series, trading) and more...