JP7768693B2 - Data management method, data management system, and data management program - Google Patents

Description

The present invention relates to a data management method, a data management system, and a data management program.

In recent years, research has been conducted into technologies that allow farm equipment to automatically perform tasks in the field, such as spreading fertilizer, using work data for that task, such as a fertilization map that sets the amount of fertilizer to be spread.

For example, Patent Document 1 discloses a technology that generates a spraying plan that sets the amount of fertilizer to be sprayed, and then uses the generated spraying plan to have a work device automatically apply fertilizer.

Japanese Patent Application Laid-Open No. 2019-187377

The technology described in Patent Document 1 is based on the premise that work data is generated for a single field and that the work is performed by a work device using the generated work data. However, there are cases where work data is generated for multiple fields and work is performed in multiple fields by a work device.

Generally, work data is generated based on registered field information. In some cases, the areas of multiple fields represented in the registered field information overlap with each other due to factors such as past field areas or missed updates to field areas. When field areas overlap with each other, the work areas represented in the generated work data may also overlap with each other.

For example, the same field may be harvested in the spring, say May, and in the fall, say October, of the same year. In this case, if work data, such as fertilization data, is generated from the yield data for the year the harvest took place, work data based on the yield data for the spring harvest and work data based on the yield data for the fall harvest will be generated.

In this way, when the work areas represented in the work data include overlapping areas, this can have a negative impact on cultivation, such as work devices performing overlapping tasks.

In light of the above situation, one of the objectives of this disclosure is to reduce the output of overlapping work data. Other objectives can be understood from the following description and explanation of the embodiments.

The following describes the means for solving the problems using the numbers and symbols used in the description of the invention. These numbers and symbols are added in parentheses for reference purposes to show an example of the correspondence between the claims and the description of the invention. Therefore, the claims should not be interpreted as being limited by the parenthetical descriptions.

To achieve the above objective, one embodiment of a data management method includes detecting overlapping work data, among multiple work data for work performed by a work device (30) in multiple fields (400), in which at least a portion of the work areas represented by the work data overlap with each other. The data management method also includes outputting non-overlapping work data in which at least a portion of the overlapping work data has been removed from the multiple work data. Here, the work areas represented by each of the output non-overlapping work data do not overlap with work areas represented by other work data in the non-overlapping work data.

To achieve the above object, a data management system (1000) according to one embodiment includes an overlap detection unit (170) and an output unit (180). The overlap detection unit (170) detects overlapping work data, among a plurality of work data for a work device (30) to perform work in a plurality of fields (400), in which at least a portion of the work areas represented by the work data overlap with each other. The output unit (180) outputs non-overlapping work data obtained by excluding at least a portion of the overlapping work data from the plurality of work data. Here, the work areas represented by each of the output non-overlapping work data do not overlap with work areas represented by other work data of the non-overlapping work data.

To achieve the above objective, a data management program (310) according to one embodiment causes a calculation device (120) to detect overlapping work data, among multiple work data for a work device (30) to perform work in multiple fields (400), in which at least a portion of the work areas represented by the work data overlap with each other. The data management program also causes the calculation device (120) to output non-overlapping work data in which at least a portion of the overlapping work data has been removed from the multiple work data. Here, the work areas represented by each of the output non-overlapping work data do not overlap with work areas represented by other work data in the non-overlapping work data.

The above configuration reduces the output of overlapping work data.

FIG. 1 is a configuration diagram of a data management system according to an embodiment. FIG. 2 is a diagram illustrating a field for which work data is generated in one embodiment. FIG. 2 is a diagram illustrating a field for which work data is generated in one embodiment. FIG. 2 is a diagram illustrating functional blocks executed by a data management system according to an embodiment. 1 is a flowchart illustrating a process performed by a data management system according to an embodiment. 1 is a flowchart illustrating a process performed by a data management system according to an embodiment.

