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 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?
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 <neteler@osgeo.org>:
Hi Vero,
On Fri, Jan 8, 2016 at 6:56 PM, Veronica Andreo <veroandreo@gmail.com> wrote:
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?
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.
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.
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?
Here is the diff file for release branch manual page. It just adds a line or so explaining that t_where in t.vect.observe.strds works only when one strds is to be sampled.
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.
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.
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?
On Tue, Feb 9, 2016 at 6:42 PM, Veronica Andreo <veroandreo@gmail.com> wrote:
Hi
Here is the diff file for release branch manual page. It just adds a line or
so explaining that t_where in t.vect.observe.strds works only when one strds
is to be sampled.
