That is more CPU than I would expect in normal operation. That said it looks like it is not connecting to the data feed correctly. That may have a slight increase as it opens and closes the socket.
Check that the IP and port are correct. If this is on the same Pi I would use the loopback...
It could be that not a lot flies that way to be honest. The predicted range is based on the terrain and what is around. However if no planes fly in that direction we have no way of knowing if that is true or not.
The actual measured?
Our ADS-B decoder is quite conservative and so you may see more or less aircraft than you are seeing in say Dump1090. We tend to err on the side of caution with correcting of CRC errors and single position reports and so that might be affecting your range. We tend to...
No problem, the data comes from our own terrain models that power the 3D functionality in Plane Finder.
We used to use HWT but wanted something more integrated into our own toolsets and so we wrote our own!
We have a new tool to unveil and it can be accessed @ https://planefinder.net/account/receivers
Simply sign in (or create an account) and click on one of your shared codes that you want to look at.
In the "Coverage Map" section alongside your actual coverage are two new plots to show...
Sorry that I can't say more. We did spend a lot of time trying to get MLAT with "unknown" third party systems working.
Whilst it was working, the level of errors we could see was not acceptable to us so we drew a hard line in the sand on the requirements. You can actually see some of these...
Yes that will do it!
Also you can look at a new feature on the https://planefinder.net/account/receivers web page. Make sure you are logged in!
If you go to the new Coverage Map tab it will show you what we'd expect you able to receive!! (see attached)