(Embodiment 1)
A data management system 1000 according to this embodiment of the present invention will be described with reference to the drawings. In this embodiment, as shown in Fig. 1, the data management system 1000 includes a data management device 100 and a terminal 200. The data management device 100 is communicably connected to the terminal 200 and a working device 30 via a network 20, for example, the Internet.

The data management device 100 generates work data, for example, data representing the amount of fertilizer to be spread on small areas obtained by dividing a field into a mesh pattern. The generated work data is registered in the work device 30. The work device 30 spreads the amount of fertilizer registered in the work data according to each position in the field. The work data represents any work performed by the work device 30, such as fertilizing or spraying pesticides. Note that work devices 30 include tractors that pull spraying machines that spread fertilizer or pesticides, drones that spray pesticides, etc.

For example, work data represents the location where work is performed (e.g., latitude, longitude, etc.) in association with the work content to be performed at that location (e.g., amount applied). For example, if the work data is fertilization data for applying fertilizer, the work data represents the amount of fertilizer to be applied to each of multiple small areas into which the field is divided, such as the amount applied per unit area. Also, if the work data is pesticide application data for applying pesticide, the work data represents the amount of pesticide to be applied to each of multiple small areas into which the field is divided, such as the amount applied per unit area.

The work device 30 may have multiple work data registered corresponding to multiple fields. As shown in FIG. 2, the work data stores information for spreading fertilizer on multiple fields 400, for example, a first field 400-1, a second field 400-2, and a third field 400-3. Here, as shown in FIG. 3, the first field 400-1 may have been previously divided into multiple divided fields 410, for example, a first divided field 410-1 and a second divided field 410-2, with different crops being cultivated in each divided field 410. In this case, the work data may record information for spreading fertilizer on the previous divided fields 410.

When the work areas represented in multiple work data overlap in part, the work device 30 will apply fertilizer to the same location multiple times, spreading more than the planned amount of fertilizer. The work device 30 is equipped with a positioning device, such as a GNSS (Global Navigation Satellite System) receiver, and spreads fertilizer in the amount represented in the work data according to the position of the work device 30. For example, the work device 30 obtains the amount to be spread at the position of the work device 30 from the work data and spreads fertilizer in the obtained amount. Therefore, in the example shown in FIG. 3, the work device 30 performs two spraying operations in the first field 400-1: one based on the work data registered as the first field 400-1, and the other based on the work data registered as the divided field 410. This results in overlapping fertilization of the first field 400-1.

For this reason, the data management device 100 restricts the registration of work data when the work areas represented by the work data overlap. In this way, the data management system 1000 reduces the number of times that the work device 30 performs overlapping work.

The work area represented by the work data represents the area within the field 400 where work is performed by the work device 30. Information on an area larger than the work area may also be registered in the work data. In this case, the work data includes information representing the area of the field 400, for example, to distinguish the work area from other areas. The work device 30 moves within the field 400, obtains the work content, such as the amount of spraying, at the location where the work device 30 is located from the work data, and performs the work.

(Data management system configuration)
The configuration of the data management device 100 will be described. As shown in FIG. 1 , the data management device 100 includes an input/output device 110, a calculation device 120, a communication device 130, and a storage device 140. The data management device 100 is, for example, a computer. Information used by the calculation device 120 to execute processing is input to the input/output device 110. The input/output device 110 also outputs the results of processing executed by the calculation device 120. The input/output device 110 includes various input devices and output devices, such as a keyboard, a mouse, a microphone, a display, a speaker, and a touch panel. The input/output device 110 may be omitted.

The communication device 130 is electrically connected to the network 20 and communicates with each device via the network 20. The communication device 130 transfers signals received from each device, for example, the terminal 200, to the calculation device 120. The communication device 130 also transfers signals generated by the calculation device 120 to each device, for example, the terminal 200. The communication device 130 includes various interfaces, for example, a network interface card (NIC) and a universal serial bus (USB).

The storage device 140 stores various data for outputting work data whose working areas do not overlap, such as field data 300 and a data management program 310. The storage device 140 is used as a non-transitory tangible storage medium for storing the data management program 310. The data management program 310 may be provided as a computer program product recorded on a computer-readable storage medium 1, or as a computer program product downloadable from a server.

The field data 300 stores area information representing the area of the field 400 where the work device 30 performs work, and the area of the divided field 410. For example, the field data 300 stores the position (latitude, longitude, etc.) and shape of the field 400 and the divided field 410. The area information for the field 400 and the divided field 410 is, for example, entered by the user into the terminal 200 and registered in advance.

The computing device 120 reads and executes the data management program 310 from the storage device 140, and performs various data processing to output working data whose areas do not overlap. For example, the computing device 120 includes a central processing unit (CPU).

By reading and executing the data management program 310, the computing device 120 implements a data storage unit 150, a work data generation unit 160, an overlap detection unit 170, and an output unit 180, as shown in FIG. 4. The data storage unit 150 stores field data 300. The work data generation unit 160 generates work data based on area information stored in the field data 300. The overlap detection unit 170 detects overlapping work data, where the area represented by the generated work data overlaps with the area represented by other work data. The output unit 180 outputs multiple work data whose areas represented by the work data do not overlap with each other.

Next, the configuration of the terminal 200 will be described. As shown in FIG. 1, the terminal 200 includes an input/output device 210, a computing device 220, a communication device 230, and a storage device 240. The terminal 200 includes, for example, a computer, a tablet, a mobile phone, etc. Information used by the computing device 220 to execute processing is input to the input/output device 210. The input/output device 210 also outputs the results of processing executed by the computing device 220. The input/output device 210 includes various input and output devices, such as a keyboard, a mouse, a microphone, a display, a speaker, a touch panel, etc.

The communication device 230 is electrically connected to the network 20 and communicates with the data management device 100 via the network 20. The communication device 230 transfers signals acquired from the data management device 100 to the calculation device 220. It also transfers signals generated by the calculation device 220 to the data management device 100. The communication device 230 includes various interfaces, such as a transceiver used for wireless communication such as a wireless LAN (Local Area Network) or a cellular network, a NIC (Network Interface Card), and a USB (Universal Serial Bus).

The storage device 240 stores various data for acquiring work data, such as the notification program 320. The storage device 240 is used as a non-transitory tangible storage medium for storing the notification program 320. The notification program 320 may be provided as a computer program product recorded on a computer-readable storage medium 2, or as a computer program product downloadable from a server.

By reading and executing the notification program 320, the computing device 220 cooperates with the input/output device 210 to implement the notification unit 250, as shown in FIG. 4. The notification unit 250 acquires work data from the data management device 100 and registers the acquired work data in the work device 30. Furthermore, based on a signal from the data management device 100, the notification unit 250 notifies that there is work data with overlapping areas.

(Data Management System Operation)
1 executes a data management program 310 when the data management device 100 is started. The user inputs a startup operation to start a notification program 320 to the input/output device 210 of the terminal 200. When the user inputs an input operation, the calculation device 220 of the terminal 200 executes the notification program 320 and starts the process shown in FIG. 5, which is a data management method.

In step S110, the notification unit 250, which is realized by the calculation device 220, accepts multiple requests for work data. For example, the notification unit 250 outputs information representing the fields 400 registered in the field data 300. The user inputs a request to the input/output device 210 to select the field 400 for which work data will be generated from the output information. Based on the request, the notification unit 250 transmits request information representing the field 400 for which work data will be generated to the data management device 100. The notification unit 250 may also transmit request information for generating work data for the registered field 400 without the user having to input a selection operation.

In step S120, the work data generation unit 160, implemented by the calculation device 120 of the data management device 100, generates work data for the target field 400 based on the request information. The work data represents, for example, the work to be performed for each of multiple small areas into which the field 400 is divided, such as the amount of fertilizer to be applied.

First, the work data generation unit 160 acquires the area of the field 400 for which work data is to be generated based on the request information. For example, the work data generation unit 160 acquires a list of the fields 400 for which work data is to be generated from the request information, and acquires the area of the target field 400 from the field data 300.

Next, the work data generation unit 160 generates work data based on past information about the field 400, such as the yield in a small area of the field 400, and the Normalized Difference Vegetation Index (NDVI), which indicates the presence or absence and activity of vegetation in the small area of the field 400. For example, the work data generation unit 160 generates fertilization data so that the amount of fertilizer applied in a small area with a low past yield is relatively greater than that in a small area with a high past yield. The work data generation unit 160 may also generate work data based on work information input by the user to the input/output device 210 of the terminal 200, such as information indicating the amount of fertilizer applied for each small area.

In step S130, the duplication detection unit 170 determines whether any of the generated work data contains overlapping work data whose area overlaps with that of other work data. The duplication detection unit 170 detects overlapping work data from the generated work data, where at least a portion of the area represented by the work data overlaps with that represented by other work data. When the duplication detection unit 170 detects overlapping work data, it outputs overlap information representing the field 400 corresponding to the overlapping work data to the terminal 200. When the duplication detection unit 170 outputs the overlap information, processing proceeds to step S140. When no overlapping work data is detected, processing proceeds to step S160.

In step S140, the notification unit 250 of the terminal 200 accepts a selection operation for the detected overlapping work data. For example, the notification unit 250 outputs overlap information indicating the field 400 and divided field 410 corresponding to the detected overlapping work data to the input/output device 210. For example, the notification unit 250 displays an image showing the field 400 and divided field 410 corresponding to the overlapping work data on a map. The user checks the output overlap information and inputs a selection operation to the input/output device 210 to select the field 400 and divided field 410 corresponding to the work data to be generated. For example, to generate work data corresponding to the field 400 shown in Figure 2, the user inputs a selection operation to select the first field 400-1.

The notification unit 250 determines whether the work areas of the work data corresponding to the selected fields 400 overlap. When the work areas of the selected work data overlap, the notification unit 250 notifies the user that the work areas overlap and accepts another selection operation. When the work areas of the work data do not overlap, the notification unit 250 outputs selection information representing the selected field 400 to the data management device 100. Note that the notification unit 250 may also obtain information representing combinations of overlapping work data whose work areas overlap from the overlap detection unit 170 of the data management device 100.

In step S150 shown in FIG. 5, the overlap detection unit 170 of the data management device 100 excludes overlapping work data corresponding to non-selected fields 400, such as divided fields 410, based on the selection information representing the selected field 400. The overlap detection unit 170 excludes overlapping work data corresponding to non-selected fields 400 from the generated work data, and determines multiple work data whose work areas do not overlap with each other. Here, the determined multiple work data may be referred to as non-overlapping work data whose work areas do not overlap with each other.

In step S160, the output unit 180 outputs multiple pieces of work data whose work areas do not overlap each other, for example, non-overlapping work data, to the terminal 200.

In step S170, the notification unit 250 of the terminal 200 acquires multiple pieces of work data, for example, non-overlapping work data, from the output unit 180 of the data management device 100. The acquired multiple pieces of work data are registered in the work device 30 and used when the work device 30 performs work in the field 400.

In this way, the data management system 1000 outputs work data in which the work areas do not overlap, reducing duplicate work by the work device 30. Furthermore, other effects caused by overlapping work areas represented in the work data are reduced.

(Embodiment 2)
In the first embodiment, the overlap detection unit 170 detects overlapping work areas after generating the work data, but this is not limiting. The overlap detection unit 170 may detect overlapping work areas before generating the work data. In this case, the configuration of the data management system 1000 is the same as in the first embodiment, and therefore a detailed description thereof will be omitted.

(Data Management System Operation)
1 executes a data management program 310 when the data management device 100 is started. The user inputs a startup operation to start a notification program 320 to the input/output device 210 of the terminal 200. When the user inputs an input operation, the calculation device 220 of the terminal 200 executes the notification program 320 and starts the process shown in FIG. 6, which is a data management method.

In step S110, the notification unit 250, implemented by the computing device 220, accepts multiple operation data request operations. The processing in step S110 is the same as in embodiment 1, and therefore a detailed description will be omitted.

