# Tag history binding periodic aggregation

**URL:** <https://forum.inductiveautomation.com/t/tag-history-binding-periodic-aggregation/69417>\
**Category:** Ignition\
**Tags:** perspective, ignition81\
**Created:** [February 3, 2023, 4:58pm UTC](https://forum.inductiveautomation.com/t/tag-history-binding-periodic-aggregation/69417 "2023-02-03T16:58:42Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![bfreeman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bfreeman/32/87436_2.png) [@bfreeman](https://forum.inductiveautomation.com/u/bfreeman)\
**Post date:** [February 3, 2023, 7:34pm UTC](https://forum.inductiveautomation.com/t/tag-history-binding-periodic-aggregation/69417/5 "2023-02-03T19:34:00Z")

</div>

> [@paul-griffith](#):
>
> > [@bfreeman](#):
> >
> > IMHO I don't see the point of these units if this is the case.
> 
> I mean, would you rather set a period of 604800 seconds, or 1 week? It's all ultimately _milliseconds_ under the hood. The different units are just a convenience.

Haha, sure 😅 My point was more on the semantic.

I agree a week is 604800 seconds 🙃 but what about **month** (and **year** to a greater extent)?

> [@paul-griffith](#):
>
> From what I see in the code, it looks like in this particular case the end date would be adjusted to 48 hours (i.e. start: Jan1@midnight, end: Jan3@midnight) but the 'return size' will be _2_, so you'll get two output rows: Jan1@midnight, and Jan2@midnight.

Understood! Thanks for looking into the code!

I think all this deserves to be documented.

---

_[View the full topic](https://forum.inductiveautomation.com/t/tag-history-binding-periodic-aggregation/69417)._