Oct 2024 - Migrated from OpenWeatherMap to Open-Meteo. Alerts now come from weather.gov.
- node
- Clone repo.
- Create a GeoNames account here.
- For personal use, add your
username
to.env
. - To protect your
username
, set up a proxy server that adds theusername
to requests.
- For personal use, add your
- To install depenencies, run
npm i
. - For local dev, run
npm run dev
.
Example: https://github.com/ehicks05/vaer-api
The idea is:
- someone visits vaer
- requests to 3rd party services that require auth are sent to vaer-api
- vaer-api takes the request, adds auth info, and sends it to the 3rd party
- vaer-api takes the response, and sends it back to the original requester
- open-meteo provides weather data
- weather.gov provides alerts and geolocation lat,long -> point data (city, state, timezone, etc...)
- geonames provides search by city name or zip -> geoname data (city, state, timezone, etc...)
- windy.com provides the map. would prefer something lighter that doesn't make so many requests
- openweather has basic maps that don't appear to include a base layer (land outlines, political names)
- NWS has maps, but menu ui takes up too much space when you embed it as a small widget.
Flow starts with either the device's geolocation, or a search term.
More info on Geonames search api here.
Open-meteo api here.
OpenWeather OneCall api here.