Device, method and program for creating support information

Abstract

To provide a support information creating device for facilitating inputting of inspection results of road accessories to an inspection information recording database.SOLUTION: A support information creating device 1 comprises: an inspection table information inputting part 301 for receiving an input of inspection table information by reading inspection table information; a facility ID outputting part 302 for creating a facility ID of a road accessory, and for outputting the created facility ID; a MICHI facility key and management key inputting part 303 for receiving an input of a MICHI facility key and a management key; an ID, key and inspection table information integrating part 18 for integrating a facility ID, a MICHI facility key, a management key, and inspection table information, and for creating format data for xROAD registration; and an input data outputting part 5 for outputting format data for xROAD registration.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a tool for assisting in inputting inspection results of road accessories to an inspection information record database, and more particularly to an assistance information creating device, an assistance information creating method, and an assistance information creating program.

[0002] Road accessories such as signs and road lighting facilities are required to undergo regular inspections once every few years. Starting in fiscal year 2023, it will be mandatory to input the results of regular inspections into the data platform "xROAD." The data platform "xROAD" forms part of the "National Road Facility Inspection Database." This invention supports this data input work. [Background technology]

[0003] Patent Document 1 discloses a collaborative processing system that enables flexible access to documents and map data by linking a data platform, a GIS (Graphic Information System), with a document file system, and mutually sharing and utilizing information organization functions. The map data includes location data, attribute data, and shape data. Using these data, it is possible to access the corresponding document data from within a document database.

[0004] Furthermore, Patent Document 1 enables access to corresponding attribute data and shape data by using document data and an ID that specifies that document data. However, the invention described in Patent Document 1 is not a mechanism for registering information that is updated, such as inspection results, but rather a method for utilizing existing registered information. Furthermore, the invention described in Patent Document 1 does not have a mechanism for converting information into CSV output or the like using electronic files or input information. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2003-167919 A Summary of the Invention [Problem to be solved by the invention]

[0006] Possible methods for inputting inspection results into xROAD include manual input and bulk registration using a CSV file for uploading to xROAD.

[0007] When inputting data manually, many of the inspection results must be entered in a pull-down format. It takes about 20 to 30 minutes to input data per unit, and there are often hundreds or thousands of units to be inspected. This means that the data input process takes a huge amount of time.

[0008] When using the input method of CSV for uploading to xROAD, the CSV format is special, so it is difficult to convert inspection results into CSV. In addition, when inputting to xROAD, it is necessary to input xROAD's unique IDs, such as the facility ID, MICHI facility key, and management key. The facility ID is an ID generated based on latitude and longitude information. The MICHI facility key is an ID that can be found by searching the database using the facility ID. In addition, the management key is an ID that changes depending on the business operator, management area, etc. It is necessary to input these IDs when inputting to xROAD. Therefore, inputting inspection results into xROAD requires additional work in addition to simply transcribing the inspection sheet data.

[0009] An object of the present invention is to provide a support information creating device that makes it easy to input the inspection results of road accessories to an inspection information record database. [Means for solving the problem]

[0010] The support information creation device of the present invention is a support information creation device that creates xROAD registration format data for registering inspection results recorded on an inspection form for a road accessory in an inspection information registration database, and includes an inspection form information input unit that accepts input of the inspection form information by reading the inspection form information contained in the inspection form, a facility ID output unit that creates a facility ID for the road accessory from the latitude and longitude information of the road accessory listed on the inspection form and outputs the created facility ID, a MICHI facility key / management key input unit that accepts input of a MICHI facility key for identifying the road accessory and a management key for accessing the inspection information registration database, an ID / key / inspection form information integration unit that integrates the facility ID, the MICHI facility key, the management key and the inspection form information to create the xROAD registration format data, and an input data output unit that outputs the xROAD registration format data. Effect of the Invention

[0011] According to the present invention, it is possible to provide a support information creating device that makes it easy to input the inspection results of road accessories to an inspection information record database. [Brief description of the drawings]

