• Stars
    star
    220
  • Rank 180,422 (Top 4 %)
  • Language
    R
  • License
    GNU General Publi...
  • Created about 5 years ago
  • Updated 7 months ago

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

FIELDimageR: A R package to analyze orthomosaic images from agricultural field trials. This package is a compilation of functions to analyze pos-mosaicking images from research fields, and allows to: crop the image; remove soil effect; build vegetation indices; rotate the image; build the plot shapefile; extract information for each plot; and evaluate stand count, canopy percentage, and plant height.

FIELDimageR: A Tool to Analyze Images From Agricultural Field Trials and Lab in R.

This package is a compilation of functions to analyze orthomosaic images from research fields. To prepare the image it first allows to crop the image, remove soil and weeds and rotate the image. The package also builds a plot shapefile in order to extract information for each plot to evaluate different wavelengths, vegetation indices, stand count, canopy percentage, and plant height.


Resources


Installation

If desired, one can build a rocker/rstudio based Docker image with all the requirements already installed by using the Dockerfile in this repository.

With RStudio

First of all, install R and RStudio. Then, in order to install R/FIELDimageR from GitHub GitHub repository, you need to install the following packages in R. For Windows users who have an R version higher than 4.0, you need to install RTools, tutorial RTools For Windows.


Now install R/FIELDimageR using the install_github function from devtools package. If necessary, use the argument type="source".

install.packages("devtools")
devtools::install_github("OpenDroneMap/FIELDimageR")

If the method above doesn't work, use the next lines by downloading the FIELDimageR-master.zip file

setwd("~/FIELDimageR-master.zip") # ~ is the path from where you saved the file.zip
unzip("FIELDimageR-master.zip") 
file.rename("FIELDimageR-master", "FIELDimageR") 
shell("R CMD build FIELDimageR") # or system("R CMD build FIELDimageR")
install.packages("FIELDimageR_0.3.2.tar.gz", repos = NULL, type="source") # Make sure to use the right version (e.g. 0.3.2)



With Docker

When building the Docker image you will need the Dockerfile in this repository available on the local machine. Another requirement is that Docker is installed on the machine as well.

Open a terminal window and at the command prompt enter the following command to build the Docker image:

docker build -t fieldimager -f ./Dockerfile ./

