Skip to content
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

bfastts Output #79

Open
smithve87 opened this issue Aug 23, 2017 · 2 comments
Open

bfastts Output #79

smithve87 opened this issue Aug 23, 2017 · 2 comments

Comments

@smithve87
Copy link

Hello,

I am trying to extract the real time-series data for an analysis separate from the model produced by bfast/bfastmonitor (basically I want to use only the real data to eliminate false positive breaks). However, I am having difficulty interpreting the time series object produced by bfastts. I subset my raster brick NDVI data by sensor and ran bfastts with an output that looks like this:

screen shot 2017-08-23 at 1 17 12 pm

I wrote the output to a .csv file and opened it in excel which looked like this:

screen shot 2017-08-23 at 1 21 15 pm

I understand the headings (Landsat scene ID) and values within the table (NDVI), but am unsure of the rows. What does the 2000.16, 2000.19, etc. indicate? Also, in the excel, are the rows supposed to be the pixels? There are about 6,000 rows, but the ncell of the raster brick is over 99,000. Also in the excel, as you scroll down (excel table attached), only certain rows will have values, which doesn't seem right since the cloud mask produces NA values, but clouds wouldn't be in the same pixels for each date. If someone could shed some light on this issue I would much appreciate it.

Best Regards,
-Vaughn
ndvi_TS.xlsx

@loicdtx
Copy link
Owner

loicdtx commented Aug 23, 2017

With the code below I'm able to produce a time-series object for each pixel of the first row of the tura dataset. Rows correspond to dates in decimal form, and each column correspond to an individual pixel.
There are a lot more NAs than in the original raster object because bfastts produces a time-series with daily observations, while the original data are irregular with at least 8 days between each observation. Days filled in between observations to produce the daily time-series are automatically set to NA.

library(bfastSpatial)
data("tura")
time <- getZ(tura)
v <- t(getValues(tura, row = 1, nrows = 1))
ts <- bfastts(v, dates = time, type = 'irregular')

@sumanjnu
Copy link

sumanjnu commented Feb 27, 2019

@loicdtx , @bendv How do I smooth the bfmpixel generated graph, as it shows lots of ups and down? How do I save corresponding data of bfmpixel for doing the interactive graph in other software?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants