An android app for the national weather service.

License: GNU General Public License v3.0

Kotlin 58.74% Java 41.26%

national-weather-service-android-app's Introduction

Go to ideas ➡️

🥇 Open Source Ideas have proudly led to 11 projects coming to fruition in a perfect harmony of talent and the open source spirit, and has over 200 ideas for those looking for a new project!

💡 Open Source Ideas

For many working with Open Source, good ideas or cool projects aren't the limiting factor. Time is. But there are a lot of different people out there with various levels of experience and background. Some want to create open source projects, but don't know where to start or what to create. Why don't we solve both of these problems with each other's help? 🐦 🐔 💥

Welcome to Open Source Ideas! 👋 This is a crowdsourced collection of open source ideas you can take inspiration from, join, or encourage others to attempt! The community is fueled by the dedicated contributors like yourself, and each and every idea is greatly appreciated!

If you would like to take a look at the existing ideas, head on over to the issues page! We've also labelled and tagged every issue to make it easier for people like yourself to find them!

Tags and filters

💪 Want to put in a minimal effort? Or perhaps build a rocketship? Got little time? Got a lot of time? Filter by estimated workload here!

🧑‍💼 Are you just starting your programming carreer? Or are you taking a break from your senior backend developer position? Filter by difficulty?

🧐 Are you a sucker for the grand Internet of Things? Or perhaps you want to whip out your favorite OCR library and recognise some L's? Check out all our available categories!

If you're curious what other projects have started from this community, take a look at the Hall of Fame!

Let's show what open in Open Source means by creating a welcoming, inclusive and supportive community for all that want to be involved. My hope is that we can get more people involved with Open Source, learning the customary behavior and continuing to drive the open community forward. Read more about the initiative in the blog post.

This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code.

I've got an idea to share

If there is anyone with cool ideas for projects and doesn't have the time to create them, post it as an issue on this repo, mark it with the appropriate label(s) and advertise it if you so please.

Try to include as much information as needed to implement the project, and be open to answering questions if necessary. Add a label to the project for whether it is estimated to be Little work, Medium work or Much work.
Also, try to answer the issue template as correctly as possible. If the project is perfect for first-timers, label the issue as First Contribute.
Finally, try to label the issue with the most appropriate tech categor(y|ies) to attract excited, motivated developers to your idea! (see list above)

I want to create a project

If you are Open Source-curious or just looking for your next project, you can look through the Issue-list and pick one of your liking. If anything captures your imagination, you can join the issue by commenting on it. If there are people who want to cooperate, that's fantastic. Just submit a comment and the person who created the issue can answer.

Feel free to keep the issue updated with the progress of the project and ask for help if needed. When the project is finished/published, add a link to the published project and the issue can be closed (and you & your teammates will make the Completed Hall of Fame below!)

If it already exists

As is often the case with Open Source, a project already exists, but people aren't aware that it does. If there are any issues opened that already exist in the real world, let us know and the issue will be closed (with a link to the existing project for people to use).

Completed Hall of Fame

HamzaEzzRa/Multishot

✅ Completed by @HamzaEzzRa
❤️ Pitched in issue #234 by @AdrienDS

roymoran/page

✅ Completed by @roymoran
❤️ Pitched in issue #271 by @roymoran
🚀 Website pagecli.com

AmruthPillai/All-The-Words-That-I-Know

✅ Completed by @AmruthPillai
❤️ Pitched in issue #204 by @xenotropic

azz-eddine/nws_webapp

✅ Completed by @azz-eddine
❤️ Pitched in issue #74 by @xenotropic
🚀 Website nws.overnightproject.com/

projectunic0rn/pub

✅ Completed by @rmjordas, @rickywid, @aaron2212, @roymoran
❤️ Pitched in issue #195 by @roymoran
🚀 Website projectunicorn.net

fredrikaugust/bulk-renamer

✅ Completed by @fredrikaugust
❤️ Pitched in issue #149 by @KOLANICH

bsonntag/npm-notifier

✅ Completed by @bsonntag
❤️ Pitched in issue #6 by @mikaelbr

twobucks/slack-message

✅ Completed by @dinodsaurus
❤️ Pitched in issue #2 by @mikaelbr

kencrocken/FiraCodeiScript

✅ Completed by @kencrocken
❤️ Pitched in issue #10 by @mikaelbr

mikaelbr/open-source-ideas

✅ Completed by @FredrikAugust
❤️ Pitched in issue #1 by @mikaelbr

national-weather-service-android-app's People

Contributors

Stargazers

Watchers

Forkers

ppeters0502 coolprojects nsqtr

national-weather-service-android-app's Issues

Partial view to show 5 day forecast

After talking on the slack server, we decided that the app should have a main view that is consisted of smaller partial views that show the current forecast, hourly, 5 day and 10 day forecast. This specific issue is to track the partial view for the 5 day forecast.
Issue entails API connection to NWS with coordinates (use test coordinates) then pulling the 5 day forecast with the grid points or zone that is returned from the lat/long request (see FAQ page of https://www.weather.gov/documentation/services-web-api). Take the data returned from the request, and stuff it into a view in the meantime. Doesn't need to be styled or fancy yet, we're still working through how we want all of the data displayed.

Partial view to show 10 day forecast

After talking on the slack server, we decided that the app should have a main view that is consisted of smaller partial views that show the current forecast, hourly, 5 day and 10 day forecast. This specific issue is to track the partial view for the 5 day forecast.
This one should be very similar to the 5 day forecast issue, since they both pull from the same API endpoint. Issue entails API connection to NWS with coordinates (use test coordinates) then pulling the 10 day forecast with the grid points or zone that is returned from the lat/long request (see FAQ page of https://www.weather.gov/documentation/services-web-api). Take the data returned from the request, and stuff it into a view in the meantime. Doesn't need to be styled or fancy yet, we're still working through how we want all of the data displayed.

Current location integration with Android Location/Google Maps

Currently working on integrating with Google maps, so that longitude and latitude that are supplied to API call come from current location rather than manual entry.

Model Classes for gridPoints, forecasts, and alerts

(You can find this data in the Contributing markup, or at https://www.weather.gov/documentation/services-web-api)

To check the weather for your area, you first have to supply lat and long coordinates to https://api.weather.gov/points/ to grab your forecast zone. So if I'm in New York City, for example, I can find my forecast zone by hitting https://api.weather.gov/points/40.6171,-74.0133.

Once you can lookup your forecast zone, you can call for either a 7 day forecast (https://api.weather.gov/gridpoints/OKX/33,30/forecast for example), an hourly forecast (https://api.weather.gov/gridpoints/OKX/33,30/forecast/hourly) or you can check your station for weather alerts (https://api.weather.gov/alerts/active/zone/NYZ075).

We need classes in the model of the MVP pattern to store the data you can obtain from these API calls. These classes will eventually be the middlemen between the DataManager, and the database helpers, so all of the MVP logic is removed from these classes, which makes them great for a first issue! We'll need a gridPoint class that has relevant data (such as the forecastZoneID, lat/long, and URLs for grabbing the different forecasts), a forecast class that has relevant data from the 2 forecast API calls (feel free to leave comments on what should be "relevant data"), and an alert class for relevant data on any alerts that are in a zone requested from the API call.

Feel free to leave comments if you want to take this issue on, or if you have questions. Be sure to hit the example API URLs mentioned above to get a good idea of the relevant data we can grab from the API requests!

Partial View to show current forecast of location

After talking on the slack server, we decided that the app should have a main view that is consisted of smaller partial views that show the current forecast, hourly, 5 day and 10 day forecast. This specific issue is to track the partial view for the current forecast.
Issue entails making the API connection to NWS with coordinates (use test coordinates for now), pulling the current forecast (in the properties returned, look for "shortForecast") and displaying it in a view. Nothing fancy yet, since we're still figuring out how we want everything displayed just display the text.

Partial view to show hourly forecast

After talking on the slack server, we decided that the app should have a main view that is consisted of smaller partial views that show the current forecast, hourly, 5 day and 10 day forecast. This specific issue is to track the partial view for the hourly forecast.
Issue entails making the API connection to NWS with coordinates (use test coordinates for now), pulling the hourly forecast ( https://api.weather.gov/points/{point}/forecast/hourly) and displaying it in a view. Nothing fancy yet, just display the text.
API reference page: https://www.weather.gov/documentation/services-web-api

Support for storing multiple locations to receive alerts from

I had an idea for giving the ability to store multiple locations that I could receive weather alerts from. So, for example, if I live in New York, but I have family living in New Orleans, or Chicago, I could store their location information in the app as well, and receive alerts if there is severe weather in their location.
Mainly wanted to put it up here to remember it, I know we're not there yet, and this issue probably wouldn't be worked on for a while.
Any thoughts on this?

open-source-ideas / national-weather-service-android-app Goto Github PK