[GRASS-dev] TGRASS: best practice management of aggregated data

[Veronica Andreo]

Hi,

El sep 27, 2015 9:11 AM, "Markus Neteler" <neteler at osgeo.org> escribió:
>
> Hi,
>
> while processing MODIS LST time series, I came across some questions
> concerning best practice:
>
> Say, I'm aggregating from daily temperature  data a set of weekly
> min/max/avg maps. So the best pracise is about
>
> - using a reasonable name for the output strds
> - using reasonable map names (alias "basename" in t.*)
>
> They should be long-term understandable (with too cryptic names you
> will have troubles even a few weeks later) but also parsable (think
> "pattern" of g.list).
>
> So, in my case I would call the output strds e.g.
"lst_aggreg_modis_weekly".
> I would use as "basename" something like "lst_${year}_avg_min_week",
> "lst_${year}_avg_avg_week", "lst_${year}_avg_max_week".
> (better ideas?)

Have you noticed the -s flag in t.rast.aggregate? It adds date to file
names according to granularity of aggregation. I've discovered it recently
and it is very useful for me.

> But: do I put these three sets into a single strds or into three separate
ones?

If you use t.rast.aggregate and different methods, you get different strds.
IMHO, this is best practice, since you can aggregate them to other
granularities without having to select maps by method inside them. Does
that make sense?

HTH
Vero

_______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20150927/6b7f0141/attachment.html>