Hi Soeren, Thanks for your answer :) I perfectly understand. I wish I could be of more help, though.
I do not know how to add such a warning in the module, but I would suggest, if you don't have any objections, to add a side note in the manual page (or maybe just in the description section) stating this special behavior. Probably something simple like: "*The temporal where will work as expected only when one strds is to be sampled. Otherwise, if more than one strds are selected, t_where will not be considered.*" IMHO, the t_where is a very nice feature, even though it does not work in this special case of more than one strds. Best, Vero 2016-01-18 15:35 GMT-03:00 Sören Gebbert <[email protected]>: > Hi, > the reason behind the removal of the temporal where option was, that > it will not work in certain conditions when several STRDS are > involved. A warning will not be printed if the result is wrong. Hence, > i removed the option, since i do not have the time to implement an > always proper working solution. > > Best regards > Soeren > > 2016-01-15 0:24 GMT+01:00 Markus Neteler <[email protected]>: > > Hi Vero, > > > > On Fri, Jan 8, 2016 at 6:56 PM, Veronica Andreo <[email protected]> > wrote: > >> Hi devs, > >> > >> I was using t.vect.observe.strds and while reading the manual from > grass71 > >> (https://grass.osgeo.org/grass71/manuals/t.vect.observe.strds.html), I > found > >> that in the Description section a parameter "t_where" was mentioned > >> while not listed under Parameters. > > > > Thanks for catching that: I have remove the reference to t_where > > parameter t.vect.observe.strds manual as it was deleted in r64560. > > > >> However, this t_where parameter is present for > >> t.vect.observe.strds in grass70 manual > >> (https://grass.osgeo.org/grass70/manuals/t.vect.observe.strds.html). > >> > >> I found in trac that changeset 64560, removes t_where from trunk since > it is > >> not supported in case of multiple strds sampling, but I did not find > >> something similar for release branch. Is there a reason why it should > work > >> in 70 but not in 71? > > > > I guess it doesn't always work in relbranch70. > > Maybe Soeren knows? > > > > > > Markus >
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
