search

vradarserver / vrs

A .NET web server that can plot the positions of aircraft on a map
http://www.virtualradarserver.co.uk/
Other
267 stars 50 forks source link

Route lookup fails on BDS-derived callsigns #115

Open marcus-aa opened 10 months ago

marcus-aa commented 10 months ago

When a callsign is marked with "*" , afaik meaning it was derived from a BDS messgae, the route lookup doesn't work properly (or at all)

image

But if I click on "submit route", it is found without problem.

image

/M

marcus-aa commented 10 months ago

Or is this related to HP/APF, you had to fix something with it before routes could be entered, here is another one with normal callsign that also doesn't work. But some of them seems work normally.

image

marcus-aa commented 10 months ago

It showed up but after a while, and now this one also indicated by an asterisk.

image

marcus-aa commented 10 months ago

When a callsign is marked with "*" , afaik meaning it was derived from a BDS messgae, the route lookup doesn't work properly (or at all) /M

It looks like they entered APF672_ (with a trailing space), could that be the issue?

marcus-aa commented 10 months ago

No, there is something else going on, possibly related to receiver type, or some other kind of delay.

This one had no route until it more or less landed. No route at 52 minutes, route popped up at 54 minutes. Same callsign.

image

Could there be an issue looking up callsigns if they are only delivered by JSON receivers?

What triggers the route lookup ?