Crop Planning System

Abstract

To provide a crop planting plan formulation system capable of automatically formulating a crop planting plan.SOLUTION: Disclosed is a crop planting plan formulation system in which a crop planting plan formulation device, a growth prediction device, a user terminal and a weather data providing device are connected to each other via a network such as the Internet. This crop planting plan formulation device includes: a growth amount acquisition part which acquires the predicted growth amount using a prediction model for predicting the growth amount of the crop from weather information; and a presentation part which presents a first planting date from among multiple planting dates of the crop, which satisfies the shipping standard in terms of the growth amount at the scheduled harvest date.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present invention relates to a crop planning system. [Background technology]

[0002] Since it is difficult to store crops such as outdoor vegetables while maintaining their freshness after harvest, it is preferable to carefully plan the amount of crops to be planted so that a predetermined harvest amount can be harvested on the shipping date, and to plant the crops according to that plan. In particular, when the daily shipping amount is determined by contract with the shipping destination, it is desirable to carefully plan the amount of crops to be planted in order to prevent a shortage of shipping amount and a breach of contract.

[0003] In particular, in recent years, improvements in breeding and cultivation techniques have made it possible to produce some crops year-round. Therefore, in order to harvest a predetermined yield every day, it is necessary to calculate the cultivation period for different crop seasons, such as winter and summer, depending on the climate. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] International Publication No. 2015 / 173875 [Patent Document 2] International Publication No. 2017 / 164097 [Patent Document 3] Japanese Patent Application Publication No. 2019-219704 Summary of the Invention [Problem to be solved by the invention]

[0005] For example, Patent Document 1 describes a cultivation plan generating device that, upon receiving a target sales period and a target sales amount, specifies the planting period and the amount of planting required to achieve the target sales amount.

[0006] However, Patent Document 1 sets the crop growth period in advance, and as mentioned above, it is not possible to formulate a planting plan that allows crops to be harvested on the desired shipping date while taking into account the amount of crop growth due to differences in climate.

[0007] Patent Document 2 describes an information processing device that generates harvest time and yield information using weather information, etc., and generates harvest plans and transportation plans based on that information. Patent Document 3 describes an agricultural management support system that provides predicted harvest yields for each unit period in order to level out harvest yields.

[0008] However, Patent Documents 2 and 3 do not formulate a cropping plan according to the harvest time.

[0009] An object of the present invention is to provide a crop cultivation plan formulation system that can automatically formulate a crop cultivation plan while taking into account crop growth rates due to differences in climate. [Means for solving the problem]

[0010] The crop planning system of the present invention includes a growth amount acquisition unit that acquires a predicted growth amount of a crop using a prediction model that predicts the growth amount of the crop from meteorological information, and a presentation unit that presents a first cropping date among a plurality of crop planting dates on which the growth amount on the planned harvest date satisfies a shipping standard. If there are a plurality of first planting dates, the presenting unit presents the latest of the plurality of first planting dates. It is a system that [Effects of the Invention]

[0011] The crop cultivation plan formulation system of the present invention can automatically formulate a crop cultivation plan. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a system configuration diagram of a crop planning system according to this embodiment. [Figure 2] FIG. 2 is a functional configuration diagram of the crop planning device. [Figure 3]FIG. 3 is a functional configuration diagram of the growth prediction device. [Figure 4] FIG. 4 is a flowchart of a growth prediction method executed by the growth prediction device. [Figure 5] FIG. 5 is a schematic diagram of the process for predicting the growth amount of cabbage. [Figure 6] FIG. 6 is a sequence diagram (part 1) showing the operation of the crop planning system according to the first example. [Figure 7] FIG. 7 is a sequence diagram (part 2) showing the operation of the crop planning system according to the first example. [Figure 8] FIG. 8 is a sequence diagram (part 1) showing the operation of the crop planning system according to the second example. [Figure 9] FIG. 9 is a sequence diagram (part 2) showing the operation of the crop planning system according to the second example. [Figure 10] FIG. 10 is a schematic diagram of the growth amount table. [Figure 11] FIG. 11 is a functional configuration diagram of a crop cultivation plan formulation device according to the third example. [Figure 12] Figure 12 is a schematic diagram of the planting and harvesting period table. [Figure 13] FIG. 13 is a functional configuration diagram of a crop cultivation plan formulation device according to the second embodiment. [Figure 14] FIG. 14 is a schematic diagram of a crop planning table. [Figure 15] FIG. 15 is a schematic diagram showing another example of a method for setting priorities. [Figure 16] FIG. 16 is a flowchart of the cultivation plan formulation method according to the second embodiment. [Figure 17] FIG. 17 is a schematic diagram of the cultivation plan table at the time when the allocating unit acquires it from the user terminal. [Figure 18] FIG. 18 is a schematic diagram of the crop plan table when the determination in step S72 is negative. [Figure 19] FIG. 19 is a flowchart of the adjustment process. [Figure 20]FIG. 20 is a schematic diagram showing the processing content of step S82 performed on the crop planning table shown in FIG. [Figure 21] FIG. 21 is a flowchart of the adjustment process to a later date in step S87. [Figure 22] FIG. 22 is a hardware configuration diagram of the crop cultivation plan development device 2 according to each embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] FIG. 1 is a system configuration diagram of a crop planning system according to this embodiment.

[0014] The crop planning system 1 is a system that presents cropping dates that enable harvesting on a desired harvest date, and includes a crop planning device 2, a growth prediction device 3, a user terminal 4, and a weather data providing device 5. These devices are connected to each other via a network 6 such as the Internet.

[0015] The crop cultivation plan formulation device 2 is a computer such as a physical server or a virtual server for formulating a crop cultivation plan.

[0016] The growth prediction device 3 is a computer such as a physical server or a virtual server that predicts the amount of crop growth required for the crop planning device 2 to formulate a crop plan. As an example, the growth prediction device 3 is a server for predicting the amount of growth managed by the National Agriculture and Food Research Organization, a National Research and Development Agency.

[0017] The user terminal 4 is a portable terminal such as a smartphone or tablet terminal that allows the user to input parameters required by the growth prediction device 3. Note that a PC (Personal Computer) may be used as the user terminal 4 to improve the efficiency of input work. However, when working in a field, it is preferable to use a smartphone or tablet terminal as the user terminal 4, as portability is important. The user terminal 4 also obtains crop dates from the crop plan formulation device 2 and presents them to the user.

[0018] The weather data providing device 5 is a computer such as a physical server or a virtual server that provides the growth prediction device 3 with weather data required for the growth prediction device 3 to predict the amount of crop growth. As an example, the weather data providing device 5 is a server managed by the Japan Meteorological Agency that provides AMeDAS data, but is not limited to this. For example, the weather data providing device 5 may be a server that stores and provides AMeDAS weather data at a location closest to the field where the crops are cultivated. Note that a weather observation point may be set up near the field to acquire weather data, and the growth prediction device 3 may acquire the average values acquired there over a single or multiple years as weather data.

[0019] While there are no particular limitations on the crops for which the crop planning system 1 can formulate a crop plan, in this embodiment, a crop planning for open-field vegetables is formulated. Examples of such open-field vegetables include cabbage, lettuce, broccoli, onions, leeks, Chinese cabbage, spinach, Japanese radish, and carrots. Because it is difficult to store these open-field vegetables while maintaining their freshness, a detailed crop planning is required to comply with the daily shipping volume stipulated in the contract with the shipping destination.

[0020] The crop cultivation plan formulation system 1 will now be described in more detail. First, an operator inputs initial conditions using the user terminal 4. The initial conditions include at least the type of crop, the condition of the crop at the time of planting, the location of the field where the crop will be planted, the desired harvest date, and the required shipping specifications of the crop, such as grade, size, or weight. The condition of the crop at the time of planting refers to the seedlings if planting seedlings, or the seeds if sowing seedlings, and the size of the seedlings is expressed in terms of leaf area. Instead of directly inputting the type of crop into the user terminal 4, the operator may select the type of crop from a list of pre-registered types. In this case, the types of crops registered in a parameter table 30, which is stored as information necessary for growth prediction in the memory unit 22 of the crop cultivation plan formulation device 2 (described later), may be listed.

[0021] The user terminal 4 is configured to be connectable to the network 6 by means of an internal communication function.

[0022] After inputting the initial conditions, the operator instructs the crop planning device 2 to execute processing from the user terminal 4, and the crop planning device 2 starts calculating the crop dates that match the initial conditions. When the crop planning device 2 finishes calculating the crop dates, the results are displayed on the user terminal 4, and the crop planning process ends.

[0023] Next, we will explain the crop cultivation plan development device 2 according to this embodiment. Fig. 2 is a functional configuration diagram of the crop cultivation plan development device 2. As shown in Fig. 2, the crop cultivation plan development device 2 includes a communication unit 21, a storage unit 22, and a control unit 23.

[0024] Of these, the communication unit 21 is an interface for connecting the crop planning device 2 to the network 6 (see FIG. 1). The storage unit 22 stores a growth amount table 15, a crop and harvest period table 24, and a parameter table 30, which will be described later.

[0025] On the other hand, the control unit 23 is a processing unit that controls each unit of the crop cultivation plan formulation device 2. As an example, the control unit 23 includes a parameter acquisition unit 25, a condition setting unit 26, a growth amount acquisition unit 27, a determination unit 28, and a presentation unit 29.

[0026] Among these, the parameter acquisition unit 25 is a processing unit that acquires various parameters from the user terminal 4 that are necessary for the crop cultivation plan formulation device 2 to formulate a shipping plan. The various parameters are initial conditions input to the user terminal 4. Specifically, the parameters include field location information indicating the location of the field where the crop is to be cultivated, the name of the crop, the condition of the crop at the time of cultivation, the planned harvest date of the crop, and the shipping standard value. For example, if the type of crop to be cultivated is cabbage, the shipping standard value is generally determined by the weight of the cabbage, i.e., the head weight, and cabbages are classified into small, medium, large, etc., based on the head weight. If the shipping standard for large cabbages is a head weight between 2000g and 2300g, the minimum shipping standard value is 2000g, and the maximum shipping standard value is 2300g. Note that "head weight" is an example of growth amount and is the fresh weight (g) of a cabbage head.

[0027] The condition setting unit 26 is a processing unit that sets a tentative planting date that the growth prediction device 3 uses to calculate the growth amount of the crop. The growth amount acquisition unit 27 is a processing unit that acquires the growth amount predicted by the growth prediction device 3. The determination unit 28 is a processing unit that determines whether the growth amount acquired by the growth amount acquisition unit 27 matches the determination conditions. The presentation unit 29 is a processing unit that presents the planting date that the determination unit 28 determines matches the determination conditions to the user terminal 4. The specific operation of each processing unit will be described later.

[0028] Next, a description will be given of the growth prediction device 3. Fig. 3 is a functional configuration diagram of the growth prediction device 3. As shown in Fig. 3, the growth prediction device 3 includes a communication unit 11, a storage unit 12, and a control unit 13.

[0029] Of these, the communication unit 11 is an interface for connecting the growth prediction device 3 to the network 6. The storage unit 12 stores a growth prediction model 14 for predicting the amount of crop growth. The growth prediction model 14 is a model in which a plurality of algorithms and parameters used to predict crop growth are recorded in association with the type of crop.

[0030] On the other hand, the control unit 13 is a processing unit that controls each unit of the growth prediction device 3. As an example, the control unit 13 includes an acquisition unit 16, a prediction unit 17, and a notification unit 18.

[0031] When the acquisition unit 16 receives an instruction to execute processing from the user terminal 4 via the network 6, it acquires the type of crop input to the user terminal 4, the conditions when the crop is cultivated, and the location of the field where the crop is to be cultivated from the crop planning device 2. The acquisition unit 16 also acquires weather data for or near the location of the field where the crop is to be cultivated from the weather data providing device 5 via the network 6. The acquisition unit 16 may acquire weather data from the weather data providing device 5 every time weather data is requested, or alternatively, the acquisition unit 16 may acquire all the weather data from the weather data providing device 5 and store it in the memory unit 12. In this case, the prediction unit 17 acquires the necessary weather data from the memory unit 12.

[0032] The prediction unit 17 is a processing unit that predicts the daily growth amount of the crop after planting, based on the state of the crop and weather conditions at the time of planting acquired by the acquisition unit 16. When making the prediction, the prediction unit 17 uses an algorithm and parameters corresponding to the type of crop acquired by the acquisition unit 16 from the growth prediction model 14 stored in the memory unit 12. The notification unit 18 notifies the crop planning device 2 of the result predicted by the prediction unit 17 via the network 6.

[0033] Next, a description will be given of a growth prediction method executed by the growth prediction device 3. FIG.

[0034] First, the acquisition unit 16 acquires the type of crop to be cultivated, the state of the crop at the time of cultivation, and the location of the field from the cultivation plan development device 2 (step S11).

[0035] Next, the acquisition unit 16 acquires the weather conditions of the field corresponding to the acquired position of the field as weather information from the weather data providing device 5 (step S12). Here, the weather information acquired by the acquisition unit 16 as the weather conditions includes the daily global solar radiation (MJ / m 2 ) and average temperature (℃) for one year.

[0036] Next, the prediction unit 17 performs a prediction process to predict the future daily growth amount of the crop using the growth prediction model 14 (step S13). The prediction process will be described in detail later.