The different command line parameters are as follows:

  • docker is the Docker command itself
  • build tells Docker that we want to build an image
  • -t indicates that we will be specifying then tag (name) of the created image
  • fieldimager is the tag (name) of the image and can be any acceptable name; this needs to immediately follow the -t parameter
  • -f indicates that we will be providing the name of the Dockerfile containing the instructions for building the image
  • ./Dockerfile is the full path to the Dockerfile containing the instructions (in this case, it's in the current folder); this needs to immediately follow the -f parameter
  • ./ specifies that Docker build should use the current folder as needed (required by Docker build)

The container includes a copy of RStudio Server and tidyverse (see rocker/tidyverse). Alternatively, you can substitute rocker/tidyverse in the first line of Dockerfile with rocker/rstudio for a RStudio environment without the tidyverse package.

Once the docker image is built, you use the Docker run command to access the image using the suggested rocker/rstudio command:

docker run --rm -p 8787:8787 -e PASSWORD=yourpasswordhere fieldimager

Open a web browser window and enter http://localhost:8787 to access the running container. To log into the instance use the username and password of rstudio and yourpasswordhere.


If you are using anaconda and Linux

To install this package on Linux and anaconda it is necessary to use a series of commands before the recommendations

  • Install Xorg dependencies for the plot system (on conda shell)
conda install -c conda-forge xorg-libx11
  • Install the BiocManager package manager
install.packages("BiocManager")
  • Use the BiocManager to install the EBIMAGE package
BiocManager::install("EBImage")
  • If there is an error in the fftw3 library header (fftw3.h) install the dependency (on conda shell)
conda install -c eumetsat fftw3
  • If there is an error in the dependency doParallel
install.packages ("doParallel")
  • Continue installation
setwd("~/FIELDimageR-master.zip") # ~ is the path from where you saved the file.zip
unzip("FIELDimageR-master.zip") 
file.rename("FIELDimageR-master", "FIELDimageR") 
system("R CMD build FIELDimageR") #only system works on linux
install.packages("FIELDimageR_0.3.2.tar.gz", repos = NULL, type="source") # Make sure to use the right version (e.g. 0.3.2)

Menu


Using R/FIELDimageR

1. First steps

Taking the first step:

library(FIELDimageR)
library(raster)

Menu


2. Selecting the targeted field from the original image

It is necessary to first reduce the image/mosaic size around the field boundaries for faster image analysis. Function to use: fieldCrop. The following example uses an image available to download here: EX1_RGB.tif.

EX1 <- stack("EX1_RGB.tif")
plotRGB(EX1, r = 1, g = 2, b = 3)


EX1.Crop <- fieldCrop(mosaic = EX1) # For heavy images (large, high resolution, etc.) please use: fast.plot=T

Menu


3. Rotating the image

To build the plot shape file first we need to make sure that the image base line (dashed in red) has a correct straight position (vertical or horizontal). If not, it is necessary to find the right-angle theta to rotate the field, fieldRotate allows you to click directly on the image and select two points on where you want to base your field and return the theta value to finally rotate the image.

# Codeline when you don't know the rotation angle "Theta":
EX1.Rotated <- fieldRotate(mosaic = EX1.Crop, clockwise = F, h=F) # h=horizontal

# Codeline when you know the rotation angle "Theta" (theta = 2.3):
EX1.Rotated <- fieldRotate(mosaic = EX1.Crop, theta = 2.3)

# Codeline with "extentGIS=TRUE" to fit back the shapefile to the original image GIS. More information at section "5. Building the plot shape file":
EX1.Rotated<-fieldRotate(mosaic = EX1.Crop, theta = 2.3, extentGIS=TRUE)

Menu


4. Removing soil using vegetation indices

The presence of soil can introduce bias in the data extracted from the image. Therefore, removing soil from the image is one of the most important steps for image analysis in agricultural science. Function to use: fieldMask

EX1.RemSoil <- fieldMask(mosaic = EX1.Rotated, Red = 1, Green = 2, Blue = 3, index = "HUE")

Menu


5. Building the plot shape file

Once the field has reached a correct straight position, the plot shape file can be drawn by selecting at least four points at the corners of the experiment. The number of columns and rows must be informed. At this point the experimental borders can be eliminated, in the example bellow the borders were removed in all the sides. Function to use: fieldShape

EX1.Shape<-fieldShape(mosaic = EX1.RemSoil,ncols = 14, nrows = 9)


Attention: The plots are identified in ascending order from left to right and top to bottom being evenly spaced and distributed inside the selected area independent of alleys.



One matrix can be used to identify the plots position according to the image above. The function fieldMap can be used to specify the plot ID automatic or any other matrix (manually built) also can be used. For instance, the new column PlotName will be the new identification. You can download an external table example here: DataTable.csv.

### Field map identification (name for each Plot). 'fieldPlot' argument can be a number or name.

DataTable<-read.csv("DataTable.csv",header = T)  
fieldMap<-fieldMap(fieldPlot=DataTable$Plot, fieldColumn=DataTable$Row, fieldRow=DataTable$Range, decreasing=T)
fieldMap

# The new column PlotName is identifying the plots:
EX1.Shape<-fieldShape(mosaic = EX1.RemSoil, ncols = 14, nrows = 9, fieldMap = fieldMap)


### Joing all information in one "fieldShape" file:

EX1.Shape<-fieldShape(mosaic = EX1.RemSoil, ncols = 14, nrows = 9, fieldMap = fieldMap, 
                      fieldData = DataTable, ID = "Plot")
                      
# The new column PlotName is identifying the plots:                      
EX1.Shape$fieldShape@data                      


### Different plot dimensions using "fieldShape":

# ncols = 14 and nrows = 9
EX1.Shape.1Line<-fieldShape(mosaic = EX1.RemSoil, ncols = 14, nrows = 9)

# ncols = 7 and nrows = 9
EX1.Shape.2lines<-fieldShape(mosaic = EX1.RemSoil, ncols = 7, nrows = 9)

# ncols = 7 and nrows = 3
EX1.Shape.6lines<-fieldShape(mosaic = EX1.RemSoil, ncols = 7, nrows = 3)                     


Important: Code showing how to make ShapeFile using original GIS

Example 01: Using the rotation angle (theta=2.3) from step 3 (fieldRotate) to fit the "fieldShape" file back to the original image GIS (fieldShapeGIS):

### Rotation angle "theta=2.3" from fieldRotate():

EX1.Shape<-fieldShape(mosaic = EX1.RemSoil, ncols = 14, nrows = 9, fieldMap = fieldMap, 
                      fieldData = DataTable, ID = "Plot", theta = 2.3)
                      
plotRGB(EX1.RemSoil$newMosaic)
plot(EX1.Shape$fieldShape,add=T)

plotRGB(EX1)
plot(EX1.Shape$fieldShapeGIS,add=T) 


Example 02: Comparing the outputs $fieldShape (straight) with $fieldShapeGIS (theta = -60):



Menu


6. Building vegetation indices

A general number of indices are implemented in FIELDimageR using the function fieldIndex. Also, you can build your own index using the parameter myIndex.



# Calculating myIndex = "(Red-Blue)/Green" (not avaliable at 'FIELDimageR')

EX1.Indices<- fieldIndex(mosaic = EX1.RemSoil$newMosaic, Red = 1, Green = 2, Blue = 3, 
                          index = c("NGRDI","BGI"), 
                          myIndex = c("(Red-Blue)/Green"))
                          
# More than one myIndex code: myIndex = c("myIndex1","myIndex2","myIndex3")    

EX1.Indices.myIndex<- fieldIndex(mosaic = EX1.RemSoil$newMosaic, Red = 1, Green = 2, Blue = 3, 
                          index = c("NGRDI","BGI"), 
                          myIndex = c("(Red-Blue)/Green","Red/Green","Blue/Green"))
                          


Sugestion: This function could also be used to build an index to remove soil or weeds. First it is necessary to identify the threshold to differentiate soil from the plant material. At the example below (B), all values above 0.7 were considered as soil and further removed using fieldMask (C & D).

EX1.Indices.BGI<- fieldIndex(mosaic = EX1.Rotated, index = c("BGI"))

dev.off()
hist(EX1.Indices.BGI$BGI) # Image segmentation start from 0.7 (soil and plants)

EX1.BGI<- fieldMask(mosaic = EX1.Rotated, Red = 1, Green = 2, Blue = 3, 
                   index = "BGI", cropValue = 0.7, cropAbove = T) 

#Check if: cropValue=0.8 or cropValue=0.6 works better.
                                            

Menu


7. Counting the number of objects (e.g. plants, seeds, etc)

FIELDimageR can be used to evaluate stand count during early stages. A good weed control practice should be performed to avoid misidentification inside the plot. The mask output from fieldMask and the fieldshape output from fieldShape must be used. Function to use: fieldCount. The parameter n.core is used to accelerate the counting (parallel).

EX1.SC<-fieldCount(mosaic = EX1.RemSoil$mask, fieldShape = EX1.Shape$fieldShape, cex=0.4, col="blue")
EX1.SC$fieldCount

### Parallel (n.core = 3)
EX1.SC<-fieldCount(mosaic = EX1.RemSoil$mask, fieldShape = EX1.Shape$fieldShape, n.core = 3, cex=0.4, col="blue")
EX1.SC$fieldCount


To refine stand count, we can further eliminate weeds (small plants) or outlying branches from the output using the parameter min Size. The following example uses an image available to download here:EX_StandCount.tif

# Uploading file
EX.SC<-stack("EX_StandCount.tif")
plotRGB(EX.SC, r = 1, g = 2, b = 3)

# Removing the soil
EX.SC.RemSoil<- fieldMask(mosaic = EX.SC, Red = 1, Green = 2, Blue = 3, index = "HUE")

# Building the plot shapefile (ncols = 1 and nrows = 7)
EX.SC.Shape<-fieldShape(mosaic = EX.SC.RemSoil,ncols = 1, nrows = 7)


### When all shapes are counted: minSize = 0.00

EX1.SC<-fieldCount(mosaic = EX.SC.RemSoil$mask, 
                   fieldShape = EX.SC.Shape$fieldShape,
                   minSize = 0.00)
                   
EX1.SC$objectSel[[4]] # Identifies 14 points, but point 6 and 9 are small artifacts
EX1.SC$objectReject[[4]] # No shape rejected because minSize = 0.00


### When all shapes with size greater than 0.04% of plot area are counted: minSize = 0.04

EX1.SC<-fieldCount(mosaic = EX.SC.RemSoil$mask, 
                   fieldShape = EX.SC.Shape$fieldShape,
                   minSize = 0.04)

EX1.SC$objectSel[[4]] # Identifies 12 points
EX1.SC$objectReject[[4]] # Shows 2 artifacts that were rejected (6 and 9 from previous example)


fieldCount also can be used to count other objects (e.g. seed, pollen, etc). The example below FIELDimageR pipeline was used to count seeds in a corn ear.



fieldMask with index BIM (Brightness Index Modified) was used to identify pollen and fieldCount was used to count total and germinated pollens per sample. Download EX_Pollen.jpeg


# Uploading image
EX.P<-stack("EX_Pollen.jpeg")

# Reducing image resolution (fast analysis)
EX.P<-aggregate(EX.P,fact=4) 
plotRGB(EX.P, r = 1, g = 2, b = 3)

# Shapefile using the entire image (extent = T)
EX.P.shapeFile<-fieldPolygon(EX.P,extent = T)

# Using index "BIM" to remove background (above 19)
EX.P.R1<- fieldMask(mosaic = EX.P,index = "BIM", cropValue = 19, cropAbove = T)
plotRGB(EX.P.R1$newMosaic)

# Counting all pollens above 0.01 size (all sample)
EX.P.Total<-fieldCount(mosaic = EX.P.R1$mask, fieldShape = EX.P.shapeFile$fieldShape, minSize = 0.01) 

# Using index "BIM" to identify germinated pollen grain (removing values above 16)
EX.P.R2<- fieldMask(mosaic = EX.P, index = "BIM", cropValue = 16, cropAbove = T)
plotRGB(EX.P.R2$newMosaic)

# Counting all germinated pollen above 0.005 
EX.P.<-fieldCount(mosaic = EX.P.R2$mask, fieldShape = EX.P.shapeFile$fieldShape, minSize = 0.005)

Menu


8. Evaluating the object area percentage (e.g. canopy)

FIELDimageR can also be used to evaluate the canopy percentage per plot. The mask output from fieldMask and the fieldshape output from fieldShape must be used. Function to use: fieldArea. The parameter n.core is used to accelerate the canopy extraction (parallel).

EX1.Canopy<-fieldArea(mosaic = EX1.RemSoil$mask, fieldShape = EX1.Shape$fieldShape)
EX1.Canopy$areaPorcent

### Parallel (n.core = 3)
EX1.Canopy<-fieldArea(mosaic = EX1.RemSoil$mask, fieldShape = EX1.Shape$fieldShape, n.core = 3)
EX1.Canopy$areaPorcent


fieldArea also can be associated with the function fieldMask to evaluate the proportion of seed colors in Glass Gems Maize. An important step is to choose the right contrasting background to differentiate samples. The same approach can be used to evaluate the percentage of disease/pests’ damage, land degradation, deforestation, etc.


Menu


9. Extracting data from field images

The function extract from raster is adapted for agricultural field experiments through function fieldInfo. The parameter n.core is used to accelerate the plot extraction (parallel).

EX1.Info<- fieldInfo(mosaic = EX1.Indices,fieldShape = EX1.Shape$fieldShape)
EX1.Info$fieldShape@data

### Parallel (n.core = 3)
EX1.Info<- fieldInfo(mosaic = EX1.Indices,fieldShape = EX1.Shape$fieldShape, n.core = 3)
EX1.Info$fieldShape@data

Menu


10. Estimating plant height

The plant height can be estimated by calculating the Canopy Height Model (CHM). This model uses the difference between the Digital Surface Model (DSM) from the soil base (before there is any sproute, Download EX_DSM0.tif) and the DSM file from the vegetative growth (once plants are grown, Download EX_DSM1.tif). To calculate the plant height, first we used a previously generated mask from step 4 to remove the soil, and the output from fieldshape in step 5 to assign data to each plot. The user can extract information using the basic R functions mean, max, min, and quantile as a parameter in function fieldInfo.

# Uploading files from soil base (EX_DSM0.tif) and vegetative growth (EX_DSM1.tif):
DSM0 <- stack("EX_DSM0.tif")
DSM1 <- stack("EX_DSM1.tif")

# Cropping the image using the previous shape from step 2:
DSM0.C <- fieldCrop(mosaic = DSM0,fieldShape = EX1.Crop)
DSM1.C <- fieldCrop(mosaic = DSM1,fieldShape = EX1.Crop)

# Canopy Height Model (CHM):
DSM0.R <- resample(DSM0.C, DSM1.C)
CHM <- DSM1.C-DSM0.R

# Rotating the image using the same theta from step 3:
CHM.R<-fieldRotate(CHM, theta = 2.3)

# Removing the soil using mask from step 4:
CHM.S <- fieldMask(CHM.R, mask = EX1.RemSoil$mask)

# Extracting the estimate plant height average (EPH):
EPH <- fieldInfo(CHM.S$newMosaic, fieldShape = EX1.Shape$fieldShape, fun = "mean")
EPH$plotValue

# Extracting the estimate plant height at 10% and 90% of quantile:
probs = c(0.1,0.9)
EPH.Extract<-extract(x = CHM.S$newMosaic, y = EX1.Shape$fieldShape)
EPH.10.90<-do.call(rbind,lapply(EPH.Extract, quantile, probs = probs, na.rm=TRUE))
EPH.10.90

# Data:
EPH.DataTotal<-data.frame(EPH$fieldShape@data,EPH.10.90)
colnames(EPH.DataTotal)[c((dim(EPH.DataTotal)[2]-length(probs)):c(dim(EPH.DataTotal)[2]))]<-c("EPH_Mean",paste("EPH_",probs*100,"%",sep=""))
EPH.DataTotal

Menu


11. Distance between plants, objects length, and removing objects (plot, cloud, weed, etc.)

The function fieldObject can be used to take relative measurement from objects (e.g., area, "x" distance, "y" distance, number, extent, etc.) in the entire mosaic or per plot using the fieldShape file. Download example here: EX_Obj.jpg.

# Uploading file (EX_Obj.tif)
EX.Obj <- stack("EX_Obj.jpg")
plotRGB(EX.Obj)
EX.Obj <- aggregate(EX.Obj,4)
EX.shapeFile<-fieldPolygon(EX.Obj,extent = T)

# Removing the background
EX.Obj.M<- fieldMask(mosaic = EX.Obj, index = "BGI",cropValue = 0.7,cropAbove = T)
dev.off()

# Taking measurements (Remove artifacts by changing the parameter *minArea* and observing the values on EX.Obj.D$Dimension$area)
EX.Obj.D<-fieldObject(mosaic = EX.Obj.M$mask, watershed = T, minArea = 0.01)

# Measurement Output:
EX.Obj.D$numObjects
EX.Obj.D$Dimension
plotRGB(EX.Obj)
plot(EX.shapeFile$fieldShape, add=T)
plot(EX.Obj.D$Objects, add=T, border="red")
plot(EX.Obj.D$Polygons, add=T, border="blue")
plot(EX.Obj.D$single.obj[[1]], add=T, col="yellow")
lines(EX.Obj.D$x.position[[1]], col="red", lty=2)
lines(EX.Obj.D$y.position[[1]], col="red", lty=2)
EX.Obj.I<- fieldIndex(mosaic = EX.Obj,index = c("SI","BGI","BI"))
EX.Obj.Data<-fieldInfo(mosaic = EX.Obj.I[[c("SI","BGI","BI")]], fieldShape = EX.Obj.D$Objects, projection = F)
EX.Obj.Data$fieldShape@data

# Perimeter:
# install.packages("spatialEco")
library(spatialEco)
perimeter<-polyPerimeter(EX.Obj.D$Objects)
box<-polyPerimeter(EX.Obj.D$Polygons)
Data.Obj<-cbind(EX.Obj.Data$fieldShape@data,EX.Obj.D$Dimension,perimeter=perimeter,box=box)
Data.Obj


The function fieldCrop can be used to remove objects from the field image. For instance, the parameter remove=TRUE and nPoint should be used to select the object boundaries to be removed. Download EX_RemObj.tif).

