Skip to content
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

Site Location / Range rings missing in 8.2 #142

Open
speedst3r opened this issue Apr 12, 2023 · 6 comments
Open

Site Location / Range rings missing in 8.2 #142

speedst3r opened this issue Apr 12, 2023 · 6 comments

Comments

@speedst3r
Copy link

I am using the piaware v8.2 amd64 container and have noticed my site location and range rings are not displaying. I have unset the LAT/LONG environment variables to no effect. My understanding is with 8.2 it is meant to get the site information from piaware itself, and it looks like it is.

https://pastebin.com/DcwjiCr6

If I set the LAT/LONG env vars and downgrade to 8.1 this works successfully. Is there some additional work required for this container to get location/range rings on 8.2?

@speedst3r
Copy link
Author

Rings visible in 8.1
20230412_104201

Rings missing in 8.2
20230412_104137

@speedst3r
Copy link
Author

speedst3r commented Apr 15, 2023

Tested with truecharts/piaware:v8.2.0 container (that still accepts LAT/LONG env vars) and station/rings are visible.

https://pastebin.com/PauBSj4n

@speedst3r
Copy link
Author

I built this container locally after reverting f7e57dd (and supplying LAT/LONG environment vars); the station location and rings returned.

@seichold
Copy link

seichold commented Jul 3, 2023

Also impacts me. Also breaks UAT range estimations when using ultrafeeder (stats graph for UAT range is just blank). While this works for feeding flight aware (mlat etc works), it breaks other things locally. Please allow these again at least as a optional env.

@Tagliax
Copy link

Tagliax commented Jan 17, 2024

Same problem here, on version 9.0
I fixed this problem editing config.js in /usr/share/skyaware/html.
More precisely I set the parameter SiteShow to "true".
For the localization to be correct, also change the location coordinates.
Important: clear web cache.
image

@speedst3r
Copy link
Author

This seems to have been ignored... reported 16 months ago and no movement.

@mikenye any chance this could get looked at?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants