Hi Samweli,
Thanks for looking into this, I created an issue:
https://github.com/qgis/QGIS/issues/38468
with more clear example data and project, AND a movie in which you can see the
problem
I do think it *is* an issue.
Regards,
Richard Duivenvoorde
On 8/27/20 3:21 AM, Samweli wrote:
> Hi
Hi Richard, Nyall,
I had a quick look and it seems updating the filtering logic from
https://github.com/qgis/QGIS/blob/cb51326eb5585363078ee97fa0406a1ea341e2a8/src/core/qgsvectorlayertemporalproperties.cpp#L513
can fix the issue. I have played around with it, see image below showing one
point per
On Thu, 27 Aug 2020 at 01:54, Richard Duivenvoorde wrote:
> Searching in the code:
> https://github.com/qgis/QGIS/blob/master/src/core/qgsrange.h#L228-L238
> it looks like both limits are taken into account by default.
> Which in my case does not reflect my intention...
Actually it doesn't --
Hi Devs,
I want to talk about how the 'filter'-range is calculated for data.
I'm working with 'time based model output' in which for every hour a value is
calculated (via some math model).
So it is 'hourly' data, which you can either see as:
idstart data
1 10:00 10
2 11:00
