-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tar1090 location does not map to readsb container #4
Comments
Hi @rucknapucknavitz, this has been solved. The docker image |
It's still not working for me. I pulled the :latest (docker-compose pull and then docker-compose up -d) and that didn't work. I then updated my docker-compose.yml with LAT and LONG per the update to the guide (https://github.com/mikenye/docker-readsb/wiki/Guide-to-ADS-B-Data-Receiving,-Decoding-and-Sharing,-Leveraging-RTLSDR-and-Docker#deploying-tar1090-for-improved-visualisation) and that also didn't work. I'm still stuck in NY, unfortunately. Location on the map in PiAware and PlaneFinder containers work fine. |
Bingo. Re-pulled following the latest update here and it's working great! Map defaults to my location. Now shows distance rings, and distance from antenna in the data columns on the right. Thank you! |
The mikenye/docker-tar1090 location does not correctly map to the lat/lon set in mikenye/docker-readsb
The default location is over Manhattan, NY.
Pressing the H (H)ome/Reset Map key on the browser will reset the map on NY.
@wiedehopf suspects that the tar1090 container has its own readsb, if so it will need its own lat lon set as well
The text was updated successfully, but these errors were encountered: