3 ms·
I do use a service for getting the weather (backend: https://github.com/blixt/sol-mate https://github.com/blixt/sol-mate) Yeah the second part I consider a bon
by blixt 2y ago
I do use a service for getting the weather (backend: https://github.com/blixt/sol-mate https://github.com/blixt/sol-mate)
Yeah the second part I consider a bonus. Especially because I can use street names or slang for locations that no rigid API supports.
> Taken together, it sounds like you're blindly trusting the coordinates generated by AI
Actually I guess I do "blindly" trust the AI's coordinates more than a traditional location search service. Not sure how much you've tested it yourself, but I haven't gotten a single false latitude/longitude pair from GPT-4 unless the location was truly ambiguous, in which case it would be one of them. But as a European, I've definitely experienced rigid APIs happily giving me the weather for "Stockholm, NY" which apparently does exist, but wouldn't have been my first option...
But yeah, it is just a fun app, so I wouldn't want to make it more rigid either way!
- itishappy 2y agoHave you stress tested it? "Springfield" is a very common name in the US. I'd love to know how it handles "Sandwich" as well. Again, probably overboard for a fun app!
- blixt 2y agoThey're fair questions, and yeah it will have to disambiguate in such cases. I tried it now and it picked: - Springfield in Illinois - Sandwich in Massachusetts (the exact coords: https://www.google.com/maps/place/41%C2%B045'31.0%22N+70%C2%B029'36.2%22W https://www.google.com/maps/place/41%C2%B045'31.0%22N+70%C2%...) I think that people underestimate how much non-AI technology fails in these cases. And the recovery path is to retry with more specificity in either case.
- itishappy 2y ago> I think that people underestimate how much non-AI technology fails in these cases. That's an excellent point! Just browsed through your code and I see that you're calculating the positions of the sun and moon. Very cool! Really fun project!