https://github.com/martinschneider/openweathermap

JAVA demo for the OpenWeatherMap API
https://github.com/martinschneider/openweathermap

Last synced: 25 days ago
JSON representation

JAVA demo for the OpenWeatherMap API

• Host: GitHub
• URL: https://github.com/martinschneider/openweathermap
• Owner: martinschneider
• Created: 2017-07-02T22:54:01.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2018-03-15T06:12:46.000Z (almost 7 years ago)
• Last Synced: 2024-11-08T11:56:40.668Z (3 months ago)
• Language: Java
• Homepage:
• Size: 4.15 MB
• Stars: 1
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Preconditions

1. Get an API key for OpenWeatherMap and set it in application.properties:

```

openweathermap.api = xxx

```

2. Set the database properties in application.properties:

```

jdbc.url = jdbc:mysql://localhost:3306/weather

jdbc.username = 

jdbc.password = 

```

# Usage

1. Build the project and deploy it in an in-memory Tomcat:

```sh

$ mvn clean install tomcat7:run

```

2. In your browser navigate to

```

localhost:9090

```

Alternatively, you can use mvn clean install and deploy the WAR-file in any standalone Tomcat.

# First steps

* Click on "Update weather data" to fetch the current weather for all cities configured in the database. Note, that 10 cities are initialized on setting up the context. 

# Limitations (and possible improvements)

* Weather data is limited to one entry per city and date. If data is fetched again any existing data for the same day is overwritten.

* If a city is removed all weather data for the city is removed as well and no more weather data will be queried for it. This could be configurable, e.g. allow disabling a city for future updates while still keeping historic data.

* All weather data is fetched by city name (vs. city id, which the API also supports). For this reason bulk requests are currently not used although some parts of it have been implemented (see the javadoc for comments on what changes would be necessary).

* Filtering (searching) and sorting is currently done on the frontend. This is not suitable for larger amounts of data.

* hibernate.hbm2ddl.auto = update is used which is apparently not the right choice in a productive setup. Use Liquibase (or similar) for DB versioning

* Detailed error handling and handling of invalid/faulty data from the API is not implemented! What is handled are invalid city names.

* Unit tests need to be extended!