# Uploading file (EX_RemObj.tif)
EX.RemObj <- stack("EX_RemObj.tif")

# Selecting the object boundaries to be removed (nPoint = 10)
EX.RemObj.Crop <- fieldCrop(mosaic = EX.RemObj, remove = T, nPoint = 10) # Selecting the plant in plot 13

# Removing the soil
EX.RemObj.RemSoil<- fieldMask(mosaic = EX.RemObj.Crop,index = "HUE")

# Building the plot shapefile (ncols = 8 and nrows = 4)
EX.RemObj.Shape<-fieldShape(mosaic = EX.RemObj.RemSoil,ncols = 8, nrows = 4)

# Building indice (NGRDI)
EX.RemObj.Indices<- fieldIndex(mosaic = EX.RemObj.RemSoil$newMosaic,index = c("NGRDI"))

# Extracting data (NGRDI)
EX.RemObj.Info<- fieldInfo(mosaic = EX.RemObj.Indices$NGRDI,
                      fieldShape = EX.RemObj.Shape$fieldShape,
                      n.core = 3)
                      
# Comparing plots values (the plant in plot 13 was removed and its value must be lower than plot 12 and 14)                      
EX.RemObj.Info$plotValue[c(12,13,14),]


The function fieldDraw can be used to draw lines or polygons in the field image. This function allows to extract information of specific positions in the field (x, y, value). Also, this function can be used to evaluate distances between objects (for example: distance between plants in a line) or either objects length (for example: seed length, threes diameter, etc.). Let's use the image above to evaluate the distance between potato plots and later to extract NGRDI values from a line with soil and vegetation to observe the profile in a distance plot.

# Uploading file (EX_RemObj.tif)
EX.Dist <- stack("EX_RemObj.tif")

# vegetation indices
EX.Dist.Ind <- fieldIndex(mosaic = EX.Dist,index = c("NGRDI"))

# Removing the soil
EX.Dist.RemSoil <- fieldMask(mosaic = EX.Dist.Ind)

# Evaluating distance between plants. Remember to press ESC when finished to draw the line.
EX.Dist.Draw <- fieldDraw(mosaic = EX.Dist.RemSoil$mask, 
                          dist = T,
                          value = 1, # Use the number to identify the object to be measured (1 for space and 0 for plants)
                          distSel = 0.4) 
EX.Dist.Draw$drawDist # Distance between plants
                          
# Making plots                         
plot(EX.Dist.Ind$NGRDI)
points(EX.Dist.Draw$drawData$x,EX.Dist.Draw$drawData$y, col="red",pch=16,cex=0.7)
points(EX.Dist.Draw$drawSegments$x,EX.Dist.Draw$drawSegments$y, col="blue",pch=16,cex=0.7)
lines(EX.Dist.Draw$drawDist[1,c("x1","x2")],EX.Dist.Draw$drawDist[1,c("y1","y2")], col="green",lwd=5)

# Evaluating an specific layer profile (e.g. NGRDI)
EX.Dist.Draw.2 <- fieldDraw(mosaic = EX.Dist.Ind,
                            ndraw = 4, # Making 4 lines (press ESC to conclude each line)
                            lwd = 5)
EX.Data<-EX.Dist.Draw.2$Draw1$drawData
dev.off()
plot(x = EX.Data$x, y = EX.Data$NGRDI, type="l", col="red",lwd=2,xlab="Distance (m)", ylab="NGRDI")
abline(h=0.0,col="blue", lty=2, lwd=3)

# Making polygons and extracting data per cell
EX.Dist.Draw.3 <- fieldDraw(mosaic = EX.Dist.Ind,
                            line = F, # Making 2 polygons (press ESC to conclude each polygon)
                            ndraw = 2,
                            lwd = 5)
plotRGB(EX.Dist.RemSoil$newMosaic)
plot(EX.Dist.Draw.3$Draw1$drawObject, col="red",add=T)

Menu


12. Resolution and computing time

The influence of image resolution was evaluated at different steps of the FIELDimageR pipeline. For this propose, the resolution of image EX1_RGB_HighResolution.tif Download was reduced using the function raster::aggregate in order to simulate different flown altitudes Above Ground Surface (AGS). The parameter fact was used to modify the original image resolution (0.4x0.4 cm with 15m AGS) to: first, fact=2 to reduce the original image to 0.8x0.8 cm (simulating 30m AGS), and fact=4 to reduce the original image to 1.6x1.6 (simulating 60m AGS). The steps (i) cropping image, (ii) removing soil, (iii) rotating image, (iv) building vegetation index (BGI), and (v) getting information were evaluated using the function system.time output elapsed (R base).

### Image and resolution decrease 

RES_1<-stack("EX1_RGB_HighResolution.tif")
RES_2<-aggregate(RES_1, fact=2)
RES_4<-aggregate(RES_1, fact=4)

res(RES_1)
res(RES_2)
res(RES_4)

par(mfrow=c(1,3))
plotRGB(RES_1)
plotRGB(RES_2)
plotRGB(RES_4)

### Crooping 

system.time({RES_1_C <- fieldCrop(mosaic = RES_1,fieldShape = EX1.Crop, plot = T)})
system.time({RES_2_C <- fieldCrop(mosaic = RES_2,fieldShape = EX1.Crop, plot = T)})
system.time({RES_4_C <- fieldCrop(mosaic = RES_4,fieldShape = EX1.Crop, plot = T)})

### Rotating 
  
system.time({RES_1_R <- fieldRotate(RES_1_C,theta = 2.3, plot = T)}) 
system.time({RES_2_R <- fieldRotate(RES_2_C,theta = 2.3, plot = T)})
system.time({RES_4_R <- fieldRotate(RES_4_C,theta = 2.3, plot = T)})
  
### Removing Soil 

system.time({RES_1_S <- fieldMask(RES_1_R,index="HUE")})
system.time({RES_2_S <- fieldMask(RES_2_R,index="HUE")})
system.time({RES_4_S <- fieldMask(RES_4_R,index="HUE")})

### Indices
  
system.time({RES_1_I <- fieldIndex(RES_1_S$newMosaic,index=c("BGI"))})
system.time({RES_2_I <- fieldIndex(RES_2_S$newMosaic,index=c("BGI"))})
system.time({RES_4_I <- fieldIndex(RES_4_S$newMosaic,index=c("BGI"))})
  