In step S112, the overlap detection unit 170 of the data management device 100 determines whether any of the selected fields 400 are overlapping fields, where the area of the field 400 overlaps with the area of another field 400. The overlap detection unit 170 detects overlapping fields from the selected fields 400, where at least a portion of the area included in the field 400 overlaps with an area included in another field 400. When the overlap detection unit 170 detects an overlapping field, it outputs overlap information indicating the overlapping field to the terminal 200. When the overlap detection unit 170 outputs the overlap information, processing proceeds to step S114. If no overlapping fields are detected, processing proceeds to step S120.

In step S114, the notification unit 250 of the terminal 200 accepts a selection operation for the detected overlapping field. For example, the notification unit 250 outputs overlap information representing the field 400 and the divided field 410 corresponding to the detected overlapping field to the input/output device 210. The user checks the output overlap information and inputs a selection operation to the input/output device 210 to select the field 400 and the divided field 410 corresponding to the work data to be generated. For example, to generate work data corresponding to the field 400 shown in Figure 2, the user inputs a selection operation to select the first field 400-1.

The notification unit 250 determines whether the areas of the selected fields 400 overlap each other. When the areas of the selected fields 400 overlap each other, the notification unit 250 notifies the user that the areas of the fields 400 overlap and accepts another selection operation. When the areas of the fields 400 do not overlap each other, the notification unit 250 outputs selection information representing the selected field 400 to the data management device 100. Note that the notification unit 250 may also obtain information representing a combination of overlapping fields, where the areas of the fields 400 overlap each other, from the overlap detection unit 170 of the data management device 100.

In step S116 shown in FIG. 6, the overlap detection unit 170 of the data management device 100 excludes non-selected fields 400, for example, overlapping fields corresponding to divided fields 410, based on the selection information representing the selected fields 400. The overlap detection unit 170 excludes non-selected overlapping fields from the initially selected fields 400 and determines multiple fields 400 whose areas do not overlap with each other. Here, the determined multiple fields 400 may be referred to as non-overlapping fields whose areas do not overlap with each other.

In step S120, the work data generation unit 160 generates work data for the determined multiple fields 400, for example, non-overlapping fields. First, the work data generation unit 160 acquires the areas of the fields 400 determined by the overlap detection unit 170, for example, the non-overlapping fields. For example, the work data generation unit 160 acquires a list of the non-overlapping fields determined by the overlap detection unit 170 and acquires the areas of the non-overlapping fields from the field data 300. Next, the work data generation unit 160 generates work data based on past information about the fields 400. The generated work data represents non-overlapping work data whose work areas do not overlap with each other, as the areas of the fields 400 do not overlap.

In step S160, the output unit 180 outputs multiple pieces of work data whose work areas do not overlap each other, for example, non-overlapping work data, to the terminal 200.

In step S170, the notification unit 250 of the terminal 200 acquires multiple pieces of work data from the output unit 180 of the data management device 100. The acquired multiple pieces of work data are registered in the work device 30 and used when the work device 30 performs work in the field 400.

In this way, the overlap detection unit 170 may determine whether the work areas represented by the work data overlap before generating the work data.

(Modification)
The configurations described in each embodiment may be modified as desired without impairing functionality. For example, when work areas represented in work data overlap, the data management system 1000 may exclude all overlapping work data with overlapping work areas and output the work data to the terminal 200. In this case, step S140 is omitted in the example shown in FIG. 5 . In step S150, the overlap detection unit 170 determines multiple work data sets from which all overlapping work data have been excluded. In step S160, the output unit 180 outputs the multiple work data sets excluding the overlapping work data to the terminal 200.

Furthermore, when all overlapping work data with overlapping work areas is excluded, step S114 is omitted in the example shown in Figure 6. In step S116, the overlap detection unit 170 determines multiple fields 400 from which all overlapping fields have been excluded. In step S120, the work data generation unit 160 generates work data for the multiple fields 400 excluding the overlapping fields.

