Strange callsign in the data feed.

Discussion in 'Other technical not related to ADSBx Feeding' started by XM192, Jun 22, 2020.

  1. XM192

    XM192 New Member

    There is a Typhoon near Norwich ZK354 that has no callsign, when it was near a C-17 it got the C-17s callsign of RRR818, now it has the Voyagers callsign of TARTN19. Not sure if this helps.
     
  2. wiedehopf

    wiedehopf Administrator Staff Member

    "data feed"

    Please be more specific.
    If you're talking about the web page, copy the share link on the left please and post it here.
     
  3. XM192

    XM192 New Member

    Sorry: The API URL is
    https://adsbexchange.com/api/aircraft/json/lat/53.883316/lon/-1.955175/dist/250/

    Returned two aircraft with the same callsign:

    {"postime":"1592838311422","icao":"43C77D","reg":"ZK354","type":"EUFI","wtc":"2","spd":"340","altt":"0","alt":"16900","galt":"16900","talt":"16000","lat":"52.585367","lon":"1.221596","vsit":"0","vsi":"-162","trkh":"0","ttrk":"","trak":"111","sqk":"6061","call":"RRR818","gnd":"0","trt":"3","pos":"1","mlat":"1","tisb":"0","sat":"0","opicao":"","cou":"United Kingdom","mil":"1","interested":"0","dst":"138.11"},

    ...

    {"postime":"1592838314175","icao":"43C172","reg":"ZZ172","type":"C17","wtc":"3","spd":"344","altt":"0","alt":"11000","galt":"11010","talt":"11008","lat":"52.259583","lon":"-0.854034","vsit":"1","vsi":"64","trkh":"0","ttrk":"244","trak":"242.5","sqk":"6401","call":"RRR818","gnd":"0","trt":"5","pos":"1","mlat":"0","tisb":"0","sat":"0","opicao":"RRR","cou":"United Kingdom","mil":"1","interested":"0","dst":"105.19"},

    The first line for 43C77D on the website and on my Pi didn't have a callsign, but here it acquired the callsign of a nearby RAF C-17 doing two circuits at Mildenhall. When the C-17 left the area the Typhoon became TARTN19 which was the callsign of the nearby Voyager in AARA8.

    At first I though it was something in my code that if no callsign was set it was using the callsign from the previous entry but after doing a curl I found that the callsign was wrong in the data.

    It's not a big issue (and not a complaint) but just thought it would be interesting to see what caused it.

    Thanks regards, Rob.
     
  4. wiedehopf

    wiedehopf Administrator Staff Member

    Yeah it was a data reception error probably.

    And as it wasn't sending a callsign, it stayed in there for quite some time.
    Might need to adjust that timeout.
     
    Last edited: Jun 23, 2020