RainViewer will discontinue Jan 2026

[John-William]

Definitely! 100 percent right.

[Hubiug]

Hi, I understand that dealing with radar data is not your priority, however, I still thinks there might be something to be done here. Since your goal with Flowx is to focus on weather forecasting, I think one solution would be to add more nowcasting models. As far as I understand, most people who use RainViewer data in Flowx use it as a rain predictor or to assess model accuracy. There are far better radar apps for more in depth analysis(namely, RainViewer itself). I think nowcasting models could be an alternative to RainViewer data for that, even if they’re not completely comparable. There are still coverage issues, but that’s the same as with any forecasting models. I know Météo-France has the “AROME Prévision Immédiate” model, and I assume similar models exist for other regions. I imagine that implementing new models is easier than dealing with different radar sources, though I guess it really depends on each model.

On a side note, I think a forum post listing all available models as well as models planned for future implementation could be really useful. (Sorry if the information already exists, I couldn’t find it)

[duane]

Yes, exactly this. HRRR is an example and has composite, 1km and 4km radar. Arome Pi is on the todo list.

All models are planned I just don’t know when. I was just looking at JMA for models because I don’t have any high res models in that region.

I am also looking at temperature, wind, humidity, etc… at higher altitudes - I am part way through adding this.

[Psamathe]

@duane

I have three options:

1. Pay for radar data. It already exists. <— I can’t justify spending money on radar data.
   …

I would see nothing wrong with FlowX having a number of additional add-in licenses/subscriptions. Presented to users as options "Unfortunately some providers of some data change significant costs for access to that data. Thus if a user wishes to add such data we must change an additional license fee".

Maybe even RainViewer might be open to continuing access on some sort of “profit share” from additional licenses? If not charge to reflect your own increased costs. I feel the same additional licenses quite reasonable pactice for any useful data sources that charge for access (ie not just rainfall reflectivity/radar).

Of course this does not consider the additional development work (but eg RainViewer work already done).

[duane]

I’ll keep saying it - it’s a lot of work that distracts from Flowx’s core strengths.

Regarding other API, they charge a minimum price with API limits per month, e.g., 990 EUR/year 1 million queries at 10 request per second.

Foreca Weather API

At 10 requests per second, you cannot serve Flowx users. I don’t know how many users will buy, I don’t know how much they will user it, so how do I price that???

If they allowed me to process the data to my servers, at 10 request per second, it’ll take 9 minutes to process a global radar image. But they don’t have a global image, so I’ll have to stitch them together… things are not that simple.

Pricing is not that simple. But RainViewer cost $22/year NZD - about the same as Flowx. Let assume I can get radar data into Flowx for the same price, i.e., the additional license you suggest. Why would users in the USA pay an extra $20 for radar data they can get in HRRR??

RainViewer is discontinuing their service because they don’t see at being viable. They are not going to keep the service running for one customer. Oleksii and the RainViewer team have been kind to Flowx over the years, I trust their decision and won’t question or pressure them.

[duane]

I don’t know how else to say this. It is extremely unlikely radar will be replaced.

If users cancel subscription because of this, that is their choice and I’m fine with that.

If everyone cancels their subscription because of this, then clearly I wasted 14 years working on weather simulation data when radar was the only reason they used Flowx. Given 90%+ of users are free users and don’t have radar, I don’t think this is the case.

If you want to understand more:

• add a place in the USA that has rains, e.g., New York,
• go to HRRR
• add the “Radar Menu” to the map menu
• toggle between Rainviewer reflectivity and HRRR Composite reflectivity

The HRRR radar goes into the future too.

Why would I spend time and money, when Flowx is not covering costs, to replace something HRRR Composite can nearly match??

---

I am not replying to this topic anymore. RainViewer Radar Refelctivity will not be replaced.

[Psamathe]

Sorry if you don’t like people coming up with sensible, courteous polite ideas. Most develop[ers would welcome such input even if they can’t accommodate it. As a s/w developer myself we welcome user input and ideas to broaden out product appeal.

[duane]

@duane

Also consider this. Radar data would likely cost thousands per year - let’s say $2000 per year (probably way more). This is equivalent to 100 subscriptions. Will Flowx lose 100 subscriptions due to radar disappearing? Probably not, because people don’t pay $20/year for the radar feature in Flowx when there are bigger and better radar apps out there. In conclusion, Flowx will lose money.

UKMO data costs around $2500 per year. Will I get 100-200 subscriptions to cover this cost? I don’t know but more likely than radar since people buy Flowx for this kind of data.

@duane

Here is a post by Oleksii from RainViewer:

Weather Radar APIs in 2025 | Rain Viewer Blog

Notice it has pricing. If a user viewed radar at 8pm for 15 days out of 30 days in a month. There might be 4 tiles required to cover the map view. With 10 minute time steps, that will be 6 frames per hour. Therefore, 12 months * 15 days * 20 hours * 6 time steps/hour * 4 frames * $0.2 / 1000 = $17 / year. This is conservative.

There is nothing wrong with suggesting ideas but I feel like I’m repeating myself and re-justifying my decisions.

This is why I don’t want to keep replying to this topic.

If something simple comes along I’ll consider it. In the meantime, I will spend my time adding data at altitude and adding more weather simulation forecasts, like the Japan, the Korean and possibly the AI models. Takes less time, less cost and more impactful.

[mrnano]

@duane

I will spend my time adding data at altitude and adding more weather simulation forecasts, like the Japan, the Korean and possibly the AI models.

This is truly wonderful news for me!!!
I’ve been subscribing and waiting for a long time!!
Please add models for Koreans and Asian people.

[BrianLY-38]

@mrnano Hello and Welcome to the Forum and Thank you for Using Flowx

[duane]

BTW everyone, RainViewer has extended their service to the end of January now which is why you still see the radar reflectivity data.

[Alex]

EURADCLIM (EUropean RADar CLIMatology) dataset, which is a key, high-resolution gauge-adjusted radar precipitation dataset for Europe, is generally considered publicly available and free to use.
Not global.

[andrelevy]

@duane

I should spend the money I don’t have buying weather simulation data like the UKMO model or the Australia BOM ACCESS models.

Yes, please! Or, alternatively, you make the API connector to the data something like a “community extension” that users can add to flowx so they can legally download forecast data for their own free non-commercial use.

[duane]

How does Flowx make money off this API?

[andrelevy]

Either/or: either you resell data, as I’ve been suggesting, or you sell functionality (as you already do). If you choose to resell data, you can resell ACCESS through flowx as a premium addon, but since you said you can hardly justify paying for it, and you’ve chosen thus far the functionality revenue model, to make it freely available on the app while not incurring its cost, you can make it as if it’s something the user is plugging directly into the flowx GUI, not intermediated by you. That’s the loophole stremio exploits to stay on the appstores, with their community add-ons. Right now I can get ACCESS-C (1.5km) on Windy, but I’d much rather see it on flowx.

[duane]

It’s not as simple as you describe. You can’t just decide “Either/or”. “Either/or” might be months of work for no return. I have totally wasted time adding a feature no one used.

I have a list of 10+ free data sources I can add right now. The issue is time. Why would I spend money buying data that I have no idea whether I can cover its cost, when I can add free data? The issue is time.

I understand you are tying to make suggestions, but it’s not as simple as you think, otherwise it would be done.

BTW, the founder of Windy is worth a billion. He can pay $150,000 Euro per year, and did, without much risk. Ivo Lukačovič - Wikipedia

Windy was built on existing open-source code from: https://earth.nullschool.net

It’s not as simple as you think. You should try making a weather app, releasing it and making a single dollar. When I started, I would be luck to make $0.23 cents a week. Flowx was reviewed New York Times and I only knew because it make $3+ in one day!!!