The field data 300 may store a priority for generating work data for each field 400 (including divided fields 410). The priority may be set by the user via the terminal 200. The priority may also be set based on the date and time the field 400 was registered. For example, the priority may be set higher the more recently the field 400 was registered.

When a priority has been set for the field 400, the overlap detection unit 170 may output overlap information, including the priority of the field 400, to the terminal 200 in step S130 shown in FIG. 5. In step S140, the notification unit 250 of the terminal 200 outputs the overlap information, including the priority of the field 400, to the input/output device 210. This allows the user to easily select the field 400 for which work data should be generated by checking the priority of the field 400.

Furthermore, when a priority has been set for the field 400, the duplication detection unit 170 may determine the overlapping work data to exclude based on the priority set for the field 400. In this case, step S140 shown in FIG. 5 and step S114 shown in FIG. 6 may be omitted. The duplication detection unit 170 determines the overlapping work data to exclude based on the priority in step S150 shown in FIG. 5. For example, the duplication detection unit 170 detects overlapping work data whose work areas overlap, and excludes from the generated multiple work data sets all of the detected overlapping work data sets except for the overlapping work data with the highest priority. The processing from step S160 onwards is performed on the multiple work data sets from which some of the overlapping work data have been excluded.

In this case, in step S170, the notification unit 250 of the terminal 200 may notify the user that overlapping work data exists. Furthermore, the notification unit 250 may notify the user of the field 400 corresponding to the overlapping work data and the field 400 corresponding to the output work data. For example, in step S160, the output unit 180 of the data management device 100 outputs image information for displaying on a map the field 400 corresponding to the overlapping work data and the field 400 corresponding to the output work data. In step S170, the notification unit 250 displays an image on a map based on the image information, showing the field 400 corresponding to the overlapping work data and the field 400 corresponding to the output work data.

Furthermore, in step S116 shown in FIG. 6, the overlap detection unit 170 determines overlapping fields to exclude based on priority. For example, the overlap detection unit 170 detects overlapping fields where the areas of the fields 400 overlap, and excludes the overlapping fields from the multiple fields 400, excluding the overlapping field with the highest priority among the detected overlapping work data. The processing from step S120 onwards is performed for the multiple fields 400 from which some of the overlapping fields have been excluded.

In this case, in step S170, the notification unit 250 of the terminal 200 may notify the user that there is overlapping work data with overlapping areas, for example, an overlapping field. Furthermore, the notification unit 250 may notify the user of the field 400 corresponding to the overlapping work data, for example, the overlapping field, and the field 400 corresponding to the output work data. For example, in step S160, the output unit 180 of the data management device 100 outputs image information for displaying on a map the field 400 corresponding to the overlapping work data, for example, the overlapping field, and the field 400 corresponding to the output work data. In step S170, the notification unit 250 displays an image showing on a map the overlapping field and the field 400 corresponding to the output work data.

The above-described embodiments and variations are merely examples, and the configurations described in each embodiment and variation may be modified and/or combined as desired, provided that the functionality is not impaired. Furthermore, some of the functions described in the embodiments and variations may be omitted as long as the required functionality is achieved. For example, the data management system 1000 shown in FIG. 1 does not need to include the terminal 200. The terminal 200 may be incorporated into the operation device 30. Furthermore, all or part of the processing of the data management device 100 may be executed by the terminal 200. For example, the duplication detection unit 170 and the output unit 180 may be implemented by the computing device 220 of the terminal 200. In this case, steps S130, S150, and S160 shown in FIG. 5 may be executed by the computing device 220 of the terminal 200. Furthermore, all or part of the processing of the terminal 200 may be executed by the data management device 100. Furthermore, the data management program 310 may include a notification program 320.

The work data generation unit 160 of the data management device 100 may also be implemented in another system. In this case, steps S110 and S120 may be omitted in the example shown in FIG. 5. The data management system 1000 performs processing from step S130 on multiple work data generated in the other system. For example, in step S130, the overlap detection unit 170 detects work data whose work areas overlap with each other among the multiple work data generated in the other system.

