Welcome to Radarspotting. Please login or sign up.

April 18, 2025, 07:54:46 AM

Login with username, password and session length

New Members

New Members

You should get an activation email when you join.  If not, please use the Contact option.

~ICAO

Started by rikgale, February 13, 2021, 01:58:55 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

rikgale

Hi All

Quick question on VRS displaying ICAO codes.

I have very recently added my MLAT back feeds from ADSBExchange and Flightaware to feed into my VRS server. ADSBExchange was on there before the following issue but the Flightaware is a new addition to my merged feed.  Better late than never. Anyway, since adding in the Flightaware MLAT back feed I keep occasionally getting ICAO codes listed in my Database with a '~' at the front of them e.g. ~A91894. Does anyone know what these are? The example I posted has 5 position reports attached to it.

My MLAT back feeds were being feed to VRS using the Basestation format, so I have switched them to BEAST format and adjusted the listening port accordingly to see if this stops the issue.

They must be coming from my Flightaware feed as previously had ADSBEx feed. Any idea what they are, what's causing them and if there is anyway of linking these to a real plane?

Any advice, explanation gratefully received.

Thanks
Richard

Auto updated daily ZIP files on GitHub

Anmer

Quote from: rikgale on February 13, 2021, 01:58:55 PM
I keep occasionally getting ICAO codes listed in my Database with a '~' at the front of them e.g. ~A91894. Does anyone know what these are? The example I posted has 5 position reports attached to it.

Possibly anonymised MLAT data.  Have a look on the FlightAware forum.
Here to Help.

rikgale

Many thanks for the suggestion... will try over there, if I get another one. Will see if the format change from Basestation to BEAST makes any difference :)

Auto updated daily ZIP files on GitHub

rikgale

UPDATE: It would appear to be a TIS-B data from reading the FA forums. How I ended up with that in I have no idea.

Auto updated daily ZIP files on GitHub

rikgale

The change of message format from Basestation to BEAST appears to have cured the ~ issue.

Auto updated daily ZIP files on GitHub

Anmer

Thanks for letting us know what fixed it.
Here to Help.