Stop Blaming the "Weatherman"
developer.sealegs.ai
Stop Blaming the "Weatherman"
1–5 of 5 posts
Re: Stop Blaming the "Weatherman"
#2I like the concept, but the blog post describes a USP which I can't see in the API.
> "Our approach uses AI to do what humans try to do…"
> "factor in your vessel type and planned route"
Have I misread the API, or are routes and vessel-types part of a future planned capability?
Re: Stop Blaming the "Weatherman"
#3I like the concept, but the blog post describes a USP which I can't see in the API. > "Our approach uses AI to do what humans try to do…" > "factor in your vessel type and planned route" The API describes a single latitude parameter and longitude parameter, rather than a route, and doesn't appear to accommodate vessel type. Have I misread the API, or are routes and vessel-types part of a future planned capability?
The SpotCast capability does accept that information (which is how it's used in the app). I need to expose it in the docs, thanks for pointing it out. Will update shortly.
Re: Stop Blaming the "Weatherman"
#4I like the concept, but the blog post describes a USP which I can't see in the API. > "Our approach uses AI to do what humans try to do…" > "factor in your vessel type and planned route" The API describes a single latitude parameter and longitude parameter, rather than a route, and doesn't appear to accommodate vessel type. Have I misread the API, or are routes and vessel-types part of a future planned capability?
Regarding your other question about routes...in the app that is what is called a TripCast where you enter the departure and destination locations and it will determine the forecast for that trip. TripCasts are not currently exposed in the API, just the SpotCasts capability right now which we felt would have broader appeal. Exposing TripCasts in the API is a planned capability and if there is demand for it, we can expose sooner than later.
Re: Stop Blaming the "Weatherman"
#5I like the concept, but the blog post describes a USP which I can't see in the API. > "Our approach uses AI to do what humans try to do…" > "factor in your vessel type and planned route" The API describes a single latitude parameter and longitude parameter, rather than a route, and doesn't appear to accommodate vessel type. Have I misread the API, or are routes and vessel-types part of a future planned capability?
The SpotCast capability does accept that information (which is how it's used in the app). I need to expose it in the docs, thanks for pointing it out. Will update shortly.
Thanks for updating the docs[1] with the vessel parameter, I may take this for a spin.
I'd also find it valuable if the AI might accomodate context for the trip - some examples: "scuba diving", "fishing", "match racing", "touring". Do you think that's feasible with the models you have available?
[1] Link to the Spotcast API docs for future HN readers: https://developer.sealegs.ai/docs/spotcast.html