The data API(vatsim-data.json) is not reporting text_atis value properly.

[asdf1280]

Hello. It looks like vatsim data api is not providing text_atis of all controllers. Obviously most ATIS have their own text based atis data. Some controllers also have their controller info. However, the API is only showing text atis of some random controllers. Please check the status of API.

For example, at the time I'm posting this, I can see text atis of RKSS_ATIS, but not EGLL_ATIS.

I'm using the API URL here: https://data.vatsim.net/v3/vatsim-data.json

Raw data here:

{"cid":1497340,"name":"DoYoung Kim","callsign":"RKSS_ATIS","frequency":"126.400","facility":4,"rating":3,"server":"CANADA","visual_range":50,"atis_code":"D","text_atis":["GIMPO INTERNATIONAL AIRPORT INFO DELTA. TIME ONE ONE ZERO ZERO",".UTC. EXPECT VOR RUNWAY 32L APPROACH.","DEPARTURE RUNWAY 32R.","SEOUL DEPARTURE FREQUENCY WILL BE 122.80.","RUNWAY 32L TOUCH DOWN SURFACE WIND THREE TWO ZERO DEGREES, FOUR","KNOTS.. VISIBILITY 7 KILOMETERS.. .. .. .. TEMPERATURE","ZERO.CENTIGRADE. DEWPOINT MINUS SEVEN.. QNH ONE ZERO TWO","ONE.HPA. . ADVISE ON INITAL CONTACT YOU HAVE INFO DELTA."],"last_updated":"2022-01-23T11:42:41.8460552Z","logon_time":"2022-01-23T11:12:23.7195612Z"}


{"cid":1422248,"name":"Dean Benavidez","callsign":"EGLL_ATIS","frequency":"128.070","facility":4,"rating":4,"server":"SINGAPORE","visual_range":0,"atis_code":null,"text_atis":null,"last_updated":"2022-01-23T11:42:27.8798653Z","logon_time":"2022-01-23T09:45:39.2922068Z"}

[asdf1280]

vatsim-data.json.txt

Here's the immediate API response that is problematic. Here you can clearly see some ATIS and controllers don't have text_atis which they should obviously have.

[fixterjake]

Working on resolving this now

[dylanm312]

Bumping this issue as I am also having issues with intermittent text atises.

[mbozwood]

When you see the values are null in the datafeed are you checking they exist in FSD by getting it from another client? It can take a minute or so for the ATIS to pull through to the dataserver and looking at the monitoring, there haven't been any servers not reporting any ATIS values as far as we can identify.

[dylanm312]

Hey Matt! So after looking at it more closely it seems that it does eventually make it to the data feed, it just sometimes takes a few minutes. Together with the cron job on the ZOA site that pulls in the info from the data feed once a minute, this would explain why we are sometimes seeing delays of up to 5 minutes or so before the text atis will update.

TL;DR it just takes a few minutes to update like you said, but it gets there eventually, so no issue.

[jonaseberle]

I think this is mostly resolved.

Anyways, I am leaving that here:
This helps to get a feeling for the data:

#! /bin/bash
# Outputs ATIS stations with `atis_code === null` with the time they have been online (ignore newly connected stations)
# and their first ATIS line.
# I think it is normal to only contain stations that have been freshly connected. But we sometimes see stations change their state
watch "$(cat <<'EOL'
data="$(curl --silent https://data.vatsim.net/v3/vatsim-data.json)"; update_timestamp="$(jq '.general.update_timestamp | strptime("%Y-%m-%dT%H:%M:%S.%GZ") | mktime' <<<"$data")"; echo "updated $update_timestamp"; jq -r ".atis[] | select(.atis_code==null) | {callsign:.callsign, text_atis0: .text_atis[0], onlineSince_sec:($update_timestamp - (.logon_time | strptime(\"%Y-%m-%dT%H:%M:%S.%GZ\") | mktime))}" <<<"$data"
EOL
)"

I guess the feed generator receives that status package from the client but nulls its state when it does not see that package for some time. (It might be that Cloudflare edge routing also plays a role.)

Ref: qutescoop/qutescoop#328