The duplication detection unit 170 may also exclude unselected duplicate work data or duplicate fields and determine one work data or field 400. In this case, the output unit 180 outputs the determined one work data or one work data corresponding to the determined field 400.

1, 2: Storage medium 20: Network 30: Work device 100: Data management device 110: Input/output device 120: Computing device 130: Communication device 140: Storage device 150: Data storage unit 160: Work data generation unit 170: Duplication detection unit 180: Output unit 200: Terminal 210: Input/output device 220: Computing device 230: Communication device 240: Storage device 250: Notification unit 300: Field data 310: Data management program 320: Notification program 400: Field 410: Divided field (field)
1000: Data management system

Claims (9)

Detecting overlapping work data, among a plurality of work data representing work to be performed by the work implement in a plurality of fields, in which work areas represented by the work data at least partially overlap with each other;
outputting non-overlapping work data obtained by excluding at least some of the overlapping work data from the plurality of work data;
Including,
each of the plurality of work data represents an entire work to be performed in one field of the plurality of fields, and is used when work is performed in the one field;
A data management method, wherein the work area represented by each of the output non-overlapping work data does not overlap with the work area represented by other work data of the non-overlapping work data. Detecting the duplicate work data includes:
The data management method according to claim 1 , further comprising: determining the non-overlapping task data by excluding some of the overlapping task data from the plurality of task data based on a selection operation input by a user. The data management method according to claim 2 , further comprising displaying to the user an image showing overlap information representing fields corresponding to the overlapping work data on a map, and accepting an operation by the user to select a field. Detecting overlapping work data in which at least a part of the work area represented by the work data overlaps with each other among a plurality of work data for the work implement to perform work in a plurality of fields;
outputting non-overlapping task data obtained by excluding at least a portion of the overlapping task data from the plurality of task data;
Including,
Detecting the duplicate work data includes:
determining the non-overlapping work data by excluding a portion of the overlapping work data from the plurality of work data based on priorities set for the plurality of fields;
A data management method, wherein the work area represented by each of the output non-overlapping work data does not overlap with the work area represented by other work data of the non-overlapping work data. outputting the non-duplicate work data
The data management method according to claim 1 , further comprising: outputting image information for displaying on a map the farm field corresponding to the overlapping work data. generating the plurality of work data based on areas of the plurality of fields;
Detecting the duplicate work data includes:
Detecting the duplicated work data from the generated plurality of work data;
excluding at least a portion of the overlapping work data detected from the plurality of work data to determine the non-overlapping work data;
The data management method according to claim 1 , further comprising: generating the plurality of operation data;
Detecting the duplicate work data includes:
detecting overlapping fields among the plurality of fields, the fields having at least a portion of their areas overlapping each other;
determining non-overlapping fields by excluding at least some of the overlapping fields detected from the plurality of fields;
Including,
Generating the plurality of pieces of work data includes:
The data management method according to claim 1 , further comprising: generating the plurality of pieces of work data based on areas representing the non-overlapping fields. an overlap detection unit that detects overlapping work data, among a plurality of work data representing work to be performed by work implements in a plurality of fields, in which work areas represented by the work data overlap at least partially with each other;
an output unit that outputs non-overlapping work data obtained by excluding at least some of the overlapping work data from the plurality of work data;
Equipped with
each of the plurality of work data represents an entire work to be performed in one field of the plurality of fields, and is used when work is performed in the one field;
A data management system in which the work area represented by each of the output non-overlapping work data does not overlap with the work area represented by other work data of the non-overlapping work data. Detecting overlapping work data, among a plurality of work data representing work to be performed by the work implement in a plurality of fields, in which work areas represented by the work data at least partially overlap with each other;
outputting non-overlapping work data obtained by excluding at least some of the overlapping work data from the plurality of work data;
causing a computing device to execute
each of the plurality of work data represents an entire work to be performed in one field of the plurality of fields, and is used when work is performed in the one field;
A data management program in which a work area represented by each of the output non-overlapping work data does not overlap with a work area represented by other work data of the non-overlapping work data.