[0037] Next, the notification unit 18 notifies the crop cultivation plan formulation device 2 of the predicted daily growth amount in association with the "date" (step S14).

[0038] Next, the growth amount prediction process in step S13 will be described. FIG. 5 is a schematic diagram of the growth amount prediction process using an example in which cabbage is input as the type of crop. In the case of cabbage, since seedlings are to be planted, the leaf area per plant of the crop expected at the time of planting is used as the initial value for the state of the crop at the time of planting. In response to the selection of cabbage as the type, the prediction unit 17 acquires the algorithm and parameters required for prediction from the growth prediction model 14 in the memory unit 12. As parameters for predicting the growth of cabbage, the growth prediction model 14 includes the solar radiation use efficiency (g / MJ) for cabbage, the leaf head dry matter distribution rate (%), the outer leaf dry matter distribution rate (%), the leaf head dry matter distribution rate (%), and the leaf area / fresh weight ratio (m 2 / g) are stored in advance.

[0039] As will be described later, the solar radiation use efficiency, outer leaf dry matter rate, and leaf head dry matter rate may depend on the daily mean temperature, and the relationships between these may be stored in the growth prediction model 14.

[0040] The prediction unit 17 repeatedly executes the operations from step S21 to step S28 according to the acquired algorithm. Executing steps S21 to S28 once is equivalent to one day's worth of growth prediction work. The prediction unit 17 executes the prediction process assuming that cropping was performed on the date specified by the crop planning device 2.

[0041] First, in step S21, the leaf area per plant of the crop expected at the time of planting is input for the prediction for the day after the planting date, and if it is the day after the planting date or later, the leaf area calculated as the predicted value for the previous day and the daily accumulated solar radiation (MJ / m 2) and calculate the daily integrated amount of light received (MJ / plant). For example, 2 / share) and daily accumulated solar radiation (MJ / m 2 ) to obtain the daily accumulated amount of received light (MJ / share). The prediction unit 17 may obtain the daily accumulated amount of received light from the weather data providing device 5, or may obtain the daily accumulated amount of received light stored in advance in the storage unit 12.

[0042] Next, the process proceeds to step S22, where the prediction unit 17 calculates the daily dry matter production (g / plant) for that day from the calculated daily accumulated amount of received light (MJ / plant). In calculating this daily dry matter production, the prediction unit 17 uses the solar radiation use efficiency (g / MJ), which represents the amount of photosynthetic product produced per unit of physical energy of solar radiation received by the crop. For example, the prediction unit 17 obtains the daily dry matter production (g / plant) from the product of the daily accumulated amount of received light (MJ / plant) and the solar radiation use efficiency (g / MJ). Note that the solar radiation use efficiency (g / MJ) may be given a different value depending on the daily mean temperature.

[0043] Next, proceeding to step S23, the prediction unit 17 calculates the dry matter weight (g / plant) of the plant on that day by adding (not shown) the daily dry matter production (g / plant) calculated in step S22 to the dry matter weight (g / plant) up to the previous day.

[0044] Next, the process proceeds to step S24, where the prediction unit 17 calculates the head dry matter weight (g / plant) and the outer leaf dry matter weight (g / plant) using the plant dry matter weight (g / plant) and the head dry matter distribution rate (%), which indicates the proportion of the head dry matter weight (g / plant) to the plant dry matter weight (g / plant). Note that cabbage has a characteristic in which the head dry matter weight (g / plant) does not increase unless the outer leaf dry matter weight (g / plant) increases to a certain extent. In other words, the head dry matter distribution rate (%) depends on the outer leaf dry matter weight (g / plant), and when the outer leaf dry matter weight (g / plant) is smaller than a predetermined weight, the head dry matter distribution rate (%) used to calculate the head dry matter weight (g / plant) may be set to "0."

[0045] Next, proceeding to step S25, the prediction unit 17 calculates the outer leaf fresh weight (g / plant) based on the outer leaf dry matter weight (g / plant) calculated in step S24 and the outer leaf dry matter rate (%) indicating the ratio of the dry matter weight (g / plant) to the fresh weight (g / plant) of the outer leaves. For example, the outer leaf fresh weight (g / plant) is calculated from the product of the outer leaf dry matter weight (g / plant) and the outer leaf dry matter rate (%) indicating the ratio of the dry matter weight (g / plant) to the fresh weight (g / plant). Note that the outer leaf dry matter rate (%) may be given a different value depending on the daily average temperature.

[0046] Next, the process proceeds to step S26, where the prediction unit 17 calculates the leaf head fresh weight (g / plant) based on the leaf head dry weight (g / plant) calculated in step S24 and the leaf head dry matter rate (%), which indicates the ratio of the dry matter weight (g / plant) to the fresh weight (g / plant) of the leaf head. For example, the prediction unit 17 obtains the leaf head fresh weight (g / plant) by multiplying the leaf head dry matter weight (g / plant) by the leaf head dry matter rate (%), which indicates the ratio of the dry matter weight (g / plant) to the fresh weight (g / plant). Note that the leaf head dry matter rate (%) may be assigned a different value depending on the daily average temperature. This leaf head fresh weight (g / plant) becomes the "head weight" in the growth amount table 15 (see FIG. 10), which will be described later.

[0047] Next, the process proceeds to step S28, and the prediction unit 17 calculates the leaf area / fresh weight ratio (m 2 / g) and the fresh weight of outer leaves (g / plant) to obtain the leaf area (m 2 This completes one day's prediction. The growth prediction device 3 repeats this process a predetermined number of times in response to an instruction from the crop planning device 2.

[0048] Next, the operation of the crop planning system 1 will be described in more detail by dividing it into several embodiments.

[0049] First Embodiment First example 6 and 7 are sequence diagrams showing the operation of the crop cultivation plan formulation system 1 according to the first example.

[0050] First, when the processing of the crop planning system 1 is started, the user terminal 4 accepts input of the field location information (L), the type of crop to be cultivated (F), the condition of the crop at the time of planting (S), the planned harvest date of the crop (Dp), and the minimum head weight (Wmin) as the shipping standard or shipping standard value, and inputs these values into each of the parameters L, F, S, Dp, and Wmin (steps S31 to S35). Note that when the shipping standard is specified on the user terminal 4, the user terminal 4 may refer to the parameter table 30 of the crop planning device 2 and obtain the minimum head weight of the input shipping standard.

[0051] Next, the user terminal 4 notifies the crop planning device 2 of these parameters L, F, S, Dp, and Wmin (step S36), and the parameter acquisition unit 25 of the crop planning device 2 acquires these parameters.

[0052] Next, the condition setting unit 26 of the crop cultivation plan formulation device 2 assigns December 31st as a tentative cultivation date to the parameter D (step S37).

[0053] Next, the presenting unit 29 assigns 1 to a parameter n indicating the number of days that have passed since the date set as parameter D (step S38).

[0054] Next, the crop planning device 2 notifies the growth prediction device 3 of the parameters L, F, S, D, and n (step S40).

[0055] Next, the acquisition unit 16 of the growth prediction device 3 acquires weather data for the day corresponding to D+n for the location closest to the field from AMeDAS, which is the weather data providing device 5, based on the location information of the field indicated by the parameter L (step S41).

[0056] Next, the growth prediction device 3 calculates the head weight We at D+n when planted at D based on the parameters F, S, D, and n (step S42). The head weight We is calculated using the data for one day from steps S21 to S28 described above.

[0057] Next, the growth prediction device 3 notifies the crop planning device 2 of the calculated head weight We (step S43), and the growth amount acquisition unit 27 of the crop planning device 2 acquires the head weight We.

[0058] Next, the determination unit 28 of the crop cultivation plan formulation device 2 determines whether the head weight We is equal to or greater than the minimum value Wmin of the shipping standard (step S44).

[0059] If this determination is negative, the process proceeds to step S45, where the determination unit 28 increments n by 1 (step S45), and then the process starts again from step S40.

[0060] On the other hand, if the determination in step S44 is affirmative, the process proceeds to step S46.

[0061] In step S46, the determination unit 28 of the crop cultivation plan formulation device 2 determines whether the nth day counted from the cultivation date D is equal to the planned harvest date Dp.

[0062] If it is determined that they are not equal, planting on planting date D would mean that the day on which the head weight We reaches or exceeds the minimum shipping standard value Wmin would be past the planned harvest date Dp. Therefore, in this case, the process moves to step S47, where the determination unit 28 subtracts 1 from D and starts over from step S38.

[0063] On the other hand, if the determination in step S46 is positive, it means that the head weight We is equal to or greater than the minimum value Wmin of the shipping standard on the planned harvest date Dp. Therefore, in this case, the presentation unit 29 presents D as the planting date to the user terminal 4 (step S48), and the user terminal 4 presents this planting date to the user (step S49). This completes the process.

[0064] According to the first example described above, in step S44, the presentation unit 29 presents the planting date D (first planting date) on which the head weight We on the planned harvest date Dp will be equal to or greater than the minimum value Wmin of the shipping standard. This makes it possible to predict that if the worker plants a crop on that planting date D, the worker will harvest a crop with a head weight We that meets the shipping standard on the planned harvest date Dp.

[0065] 6 and 7, the latest planting date D is displayed on which the head weight We on the planned harvest date Dp is equal to or greater than the minimum shipping standard value Wmin. This prevents the crop from growing too much on the planned harvest date Dp.

[0066] In step S37, the planting date D is initially set to December 31, but the planting date may also be set to January 1. In this case, D←D+1 should be set in step S47.

[0067] Furthermore, the initial value of the planting dates D does not have to be December 31st or January 1st. For example, the first or last day of an appropriate period for the crop growing period may be set as the initial value of D. In this case, the period of the planting dates D may be specified from the user terminal 4, or may be stored in the parameter table 30 of the crop planning device 2. If it is stored in the parameter table 30, the condition setting unit 26 may set the period of the planting dates D without checking whether the period of the planting dates D has been specified by the user terminal 4, or may check and then obtain the period stored in the parameter table 30. This reduces the processing time of the crop planning system 1.

[0068] Second example 8 and 9 are sequence diagrams showing the operation of the crop cultivation plan formulation system 1 according to the second example. In the second example, in addition to the configuration shown in the first example, a growth amount table 15 is stored in the memory unit 22 of the crop planning device 2. The growth amount table 15 stores the head weight We for each day of the year, together with the date, assuming that the crop dates calculated by the growth prediction device 3 are from January 1st to December 31st.

[0069] FIG. 10 is a schematic diagram of a growth amount table 15 calculated for cabbage. As shown in FIG. 10, the growth amount table 15 is a table in which "number of cultivation days," "date," and "head weight" are each associated with each planting date in a year and arranged in chronological order. Of these, "number of cultivation days" is the number of days counted from the planting date. Furthermore, "date" is the date corresponding to "number of cultivation days."

[0070] Referring again to Figure 8, first, the user terminal 4 accepts input of the field location information (L), the type of crop to be planted (F), the condition of the crop at the time of planting (S), the planned harvest date of the crop (Dp), and the minimum (Wmin) and maximum (Wmax) head weight as shipping standard values, and inputs these into the parameters L, F, S, Dp, Wmin, and Wmax (steps S51 to S56). Note that, as in the first example, the shipping standard may be input instead of the shipping standard value.

[0071] Next, the user terminal 4 notifies the crop planning device 2 of these parameters L, F, S, Dp, Wmin, and Wmax (step S57), and the parameter acquisition unit 25 of the crop planning device 2 acquires these parameters.

[0072] Next, the condition setting unit 26 of the crop cultivation plan formulation device 2 assigns January 1 as a tentative cultivation date to parameter D indicating the cultivation date (step S58).

[0073] Next, the crop planning device 2 notifies the growth prediction device 3 of the parameters L, F, S, and D (step S59).

[0074] Next, the acquisition unit 16 of the growth prediction device 3 acquires weather data from the AMeDAS closest to the field based on the location information of the field indicated by the parameter L from the weather data providing device 5 (step S60).

[0075] Next, the growth prediction device 3 calculates the annual head weight We for each day when planted on D based on the parameters F, S, and D (step S61). The head weight We is calculated using the one-year data from steps S21 to S28 described above. That is, if planting is performed on planting day D, the head weight We for one year from that day is calculated.

[0076] Next, the growth prediction device 3 notifies the crop planning device 2 of the head weight We for each day of the year (step S62).

[0077] Thereafter, the growth amount acquisition unit 27 of the crop planning device 2 associates the head weight We for each day of the year with the crop date D and stores them in the growth amount table 15 of the storage unit 22 (step S63).

[0078] Next, the determination unit 28 of the crop planning device 2 determines whether the crop date D is equal to December 31 (step S64). If this determination is negative, the process proceeds to step S65, where the condition setting unit 26 increments the crop date D by 1. Then, the process is started again from step S59.

[0079] On the other hand, if the determination in step S64 is positive, the process proceeds to step S66. When the determination in step S64 is positive, the growth amount table 15 in the memory unit 22 of the crop planning device 2 stores the head weight We for each day in the year from each crop date, assuming that the crop date D is from January 1 to December 31.

[0080] In step S66, the judgment unit 28 of the crop planning device 2 compares the parameter Wmin acquired from the user terminal 4 and extracts the crop date D on which the head weight We on the planned harvest date will be equal to or greater than the minimum value Wmin of the shipping standard.

[0081] Next, the determining unit 28 further extracts, from the planting dates D extracted in step S66, planting dates D on which the head weight We on the planned harvest date will be equal to or less than the maximum value Wmax of the shipping standard (step S67).

[0082] Thereafter, the presentation unit 29 presents the crop date D extracted in step S67 to the user terminal 4 (step S68), and the user terminal 4 further presents the crop date D to the user (step S69), and the process ends.

[0083] According to the second example described above, in step S69, the presentation unit 29 presents the planting date D on which the head weight We on the planned harvest date Dp is equal to or greater than the minimum value Wmin and equal to or less than the maximum value Wmax of the shipping specifications.

[0084] As a result, by having the worker plant the crop on the planting date D, the crop with a head weight We that meets the shipping standard can be harvested on the planned harvest date Dp, just like in the first example.

[0085] According to the second example, there may be multiple cultivation dates D that satisfy the determinations of both steps S66 and S67. In this case, multiple cultivation dates D that satisfy the determinations of both steps S66 and S67 may be presented in step S69. Alternatively, conditions may be accepted at the user terminal 4 at the start of the cultivation plan formulation process, and dates that meet those conditions may be presented. The conditions may be, for example, the date closest to the beginning of the year, the date closest to the end of the year, or the date in the middle of these.

[0086] Furthermore, in step S58, the initial condition for the planting date D is set to January 1, and in step S64, the final day of the planting date D is set to December 31, but this is not limited to this. For example, the first day of an appropriate period for growing crops may be set to D in step S58, and the final day may be set to D in step S64. By doing so, the processing time of the crop planning system 1 can be shortened.

[0087] Furthermore, each time the daily bulb weight We is calculated in step S61, a step can be added to determine whether the bulb weight We exceeds the shipping standard (maximum value) Wmax, so that it is not necessary to calculate the growth amount after the day on which the bulb weight We exceeds the maximum value Wmax.

[0088] Third Example In the first and second examples above, only one planting date is specified to allow for harvesting on the desired scheduled harvest date. In contrast, in the third example, multiple harvest dates or harvest periods can be specified, and planting dates corresponding to those dates can be displayed.

[0089] In the third example, the user terminal 4 accepts input of multiple desired harvest dates or a predetermined desired harvest period as initial conditions. Fig. 11 is a functional configuration diagram of a crop cultivation plan development device 2 according to the third example. As shown in Fig. 11, the crop cultivation plan development device 2 has a period specification unit 32 instead of the condition setting unit 26 of the first example.

[0090] The period specification unit 32 is a processing unit that extracts, for each planting date, the "head weight" and "date" that meet the shipping standards from the growth amount recorded in the growth amount table 15 stored in the memory unit 12, and creates a planting and harvestable period table 24 in which the data are arranged by planned harvest date, and stores the table in the memory unit 22. The period specification unit 32 also references the planting and harvestable period table 24 to specify multiple planned harvest dates corresponding to a certain planting date as harvestable periods.

[0091] When the crop planning device 2 determines that one year's worth of growth prediction work has been completed, the growth amount acquisition unit 27 acquires daily growth amounts from the growth prediction device 3, creates a growth amount table 15 arranged in chronological order, and stores it in the memory unit 22.

[0092] When the growth amount table 15 is created, the period identification unit 32 extracts from the growth amount table 15 a period that satisfies the planned harvest period and shipping standards set as initial conditions, creates a planting and harvestable period table 24, and stores it in the memory unit 22.

[0093] As an example, it is assumed here that the planned harvest period is between October 30th and November 5th, and that the shipping standard specifies that the head weight is between 2000g and 2300g.

[0094] In this case, the period specifying unit 32 specifies, for each "planting date," a period during the planned harvest period from October 30 to November 5 in which the "head weight" is between 2000g and 2300g inclusive in the growth amount table 15. The period specifying unit 32 then creates the planting and harvestable period table 24 by associating the "date" within the specified period with the "head weight" on that "date."

[0095] FIG. 12 is an example of a planting and harvesting period table 24 created in this manner. Each number shown in the planting and harvesting period table 24 is the predicted head weight for each combination of planting date and planned harvest date that meets the shipping standards. Note that instead of storing head weights in the planting and harvesting period table 24, information indicating that a combination of planting date and planned harvest date is expected to meet the shipping standards may be stored. For example, instead of head weights, a character such as "OK" may be stored in the planting and harvesting period table 24, or the corresponding column may be colored or surrounded by a thick line.

[0096] When the cropping plan formulation device 2 creates the cropping and harvesting period table 24, the presentation unit 29 notifies the user terminal 4 of the cropping and harvesting period table 24. Then, the user terminal 4 acquires the cropping and harvesting period table 24 and displays it.

[0097] As shown in Figure 12, in this example, when the "scheduled harvest date" is October 31st, the planting period is August 16th to August 18th. In this way, a planting period consisting of multiple days is presented as the planting date for harvesting on the desired harvest date, making it easier to plan planting work.

[0098] Also, according to Figure 12, if the crop is planted on August 18, the harvest period will be from October 31 to November 3. In this way, the date of planting can be specified and used to predict the shipping date.

[0099] Instead of the period determination unit 32 determining the possible periods for planting and harvesting in this manner, the user may input each possible period that they have calculated themselves into the user terminal 4, and the user terminal 4 may notify the planting plan formulation device 2.

[0100] Second Embodiment Next, a second embodiment of the crop planning system will be described. In the first embodiment, the amount of crop that can be planted per planting day was not taken into consideration. As a result, there may be cases where it is not possible to plant the same amount of crop as desired to be harvested on the desired harvest date in one day. In the second embodiment, a crop planning system is developed for such cases.

[0101] The second embodiment of the crop planning system starts operation when the crop planning system 1 creates the crop planning table 31 described below in place of the crop and harvest period table 24 created in the third example of the first embodiment.

[0102] 13 is a functional configuration diagram of the crop planning device 2 according to this embodiment. The condition setting unit 26 of the crop planning device 2 changes the display format of the crop and harvest period table 24 created in the third example of the first embodiment and transmits it to the user terminal 4 as a crop planning table 31. The control unit 23 of the crop planning device 2 has an allocation unit 33 instead of the determination unit 28 in the first embodiment. When predetermined information is entered into the crop planning table 31 transmitted to the user terminal 4 and returned to the crop planning device 2, the allocation unit 33 adjusts the crop planning table 31 so that the harvest volume for each planned harvest date is met and the crop work limit for that crop day is not exceeded, and notifies the user terminal 4 of the results.

[0103] 14 is a schematic diagram of the crop cultivation plan table 31. The crop cultivation plan table 31 is a table showing a cultivation plan for a crop, and has items 31a and 31b, and an area 31c configured by the items 31a and 31b.

[0104] Item 31b is an item related to the harvest plan, and is an item that corresponds to each of "planned harvest date," "planned harvest amount (number of bulbs)," and "surplus / deficiency (number of bulbs)."

[0105] Here, the "planned harvest date" is the harvest date of the crop as stipulated in the contract with the shipping destination. Also, the "planned harvest volume (number of bulbs)" is the harvest volume as stipulated in the contract. The "surplus / deficiency (number of bulbs)" will be discussed later.

[0106] Item 31a is an item related to the cultivation plan, and is an item in which "cultivation date," "upper limit quantity (number of plants)," "cultivation quantity (number of plants)," and "excess quantity (number of plants)" are associated with each other.

[0107] The "maximum amount (number of plants)" is the maximum amount of crop that can be planted in a day, which depends on the number of workers and the working hours, etc. The number of workers and the working hours can change from day to day.

[0108] A harvestable period 31d is further shown within area 31c of the matrix composed of items 31a and 31b. Harvestable period 31d is a combination of planting date and planned harvest date calculated as harvestable for crops that meet shipping specifications, as shown in planting and harvestable period table 24 (FIG. 12). Harvestable period 31d may be shown by hatching as shown in FIG. 14, or by other display methods.

[0109] Furthermore, a priority is assigned to each planting date. The priority is the order of precedence for adjusting the planting amount, which will be described later. Figure 14 shows (1), (2), (3), and (4) as examples of priorities. In this example, the smaller the value, the higher the priority. Priorities are assigned in the order (1) for the earliest possible harvest date for a planting date, (2) for the next possible harvest date, and so on, but this is not limitative. For example, (1) could be assigned to the latest possible harvest date, and (2) for the day before that.

[0110] Fig. 15 is a schematic diagram showing another example of priority. As shown in Fig. 15, the highest priority may be given to days approximately in the middle of the harvestable period for each planting date.

[0111] The priorities may be automatically assigned by the allocation unit 33 of the crop cultivation plan formulation device 2, or may be set by an operator via the user terminal 4. Alternatively, the priorities set by the allocation unit 33 may be configured to be modifiable via the user terminal 4.

[0112] 16 is a flowchart of the crop planning method according to the second embodiment. Here, the description will start from the stage where the crop planning table 31 created by the crop planning device 2 is displayed on the user terminal 4.

[0113] When the cultivation plan table 31 is displayed on the user terminal 4, the user terminal 4 acquires the planned harvest volume (number of bulbs) input by the worker for each planned harvest date in item 31b. The user terminal 4 also acquires the upper limit volume (number of plants) input by the worker for each cultivation date in item 31a (step S70).

[0114] That is, in addition to the functions of the user terminal 4 shown in the third example, the user terminal 4 has the function of inputting the planned harvest yield (number of bulbs) for each planned harvest date and the upper limit of the planting yield (number of plants) for each planting date.

[0115] Next, the allocation unit 33 of the crop planning device 2 acquires the crop planning table 31 with the parameters entered in step S70 from the user terminal 4, and adjusts the crop volume for each crop day so that it does not exceed the value set as the upper limit volume for the crop plan (step S71).

[0116] FIG. 17 is a schematic diagram of the crop planning table 31 at the time the allocating unit 33 acquires it from the user terminal 4. First, the allocating unit 33 transfers the planned harvest volume input for each planned harvest date to the planting date with the highest priority for that planned harvest date. For example, when the planned harvest date is November 4, the harvestable period 31d is August 19 and August 20. In this case, the allocating unit 33 allocates "2000" for the "planned harvest volume (number of bulbs)" for November 4 to August 20 (the second planting date), which has the highest priority among the harvestable periods 31d.

[0117] Furthermore, for the "planned harvest volume (number of bulbs)" for a planned harvest date of November 6th, the harvestable period 31d includes planting dates of August 20th and August 21st, and of these, August 21st is allocated, which has the highest priority. Note that different planting dates may have the same priority, such as the planned harvest date of November 3rd shown in FIG. 14. In this case, the allocation unit 33 may allocate the planting volume to one of multiple planting dates, or may allocate the "planned harvest volume (number of bulbs)" evenly to these planting dates. When selecting one planting date from planting dates with the same priority, selecting the latest planting date can shorten the cultivation period.

[0118] Furthermore, the allocating unit 33 allocates the total value of the planned harvest amounts allocated to each planting date as the planting amount for that planting date. For example, consider the "planting amount (number of plants)" for the planting date of August 23rd. For the harvestable period 31d corresponding to August 23rd, "2000" for the planned harvest date of November 9th and "2000" for November 10th are allocated as planned harvest amounts. For cabbage, one head is harvested from one plant, so the allocating unit 33 allocates "4000", the sum of "2000" and "2000", as the "planting amount (number of plants)" for August 23rd. The allocating unit 33 allocates the "planting amount (number of plants)" for the other planting dates in the same manner.

[0119] The allocation unit 33 also stores a value in the "excess quantity (number of plants)" column in the cultivation plan table 31. The "excess quantity (number of plants)" indicates the quantity when the "cultivation quantity (number of plants)" is greater than the "upper limit quantity (number of plants)," and is the value obtained by subtracting the "upper limit quantity (number of plants)" from the "cultivation quantity (number of plants)."

[0120] For example, consider the "excess amount (number of shares)" for the planting date of August 21st. The "maximum amount (number of shares)" for August 21st is "4000," and the "planted amount (number of shares)" is "5000." Therefore, the allocation unit 33 subtracts "4000" from "5000" to obtain "1000," and stores this in the "excess amount (number of shares)." Note that for other planting dates, the "planted amount (number of shares)" is equal to or less than the "maximum amount (number of shares)," so the "excess amount (number of shares)" is displayed as "0."

[0121] Referring again to Figure 16, the allocation unit 33 then determines whether there is at least one planting date that is set as the harvestable period 31d for all planned harvest dates (step S72). In other words, it determines whether there is a harvestable period 31d for all planned harvest dates.

[0122] Depending on the time of year that includes the date set as the planned harvest date, it may not be suitable for crop growth, and it may not be possible to calculate a planting date that meets shipping specifications for the desired planned harvest date.

[0123] FIG. 18 is a schematic diagram of the cultivation plan table 31 when the determination in step S72 is negative.

[0124] In the example of Figure 18, two planting dates, September 15th and 16th, are calculated. This shows that if planting is done on September 15th, harvesting will be possible on January 27th, but if planting is done the following day, September 16th, the standard value for harvesting will not be reached until February 7th. In other words, for the planned harvest dates from January 28th to February 6th, there are no planting dates that make these days part of the harvestable period 31d. Therefore, in this case, the determination in step S72 is negative. In contrast, in the example of FIG. 17 described above, for all planned harvest dates from November 3rd to November 12th, there is at least one planting date that falls within the harvestable period 31d, so the determination in step S72 is positive.

[0125] Returning to Figure 16, if the determination in step S72 is negative, the allocation unit 33 stores the number of bulbs for which no cultivation date has been assigned in the "Excess / Shortage (Number of Bulbs)" column of the cultivation plan table 31. In the example of Figure 18 mentioned above, the "Excess / Shortage (Number of Bulbs)" for the planned harvest dates of January 28th to February 6th is "-2000".

[0126] If the determination in step S72 is negative, the process proceeds to step S75, where the presentation unit 29 presents a revision of the shipping specifications or harvest plan to the user terminal 4, and the process ends.

[0127] On the other hand, if the determination in step S72 is positive, the process proceeds to step S73. In step S73, the presentation unit 29 determines whether there is an excess amount on any of the planting dates. For example, in the example of FIG. 17, the "excess amount (number of plants)" on the planting date of August 21 is "1000," so the determination in step S73 is positive.

[0128] If the determination in step S73 is affirmative, the adjustment process described below is performed (step S74). On the other hand, if the determination in step S73 is negative or if the adjustment process in step S74 has been performed, the process ends.

[0129] Next, the adjustment process in step S74 will be described with reference to the flowchart of FIG.

[0130] Hereinafter, the planting date for which the "excess amount (number of plants)" is greater than 0 will be referred to as the "planting date (nth day)" with an integer parameter n added. In the example of Figure 17, the planting date of August 21st will be the "planting date (nth day)."

[0131] Furthermore, among the planned harvest dates included in the harvestable period 31d corresponding to the "planting date (nth day)," the planned harvest date for which the planting amount is to be adjusted is called the adjustment target date. In the example of FIG. 17 described above, the planned harvest date for one of the four days from November 5th to November 8th included in the harvestable period 31d for which the planting date is August 21st is the adjustment target date. In this example, adjustment begins on November 5th, which is the planned harvest date with the highest priority as described above among the days from November 5th to November 8th. Under this premise, the adjustment process is executed as follows.

[0132] First, the allocation unit 33 determines whether the planting date (n-1), which is one day before the planned harvest date and serves as the adjustment target date corresponding to the planting date (n), is included in the harvestable period 31d for the planned harvest date and serves as the adjustment target date (step S81). In the example of FIG. 17 described above, the planned harvest date and serves as the adjustment target date corresponding to the planting date (n), is November 5th. November 5th is included in the harvestable period 31d for August 20th, which is the planting date (n-1th). Therefore, in the example of FIG. 17, the determination in step S81 is positive.

[0133] If the determination in step S81 is affirmative, the process proceeds to step S82. In step S82, the allocation unit 33 allocates the excess amount for the planting date (nth day) to the same planned harvest date for the planting date (n-1) one day earlier, within the range of values allocated to the adjustment target day.

[0134] FIG. 20 is a schematic diagram showing the processing content of step S82 performed on the crop planning table 31 shown in FIG.

[0135] In the example of Figure 17 mentioned above, the "excess amount (number of plants)" for the planting date of August 21 is "1000." Furthermore, since "2000" is assigned to the adjustment date of November 5, it is possible to assign within the range of "0" to "2000" to the same planned harvest date on the planting date one day earlier (n-1).

[0136] Therefore, the allocating unit 33 allocates "1000" of the "2000" allocated to November 5th, the planned harvest date that is the adjustment date, to November 5th, which also has a planting date of August 20th, the planned harvest date. This eliminates the "excess quantity (number of shares)" for August 21st. Furthermore, after the allocation, the "planting quantity (number of shares)" for August 20th is 4000, which does not exceed the "upper limit quantity (number of shares)" of 4000, so the "excess quantity (number of shares)" for August 20th remains 0.

[0137] Referring again to Figure 19, the allocation unit 33 then determines whether there is still an excess amount on the planting date (day n) (step S83). If the determination in step S83 is positive, the process returns to step S81, and the same process is repeated on the planned harvest date with the second highest priority.

[0138] On the other hand, if the determination in step S83 is negative, the process proceeds to step S84. In step S84, the allocation unit 33 determines whether there is an excess amount on the cultivation date (n-1 day). If this determination is positive, the process proceeds to step S85, where the allocation unit 33 decrements n by 1. Thereafter, the process returns to step S81, and the same process is repeated.

[0139] When repeating these processes, if the judgment in step S81 is negative, the processes from step S81 to step S85, which start from the planned harvest date with the highest priority among the planting dates (day n), are returned to their initial state, and the process proceeds to adjustment to a later date in step S86.

[0140] On the other hand, if the determination in step S84 is negative, the process proceeds to step S87. In step S87, the allocation unit 33 determines whether there is an excess amount on a cultivation date (mth day) different from the cultivation date (nth day). If this determination is negative, the process ends.

[0141] If the determination in step S87 is affirmative, the allocation unit 33 substitutes m for n (step S88) and starts over from step S81.

[0142] 21 is a flowchart of the adjustment process to a later date in step S87. First, the allocation unit 33 determines whether the planned harvest date, which is the adjustment target date corresponding to the planting date (day n), is included in the harvestable period 31d for the planting date one day later (day n+1) (step S91). If this determination is negative, the process proceeds to step S97, where the presentation unit 29 presents the user terminal 4 with a proposal to review the upper limit of the planting amount. Then, the process ends.

[0143] On the other hand, if the determination in step S91 is positive, the process proceeds to step S92. In step S92, the allocation unit 33 allocates the excess amount for the planting date (nth day) to the same planned harvest date, which is the planting date (n+1) one day later, within the range of the value allocated to the adjustment target day.

[0144] Next, the allocation unit 33 determines whether there is still an excess amount on the planting date (nth day) (step S93). If the determination in step S93 is positive, the process returns to step S91 and the same process is repeated on the planned harvest date with the second highest priority.

[0145] On the other hand, if the determination in step S93 is negative, the process proceeds to step S87 in FIG.

[0146] According to the present embodiment described above, the allocating unit 33 allocates the excess amount of the planting amount for a planting day determined to have an excess amount in step S73 to another planting day different from the planting day in step S82 or step S92. Therefore, even if there is an upper limit to the planting amount for each planting day due to restrictions on the number of workers, working hours, etc., the planting amount for each planting day can be adjusted so as not to exceed the upper limit.

[0147] (Hardware configuration) Next, the hardware configuration of the crop cultivation plan development device 2 according to each embodiment will be described.

[0148] Fig. 22 is a hardware configuration diagram of a crop cultivation plan development device 2 according to each embodiment. As shown in Fig. 22, the crop cultivation plan development device 2 includes a storage device 2a, a memory 2b, a processor 2c, a communication interface 2d, and a medium reading device 2g. These components are interconnected by a bus 2h.

[0149] Of these, the storage device 2a is a non-volatile storage such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive), and stores the crop cultivation plan formulation program 100 according to this embodiment.

[0150] The crop planning program 100 may be recorded on a computer-readable recording medium 2k, and the processor 2c may read the crop planning program 100 via a medium reading device 2g.

[0151] Such recording media 2k include physically portable recording media such as CD-ROMs (Compact Disc Read Only Memory), DVDs (Digital Versatile Discs), and USB (Universal Serial Bus) memories. Furthermore, semiconductor memories such as flash memories and hard disk drives may also be used as the recording media 2k. These recording media 2k are not temporary media such as carrier waves that do not have a physical form.

[0152] Furthermore, the crop cultivation plan formulation program 100 may be stored in a device connected to a public line, the Internet, a LAN, etc. In this case, the processor 2c may read and execute the crop cultivation plan formulation program 100.

[0153] On the other hand, the memory 2b is hardware that temporarily stores data, such as a DRAM (Dynamic Random Access Memory), and the crop planning program 100 is developed on it.

[0154] The processor 2c is hardware such as a CPU (Central Processing Unit) or a GPU (Graphical Processing Unit) that controls each part of the crop cultivation plan development device 2. The processor 2c also executes the crop cultivation plan development program 100 in cooperation with the memory 2b.

[0155] In this way, the memory 2b and the processor 2c cooperate to execute the crop planning program 100, thereby realizing the functions of the control units 23 in each of FIGS.

