Displaying 3 results from an estimated 3 matches for "250m_16_days_evi".
2017 Jun 23
0
MODISTools Help
...ious 14 days
firstobs$start.date <- dmy(firstobs$start.date)
firstobs$end.date <- dmy(firstobs$end.date)
firstobs$start.date <- firstobs[,2] - as.difftime(14, unit='days') ###time frame now spands two weeks
###define parameters
product <- "MOD13Q1"
bands <- c('250m_16_days_EVI', '250m_16_days_NDVI', '250m_16_days_VI_Quality')
pixel <- c(0,0)
###define data
period <- data.frame(lat=firstobs$lat, long=firstobs$long, start.date =firstobs$start.date, end.date = firstobs$end.date, id=firstobs$id)
###MODISSubsets
MODISSubsets(LoadDat = period, Prod...
2017 Jun 23
1
MODISTools Help
...date <- dmy(firstobs$start.date)
> firstobs$end.date <- dmy(firstobs$end.date)
> firstobs$start.date <- firstobs[,2] - as.difftime(14, unit='days') ###time frame now spands two weeks
>
> ###define parameters
> product <- "MOD13Q1"
> bands <- c('250m_16_days_EVI', '250m_16_days_NDVI', '250m_16_days_VI_Quality')
> pixel <- c(0,0)
>
> ###define data
> period <- data.frame(lat=firstobs$lat, long=firstobs$long, start.date =firstobs$start.date, end.date = firstobs$end.date, id=firstobs$id)
>
>
> ###MODISSubsets
>...
2017 Jun 22
1
MODISTools Help
1. You should always cc the list unless there is a clear reason not to.
2. You still have failed to follow the posting guide: You say you have
difficulty troubleshooting your code, but you have shown us no code.
You got an error message that seems explicit, but with neither code
nor data, I do not know whether anyone can make sense of it. In any
case, I certainly cannot.
Cheers,
Bert
Bert