JP2020123332A - System and method for managing history of setting boundary point, program, data structure of boundary point setting data - Google Patents

Abstract

To provide a system and a method for managing the history of setting a boundary point, a program, and the data structure of boundary point setting data which allow a user to know the position and the reliability of a boundary point in a unified manner shown in a plurality of maps or drawings.SOLUTION: A boundary point setting data generation unit 34 generates boundary point setting data including positional data which shows the position of a boundary point shown in a map or in a drawing and intensity data which shows the level of the reliability of the position related to the type of the map or the drawing. The boundary point setting data generation unit 34 causes newly generated boundary point setting data to be stored in a boundary point setting data storage unit 28 in relation to boundary point setting data including the positional data showing the position of the boundary point shown in another map or drawing and intensity data related to the map or the drawing stored in the boundary point setting data storage unit 28 in advance.SELECTED DRAWING: Figure 2

Description

The present invention relates to a boundary point setting history management system, a boundary point setting history management method, a program, and a data structure of boundary point setting data, and more particularly to a system compatible with block chain technology.

Patent Document 1 describes a real estate information display system that displays a map in a display range determined by a user's operation on a screen.

JP, 2005-13812, A

There are various maps or drawings that describe the situation on a land. For example, there are geological survey maps, real estate registration method Article 14 maps, quasi-maps (public maps), etc. that are available from the registry office. In addition, there are lot number maps created by the Ministry of Land, Infrastructure, Transport and Tourism, local governments, etc. for grasping lot numbers, shapes, and neighboring relationships.

In some of these maps or drawings, the position shown as the position of the boundary point of the land is not the position based on the boundary mark, and the credibility of the position of the boundary point shown in such map or drawing Is low. Therefore, even if it is shown as the same boundary point in various maps or drawings, the position shown as the position of the boundary point and its credibility are not the same.

Here, even if the technique described in Patent Document 1 is used, the position of a certain boundary point and the high credibility thereof, which are shown in a plurality of maps or drawings, cannot be grasped in a unified manner. Therefore, for example, for a boundary point shown in a certain map or drawing, even if there is another map or drawing with a higher credibility of the position, the user could not easily grasp that. ..

The present invention has been made in view of the above circumstances, and one of its objects is that the user unifies the position of a certain boundary point and the high credibility thereof, which are shown in a plurality of maps or drawings. It is to provide a boundary point setting history management system, a boundary point setting history management method, a program, and a data structure of boundary point setting data that can be grasped in detail.

In order to solve the above-mentioned problems, the boundary point setting history management system according to the present invention, position data indicating the position of the boundary point, and the position corresponding to the type of map or drawing in which the boundary point is shown, the position Boundary point setting data storage means for storing boundary point setting data including strength data indicating a high level of credibility, and the position of the boundary point shown on a map or drawing different from the map or drawing. Boundary position setting data generation means for generating the new boundary point setting data including the new position data indicating the new position data and the new intensity data associated with the different map or drawing type. A storage unit that stores the new boundary point setting data in the boundary point setting data storage unit in association with the boundary point setting data already stored in the boundary point setting data storage unit.

In one aspect of the present invention, the method further includes map data acquisition means for acquiring map data indicating a map or drawing associated with a registration application of a predetermined type, wherein the boundary point setting data generation means converts the map data into the map data. The new boundary point setting data including the new position data indicating the position of the boundary point shown and the new intensity data associated with the type of the map data is generated.

Moreover, in one aspect of the present invention, the plurality of boundary point setting data are data managed by a block chain.

Further, in one aspect of the present invention, the boundary point setting data storage means stores the boundary point setting data for a plurality of different boundary points, and polygon data representing a polygon including the plurality of boundary points as vertices. Map image generating means for generating a map image based on the above, and at least two vertices included in the polygon are different from each other in the map or drawing in which the vertices are shown as the boundary points.

In this aspect, an updating unit that updates the polygon data that represents a polygon including the boundary point whose position is indicated in the boundary point setting data as an apex according to the generation of the new boundary point setting data, It may further include.

Further, the boundary point setting history management method according to the present invention has a high reliability of the position, which is associated with the position data indicating the position of the boundary point shown on the map or drawing and the type of the map or drawing. A step of generating boundary point setting data including strength data indicating the height, and the new generated boundary point setting data, which is already stored in the boundary point setting data storage means, with the map or drawing. Is associated with the boundary point setting data including the position data indicating the position of the boundary point shown in another map or drawing, and the intensity data associated with the type of the different map or drawing. And storing in the boundary point setting data storage means.

Further, the program according to the present invention is position data indicating the position of the boundary point shown on the map or drawing, and strength data indicating the high credibility of the position, which is associated with the type of the map or drawing. A procedure for generating boundary point setting data including the following, and the new generated boundary point setting data, which is already stored in the boundary point setting data storage means, is a map or drawing different from the map or drawing. In association with the boundary point setting data including the position data indicating the position of the boundary point shown in, and the intensity data associated with the type of another map or drawing, the boundary point setting data The computer is caused to execute the procedure of storing in the storage means.

Further, the data structure of the boundary point setting data according to the present invention is the position data indicating the position of the boundary point shown in the map or the drawing, and the reliability of the position associated with the type of the map or the drawing. And intensity data indicating the height.

It is a figure which shows an example of the whole structure of the computer network which concerns on one Embodiment of this invention. It is a functional block diagram which shows an example of the function mounted in the server which concerns on one Embodiment of this invention. It is a figure which shows an example of registration application information data. It is a figure which shows an example of boundary point setting data. It is a figure which shows an example of boundary point setting data. It is a figure which shows an example of data corresponding to map type intensity. It is a figure which shows an example of polygon data. It is a figure which shows an example of a lot number map image. It is a flow figure showing an example of a flow of processing performed in a server concerning one embodiment of the present invention.

An embodiment of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a diagram showing an example of the overall configuration of a computer network according to an embodiment of the present invention. As shown in FIG. 1, a computer network 18 such as the Internet is connected to a server 10, a terminal 12, a registration application information data providing system 14, and a registration information providing service 16 each of which is mainly composed of a computer.

As shown in FIG. 1, the server 10 includes a processor 10a, a storage unit 10b, a communication unit 10c, an output unit 10d, and an input unit 10e.

The processor 10a is a program control device such as a CPU, and executes various types of information processing according to a program stored in the storage unit 10b.

The storage unit 10b is, for example, a storage element such as a ROM or RAM, a hard disk drive, or the like. The storage unit 10b stores programs executed by the processor 10a.

The communication unit 10c is a communication interface for exchanging data with the terminal 12, the registration application information data providing system 14, and the registration information providing service 16 via the computer network 18, for example. The server 10 transmits/receives information to/from the terminal 12, the registration application information data providing system 14, and the registration information providing service 16 via the communication unit 10c.

The output unit 10d is, for example, a display unit such as a display that outputs information according to an instruction input from the processor 10a, a voice output unit such as a speaker that outputs voice, a print output unit such as a printer, or the like.

The input unit 10e is, for example, a game controller, a touch pad, a mouse, a keyboard, a microphone, or the like that outputs the content of the operation performed by the user to the processor 10a.

As shown in FIG. 1, the terminal 12 includes a processor 12a, a storage unit 12b, a communication unit 12c, an output unit 12d, and an input unit 12e.

The processor 12a is, for example, a program control device such as a CPU, and executes various types of information processing according to a program stored in the storage unit 12b.

The storage unit 12b is, for example, a storage element such as a ROM or RAM, a hard disk drive, or the like. The storage unit 12b stores programs executed by the processor 12a and the like.

The communication unit 12c is a communication interface for exchanging data with the server 10, the registration application information data providing system 14, and the registration information providing service 16 via the computer network 18, for example. The terminal 12 transmits and receives information to and from the server 10, the registration application information data providing system 14, and the registration information providing service 16 via the communication unit 12c.

The output unit 12d is, for example, a display unit such as a display for displaying and outputting information in accordance with an instruction input from the processor 12a, a voice output unit such as a speaker for outputting voice, a print output unit such as a printer, or the like.

The input unit 12e is, for example, a game controller, a touch pad, a mouse, a keyboard, a microphone or the like that outputs the content of the operation performed by the user to the processor 12a.

The registration application information data providing system 14 is, for example, a computer system in which registration application information corresponding to the description content of the real estate registration reception book managed by the Legal Affairs Bureau is registered as data. The registration application information data providing system 14 provides the requested registration application information data to the computer system in response to a request from the computer system such as the server 10.

The registration information providing service 16 is a computer system that provides a registration information providing service by, for example, the General Foundation Law People's Legal Association. The registration information providing service 16 provides registration information such as all requested real estate registration items to the computer system in response to a request from the computer system such as the server 10.

There are various maps or drawings that describe the situation on a land. For example, there are geological survey maps, real estate registration method Article 14 maps, quasi-maps (public maps), etc. that are available from the registry office. In addition, there are lot number maps created by the Ministry of Land, Infrastructure, Transport and Tourism, local governments, etc. for grasping lot numbers, shapes, and neighboring relationships.

In some of these maps or drawings, the position shown as the position of the boundary point of the land is not the position based on the boundary mark, and the credibility of the position of the boundary point shown in such map or drawing Is low. Therefore, even if it is shown as the same boundary point in various maps or drawings, the position shown as the position of the boundary point and its credibility are not the same.

Based on the above points, in the present embodiment, the user can uniformly understand the positions of the boundary points represented by various maps and drawings and the high credibility thereof in the following manner.

FIG. 2 is a functional block diagram showing an example of functions implemented in the server 10 according to this embodiment. It should be noted that the server 10 according to the present embodiment does not need to have all the functions shown in FIG. 2 installed, and may have functions other than the functions shown in FIG.

As shown in FIG. 2, the server 10 according to the present embodiment functionally has, for example, a registration information storage unit 20, a registration application information data storage unit 22, a registration application information data request unit 24, and a registration application information data acquisition unit. Unit 26, boundary point setting data storage unit 28, map type strength correspondence data storage unit 30, polygon data storage unit 32, boundary point setting data generation unit 34, polygon data management unit 36, lot number map image generation unit 38, request reception unit. 40 and a data transmission unit 42 are included.

The registration information storage unit 20, the registration application information data storage unit 22, the boundary point setting data storage unit 28, the map type strength correspondence data storage unit 30, and the polygon data storage unit 32 are implemented mainly by the storage unit 10b. The registration application information data request unit 24, the registration application information data acquisition unit 26, the request reception unit 40, and the data transmission unit 42 are implemented mainly by the communication unit 10c. The boundary point setting data generation unit 34, the polygon data management unit 36, and the lot number map image generation unit 38 are implemented mainly by the processor 10a.

The above functions may be implemented by causing the processor 10a to execute a program that is installed in the server 10 that is a computer and that includes a command corresponding to the above functions. This program may be supplied to the server 10 via a computer-readable information storage medium such as an optical disc, a magnetic disc, a magnetic tape, a magneto-optical disc, a flash memory, or the like, or via the Internet or the like.

In the present embodiment, the registration information storage unit 20 stores, for example, registration information provided by the registration information providing service 16.

In the present embodiment, the registration application information data storage unit 22 stores, for example, the registration application information data illustrated in FIG.

The registration application information data is data associated with one real estate registration application. The registration application information data according to the present embodiment includes reception date data, reception number, property identification data, registration purpose data, and real estate type data.

The acceptance date data is data indicating the acceptance date of the registration application that is associated with the registration application information data, for example. The reception number is, for example, a number set according to the registration application reception order associated with the registration application information data. The property identification data is, for example, data for identifying a real estate subject to registration application that is associated with the registration application information data. The property identification data includes prefecture name data, city/ward name data, large name town name data, character name chome data, lot number house number data. Prefectural name data, municipality name data, large-scale name town name data, character name chome data, lot number house number data are the prefecture name, municipality name, large-scale name or town name of the real estate subject to registration application , Character name or chome, lot number or house number. The registration purpose data is data indicating the purpose of the registration application associated with the registration application information data. The purpose of the registration application shown in the registration purpose data corresponds to the reason for registration shown in the title section of the registration information associated with the registration application information data.

The registration application information data request unit 24 requests the registration application information data in this embodiment, for example. The registration application information data requesting unit 24 transmits, for example, a registration application information data transmission request to the registration application information data providing system 14.

Then, the registration application information data providing system 14 specifies one or more registration application information data to be transmitted in response to the reception of the transmission request. Then, the registration application information data providing system 14 transmits the specified registration application information data to the server 10.

The registration application information data acquisition unit 26 acquires the registration application information data in the present embodiment, for example. The registration application information data acquisition unit 26 receives the registration application information data transmitted from the registration application information data providing system 14, and stores the registration application information data in the registration application information data storage unit 22, for example.

Here, for example, the registration application information data requesting unit 24 may repeatedly transmit a transmission request for newly registered registration application information data. Then, the registration application information data providing system 14 may transmit the registration application information data newly registered after the previous transmission to the server 10 in response to the reception of the transmission request. Then, the registration application information data acquisition unit 26 may receive the registration application information data and store the registration application information data in the registration application information data storage unit 22. The registration application information data may be acquired at predetermined time intervals such as one day intervals.

In addition, when applying for real estate registration, a map or drawing related to the real estate registration application may be submitted. The registration application information data providing system 14 according to the present embodiment transmits the map data showing the map or drawing submitted in this manner to the server 10 in association with the registration application information data corresponding to the real estate registration application. Then, the map data is stored in the registration application information data storage unit 22 in a state of being associated with the registration application information data.

The map data according to the present embodiment includes map type data indicating the type of map or drawing represented by the map data, and creation date data indicating the creation date of the map data.

For example, the registration application information data whose registration purpose data has the value "separation" or "relocation of land" includes the map type data whose value is "geographic survey map". The map data of the survey map is associated. In addition, for example, the registration application information data in which the value of the registration purpose data is “Title” and the value of the real estate type data is “land” includes the map type data whose value is “Area survey map”. The map data of the geological survey map created with the registration application is associated. Further, for example, the registration application information data in which the value of the registration purpose data is “land improvement/land readjustment” includes map type data in which the value is “land readjustment drawing” was created in association with the registration application. Map data of the land readjustment plan is associated.

