JSON version of the stats

[Jeff Thomas]

Is there a different endpoint or header i can p[Mod - Happy Thoughts] in to get the response in JSON v XML?

 

Thanks!

[Nestor Perez]

For which of all endpoints?

[Moritz Frenken]

What is the difference between

 

http://eu.data.vatsim.net/vatsim-data.json

 

and

 

http://eu.data.vatsim.net/vatsim-data.txt

?

 

Does these two contain exactly the same data? Because the json file is not published as far as I know

[Yanick Coulombe 965064]

What is the difference between

 

http://eu.data.vatsim.net/vatsim-data.json

 

and

 

http://eu.data.vatsim.net/vatsim-data.txt

?

 

Does these two contain exactly the same data? Because the json file is not published as far as I know

 

Yes I don't see any reason for the data to be different, only the format is different.

[Nestor Perez]

Correct. JSON geta updated a bit more frequently than TXT too.

[Felix Holmertz]

Would it be possible to add the logon time for each client like it's presented in the regular .txt status file?

[Alex Long]

Would it be possible to add the logon time for each client like it's presented in the regular .txt status file?

 

This, with a few other things, are on the to-do list.

[Nestor Perez]

And if someone wants to give it a shot... https://github.com/vatsimnetwork/dataserver/issues

[Daniel Roesen]

On 12/11/2019 at 8:54 AM, Yanick Coulombe 965064 said:

Yes I don't see any reason for the data to be different, only the format is different.

 

On 12/11/2019 at 9:12 AM, Nestor Perez said:

Correct. JSON geta updated a bit more frequently than TXT too.

So is the difference in line breaks in controller info ("ATIS") text between TXT ("^§") and JSON ("^§") intentional?

The former seems to be a regression introduced some time ago and breaking at least one application (QuteScoope) which still parses the TXT for ^§ like used in JSON: https://github.com/qutescoop/qutescoop/issues/24

[Matt Bozwood-Davies]

We're investigating this now @Daniel Roesen

[Daniel Roesen]

BTW; I seem to have found an earlier (April) report of this problem:

 

[Luke Kolin]

I'm getting a ton of JSON parsing errors on the data feed. Is anyone else?

Cheers!

[Ross Carlson]

12 minutes ago, Luke Kolin said:

I'm getting a ton of JSON parsing errors on the data feed. Is anyone else?

Cheers!

I'm not getting any issues in VAT-Spy. What errors are you getting?

[Martijn Rammeloo]

So do I. Parsing the JSON has been working for ages (in PHP), but all of a sudden json_decode returns a string instead of an array.

 

Update 1530Z: It seems as if the data is encoded twice on the VATSIM side. Because, if I decode it twice, everything works fine again.

$total_results = json_decode($string, true); // $string is the curl return
$total_results = json_decode($total_results, true);  // <- This line was not needed until yesterday

@Nestor Perez

Martijn

 

Edited December 8, 2020 at 02:43 PM by Martijn Rammeloo
Update: sort of solved it...

[Daniel Roesen]

On 11/24/2020 at 10:52 PM, Matt Bozwood-Davies said:

We're investigating this now @Daniel Roesen

Any update? It's still broken...