Live data from Hacker News

Show HN: Weather API for non-commercial use

open-meteo.com

141–150 of 154 posts

Re: Show HN: Weather API for non-commercial use

#141
post #76
post #39

Earlier quoted context omitted.

If you're referring to https://uw.leftium.com/ , tap the temperature in landscape mode ;) The app defaults to F because it gives the more "human" temperature range.

This doesn't seem to work on desktop? I've never heard of F as the more 'human' temperature range. Don't you either use C or F. Since I've never used F it doesn't seem more human to me.

I found the exact timestamp in the video, but MKBDH actually didn't explain it very well.

So I found some other articles that articulate why F is better for weather: https://news.ycombinator.com/item?id=28524505

Re: Show HN: Weather API for non-commercial use

#142
post #39

Earlier quoted context omitted.

If you're referring to https://uw.leftium.com/ , tap the temperature in landscape mode ;) The app defaults to F because it gives the more "human" temperature range.

> The app defaults to F because it gives the more "human" temperature range. It because you are american. For europeans using celsius this is more like hieroglyphs (but I understand it works same other way around).

I've learned to use both C/F (although I admit I am more accustomed to F).

More detailed arguments for F for weather here: https://news.ycombinator.com/item?id=28524505

Merits of Metric vs. Imperial generalized:

- Metric: science-based, regular (powers of 10)

- Imperial: human-scaled, divisible (many divisors, including 3) An inch is about the breadth of a human thumb, and a foot is 12 inches. (Also about the length of a human foot.)

For example, a surfer says "if you measure wave height in metres or cm it is not as accurate compared to the human body (a 6ft wave is under 2 m and we would not call a wave 182.88 cm high)"

edit: length -> breadth

Re: Show HN: Weather API for non-commercial use

#143
post #70

Earlier quoted context omitted.

I don't have an application per se, but I'd like to see the historical temps and rainfall for my town of the past... 20 years? :) I've seen pages like Weather Spark that give you historical averages, but I would like to see how the weather has (or not) changed over a long period.

As linked from elsewhere in the thread: https://oikolab.com/

Thanks!

Re: Show HN: Weather API for non-commercial use

#144

I like the UI generating the URL to send to the API vs just a PDF of all of the possible key/value pairs to generate manually. A little above&beyond for most APIs I've used personally. Its effort not lost on me.

Glad you like it! Bootstrap v5 helped a lot :) I hope to improve the UX a bit further with a city-search for example. Unfortunately I am lacking a good geocoding API for that.

I've been using the GeoLite2 [0] downloadable database as a fallback for CoreLocation in my macOS app for changing monitor brightness based on the sun position [1].

It works well and with zero maintenance if you use their auto-updating Docker image [2].

[0] https://dev.maxmind.com/geoip/geolite2-free-geolocation-data

[1] https://lunar.fyi

[2] https://hub.docker.com/r/maxmindinc/geoipupdate

Re: Show HN: Weather API for non-commercial use

#145
post #95

Earlier quoted context omitted.

You can check the Norwegian service Yr.no. https://www.yr.no/en/details/table/2-1263968/India/Tamil%20N... https://hjelp.yr.no/hc/en-us/articles/360001940793-Free-weat...

Thanks, this is one of the more accurate ones I've seen, it's still a bit off (3-4 degrees). Do you know where I can get historical data going back at least 10 years?

yr.no/met.no are using the Arome-model for Scandinavia and Baltic states (It is a cooperation between the states,shearing HPC's and human resources), and the ECMWF model for the rest of the world

Re: Show HN: Weather API for non-commercial use

#146
This looks like the API I was looking for to compute the best screen brightness in the absence of a light sensor in Lunar [0]

I would probably do a request per day for each user of this feature, which would amount to about 300-400 requests/day. Would that fit in the non-commercial use tier?

I would be happy to start paying like $5/month if I'll find a way to improve the brightness calculation logic with your API. If you don't yet have a payment processor integrated, maybe we can work it out through something simpler like Patreon or Buy me a coffee recurring payments.

What I'm not sure about is what data would best fit my needs. I was thinking of using Cloud Cover first but I don't know which one would affect the daylight perceived brightness:

    cloudcover
    cloudcover_low
    cloudcover_mid
    cloudcover_high
There's also the (new to me) sun radiation data which seems even more fitting to what I need, but again, not sure which one to use:

    shortwave_radiation
    direct_radiation
    diffuse_radiation
I would guess that direct_radiation is what I need but I thought I should ask first in case you have more insight into what data would most fit my use case.

[0] https://lunar.fyi/#location

Re: Show HN: Weather API for non-commercial use

#147

Earlier quoted context omitted.

Thanks, this is one of the more accurate ones I've seen, it's still a bit off (3-4 degrees). Do you know where I can get historical data going back at least 10 years?

I run a service ( https://oikolab.com ) that has hourly data going back 70 years.

How do I contact you? My email is in my profile.

Re: Show HN: Weather API for non-commercial use

#149

Earlier quoted context omitted.

I run a service ( https://oikolab.com ) that has hourly data going back 70 years.

How do I contact you? My email is in my profile.

Got it - will send you an email to connect.

Re: Show HN: Weather API for non-commercial use

#150

Earlier quoted context omitted.

Curious how much this would cost you to do from Google cloud storage or aws. Historical data access can be quite valuable (and something that might be a premium paid feature even).

For the VMs, the absolut minimum memory requirement is 16GB. The more, the better. Otherwise it takes around 40 GB of disk space for every day of data. For an history of 100 days, 4000 GB are required. With compression I could save 50%, but have to invest a couple of days development time to make is work. You could calculate the AWS bill now ;-) Data on cold storage is an option, but it also super slow.... Currently,…

Curious if you could link directly to GCS standard storage and link to it directly - I don't know how slow, but could be reasonable compromise for historical access...

Interesting problem to solve.

Post reply on HN