Especially the low number of positions > 320 km is coming and going in waves over the days.
One day i had over 300, now just around 130 - goes up and down.
Beside that it doesn’t matter which feeder i use (FA Stick, Airspy, Airsquitter) because i am at my max range on this location.
For my location, every day is groundhog day – same number of flights, same distances. Course the weather is the same every day also.
I see your distances are in km . Mine are in mi (statute miles I guess). Is there a place to set that or is it automatic based on country? I would think nautical miles would be used for consistency.
Weather and tropo influence my topography-constrained farthest position counts. My wet trees cause more trouble than dry trees for example. So those farthest #s do vary significantly by day. While Airspy provides more messages and positions overall, I don’t recall that impacting position count at the longest ranges.
I have browsed the these charts on other stations. You can figure out a lot about a station’s location relative to airports and obstructions by looking at the coverage graph too.
Some of us use NM instead of km or mi too. And the chart distance buckets don’t actually align between measurement units. 240 km is 130 nmi for example.
In km by comparison, I guess they are pretty close.
You can set it under My account (hover over your name once logged in).
Option 5 lets you determine which measurement units you want to use, NM or KM depending on your liking.
If you are talking about the coverage graph, that just rounds up/down to fit the little box quadrants. 40 nmi is 46 mi or 74 km. So when viewed in mi, you get 50, when viewed in km you get 80 increments, and 40 for nmi.
Right, but I just wanted the polar coverage plot to have the same increments (and units) as the range rings in the SkyAware map. I guess I could change the range rings in SkyAware map.
No, I look @ mine all the time. I used to see a good number of pings at 250 miles (+/- 400 km) pre pandemic. No antenna or system change since then, heck no.