Auxiliary functions to screen input RasterBrick for correct layer names and to trim RasterBrick based on sensor or date parameters about bfastspatial HOT 6 CLOSED

Yes we should. Something like .hasLandsatMetadata() ? Will also make life easier whenever they decide to suddenly change naming convention. Or launch landsat 9. Or if we want to do sentinel2/Landsat merged analysis...
What do you mean by trim rasterbrick?

from bfastspatial.

Actually, subset would have been a better term. I have added a function subsetRasterTS(), which works similarly to raster::subset(), but uses dates and/or sensor information (from getSceneinfo) to subset a time series raster. Also check out my changes to bfmSpatial() - this is more or less how I have run bfm

from bfastspatial.

I have created a new remote branch - feature-isLandsatSceneID, with a function .isLandsatSceneID() that returns TRUE if a character conforms to Landsat scene naming convention. I changed the name from .hasLandsatMetadata for clarity, in case you want to work with actual Landsat metadata in the future. The idea is to call this function wherever a dates, sensor, or other Landsat-specific information is needed. This can also be replicated for other datasets if needed.

Check out the branch and let me know what you think before merging to develop. If it's ok, then I'll call it in the other functions and merge back to develop.

from bfastspatial.

Okay, just reading that now; I've commented the commit though. I had two comments I think which are to remove the export rocklet and to extend it to classes rasterbrick and stack, and not only to single characters.

from bfastspatial.

yup, working on it, and I'll commit something tomorrow

from bfastspatial.

Okay, just did it. I simplified quite a lot. Quite safe to assume that the pattern '(LT4|LT5|LE7|LC8)\d{13}' is sensor path row year jday I think

from bfastspatial.