### Get Information (1 Band)
  
system.time({RES_1_Info <- fieldInfo(RES_1_I$BGI,fieldShape = EX1.Shape$fieldShape,n.core = 3)})
system.time({RES_2_Info <- fieldInfo(RES_2_I$BGI,fieldShape = EX1.Shape$fieldShape,n.core = 3)})
system.time({RES_4_Info <- fieldInfo(RES_4_I$BGI,fieldShape = EX1.Shape$fieldShape,n.core = 3)})
  
### Get Information (3 Bands)
  
system.time({RES_1_Info2 <- fieldInfo(RES_1_I[[c(1,2,3)]],fieldShape = EX1.Shape$fieldShape,n.core = 3)})
system.time({RES_2_Info2 <- fieldInfo(RES_2_I[[c(1,2,3)]],fieldShape = EX1.Shape$fieldShape,n.core = 3)})
system.time({RES_4_Info2 <- fieldInfo(RES_4_I[[c(1,2,3)]],fieldShape = EX1.Shape$fieldShape,n.core = 3)})

### Correlation

DataBGI <- data.frame(R1=RES_1_Info$plotValue$BGI,
                    R2=RES_2_Info$plotValue$BGI,
                    R4=RES_4_Info$plotValue$BGI)
DataBlue <- data.frame(R1=RES_1_Info2$plotValue$Blue,
                       R2=RES_2_Info2$plotValue$Blue,
                       R4=RES_4_Info2$plotValue$Blue)
DataGreen <- data.frame(R1=RES_1_Info2$plotValue$Green,
                       R2=RES_2_Info2$plotValue$Green,
                       R4=RES_4_Info2$plotValue$Green)
DataRed <- data.frame(R1=RES_1_Info2$plotValue$Red,
                       R2=RES_2_Info2$plotValue$Red,
                       R4=RES_4_Info2$plotValue$Red)
cor(DataBGI)
cor(DataBlue)
cor(DataGreen)
cor(DataRed)

The time to run one function using the image with pixel size of 0.4x0.4 cm can be 10 (fieldInfo) to 70 times (fieldIndex) slower than the image with pixel size of 1.6x1.6 cm (Table 1). The computing time to extract BGI index (one layer) with 0.4x0.4 cm was ~23 min whereas only ~7 min with the 0.8x0.8 cm image, and ~2 min using the 1.6x1.6 cm image. the time to extract the RGB information (three layers) was ~2.3 min for the 1.6x1.6 cm image and ~66 min for the 0.4x0.4 cm image. It is important to highlight that the resolution did not affect the plots mean, it has a correlation >99% between 0.4x0.4 cm and 1.6x1.6 (Table 2). High resolution images showed to require higher computational performance, memory, and storage space. We experienced that during the image collection in the field a low altitudes flight needs more batteries and a much greater number of pictures, and consequently longer preprocessing images steps to build ortho-mosaics.


Menu


13. Crop growth cycle

The same rotation theta from step 3, mask from step 4, and plot shape file from step 5, can be used to evaluate mosaics from other stages in the crop growth cycle. Here you can download specific images from flowering and senecense stages in potatoes. (Flowering: EX2_RGB.tif and Senescence: EX3_RGB.tif)



# Uploading Flowering (EX2_RGB.tif) and Senescence (EX3_RGB.tif) files:
EX2 <- stack("EX2_RGB.tif")
EX3 <- stack("EX3_RGB.tif")

# Cropping the image using the previous shape from step 2:

EX2.Crop <- fieldCrop(mosaic = EX2,fieldShape = EX1.Crop, plot = T)
EX3.Crop <- fieldCrop(mosaic = EX3,fieldShape = EX1.Crop, plot = T)

# Rotating the image using the same theta from step 3:

EX2.Rotated<-fieldRotate(EX2.Crop,theta = 2.3, plot = T)
EX3.Rotated<-fieldRotate(EX3.Crop,theta = 2.3, plot = T)

# Removing the soil using index and mask from step 4:

EX2.RemSoil<-fieldMask(EX2.Rotated,index="HUE",cropValue=0,cropAbove=T,plot=T)
EX3.RS<-fieldMask(EX3.Rotated,index="HUE",cropValue=0,cropAbove=T,plot=T) # Removing soil at senescence stage
EX3.RemSoil<-fieldMask(EX3.RS$newMosaic,mask = EX2.RemSoil$mask ,cropValue=0,cropAbove=T,plot=T) # Removing weeds from senescence stage with flowering mask 

# Building indices

EX2.Indices <- fieldIndex(EX2.RemSoil$newMosaic,Red=1,Green=2,Blue=3,
                 index = c("NGRDI","BGI"), myIndex = c("(Red-Blue)/Green"))
EX3.Indices <- fieldIndex(EX3.RemSoil$newMosaic,Red=1,Green=2,Blue=3,
                 index = c("NGRDI","BGI"), myIndex = c("(Red-Blue)/Green"))

# Extracting data using the same fieldShape file from step 5:

EX2.Info<- fieldInfo(mosaic = EX2.Indices$myIndex,fieldShape = EX1.Shape$fieldShape,n.core = 3)
EX3.Info<- fieldInfo(mosaic = EX3.Indices$myIndex,fieldShape = EX1.Shape$fieldShape,n.core = 3)

Data.Cycle<-data.frame(EX1=EX1.Info$plotValue$myIndex,
      EX2=EX2.Info$plotValue$myIndex,
      EX3=EX3.Info$plotValue$myIndex)

Data.Cycle




Menu


14. Multispectral and Hyperspectral images

FIELDimageR can be used to analyze multispectral and hyperspectral images. The same rotation theta, mask, and plot shape file used to analyze RGB mosaic above can be used to analyze multispectral or hyperspectral mosaic from the same field.


Multispectral: You can dowload a multispectral example here: EX1_5Band.tif


#####################
### Multispectral ###
#####################

# Uploading multispectral mosaic:
EX1.5b <- stack("EX1_5Band.tif")

# Cropping the image using the previous shape from step 2:
EX1.5b.Crop <- fieldCrop(mosaic = EX1.5b,fieldShape = EX1.Crop, plot = T)

# Rotating the image using the same theta from step 3:
EX1.5b.Rotated<-fieldRotate(EX1.5b.Crop,theta = 2.3, plot = T)

# Removing the soil using index and mask from step 4:
EX1.5b.RemSoil<-fieldMask(EX1.5b.Rotated,Red=1,Green=2,Blue=3,index="HUE",cropValue=0,cropAbove=T,plot=T)

# Building indices (NDVI and NDRE)
EX1.5b.Indices <- fieldIndex(EX1.5b.RemSoil$newMosaic,Red=1,Green=2,Blue=3,RedEdge=4,NIR=5,
                 index = c("NDVI","NDRE"))

