# XY Chart Data Bounds

**URL:** <https://forum.inductiveautomation.com/t/xy-chart-data-bounds/40682>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [November 16, 2020, 10:23am UTC](https://forum.inductiveautomation.com/t/xy-chart-data-bounds/40682 "2020-11-16T10:23:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![matthew.ayre](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matthew.ayre/32/19499_2.png) [@matthew.ayre](https://forum.inductiveautomation.com/u/matthew.ayre)\
**Post date:** [November 16, 2020, 10:23am UTC](https://forum.inductiveautomation.com/t/xy-chart-data-bounds/40682/1 "2020-11-16T10:23:18Z")

</div>

I am using an XY chart component to produce something similar to the Gantt Chart example in the manual [here](https://docs.inductiveautomation.com/display/DOC81/Perspective+-+XY+Chart). However, it seems the data I am using is being displayed incorrectly, it seems to be bound by the grid [see below image].

 ![ErrorChart](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/f/5face7343fe0eaaddb8bdb5b3c4681414e9bdd4c.jpeg)

As far as I can tell the data is correct, and I’ve tried various datetime formats for both the source data and the range min/max, but nothing seems to change the display. Is there a property I am missing?

---

<div class="post-metadata">

**Author:** ![matthew.ayre](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matthew.ayre/32/19499_2.png) [@matthew.ayre](https://forum.inductiveautomation.com/u/matthew.ayre)\
**Post date:** [February 17, 2021, 8:26am UTC](https://forum.inductiveautomation.com/t/xy-chart-data-bounds/40682/2 "2021-02-17T08:26:02Z")

</div>

Feedback from support:

> I looked into the method of increasing the granularity of the Gantt chart. I agree that the place to change that would be "xAxes[0].date.baseInterval", but I was unable to get this to work as well. I spoke with the development team regarding this, and we discovered a bug with the xAxes[0].date.baseInterval properties that is preventing the interval from going down to the minute. The development team is now aware of the issue, and they will be working on a fix for a future update.

> There currently isn't a workaround for the baseInterval. Perhaps you could change the "series.column.appearance.fill" color of the columns and the "series.column.appearance.stroke" color to display a gap between the times This would not have the level of granularity to the minute, but it will show a distinction in the times.

---

<div class="post-metadata">

**Author:** ![matthew.ayre](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matthew.ayre/32/19499_2.png) [@matthew.ayre](https://forum.inductiveautomation.com/u/matthew.ayre)\
**Post date:** [February 17, 2021, 8:28am UTC](https://forum.inductiveautomation.com/t/xy-chart-data-bounds/40682/3 "2021-02-17T08:28:00Z")

</div>

p.s. support did not take this long to reply, I just forgot to update the post 🙂

---

<div class="post-metadata">

**Author:** ![bao.nguyen](https://avatars.discourse-cdn.com/v4/letter/b/8c91f0/32.png) [@bao.nguyen](https://forum.inductiveautomation.com/u/bao.nguyen)\
**Post date:** [July 12, 2023, 12:31am UTC](https://forum.inductiveautomation.com/t/xy-chart-data-bounds/40682/4 "2023-07-12T00:31:31Z")

</div>

Hi Matthew,

Thank you for sharing the information from support.

Since the intervals seem to be bound by the grids, I tried varying the grid distance instead of using the 'baseInterval' property. And it worked for me.

Hopefully this workaround will work for you also.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/c/acdb363e7ce6f8068e1c874f35cd3ba25d600f2c.png)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/d/1dc2313b8701f5b5078ed65a1d4f01023c994b47.png)