Fishing conditions on each day in each location are affected by the weather and solunar conditions on that day. Additionally, because water is an insulator that is affected by weather conditions for longer than a single day, the fishing conditions in each location are also affected by the weather conditions that occurred in that location in the recent past.
Accordingly, disclosed is a system and method for generating a location-specific and date-specific forecast (a forecast rating) indicative of future fishing conditions based on past and forecasted weather conditions. In some embodiments, the forecast rating may also be generated based on solunar conditions. Additionally, the system may also generate a seasonal forecast characterizing fishing conditions on a specific date as being indicative of one of a number of predetermined fishing seasons (e.g., early fall, fall, late fall, winter, pre-spawn, spawn, post-spawn, summer, “dog days”, etc.). The system may also identify recommended bait for the specific forecasted fishing conditions identified by the system. The system may identify recommended bait for the forecasted fishing conditions in locations that include specific structures, such as wood, weeds, and rock. The system may also identify a recommended fishing rod, a recommended reel type, and/or a recommended line type for each recommended bait as identified by the system. The system may also identify a recommend presentation (e.g., slow, medium speed, fast) for the specific forecasted fishing conditions. Finally, the system may also identify a recommend fishing location (within a generic body of water) for the specific forecasted fishing conditions.
Aspects of exemplary embodiments may be better understood with reference to the accompanying drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of exemplary embodiments.
Reference to the drawings illustrating various views of exemplary embodiments is now made. In the drawings and the description of the drawings herein, certain terminology is used for convenience only and is not to be taken as limiting the embodiments of the present invention. Furthermore, in the drawings and the description below, like numerals indicate like elements throughout.
The system 100 may be realized by software stored on a server 140 that is accessible to a user via one or more computer network 150 (e.g., the Internet). For example, the system may provide a software application (e.g., a web-based application, a desktop application, a smartphone application, etc.) that is executable by a user device 120 (e.g., a desktop computer 122, a tablet 124, a smartphone 116, etc.) or accessibly by the user device 120 (e.g., via an application programming interface). The software application may include a user interface that provides functionality for a user to specify a forecast date 106 and a forecast location 108. If the user device 120 is location-enabled, the system 100 may also receive information indicative of the location of the user device 120 and determine the forecast location 108 based on the location of the user device 120.
As described in detail below, the system 100 generates a forecast rating 180 indicative of future fishing conditions in the forecast location 108 specified by the user on the forecast date 106 specified by the user based on the forecasted weather conditions 136 in the forecast location 108 for the forecast date 106 as well as the past weather conditions 134 in the forecast location 108 during a time period before the forecast date 106. However, users may specify a forecast date 106 that is days and even weeks in the future. In those instances, some or all of the relevant time period before the forecast date 106 may not have occurred yet. Therefore, some or all of the “past” weather conditions 134 may actually be forecasted weather conditions 136 that are forecasted to occur in the forecast location 108 on a future date that is before the forecast date 106.
While the system 100 may be used to generate a forecast rating 180 that is broadly indicative of the conditions for fishing any fish in the forecast location 108 on the forecast date 106, the system 100 is particularly well suited to generate a bass forecast rating 180 indicative of bass fishing conditions because the process 200 described below captures the specific weather conditions 132 that affects bass fishing conditions over the specific time period that those weather conditions 132 continue to have an effect.
To generate the forecast rating 180 as described below, the system 100 may receive weather data 132, for example from a third party 130 via the Internet 150. As mentioned above, the weather data 132 may include past weather conditions 134 and forecasted weather conditions 136. Those weather conditions 134 and 136 may include the average daily temperature, wind speed, sky condition (e.g., clear, mostly sunny, partly cloudy, mostly cloudy, cloudy, overcast, etc.), precipitation (e.g., rain showers, rain, thunderstorm, etc.), daily maximum atmospheric pressure, the time (e.g., hour) of the daily maximum atmospheric pressure, the daily minimum atmospheric pressure, the time (e.g., hour) of the daily minimum atmospheric pressure, etc. The weather data 134 may be received, for example, from a government agency (e.g., the U.S. National Weather Service), a private weather information provider (e.g., AccuWeather, Inc.), etc.
The system 100 may receive the weather conditions 132 used to generate a location-specific and date-specific forecast rating 180 by outputting the forecast location 108 and the forecast date 106 to a third party 130 and receiving the weather conditions 132 for the forecast location 108 and the forecast date 106. Alternatively, the system 100 may receive past weather conditions 134 and forecasted weather conditions 136 for a large number of locations and store them in a database 160. In those embodiments, the system 100 may identify the weather conditions 132 for the forecast location 108 and the forecast date 106 by retrieving them from the database 160 of the system 100.
The system may also receive solunar data (for example, a lunar calendar as described below) from a third party 130 via the one or more networks 150 (e.g., the Internet).
The server 140 may be any hardware computing device having a hardware computer processor suitably configured to perform the functions described herein. The server 140 stores instructions for performing those functions and the data described below in non-transitory computer readable storage media.
As described in detail below with reference to
As described in detail below with reference to
As described in detail below with reference to
As described in detail below with reference to
As described in detail below with reference to
As described in detail below with reference to
As shown in
To generate the calculated forecast rating 340 for the forecast location 108 and forecast date 106 in step 330, the system 100 may adjust the base rating 320 based on the forecasted weather conditions 136 and past weather conditions 134 for the forecast location 108 and the forecast date 106. Therefore, as briefly mentioned above and described in detail below, the system 100 may calculate a pressure adjustment 480 (described below with reference to
The system may store a maximum forecast rating 360 and adjust the calculated forecast rating 340 in step 360, for example by making the forecast rating 180 equal to the maximum forecast rating 360 if the calculated forecast rating 340 is greater than the maximum forecast rating 360. In some embodiments, the system 100 may also store a minimum forecast rating and similarly make the forecast rating 180 equal to the minimum forecast rating if the calculated forecast rating 340 is below the minimum forecast rating. The system 100 may further impose upper and/or lower limits on any of the other calculated numerical metrics described herein.
Having generated a (numerical) forecast rating 180 for the forecast location 108 and the forecast date 106, the system 100 may also identify a description 380 describing the fishing conditions indicated by the forecast rating 180 in step 370. For example, the system 100 may store a plurality of predetermined descriptions 380 (e.g., “Tough”, “Fair”, “Good”, “Epic”), each associated with a predetermined numerical range 390 (e.g., an upper range 392, an upper middle range 394, a lower middle range 396, and a lower range 398, etc.), and identify the relevant description 380 for the forecast rating 180 by selecting the predetermined description 380 associated with the predetermined numerical range 390 that includes the forecast rating 180.
Depending on the time of year, however, different descriptions 380 may be applicable to the fishing conditions indicated by the same forecast rating 180. For instance, the same forecast rating 180 may be below average during one time of year while being significantly above average for another time of year. Therefore, as shown in
Each predetermined description 180 may also be associated with a predetermined color 388 used by the system 100 when displaying the forecast rating 180 and/or description 380 to the user, for example via a graphical user interface of the user device 120.
The system 100 may also store a plurality of predetermined categories 382, each associated with one or more of the predetermined numerical ranges 390. The category 382 may be broadly indicative of the fishing conditions indicated by the forecast rating 180 and may be used by the system 100, for example, to identify recommended baits, recommended fishing locations, and/or recommended presentations (as described below with reference to
As shown in
Each of the daily pressure components 440 may be based on pressure conditions (e.g., whether the atmospheric pressure was (or is forecasted to be) stable 432, falling 434, or rising 436 on that day) determined using the process 410. The system 100 may calculate the difference (ΔP 416) between the maximum atmospheric pressure 419 and the minimum atmospheric pressure 411 in step 415 determine that the atmospheric pressure was (or is forecasted to be) stable 432 in step 422 if the difference (ΔP) 416 is within a predetermined pressure threshold 423. The system 100 may determine that the atmospheric pressure was (or is forecasted to be) falling 434 in step 425 if the time 418 of the maximum atmospheric pressure 419 is before the time 412 of the minimum atmospheric pressure 411. On the other hand, the system 100 may determine that the atmospheric pressure was (or is forecasted to be) rising 437 in step 425 if the time 418 of the maximum atmospheric pressure 419 is after the time 412 of the minimum atmospheric pressure 411.
In the case of rising atmospheric pressure 437, the pressure component may also depend on whether the maximum atmospheric pressure 419 occurred (or is forecasted to occur) early or late in the day. To determine whether the maximum atmospheric pressure 419 occurred (or is forecasted to occur) early or late in the day, the system 100 may determine in step 427 whether the time 418 of the maximum atmospheric pressure 418 is before a predetermined time threshold 429.
The system 100 may store a plurality of predetermined pressure components 440 for each day (e.g., Day 0, Day −1, Day −2, etc.), pressure condition (e.g., falling 432, stable 434, or rising 437), and (in the case of rising pressure 437, for example) the time of day of the maximum pressure (e.g., early 436 or late 438). The system 100 may store different predetermined pressure components 440 for the same pressure condition depending on the day 106, 405, or 404. For example, falling pressure 432 may have a different impact on fishing conditions on the forecast day 106 (Day 0) than falling pressure 432 occurring on either of the previous days 405 or 404. At the same time, the system 100 may store and use the same predetermined pressure component 440 for different conditions on different days. For example, the same predetermined pressure component 440 may be used to characterize rising pressure early 436 on the forecast date 106 (Day 0) or late 438 on the day before 405 (Day −1).
To calculate the pressure component 440 for each day, the system may select the predetermined pressure component 440 associated with the pressure condition (and time of day of the maximum pressure) determined for that day. Again, the system 100 may generate the calculated pressure adjustment 460 in step 450 by calculating the sum of the pressure components 440 for each day. The system 100 may compare the calculated pressure adjustment 460 to an upper limit 479 and/or a lower limit 471. If the calculated pressure adjustment 460 is within the range between the upper limit 479 and the lower limit 471, the system 100 may generate the pressure adjustment 480 by outputting the calculated pressure adjustment 460. In some embodiments, however, if the calculated pressure adjustment 460 is greater than the upper limit 479 (or less than the lower limit 471), then the system 100 may generate the pressure adjustment 480 by outputting the upper limit 479 (or the lower limit 471).
As shown in
To calculate the past temperature adjustment 540 in step 520, the system may store a plurality of predetermined past temperature adjustments 540, each associated with a predetermined past temperature range 522, and identify the past temperature adjustment 540 for the forecast location 108 and the forecast date 106 by selecting the predetermined past temperature adjustment 540 that is associated with the predetermined past predetermined range 512 that includes the past temperature metric 512 for the forecast location 108 and the forecast date 106.
The temperature change adjustment 590 may be the product of a past temperature component 530 and a temperature change component 570. To calculate the past temperature component 530, the system 100 may similarly store a plurality of predetermined past temperature components 530, each associated with one of the predetermined past temperature ranges 522, and identify the past temperature component 530 for the forecast location 108 and the forecast date 106 by selecting the predetermined past temperature component 530 that is associated with the predetermined past predetermined range 522 that includes the past temperature metric 512 for the forecast location 108 and the forecast date 106.
To calculate the temperature change component 570 in step 560, the system may store a plurality of predetermined temperature change components 570, each associated with a predetermined temperature change range 562, and identify the temperature change component 570 for the forecast location 108 and the forecast date 106 by selecting the predetermined temperature change component 570 that is associated with the predetermined temperature change range 562 that includes the temperature change 555 for the forecast location 108 and the forecast date 106.
As shown in
To calculate the wind speed adjustment 680, the system 100 may store a plurality of predetermined wind speed adjustments 680, each associated with a predetermined wind speed range 640, and identify the wind speed adjustment 680 for the forecast location 108 and the forecast date 106 by selecting the predetermined wind speed adjustment 680 that is associated with the predetermined wind speed range 640 that includes the forecasted wind speed 610 in the forecast location 108 for the forecast date 106.
As shown in
To calculate the sky adjustment 780, the system may store a sky adjustment table 750 having a plurality of predetermined sky adjustments 780, each associated with a sky condition 714 (e.g., clear, mostly sunny, partly cloudy, mostly cloudy, cloudy, overcast, etc.) and identify the sky speed adjustment 780 for the forecast location 108 and the forecast date 106 by selecting the predetermined sky adjustment 780 that is associated with the forecasted sky condition 714 in the forecast location 108 for the forecast date 106. In some instances, the system 100 may store multiple predetermined sky adjustments 780 associated with the same sky condition 714, each associated with a precipitation type 716 (e.g., rain showers, rain, thunderstorm, etc.). In those instances, the system 100 may identify the sky speed adjustment 780 for the forecast location 108 and the forecast date 106 by selecting the predetermined sky adjustment 780 that is associated with the forecasted sky condition 714 and the forecasted precipitation type 716 in the forecast location 108 on the forecast date 106.
In some embodiments, the system 100 may also store a predetermined temperature-based sky adjustment 740 and compare a past temperature metric 512 (calculated, for example, as described above with reference to
As shown in
The system 100 may store a plurality of predetermined moon adjustments 880, each associated with one or more dates of the lunar calendar 830. As shown in
To compare the forecast date 106 to the lunar calendar 830 for the forecast location 108, the system 100 may output the forecast location 108 to a third party 130 via the one or more networks 150 (e.g., via the Internet), receive the lunar calendar 830 for the forecast location 108 from the third party 130 in step 820, and compare the forecast date 106 and the lunar events on the lunar calendar 830 in step 840. In other embodiments, the system 100 may output the forecast location 108 and the forecast date 106 to the third party 130 and receive, from the third party 130 as calculated by the third party 130, the distance between the forecast date 106 and the lunar events on the lunar calendar 830 for the forecast location 108.
Referring back to
As shown in
The system 100 may store a plurality of predetermined fishing seasons 980, each associated with one of a plurality of predetermined date ranges 940 and one of a plurality of predetermined temperature ranges 970. The system 100 may generate a seasonal forecast 980 for the forecast date 106 by selecting the predetermined fishing season 980 associated with the predetermined date range 940 that includes the forecast date 106 and the predetermined temperature range 970 that includes the past temperature metric 512 calculated for the forecast date 106.
The system 100 may store information identifying each of a plurality of baits 1040, for example a name, a description, a universal resource location (URL), etc. The system 100 may also store a plurality of presentations 1060 (e.g., slow, medium speed, fast). The system 100 may also store a plurality of distinct fishing locations 1050 that are commonly found in bodies of water. For example, the system 100 may store an image of a generic body of water (e.g., as shown in
As described above with reference to
As shown in
For example, for each of a plurality of predetermined past temperature ranges 1030 and each of the plurality of categories 382, the system 100 may store a predetermined subset of the plurality of baits 1040, a predetermined subset of the fishing locations 1050, and a predetermined subject of the plurality of presentations 1060. The system 100 may then identify recommended baits 1040, recommended fishing locations 1050, and/or recommended presentations 1060 for the forecasted fishing conditions 180 in the forecast location 108 by identifying the predetermined subset of baits 1040, the predetermined subset of fishing locations 1050, and/or the predetermined subset of presentations 1060 associated with the predetermined past temperature range 1030 that includes the past temperature metric 512 in the forecast location 108 on the forecast date 106 and the category 382 indicative of the fishing conditions indicated by the forecast rating 180 for the forecast location 108 and the forecast date 106.
For each predetermined past temperature range 1030 and category 382, the system 100 may further store a predetermined subset 1042 of the baits 1040 for fishing in locations 1050 that include wood, a predetermined subset 1044 of the baits 1040 for fishing in locations 1050 that include weeds, and/or a predetermined subset 1046 of the baits 1040 for fishing in locations 1050 that include rock. In those embodiments, the system 100 may identify recommended baits 1040 for the forecasted fishing conditions in the forecast location 108 by identifying the predetermined wood baits 1042, the predetermined weeds baits 1044, and/or the predetermined rock baits 1066 associated with the predetermined past temperature range 1030 that includes the past temperature metric 512 in the forecast location 108 on the forecast date 106 and the category 382 indicative of the fishing conditions indicated by the forecast rating 180 for the forecast location 108 and the forecast date 106.
For each of the plurality of baits 1040, the system 100 may also store a recommended type of fishing rod, a recommended type of fishing reel, a recommended type of fishing line, and/or a description of a recommended method of fishing with that bait. Accordingly, the system may be configured to identify a recommended type of fishing rod, a recommended type of fishing reel, a recommended type of fishing line, and/or a recommended fishing method for fishing in the fishing conditions indicated by the forecast rating 180 for the forecast location 108 and the forecast date 106.
While the system 100 may be used to generate a forecast rating 180 that is broadly indicative of the conditions for fishing any fish in the forecast location 108 on the forecast date 106, the system 100 described above is particularly well suited to generate a bass forecast rating 180 indicative of the bass fishing conditions because the process 200 described above captures the specific weather conditions 132 that affects bass fishing conditions over the specific time period that those weather conditions 132 continue to have an effect. As described above, the system 100 identifies a number of relevant parameters by storing thresholds and/or ranges and comparing current and/or forecasted weather data 132 (and, in some embodiments, solunar data) to those thresholds and/or ranges. The system may do so, for example, using look-up tables, formulas, if-then statements, etc. While preferred embodiments have been described above, those skilled in the art who have reviewed the present disclosure will readily appreciate that other embodiments can be realized within the scope of the invention. Accordingly, the present invention should be construed as limited only by any appended claims.
This application claims priority to U.S. Prov. Pat. Appl. No. 63/219,555, filed Jul. 8, 2021, which is hereby incorporated by reference.
Number | Date | Country | |
---|---|---|---|
63219555 | Jul 2021 | US |