JP2005043499A - Map data editing system and map data editing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a map data editing system and a map data editing method capable of uniformly providing the history of map data and smoothly operating the editing work for the map data. <P>SOLUTION: The map data editing system 12 which accepts the request for the map data and edits the map data in compliance with the request, is equipped with a request storage means 44 which successively stores the requests for the map data prohibited of edition, and a history forming means 34 which reads the request for the map data accepted during the prohibition time of the edition when the prohibition of the edition to the map data is canceled out of the request storage means 44 and forms the history of the map data according to the request for the map data accepted during the prohibition time of the edition from that request and the map data of the present situation. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a map data editing apparatus and a map data editing method, and more particularly to a map data editing apparatus and a map data editing method for editing map data that may be temporarily prohibited from being edited.
[0002]
[Prior art]
For example, in the real estate registration, the location and shape of the land must be accurately displayed, but there are areas where the map situation differs from the local situation due to various factors. Such areas are called map-confused areas. Areas that have been determined to be map confused areas by the staff of the Legal Affairs Bureau (for example, map registrars) will be unable to register for land display. Legal personnel will determine map disruption based on experience. In addition, methods for resolving map disruption areas include land improvement / land readjustment projects and the creation of Article 17 maps.
[0003]
Since the map of the map disruption area is clearly different from the local situation, it is not possible to create digitized map data. For this reason, in the map system used for real estate registration, the map transfer process is not performed until the map confused area is resolved, and the map change process is performed from the time when the map confused area is resolved.
[0004]
That is, since the map system used for real estate registration does not manage the history of map changes in the map confused area, the map change history during the map mess cannot be provided.
[0005]
Patent Document 1 describes the technical content of reversely generating a past satellite trajectory from orbital element parameters when there is no past satellite trajectory information.
[0006]
[Patent Document 1]
JP-A-8-262119
[0007]
[Problems to be solved by the invention]
In real estate registration, map data is required to determine the location and shape of land. In other words, economic transactions cannot be realized with only registered items published in the registry. Therefore, the map system used for real estate registration has a specification for managing not only the current map data but also the history of map changes for which registration has been applied in the past.
[0008]
However, since the conventional map system does not manage the history of map changes in the map confused area, there is a problem that even after the map mess is resolved, the map change history during the map mess cannot be provided. . For this reason, the convenience of users in the map-confused area remains impaired, and uniform services cannot be provided nationwide.
[0009]
Furthermore, since the map confused area was judged based on the experience of the staff of the Legal Affairs Bureau, the judgment standard of the map confused area was not constant, and there was a problem that the smooth operation of the real estate registration business was impaired.
[0010]
The present invention has been made in view of the above points, and provides a map data editing apparatus and a map data editing method capable of uniformly providing a history of map data and smoothly operating a map data editing operation. The purpose is to provide.
[0011]
[Means for Solving the Problems]
Therefore, in order to solve the above problems, the present invention is a map data editing apparatus that accepts a request for map data and edits the map data in response to the request, and stores a request for map data that is prohibited from being edited. When the prohibition of editing with respect to the request storage means and the map data is released, the request for the map data received while the editing is prohibited is read from the request storage means, and the request and the current map data And a history creation means for creating a history of map data in response to a request for the map data received while editing is prohibited.
[0012]
Further, the present invention compares the request for map data with the map data read from the map data storage means, and according to the ratio that the target area of the request is not included in the map data read from the map data storage means. A configuration may further include editing prohibition notification means for notifying the necessity of prohibition of editing for map data.
[0013]
Further, the present invention is a map data editing method of a map data editing apparatus that accepts a request for map data and edits the map data in response to the request, and stores a request for map data for which editing is prohibited. When the prohibition of editing on the map data is lifted, the request for the map data received while the editing is prohibited is read from the request storage means, and the request and the current map data And a step of creating a history of map data in response to a request for the map data received while editing is prohibited.
[0014]
According to the present invention, it is possible to create a history of map data in response to a request for map data received while editing is prohibited, so map data regardless of whether editing has been prohibited in the past. Can provide a uniform history.
[0015]
In addition, according to the present invention, since it is possible to notify the necessity of prohibiting editing of map data, the determination criteria for prohibiting editing of map data can be made constant and map data editing can be smoothly operated.
[0016]
DETAILED DESCRIPTION OF THE INVENTION
Next, embodiments of the present invention will be described with reference to the drawings. In addition, although a present Example demonstrates the process at the time of operation of the real estate registration application as an example, what kind of process which receives the request | requirement with respect to map data and edits map data according to the request | requirement may be sufficient.
[0017]
FIG. 1 is a configuration diagram of an example of a system for operating a real estate registration application. In the system 1 of FIG. 1, an application reception system 10, a registration system 11, a map system 12, and terminals 13a to 13n are connected via a network 14 such as the Internet or a LAN.
[0018]
The terminals 13 a to 13 n are operated by an applicant, a staff of the Legal Affairs Bureau (hereinafter referred to as a registrar), and are connected to the application reception system 10, the registration system 11, and the map system 12 via the network 14. The terminals 13a to 13n are connected to the application reception system 10 when operated by the applicant, and are connected to any of the application reception system 10, the registration system 11, and the map system 12 when operated by the registrar.
[0019]
The application reception system 10 performs an authentication process when any of the terminals 13 a to 13 n is connected via the network 14. When the authentication process is normally completed, the application reception system 10 receives an online application from the applicant and performs a format examination, and then distributes the application to the system according to the application content, while the application result from the system according to the application content. Is notified to the terminals 13a to 13n.
[0020]
For example, the application reception system 10 receives a registration application form and a land surveying map, performs format examination, and then distributes the registration application form and the land surveying map to the registration system 11. The registration system 11 receives the registration application form and the land surveying map distributed by the application reception system 10.
[0021]
Also, the registration system 11 is connected to any of the terminals 13a to 13n operated by the registrar via the network 14, and receives the registration application form and the land surveying map received by the window application. The registration system 11 performs a registration process according to the received registration application form and the land surveying map, and stores the application content in the registered item DB.
[0022]
When the received application content is an application related to a map such as a division or a combined writing, the registration system 11 transmits the application content to the map system 12 after the registration process is completed. The map system 12 performs a process related to a map as described later. The map system 12 corresponds to the map data editing device of the present invention.
[0023]
Next, the configuration of the map system 12 will be described. FIG. 2 is a configuration diagram of an example of a computer that implements the map system. The map system 12 includes an input device 21, a display device 22, a drive device 23, a recording medium 24, an auxiliary storage device 25, a memory device 26, and an arithmetic processing device 27 that are connected to each other via a bus B. And an interface device 28 and a database (hereinafter referred to as DB) 29.
[0024]
The input device 21 includes a keyboard and a mouse, and is used for inputting various operation signals. The display device 22 includes a display device and is used to display various windows and data. The interface device 28 includes a modem, a terminal adapter, and the like, and is used for connecting to the network 14. The DB 29 stores various information necessary for performing processing related to the map.
[0025]
A program related to the processing of the map system 12 is provided by, for example, distribution of the recording medium 24 or downloading from the network 14. As the recording medium 24, information such as a CD-ROM, a flexible disk, a magneto-optical disk (MO), etc., which records information optically, electrically or magnetically, ROM, a flash memory, etc. Various types of recording media such as a semiconductor memory for electrical recording can be used.
[0026]
When the recording medium 24 on which the program is recorded is set in the drive device 23, the program is installed from the recording medium 24 to the auxiliary storage device 25 via the drive device 23. The program downloaded from the network 14 is installed in the auxiliary storage device 25 via the interface device 28.
[0027]
The auxiliary storage device 25 stores the installed program and also stores necessary files, data, and the like. The memory device 26 reads and stores the program from the auxiliary storage device 25 when the computer is started. The arithmetic processing unit 27 implements various functions of the map system 12 in accordance with a program stored in the memory device 26.
[0028]
FIG. 3 is a functional configuration diagram of an example of the map system. The map system 12 of FIG. 3 includes a map data processing unit 31, a map confused area determination unit 32, a confusion application management unit 33, a confusion history map creation unit 34, a map reception DB 41, and a registration realized by a program. A place map attribute DB 42, a registry map figure DB 43, and a map confusion state management DB 44 are configured.
[0029]
The processing of the various functional units in FIG. 3 will be described with reference to the flowchart in FIG. FIG. 4 is a flowchart of an example of processing of the map system. In step S10, the map data processing unit 31 of the map system 12 stores the application content received from the registration system 11 in the map reception DB 41.
[0030]
FIG. 5 is a configuration diagram of an example of the map reception DB. The map reception DB 41 in FIG. 5 has data items such as reception ID, lot number area, application lot number, pre-change lot number, post-change lot number, classification, map number, and registration date. Details of the data items in the map reception DB 41 will be described later.
[0031]
In step S11, the map data processing unit 31 searches the registration number map attribute DB 42 as shown in FIG. 6 for a lot number area corresponding to the application content received from the registration system 11, and associates the application content with the map.
[0032]
FIG. 6 is a configuration diagram of an example of the registry map attribute DB. The registry office map attribute DB 42 in FIG. 6 has data items such as a reception ID, a lot number area, a lot number, a latest determination flag, a map number, and a lot number. Details of data items in the registry map attribute DB 42 will be described later.
[0033]
In step S12, the map confused area determination unit 32 searches the registry map attribute DB 42 for a lot number area and lot number corresponding to the application received from the registration system 11, and applies the property and application registered in the registry map attribute DB 42. Automatically associate content.
[0034]
In addition, the map confused area determination unit 32 presents a property specifying screen for allowing the registrar to specify a property when the property registered in the registry map attribute DB 42 cannot be automatically associated with the application content. If possible, the property registered in the registry map attribute DB 42 is associated with the application content.
[0035]
The map confused area determination unit 32 stores the map transfer application count and the property identification failure count in the map confused state management DB 44 as shown in FIG. The number of property identification failures represents the number of times the property registered in the registry map attribute DB 42 and the application content are not automatically associated. Further, when the ratio of the number of property identification failures to the number of map transfer applications exceeds a certain value for the map corresponding to the application content, the map confused area determination unit 32 sets the map confused state flag in the map confused state management DB 44 to the content. Set the flag to represent.
[0036]
FIG. 7 is a configuration diagram of an example of the map confusion state management DB. The map confusion state management DB 44 of FIG. 7 has data items such as a map number, a map confusion state flag, the number of map transfer applications, and the number of property identification failures. The map confusing state flag means that the ratio of the number of property identification failures to the number of map transfer applications exceeds a certain value, the ratio of the number of property identification failures to the number of map transfer applications does not exceed a certain value, This is a data item for identifying the state specified for the area. The details of the data items other than the map confusion state flag in the map confusion state management DB 44 will be described later.
[0037]
In step S13, the confusion application management unit 33 sets the property that could not be automatically associated with the application content in the map confusion area determination unit 32 as a map confusion candidate, and prepares for the future map confusion in FIG. Data necessary for creating a transfer history map, which will be described later, is stored in the registry map graphic DB 43 of FIG.
[0038]
FIG. 8 is a configuration diagram of an example of a registry map graphic DB representing coordinate information. The registry map graphic DB 43 in FIG. 8 has normal coordinate information and coordinate information necessary for creating a transfer history map, which will be described later.
[0039]
FIG. 8A shows normal coordinate information. FIG. 8B shows coordinate information necessary for creating a change history map, which will be described later. The registry map graphic DB 43 in FIG. 8A has data items such as reception ID, point number, latest discrimination flag, system X coordinate, system Y coordinate, public X coordinate, and public Y coordinate. The registry map graphic DB 43 in FIG. 8B has data items such as a reception ID, a point number, a public X coordinate, and a public Y coordinate.
[0040]
FIG. 9 is a configuration diagram of an example of a registry map graphic DB representing connection information. The registry map graphic DB 43 in FIG. 9 has normal connection information and connection information necessary for creating a transfer history map, which will be described later.
[0041]
FIG. 9A shows the connection information at the normal time. FIG. 9B shows connection information necessary for creating a transfer history map, which will be described later. The registry map figure DB 43 in FIG. 9A has data items such as reception ID, lot number area, lot number, latest discrimination flag, dot number 1, dot number 2, brush stroke, and application date. The registry map figure DB 43 in FIG. 9B has data items such as reception ID, lot number area, lot number, point number 1, point number 2, pen stroke line, and application date. Details of the data items of the registry map graphic DB 43 in FIGS. 8 and 9 will be described later.
[0042]
In step S14, the map confused area determination unit 32 refers to the map confused state flag in the map confused state management DB 44, and when the ratio of the number of property identification failures to the number of map transfer applications exceeds a certain value, the registration system The registration operator operates, for example, the terminal 13a to notify that the property corresponding to the application content received from 11 is a map confused area with a high probability.
[0043]
The registrar confirms, for example, on the screen of the terminal 13a a message that the property corresponding to the application received from the registration system 11 is a map confused region with a high probability, and whether or not to designate the property as a map confused region. Is input to the terminal 13a. The terminal 13a transmits to the map confused area determination unit 32 of the map system 12 an instruction as to whether or not to designate the map confused area input from the registrar. That is, when a registrar designates a property as a map confused area, the registrar does not perform map transfer processing according to the application content, and interrupts the application for the property.
[0044]
Proceeding to step S15, when the instruction to designate the map confused area input from the registrar is received (YES in S15), the map confused area determining unit 32 proceeds to step S17. In step S17, the map confused area determination unit 32 sets a flag indicating the state designated as the map confused area as a map confused state flag in the map confused state management DB 44, and ends the process.
[0045]
In step S15, when the instruction indicating that the map is not designated as a map confused area input from the registrar is received (NO in S15), the map confused area determination unit 32 proceeds to step S16. In step S16, the map data processing unit 31 performs a map transfer process according to the application contents, reflects the result of the map transfer process in the registry map attribute DB 42 and the registry map graphic DB 43, and ends the process.
[0046]
Next, processing for replacing a map of a property designated as a map confused area and a new map that has solved the map confusing will be described with reference to FIG. FIG. 10 is a flowchart of an example of processing at the time of eliminating map confusion.
[0047]
Proceeding to step S20, when the map data processing unit 31 receives an instruction from the registrar, for example, from the terminal 13a operated by the registrar to replace the new map with the map confusion resolved and the map designated as the map confusion area. Then, the contents of the new map that has solved the map confusion are reflected in the map reception DB 41, the registry map attribute DB 42, and the registry map graphic DB 43. Proceeding to step S21, the confusion history map creation unit 34 creates a transfer history map during map confusion as described later, and ends the processing.
[0048]
Hereinafter, the process of the various function parts which comprise the map system 12 is demonstrated in detail. 11 and 12 are flowcharts of an example of detailed processing of the map system. In step S30, the map data processing unit 31 stores the application content received from the registration system 11 in the map reception DB 41. Here, as a result of receiving the application contents as shown in FIG. 13, the application contents as shown in FIG. 14 are stored in the map reception DB 41.
[0049]
FIG. 13 is a configuration diagram of an example of application contents accepted by the map system. The application content in FIG. 13 includes a reception ID and content including a lot number area, lot number, and division. The reception ID is a number that uniquely identifies the application. The lot number area is information for specifying the location of the property to be applied. The lot number is a number uniquely assigned in the map to the brush, and is information for identifying the property to be applied. The classification is information representing the content of the application (division, writing, map correction, etc.). Further, the registration date is information that identifies the date on which registration is applied.
[0050]
FIG. 14 is a configuration diagram of an example of a map reception DB in which application contents from the registration system are stored. The map reception DB 41 in FIG. 14 is configured to have data items such as reception ID, lot number area, application lot number, pre-change lot number, post-change lot number, classification, map number, registration date, and the like. , Lot number area, application lot number, classification, and application date are stored.
[0051]
In step S31, the map data processing unit 31 searches the registry location map attribute DB 42 as shown in FIG. 15 for a lot number area corresponding to the application content received from the registration system 11, and associates the application content with the map.
[0052]
FIG. 15 is a configuration diagram of an example of a registry office map attribute DB. The registry office map attribute DB 42 in FIG. 15 has data items such as a reception ID, a lot number area, a lot number, a latest determination flag, a map number, and a lot number. The latest determination flag is a flag indicating whether or not the map corresponding to the record is the latest. A map number is a number that uniquely identifies a map. The ground pattern is information indicating the main use of the lot number area.
[0053]
The process of step S31 will be further described. FIG. 16 is an explanatory diagram of an example of processing for associating application contents with a map. First, the map data processing unit 31 searches the registry map attribute DB 42 for records with matching lot numbers using the lot number area included in the application content as key information.
[0054]
However, the map data processing unit 31 determines that only records whose latest determination flag is ON are valid records. The map data processing unit 31 reads the map number of a valid record among the searched records, and transfers the map number to the map number of the map reception DB 41 as shown in FIG. The map data processing unit 31 indicates that there is no property to be applied for in the property presence flag of the map reception DB 41 if there is no record in the registry map attribute DB 42 that matches the lot number area included in the application content. Set the flag “ON”.
[0055]
In step S32, the map data processing unit 31 refers to the map confusion state flag of the map confusion state management DB 44 as shown in FIG. 17, and the map confusion candidate in which the ratio of the number of property identification failures to the number of map transfer applications exceeds a certain value. It is determined whether the state is a normal state where the ratio of the number of property identification failures to the number of map transfer applications does not exceed a certain value, or a map confused state designated as a map confused area.
[0056]
FIG. 17 is a configuration diagram of an example of the map confusion state management DB. In the map disruption state flag, “◯” represents a normal state, “Δ” represents a map disruption candidate state, and “×” represents a map disruption state.
[0057]
If it is determined in step S32 that the map confusion state flag is in the normal state or the map confusion candidate state, the map data processing unit 31 proceeds to step S33. In step S33, the map data processing unit 31 refers to the property presence flag in the map reception DB 41, and determines whether or not the property to be applied exists in the map system 12.
[0058]
If the property presence flag is “ON” (ON in S33), the map data processing unit 31 proceeds to step S34. On the other hand, if the property presence flag is a flag “OFF” indicating that there is no property to be applied (OFF in S33), the map data processing unit 31 proceeds to step S36 described later.
[0059]
In step S34, the map confused area determination unit 32 searches the registry office map attribute DB 42 for a lot number area and lot number corresponding to the application content received from the registration system 11, and registers the property and application registered in the registry map attribute DB 42. Automatically associate content. The map confused area determination unit 32 reads out the lot number of the property registered in the registry map attribute DB 42 associated with the application content, and registers the lot number in the pre-change lot number of the record in the map reception DB 41 corresponding to the application.
[0060]
The process of step S34 will be further described. FIG. 18 is an explanatory diagram of an example of a process for automatically associating a property registered in the registry map attribute DB 42 with the application content.
[0061]
First, the map confused area determination unit 32 searches for a record where the lot number area and the lot number coincide with each other as the location information in the registry map attribute DB 42 using the lot number area and the application lot number as the location information in the map reception DB 41 as key information, The property registered in the registry map attribute DB 42 is automatically associated with the application content. However, the map confused area determination unit 32 determines that only the record having the latest determination flag ON is a valid record.
[0062]
For example, in FIG. 18, the application contents of the reception IDs “a001”, “a002”, and “a005” have been successfully associated with the properties registered in the registry map attribute DB42. Further, the application contents of the reception IDs “a003” and “a004” have failed to be associated with the property registered in the registry map attribute DB 42.
[0063]
Proceeding to step S35, if the map confused area determination unit 32 determines that the association between the property registered in the registry map attribute DB 42 and the application content has all been successful (successful in step S35), the process proceeds to step S38. If it is determined in step S32 that the map confusion state flag is a map confusion state, the map data processing unit 31 proceeds to step S38.
[0064]
On the other hand, if the map confusion area determination unit 32 determines that at least part of the association between the property registered in the registry map attribute DB 42 and the application content has failed (failed in step S35), the process proceeds to step S36.
[0065]
In step S36, the map confused area determination unit 32 displays the property specifying screen for allowing the registrar to specify the property on the terminal 13a operated by the registrar, and is registered in the registry map attribute DB 42 if possible. Associate the property with the application details.
[0066]
Proceeding to step S37, if the association between the property registered in the registry map attribute DB 42 and the application content is successful (successful in S37), the map confused area determination unit 32 responds to the application content from the registry map attribute DB 42. After reading the lot number of the attached property and registering the lot number in the pre-change lot number of the record in the map reception DB 41 corresponding to the application, the process proceeds to step S38.
[0067]
On the other hand, if the association between the property registered in the registry map attribute DB 42 and the application content fails (failed in S37), the map confused area determination unit 32 has the property presence flag in the record of the map reception DB 41 corresponding to the application. Is set to “OFF”. In this case, the processing returns to step S32 after performing the necessary steps for identifying the property, such as correction of the application content or investigation.
[0068]
Details of the processing in steps S36 and S37 will be further described. FIG. 19 is an image diagram of an example of the property identification screen. The property specifying screen 50 selects a column 51 for selecting an application, a column 52 for selecting a property to be applied, a column 53 for selecting a property stored in the registry map attribute DB 42 associated with the application, and a location of the property. It is configured to have a column 54.
[0069]
In the property specifying screen 50, the association between the property registered in the registry map attribute DB 42 and the application content can be added, modified, or deleted. When the cancel button on the property specifying screen 50 is pressed without adding the correspondence between the property registered in the registry map attribute DB 42 and the application content, the map confused area determination unit 32 has the property present in the map reception DB 41. In the flag, a flag “OFF” indicating that there is no property to be applied is set.
[0070]
A process when the association between the property registered in the registry map attribute DB 42 using the property specifying screen 50 and the application content is successful will be described. FIG. 20 is an explanatory diagram of an example of processing when the association between the property registered in the registry map attribute DB and the application content using the property identification screen is successful.
[0071]
First, the reception ID “A 004” is selected in the column 51 of the property identification screen 50, and the map confused area determination unit 32 displays the application lot number “28” read from the map reception DB 41a in the column 52. When the lot number area “Ichikawa-shi Nitta 2-chome” is selected in the column 54, the map confusion area determination unit 32 lists the lot numbers existing in the lot number area “Ichikawa-shi Nitta 2-chome” read from the registered map attribute DB 42. Is displayed in the column 53.
[0072]
When the registration button is pressed after the lot number “28-1” is selected in the field 53, the map confused area determination unit 32 sets the lot number “28-1” as the pre-change lot number in the map reception DB 41b.
[0073]
A process when the correspondence between the property registered in the registry map attribute DB 42 using the property specifying screen 50 and the application content fails will be described. FIG. 21 is an explanatory diagram of an example of processing when the association between the property registered in the registry map attribute DB using the property specifying screen and the application content fails.
[0074]
The reception ID “A 003” is selected in the column 51 of the property identification screen 50, and the map confused area determination unit 32 displays the application lot number “31-1” read from the map reception DB 41a in the column 52. The lot number area “Yokosuka City Urakamidai 2-chome” is selected in the column 54, and the map confusion area determination unit 32 displays a list of lot numbers existing in the lot number area “Yokosuka City Urakamidai 2-chome” in the column 53. indicate. When the cancel button is pressed without selecting a lot number in the field 53, the map confused area determination unit 32 sets “OFF” in the property presence flag of the map reception DB 41b.
[0075]
In step S38, the map confused area determination unit 32 refers to the map confused state flag of the map confused state management DB 44 as shown in FIG. 17, and determines whether the map confused candidate state, the normal state, or the map confused state. If it is determined in step S38 that the map confused state flag is normal, the map confused area determining unit 31 proceeds to step S40. On the other hand, if it is determined in step S38 that the map confused state flag is the map confused candidate state or the map confused state, the map confused area determining unit 31 proceeds to step S39. In step S39, the confused application management unit 33 performs a map confused application history creation process to be described later, and then proceeds to step S40.
[0076]
In step S40, when the map confused area determination unit 32 refers to the map confused state flag in the map confused state management DB 44 and the ratio of the number of property identification failures to the number of map transfer applications exceeds a certain value, the registration system The registration operator operates, for example, the terminal 13a to notify that the property corresponding to the application content received from 11 is a map confused area with a high probability.
[0077]
The process of step S40 will be described in detail. FIG. 22 is an image diagram of an example of the map confusion notification process. The map confused area determination unit 32 refers to the map confused state flag in the map confused state management DB 44, and calculates an automatic property identification failure rate by the following equation (1).
[0078]
Automatic property identification failure rate = Number of automatic property identification failures ÷ Number of map transfer applications (1)
Here, a process when the allowable limit of the property automatic identification failure rate is set to be less than 50% will be described. It is assumed that the data stored in the map confusion state management DB 44 is changed from the numerical value or symbol in parentheses to the numerical value or symbol outside the parentheses by the processing in steps S30 to S39 described above.
[0079]
According to the above formula (1), since the map with the map number “G501” has exceeded the automatic property identification failure rate of 50%, the map confused area determination unit 32 sets the map confused state flag of the map with the map number “G501” from the normal state. It has changed to a map confusing candidate state. When the application content at this time is the map reception DB 41 in FIG. 22, the map confused area determination unit 32 has a higher property corresponding to the application content than the application with the application ID “A003” for the map with the map number “G501”. The registrant notifies the terminal 13a, for example, that the area is a map confused area with a probability.
[0080]
The registrar confirms, for example, on the screen of the terminal 13a a message that the property corresponding to the application received from the registration system 11 is a map confused region with a high probability, and whether or not to designate the property as a map confused region. Is input to the terminal 13a. The terminal 13a transmits to the map confused area determination unit 32 of the map system 12 an instruction as to whether or not to designate the map confused area input from the registrar.
[0081]
In step S41, the map confused area determination unit 32 receives an instruction from the registrar as to whether or not to designate the property as a map confused area. When the instruction to designate the map confused area is received (YES in S41), the map confused area determination unit 32 sets a flag indicating the map confused state in the map confused state flag of the map confused state management DB 44, and proceeds to step S43. move on. In step S43, the transfer application is interrupted until, for example, an Article 17 map is created and the map confusion is resolved.
[0082]
When receiving an instruction not to designate a map confused area (NO in S41), the map confused area determination unit 32 proceeds to step S42. In step S42, the map data processing unit 31 performs a map transfer process according to the application contents, reflects the result of the map transfer process in the registry map attribute DB 42 and the registry map graphic DB 43, and ends the process.
[0083]
The number of map transfer applications in the map confusion state management DB 44 is counted in step S31. Counting the number of map transfer applications is performed when a map corresponding to the application content is specified. In addition, the number of property automatic identification failures in the map confusion state management DB 44 is counted after the correspondence between the property registered in the registry map attribute DB 42 and the application content fails in step S35.
[0084]
Next, details of the map confusion application history creation processing in step S39 will be described with reference to the flowchart of FIG. FIG. 23 is a flowchart of an example of a map confusion application history creation process.
[0085]
Here, it is assumed that the local situation in the map confused area is as shown in FIG. Further, the image of the map confused area managed by the map system 12 is processed as shown in FIG. At this time, the map data corresponding to the map confused area image of FIG. 25 is stored in the registry map attribute DB 42 and the registry map graphic DB 43 of FIGS.
[0086]
FIG. 24 is an image diagram of an example showing the local situation in a map confused area. FIG. 25 is an image diagram showing a map confused area managed by the map system. FIG. 26 is a configuration diagram of an example of a registry map graphic DB representing coordinate information. FIG. 27 is a configuration diagram of an example of a registry map graphic DB representing connection information. FIG. 28 is a block diagram of an example of a registry map attribute DB.
[0087]
First, it is assumed that an application including the geodetic survey map of FIG. 29 and the geodetic survey map data of FIG. 30 has been made to the map confused area shown in FIGS. FIG. 29 is an image diagram of an example of a land survey map. FIG. 30 is an image diagram of an example of land survey data.
[0088]
In step S50, the confusion application management unit 33 determines the record classification of the map reception DB 41 corresponding to the application. If it is determined that the record classification in the map reception DB 41 is a pen (in S50, the pen), the confusion application management unit 33 proceeds to step S51.
[0089]
In step S51, the confusion application management unit 33 reads the applied land survey data of FIG. Proceeding to step S52, the confusing application management unit 33 stores the coordinate information necessary for creating the transfer history map in the registry map graphic DB 43 among the land survey data read in step S51. The coordinate information necessary for creating the transfer history map is information on coordinates (new points) newly created based on the land surveying map included in the application.
[0090]
Proceeding to step S53, the confusion application management unit 33 stores the connection information necessary for creation of the transfer history map in the registry map graphic DB 43 among the land survey data read in step S51, and ends the process. The connection information necessary for the creation of the transfer history map is information on a connection (pencil line) newly created based on the geodetic survey map included in the application.
[0091]
FIG. 31 is an explanatory diagram for explaining the processing of steps S52 and S53. In step S52, the newly created coordinate information is stored in the registry map graphic DB 43 based on the data item “new point” of the survey point coordinate value included in the land survey data.
[0092]
In step S53, the newly created connection information is stored in the registry map graphic DB 43 based on the lot number data item “pencil line” included in the land survey data.
[0093]
On the other hand, if it is determined that the record classification in the map reception DB 41 is a handwriting (writing in S50), the confusion application management unit 33 proceeds to step S54. Normally, the application for writing will not include a geodetic survey map. The application contents received by the map system 12 in the application for writing are the lot number area, the lot number before writing, and the lot number after writing.
[0094]
The confusion application management unit 33 stores a work table as shown in FIG. 32, which includes a reception ID, a lot number area, a pre-writing lot number, a post-writing lot number, and an application date, in a temporary work area. FIG. 32 is a configuration diagram of an example of a work table used in processing related to writing. The confusion application management unit 33 searches a predetermined table (not shown) for managing the geodetic survey map and the geodetic survey map data using the pre-writing lot number of the work table in FIG. 32 as key information.
[0095]
In step S55, the confusion application management unit 33 determines whether the pre-writing lot number exists in the predetermined table that manages the land survey map and the land survey data. If it is determined that the pre-handwriting lot number exists in the predetermined table that manages the geodetic survey map and the geodetic survey map data (YES in S55), the confused application management unit 33 manages the geodetic survey map and the geodetic survey map data The record shown in FIG. 33 in which the pre-writing lot number exists is read from the predetermined table. FIG. 33 is a configuration diagram of an example of a record read from a predetermined table that manages the geodetic survey map and the geodetic survey map data.
[0096]
Proceeding to step S57, the confusing application management unit 33 stores the coordinate information necessary for creating the transfer history map in the registry map graphic DB 43 from the record shown in FIG. 33 read in step S55. The coordinate information necessary for the creation of the transfer history map is information on the coordinates that form the dividing line (line common to the two brushstrokes) of the address before writing.
[0097]
In addition, if the dividing line of the address before writing (a line common to two brushes) does not exist, the address before writing is not adjacent. Accordingly, the confusion application management unit 33 proceeds to step S56.
[0098]
In step S58, the confusion application management unit 33 stores the connection information necessary for creating the transfer history map in the registry map graphic DB 43 from the record shown in FIG. 33 read in step S55, and ends the process. The connection information necessary for creating the transfer history map is information on the connection that forms the divided line (the line common to the two brushstrokes) of the address before writing.
[0099]
FIG. 34 is an explanatory diagram for explaining the processing of steps S57 and S58. In step S57, coordinate information necessary for creating the change history map is read from the record 60 read in step S55, and stored in the registry map graphic DB 43 as coordinate information 62 required for creating the change history map.
[0100]
In step S58, the connection information necessary for creating the change history map is read from the record 61 read in step S55, and stored in the registry map graphic DB 43 as the connection information 63 necessary for creating the change history map. In addition, in the coordinate information 62 and the connection information 63 necessary for creating the change history map, the reception ID of the work table 64 as shown in FIG. 32 corresponding to the application is stored.
[0101]
If it is determined that there is no pre-handwriting lot number in the predetermined table that manages the geodetic survey map and the geodetic survey map data (NO in S55), the confusion application management unit 33 proceeds to step S56.
[0102]
In step S56, the confusing application management unit 33 uses the lot number area and the pre-writing lot number included in the work table of FIG. 32 as key information from the registered item DB as illustrated in FIG. The area of the land is acquired and the process is terminated. FIG. 35 is a configuration diagram of an example of an entry item DB included in the registration system 11.
[0103]
FIG. 36 is an explanatory diagram for describing the processing in step S56. In step S56, the confusion application management unit 33 reads the reception ID from the work table 64 and stores it in the registry map graphic DB 43 as coordinate information 62 necessary for creating the transfer history map. In addition, the confused application management unit 33 reads the reception ID, lot number area, lot number, and application date from the work table 64, and stores them in the registry map figure DB 43 as connection information 63 necessary for creating the transfer history map. .
[0104]
Next, for example, a process performed after the 17th map is created and the map confusion is resolved will be described with reference to the flowchart of FIG. FIG. 37 is a flowchart of an example of processing performed after the map confusion is resolved.
[0105]
Here, it is assumed that the map confusion has been resolved by the land improvement / land readjustment project and the creation of the Article 17 map. Further, the image of the Article 17 map in which the map confusion is resolved is processed as shown in FIG. FIG. 38 is an image diagram of an example of the 17th map in which map confusion is resolved.
[0106]
At this time, the map data corresponding to the image of the 17th map in FIG. 38 is expressed as shown in FIGS. FIG. 39 is a configuration diagram of an example of a registry map graphic DB representing coordinate information. FIG. 40 is a configuration diagram of an example of a registry map graphic DB representing connection information. FIG. 41 is a configuration diagram of an example of a registry office map attribute DB.
[0107]
In step S60, when the map data of the new map as shown in FIG. 38 in which the map confusion is resolved is created, the map data processing unit 31 stores the map data in the registry map attribute DB 42 and the registry map figure DB 43. Store in the temporary storage area.
[0108]
In step S61, the map data processing unit 31 deletes the map data of the map in the map confused area as shown in FIG. 42 in order to replace the map in the map confused area with the map in which the map confused area is resolved.
[0109]
FIG. 42 is a flowchart of an example of map data deletion processing of a map in a map confused area. First, the map data processing unit 31 searches for a record from the registry map attribute DB 71 using the map number of the map to be replaced as key information. Next, the map data processing unit 31 searches for records from the connection information in the registry map graphic DB 72 using the lot numbers included in the searched records as key information. Next, the map data processing unit 31 searches for the record from the coordinate information of the registry map graphic DB 73 using the point numbers 1 and 2 included in the searched record as key information. The map data processing unit 31 deletes the record searched as described above. The map data processing unit 31 saves the map number included in the deleted record in the save area.
[0110]
In step S62, the map data processing unit 31 stores the map data stored in the temporary storage area in step S60 in the registry map attribute DB 42 and the registry map graphic DB 43.
[0111]
In step S63, the confused history map creation unit 34 uses the map number saved in the save area in step S61 as key information to display the application contents for the replacement target map received while the transfer application is suspended as shown in FIG. One is retrieved from the map reception DB 41 like.
[0112]
FIG. 43 is a configuration diagram of an example of the map reception DB. For example, if the map number saved in the save area in step S61 is “A201”, the confusion history map creation unit 34 searches for a record with the reception ID “A001”.
[0113]
Proceeding to step S64, the confused history map creation unit 34 determines the classification of the record searched at step S63. If it is determined that the record category searched in step S63 is a pen (in S64), the confusion history management unit 33 proceeds to step S65. In step S65, the confused history map creation unit 34 performs a history map creation process for a dispensing application as described below.
[0114]
On the other hand, when it is determined that the classification of the record searched in step S63 is handwriting (writing in S64), the confusion history management unit 33 proceeds to step S66. In step S66, the confusion history map creation unit 34 performs a history map creation process for a handwriting application as will be described later.
[0115]
Progressing to step S67 following step S65 or S66, whether or not the history map creation processing of the application content for the replacement target map received while the transfer application is interrupted has been completed. Determine.
[0116]
If it is determined that the history map creation process of the application content for the replacement target map received while the transfer application is interrupted is incomplete (incomplete in S67), the confused history map creation unit 34 returns to step S63. On the other hand, if it is determined that the history map creation process of the application content for the replacement target map received while the transfer application is interrupted (completed in S67), the confused history map creation unit 34 ends the process.
[0117]
Next, details of the history map creation process for the pen application in step S65 will be described with reference to the flowchart of FIG. FIG. 44 is a flowchart of an example of a history map creation process for a dispensing application.
[0118]
In this case, it is assumed that a record having a division as a division as shown in FIG. 45 is retrieved in step S63. FIG. 45 is a configuration diagram of an example of the record searched in step S63.
[0119]
The confusion history map creation unit 34 creates a transfer history map by writing when the division is a pen. Specifically, the during-confusion history map creation unit 34 creates a change history map by writing based on the post-change location number “5-1, 5-2” of the searched record.
[0120]
Proceeding to step S70, the confused history map creation unit 34 searches the registry map attribute DB 42 as shown in FIG. 46 using the post-change lot number of the record searched in step S63 as key information. For example, the confusion history map creation unit 34 searches the registry map attribute DB 42 of FIG. 46 using the post-change address “5-1, 5-2” of the record of FIG. 45 as key information.
[0121]
FIG. 46 is a block diagram of an example of a registry map attribute DB. In the case of the registry office map attribute DB 42 of FIG. 46, the first record including the lot number “5-1” and the second record including the lot number “5-2” are searched.
[0122]
Proceeding to step S71, the confused history map creation unit 34 creates a pre-application record using the record searched in step S63 and the post-application record searched in step S70. Then, the confused history map creation unit 34 adds the created pre-application record to the registry map attribute DB 42 as shown in FIG.
[0123]
Specifically, the confusion history map creation unit 34 sets the reception ID “A001” of the record searched in step S63 to the reception ID 81 of the record searched in step S70. Next, the during-confusion history map creation unit 34 sets “Low” in the reception ID 82 of the added record before application.
[0124]
The confusion history map creation unit 34 sets the application location number “5” of the record searched in step S63 to the address 83 of the added record before application. In addition, the confusion history map creation unit 34 leaves the latest determination flag and map number of the added record before application blank. The confusion history map creation unit 34 sets the other data items in the added record before the application to be the same as the record searched in step S70.
[0125]
Proceeding to step S72, the confusion history map creation unit 34 searches the registry map figure DB 43 representing the connection information as shown in FIG. 48 using the post-change lot number of the record searched in step S63 as key information. For example, the confusion history map creation unit 34 searches the registry map figure DB 43 of FIG. 48 using the post-change address “5-1, 5-2” of the record of FIG. 45 as key information.
[0126]
FIG. 48 is a configuration diagram of an example of a registry map graphic DB representing connection information. In the case of the registry map graphic DB 43 in FIG. 48, the first to fourth records including the lot number “5-1” and the fifth to eighth records including the lot number “5-2” are searched.
[0127]
Proceeding to step S73, the confused history map creation unit 34 creates a record before application using the record searched at step S63 and the record after application searched at step S72. Then, as shown in FIG. 49, the confusing history map creation unit 34 adds the created record before application to the registry map graphic DB 43.
[0128]
Specifically, the confusion history map creation unit 34 sets the reception ID “A001” of the record searched in step S63 to the reception ID 91 of the record searched in step S72. Next, the confusion history map creation unit 34 sets “Low” in the reception ID 92 of the added record before application.
[0129]
The confused history map creation unit 34 sets the application location number “5” of the record searched in step S63 to the address 93 of the added record before application. Also, the during-confusion history map creation unit 34 sets the registration date “20030420” of the record searched in step S63 to the application date 94 of the added record before application. The confused history map creation unit 34 sets “Low” to the registration date 95 of the added record before application. The confusion history map creation unit 34 sets the other data items in the added record before the application to be the same as the record searched in step S72.
[0130]
Proceeding to step S74, the confusing history map creation unit 34 deletes the extra stroke lines because the connection information added to the registry map graphic DB 43 in step S73 includes the extra stroke lines.
[0131]
Specifically, the confusion history map creation unit 34 uses the reception ID of the record searched in step S63 as key information, and the connection information necessary for creating the transfer history map stored in the registry map graphic DB 43 in step S58. Search for. Then, the confusing history map creation unit 34 deletes the same line as the searched stroke line from the pre-application record added in step S73.
[0132]
FIG. 50 is an image diagram illustrating an example of a process of deleting a stroke line. In FIG. 50, the connection information 100 necessary for creating the transfer history map is searched, and the stroke line (connection consisting of the dot numbers T14 and T15) included in the connection information 100 is added from the record 101 before application added in step S73. An example of being deleted is shown.
[0133]
In step S75, the confused history map creation unit 34 determines whether or not there is a new point created by the dividing brush. Specifically, the confused history map creation unit 34 uses the reception ID of the record searched in step S63 as key information, and obtains the coordinate information necessary for creating the transfer history map stored in the registry map graphic DB 43 in step S57. Search for records that contain it. Then, the during-confusion history map creation unit 34 confirms the state of the new point of the retrieved record. FIG. 51 is a configuration diagram of an example of a record searched in the process of step S75.
[0134]
If the new point is “ON”, the confused history map creation unit 34 determines that there is a new point created by the dividing brush, and proceeds to step S76. When the new point is “ON”, the confusion history map creation unit 34 creates a new writing point. Therefore, when the confusion history map creation unit 34 deletes the extra connection information, it is necessary to synthesize the brush stroke line connecting the newly created stroke line as shown in FIG.
[0135]
FIG. 52 is an image diagram of an example of processing for deleting excess connection information when the new point is “ON”. When the writing boundaries 5 and 6 are new points, the confusion history map creation unit 34 not only deletes the dividing line (5-6) but also connects the writing lines (1-5) and (5-2). It is necessary to create a stroke line (1-2). Similarly, it is necessary to create the writing line (3-4) by connecting the writing lines (3-6) and (6-4).
[0136]
If the new point is blank, the confusion history map creation unit 34 determines that there is no new point created by the dividing brush and ends the process. When the new point is blank, the confusion history map creation unit 34 has not created a new writing point as shown in FIG.
[0137]
FIG. 53 is an image diagram of an example of processing for deleting extra connection information when a new point is blank. If the writing points 1 and 3 are not new points, the confusion history map creation unit 34 only needs to delete the stroke line (1-3).
[0138]
In step S76, the confusion history map creation unit 34 synthesizes the stroke line connecting the newly created stroke line as shown in FIG. FIG. 54 is an image diagram of an example of processing for deleting excess connection information when the new point is “ON”.
[0139]
First, the confused history map creation unit 34 uses the new points T14 and T15 created by the division as key information, and records the pre-application record 111 in which the division line (connection consisting of the point numbers T14 and T15) is deleted in step S74. Search in order. A record 111 before application in FIG. 54 represents records 112 and 113 selected when the new point T14 is used as key information.
[0140]
The confused history map creation unit 34 can create the record 121 from the records 112 and 113 by deleting the new points T14 included in the records 112 and 113 and connecting the point numbers T10 and T11. Similarly to the new point T14, the confusion history map creation unit 34 deletes the new point T15 included in the records 112 and 113 and connects the point numbers T12 and T13, so that the pre-application as shown in FIG. Can create records.
[0141]
Proceeding to step S77, the confused history map creation unit 34 uses the receipt ID of the record searched at step S63 as key information, and obtains the coordinate information necessary for creating the transfer history map stored in the registry map graphic DB 43 at step S57. Search for. Then, the registry map graphic DB 43 representing coordinate information is searched using the point number included in the searched record as key information, and the reception ID of the record searched in step S63 is set as the reception ID of the searched record. finish.
[0142]
FIG. 56 is an image diagram of an example of the process of step S77. In FIG. 56, the record 131 necessary for creating the transfer history map is searched using the reception ID “A001” as key information, the record 132 is searched using the point numbers T14 and T15 included in the record 131 as the key information, The reception ID “A 001” is set in 132.
[0143]
44, the registry map attribute DB 42 in FIG. 57, the registry map graphic DB 43 representing the coordinate information in FIG. 58, the registry map graphic DB 43 representing the connection information in FIG. A map reception DB 41 can be created.
[0144]
Next, details of the history map creation process for the writing application in step S66 will be described with reference to the flowchart of FIG. FIG. 61 is a flowchart of an example of a history map creation process for a dispensing application. Here, it is assumed that the image of the 17-article map in which the map confusion has been eliminated is shown in FIG. FIG. 62 is an image diagram of an example of the 17th map in which map confusion is resolved.
[0145]
At this time, the map data corresponding to the image of the 17th map in FIG. 62 is expressed as shown in FIGS. 63 to 65, for example. FIG. 63 is a configuration diagram of an example of a registry map graphic DB representing coordinate information. FIG. 64 is a configuration diagram of an example of a registry map graphic DB representing connection information. FIG. 65 is a block diagram of an example of a registry map attribute DB.
[0146]
In step S63, a process is performed in which a record in which the classification is a writing as shown in FIG. 66 is retrieved. FIG. 66 is a block diagram showing an example of the record searched in step S63.
[0147]
The confusion history map creation unit 34 creates a change history map by dividing the classification when the classification is a writing. Specifically, the during-confusion history map creation unit 34 creates a change history map by dividing the number based on the post-change lot number “6” of the searched record.
[0148]
Proceeding to step S80, the confusion history map creation unit 34 searches the registry map attribute DB 42 as shown in FIG. 67 using the post-change lot number of the record searched in step S63 as key information. For example, the confusion history map creation unit 34 searches the registry map attribute DB 42 in FIG. 67 using the post-change address “6” in the record in FIG. 66 as key information. FIG. 67 is a block diagram of an example of a registry map attribute DB. In the case of the registry map attribute DB 42 shown in FIG. 46, the first record including the lot number “6” is searched.
[0149]
Proceeding to step S81, the confused history map creation unit 34 creates a record before application using the record searched at step S63 and the record after application searched at step S80. Then, the confused history map creation unit 34 adds the created pre-application record to the registry map attribute DB 42 as shown in FIG.
[0150]
Specifically, the confused history map creation unit 34 sets the reception ID “A001” of the record searched in step S63 to the reception ID 141 of the record searched in step S80. Next, the confusion history map creation unit 34 sets “Low” in the reception ID 142 of the added record before application.
[0151]
The confused history map creation unit 34 sets the application lot numbers “6” and “7” of the record searched in step S63 to the addresses 143 and 144 of the added record before application. In addition, the confusion history map creation unit 34 leaves the latest determination flag and map number of the added record before application blank. The confusion history map creation unit 34 sets the other data items in the added record before the application to be the same as the record searched in step S80.
[0152]
Proceeding to step S82, the confusion history map creation unit 34 searches the registry map figure DB 43 representing the connection information as shown in FIG. 69 using the post-change lot number of the record searched in step S63 as key information. For example, the confusion history map creation unit 34 searches the registry map figure DB 43 of FIG. 69 using the post-change address “6” of the record of FIG. 66 as key information.
[0153]
FIG. 69 is a configuration diagram of an example of a registry map graphic DB representing connection information. In the case of the registry map graphic DB 43 in FIG. 69, the first to fifth records including the lot number “6” are searched.
[0154]
Proceeding to step S83, the confusing history map creation unit 34 determines whether or not the geodetic survey map and the geodetic survey map data have been submitted in the past. If it is determined that the geodetic survey map and the geodetic survey map data have been submitted in the past (YES in S83), the confusing history map creation unit 34 proceeds to step S84. On the other hand, if it is determined that the geodetic survey map and the geodetic survey map data have not been submitted in the past (NO in S83), the confusing history map creation unit 34 proceeds to step S86.
[0155]
Proceeding to step S84, the confusing history map creation unit 34 creates a record before application using the record searched at step S63 and the record after application searched at step S82. Then, as shown in FIG. 70, the confused history map creation unit 34 adds the created record before application to the registry map graphic DB 43.
[0156]
Specifically, the confused history map creation unit 34 sets the reception ID “A001” of the record searched in step S63 to the reception ID 151 of the record searched in step S82. Next, the confusion history map creation unit 34 sets “Low” to the reception ID 152 of the added record before application.
[0157]
The confusion history map creation unit 34 sets the application location numbers “6” and “7” of the record searched in step S63 to the added address 153 of the record before application. The confused history map creation unit 34 sets the application date “20030420” of the record searched in step S63 to the application date 154 of the added record before application.
[0158]
The confused history map creation unit 34 sets “Low” to the registration date 155 of the added record before application. Further, the confusion history map creation unit 34 sets the other data items in the added record before the application to be the same as the record searched in step S82.
[0159]
Proceeding to step S85, the confused history map creation unit 34 creates transfer history maps stored in the registry map figure DB 43 in step S57 using the reception ID “A001” of the record searched in step S63 as key information. Search for the necessary coordinate information. Then, the confused history map creation unit 34 adds the found record to the registry map graphic DB 43 and ends the process.
[0160]
FIG. 71 is an image diagram of an example of the process of step S85. In FIG. 71, the coordinate information 161 necessary for creating the transfer history map is searched, and the coordinate information 161 is added to the registry map graphic DB 162 representing the coordinate information.
[0161]
On the other hand, if it is determined that the geodetic survey map and the geodetic survey map data have not been submitted in the past, the confused history map creation unit 34 proceeds to step S86. In this case, there is no area surveying map and area surveying map data for the writing brush, so even if the map confusion is resolved, a complete transfer history map cannot be created. Therefore, the confusion history map creation unit 34 creates a record before application within a possible range, and outputs a message as in the screen example of FIG. FIG. 72 is an image diagram of an example of a screen output when a transfer history map cannot be created.
[0162]
Proceeding to step S86, the confused history map creation unit 34 creates a record before application using the record searched at step S63 and the record after application searched at step S82. Then, the confused history map creation unit 34 adds the created pre-application record to the registry map graphic DB 43 as shown in FIG.
[0163]
Specifically, the confusion history map creation unit 34 sets the reception ID “A001” of the record searched in step S63 to the reception ID 171 of the record searched in step S82. Next, the confusion history map creation unit 34 sets “Low” in the reception ID 172 of the added record before application.
[0164]
The confusion history map creation unit 34 sets the application location numbers “6” and “7” of the record searched in step S63 to the added address 173 of the record before application. The confused history map creation unit 34 sets the application date “20030420” of the record searched in step S63 to the application date 174 of the added record before application.
[0165]
The confusion history map creation unit 34 sets “Low” to the registration date 175 of the added record before application. In addition, the confusing history map creation unit 34 sets “unknown” to the point number 1 and the point number 2 of the added record before application. In addition, the confusion history map creation unit 34 assumes that the other data items in the added record before application are the same as the record searched in step S82.
[0166]
Proceeding to step S87, as shown in FIG. 74, the confused history map creation unit 34 stores the reception ID “A001” of the record retrieved in step S63 as key information in the registry map graphic DB 43 in step S56. The recorded record 181 is searched. Then, the confusion history map creation unit 34 adds the retrieved record 181 to the registry map graphic DB 182 and ends the process.
[0167]
When the geodetic survey map and the geodetic survey data have been submitted in the past, the registry map attribute DB 42 of FIG. 75 and the registry map map DB 43 representing the coordinate information of FIG. , The registry map graphic DB 43 representing the connection information in FIG. 77 and the map reception DB 41 in FIG. 78 can be created.
[0168]
In addition, when the geodetic survey map and the geodetic survey data have not been submitted in the past, the registry map representing the coordinate information of the registry map attribute DB 42 in FIG. 79 and the coordinate information in FIG. The graphic DB 43, the registry map graphic DB 43 representing the connection information of FIG. 81, and the map reception DB 41 of FIG. 82 can be created.
[0169]
Therefore, according to the system 1 that operates the real estate registration application of FIG. 1, it is possible to provide a map of the transfer history of the map data in which the map mess has been resolved, thereby improving the convenience for the user in the map confused area. It will be possible to provide uniform services nationwide.
[0170]
In addition, according to the system 1 that operates the real estate registration application in FIG. 1, it is possible to support the determination of the map confused area performed by the staff of the Legal Affairs Bureau, so that the real estate registration business can be smoothly operated.
[0171]
The present invention may have the following configurations as described below.
(Supplementary Note 1) A map data editing apparatus that accepts a request for map data and edits the map data in response to the request,
A request storage means for storing a request for map data prohibited from editing;
When the prohibition on editing the map data is lifted, the request for the map data received while the editing is prohibited is read from the request storage means, and the editing is prohibited from the request and the current map data. A history creation means for creating a history of map data in response to a request for the map data received in between;
A map data editing apparatus comprising:
(Supplementary note 2) The map data request and the map data read from the map data storage means are compared, and according to the ratio that the target area of the request is not included in the map data read from the map data storage means The map data editing apparatus according to appendix 1, further comprising editing prohibition notification means for notifying the necessity of prohibition of editing data.
(Additional remark 3) When the request | requirement with respect to the said map data is a pen, the said log | history creation means creates the log | history of map data by writing the target area | region included in the current map data, and the said map The map data editing device according to appendix 1 or 2, wherein when the request for data is a handwriting, the handwritten target area included in the current map data is divided to create a history of the map data .
(Additional remark 4) The said log | history creation means produces the log | history of the map data one generation before the said one generation from the log | history of the map data of one generation in order, The map data editing apparatus of Additional remark 3 characterized by the above-mentioned .
(Supplementary note 5) The map data editing according to any one of supplementary notes 1 to 4, wherein the request for map data for which editing is prohibited is a request for a map confused area where the map data and the local situation are different. apparatus.
(Supplementary Note 6) A map data editing method for a map data editing apparatus that accepts a request for map data and edits the map data in response to the request,
Storing a request for map data prohibited from editing in a request storage means;
When the prohibition on editing the map data is lifted, the request for the map data received while the editing is prohibited is read from the request storage means, and the editing is prohibited from the request and the current map data. Creating a history of map data in response to a request for the map data received in-between;
A map data editing method comprising:
[0172]
【The invention's effect】
As described above, according to the present invention, it is possible to provide a map data editing apparatus and a map data editing method that can uniformly provide a history of map data and can smoothly operate a map data editing job.
[0173]
[Brief description of the drawings]
FIG. 1 is a configuration diagram of an example of a system for operating a real estate registration application.
FIG. 2 is a configuration diagram of an example of a computer that implements a map system.
FIG. 3 is a functional configuration diagram of an example of a map system.
FIG. 4 is a flowchart of an example of processing of a map system.
FIG. 5 is a configuration diagram of an example of a map reception DB.
FIG. 6 is a configuration diagram of an example of a registry office map attribute DB.
FIG. 7 is a configuration diagram of an example of a map confusion state management DB.
FIG. 8 is a configuration diagram of an example of a registry map graphic DB representing coordinate information.
FIG. 9 is a configuration diagram of an example of a registry map graphic DB representing connection information.
FIG. 10 is a flowchart illustrating an example of a process when a map mess is resolved.
FIG. 11 is a flowchart (1/2) of an example of detailed processing of the map system;
FIG. 12 is a flowchart (2/2) of an example of detailed processing of the map system.
FIG. 13 is a block diagram showing an example of application contents accepted by the map system.
FIG. 14 is a configuration diagram of an example of a map reception DB in which application contents from a registration system are stored.
FIG. 15 is a configuration diagram of an example of a registry office map attribute DB.
FIG. 16 is an explanatory diagram illustrating an example of processing for associating application contents with a map;
FIG. 17 is a configuration diagram of an example of a map confusion state management DB.
FIG. 18 is an explanatory diagram of an example of a process for automatically associating a property registered in a registry map attribute DB with an application content.
FIG. 19 is an image diagram of an example of a property identification screen.
FIG. 20 is an explanatory diagram illustrating an example of processing in a case where the association between the property registered in the registry map attribute DB using the property specifying screen and the application content is successful.
FIG. 21 is an explanatory diagram illustrating an example of processing in a case where the association between the property registered in the registry map attribute DB and the application content using the property specifying screen fails.
FIG. 22 is an image diagram of an example of a map confusion notification process.
FIG. 23 is a flowchart of an example of a map confusion application history creation process;
FIG. 24 is an image diagram showing an example of a local situation in a map confused area.
FIG. 25 is an image diagram showing a map confused area managed by the map system.
FIG. 26 is a configuration diagram of an example of a registry map graphic DB representing coordinate information.
FIG. 27 is a configuration diagram of an example of a registry map graphic DB representing connection information.
FIG. 28 is a block diagram of an example of a registry map attribute DB.
FIG. 29 is an image diagram of an example of a land survey map.
FIG. 30 is an image diagram of an example of land survey data.
FIG. 31 is an explanatory diagram for describing processing of steps S52 and S53;
FIG. 32 is a configuration diagram of an example of a work table used in a process related to writing.
FIG. 33 is a configuration diagram of an example of a record read from a predetermined table that manages the geodetic survey map and the geodetic survey map data.
FIG. 34 is an explanatory diagram for describing processing of steps S57 and S58.
FIG. 35 is a configuration diagram of an example of an entry item DB included in the registration system.
FIG. 36 is an explanatory diagram for describing the process in step S56;
FIG. 37 is a flowchart of an example of processing that is performed after map confusion is resolved.
FIG. 38 is an image diagram of an example of an Article 17 map in which map confusion is resolved.
FIG. 39 is a configuration diagram of an example of a registry map graphic DB representing coordinate information.
FIG. 40 is a configuration diagram of an example of a registry map graphic DB representing connection information.
FIG. 41 is a configuration diagram of an example of a registry office map attribute DB.
FIG. 42 is a flowchart of an example of map data deletion processing of a map in a map confused area.
FIG. 43 is a block diagram of an example of a map reception DB.
FIG. 44 is a flowchart of an example of a history map creation process for a stroke application.
FIG. 45 is a block diagram showing an example of a record searched in step S63.
FIG. 46 is a block diagram of an example of a registry map attribute DB.
FIG. 47 is a configuration diagram of an example of a registry map attribute DB to which a created pre-application record is added.
FIG. 48 is a configuration diagram of an example of a registry map graphic DB representing connection information.
FIG. 49 is a configuration diagram of an example of a registry map graphic DB to which a created record before application is added.
FIG. 50 is an image diagram illustrating an example of a process of deleting a stroke line.
FIG. 51 is a configuration diagram of an example of a record searched in the process of step S75.
FIG. 52 is an image diagram of an example of a process for deleting excess connection information when a new point is “ON”.
FIG. 53 is an image diagram of an example of a process for deleting excess connection information when a new point is blank.
FIG. 54 is an image diagram of an example of a process for deleting excess connection information when a new point is “ON”.
FIG. 55 is a configuration diagram of an example of a registry map graphic DB to which a created record before application is added.
FIG. 56 is an image diagram of an example of a process in step S77.
FIG. 57 is a block diagram of an example of a registry map attribute DB.
FIG. 58 is a configuration diagram of an example of a registry map graphic DB representing coordinate information.
FIG. 59 is a block diagram of an example of a registry map graphic DB representing connection information.
FIG. 60 is a block diagram of an example of a map reception DB.
FIG. 61 is a flowchart of an example of a history map creation process for a stroke application.
FIG. 62 is an image diagram of an example of an Article 17 map in which map confusion is resolved.
FIG. 63 is a configuration diagram of an example of a registry map graphic DB representing coordinate information.
FIG. 64 is a configuration diagram of an example of a registry map graphic DB representing connection information.
FIG. 65 is a block diagram of an example of a registry map attribute DB.
FIG. 66 is a block diagram showing an example of a record searched in step S63.
FIG. 67 is a block diagram of an example of a registry map attribute DB.
FIG. 68 is a configuration diagram of an example of a registry map attribute DB to which a created record before application is added.
FIG. 69 is a block diagram of an example of a registry map graphic DB representing connection information.
FIG. 70 is a configuration diagram of an example of a registry map graphic DB to which a created pre-application record is added.
FIG. 71 is an image diagram of an example of a process in step S85.
FIG. 72 is an image diagram of an example of a screen output when a change history map cannot be created.
FIG. 73 is a configuration diagram of an example of a registry map graphic DB to which a created pre-application record is added.
FIG. 74 is an image diagram of an example of a process in step S87.
75 is a block diagram of an example of a registry office map attribute DB. FIG.
FIG. 76 is a configuration diagram of an example of a registry map graphic DB representing coordinate information.
77 is a configuration diagram of an example of a registry map graphic DB representing connection information. FIG.
78 is a block diagram of an example of a map reception DB. FIG.
FIG. 79 is a block diagram of an example of a registry map attribute DB.
FIG. 80 is a configuration diagram of an example of a registry map graphic DB representing coordinate information.
FIG. 81 is a configuration diagram of an example of a registry map graphic DB representing connection information.
82 is a block diagram of an example of a map reception DB. FIG.
[Explanation of symbols]
1 system
10 Application reception system
11 Registration system
12 Map system
13a-13n terminal
14 network
21 Input device
22 Display device
23 Drive device
24 recording media
25 Auxiliary storage
26 Memory device
27 Arithmetic processing unit
28 Interface device
29 Database (DB)
31 Map data processing section
32 Map confusion area judgment part
33 Confused Application Management Department
34 Confusion history map creation part
41 Map reception DB
42 Registry map attribute DB
43 Registry Map Graphic DB
44 Map confusion state management DB
B bus

Claims (5)

A map data editing device that accepts a request for map data and edits the map data in response to the request,
A request storage means for storing a request for map data prohibited from editing;
When the prohibition on editing the map data is lifted, the request for the map data received while the editing is prohibited is read from the request storage means, and the editing is prohibited from the request and the current map data. A map data editing apparatus, comprising: a history creation unit that creates a history of map data in response to a request for the map data received in between. The request for map data is compared with the map data read from the map data storage means, and the map data is edited according to the ratio that the target area of the request is not included in the map data read from the map data storage means. 2. The map data editing apparatus according to claim 1, further comprising editing prohibition notification means for notifying the necessity of prohibition. In the case where the request for the map data is a pen, the history creating means creates a history of the map data by writing the target area included in the current map data, while the request for the map data is The map data editing apparatus according to claim 1 or 2, wherein in the case of writing, the map data history is created by dividing the handwritten target area included in the current map data. 4. The map data editing apparatus according to claim 1, wherein the request for map data for which editing is prohibited is a request for a map confused area where map data and a local situation are different. A map data editing method of a map data editing device that accepts a request for map data and edits the map data in response to the request,
Storing a request for map data prohibited from editing in a request storage means;
When the prohibition on editing the map data is lifted, the request for the map data received while the editing is prohibited is read from the request storage means, and the editing is prohibited from the request and the current map data. A map data editing method comprising: creating a history of map data in response to a request for the map data received in between.

Images