In addition, in the present embodiment, the registration application information data storage unit 22 includes, in addition to the map data of the land area survey map and the land readjustment plan, for example, the land area map, the article 14 map, the base map, the quasi-map (public map), Map data such as a lot number map is stored.

The map data according to this embodiment is digitized. Therefore, based on the map data, it becomes possible to specify the position of the polygon associated with the land section shown in the map data and the position of the apex included in the polygon (for example, latitude and longitude). There is.

In the present embodiment, for example, the boundary point setting data storage unit 28 has high reliability of the position, which is associated with position data indicating the position of the boundary point and the type of map or drawing in which the boundary point is indicated. Boundary point setting data including the strength data indicating the height is stored. The position of the boundary point indicated by the boundary point setting data may indicate the position of the installed boundary mark, or may indicate the position of the boundary point on which the boundary mark is not installed. Further, in the present embodiment, the boundary point setting data storage unit 28 stores boundary point setting data for a plurality of different boundary points.

4A and 4B are diagrams illustrating an example of boundary point setting data. As shown in FIGS. 4A and 4B, the boundary point setting data includes, for example, a boundary point ID, a setting sequence number, position data, setting timing data, corresponding map type data, and intensity data.

A boundary point may appear on multiple maps or drawings. And the position of the said boundary point shown in each map or drawing may differ. For example, if a geological survey map with the installation of boundary markers is created for a boundary point represented on a quasi-map (public map), the position of the boundary point will be categorized on the quasi-map It will be represented more accurately than (public chart). In this embodiment, the history of the positions of the boundary points appearing in various maps or drawings can be managed by the boundary point setting data by performing the setting a plurality of times in this way.

The boundary point ID included in the boundary point setting data is, for example, identification information of the boundary point associated with the boundary point setting data. In the present embodiment, for one boundary point, the boundary point setting data in which the common boundary point ID corresponding to the boundary point is set by the number of times corresponding to the number of times the boundary point is set is the boundary point setting data. It is stored in the data storage unit 28.

The setting order number included in the boundary point setting data is, for example, a number indicating the order in which the boundary points associated with the boundary point setting data are set. For example, for the boundary points corresponding to a certain boundary point ID, the setting sequence number of the boundary point setting data including the boundary point ID is set in order from the oldest creation date of the map showing the boundary point. ..

In the present embodiment, the position data included in the boundary point setting data associated with the boundary point is, for example, data indicating the position of the boundary point shown in the map or the drawing associated with the boundary point setting data. .. In the example of FIGS. 4A and 4B, the position is represented by the latitude and the longitude, but the position of the boundary point may be represented by other than the latitude and the longitude.

In the present embodiment, the setting timing data included in the boundary point setting data is, for example, data indicating the setting timing of the boundary point associated with the boundary setting data. The setting timing data may indicate, for example, the creation date of the map or drawing in which the boundary point is represented. In addition, when a map or drawing is created in association with real estate registration, the setting timing data included in the boundary point setting data of the boundary point shown on the map indicates the date when the real estate registration was performed. It may be shown.

In the present embodiment, the corresponding map type data included in the boundary point setting data is, for example, data indicating the type of map or drawing associated with the boundary point setting data.

In the present embodiment, the intensity data included in the boundary point setting data is, for example, data indicating the degree of credibility of the position of the boundary point indicated by the position data included in the boundary point setting data. In the present embodiment, for example, in the map type strength correspondence data shown in FIG. 5, the type of map or drawing is associated with the high credibility of the position of the boundary point. Then, in the present embodiment, the value of the intensity data is determined based on the map type intensity correspondence data. In this embodiment, for example, the value of intensity data associated with a map or drawing is set to a larger value as the credibility of the position of the boundary point shown in the map or drawing is higher.

In the present embodiment, the map type strength correspondence data storage unit 30 stores the map type strength correspondence data illustrated in FIG. 5, for example.

As shown in FIG. 5, the map type strength correspondence data includes map type data indicating a map type and strength data associated with a map of the type.

The boundary point setting data shown in FIGS. 4A and 4B shows a history of setting the boundary points for the same boundary point having the boundary point ID 111.

In the position data included in the boundary point setting data shown in FIG. 4A, the position of the boundary point shown in the sectioned drawing which is the map or the drawing in which the boundary point having the boundary point ID 111 appears for the third time is shown. It is shown. The value of the setting timing data included in the boundary point setting data shown in FIG. 4A is set to April 6, 1996, which is the creation date of the relevant section control drawing.

Assume that a land area survey map was created on April 2, 2019 for the land represented in the land readjustment plan. Along with this, the boundary point setting data shown in FIG. 4B is newly registered in the boundary point setting data storage unit 28. Since the geological survey map is the map or drawing in which the boundary point having the boundary point ID 111 is the fourth time, the setting sequence number included in the boundary point setting data shown in FIG. 4B is set to 4. Then, as the value of the position data included in the boundary point setting data shown in FIG. 4B, a value indicating the position of the boundary point shown in the geological survey map is set.

In this way, according to this embodiment, it is possible to manage the history in which the boundary points are set.

In the boundary point setting data shown in FIG. 4A, in the map type strength corresponding data shown in FIG. 5, “2.5” is associated with the value “section adjustment drawing” of the corresponding map type data included in the boundary point setting data. Is set to the value of the intensity data. In the boundary point setting data shown in FIG. 4B, in the map type strength correspondence data shown in FIG. 5, “3.0” is associated with the value “geographical survey map” of the corresponding map type data included in the boundary point setting data. Is set to the value of the intensity data.

It is desirable that the administrator of the server 10 preset the map type strength corresponding data such that the higher the credibility of the map or the drawing, the larger the value of the strength data. By doing so, the user can easily compare the credibility with respect to each of the positions of the boundary points set a plurality of times by referring to the value of the intensity data.

In the example of the map type strength correspondence data shown in FIG. 5, the value of the strength data associated with the land area survey map is determined because the land owner's strong sense of writing boundary is confirmed when creating the land volume survey map. It is the largest "3.0".

In addition, when creating a land readjustment plan, a writing field is created to match the local survey results with the plots drawn on the desk.Therefore, the strength data value associated with the land readjustment plan is It is a big "2.5".

In addition, since the landowner is present in creating the cadastral map, the value of the intensity data associated with the cadastral map is “2.0”, which is the next largest value after the land readjustment drawing.

In addition, since the Article 14 map has local resilience, the value of the intensity data associated with the Article 14 map is “2.0”, which is the same as the cadastral map.

In addition, the drawings are prepared by experts based on a certain basis on the assumption that the landowner is present, and although they can be browsed, the grounds of the writing world are insufficient. From this, the value of the intensity data associated with the map is “1.0”, which is the next largest value after the cadastral map and the Article 14 map.

Since the accuracy of the quasi-map (public map) and the lot number map varies, the value of the intensity data associated with the quasi-map (public map) and the lot number map is the smallest "0.0".

The value of the intensity data shown in FIG. 5 is merely an example, and a value different from the value shown in FIG. 5 may be set as the value of the intensity data.

In the present embodiment, the boundary point setting data generation unit 34 has, for example, position data indicating the position of a boundary point shown on a map or drawing, and high reliability of the position associated with the type of the map or drawing. And new boundary point setting data including the strength data indicating the height. Then, the boundary point setting data generation unit 34 stores the new generated boundary point setting data in the boundary point setting data storage unit 28.

At this time, the new boundary point setting data is the same as the boundary point indicated by the new boundary point setting data already stored in the boundary point setting data storage unit 28. It is stored in association with the boundary point setting data associated with another map or drawing. For example, as the value of the boundary point ID of the new boundary point setting data, the boundary point indicating the same boundary point as the boundary point indicated by the new boundary point setting data, which is already stored in the boundary point setting data storage unit 28. The value of the boundary point ID of the setting data is set.

Here, the boundary point setting data generation unit 34 may acquire map data indicating a map or a drawing in which the positions of the boundary points are shown. The boundary point setting data generation unit 34 may acquire the map data stored in the registration application information data storage unit 22, for example. Further, here, the boundary point setting data generation unit 34 may acquire the map data associated with the registration application of a predetermined type.

Then, the boundary point setting data generation unit 34 calculates the position data indicating the position of the boundary point shown in the map data acquired as described above and the strength data associated with the type of the map data. New boundary point setting data including may be generated. The boundary points correspond to, for example, the vertices included in the polygons associated with the land sections shown in the map data.

Further, for example, when new registration application information data is stored in the registration application information data storage unit 22, the boundary point setting data generation unit 34 may confirm the value of the registration application information data. Then, when the value of the registration application information data is a predetermined value, the boundary point setting data generation unit 34 may acquire the map data associated with the registration application information data.

For example, if the value of the registration purpose data included in the newly stored registration application information data is “separation stroke” or “reclaimed land area”, a map of the geological survey map stored in association with the registration application information data. Data may be acquired.

In addition, for example, when the value of the registration purpose data included in the newly stored registration application information data is “title” and the value of the real estate type data is “land”, the registration application information data is associated with the registration application information data. Map data of the stored geological survey map may be acquired.

In addition, for example, when the value of the registration purpose data included in the newly stored registration application information data is “land improvement/land readjustment”, the land readjustment plan stored in association with the registration application information data is stored. Map data may be acquired.

Then, the boundary point setting data generation unit 34 sets new position data indicating the position of the boundary point shown in the map data thus obtained, and new strength data associated with the type of the map data. New boundary point setting data including and may be generated. In the position data included in the boundary point setting data, a value indicating the position of the apex included in the polygon associated with the land section shown in the map data is set.

In the present embodiment, the polygon data storage unit 32 stores, for example, the polygon data illustrated in FIG.

The polygon data according to the present embodiment is data representing a polygon including a plurality of boundary points whose positions are respectively shown in a plurality of boundary point setting data as vertices. The polygon data is associated with the polygon of the parcel of land. As shown in FIG. 6, the polygon data according to the present embodiment includes, for example, a polygon ID, property identification data, and boundary point ID group data.

The polygon ID included in the polygon data is, for example, identification information of the polygon associated with the polygon data.

The property specifying data included in the polygon data is, for example, data for specifying a real estate such as land represented by the polygon associated with the polygon data. The property specifying data included in the polygon data corresponds to the property specifying data included in the registration application information data shown in FIG. The property specifying data included in the property specifying data of the polygon data includes the prefecture name, city name, city name, city name, town name, city name, city name, street name or house number of the real estate represented by the polygon associated with the polygon data. Is shown.

The boundary point ID group data included in the polygon data is, for example, data indicating the ordered array of the boundary point IDs described above. The polygon data according to this embodiment is associated with polygons whose vertices are points associated with a plurality of boundary point IDs included in the boundary point ID group data.

As described above, a plurality of boundary point setting data including the common boundary point ID may be stored in the boundary point setting data storage unit 28. In order to identify the one indicating the position of the vertex of the polygon from the plurality of boundary point setting data, the boundary point ID group data shown in FIG. 6 shows the setting sequence number in parentheses following the boundary point ID. Has been done.

For example, the position of the first vertex included in the polygon associated with the polygon data shown in FIG. 6 is indicated by the position data included in the boundary point setting data having the boundary point ID 111 and the setting sequence number 4. The position. The position of the second vertex is the position indicated by the position data included in the boundary point setting data having the boundary point ID 112 and the setting order number 3. The position of the third vertex is the position indicated by the position data included in the boundary point setting data having the boundary point ID 113 and the setting sequence number 3. The position of the fourth vertex is the position indicated by the position data included in the boundary point setting data having the boundary point ID 114 and the setting sequence number 5.

In the present embodiment, the polygon data management unit 36 executes, for example, generation, updating, and deletion of polygon data. The polygon data management unit 36 may generate polygon data in response to a user operation, for example.

Here, the polygon data management unit 36 may receive the designation of the boundary point ID set in the boundary point ID group data from the user. Then, the polygon data management unit 36 may specify a plurality of boundary point setting data including the boundary point ID. Specifically, for example, when 111 is specified as the boundary point ID, a plurality of boundary point setting data whose boundary point ID is 111 may be specified. Then, from among these boundary point setting data, the setting sequence number of the one having the largest value of the set strength data may be specified. Here, for example, it is assumed that the intensity data value of the boundary point setting data having the setting order number 4 is the largest.

In this case, the boundary point ID specified by the user and the specified setting sequence number may be set in the boundary point ID group data. In this case, for example, 111(4) may be set as the value of the boundary point ID group data. By doing the above, polygon data representing a polygon including a vertex with high credibility is generated.

Further, in this embodiment, at least two vertices included in the polygon represented by the polygon data may be different from each other in maps or drawings in which the vertices are shown as boundary points. By doing so, the polygon data according to the present embodiment makes it possible to represent a polygon in which vertices respectively appearing in a plurality of different maps or drawings are mixed.

In the present embodiment, the lot number map image generation unit 38 generates a map image such as the lot number map image illustrated in FIG. 7 based on the polygon data and the boundary point setting data, for example. The lot number map image shows the correspondence between the lot number and the land division. For example, a quadrilateral polygon whose lot number is shown as 7-3 in FIG. 7 is a polygon corresponding to the polygon data shown in FIG.

In the present embodiment, the request receiving unit 40 receives a request from the user of the terminal 12, for example.

In the present embodiment, the data transmission unit 42 transmits, for example, data corresponding to the request accepted by the request acceptance unit 40 to the terminal 12.

Here, for example, it is assumed that the request receiving unit 40 receives the designation of the place by the user of the terminal 12 (for example, designation of latitude and longitude, address, lot number, etc.). In this case, the lot number map image generation unit 38 may generate the lot number map image of the designated place. Then, the data transmission unit 42 may transmit the generated lot number map image to the terminal 12. Then, the terminal number map image transmitted by the terminal 12 may be displayed on the display.

