wttr.in out of datasource capacity about wttr.in

[chubin]

The query limits are removed now.

[skip-]

Please excuse the above if you did implement caching. I didn't see it when I read through srv.py but perhaps it is implemented in wego or some other dependency.

I did go to worldweatheronline.com and found in their FAQ the following entry requesting that free API users cache requests in 15 minute intervals (even longer than I was thinking):

Is there a limit on the number of weather data requests per day for Free API users?

Our free weather API users have a limit of 250 requests per day.

We also request the proper caching of data before new requests for same location are made within 15 minutes.

[chubin]

see also: #9

[alexellis]

Is there a rate limit on the public service?

[chubin]

@alexellis Yes, but it can be hardly reached. Why? Are you experiencing some problems currently?

[alexellis]

Curious how much it can be used by an individual user. 100 times? 1k times? 100k times?

I might accept it into the OpenFaaS Function Store

[chubin]

@alexellis currently we have the following limits (per IP):

# (minute, hour, day) limitations:
QUERY_LIMITS = (300, 3600, 24*3600)

but they will be increased soon

I've just gone through the issue you've mentioned, I would like to make a couple of remarks:

1. wttr.in supports configurable queries (/:help for that), you should consider making them configurable; via some additional function parameters etc;
2. wttr.in is translated into 60 languages, is should be configurable too;
3. wttr.in supports single line mode with many addtional data that can't be seen in the main mode (see: curl wttr.in/?format=3 for example)
4. Several new cool features (output formats) will be added soon