Dear Markus and Luca, feel free to implement user defined granularities in t.register. It should be convenient to use something like "astro_seasons" as identifier to apply the astronomical seasons to map layers that should be registered in the temporal database. However, the computed granularity of the resulting space-time dataset will be 1 day, unless you modify the granularity computation in lib/python/temporal/temporal_granularity.py to acknowledge user defined granularities. Which would be really nice indeed.
Best regards Soeren 2015-08-13 22:08 GMT+02:00 Markus Neteler <[email protected]>: > Hi Soeren, > > On Thu, Aug 13, 2015 at 5:55 PM, Sören Gebbert > <[email protected]> wrote: >> Hi Luca, >> what kind of seasons do you think of? > > For example, we would need something like this (Northern hemisphere): > - spring: 22/03/ .. 20/06/ > - summer: 21/06/ .. 23/09/ > - autumn: 24/09/ .. 20/12/ > - winter: 21/12/ .. 21/03/ > > It would be *really* good to let the user decide the start/end date of > the seasons. > > thanks > Markus _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
