Use local cache
Created by: Carlos Suárez (bitseater)
Created by: khurshid-alam
It would be nice if the app can use a local cache, i.e. weather data stored in a local file. It could be a simple database or even a simple json file.
Thanks.
Imported comments:
By Carlos Suárez (bitseater) on 2018-02-20T16:24:00.000Z
Yes @khurshid-alam it will use the cache data in the next releases. Now i must fix some issues as soon as possible , for people who use Flatpak, so i need to commit a new release in these days.
By Carlos Suárez (bitseater) on 2018-02-20T08:40:59.000Z
Created by: khurshid-alam
@bitseater In case of offline will it use that cache data? I think it describes the problem in another issue.
By Carlos Suárez (bitseater) on 2018-02-19T19:55:26.000Z
@khurshid-alam , a simple view of data to copy and paste, to the next release. More features in the future. I close this issue.
By Carlos Suárez (bitseater) on 2018-02-19T19:53:52.000Z
I have added a simple screen with current weather data , showing a cache file with them. You can copy and paste these data, or you can save the cache file to another folder. In next release, I will develop this feature more deeply.
By Carlos Suárez (bitseater) on 2018-02-03T19:29:52.000Z
Created by: khurshid-alam
Awesome!
By Carlos Suárez (bitseater) on 2018-02-03T19:27:46.000Z
Good news @khurshid-alam . OWM accept to save the current query to local cache, in order to prevent numerous queries from same IP. I'm going to add a note to ROADMAP to include it as soon as possible.
By Carlos Suárez (bitseater) on 2018-02-03T19:22:13.000Z
Created by: khurshid-alam
No, not the entire weather history, some of them. I am talking about only current weather data...(and not all the data type but the most important one like temp, humidity, etc). Every-time the app updates the weather it should save/overwrite the data to a database.
By Carlos Suárez (bitseater) on 2018-02-03T19:12:02.000Z
Hi @khurshid-alam . Are you talking about saving each query to local database? or some of them? OpenWeatherMap API have an option to query historical data, but it's to expensive for normal users. The Term of Use of this API warns about keeping information historical to offer to users. I try to find another solution, preferably for free.