[0012] [Figure 1] FIG. 13 is a diagram showing an overview of the creation of the xROAD registration format csv using the support information creation device. [Diagram 2] FIG. 2 is a diagram showing an internal configuration of a support information creating device. [Diagram 3] FIG. 2 is a diagram showing the inside of the support information creating device by function. [Figure 4] 13 is a flowchart showing a process flow of a support information creating method. [Diagram 5] FIG. 13 is a diagram showing the process of the support information creation method from the viewpoint of data. [Figure 6] FIG. 2 is a diagram showing a hardware configuration of a support information creating device. [Figure 7] FIG. 13 is a diagram showing an overview of the data included in the xROAD registration format csv. [Figure 8] A diagram showing the structure of xROAD registration data including image data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] (Summary of the support information creation device) 1 is a diagram showing an overview of the creation of the xROAD registration format csv60 using a support information creation device 1. The support information creation device 1 is a device that outputs a CSV for input to an inspection result platform such as xROAD based on information contained in an electronic file of an inspection sheet 50 related to road accessories. The following describes an example in which the input CSV is the xROAD registration format csv60. Also, CSV is an example of a data format, and the data format is not limited to CSV.

[0014] In the example shown in FIG. 1, the support information creation device 1 is configured as a PC (personal computer). The support information creation device 1 creates an input CSV 60 by integrating data processing by software in the PC, a MICHI facility key search function in xROAD, and input work by an operator. In this embodiment, an inspection table 50 in a predetermined format is created by an inspector operating a tablet on-site on which an application for inputting inspection results (hereinafter, referred to as an inspection application) is installed, and one or more inspection tables 50 are input (transferred) to the support information creation device 1, but this configuration is not limited to this. For example, the tablet side may be configured to include each function of the support information creation device 1 according to this embodiment. In this configuration, the support information creation device 1 alone can create an input CSV 60 by integrating the creation of an inspection table, the MICHI facility key search function in xROAD, and input work by an operator.

[0015] As indicated by arrow 101, electronic data of the checklist 50 is input to the support information creation device 1. As indicated by arrow 102, the support information creation device 1 outputs predetermined information to the worker 100 based on the input electronic data. As indicated by arrow 103, the worker 100 inputs predetermined new information to the support information creation device 1 based on the output information. As indicated by arrow 104, the support information creation device 1 creates and outputs an xROAD registration format csv60 based on the electronic data of the checklist 50 and the information input by the worker 100.

[0016] In this way, the support information creation device 1 can create the xROAD registration format csv60 while reducing the input burden on the worker 100.

[0017] The input of the inspection list 50 to the support information creating device 1 is not limited to an inspection list for one road accessory. For example, a plurality of inspection lists 50 for different road accessories, such as an inspection list 51 for accessory A, an inspection list 52 for accessory B, and an inspection list 53 for accessory C, may be input to the support information creating device 1.

[0018] When multiple inspection tables 50 are input into the support information creation device 1, an xROAD registration format csv60 may be created for each of the multiple inspection tables 50, or the multiple inspection tables 50 may be integrated to create an xROAD registration format csv for bulk registration.

[0019] (Configuration of the support information creation device) The support information creating device 1 will be specifically described with reference to Fig. 2. Fig. 2 is a diagram showing a specific configuration of the support information creating device 1. As shown in Fig. 2, the support information creating device 1 includes a checklist information input unit 301, a facility ID output unit 302, a MICHI facility key / management key input unit 303, an ID / key / checklist information integrator 18, and an input CSV output unit 501.

[0020] The checklist information input unit 301 is a part that accepts input of checklist information by reading the checklist information, which is information included in the checklist 50.

[0021] The facility ID output unit 302 is a part that creates a facility ID for the road accessory from the latitude and longitude information of the road accessory recorded on the inspection list 50, and outputs the created facility ID.

[0022] The MICHI facility key / management key input unit 303 is a part that accepts input of a MICHI facility key for identifying road accessories and a management key for accessing the inspection information registration database.

[0023] The ID / key / checklist information integration unit 18 is a part that integrates the facility ID, MICHI facility key, management key and checklist information, and creates a CSV format for xROAD registration.

[0024] The input csv output unit 501 is a part that outputs the xROAD registration format csv.

[0025] The checklist information input unit 301, the facility ID output unit 302, and the MICHI facility key / management key input unit 303 correspond to the input unit 3 in the support information creation device 1. The input CSV output unit 501 corresponds to the output unit 5 in the support information creation device 1.

[0026] (Processing Overview) An overview of the processing in the support information creation device 1 will be described. First, electronic data is input from the file of the checklist 50 to the checklist information input unit 301, as indicated by the arrow 101. The facility ID output unit 302 acquires the latitude and longitude information of the road accessory listed on the checklist from the input electronic data, and creates a facility ID. The facility ID is an ID that identifies the road accessory. The facility ID is created by combining the latitude information and the longitude information.

[0027] The facility ID output unit 302 outputs the created facility ID, as indicated by arrow 102. The worker 100 searches for a MICHI facility key based on the facility ID. The MICHI facility key is an ID that identifies the road accessory in the inspection information registration database. The MICHI facility key is an individual key created by combining the management number registered in the inspection form 50 and the facility ID. The worker 100 identifies the MICHI facility key for the target road accessory by searching the inspection information registration database using the facility ID.

[0028] If the latitude and longitude of the road accessory recorded on the inspection form coincides with the latitude and longitude of the road accessory recorded in the inspection information registration database, the MICHI facility key is identified.

[0029] In addition, if the latitude and longitude of the road accessory recorded on the inspection form do not match the latitude and longitude of the road accessory recorded in the inspection information registration database, the road accessory recorded on the inspection form may be registered as a new road accessory that does not exist in the inspection information registration database, or the response may be discussed on a case-by-case basis with the inspection information registration database administrator, etc.

[0030] After the MICHI facility key has been identified, the worker 100 inputs the MICHI facility key and management key into the MICHI facility key / management key input unit 303, as indicated by arrow 103. The management key is an ID indicating, for example, the business operator code, the target area code, the business operator classification, etc. The management key is a value that changes depending on the user logged in to xROAD. Even if there are multiple inspection tables 50, the management key only needs to be input once. In other words, by inputting the management key once, the same management key will be input (copied) into the management keys of other facilities.

[0031] When the MICHI facility key and management key are entered into the MICHI facility key / management key input unit 303, the ID / key / inspection table information integration unit 18 creates the xROAD registration format csv60. The ID / key / inspection table information integration unit 18 integrates the electronic data of the inspection table 50, the MICHI facility key, and the management key. This completes the data required for registration in the inspection information registration database.

[0032] The ID / key / inspection sheet information integration unit 18 creates a CSV format for xROAD registration based on the integrated electronic data of the inspection sheet 50, the MICHI facility key, and the management key.

[0033] The input csv output unit 501 outputs the xROAD registration format csv, as indicated by the arrow 104. This completes the creation and output of the batch registration csv file by the support information creation device 1.

[0034] Using the created and output bulk registration CSV file, it is possible to bulk register the contents of inspection sheet 50 to xROAD.

[0035] (Functional configuration of the support information creation device) 3 is a diagram showing the internal functions of the support information creating device 1. The support information creating device 1 can be classified into an input unit 3, a processing unit 10, and an output unit 5 according to its functions.

[0036] (Input section) As shown by arrows 111 to 113, an inspection table file, a management key, and a MICHI facility key are input to the support information creating device 1. The input is made to the input unit 3.

[0037] The checklist information input section 301, the facility ID output section 302 and the MICHI facility key / management key input section 303 shown in FIG.

[0038] (Processing section) The input data is processed by the processing unit 10, and a bulk registration CSV file is created. The processing unit 10 includes a facility ID creation unit 12, an extraction unit 14, an integration unit 16, and a second integration unit 18.

[0039] The facility ID generating unit 12 generates a facility ID. A facility ID output unit 302 shown in FIG.

[0040] The extraction unit 14 is a part that extracts various pieces of information related to inspection, the latitude and longitude of road accessories, and the like from the input inspection list information.

[0041] The integration unit 16 is a part that integrates the inspection information, facility ID, MICHI facility key, and management key so that they correspond to the input items of the inspection information registration database, and creates a csv format for xROAD registration.