# Extracting data using the same fieldShape file from step 5:
EX1.5b.Info<- fieldInfo(mosaic = EX1.5b.Indices$NDVI,fieldShape = EX1.Shape$fieldShape,n.core = 3)

Hyperspectral: in the following example you should download the hyperspectral tif file (EX_HYP.tif), the 474 wavelength names (namesHYP.csv), and the field map data (DataHYP.csv).


#####################
### Hyperspectral ###
#####################

# Uploading hyperspectral file with 474 bands (EX_HYP.tif)
EX.HYP<-stack("EX_HYP.tif")

# Wavelengths (namesHYP.csv)
NamesHYP<-as.character(read.csv("namesHYP.csv")$NameHYP)

# Building RGB image 
R<-EX.HYP[[78]] # 651nm (Red)
G<-EX.HYP[[46]] # 549nm (Green)
B<-EX.HYP[[15]] # 450nm (Blue)
RGB<-stack(c(R,G,B))
plotRGB(RGB, stretch="lin")

# Removing soil using RGB (index NGRDI)
RGB.S<-fieldMask(RGB,index="NGRDI",cropValue = 0.0, cropAbove = F)

# Data frame with field information to make the Map
Data<-read.csv("DataHYP.csv")
Map<-fieldMap(fieldPlot = as.character(Data$Plot),fieldRow = as.character(Data$Range),fieldColumn = as.character(Data$Row),decreasing = T)

# Building plot shapefile using RGB as base
plotFile<-fieldShape(RGB.S,ncols = 14, nrows = 14, fieldMap = Map,fieldData = Data, ID = "Plot")

# Removing soil using the RGB mask
EX.HYP.S<-fieldMask(EX.HYP,mask = RGB.S$mask, plot = F)

# Extracting data (474 bands)
EX.HYP.I<-fieldInfo(EX.HYP.S$newMosaic,fieldShape = plotFile$fieldShape,n.core = 3)

# Saving the new csv with hyperspectral information per plot
DataHYP<-EX.HYP.I$fieldShape@data
colnames(DataHYP)<-c(colnames(DataHYP)[1:9],NamesHYP)
write.csv(DataHYP,"DataHypNew.csv",col.names = T,row.names = F)

###############
### Graphic ###
###############

dev.off()
DataHYP1<-EX.HYP.I$plotValue[,-1]

plot(x=as.numeric(NamesHYP),y=as.numeric(DataHYP1[1,]),type = "l",xlab = "Wavelength (nm)",ylab = "Reflectance", col="black",lwd=2,cex.lab=1.2)
for(i in 2:dim(DataHYP1)[2]){
  lines(x=as.numeric(NamesHYP),y=as.numeric(DataHYP1[i,]),type = "l",col=i,lwd=2)
}
abline(v=445,col="blue",lwd=2,lty=2)
abline(v=545,col="green",lwd=2,lty=2)
abline(v=650,col="red",lwd=2,lty=2)
abline(v=720,col="red",lwd=2,lty=3)
abline(v=840,col="red",lwd=2,lty=4)
legend(list(x = 2000,y = 0.5),c("Blue (445nm)","Green (545nm)","Red (650nm)","RedEdge (720nm)","NIR (840nm)"),
       col =c("blue","green","red","red","red"),lty=c(2,2,2,3,4),box.lty=0)

Menu


15. Building shapefile with polygons (field blocks, pest damage, soil differences, etc)

If your field area does not have a pattern to draw plots using the function fieldShape you can draw different polygons using the function fieldPolygon. To make the fieldshape file the number of polygons must be informed. For instance, for each polygon, you should select at least four points at the polygon boundaries area. This function is recommended to make shapefile to extract data from specific field blocks, pest damage area, soil differences, etc. If extent=TRUE the whole image area will be the shapefile (used to analyze multiple images for example to evaluate seeds, ears, leaves, diseases, etc.). Function to use: fieldPolygon. The following example uses an image available to download here: EX_polygonShape.tif.

# Uploading file (EX_polygonShape.tif)
EX.polygon<-stack("EX_polygonShape.tif")
plotRGB(EX.polygon, r = 1, g = 2, b = 3)

# Removing soil
EX.polygon.RemSoil<- fieldMask(mosaic = EX.polygon)

# Data frame with polygons information
polygonData<-data.frame(ID=c("Polygon1","Polygon2","Polygon3"),
                        FlowerColor=c("white","white","white"),
                        FlowerPercent=c(20,40,50),
                        LeafColor=c("dark","light","dark"))
polygonData

# Building plot shapefile with 3 polygons (select 4 points around the polygon area)
EX.polygon.Shape<-fieldPolygon(mosaic = EX.polygon.RemSoil,
                               nPolygon = 3,nPoint = 4,ID = "ID",
                               polygonData = polygonData,cropPolygon = T,
                               polygonID = c("Polygon1","Polygon2","Polygon3"))
plotRGB(EX.polygon.Shape$cropField)

# Building indice (NGRDI and BGI)
EX.polygon.Indices<- fieldIndex(mosaic = EX.polygon.RemSoil$newMosaic, Red = 1, Green = 2, Blue = 3, 
                             index = c("NGRDI","BGI"))

# Extracting data (NGRDI and BGI)
EX.polygon.Info<- fieldInfo(mosaic = EX.polygon.Indices[[c("NGRDI","BGI")]],
                   fieldShape = EX.polygon.Shape$fieldShape, n.core = 3)
EX.polygon.Info$fieldShape@data

# Making graphics (BGI)
fieldPlot(fieldShape=EX.polygon.Info$fieldShape,
          fieldAttribute="BGI",
          mosaic=EX.polygon, color=c("red","blue"), alpha = 0.5)

Menu


16. Making plots

Graphic visualization of trait values for each plot using the fieldShape file and the Mosaic of your preference. Function to use: fieldPlot.

### Interpolating colors: c("white","black")
fieldPlot(fieldShape=EX1.Info$fieldShape,fieldAttribute="Yield", mosaic=EX1.Indices, color=c("white","black"), alpha = 0.5)

### Interpolating colors: c("red","blue")
fieldPlot(fieldShape=EX1.Info$fieldShape,fieldAttribute="myIndex", mosaic=EX1.Indices, color=c("red","blue"), alpha = 0.5)

Menu


17. Saving output files

### Images (single and multi layers)
writeRaster(EX1.Indices, filename="EX1.Indices.tif", options="INTERLEAVE=BAND", overwrite=TRUE)
# EX1.Indices.2 <- stack("EX1.Indices.tif") # Reading the saved image.

### FieldShape file
library(rgdal)
writeOGR(EX1.Info$fieldShape, ".", "EX1.fieldShape", driver="ESRI Shapefile")
# EX1.fieldShape.2 <- terra::vect("EX1.fieldShape.shp") # Reading the saved shapefile option 01.
# EX1.fieldShape.2 <- readOGR("EX1.fieldShape.shp") # Reading the saved shapefile option 02.

