Comments on: Adding Local Weather Conditions To Your App (Part 2/2: Accessing Google’s XML Weather API)

By: soch

soch — Fri, 05 Apr 2013 15:46:00 +0000

I understand the mission, but currently how many weather stations in US do you collect data from. I am interested in accurate current weather and forecast. I get this info fairly easily in JSON format from NOAA.

By: Metwit

Metwit — Fri, 05 Apr 2013 08:04:00 +0000

Hello, sorry for the late response, but if you don’t hit reply it won’t trigger a notification to me. The crowdsourced data in /weather API is used to enhance the accuracy, but it isn’t the only source. One of our mission is to aggregate as many sources as possibile and let access to them with a single simple unified endpoint. If you have any trouble please shot an email to us and we’re glad to help 😉

By: soch

soch — Wed, 03 Apr 2013 10:26:00 +0000

Also it would be good to see a sample app to see the coverage in US. Looks like you rely only on end users submitting the weather data, if so, it would mean very less information on weather would be available during late nights (as every one is asleep ;-(), also it may not be accurate and may not have all the variables (like relative humidity, dew point, wind speed, and other numerous detailed weather conditions).

By: soch

soch — Wed, 03 Apr 2013 10:19:00 +0000

Thats good. How many weather stations data do you have? Are there any other restrictions I should be aware of before using the api for iOS?

By: Metwit

Metwit — Wed, 03 Apr 2013 09:29:00 +0000

200 calls per day per IP are enough if you made these calls client side. Anyway please send me at info(AT)metwit.com and I’m sure we can sort it out 😉

By: soch

soch — Tue, 02 Apr 2013 23:27:00 +0000

200 calls per day

That’s too less. I will stick to NOAA.

By: Vijay Sridhar

Vijay Sridhar — Tue, 02 Apr 2013 23:12:00 +0000

Yeah I agree, I wrote that message a while back but have switched to the NOAA now. Like you said it was a very easy transition but MUCH more accurate forecasts.

By: soch

soch — Tue, 02 Apr 2013 23:09:00 +0000

Nah. For US I would stick with NOAA, it’s not that hard also there is no usage limitation(worldweatheronline.com) or unnecessary display of logo for the source data (e.g. accuwether). 99% of iOS my app revenue is from US only. I will worry of the 1% revenue (from Europe, India, etc) later.

By: soch

soch — Tue, 02 Apr 2013 23:02:00 +0000

What is the cost & usage limit & restrictions, if any?

By: Howdy Clowdy

Howdy Clowdy — Tue, 29 Jan 2013 12:18:00 +0000

Howdy,

if you are looking for a *weather API* I have a suggestion for you!

I made a [Weather API][1] available on mashape, and they have a ready to use simple obj-c SDK.

This api is really simple to use because we use the cool standards that are available nowadays, like JSON and REST, while our competitors still use legacy SOAP/XML systems.

Speaking about the quality of data Metwit (my “company”) born as a crowdsourced platform for gathering real-time weather reports from real people. After more then ten thousand users started to using our apps and send a massive amount of reports,

we decided to release those precious reports through our APIs.

We also act as single gateway for multiple, hard to parse, sources of forecasts like NOAA, and we’re enhancing them with social data like photos, tweets, etc., that we leverage from existing social networks.

If you like it please give it a try on [mashape][2]!

[1]: http://metwit.com/developers/

[2]: http://www.mashape.com/metwit/weather-and-forecast