[0042] The second integration unit 18 is a unit that, when multiple checklists are read, further integrates the information integrated for each checklist by the integration unit 16, and creates a CSV file for bulk registration in xROAD.

[0043] 2 corresponds to the extraction unit 14, the integration unit 16, and the second integration unit 18. The ID / key / checklist information integration unit 18 and the second integration unit 18 have almost the same functions, and therefore are denoted by the same component numbers.

[0044] (Output section) The created bulk registration csv file is output via the output unit 5.

[0045] The input CSV output unit 501 shown in FIG.

[0046] (Processing flow) The process flow of the support information creation method will be described with reference to Fig. 4. Fig. 4 is a flowchart showing the process flow of the support information creation method. In Fig. 4 and the following description, S1 indicates step 1. The same applies to S2 and onwards. Also, Fig. 4 is based on the premise that an inspection list for a plurality of different road accessories is read, but the same applies to the case of an inspection list for a single road accessory. In the case of an inspection list for a single road accessory, S6, which will be described later, can be omitted.

[0047] First, an overview of the process will be explained. In the support information creation method, all inspection tables containing inspection results are read. The inspection tables are read in the form of electronic files. After reading, a facility key, which is an ID unique to xROAD, is generated based on the information contained in the inspection tables. The worker uses the facility key to search for the MICHI facility key of the target facility in xROAD. After the search, the worker inputs the management key and MICHI facility key. After completing this task for all inspection results, the ID / key / inspection table information integration unit integrates the inspection results, facility ID, MICHI facility key, and management key information, and outputs it as a CSV file for input into xROAD. Finally, the worker uses the output CSV file to register the inspection results. Each step will be explained in detail below.

[0048] (S1) All checklists are read by the support information creating device 1. S1 corresponds to a checklist information input step, which is a step of accepting input of checklist information by reading the checklist information, which is information contained in the checklist.

[0049] (S2) The system or application creates a facility ID from the latitude and longitude on the inspection sheet. S2 corresponds to a facility ID output step, which is a step of creating a facility ID for the road accessory from the latitude and longitude information on the road accessory written on the inspection sheet and outputting the created facility ID.

[0050] (S3) The worker manually inputs the administration key into a specified input form.

[0051] (S4) The worker searches for the Michi facility key using the facility ID in xROAD.

[0052] (S5) The worker inputs the Michi facility key into a specified input form.

[0053] Steps S3 to S5 correspond to the MICHI facility key / management key input step, which is a step for accepting input of a MICHI facility key for identifying road accessories and a management key for accessing the inspection information registration database.

[0054] (S6) Determine whether there are any inspection sheets remaining for which the Michi facility key has not been entered. If there are any inspection sheets remaining for which the Michi facility key has not been entered, the process returns to S4. If there are no inspection sheets remaining for which the Michi facility key has not been entered, the process proceeds to S7.

[0055] (S7) The support information creation device 1 integrates the facility ID, the MICHI facility key, the management key, and the checklist information, creates a format csv for xROAD registration, and outputs the csv for bulk registration. S7 corresponds to an ID / key / checklist information integration step, which is a step of integrating the facility ID, the MICHI facility key, the management key, and the checklist information, and creating a format csv for xROAD registration, and an input csv output step, which is a step of outputting the format csv for xROAD registration.

[0056] (S8) Enter the bulk registration CSV into xROAD to register in bulk.

[0057] This is the end of the processing flow of the support information generating method.

[0058] (Data flow) The process flow of the support information creating method will be described from the perspective of data with reference to Fig. 5. Fig. 5 is a diagram showing the process of the support information creating method from the perspective of data.

[0059] The internal database (DB) of the support information creation device 1 is provided with various data that form the basis of the xROAD registration format csv. This data includes data extracted from the electronic data of the inspection results, and data input by the worker 100. The electronic data of the inspection results includes a management number, latitude and longitude, photographs, rough sketches, diagrams, etc. The data input by the worker 100 is a MICHI facility key and a management key. In the processing of the support information creation method, these data are integrated, the data is formatted to match the format of the xROAD registration format csv, and output, thereby creating the xROAD registration format csv.