### CSV file (table)
write.csv(EX1.Info$fieldShape@data,file = "EX1.Info.csv",col.names = T,row.names = F)
# Data.EX1.Info<-read.csv("EX1.Info.csv",header = T,check.names = F) # Reading the saved data table.

Menu


Orthomosaic using the open source software OpenDroneMap

Image stitching from remote sensing phenotyping platforms (sensors attached to aerial or ground vehicles) in one orthophoto.

  1. Follow the OpenDroneMap’s documentation according to your operating system (Windows, macOS or Linux) to install WebODM.

  2. Start WebODM and +Add Project to upload your pictures (.tif or .jpg). Attached is one example of RGB images from experimental trials of UW-Madison Potato Breeding and Genetics Laboratory during the flowering time at Hancock Agricultural Research Station. Flight altitude was 60 m above ground, flight speed was 24 km/h, and image overlap was 75%. Donwload pictures here.

  3. After the running process 'completed', download the odm_orthophoto.tif and dsm.tif to upload in R. Then follow the pipeline of FIELDimageR. Donwload the final *odm_orthophoto.tif*.


# Uploading file (odm_orthophoto.tif):
EX.ODM<-stack("odm_orthophoto.tif")
plotRGB(EX.ODM, r = 1, g = 2, b = 3)

# Cropping the image to select only one trial (Selecting the same trial as EX.2 from step.13):
EX.ODM.Crop <- fieldCrop(mosaic = EX.ODM)

# Rotating the image using the same theta from step 3:
EX.ODM.Rotated<-fieldRotate(EX.ODM.Crop,theta = 2.3)

# Removing soil
EX.ODM.RemSoil<- fieldMask(mosaic = EX.ODM.Rotated)

# Building indices
EX.ODM.Indices <- fieldIndex(EX.ODM.RemSoil$newMosaic,Red=1,Green=2,Blue=3,
                 index = c("NGRDI","BGI"), myIndex = c("(Red-Blue)/Green"))

# Extracting data using the same fieldShape file from step 5:
EX.ODM.Info<- fieldInfo(mosaic = EX.ODM.Indices$myIndex,fieldShape = EX1.Shape$fieldShape,n.core = 3)

EX.ODM.Info$plotValue$myIndex

Menu


Parallel and loop to evaluate multiple images

The following code can be used to evaluate multiple images (e.g. root area, leave indices, damaged area, ears, seed, structures, etc.). The example below is evaluating disease damage in images of leaves (affected area and indices). Download the example here.


# Images names (folder directory: "./images/")
pics<-list.files("./images/")

# Vegetation indices
index<- c("BGI","VARI","SCI")

############
### Loop ###
############

system.time({ # system.time: used to compare the processing time using loop and parallel
EX.Table.Loop<-NULL
for(i in 1:length(pics)){
  EX.L1<-stack(paste("./images/",pics[i],sep = ""))
  plotRGB(EX.L1)
  EX.L.Shape<-fieldPolygon(mosaic=EX.L1, extent=T, plot=F) # extent=T (The whole image area will be the shapefile)
  EX.L2<-fieldMask(mosaic=EX.L1, index="BGI", cropValue=0.8, cropAbove=T, plot=F) # Select one index to identify leaves and remove the background
  EX.L3<-fieldMask(mosaic=EX.L2$newMosaic, index="VARI", cropValue=0.1, cropAbove=T, plot=F) # Select one index to identify demaged area in the leaves  
  EX.L4<-fieldIndex(mosaic=EX.L2$newMosaic, index=index, plot=F) # Indices
  EX.L5<-stack(EX.L3$mask, EX.L4[[index]]) # Making a new stack raster with new layers (demage area and indices)
  EX.L.Info<- fieldInfo(mosaic=EX.L5, fieldShape=EX.L.Shape$fieldShape, projection=F) # projection=F (Ignore projection. Normally used only with remote sensing images)
  plot(EX.L5,col = grey(1:100/100))
  EX.Table.Loop<-rbind(EX.Table.Loop, EX.L.Info$plotValue) # Combine information from all images in one table
}})
rownames(EX.Table.Loop)<-pics
EX.Table.Loop

################
### Parallel ###
################

# Required packages
library(parallel)
library(foreach)
library(doParallel)

# Number of cores
n.core<-detectCores()-1

# Starting parallel
cl <- makeCluster(n.core, output = "")
registerDoParallel(cl)
system.time({
EX.Table.Parallel <- foreach(i = 1:length(pics), .packages = c("raster","FIELDimageR"), 
                     .combine = rbind) %dopar% {
                       EX.L1<-stack(paste("./images/",pics[i],sep = ""))
                       EX.L.Shape<-fieldPolygon(mosaic=EX.L1, extent=T, plot=F) # extent=T (The whole image area will be the shapefile)
                       EX.L2<-fieldMask(mosaic=EX.L1, index="BGI", cropValue=0.8, cropAbove=T, plot=F) # Select one index to identify leaves and remove the background
                       EX.L3<-fieldMask(mosaic=EX.L2$newMosaic, index="VARI", cropValue=0.1, cropAbove=T, plot=F) # Select one index to identify demaged area in the leaves  
                       EX.L4<-fieldIndex(mosaic=EX.L2$newMosaic, index=index, plot=F) # Indices
                       EX.L5<-stack(EX.L3$mask, EX.L4[[index]]) # Making a new stack raster with new layers (demage area and indices)
                       EX.L.Info<- fieldInfo(mosaic=EX.L5, fieldShape=EX.L.Shape$fieldShape, projection=F) # projection=F (Ignore projection. Normally used only with remote sensing images)
                       EX.L.Info$plotValue # Combine information from all images in one table
                     }})
stopCluster(cl)
rownames(EX.Table.Parallel)<-pics
EX.Table.Parallel 

Menu


Quick tips (image analyze in R)

  1. Changing memory limits in R
# The rasterOptions() allows you to customize your R session (raster package): 
rasterOptions()
rasterOptions(chunksize = 1e+09)
rasterOptions(maxmemory = 1e+09)
  1. Reducing resolution for fast analysis
new_mosaic<-aggregate(previous_mosaic, fact=4)
  1. Removing previous files after used (more space in R memory): If you do not need one mosaic you should remove it to save memory to the next steps (e.g. the first input mosaic)
rm(previous_mosaic)
  1. Using ShapeFile from other software (e.g. QGIS)
ShapeFile <- rgdal::readOGR("Other_Software_ShapeFile.shp") # Option 01
ShapeFile <- terra::vect("Other_Software_ShapeFile.shp") # Option 02
  1. Combining ShapeFiles: sometimes it is better to split the mosaic into smaller areas to better draw the shapefile. For instance, the user can combine the split shapefiles to one for the next step as extractions
