Lightning data (status?)

Feature Requests & Ideas
1

It’s not the first time discussed, and I’ve been laying low with this topic while the port to iOS was in high gear.

Now when radar via RainViewer’API is going away, I think there is reason to lift this question again.

How are the plans of adding lightning data to Flowx going?

1 Like
2

The reason I don’t have plans for Radar is because of priorities. RainViewer stopping didn’t remove any job from the list so I’m still busy with the same priorities. Planning to replace RainViewer would add more the current list of jobs.

2 Likes
3

I’m sorry if I came of as ignorant to the fact that “RainViewer stopping didn’t remove any job”.

I understand that, and also why you don’t have plans for replacing it.

The sadness for loosing radar in Flowx is not ment as any criticism towards you, but rated a sadness shared with you and the other users.

For me that was not the issue, but merely a context for my actual question:

How does the “current list of jobs” actually look like, or more precisely how much more of higher prio work is there before it can be possible to consider spending time om adding new features like lightning?

The reson for me bringing up lightning in the context of loosing radar is that it also is a type of data that is more “real”-time, and hence possible to use for validating forcast data for a given time and region.

My thinking is that perhaps the lightning data is available in a format that “less work” to handle compared to re-creating the work of the team at RainViewer.

Cheers!

1 Like
4

Lightning is not on the immediate plans.

My current focus is:

  • making the app faster, more efficient and more robust.
  • improve the data processing servers - for some reason they are flaky recently.
  • add HAFS hurricane data
  • add data at altitudes
  • add other data sources.
  • improve the widgets, even though I’m over working on the widgets.
2 Likes
5

Thanks for the update.

Sounds like a solid plan.

Keep up the good work!

Cheers!

1 Like