Transform JSON time data from Coordinated Universal Time (UTC) to Indian Standard

Question

Transform JSON time data from Coordinated Universal Time (UTC) to Indian Standard

Hello, I consider myself an amateur in the world of online javascript learning. Currently, I have come across a challenge that has left me stuck.

I am working with a JSON time data provided in UTC format (e.g. 16:00:00Z) and my goal is to convert it to IST.

var main = function () {
  json_url = "http://ergast.com/api/f1/current/next.json";
  xhr = new XMLHttpRequest();
  xhr.open("GET", json_url, false);
  xhr.send(null);
  weather = JSON.parse(xhr.responseText);
  mydate = weather.MRData.RaceTable.Races[0].Qualifying.time;
  mytime = Date(mydate);
  mytime = mytime.toLocaleString();
  return mytime
}

After doing some research online, I attempted adding the following:

mytime = mytime.toLocaleString();

Unfortunately, this only returns my local day, date, and time rather than the intended time from the JSON data. Any assistance on this matter would be greatly appreciated.

javascript datetime

Answer 1

Answer №1

It has been noted in the comments that when the Date constructor is invoked as a function, it simply returns a string representing the current date and time, similar to calling new Date().toString().

There is no specific format known as "UTC format". UTC is actually a time standard, whereas the format you are likely referring to is ISO 8601.

The provided URL serves a JSON file containing the date and time in this structure:

"date":"2022-04-10",
"time":"05:00:00Z"

Parsing strings using the built-in constructor can be tricky at times, as highlighted in this Stack Overflow thread: Why does Date.parse give incorrect results?.

However, if you wish to convert the date and time into a valid ISO 8601 timestamp, you can concatenate the components like so:

2022-04-10T05:00:00Z

This combined timestamp will be correctly parsed by the internal parser when used with the Date constructor, for example:

let date = weather.MRData.RaceTable.Races[0].Qualifying.date;
let time = weather.MRData.RaceTable.Races[0].Qualifying.time;
let mydate = new Date(`${date}T${time}`;

Here's a snippet of code that you can run:

let obj = {"date":"2022-04-10", "time":"05:00:00Z"};
let date = new Date(`${obj.date}T${obj.time}`);

// UTC 
console.log(date.toISOString());
// Local time
console.log(date.toString());
// Melbourne local time (also provided in the JSON)
console.log(date.toLocaleString('en-AU', {timeZone:'Australia/Melbourne', timeZoneName:'short'}));
// Indian time
console.log(date.toLocaleString('en-AU', {timeZone:'Asia/Kolkata', timeZoneName:'long'}));

Remember to declare your variables properly to avoid global scope issues or errors in strict mode.

Answer 2

It has been noted in the comments that when the Date constructor is invoked as a function, it simply returns a string representing the current date and time, similar to calling new Date().toString().

There is no specific format known as "UTC format". UTC is actually a time standard, whereas the format you are likely referring to is ISO 8601.

The provided URL serves a JSON file containing the date and time in this structure:

"date":"2022-04-10",
"time":"05:00:00Z"

Parsing strings using the built-in constructor can be tricky at times, as highlighted in this Stack Overflow thread: Why does Date.parse give incorrect results?.

However, if you wish to convert the date and time into a valid ISO 8601 timestamp, you can concatenate the components like so:

2022-04-10T05:00:00Z

This combined timestamp will be correctly parsed by the internal parser when used with the Date constructor, for example:

let date = weather.MRData.RaceTable.Races[0].Qualifying.date;
let time = weather.MRData.RaceTable.Races[0].Qualifying.time;
let mydate = new Date(`${date}T${time}`;

Here's a snippet of code that you can run:

let obj = {"date":"2022-04-10", "time":"05:00:00Z"};
let date = new Date(`${obj.date}T${obj.time}`);

// UTC 
console.log(date.toISOString());
// Local time
console.log(date.toString());
// Melbourne local time (also provided in the JSON)
console.log(date.toLocaleString('en-AU', {timeZone:'Australia/Melbourne', timeZoneName:'short'}));
// Indian time
console.log(date.toLocaleString('en-AU', {timeZone:'Asia/Kolkata', timeZoneName:'long'}));

Remember to declare your variables properly to avoid global scope issues or errors in strict mode.

Transform JSON time data from Coordinated Universal Time (UTC) to Indian Standard

Answer №1

Similar questions

The issue of Basic Bootstrap 5 Modal triggering twice is causing a frustrating experience

Troubleshooting problem with $http in AngularJS: encountering challenges with HTTP JSONP requests

React: executing function before fetch completes

ng-repeat not functioning properly with FileReader

To avoid any sudden movements on the page when adding elements to the DOM using jQuery, is there a way to prevent the page from

Issue adding dictionary value to an array in JavaScript

Accessing XML files locally via JavaScript on Chrome or Internet Explorer, with compatiblity for Android mobile devices as well

Having trouble getting your Bootstrap v4 carousel to function properly?

Utilizing jQuery to Perform Calculations with Objects

What are the applications of global variables in node.js?

Assigning array materials in ThreeJS allows you to create complex

Having trouble extracting the video ID from a Youtube feed XML with jQuery

Prevent the ability to drag and drop within specific div elements

The issue of infinite rendering caused by useState and how to effectively resolve it

Three.js dynamic bone animation: bringing your project to life

"Enhance your database by incorporating HTML link clicks through AJAX integration with PHP and MySQL

How come the method $.when().pipe().then() is functioning properly while $.when().then().then() is not working as expected

Is there a way to locate the source or URL linked to a button on a form or webpage?

How come TypeScript remains silent when it comes to interface violations caused by Object.create?

Encountering: error TS1128 - Expecting declaration or statement in a ReactJS and TypeScript application