Andrei Mîrț

any updates on this one? @swalterfub nice one, would that work for WCS? I am not familiar with MapCache, but [the documentation](https://mapserver.org/mapcache/) suggests that it only works for WMS

@13675070160 I opened a separate issue here #2 . We will update that issue after we better understand the issue and we have a solution. If you have any further...

we discussed it privately already, but just for the record. the issue is that there is no sanity check. e.g. you can analyze a dataset spanning from 2010 to 2020...

there's 2 options: either we make a spatial* function for each bfast function, or we make a single spatial() function that accepts any bfast function as an output. With the...

even bfastmonitor doesn't only output magnitude and break, but also metadata with parameters used to get that specific result. Scientifically smart for reproducibility purposes, but everyone seems to drop it...

other forks are the github gee (no link yet) and [bfast python](https://github.com/gieseke/bfast) For both, we need to get in contact with the authors. For github gee, it's already planned.

I checked it. is it our goal to submit bfast to rOpenSci? If yes, we should perhaps all read the [developer's guide here](https://devguide.ropensci.org/), and then take some decisions, like =...

Preferably function names are descriptive verbs. We haven't decided yet on whether we want to use a namespace or not. So please also come up with namespace suggestions. Probably bfast...

No comments for a month, this means my last proposal is accepted. - bfast will be the namespace. - underscore will be the namespace separator. - e.g. **package**::**_namespace_**__functionName_ - e.g....

`I guess bfast::bfast_bfast` is not a good idea. But that's only because bfast in itself is not a great name for a function. A good name for a function should...