[0156] Furthermore, the communication interface 2d is hardware such as a network interface card (NIC) for connecting the crop planning device 2 to the network 6 (see FIG. 1). The communication interface realizes a communication unit 21 (see FIG. 6).

[0157] The medium reader 2g is hardware such as a CD drive, a DVD drive, or a USB interface for reading the recording medium 2k.

[0158] The above-described embodiment is a preferred example of the present invention, but the present invention is not limited to this and can be modified in various ways without departing from the spirit of the present invention.

[0159] For example, in the above-described embodiment, the crop planning device 2 and the growth prediction device 3 are configured as separate pieces of hardware as shown in FIG. 1 , but the functions of the growth prediction device 3 may be provided in the crop planning device 2, thereby making the growth prediction device 3 unnecessary. Similarly, the functions of the user terminal 4 may be provided in the crop planning device 2, thereby making the user terminal 4 unnecessary. Furthermore, the crop planning device 2, the growth prediction device 3, and the user terminal 4 may be realized by a single piece of hardware such as a server, a PC, or a tablet terminal.

[0160] In addition, the crop planning system 1 sets the planting density (plants / m) as an initial condition. 2For example, in the case of cabbage, which has outer leaves and heads, the planting density (plants / m 2 ), the outer leaves of adjacent plants may overlap, which may cause a discrepancy between the calculated leaf area when the growth prediction device 3 predicts growth and the leaf area that can actually receive light. Therefore, the planting density (plants / m) can be set as an initial condition by the user terminal 4. 2 ) and when growth prediction is performed by the growth prediction device 3, the leaf area is calculated based on the planting density (plants / m 2 ) and then reduce the leaf area by a predetermined amount. In this case, the distance between adjacent crops may be used instead of the planting density.

