Epoch values for date range are incorrect

#1

When requesting a set of epoch values from 1 Jan 2010 through 31 Dec 2020, the resulting values do not fall into that date range (they’re too short, resulting in values resolving to 1970.)

#2

Can you post a link to your schema and an example of an incorrect value?

#3

Here’s the schema: Mockaroo - Random Data Generator and API Mocking Tool | JSON / CSV / SQL / Excel

Here’s the first 10 results from one example that I just generated:

{
  "id": 1,
  "epochstamp": "1508140408"
}, {
  "id": 2,
  "epochstamp": "1391107722"
}, {
  "id": 3,
  "epochstamp": "1347733185"
}, {
  "id": 4,
  "epochstamp": "1501503693"
}, {
  "id": 5,
  "epochstamp": "1597379818"
}, {
  "id": 6,
  "epochstamp": "1427354655"
}, {
  "id": 7,
  "epochstamp": "1530807790"
}, {
  "id": 8,
  "epochstamp": "1592066548"
}, {
  "id": 9,
  "epochstamp": "1472903208"
}, {
  "id": 10,
  "epochstamp": "1413315439"
}

Here’s a link to a full 1000 row download

As you can see the entire set comprises a few days in mid-January 1970 rather than a random assortment across the specified range (1 Jan 2010 to 31 Dec 2020.)

#4

It looks like those are valid Unix epochs. You can convert them to date times here: https://www.epochconverter.com/

Were you expecting a different format?

#5

As you can see the entire set comprises a few days in mid-January 1970 rather than a random assortment across the specified range (1 Jan 2010 to 31 Dec 2020.)

#6

Using https://www.epochconverter.com you can see that 1472903208, for example, converts to Saturday, September 3, 2016 11:46:48 AM. What are you using to parse epochs?

#7

This is embarrassing. It hasn’t occurred to me these were simply Unix epochs (expressed in seconds) and I was converting them with Javascript (which uses milliseconds) so I just needed to multiply them by 1000. Sorry for the trouble.

#8

Are you expecting a different formate? It looks like those are valid Unix epochs. You can convert them to date times here: Apps

#9

Since I work in javascript, I’m accustomed to epoch values being expressed in milliseconds and was seeing the issue in that narrow context. It’s painfully obvious how simple my mistake was now and there is no issue.