Fine Tuning Location

[MC130E]

@obj

But it’s certainly worth getting the location right if you can; no point in introducing extra position error.

FA staff,

I reported this behavior back in December 2019 in the direct message traffic related to the post I created here. This link is for reference only for you to locate the direct message traffic. The position error problem is not discussed in the post linked.

Unique Identifier: xxxx Assigned to PlanePlotter sites for transition?

Hi all, I fully understand the changes FlightAware is making on 31 DEC 2019 regarding PlanePlotter data sent using the “secondary sharing” method direct from PlanePlotter. I understand why it is being done. This is not meant to be a us or them type of post. My question is: Is it possible for FA to assign a Unique Identifier: xxxx-xxxx-… to my fairly low number PlanePlotter receiver site internally on their servers so that I can migrate that to a Pi and maintain my fairly low number FA sit…

When I identified the problem, eric1tran located code that shows home location position changes of approximately < 250 meters are ignored.

Here is the code he linked to:

flightaware/piaware/blob/0eec6e07db850c59e49fa8579432099b574ab12d/programs/piaware/faup.tcl#L399

Here was my suggestion at the time by direct message:

Just my opinion, but while a 250 meter “error” in home location might not impact FA, it could impact other sites that are using the dump1090-fa receiver location for their mlat purposes. You guys might want to consider dropping the 250m to something smaller like 30m or so. Just a thought.

---

Thanks,

-Dan