Positions far off in local view
dervogt opened this issue · 1 comments
Hi, I am a very happy user of this docker image and kudos to the good work done here.
But, on one of my remote receivers which I deployed at my son's place in Germany, I am having a really strange issue with the Maps display, when using it directly on the container, but I think a picture tells more than 1000 words:
So the station is located in Paderborn, Germany, but the planes show up somewhere over Oxford in the UK......
The first check from me was to see if remotely loaded data had been impacted by this as well, so I setup my little own map server at home in the Netherlands and started to load the Paderborn data remotely into another readsb container running in NET_ONLY mode and subscribing to the data stream of not only my local receivers but also to the other two remote rcvrs in Hamburg and Paderborn.
In the consolidated view here in NL, everything is / was alright and the planes showed up where I would expect them: somewhere close to Paderborn and not in Oxford...
Next step then was to see if this was related to the config of the local receiver and see if there were any ENV variables which would be different to the other receivers in NL and Hamburg: identical, except the specific settings per location like LONG/LAT and the Timezones which are of course specific to every location. (Actually they are all in CET, but my home receiver gets Europe/Amsterdam, the other one's as they are in Germany, get TZ=Europe/Berlin)
So I thought, okay, the Paderborn receiver had the worst receiver and antenna setup still running on a unfiltered rtlsdr from ebay, so I changed them this weekend against a self built and burnt-in colinear antenna on a Flightaware 1090 filter with a nooelec rtlsdr as the receiver....which ran perfect and with no issues at all during the burnin test here in NL. But also with a completely different receiving hardware, the positions are still far off in the local view....
Anyone an idea on where to look further or ever experienced something like this before?
Here is a pastebin of a docker inspect of the affected container:
https://pastebin.com/BgHLqQMZ
I don't know yet what caused this issue, but I resolved this by completely re-building the container from scratch