[0161] In addition, while cabbage has been used in the above embodiment, the present invention is not limited to cabbage and is applicable to other spherical vegetables such as lettuce and Chinese cabbage. Furthermore, the crop planning system 1 is applicable not only to head vegetables but also to broccoli, onion, and leek. In this case, the parameters of head dry matter distribution rate (%) and head dry matter rate (%) shown in FIG. 5 can be substituted for the harvested part of each type, and the daily growth amount of the harvested part of each type can be calculated.

[0162] Furthermore, the crop planning system 1 can also be applied to root vegetables such as radishes and carrots. In the case of these crops, seeds are sown on the planting date instead of planting seedlings. In other words, planting in the crop planning system 1 is not limited to planting seedlings, but also includes sowing. In the case of sowing, the leaf area is zero at the beginning of the planting date. In this case, the leaf area may be calculated assuming that it has reached a predetermined value after a predetermined number of days have passed since the sowing date. Furthermore, the predetermined number of days may be determined by taking into account the temperature during that period, etc. [Explanation of symbols]

[0163] 1...crop planning system, 2...crop planning device, 3...growth prediction device, 4...user terminal, 5...weather data providing device, 6...network, 11...communication unit, 12...memory unit, 13...control unit, 14...growth prediction model, 15...growth amount table, 16...acquisition unit, 17...prediction unit, 18...notification unit, 21...communication unit, 22...memory unit, 23...control unit, 24...crop and harvest period table, 25...parameter acquisition unit, 26...condition setting unit, 27...growth amount acquisition unit, 28...determination unit, 29...presentation unit, 30...parameter table, 31...crop planning table, 32...period identification unit, 33...allocation unit.