[0060] The data shown in Fig. 5 is only a portion of the data contained in the xROAD registration format csv. Fig. 7 shows more detailed data items than those in Fig. 5. However, Fig. 7 also shows only an excerpt of a portion of the data contained in the xROAD registration format csv. The data items contained in the xROAD registration format csv are determined by the items contained in the xROAD inspection information registration database.

[0061] (Hardware configuration) Each of the above-mentioned processes can also be executed by software (programs). Fig. 6 is a diagram showing an example of the hardware configuration of the support information creating device 1 when the processes are executed by software.

[0062] Each process and functional configuration of the support information creating device 1 may be realized by a personal computer (PC). In the example shown in Fig. 6, the support information creating device 1 includes a CPU 30, a memory 32, a storage device 34, a first interface, a second interface, an input unit 3, and an output unit 5. These are connected via a bus 40. In Fig. 6, the input unit 3 and the output unit 5 are drawn outside the frame of the support information creating device 1 to indicate input and output of data to and from the outside of the support information creating device 1.

[0063] Each process and functional configuration of the support information creation device 1 may be realized by a CPU 30 that executes arithmetic processing. Programs are stored in a storage device 34. The programs are expanded in a memory 32 so that the CPU 30 can execute them. Each process is realized by the CPU 30 executing each command included in the program.

[0064] A first interface 36 and a second interface 38 are connected to the bus 40. The input unit 3 is connected to the first interface 36. The output unit 5 is connected to the second interface 38.

[0065] Electronic data and information required for processing are input from the input unit 3 to the memory 32 via a first interface 36. The xROAD registration format csv created by the processing is output via a second interface 38.

[0066] (output item) FIG. 7 is a diagram showing an overview of the data contained in the xROAD registration format csv. Note that the output items shown in FIG. 7 are excerpts. Also, the input values ​​are examples. The xROAD registration format csv covers all the items required by the road data platform. And the xROAD registration format csv has a csv format that allows bulk registration to xROAD.

[0067] As described above, in the support information creation device, support information creation method, and support information creation program of this embodiment, an xROAD registration format CSV that allows bulk registration to xROAD is created based on the data contained in the checklist and supplementary data.

[0068] In detail, the support information creation device of the present embodiment enables efficient creation of a CSV file for xROAD bulk registration. An electronic file summarizing the inspection results of road accessories is read and registered inside the system. A facility ID is automatically generated from the latitude and longitude information contained in the read file, and the worker searches for a MICHI facility key based on the generated facility ID. After the search is completed, the worker inputs the MICHI facility key and management key, and registers it inside the system. After registration, the inspection result information of the read road accessories, the automatically generated facility ID, and the MICHI facility key and management key information entered by the worker are integrated, and a CSV file for xROAD bulk registration is created and output. The final output CSV is read using the bulk reading function of xROAD to complete the registration of the inspection results.

[0069] The support information creation device of this embodiment can reduce the labor required for input work, which took a huge amount of time in the conventional method. When registering point results manually, all inspection items had to be entered using a pull-down menu. In contrast, with the support information creation device of this embodiment, the only items that need to be entered by the worker are the MICHI facility key and the management key. This allows for a significant reduction in work time.

[0070] Furthermore, compared to the method of bulk registration using manual CSV creation, all inspection results can be converted into CSV files in one go, and xROAD's unique ID information, such as the facility ID, MICHI facility key, and management key, can be integrated to create the CSV files to be used for input, making it possible to create CSV files to be used for input more efficiently than with conventional methods.

[0071] The support information creating device 1 and the like described above can be modified in various ways. An example of a modified example will be described below. In the following description, the differences from the above description will be mainly described. Items that are not specifically described can be the same as those described above.

[0072] The support information creation device 1 described above is primarily intended to create a CSV file that facilitates the batch registration of information recorded on the checklist 50 to xROAD. In other words, the support information creation device 1 is intended to batch register text data to xROAD. In addition to text data, the support information creation device 1 can also include electronic data other than text data, such as image data, in a file for batch registration to xROAD.

