johnluetke / weatherapi Goto Github PK

View Code? Open in Web Editor NEW

14.0 14.0 4.0 665 KB

Abstracts online weather services into a simple API

License: Apache License 2.0

C# 40.04% Java 59.96%

weatherapi's People

Contributors

Stargazers

Watchers

Forkers

mjschultz kboliver omt66 aalekh

weatherapi's Issues

Need to URI encode city names

Otherwise have to do currently:

IWeather weather = WeatherAPI.getWeather("New%20York%20City", "NY");

Issue using WeatherAPI from Gradle

WeatherAPI in turn depends on org.reflections, which has a Maven profile-based dependency on javassist. Gradle does not support resolving placeholders in published POMs, so you get errors like:

FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all dependencies for configuration ':compile'.
> Could not resolve org.javassist:javassist:${javassist.version}.
Required by:
  :weatherenrich:0.1.0 > net.johnluetke.WeatherAPI:WeatherAPI:0.9.4 > org.reflections:reflections:0.9.9-RC2
 > Illegal character in path at index 55: http://repo1.maven.org/maven2/org/javassist/javassist /${javassist.version}/javassist-${javassist.version}.pom

Figure out how to include PGP_PASSWORD and PGP_SECRET_KEY in Travis build

Add a Scala API

We would be happy to contribute this if #8 and #9 are greenlit.

Integrate Wunderground as a provider

Because they provide historical data.

Happy to do this one.

Add LRU cache support

For high-volume environments like Hadoop and Storm, performing an API lookup for every record is a non-starter.

Therefore, it would be worth adding an LRU cache into the WeatherAPI. In Scala we normally use Twitter's LruMap but we could use the Java equivalent instead.

We take this approach in https://github.com/snowplow/scala-forex

Better Algorithm to select a provider

At present, the first provider that can fulfill the request is used, even if multiple providers can do so. Is this acceptable? Or should a second algorithm be implemented for when > 1 providers can fulfill a request?

More providers!

We need more weather providers. Please feel free to fork and implement one!

http://blog.programmableweb.com/2012/01/11/12-json-weather-apis/

getDegreesCelcius and getDegressFahrienhiet() misspelt

Typo in IWeather

    double getPercipitation();

Add ability to construct a new WeatherAPI instance with credentials

Because reading a WeatherAPI.properties on the classpath is too inflexible.

Add ability to get weather at <timestamp>

We are interested in using WeatherAPI as the foundation of a weather-enrichment for Snowplow (snowplow/snowplow#456).

A showstopper requirement is the ability to get the weather at a specific timestamp. If we are (re-processing) 3 months of events from a mobile game, the current weather in a given location is a non-starter.

Would you be open to updating the API to support a provided timestamp? We would be happy to help integrate a provider that provides time-based weather.