currenthurricane API call - Indian Ocean - Current TimeGMT is always 1/1/1970 00:00:00

  • 1
  • Problem
  • Updated 6 years ago
Hi there.

Currently, I can see a tropical cyclone in the Indian Ocean. However, the timestamp returned by the currenthurricane api call is still 1/1/1970 00:00:00.

I am referring to the xml returned by the currenthurricane call, in the Current element, the TimeGMT element is missing the epoch info and is always 1/1/1970 00:00:00.

You had it fixed before but now the problem appears again. Can you please check?

Thank you in advance for your help.
Photo of seecago

seecago

  • 11 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 1
Photo of seecago

seecago

  • 11 Posts
  • 0 Reply Likes
The problem now appears also in the Tropical Cyclone Evan in the west Pacific.
The timestamp returned by the currenthurricane api call is always 1/1/1970 00:00:00.

Is it within your plans to fix this problem?

Can please somebody take a look at this?

Thank you very much for your help.
Photo of seecago

seecago

  • 11 Posts
  • 0 Reply Likes
Hi there.
I hate to remind you but this problem still persists. There is no timestamp info (it is just 1-1-1970) for some storms. I believe this happens for the storms that are in Indian ocean or in the South Pacific Ocean.

Is this in your plans to fix it? Because this call cannot be used as it is right now.

Thank you in advance for your help.
Photo of seecago

seecago

  • 11 Posts
  • 0 Reply Likes
This problem still persists. Currently there are two storms, one in the South Indian Ocean (Mitchell) and one in the South Pacific (Freda) and they have both their timestamps equal to 1-1-1970 00:00:00.

Are you planning to fix this problem?

This call is unusable if there is no timestamp info.

Thank you in advance for your help.
Photo of seecago

seecago

  • 11 Posts
  • 0 Reply Likes
It seems to be working now properly.
Thank you for fixing this.