Skip to main content

RadarView August 2025 Update

RadarView Update: August 2025


This update introduces several major new features, including the highly anticipated Playback function (in a public preview) and various stability fixes.


✨ NEW FEATURES

1. Multi-Language Support

RadarView is now available in multiple languages. The interface will automatically adapt to your browser's language settings.

  • Supported Languages: English, Spanish, German, Polish, French, Dutch, Chinese, and Czech.


2. Playback Function (Public Preview)


The ability to replay historical flight data is now available for everyone to test in a public preview phase. Please note that this feature is still under development and may be unstable.

During the preview, all users have full access. After the preview phase, the following limits will apply:

FEATURE

PREVIEW

FREE

PREMIUM (Supporters)

HISTORY FEATURES




Select aircraft by ICAO/Reg

YES

YES

YES

Time range

7 days

3 days

TBA*

Replay speed

All speeds

16x, 32x only

All speeds

FULL PLAYBACK




Playback time

Last 2 hours

Last 2 hours

TBA*

Data resolution




Frame Interval

10 sec

10 sec

10 sec

* TBA - To Be Announced: I currently have no idea how much the server can handle, so I do not want to promise anything for the Premium tier yet.


3. Weather Layers


This update introduces experimental weather layers, including Clouds, Precipitation, Temperature, Pressure, and Wind. Due to API rate limits, this feature will initially be available only for Feeders and Testers. (See Q&A for more details).


🔧 FIXES

1. RadarView Feeder Script

  • Fixed an issue with wget during the installation process.
  • Fixed an incorrect EOF implementation that could cause the script to crash when starting the service.
  • Action Required: Users experiencing issues should download the latest version of the script and re-run it.


2. Feeder Activation Service

  • Fixed a bug where Feeder status was not always being activated automatically after a successful connection.


🔧 KNOWN BUGS

1. Playback system

  • Playback from last 2 hours sometimes returns "Failed to fetch Data". This is caused by user's network due to not-very-well optimized data fetching. 
  • History in all history mode may load for more time due to bad optimization

2. RadarView

  • OpenAIP may not load correctly. I made some fixes but not sure if they will work

❓ Q&A about this update


Q: What's the status of the PayPal integration for Patrons? A: Work on the PayPal integration is ongoing. It requires significant compliance and security work to be done right. It is not ready for this update, but it remains a top priority for a future release.

Q: What about weather conditions at cruising altitudes for IAS/TAS calculations? A: This is a long-term goal. Accurately calculating IAS/TAS requires processing massive amounts of GFS weather data, which is a huge engineering challenge. I am currently researching solutions like the Open-Meteo API, but this feature is still in the research & development phase.

Q: Why does the OpenAIP layer sometimes disappear on RadarView but works fine on ATCView? A: This is a complex issue related to rate-limiting from the OpenAIP service. The two views use different data fetching methods. ATCView uses the API for selected data which is then cached on my server. While a recent update introduced caching for RadarView tiles which has improved the situation, a permanent solution depends on external factors. I am continuing to monitor and work on this.

Q: Why are weather layers limited to Feeders and Testers? Why are you avoiding the term "Patrons"? A: The weather data provider offers a generous free plan for non-commercial projects. Once PayPal is enabled, RadarView will be considered a "commercial" service according to their license, and I will have to move to a paid "pay-as-you-go" plan. Therefore, this feature will ultimately be a benefit for all Supporters (Feeders, Testers, and Patrons) to help cover these new operational costs. The initial limitation is simply to align with the current non-commercial status of the project.

Q: Why did you choose a custom PayPal integration instead of Patreon, Patronite, etc.? A: The key is automation. A direct PayPal integration gives me access to an API and Webhooks that allow for a seamless, fully automated process of granting and revoking access based on a user's subscription status. While platforms like Patreon are excellent, their technical integration for this kind of real-time, automated access control is significantly more complex for a solo developer to manage.

Back to top