[0073] The registration items of xROAD include image data in addition to items that can be shown by text data. Therefore, the support information creating device 1 may output image data for xROAD registration in addition to the CSV file for xROAD registration.

[0074] Examples of image data include a map showing the location where an object to be inspected (hereinafter referred to as an inspection object) is installed, and an image of the inspection object. Images of the inspection object may include still images and moving images. Images of the inspection object may also include various images, such as an image of the entire inspection object, an enlarged image of an abnormality, and an image of an area where the condition has changed since the previous inspection. Thus, the image data may be output in a format in which the image data is stored in folders organized into multiple hierarchical levels in accordance with the input items of xROAD, for example.

[0075] An example of image data output is shown in Fig. 8. Fig. 8 is a diagram showing the structure of xROAD registration data including image data. xROAD upload file 200 is a file for registering the contents of the inspection chart, etc., in xROAD. Note that "YYYYMMDDhhmmss" in xROAD upload file 200 indicates the year, month, day, hour, minute, and second.

[0076] The xROAD upload file 200 includes image data in addition to the csv data.

[0077] In Fig. 8, facility specifications.csv (211), damage record sheet.csv (212), and inspection result sheet.csv (213) are shown as examples of CSV data. These CSV data are examples. The types and number of CSV data included in the xROAD upload file 200 are not limited to the examples shown in Fig. 8. The types and number of CSV data shown as examples vary depending on the specific case.

[0078] The image data included in the xROAD upload file 200 is stored in an image data folder 221. An example of the data structure in the image data folder 221 is shown in a box 300 in FIG.

[0079] The image data folder 221 is organized into a plurality of hierarchical levels: a first hierarchical level 310, a second hierarchical level 320, and a third hierarchical level 330.

[0080] A folder is formed for each facility to be inspected and each inspection date in the first layer 310. In Fig. 8, three folders (folder 231 to folder 233) with different "(facility ID)_(inspection date)" are formed.

[0081] In the second layer 320, image data such as jpg files are stored in each folder in the first layer 310. In the example shown in Fig. 8, a folder 233 in the first layer 310 stores a jpg file 241 of a map and a jpg file 242 of facility specifications.

[0082] Folders may be formed in the second layer 320. In the example shown in Fig. 8, folders with consecutive numbers starting from 1 (folder 251 to folder 253) are formed as damage record folders. What folders are formed in what layers is not limited to the example shown in Fig. 8, and can be changed as appropriate according to the configuration of input items in xROAD, for example.

[0083] In the third layer 330, image data such as jpg files are stored for each consecutive folder formed in the second layer 320. In the example shown in Fig. 8, a jpg file 261 of a damage record sheet image is stored in the damage record sheet folder 253.

[0084] An xROAD upload file including image data, such as the xROAD upload file 200 shown in Fig. 8, can be created and output by the support information creation device 1. In the support information creation device 1 shown in Fig. 3, image data can be included in the checklist file 111 input to the input unit 3. Then, after processing by the processing unit 10, the output unit 5 can output an xROAD upload file including image data in addition to the bulk registration CSV file.

[0085] When image data is included in an upload file for xROAD, for example, when an image of an object to be inspected is captured, the following can be done. When the image data is organized and stored in an upload file for xROAD, information that can be referenced is recorded in association with the image data. For example, information that contributes to the classification or selection of image files is recorded, such as the facility ID of the object to be inspected, the type of image (such as a full image, an enlarged image, or a map), and the purpose of capturing an enlarged image (such as a damage record image or a periodic record image). This information may be input by the photographer into the imaging terminal when capturing an image, or selected from a selection screen of the imaging terminal. Also, the imaging terminal may display a message requesting the photographer to input the information.

[0086] When organizing and storing captured images in an upload file for xROAD, for example, a trained AI model can be used. By using an AI model, it becomes possible to organize image data more quickly and store it in an upload file for xROAD by referring to the contents of the image in addition to text data such as the date and time of capture recorded with the image data. In addition, an AI model can be generated by having it learn images that have already been uploaded to xROAD and the items of the upload destination.