ShapeFile <- rbind(ShapeFile1, ShapeFile2, ShapeFile3, ...)
  1. External window to amplify the RStudio plotting area (It helps to visualize and click when using functions: fieldCrop, fieldRotate, fieldShape, and fieldPolygon). The default graphics device is normally "RStudioGD". To change use "windows" on Windows, "quartz" on MacOS, and "X11" on Linux.
# Example in macOS (type the following code before running FIELDimageR functions):
options(device = "quartz")

Menu


YouTube Tutorial


FIELDimageR: A tool to analyze orthomosaic images from agricultural field trials in R (Basic Pipeline)

FIELDimageR: Counting the number of plants (fieldCount)

FIELDimageR: Calculating vegetation indices (NDVI and NDRE)

FIELDimageR: Estimate plant height using the canopy height model (CHM)


FIELDimageR courses






Google Groups Forum

This discussion group provides an online source of information about the FIELDimageR package. Report a bug and ask a question at:


Developers

Help improve FIELDimageR pipeline. The easiest way to modify the package is by cloning the repository and making changes using R projects.

If you have questions, join the forum group at https://groups.google.com/forum/#!forum/fieldimager

Try to keep commits clean and simple

Submit a pull request with detailed changes and test results.

Let's work together and help more people (students, professors, farmers, etc) to have access to this knowledge. Thus, anyone anywhere can learn how to apply remote sensing in agriculture.


Licenses

The R/FIELDimageR package as a whole is distributed under GPL-2 (GNU General Public License version 2).


Citation

Matias FI, Caraza-Harter MV, Endelman JB. FIELDimageR: An R package to analyze orthomosaic images from agricultural field trials. The Plant Phenome J. 2020; https://doi.org/10.1002/ppj2.20005


Author


Acknowledgments


Menu


More Repositories

1

ODM

A command line toolkit to generate maps, point clouds, 3D models and DEMs from drone, balloon or kite images. πŸ“·
Python
4,603
star
2

WebODM

User-friendly, commercial-grade software for processing aerial imagery. πŸ›©
JavaScript
2,662
star
3

Obj2Tiles

Converts OBJ files to OGC 3D tiles by performing splitting, decimation and conversion
C#
217
star
4

NodeODM

A lightweight REST API to access aerial image processing engines such as ODM or MicMac
JavaScript
193
star
5

ODMdata

Example data for OpenDroneMap: https://OpenDroneMap.org sourced from a variety of sources
134
star
6

PyODM

A Python SDK for adding aerial image processing capabilities to your applications πŸ”Œ
Python
94
star
7

dem2mesh

Quickly generate 2.5D meshes from elevation models.
C++
84
star
8

NodeMICMAC

A Lightweight REST API to Access MICMAC Photogrammetry and SFM Engine.
JavaScript
83
star
9

ClusterODM

A NodeODM API compatible autoscalable load balancer and task tracker for easy horizontal scaling ♆
JavaScript
80
star
10

CloudODM

A command line tool to process aerial imagery in the cloud. 🌩
Go
62
star
11

LiveODM

Live DVD/USB ISO with ODM, node-ODM and WebODM pre-installed.
Shell
49
star
12

pypopsift

Python module for CUDA accelerated SIFT on GPUs
C++
32
star
13

docs

πŸŽ‰ Contribute to OpenDroneMap's documentation! Read how below! πŸŽ‰
Python
25
star
14

python-WebODM

Python client for WebODM API
Python
22
star
15

UAVArena

Drone mapping software outputs compared side by side! Which will win? βš”οΈ
JavaScript
20
star
16

odm_vagrant

Vagrant machine for using OpenDroneMap
19
star
17

posm-gcpi

Ground Control Point interface (GCPi) for OpenDroneMap
JavaScript
15
star
18

dem2points

Extract 3D points from digital elevation models
C++
14
star
19

ODMSemantic3D

An open photogrammetry dataset of classified 3D point clouds for automated semantic segmentation. CC BY-SA 4.0
Shell
12
star
20

odm_orthophoto

ODM Orthophoto Module - Rasterize Textured 3D Models to PNG
C++
10
star
21

SkyRemoval

Create sky masks to improve photogrammetric reconstruction
Python
10
star
22

odm_data_aukerman

10
star
23

FPCFilter

Fast Point Cloud Filtering
C++
10
star
24

odm-benchmarks

Benchmark data index for OpenDroneMap and WebODM
JavaScript
9
star
25

orthorectify

Orthorectify images from ODM reconstruction
C++
9
star
26

awesome-aerial-mapping

Awesome resources for learning about aerial mapping
8
star
27

airsim-generator

Generate synthetic drone photos and elevation models from Microsoft AirSim
Python
8
star
28

odm_data_zoo

7
star
29

presentations

JavaScript
7
star
30

RSCalibration

Docs and scripts to estimate a camera's rolling shutter readout time
HTML
7
star
31

oats

OpenDroneMap Automated Testing Suite
Shell
6
star
32

odm_data_langley

OpenDroneMap Langley dataset
5
star
33

opendronemap-ecs

Serverless API to get opendronemap tasks running on AWS Elastic Container Service (ECS)
JavaScript
5
star
34

WebODM-Locale

Localization files for WebODM
5
star
35

odm-start-deprecated

Tutorial / Startup doc for using OpenDroneMap
4
star
36

odm_data_bellus

4
star
37

odm_data_copr

odm_data copr dataset
3
star
38

odm_data_garfield_msp

3
star
39

odm_data_lewis

Lewis Road Riding Arena Flight
2
star
40

odm_data_caliterra

Submodule of ODM data for Caliterra dataset
2
star
41

odm_data_seneca

OpenDroneMap Seneca dataset
2
star
42

images2geojson

Convert OpenDroneMap's images.json image database to GeoJSON point collections.
JavaScript
2
star
43

odm_data_benchmark

OpenDroneMap benchmark dataset
2
star
44

WestCreekPleasantValley

Stream topography drone flight, taken with GoPro Hero 4 (3.37mm lens) on 3DR Solo
2
star
45

odm_data_helenenschacht

2
star
46

syntheticDSM

Synthetic georeferenced DSM files to verify volume calculation accuracy
2
star
47

wiki-assets

1
star
48

multispectral-docs

Resources for getting started in multispectral processing
1
star
49

opendronemap.github.io

1
star
50

odm_data_apt

Trail (sidewalk) OpenDroneMap test dataset
1
star
51

UAVArena-data

Tilesets for the UAVArena Web Application
1
star
52

WebODM-Plugins-Archive

Plugins waiting for a hero to fix them
JavaScript
1
star
53

odm_data_toledo

1
star
54

documents

The transparent bylaws, policies and rules of OpenDroneMap βš–οΈ
1
star
55

odm_data_waterbury

1
star
56

odm_data_rv_nir

1
star