# ISTAT data problem

**URL:** <https://dbnomics.discourse.group/t/istat-data-problem/228>\
**Category:** Community\
**Created:** [March 26, 2019, 3:44pm UTC](https://dbnomics.discourse.group/t/istat-data-problem/228 "2019-03-26T15:44:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![acottrell](https://avatars.discourse-cdn.com/v4/letter/a/c68b51/32.png) [@acottrell](https://dbnomics.discourse.group/u/acottrell)\
**Post date:** [March 26, 2019, 3:44pm UTC](https://dbnomics.discourse.group/t/istat-data-problem/228/1 "2019-03-26T15:44:23Z")

</div>

It’s good to see ISTAT included as a provider, but there’s something odd about  
their time series: they’re not in time-order. For example, take the retail sales series  
ISTAT/120\_337/M.RTD\_TURN3.1.TOTAL.N.1.IT. The monthly “period” array in the  
JSON starts like this:

```
"period" : [
  "2005-01",
  "2005-10",
  "2005-11",
  "2005-12",
  "2005-02",
  "2005-03",
  "2005-04",
  "2005-05",
  "2005-06",
  "2005-07",
  "2005-08",
  "2005-09",

```

And other years are the same: January, October, …! This places a rather  
awkward burden on clients (to get the data into the right order), which we haven’t  
seen for any other providers.

---

<div class="post-metadata">

**Author:** ![cbenz](https://yyz2.discourse-cdn.com/free1/user_avatar/dbnomics.discourse.group/cbenz/32/33_2.png) [@cbenz](https://dbnomics.discourse.group/u/cbenz)\
**Post date:** [March 27, 2019, 10:06am UTC](https://dbnomics.discourse.group/t/istat-data-problem/228/2 "2019-03-27T10:06:59Z")

</div>

Hello @acottrell

Indeed, that’s a mistake in our “fetcher” for ISTAT.

We’re going to fix that.

Thanks for the report!

---

<div class="post-metadata">

**Author:** ![cbenz](https://yyz2.discourse-cdn.com/free1/user_avatar/dbnomics.discourse.group/cbenz/32/33_2.png) [@cbenz](https://dbnomics.discourse.group/u/cbenz)\
**Post date:** [March 28, 2019, 6:10pm UTC](https://dbnomics.discourse.group/t/istat-data-problem/228/3 "2019-03-28T18:10:46Z")

</div>

Please see [this issue](https://git.nomics.world/dbnomics-fetchers/management/issues/147#note_10095) to follow the resolution of this problem.

---

<div class="post-metadata">

**Author:** ![cbenz](https://yyz2.discourse-cdn.com/free1/user_avatar/dbnomics.discourse.group/cbenz/32/33_2.png) [@cbenz](https://dbnomics.discourse.group/u/cbenz)\
**Post date:** [April 1, 2019, 1:33pm UTC](https://dbnomics.discourse.group/t/istat-data-problem/228/4 "2019-04-01T13:33:16Z")

</div>

Just for your information, this has been fixed. See [https://db.nomics.world/ISTAT/120\_337/M.RTD\_TURN3.1.TOTAL.N.1.IT](https://db.nomics.world/ISTAT/120_337/M.RTD_TURN3.1.TOTAL.N.1.IT)

---

<div class="post-metadata">

**Author:** ![acottrell](https://avatars.discourse-cdn.com/v4/letter/a/c68b51/32.png) [@acottrell](https://dbnomics.discourse.group/u/acottrell)\
**Post date:** [April 1, 2019, 2:36pm UTC](https://dbnomics.discourse.group/t/istat-data-problem/228/5 "2019-04-01T14:36:50Z")

</div>

@cbenz: Thanks, that’s good to hear.