bfast2 / bfast2/geeBfastMonitor

History and Monitor period

Open
#11 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
75
Forks
30
PR merge metrics
No merged PRs in 30d

Description

Hello,
I hope this email finds you well. I am interested in Bfast monitor. I really appreciate that you solved the issue in github that I was facing. I am following (https://github.com/bfast2/geeBfastMonitor) this documentation.

I was curious to know that in this algorithm, how to define the stable history and monitor period for each Pixel? My study area is in Belgium (31UFR tile).
- Do I need to define history and monitoring period separately for each pixel manually? Or, a general history and monitoring period would be ok for the entire area?

- If I have to define history and monitor period separately every time, how would I understand that like 2016 to 2019 was stable or 2016 to 2018 was stable history period?

- How to know that a break is detected in the monitor period?

I am sorry for asking so many questions. Still I would appreciate your suggestions in this regard.

Looking forward to hearing from you. Thank you.
Have a nice day.

Regards,
Sraboni

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.