Further, for example, it is assumed that the request receiving unit 40 receives a transmission request for registration information associated with the lot number shown in the lot number map image. In this case, the data transmission unit 42 may transmit the registration information of the lot number to the terminal 12.

Further, it is assumed that the request receiving unit 40 receives the designation of the vertices included in the polygon shown in the lot number map image. In this case, the data transmission unit 42 may transmit a plurality of boundary point setting data indicating the setting history of the boundary points corresponding to the specified vertex to the terminal 12. Further, the data transmission unit 42 may transmit map data indicating a map or a drawing associated with each of the plurality of boundary point setting data to the terminal 12. Then, the value of the boundary point setting data and the map or drawing indicated by the map data may be displayed on the terminal 12.

As described above, the user of the terminal 12 can integrally understand the position of the boundary point represented by various maps and drawings and the high credibility thereof. In addition, the user of the terminal 12 can collectively obtain a plurality of maps or drawings in which the specified boundary points are represented. Further, the user can obtain the information on the position of the boundary point, which is more credible than the information on the position of the boundary point which the user grasps.

Further, according to the present embodiment, it is possible to provide the user of the terminal 12 with a lot number map image composed of boundary points having a high position credibility in which boundary points represented by a plurality of maps or drawings are mixed. Becomes

Hereinafter, an example of the flow of processing performed in the server 10 according to the present embodiment will be described with reference to the flowchart illustrated in FIG.

First, the boundary point setting data generation unit 34 monitors that a predetermined type of registration application information data is stored in the registration application information data storage unit 22 (S101). Here, for example, it may be monitored that the registration application information data in which the value of the registration purpose data is “Distribution”, “Land rehabilitation”, or “Land improvement/land readjustment” is stored. Further, for example, it may be monitored that the registration application information data in which the value of the registration purpose data is “title” and the value of the real estate type data is “land” is stored.

Here, when it is detected that the registration application information data of a predetermined type is stored in the registration application information data storage unit 22, the boundary point setting data generation unit 34 causes the map associated with the registration application information data. Data is acquired (S102).

Then, the boundary point setting data generation unit 34 specifies the positions of the plurality of boundary points shown in the map data acquired in the process of S102 (S103).

Then, the boundary point setting data generation unit 34 selects one of the plurality of boundary points whose position is specified by the processing shown in S103 (S104). Hereinafter, the position of the boundary point will be referred to as a target position.

Then, the boundary point setting data generation unit 34 generates boundary point setting data corresponding to the boundary point selected in the process of S104. Then, the boundary point setting data generation unit 34 stores the generated boundary point setting data in the boundary point setting data storage unit 28 (S105).

In the processing shown in S105, for example, the boundary point setting data generation unit 34 may specify boundary point setting data including position data indicating a position within a predetermined distance from the position of interest. Then, the boundary point setting data generation unit 34 may generate new boundary point setting data including the same boundary point ID as the boundary point ID of the specified boundary point setting data. In this case, the setting sequence number of the generated boundary point setting data is set to the number next to the maximum setting sequence number in the boundary point setting data including the boundary point ID.

Here, when there is no boundary point setting data including position data indicating a position within a predetermined distance from the position of interest, the boundary point setting data generation unit 34 sets a new boundary point setting including a new boundary point ID. Data may be generated. In this case, 1 is set to the setting sequence number of the generated boundary point setting data.

For example, a position of interest is set as the value of the position data of the boundary point setting data generated in the process shown in S105. Further, the value of the setting timing data of the boundary point setting data generated by the process of S105 is set to the value of the creation date data included in the map data acquired by the process of S102, for example. Further, as the value of the corresponding map type data of the boundary point setting data generated in the process of S105, for example, the value of the map type data included in the map data acquired in the process of S102 is set. Further, the value of the intensity data of the boundary point setting data generated in the process of S105 is set to the value of the intensity data associated with the value of the map type data in the map type intensity correspondence data, for example. ..

Then, the boundary point setting data generation unit 34 confirms whether or not the processing shown in S104 and S105 has been executed for all the boundary points whose positions have been specified in the processing shown in S103 (S106).

If the processes of S104 and S105 have not been executed for all boundary points (S106:N), the process returns to S104.

When the processing shown in S104 and S105 has been executed for all boundary points (S106:Y), the processing shown in this processing example is ended.

In this processing example, the polygon data management unit 36 updates polygon data representing a polygon including a boundary point whose position is indicated in the boundary point setting data as a vertex in response to the generation of new boundary point setting data. May be.

For example, the polygon data management unit 36 stores new boundary point setting data stored in the boundary point setting data storage unit 28 and at least one boundary point setting data having the same boundary point ID as the new boundary point setting data. May be specified. Then, the polygon data management unit 36 may specify, from the plurality of boundary point setting data, the one having the highest credibility indicated by the intensity data. Then, the polygon data management unit 36 may specify the setting order number of the specified boundary point setting data. Then, the polygon data management unit 36 may specify the polygon data including the boundary point ID of the new boundary point setting data in the value of the boundary point ID group data. Then, the polygon data management unit 36 may update the setting order number of the boundary point ID set in the boundary point ID group data of the polygon data to the specified setting order number.

In this way, the polygon data may be maintained according to the registration of the new boundary point setting data.

In the present embodiment, when the polygon data is updated or the lot number map image is updated, geometric transformation such as affine transformation may be performed on the polygon.

The present invention is not limited to the above embodiment.

For example, the plurality of boundary point setting data may be data managed by a block chain (shared management by a plurality of P2P-connected computers) instead of data managed by a single server 10. The polygon data may also be data managed by a block chain instead of data managed by a single server 10.

Further, for example, it may be specified that a predetermined type of registration application has been made based on the registration information instead of the registration application information data. Then, the map data associated with the registration application specified based on the registration information may be acquired.

Further, the specific character strings and numerical values described above and the specific character strings in the drawings are examples, and the present invention is not limited to these character strings and numerical values.

10 server, 10a processor, 10b storage unit, 10c communication unit, 10d output unit, 10e input unit, 12 terminal, 12a processor, 12b storage unit, 12c communication unit, 12d output unit, 12e input unit, 14 provision of registration application information data System, 16 registration information providing service, 18 computer network, 20 registration information storage unit, 22 registration application information data storage unit, 24 registration application information data request unit, 26 registration application information data acquisition unit, 28 boundary point setting data storage unit, 30 map type strength correspondence data storage unit, 32 polygon data storage unit, 34 boundary point setting data generation unit, 36 polygon data management unit, 38 lot number map image generation unit, 40 request reception unit, 42 data transmission unit.

Claims (8)

Stores boundary point setting data including position data indicating the position of the boundary point and intensity data indicating the high credibility of the position, which is associated with the type of map or drawing in which the boundary point is indicated. Boundary point setting data storage means for
The new position data indicating the position of the boundary point shown in a map or drawing different from the map or drawing, and the new intensity data associated with the type of the different map or drawing, Boundary point setting data generating means for generating the new boundary point setting data including;
Saving means for storing the new boundary point setting data to be generated in the boundary point setting data storage means in association with the boundary point setting data already stored in the boundary point setting data storage means,
Boundary point setting history management system characterized by including. Further comprising map data acquisition means for acquiring map data showing a map or drawing associated with a predetermined type of registration application,
The boundary point setting data generation means includes the new position data indicating the position of the boundary point shown in the map data, and the new intensity data associated with the type of the map data. Generating the new boundary point setting data including the
The boundary point setting history management system according to claim 1, wherein: The plurality of boundary point setting data is data managed by a block chain,
The boundary point setting history management system according to claim 1 or 2, characterized in that. The boundary point setting data storage means stores the boundary point setting data for a plurality of different boundary points,
A map image generating means for generating a map image based on polygon data representing a polygon including a plurality of the boundary points as vertices;
For at least two vertices included in the polygon, the maps or drawings in which the vertices are shown as the boundary points are different from each other,
The boundary point setting history management system according to any one of claims 1 to 3, wherein Update means for updating the polygon data representing a polygon including the boundary point whose position is indicated in the boundary point setting data as a vertex in response to the generation of the new boundary point setting data,
The boundary point setting history management system according to claim 4, wherein. Boundary point setting data including position data indicating the position of the boundary point shown on the map or drawing and strength data indicating the high credibility of the position associated with the type of the map or drawing. The step of generating
The new boundary point setting data to be generated is stored in the boundary point setting data storage means and indicates the position of the boundary point shown in a map or drawing different from the map or drawing. Storing in the boundary point setting data storage means in association with the boundary point setting data including position data and the intensity data associated with the different map or drawing type;
A boundary point setting history management method comprising: Boundary point setting data including position data indicating the position of the boundary point shown on the map or drawing and strength data indicating the high credibility of the position associated with the type of the map or drawing. Procedure to generate,
The new boundary point setting data to be generated is stored in the boundary point setting data storage means and indicates the position of the boundary point shown in a map or drawing different from the map or drawing. A procedure of storing the data in the boundary point setting data storage means in association with the boundary point setting data including position data and the intensity data associated with the different map or drawing type;
A program characterized by causing a computer to execute. Position data indicating the position of the boundary point shown in the map or drawing,
Strength data indicating the high credibility of the position, which is associated with the type of map or drawing,
A data structure of boundary point setting data, which includes:

Images