Rapid account: Joey Kyber

Joey Kyber / joeykyber

Discussions

8
Title
Created at (Click to sort ascending)
A
1
The API can get forecast data from any resort on snow-forecast.com: https://www.snow-forecast.com/countries. There is currently no endpoint for retrieving a list of all resorts. Thu 10:18 25/1/24
A
7
@SJVARIJAO You're welcome! And yes, that's basically all it does. The client sends a resort name to the API, then the API scrapes Google to find the correct snow-forecast.com URL (this method allows most resorts to be found even with incorrect spelling, which means it'd work great in sites that have the user searching for resorts themselves). If a URL is found, it will then scrape that page and send the data back to the client in an organized object. You can include the optional query parameters in the fetch request, which will result in a smaller response object. The more optional parameters you use, the quicker the response will be. Also, the results are cached for a certain amount of time, so if you search for the same resort like 10 times in a row, the last 9 responses will be basically instantaneous. Wed 5:11 18/10/23
A
7
@SJVARIJAO You're welcome! And yes, that's basically all it does. The client sends a resort name to the API, then the API scrapes Google to find the correct snow-forecast.com URL (this method allows most resorts to be found even with incorrect spelling, which means it'd work great in sites that have the user searching for resorts themselves). If a URL is found, it will then scrape that page and send the data back to the client in an organized object. You can include the optional query parameters in the fetch request, which will result in a smaller response object. The more optional parameters you use, the quicker the response will be. Also, the results are cached for a certain amount of time, so if you search for the same resort like 10 times in a row, the last 9 responses will be basically instantaneous. Wed 5:11 18/10/23
A
7
@SJVARIJAO You're welcome! And yes, that's basically all it does. The client sends a resort name to the API, then the API scrapes Google to find the correct snow-forecast.com URL (this method allows most resorts to be found even with incorrect spelling, which means it'd work great in sites that have the user searching for resorts themselves). If a URL is found, it will then scrape that page and send the data back to the client in an organized object. You can include the optional query parameters in the fetch request, which will result in a smaller response object. The more optional parameters you use, the quicker the response will be. Also, the results are cached for a certain amount of time, so if you search for the same resort like 10 times in a row, the last 9 responses will be basically instantaneous. Wed 5:11 18/10/23
A
7
@SJVARIJAO You're welcome! And yes, that's basically all it does. The client sends a resort name to the API, then the API scrapes Google to find the correct snow-forecast.com URL (this method allows most resorts to be found even with incorrect spelling, which means it'd work great in sites that have the user searching for resorts themselves). If a URL is found, it will then scrape that page and send the data back to the client in an organized object. You can include the optional query parameters in the fetch request, which will result in a smaller response object. The more optional parameters you use, the quicker the response will be. Also, the results are cached for a certain amount of time, so if you search for the same resort like 10 times in a row, the last 9 responses will be basically instantaneous. Wed 5:11 18/10/23
A
3
Actually I have another web-app (just a personal project) that scrapes forecast data for just USA resorts and the site I was scraping from completely changed into something else, so that API and data set would actually be super helpful for getting the app back up and working! I might also find a way to integrate the NWS API and the data set into this API in the future, but I don't have any plans for that atm. Thu 3:27 23/2/23