Claims

1. a growth amount acquisition unit that acquires the predicted growth amount using a prediction model that predicts the growth amount of a crop from meteorological information; a presentation unit that presents a first planting date among a plurality of planting dates for the crop on which the growth amount on the planned harvest date satisfies a shipping standard; and A crop planning system characterized in that, when there are multiple first crop dates, the presentation unit presents the latest of the multiple first crop dates.

2. A growth amount acquisition unit that acquires the predicted growth amount of a crop using a prediction model that predicts the growth amount of the crop from meteorological information; a presentation unit that presents a first planting date among a plurality of planting dates for the crop on which the growth amount on the planned harvest date satisfies a shipping standard; and A crop planning system characterized in that the first cropping date is a cropping date on which the growth amount on the planned harvest date is greater than or equal to the lower limit of the shipping standard and less than or equal to the upper limit of the shipping standard.

3. A growth amount acquisition unit that acquires the predicted growth amount using a prediction model that predicts the growth amount of a crop from meteorological information; a presentation unit that presents a first planting date among a plurality of planting dates for the crop on which the growth amount on the planned harvest date satisfies a shipping standard; a period specifying unit that specifies a harvestable period during which the crop is expected to meet the shipping standard if the crop is planted on the first planting date; an allocating unit that, when the planting amount exceeds an upper limit amount when at least a portion of the planned harvest amount within the harvestable period is allocated as the planting amount on the first planting date, allocates the excess amount of the planting amount that exceeds the upper limit amount to a second planting date among the plurality of planting dates that is different from the first planting date; A crop planning system comprising:

4. a priority is set in advance for each of the plurality of planting dates; 4. The crop planning system according to claim 3, wherein the second crop date is the day with the highest priority among the plurality of crop dates.

5. The crop planning system described in claim 4, characterized in that if the multiple cropping dates include multiple days with the same priority, the second cropping date is the latest day among the multiple cropping dates with the same priority.

6. 6. The crop planning system according to claim 3, wherein the allocating unit allocates the total value of the planned harvest volume within the harvestable period as the crop volume for the first cropping date.

Images