[0087] Also, the data structure in the image data folder 221 shown in the box 300 in Fig. 8 can be created using an AI model. For example, the xROAD database is input to the AI ​​model. The AI ​​model extracts items that use images as input data from the database. Then, based on the extraction results, the data structure in the image data folder 221 in the xROAD upload file is determined. [Explanation of symbols]

[0088] 1 Support information creation device 3. Input section 5 Output section 10 Processing section 12 Facility ID Creation Department 14 Extraction part 16 Integration Department 18 ID / Key / Checklist Information Integration Unit, Second Integration Unit 50 Checklist 51 Appendix A Checklist 52 Appendix B Checklist 53 Appendix C Checklist 60 xROAD registration format csv 100 workers 301 Checklist information input section 302 Facility ID output section 303 MICHI Facility Key Management Key Entry Unit 501 Input csv output section

Claims

1. A support information creation device that creates xROAD registration format data for registering inspection results recorded in an inspection list for road accessories in an inspection information registration database, comprising: an inspection table information input unit that accepts input of the inspection table information by reading the inspection table information that is information included in the inspection table; a facility ID output unit that generates a facility ID for the road accessory from the latitude and longitude information of the road accessory described in the inspection table and outputs the generated facility ID; a MICHI facility key / management key input unit for receiving an input of a MICHI facility key for identifying the road accessory and a management key for accessing the inspection information registration database; an ID / key / checklist information integration unit that integrates the facility ID, the MICHI facility key, the management key, and the checklist information to create the xROAD registration format data; An input data output unit that outputs the xROAD registration format data, Support information creation device.

2. The checklist information input unit can read a plurality of the checklists, The ID / key / checklist information integration unit creates the xROAD registration format data for each of the plurality of checklists, or creates the xROAD registration format data integrating each of the plurality of checklists, 2. The support information creating device according to claim 1.

3. The MICHI facility key is A key for identifying the road accessory registered in the inspection information registration database, or A key for identifying the road accessory that is not registered in the inspection information registration database and is to be newly registered in the inspection information registration database.

3. The support information creating device according to claim 1 or 2.

4. the checklist information includes image data; The xROAD registration format data includes an image data folder in which at least a portion of the image data is stored.

3. The support information creating device according to claim 1 or 2.

5. A method executed by a support information creation device for creating xROAD registration format data for registering inspection results recorded in an inspection list for road accessories in an inspection information registration database, comprising: an inspection table information input step of accepting input of the inspection table information by reading the inspection table information that is information included in the inspection table; a facility ID output step of generating a facility ID of the road accessory from the latitude and longitude information of the road accessory recorded on the inspection sheet and outputting the generated facility ID; a MICHI facility key / management key input step of receiving an input of a MICHI facility key for identifying the road accessory and a management key for accessing the inspection information registration database; an ID / key / checklist information integration step of integrating the facility ID, the MICHI facility key, the management key, and the checklist information to generate the xROAD registration format data; An input data output step of outputting the xROAD registration format data, How to create support information.

6. the checklist information includes image data; The xROAD registration format data includes an image data folder in which at least a portion of the image data is stored. The support information generating method according to claim 5.

7. a support information creation device for creating xROAD registration format data for registering inspection results recorded in an inspection sheet for road accessories in an inspection information registration database; an inspection table information input unit that accepts input of the inspection table information by reading the inspection table information that is information included in the inspection table; a facility ID output unit that generates a facility ID for the road accessory from the latitude and longitude information of the road accessory described in the inspection table and outputs the generated facility ID; a MICHI facility key / management key input unit for receiving an input of a MICHI facility key for identifying the road accessory and a management key for accessing the inspection information registration database; an ID / key / checklist information integration unit that integrates the facility ID, the MICHI facility key, the management key, and the checklist information to create the xROAD registration format data; The input data output unit outputs the xROAD registration format data. Support information creation program.

8. the checklist information includes image data; The xROAD registration format data includes an image data folder in which at least a portion of the image data is stored. The support information generating program according to claim 7.

Images