Approach path data generation method, approach path data generation apparatus, and approach path data generation program

Abstract

To generate an approach path satisfying a design specification value or an approach path conforming to shape data set by a user, between a road and an access destination, in accordance with the shape or arrangement of other constructions.SOLUTION: An approach path data generation method includes: a construction data acquisition step (S41) of acquiring a skeleton line and shape data of a construction including a road; a position information acquisition step (S42) of acquiring position information of the construction; an approach path skeleton line data acquisition step (S43) of acquiring a skeleton line of an approach path from the road to an access destination, the skeleton line being drawn by a user; a shape data acquisition step (S45) of acquiring shape data that specifies the approach path, the shape data being input by the user; and a model data generation step (S46) of generating model data of the approach path, using the skeleton line and the shape data of the approach path.SELECTED DRAWING: Figure 24

Description

[Technical field]

[0001] The present invention relates to an approach road data generating method, an approach road data generating device, and an approach road data generating program. [Background technology]

[0002] In the civil engineering industry, the mainstream 3D model design is direct modeling, in which a frame that constitutes a mesh is generated first, and then a mesh is generated within that frame to create a 3D model. In direct modeling, frames are independent of each other, so for example, when modifying the elevation of a structure, all related frames must be manually modified and the mesh must be regenerated, which is quite time-consuming. In addition, designing 3D models using direct modeling has problems such as the complicated drawing procedures that make it difficult for beginners to undertake, or the time it takes to improve one's skills.

[0003] On the other hand, parametric modeling is a method of generating a three-dimensional model by expressing the arrangement of a structure with a skeleton line and assigning parameters that define the three-dimensional shape to the skeleton line. In parametric modeling, the shape of the three-dimensional model can be changed by changing the parameters, and the position of the three-dimensional model can be changed by changing the position of the skeleton line. With this method, the position and shape of the three-dimensional model can be easily corrected simply by changing the position or parameters of the skeleton line. As a design technique for a three-dimensional model using such parametric modeling, for example, a CAD system that generates a three-dimensional shape of a target object using a two-dimensional drawing, as described in Patent Document 1, has been known in the past. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 09-022421 Summary of the Invention [Problem to be solved by the invention]

[0005] However, parametric modeling techniques do not recognize the shape and layout of structures, and therefore cannot generate a model of an access road between structures that satisfies the design standards according to the shape and layout of these structures. For example, when generating an access road between a road and a field, various conditions must be taken into consideration in order to generate the access road so that the longitudinal gradient is smaller than a predetermined limit value.

[0006] One aspect of the present invention aims to realize a technology that generates an approach road between a road and an access destination that meets design standards or that conforms to shape data set by a user, depending on the shapes and placement of other structures. [Means for solving the problem]

[0007] In order to solve the above problems, an approach road data generation method according to one embodiment of the present invention includes a structure data acquisition step of acquiring skeleton lines and shape data of structures including roads, a position information acquisition step of acquiring position information of the structures, an approach road skeleton line data acquisition step of acquiring a skeleton line of an approach road from the road to the approach destination drawn by a user, a shape data acquisition step of acquiring shape data defining the approach road input by a user, and a model data generation step of generating model data of the approach road using the skeleton lines and shape data of the approach road.

[0008] In addition, an approach road data generation device according to one embodiment of the present invention includes a structure data acquisition unit that acquires skeleton lines and shape data of structures including roads, a position information acquisition unit that acquires position information of the structures, an approach road skeleton line data acquisition unit that acquires a skeleton line of an approach road from the road to the approach destination drawn by a user, a shape data acquisition unit that acquires shape data input by a user that defines the approach road, and a model data generation unit that generates model data of the approach road using the skeleton line and shape data of the approach road.

[0009] In addition, an approach road data generation program according to one embodiment of the present invention is a program for causing a computer to function as the approach road data generation device, and is a program for causing a computer to function as the structure data acquisition unit, the position information acquisition unit, the approach road data acquisition unit, the shape data acquisition unit and the model data generation unit.

[0010] The approach road data generating device according to each aspect of the present invention may be realized by a computer. In this case, the control program of the approach road data generating device, which causes a computer to operate as each part (software element) of the approach road data generating device, thereby realizing the approach road data generating device on a computer, and the computer-readable recording medium on which the control program is recorded, also fall within the scope of the present invention. Effect of the Invention

[0011] According to one aspect of the present invention, an approach road that meets design standards or that conforms to shape data set by the user can be generated between a road and an approach destination, depending on the shape and placement of other structures. [Brief description of the drawings]

[0012] [Figure 1] 1 is a diagram showing an example of a two-dimensional model based on two-dimensional CAD data used in the earth's surface data generation method according to an embodiment of the present invention; [Diagram 2]1 is a block diagram showing a functional configuration of an earth's surface data generating device used in an earth's surface data generating method according to a first embodiment of the present invention. [Diagram 3] 4 is a flowchart showing the flow of a ground surface data generation process executed by the device. [Figure 4] FIG. 2 is a diagram showing an example of a shape data input screen displayed by the device. [Diagram 5] 11 is a diagram illustrating an example of a process for generating a shared connection line executed by the device. [Figure 6] FIG. 2 is a diagram showing an example of an intersection model generated by the device. [Figure 7] FIG. 2 is a diagram showing an example of a pairing search performed by the device. [Figure 8] FIG. 2 is a diagram showing an example of pairing search using the Kushi-dango method performed by the device. [Figure 9] FIG. 2 is a diagram showing an example of pairing search using the Kushi-dango method performed by the device. [Figure 10] FIG. 2 is a diagram showing an example of pairing search using the Kushi-dango method performed by the device. [Figure 11] FIG. 2 is a diagram showing an example of pairing search using the Kushi-dango method performed by the device. [Figure 12] FIG. 2 is a diagram showing an example of pairing search using the Kushi-dango method performed by the device. [Figure 13] FIG. 2 is a diagram showing an example of a switching line generated by the device. [Figure 14] FIG. 2 is a diagram showing an example of a three-dimensional model based on three-dimensional CAD data generated by the device. [Figure 15] FIG. 2 is a diagram showing an example of a method for measuring the slope of a slope performed by the device. [Figure 16] 11A to 11C are diagrams illustrating an example of a method for generating a reference line executed by the apparatus. [Figure 17] FIG. 11 is a block diagram showing the functional configuration of a device for generating mesh data for design and construction used in a method for generating mesh data for design and construction according to a second embodiment of the present invention. [Figure 18]4 is a flowchart showing the process of generating mesh data for design and construction performed by the device. [Figure 19] FIG. 11 is a diagram explaining the shape data of a drainage channel required for generating mesh data for design and construction. [Figure 20] FIG. 13 is a diagram for explaining shape data at the road construction stage that is required for generating mesh data for design and construction. [Figure 21] FIG. 13 is a diagram showing an example of a shape data input screen displayed by the device during the drainage channel construction stage. [Figure 22] This is a schematic diagram showing an example of a screen on which mesh data for the base surface, cultivated surface, and ridges used in field leveling work is generated. [Diagram 23] FIG. 11 is a block diagram showing a configuration of an approach road data generating device according to a third embodiment of the present invention. [Figure 24] 11 is a flowchart showing the flow of an approach road data generating method executed by an approach road data generating device according to a third embodiment. [Diagram 25] 1 is a flowchart showing the flow of a model data generating method. [Figure 26] 11 is a schematic diagram showing an example of positions indicated by shape data when an approach road is generated from a road; FIG. [Figure 27] FIG. 13 is a schematic diagram showing an input screen for shape data when generating an approach road from a road. [Figure 28] 13 is a schematic diagram showing the position indicated by the shape data when a horizontal section is provided between the cross slope elimination section and the slope section. FIG. [Figure 29] 11 is a schematic diagram for explaining a position indicated by shape parameters of a corner cutting portion; FIG. [Diagram 30] FIG. 13 is a detailed view showing the positions of shape data No. 3 to No. 6. [Diagram 31] FIG. 13 is a schematic diagram showing an example of a method for a user to draw an access road to a field. [Diagram 32] FIG. 2 is a schematic diagram showing skeleton line information of an approach road; [Diagram 33] FIG. 4 is a schematic diagram showing a method in which a determination unit determines whether an access road is an access road that crosses two fields. [Diagram 34] FIG. 1 is a schematic diagram showing a method for generating a cross slope eliminating section. [Diagram 35] FIG. 1 is a schematic diagram showing a method for generating a cross slope eliminating section. [Diagram 36] FIG. 1 is a schematic diagram showing a method for generating a cross slope eliminating section. [Figure 37] FIG. 1 is a schematic diagram showing a method for generating a cross slope eliminating section. [Figure 38] FIG. 13 is a schematic diagram showing a method for generating a horizontal section. [Figure 39] FIG. 13 is a schematic diagram showing a method for generating a horizontal section. [Diagram 40] FIG. 13 is a schematic diagram showing a method for generating a slope section. [Diagram 41] FIG. 13 is a schematic diagram showing a method for generating a slope section. [Diagram 42] FIG. 13 is a schematic diagram showing a method for generating a corner cutting portion. [Diagram 43] FIG. 13 is a schematic diagram showing a method of generating an access road when there is an obstacle between a road and a field. [Diagram 44] FIG. 13 is a schematic diagram showing a method of generating an access road when there is an obstacle between a road and a field. [Diagram 45] 13 is a flowchart showing what subsequent processing is performed depending on whether or not the access road is an access road that crosses two fields. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] [Embodiment 1] Hereinafter, one embodiment of the present invention will be described in detail.

[0014] [2D CAD data] First, we will explain two-dimensional CAD data, which is one type of CAD data read by the earth surface data generating device 1 described later. The two-dimensional CAD data used here is composed of multiple layers. Each layer has one or more polylines or polygons that constitute structures drawn. A "structure" includes one or more of roads, farm fields, irrigation channels, drainage channels, access roads from roads to farm fields, parking lots, housing sites, levees, concrete retaining walls, tunnels, pipelines, railway embankments, breakwaters, revetments, and seawalls. One layer may include only one type of structure.

[0015] (Layer) A layer name is given to each layer. In the two-dimensional CAD data according to this embodiment, the plan, work type, and ID are used as layer names. In the "plan", "current state" or "plan" is written. "Current state" means the current (before construction) state of the structure. "Plan" means the state after the completion of the structure. Note that there may be multiple plans (for example, plan 1, plan 2, plan 3, etc.) for one structure. "Work type" is the name of the structure (road, waterway, etc.). "ID" is information for identifying one polyline or polygon that constitutes the structure indicated by the work type. Therefore, the layer name of the two-dimensional CAD data according to this embodiment is written, for example, as "Plan_Road_ID1". The plan, work type, and ID written as the layer name are treated as attribute data in the earth surface data generation device 1 described later.

[0016] (Polyline / Polygon) Among structures, roads, irrigation channels, drainage channels, etc. are drawn using polylines. The order in which the polylines were drawn (the direction in which the lines of the polylines were drawn, and the starting point and the end point) is linked to the polylines. As a result, when the earth surface data generating device 1 reads this 2D CAD data, the polylines become directed polylines, and it becomes possible to distinguish between the right and left sides of the polylines. Meanwhile, among structures, structures that are surrounded by boundaries (farm fields, parking lots, housing sites, etc.) are drawn as polygons. Polygons are basically drawn in a single stroke in a clockwise or counterclockwise direction. However, information indicating which direction the polygons were drawn in is not linked to the polygons (it is not possible to determine the order in which the polygons were drawn). This is because the earth surface data generating device 1 has a function of performing a process of unifying the order of directions of the polygons that it reads.

[0017] (Elevation Identifier) Character information can be written on each layer of the two-dimensional CAD data. The two-dimensional CAD data used here has an elevation identifier and a number written on each layer. The elevation identifier is a symbol indicating that the elevation at the point on the polyline or polygon closest to the position (center point) where it is written is represented by the number written together. One or more pairs of an elevation identifier and a number are written for one polyline. The elevation identifier according to this embodiment is a figure such as a circle or a double circle, and indicates the elevation of the center point of the figure. The shape of the elevation identifier is not limited to a circle or a double circle. The figure may be a square or an equilateral triangle, etc., as long as the center point is easily determined. In addition, when other elevation values ​​are densely written and it is difficult to write the elevation value near the figure, a leader line is also used as the elevation identifier. In this case, when the leader line is also used, it is necessary to distinguish between the skeleton line and the leader line. In the two-dimensional CAD data according to this embodiment, the base end of the leader line is drawn so as to be inside the figure. Then, the elevation value is written near the tip of the leader line.

[0018] Furthermore, there are two types of lines handled by CAD: polylines and line segments. A polyline is a line that connects two or more points from a starting point to an end point, while a line segment is a straight line that always has only two points, a starting point and an end point, and they are each handled as having different attributes. By utilizing this characteristic, in this embodiment, skeleton lines are drawn as polylines, and leader lines are drawn as line segments. In addition, it is also possible to use the color information of the lines. For example, if the skeleton lines are specified as blue and the leader lines are specified as red, then when reading this data, it is possible to distinguish between the skeleton lines and the leader lines.

[0019] The number indicating the elevation is written near (within a specified distance from) the center point of the elevation identifier, or near the end point of the lead line. The number indicating the elevation of a structure represented by a polygon is written inside the polygon. In this case, particularly when the structure is a rice paddy, one elevation identifier and number combination is sufficient since the elevation within the paddy is uniform. Note that by writing such an elevation identifier and number combination in the two-dimensional CAD data, the earth surface data generation device 1 becomes able to obtain elevation information from two-dimensional CAD data that cannot have three-dimensional information.

[0020] If the structure is a paddy field, ridges are required around the periphery to store water on the surface of the field, but no elevation identifier or number is written on the ridges. This is because the earth surface data generating device 1 automatically determines the elevation of the ridges from the elevation of the paddy field surface.

[0021] (Cross-identifier) Two roads or waterways that extend in different directions may intersect. An intersection may be a real intersection that actually intersects with another, or a multi-level intersection that does not actually intersect with another (one of the roads or waterways becomes an underpass). Therefore, in the two-dimensional CAD data used here, an intersection identifier is described as necessary at the intersection of each road and each waterway described in each layer. The intersection identifier is a symbol indicating that the intersection is a multi-level intersection. The intersection identifier according to this embodiment is a figure with a shape (e.g., a square, etc.) different from the elevation identifier. The intersection identifier may be a symbol indicating that the intersection is a real intersection. By describing such an intersection identifier in the two-dimensional CAD data, the ground surface data generation device 1 can obtain information on whether the intersection is a real intersection or a multi-level intersection from the two-dimensional CAD data that cannot have three-dimensional information.

[0022] (Other Identifiers) In addition, among multiple waterways, there are cases where some share their respective end points and become a single waterway. In these cases, the elevations of each waterway may differ. Therefore, the 2D CAD data used here includes identifiers indicating that a manhole will be installed at the connection points (where the elevations are different) of each waterway listed on each layer. In this case, a drop work is required to install manholes at different elevations.

[0023] By overlaying layers containing polylines, polygons, etc. according to the above rules, a 2D model of the structure to be constructed, as shown in Figure 1, is obtained. Note that some parts have been omitted in Figure 1 to avoid complexity. For example, the elevation identifier mentioned above exists near the elevation value, but is not shown in Figure 1. Also, while information from multiple layers is overlaid in Figure 1, since the type of numerical value is determined on each layer, it is sufficient that an identifier is written so that the type of numerical value can be determined on each layer.

[0024] [Embodiments of Earth surface data generation method, device, and program] Next, a ground surface data generation method, device, and program will be described. The ground surface data generation device 1 described here is used when implementing the ground surface data generation method according to an embodiment of the present invention. The ground surface data generation method is a method for generating three-dimensional ground surface data between a plurality of structures. As shown in FIG. 2, the ground surface data generation device 1 includes an input unit 11, an operation unit 12, an output unit 13, a storage unit 14, and a control unit 15.

[0025] (Input section) Two-dimensional CAD data or three-dimensional CAD data is input to the input unit 11. The input unit 11 is composed of, for example, a terminal to which a cable connected to a device in which the data is stored is connected, a communication unit that communicates with the device in which the data is stored by wire or wirelessly, or a drive that reads a medium in which the data is stored.

[0026] [Operation unit] The operation unit 12 receives various input operations by a user and is configured with a keyboard, a mouse, a touch panel, or a dedicated device.

[0027] (Output section) The output unit 13 according to this embodiment outputs the generated 3D model. The output unit 13 is composed of, for example, a terminal to which a cable connected to a monitor is connected, a communication unit that communicates with other devices by wire or wirelessly, or a drive that writes data of the 3D model to a medium. The output unit 13 may be the monitor itself that displays the 3D model based on the data.

[0028] (Storage part) The storage unit 14 stores an earth surface data generation program 141. The earth surface data generation program 141 describes the flow of the earth surface data generation process executed by the control unit 15. The storage unit 14 according to this embodiment is configured with a semiconductor memory or a hard disk. Note that when the earth surface data generation program is not required (for example, when the control unit 15 performs all of the various calculations described below using logic circuits), the earth surface data generation device 1 does not need to be provided with the storage unit 14.

[0029] (Control unit) The control unit 15 includes an acquisition unit 151, a second acquisition unit 152, an interpolation unit 153, a global order setting unit 154, a determination unit 155, a connection line generation unit 156, a shared connection line generation unit 157, a pairing unit 158, a pair information setting unit 159, a switching line generation unit 160, a surface generation unit 161, a warning information extraction unit 162, a data output processing unit 163, and a change unit 164. The control unit 15 according to the present embodiment is configured with a processor. The control unit 15 executes a ground surface data generation process as shown in FIG. 3 according to the ground surface data generation program stored in the storage unit 14. The ground surface data generation process includes an acquisition step S1, a connection line generation step S6, a shared connection line generation step S7, a pairing step S8, and a surface generation step S11. The earth surface data generation process may further include a second acquisition step S2, an interpolation step S3, a global order setting step S4, a determination step S5, a pair information setting step S9, a switching line generation step S10, a warning information extraction step S12, a data output step S13, and a change step S14. Each step in the earth surface data generation process corresponds to each step included in the earth surface data generation method according to this embodiment.

[0030] (1. Acquisition step) In the first acquisition step S1, the acquisition unit 151 acquires skeleton line data. The skeleton line data is data that defines the skeleton line L1. The skeleton line is a line that is a reference line of a structure, and is defined as, for example, the center line of the road in the case of a road, and the center line of the ridge in the case of a rice field. In the case of a waterway, it is, for example, the center line of the bottom surface of the waterway. The skeleton line data is data that defines the skeleton line, and includes position data, elevation data, ID, type, etc. Each skeleton line L1 is made up of a two-dimensional or three-dimensional oriented polyline or oriented polygon having a starting point and an end point. The skeleton line data according to this embodiment is vector data included in two-dimensional CAD data or three-dimensional CAD data. When skeleton line data including a polygon (annular skeleton line L1) is acquired, the acquisition unit 151 analyzes the starting point and the end point of the polygon and corrects the winding order to a predetermined direction. This unifies the winding order of the acquired polygon. Then, by unifying the winding order, the control unit 15 becomes able to distinguish the inside and outside of the polygon by calculating the cross product.

[0031] In the acquisition step S1, the acquisition unit 151 acquires discrete elevation data of the structure. Specifically, the acquisition unit 151 identifies an elevation identifier written on a layer. Then, the acquisition unit 151 acquires a skeleton line of the structure recorded on the same layer, and an elevation identifier (predetermined mark) and a number (elevation data) written at a predetermined position on the layer. For example, the elevation identifier may be placed on the skeleton line. Then, the acquisition unit 151 judges whether or not a leader line is drawn on the identified elevation identifier. Here, if it is judged that a leader line is not drawn, the acquisition unit 151 records the number closest to the elevation identifier as an elevation value, linked to the position of the elevation identifier. On the other hand, if it is judged that a leader line is drawn on the elevation identifier, the acquisition unit 151 records the number written closest to the tip of the leader line as an elevation value, linked to the position of the elevation identifier. Note that, if the skeleton line data to be acquired is included in the three-dimensional CAD data, the elevation data is included in the skeleton line data, so that the acquisition unit 151 only needs to acquire the skeleton line data.

[0032] In the acquisition step S1, the acquisition unit 151 acquires intersection data. Specifically, the acquisition unit 151 identifies intersection identifiers written on roads or waterways on the layer. Then, the acquisition unit 151 records an intersection with an intersection identifier written thereon as a multilevel intersection. The acquisition unit 151 records an intersection without an intersection identifier written thereon as an actual intersection.

[0033] In the acquisition step S1, when drawing the skeleton line L1 of the intersection, the acquisition unit 151 may draw the section that will be an underpass with a broken line. In that case, it is preferable that the acquisition unit 151 draws the broken line section longer than the actual section, taking into consideration the case where the generated three-dimensional model is corrected.

[0034] In addition, among the multiple skeleton lines L1, there may be some that share their respective end points and become one skeleton line L1. For example, when the structure is a road (waterway), a narrow road (waterway) and a wide road (waterway) are connected to each other. An intersection generally refers to a place where two or more skeleton lines L1 intersect, but the acquisition unit 151 according to the present embodiment recognizes a case where the respective end points are shared as a two-way intersection. The reason for having the acquisition unit 151 recognize the intersection as a two-way intersection is to make the intersection (end point) have the same elevation. In other words, when it is not possible to recognize it as a two-way intersection, in the case of roads, the elevation at the end points is different, and there is a risk that a road for which an intersection is not generated will be generated. Note that the earth surface data generation device 1 may be provided with an intersection generation unit (not shown) that generates an intersection model for a multi-way intersection, including a two-way intersection. An ID is assigned to each intersection, and a corner cutting length, etc. may be input as a shape parameter for each ID, so that the intersection shape can be changed based on the shape parameter.

[0035] Furthermore, when generating oriented polygons for two fields that share a ridge, it is necessary to draw oriented polygons for each field. However, in two-dimensional CAD data, the ridge between the two fields is drawn with one skeleton line L1. For this reason, when generating the skeleton line L1 from the two-dimensional CAD data while tracing the polyline of the field, the acquisition unit 151 according to this embodiment selects a polyline that extends in a predetermined direction (right or left) toward the traveling direction when it approaches an intersection where the polyline of each field and the polyline of the ridge intersect, and extends the skeleton line L1. This makes it possible to generate the skeleton line L1 (oriented polygon) for each field, even if topographical data for two fields that share a ridge is acquired. Alternatively, one ridge between two fields may be assigned to each field, and each of the two ridges may be drawn using two skeleton lines L1.

[0036] In the earth surface data generation process according to this embodiment, in the acquisition step S1, the acquisition unit 151 further acquires attribute data of the structure. The attribute data of the structure includes at least one of the layer name, the construction type of the structure, and the ID of the structure. In two-dimensional CAD data, attribute data (ID, name, etc.) cannot be directly assigned to the skeleton line L1. For this reason, in the two-dimensional CAD data used here, each skeleton line L1 is arranged on a different layer. Then, the acquisition unit 151 links the layer name (attribute data of each skeleton line L1) assigned to each layer to the skeleton line L1 described on each layer. When multiple skeleton lines are described on the same layer, the acquisition unit 151 links the same attribute data to each of the multiple skeleton lines L1.

[0037] The acquisition unit 151 may be configured to acquire three-dimensional point cloud data and generate skeleton line data and elevation data of a structure from a plurality of coordinate values ​​(x, y, z) included in the three-dimensional point cloud data. The three-dimensional point cloud data is survey data obtained based on photos of the ground surface taken by a UAV (Unmanned Aerial Vehicle), an aircraft, an artificial satellite, etc., and reflected laser light from the ground surface collected by these. In this case, the acquisition unit 151 first reproduces a point cloud based on the acquired three-dimensional point cloud data in a three-dimensional space. Then, the acquisition unit 151 recognizes a structure from the reproduced point cloud, and draws a skeleton line L1 of the structure on a layer to which a corresponding layer name (plan, type of work, and ID) is assigned. The recognition of the structure and the drawing of the skeleton line L1 may be performed by a user.

[0038] (2. Second acquisition step) In the earth surface data generating method according to this embodiment, after acquiring the skeleton line data and the elevation data and before executing the connection line generating step S6 described later, the process proceeds to a second acquisition step S2. In the second acquisition step S2, the second acquisition unit 152 acquires shape data of the structure. The shape data is parameters that define the shape of the structure. In this embodiment, the structure is represented by a parametric model. In other words, the shape data is parameter data that defines the shape of the parametric model. The second acquisition unit 152 may further acquire material data and ground data. The material data is data that indicates the material of the structure, the presence or absence of vegetation, etc. The ground data is data related to the base layer, the cultivated layer, etc.

[0039] For example, if the structure is a road, the shape data includes basic parameters, slope parameters, ground surface parameters, and berm parameters. The basic parameters include the effective width (distance from the skeleton line L1 to the edge of the road surface), left shoulder (distance from the skeleton line L1 to the left berm), right shoulder (distance from the skeleton line L1 to the right berm), width height, and roadbed surface height. The material parameters include the material of the road and the presence or absence of vegetation on the slope. The slope parameters include the gradient of the right slope and the gradient of the left slope. The ground surface parameters include the width of the ground surface, etc. The berm parameters include the presence or absence of berms on the slope, and if there are berms, the number of berms installed, the installation height of each berm, and the width of each berm.

[0040] If the structure is an irrigation canal, the shape data includes basic parameters, slope parameters, ground surface parameters, and berm parameters. The basic parameters include flume width, flume height, foundation concrete width, foundation concrete height, bed mortar height, left irrigation canal shoulder, and right irrigation canal shoulder. The slope parameters include the gradient of the right side slope and the gradient of the left side slope. The ground surface parameters include the width of the ground surface, etc. The berm parameters include the presence or absence of berms on the slope, and if there are berms, the number of berms installed, the installation height of each berm, and the width of each berm.

[0041] The second acquisition unit 152 according to the present embodiment acquires shape data from the operation unit 12 when the user performs an input operation on the operation unit 12 while an input screen such as that shown in FIG. 4 is displayed. The second acquisition unit 152 then links the acquired shape data to the corresponding skeleton line. When multiple skeleton lines are drawn on the same layer, the second acquisition unit 152 links the same shape data to each of the multiple skeleton lines. When an input operation is performed on a real intersection, the second acquisition unit 152 acquires shape data of an intersection model. Then, regardless of whether each skeleton line constituting the real intersection is drawn on the same layer or not, each skeleton line is linked to shape data that defines the shape of the intersection. However, for the road width and the like among the shape data, the shape data linked to the original skeleton line L1 is taken over. When the structure is a paddy field, settings related to the ridges can be made on the input screen. Therefore, when the structure is a paddy field, the second acquisition unit 152 acquires information on the ridges in addition to the shape data. This second acquisition step S is repeated until the second acquisition unit 152 acquires shape data for all skeleton lines L1.

[0042] The shape data may not be obtained by inputting the shape data into the operation unit 12, but may be read from another device, a recording medium, etc. (obtained by previously accepted inputting the shape data and outputted to another device, a recording medium, etc.). In this way, the user can be spared the trouble of inputting the shape data in the second acquisition step S2. In this case, the shape data may be obtained together with the skeleton line data and the elevation data in the acquisition step S1. In this case, the second acquisition step is unnecessary.

[0043] (3. Interpolation step) In the earth surface data generating method according to the present embodiment, after generating the shared connection line L3, the process proceeds to an interpolation step S3 as shown in FIG. 3. In the interpolation step S3, the interpolation unit 153 generates points at an arbitrary interval within and / or outside the section on the skeleton line L1 between two points linked with the elevation data. The interval is preferably within a range of 1 to 10 m in a straight section of the skeleton line L1, and within a range of 0.3 to 5 m in a broken line section in which a plurality of skeleton lines L1 are connected. Then, the interpolation unit 153 allocates an elevation value to each of the generated points based on the elevation value indicated by the elevation data linked to both ends of the section. If the location where the point is generated is within the section between two points, the elevation value is allocated by interpolation (linear interpolation). On the other hand, if the location is outside the section, the elevation value is allocated by extrapolation.

[0044] When two or more skeleton lines L1 intersect to form a real intersection and the elevation value of the real intersection is to be allocated, the interpolation unit 153 performs allocation by linear interpolation for each skeleton line L1. It is preferable that the elevation values ​​obtained by each allocation are the same, but in many cases, these elevation values ​​are different. Therefore, the interpolation unit 153 adjusts the elevation value of the real intersection using a weighting that is set in advance for each skeleton line L1 (directed polyline). For example, when there are two intersecting skeleton lines and the weighting of each skeleton line L1 is set to 0.5:0.5, the interpolation unit 153 takes the average of the obtained elevation values. Also, when the weighting of each skeleton line L1 is set to 1:0, the interpolation unit 153 sets the elevation value obtained for the skeleton line L1 with the weighting set to 1 as the elevation value of the real intersection.

[0045] The weight of the skeleton line L1 may be set by the user or according to a predetermined rule. For example, when the skeleton line L1 is that of a road, the predetermined rule is set based on the width of the road. Specifically, when the difference in width between the intersecting roads is sufficiently large, the weight of the road with the larger width is made relatively large. In particular, when the intersecting roads are a main trunk road and a branch road, it is common to match the elevation of the main trunk road, so the weight of the main trunk road is set to 1 and the weight of the branch road is set to zero.

[0046] When the elevation value of a real intersection is adjusted, the elevation value of the points on the skeleton line L1 is redone. In this case, since the elevation value of the adjusted real intersection should not be changed, the elevation data is allocated within the section between the point linked to the real intersection. In other words, the elevation points of the adjusted real intersection are referenced to redeploy the elevation points of the points on the skeleton line L1.

[0047] (4. Global ranking setting step) After acquiring the skeleton line data and the elevation data, the process proceeds to a global order setting step S4. In the global order setting step S4, the global order setting unit 154 sets an overall global order for each skeleton line L1 of each structure. In the global order setting step S4 according to this embodiment, the global order setting unit 154 sets the order in accordance with a predetermined ordering rule. The ordering rule used here is as follows: All road skeleton lines L1: 1st All irrigation channels: 2nd place Fields (including ridges): 3rd to N-1 in order of altitude All drainage channels: Nth rank (lowest)

[0048] The reason why the skeleton line L1 of the road has the first global ranking is because roads in farmland are installed at a higher position than the surrounding fields, and slopes often extend from the left and right connecting lines L2 of the skeleton line L1 of the road. On the other hand, the skeleton line L1 of the drainage channel has the lowest global ranking because drainage channels are installed at a lower position than the surrounding fields, and often intersect with slopes extending from roads and fields. Also, the skeleton line L1 of the irrigation channel has the second global ranking because irrigation channels are often installed at a higher altitude than the fields. Also, the skeleton line L1 of the field is assigned a global ranking in descending order of altitude because slopes extend from high-altitude fields to low-altitude fields. By setting such global rankings, in the surface generation step S11 described later, a slope is generated from the side of the skeleton line with a high global ranking to the side of the skeleton line with a low global ranking. Also, a ground surface is generated from the side of the skeleton line with a lower global order. The ground surface is generated at a certain length from the connecting line. After the ground surface is generated, a downward slope is generated on the outside of the ground surface up to the base ground surface. Also, between skeleton lines with the same global order, processing is performed using pair information, which will be described later.

[0049] The global order may be freely set by the user. Furthermore, when a model of a new structure is additionally generated in a three-dimensional model after the generation of the three-dimensional model, the user may set an arbitrary global order for the skeleton line L1 corresponding to the new structure, or the global order setting unit 154 may automatically assign a global order according to the type of work. The model may be regenerated by the user changing the global order.

[0050] (5. Judgment step) In the ground surface data generating method according to the present embodiment, if the acquired CAD data is two-dimensional CAD data, the process proceeds to a determination step S5 after setting the global order. In the determination step S5, the determination unit 155 determines whether an intersection of multiple skeleton lines L1 in the acquired CAD data is an actual intersection that actually intersects (if the two skeleton lines L1 are each roads, it becomes an intersection) or a multi-level intersection that does not actually intersect (if the two skeleton lines L1 are each roads, one road becomes an underpass). Specifically, the determination unit 155 determines whether an intersection identifier (a predetermined mark (such as a rectangle)) is attached to the intersection of the skeleton lines L1 included in the two-dimensional CAD data. If an intersection identifier is attached, the determination unit 155 determines that the intersection is a multi-level intersection. On the other hand, if an intersection identifier is not attached, the determination unit 155 determines that the intersection is an actual intersection.

[0051] (6. Connection line generation step) After acquiring the skeleton line data and the elevation data, or after determining the intersections of the skeleton line L1, the process proceeds to a connection line generating step S6, in which the connection line generating unit 156 generates a three-dimensional connection line L2 indicating the outline of the structure from the skeleton line L1 based on the shape data.

[0052] When the input of the shape data is accepted, the connection line generating unit 156 generates a connection line L2 based on the position and shape data of the skeleton line L1. When the skeleton line L1 is a road, a waterway, or the like (the skeleton line L1 is a directed polyline), the connection line generating unit 156 generates a pair of connection lines L2, L2. Specifically, the connection line L2 (such as the connection line L2 indicating the slope) is generated on the right and left sides of the direction of the directed polyline, which is parallel to the directed polyline. When the skeleton line L1 is a directed polyline, the connection line generating unit 156 further generates a pair of end lines. Specifically, the connection line generating unit 156 generates end lines that pass through both ends of the skeleton line L1 and connect both ends of the pair of connection lines L2 that sandwich the skeleton line L1. Then, the connection line generating unit 156 assigns an ID to each generated connection line L2.

[0053] Paddy fields have ridges on the periphery because they need to store water on the surface of the field. Therefore, when the structure is a paddy field, the connection line generating unit 156 calculates the elevation of both ends of the ridge based on the elevation data of the paddy field surface, and generates a ridge skeleton line L1 of the paddy field based on the paddy field skeleton line L1 (polygon) and the calculated elevations of both ends of the ridge. The connection line generating unit 156 then generates a connection line L2 of the ridge based on the ridge skeleton line L1 and shape data that defines the shape of the ridge.

[0054] When the operation unit 12 receives an instruction from the user to generate a model of a structure other than the structure indicated by the skeleton lines L1 at the intersection of the two skeleton lines L1 (for example, a corner cut if the structure is a road, or a manhole if the structure is a waterway), the connection line generation unit 156 generates a connection line for the other structure based on the input shape data.

[0055] In addition, for structures that are recognized as a two-way intersection consisting of two roads (waterways) of different widths, an adjustment section is set up on either side of the intersection, and a connecting line L2 is generated within the adjustment section so that the width changes continuously from one road (waterway) to the other road (waterway), thereby smoothly connecting one road (waterway) to the other road (waterway).

[0056] (7. Shared connection line generation step) After generating the connection line L2, the process proceeds to a shared connection line generation step S7 as shown in FIG. 3. The shared connection line is a connection line for performing a pairing search. In the shared connection line generation step S7, the shared connection line generation unit 157 generates a single shared connection line L3 by connecting the section connection lines L21. Specifically, the shared connection line generation unit 157 first detects a shared point where a projection line obtained by projecting the target connection line L2 in the vertical direction onto a horizontal plane intersects with another projection line obtained by projecting another connection line L2 in the vertical direction onto a horizontal plane. A connection line separated by a shared point is called a section connection line. Next, the section connection lines intersecting on the vertical projection plane are connected so as to trace the outside of the structure to generate a single shared connection line. When generating a shared connection line, it may be an actual intersection where two connection lines actually intersect, or a three-dimensional intersection where they do not actually intersect. In other words, the elevations at the shared points of the two connection lines may be the same or different.

[0057] Specifically, as shown in 501 of FIG. 5, two connection lines L2(a) of the skeleton line L1(a) (assumed to be straight lines) and two connection lines L2(b) of the skeleton line L1(b) (assumed to be straight lines) are divided at a common point P1, which is an intersection point, and decomposed into a plurality of section connection lines L21 (12 in the example shown in FIG. 5). Then, the shared connection line generating unit 157 invalidates the section connection line L21 that passes through the inside of the structure from the common point P1. Then, as shown in 502 of FIG. 5, the shared connection line generating unit 157 generates the shared connection line L3 by selecting and connecting the connection line L21 that does not pass through the inside of the structure from the common point P1. In this way, the shared connection line L3 is generated with one end of the connection line L2 as the starting point. As shown in 502 of FIG. 5, the shared connection line L3 is not generated inside the intersecting structure. In other words, the section connection line inside the structure is not searched for pairing. Furthermore, when generating the intersection, a connection line of the intersection model is generated for the adjustment section. The ends of the connection lines in the intersection model share the same points as the original connection line L2.

[0058] By repeating this process of connecting the section connection lines L21 while changing the target connection line L2, the continuous section connection line L21, including the end lines, will form a loop. Therefore, the target connection line L2-shared point P1-other connection lines L2··shared point P1 is treated as a single circular shared connection line L3. All structures will be included in some loop structure.

[0059] Furthermore, when the shared connection line generating unit 157 determines that the target connection line L2 intersects with another connection line L2, it determines whether the shared point P1 is a shared point P1 at an actual intersection where the two lines actually intersect, or a shared point P1 at a multi-level intersection where the two lines do not actually intersect. Whether or not the two lines actually intersect can be determined from the presence or absence of an intersection identifier or from elevation data, as described above. Information on whether or not the two lines actually intersect is necessary to determine whether or not to generate a model along the intersecting connection lines.

[0060] In the following, a 3D mesh model of a structure including a slope or ground surface is referred to as a "model". For example, an intersection model that defines the structure of an intersection. In a real intersection, an intersection model including a slope or ground surface is generated along the connecting connection line. Therefore, it is necessary to process so that a model is not generated between the shared points inside the intersection. For this reason, the section connecting lines outside the intersection are connected at a common point, recognized as a single connecting line, and the connecting lines between the shared points are invalidated. The connecting connection line is a connecting line used to generate a 3D mesh, and in the case of a real intersection, the section connecting lines are connected at a common point to form a single connecting line. Since the connecting connection line is a common point where two connecting lines intersect in real, if the elevations of the common points obtained by interpolation are different, they need to be adjusted to the same elevation. On the other hand, the shared connection line is a connecting line used when searching for pairing, and is a single connecting line connected at a common point that is an intersection point when projected vertically, not limited to a three-dimensional intersection or a real intersection. However, it is not necessary that the shared points actually have the same elevation.

[0061] 503 and 504 in Fig. 5 show an example of a connection line for generating a model. 503 is a connection line L3 when two skeleton lines L1(a) and L1(b) shown in 501 intersect with each other in substance. In the case of an actual intersection, a connecting connection line is formed by connecting a common point P1. As shown in the figure, the connecting connection line shown in 503 has the same configuration as the common connection line shown in 502. Then, the surface generating unit 161 generates a ground surface or a slope from the connecting connection line L3.

[0062] 504 in FIG. 5 indicates a connection line when the two skeleton lines L1(a) and L1(b) shown in 501 intersect at an intersection. When there is an intersection at an intersection, the connection lines do not actually intersect, and become normal connection lines. Therefore, the two connection lines L3(a) of skeleton line L1(a) are drawn along skeleton line L1(a). The same is true for the two connection lines L3(b) of skeleton line L1(b). Then, the surface generating unit 161 generates a ground surface, a slope, or the like outside the normal connection lines L3(a) and L3(b).

[0063] Generally, a corner cut is provided at a real intersection of a road, and a square is provided at a real intersection of a waterway. Therefore, when generating a connection line L2 at a real intersection of a road or a waterway in the connection line generating step S6, the connection line generating unit 156 determines an intersection area based on the position information of the intersection point of the two skeleton lines L1 and the information of the width of the structure specified by the shape data. Then, the connection line generating unit 156 specifies the section connection line L21 included in the intersection area. Then, the connection line generating unit 156 further generates a connection line L4 of the intersection model (corner cut or square) as shown in FIG. 6 based on the shape data of the set intersection model. Then, the connection line generating unit 156 connects the connection line L4 of the generated intersection model to the connection line L2 to form a new connection line L3.

[0064] For example, when the actual intersection is a road intersection (four-way intersection), the connection line generating unit 156 generates a corner cutting connection line L2 that connects a pair of section connection lines L21 that sandwich a common point P1 in the intersection area based on the shape data of the corner cutting. Then, the connection line generating unit 156 connects the generated corner cutting connection line L2 to the already generated road connection line L2 to form one connection line L2. On the other hand, when the actual intersection is a waterway intersection, the connection line L2 that becomes the outline of the box is generated based on the position information of the intersection of the skeleton line L1 and the information of the width of the box specified by the shape data so that the center of the connection line L2 coincides with the intersection of the skeleton line L1 and a horizontal ground surface is formed around the box. Note that when the intersection model is a box, even in the case of an actual intersection, the elevations of the waterways may differ at the intersection. This is because even if the elevations of the various channels are different, the water flowing through them joins together at a manhole (the elevations do not have to be the same).

[0065] (8. Pairing step) After the elevation values ​​are assigned to the section between the two points to which the elevation data is linked and the connecting lines outside the section, the process proceeds to a pairing step S8. In the pairing step S8, the pairing unit 158 ​​first executes a pairing search. The pairing search is to search for a connecting line outside the shared connecting line L3 (in a direction perpendicular to the extension direction of the line) and to set the section where pairing is established as a paired connecting line. It can be said that the pairing search is to search for a connecting line located at a position that is likely to be paired as a combination of the ground surface or the slope. The pairing search is performed for all normal connecting lines and shared connecting lines. Note that there are two types of connecting lines for which the pairing search is performed: a normal (single) connecting line that does not intersect, and a shared connecting line (both when there is a multilevel intersection and when there is a real intersection).

[0066] The pairing search is performed at least by using the two-dimensional inscribed circle method, the three-dimensional inscribed sphere method, and the three-dimensional skewered ball method for a plurality of nodes P2. The nodes P2 are points that form the shared connection line L3. The intervals between the nodes P2 used in the pairing search are arbitrarily and discretely selected within a range of several tens of centimeters to several meters. The distance between the nodes P2 is approximated by a straight line. When performing the pairing search using two or more of the above three methods, for example, a method is given in which the section where the pair information (master and slave) described later is switched is roughly extracted using the inscribed circle method, and then only that section is examined again in detail using the skewered ball method.

[0067] In the two-dimensional inscribed circle method, first, three-dimensional vector information is converted into vector information on a two-dimensional plane by projecting it vertically onto a horizontal plane. Then, as shown in FIG. 7, a circle is generated on the two-dimensional plane that is tangent to the target non-intersecting normal connection line A (or shared connection line A) at one node P2 on the target connecting connection line A, and the circle is enlarged so that the tangent point does not move. Then, when the circle has a tangent point with the normal connection line B (or shared connection line B) or the normal connection line C (or shared connection line C) in addition to the original tangent point, pairing of the target connection line A with the other connection line B or C is established. Note that, normally, the number of tangent points that the circle has with each connection line by performing pairing is two, but there are also cases where the number of tangent points is three or more.

[0068] In the three-dimensional inscribed sphere method, first, in a three-dimensional space based on three-dimensional vector information, a sphere is generated that is in contact with the target connection line L3 at one node P2 on the target connection line L3, and the sphere is enlarged so that the contact point does not move. In the case of the three-dimensional inscribed sphere method, the sphere is generated at each node P2 in, for example, three directions, so that at least three paired contact points are generated. Which of these contact points is to be selected may be determined by judging the master-slave relationship (global order) and height relationship with the paired connection line.

[0069] In order to determine whether the direction of the inscribed sphere is a ground line or a slope line, pairing information must be obtained. However, strictly speaking, there are three directions in which the inscribed sphere is generated: the upslope line direction, the ground surface line direction, and the downslope line direction. In the case of an inscribed circle, it is paired with the connecting line with the shortest horizontal distance, but in the case of an inscribed sphere, it is paired with the connecting line with the shortest three-dimensional linear distance. However, unlike the case of an inscribed circle, in the case of an inscribed sphere, the direction of generation must be specified as one of the directions in the vertical plane relative to the connecting line. There are three such directions: the upslope direction, the ground surface direction, and the downslope direction. When a pairing search is performed in these three directions, the combination with the shortest linear distance is considered. For example, if it is an upslope line, if the point with which the other is paired is the master, the self becomes a slave, and the search in the upslope line direction is not adopted. Similarly, if the elevation of the other's internal contact point is lower than the self point, the search in the upslope line direction is not adopted. In that case, the pairing with the next shortest straight-line distance is considered. For example, if the pairing partner is a slave, the device itself is the master, and the search for the ground line direction is not adopted. On the other hand, if the partner is a slave, pairing is established. In this way, among the three directions, the direction being searched for pairing is judged in order of closest straight-line distance to see if it matches the combination of pairing information. If the combination of pairing information does not match, the next closest pairing is judged in the same way until a pairing is established. If no pairing is established until the end, it is determined that there is no pairing partner and the search ends.

[0070] Of these pairing methods, the two-dimensional inscribed circle method and the three-dimensional inscribed sphere method require relatively low computational costs for searches and are suitable for roughly creating pair connection lines. On the other hand, the two-dimensional inscribed circle method and the three-dimensional inscribed sphere method may not be able to accurately search for pair connection lines at or near points where pair connection lines (hereafter referred to as pair connection lines) switch. In contrast, the kushi-dango method requires high computational costs for searches, but can accurately search for pair connection lines.

[0071] (Skewered dumpling method) The Kushi-dango method is a pairing method for finding a pair of a first connection line and a second connection line that meets the condition that the ground surface or slope generated from the first connection line intersects with the ground surface or slope generated from the second connection line. The Kushi-dango method is a method for accurately pairing connection lines arranged three-dimensionally. The Kushi-dango method is also called the three-dimensional Kushi-dango method. An overview of the Kushi-dango method is given below.

[0072] First, the first connection line and its nodes are input as input. Next, as shown in Fig. 8, division points O1, O2...On are generated between adjacent nodes P1 and P2 at intervals of Δd1. The length of Δd1 is arbitrary. Fig. 8 is a plan view of the connection line between nodes P1 and P2 as seen from above. The coordinate symbols shown in the figure indicate that the horizontal plane is represented by the XY directions, and the vertical direction is represented by the Z axis. Note that the direction opposite to gravity (upward) is the positive direction of the Z axis.

[0073] Next, normal lines or ground plane lines are drawn from the nodes P1 and P2 and the division points O1 and O2···On. An example of drawing normal lines will be described below. FIG. 9 is a diagram showing normal lines from the nodes P1 and P2 and the division points O1 and O2···On as viewed from above. Hereinafter, the division points O1 and O2···On are also collectively referred to as division points On. First, normal lines are drawn from the nodes P1 and P2. When the angle between the connection lines at the node is 180 degrees or less, normal lines are generated at a predetermined inclination angle in a vertical plane perpendicular to the two connection lines that form the angle. In FIG. 9, the normal line vector from the node P1 is indicated as v1, and the normal line vector from the node P2 is indicated as v2. Then, intermediate points P are generated at intervals of Δd2 for the vectors v1 and v2. The length of Δd2 is arbitrary. The intermediate points P are P11, P12, . . . , P1m, etc. as shown in Fig. 9. All of these intermediate points are collectively referred to as intermediate point Pm.

[0074] Next, normal line vectors vO1, vO2, . . ., vOn are drawn from division points O1, O2, . . ., On to interpolate vector v1 and vector v2. Then, intermediate points O are generated for each vector at intervals of Δd2. The length of Δd2 is arbitrary. The intermediate points O are O11, O12, . . ., O1m, etc., as shown in Figure 9. Hereinafter, all of these intermediate points are collectively referred to as intermediate points Onm.

[0075] Fig. 10 is a diagram showing vectors v1, v2, and vectors vO1 to vOn viewed from the side (horizontal direction). As shown in Fig. 10, the inclination angle of vector v1 from node P1 and vector v2 from node P2 are different, so the inclination angle of linearly interpolated vector vO differs slightly.

[0076] Next, as shown in Figure 11, spheres with increasing radius are generated with each of the intermediate points Onm as the center. Then, another connection line that touches the generated spheres from each intermediate point Onm is searched for.

[0077] Specifically, the point of contact between a sphere with gradually increasing radius and another connecting line that first comes into contact with is defined as the contact point Q. Then, from among the multiple line segments OQ connecting the intermediate point Onm and the contact point Q, a line segment OQ (pairing line) that is approximately parallel to the normal line vector or ground surface line vector generated from the other connecting line is extracted. Then, the other connecting line that provides multiple pairing line candidates that are approximately parallel to the same normal line or ground surface line is found. With this method, the intersection line where the normal lines and ground surface lines between structures intersect can be found with high accuracy.

[0078] As described above, when the angle between the connection lines at a node is 180 degrees or less, a normal line or ground line is generated in a vertical plane perpendicular to the two connection lines that form that angle (PV line). Then, a pairing search is performed for each PV line. Thus, the above node has two pieces of pair information. On the other hand, when the angle between the connection lines is greater than 180 degrees, the connection lines are discretized at a predetermined angle from the node outward, and a normal line or ground line is generated for each angle (PV line). Then, a pairing search is performed for each PV line. Thus, a node that is open more than 180 degrees has two or more pieces of pair information.

[0079] By the above method, a pairing line (line segment OQ in FIG. 11) showing that the slope line and ground surface line between the structures are paired by the division point On, the midpoint Onm, and the contact point Q, and an intersection line connecting the intersection point where the slope line and the ground surface line intersect are obtained. An example of the pairing line and intersection line obtained in this way is shown in FIG. 12. FIG. 12 shows a pairing line and intersection line between a slope generated from one connection line and a ground surface generated from another connection line. Note that multiple pairs are obtained for each combination of a downslope and a ground surface, an upslope and a ground surface, a downslope and a downslope, an upslope and an upslope, and an upslope and a downslope, and since the combination is identified based on the global order and the relationship of the elevation position, the final pair is determined.

[0080] The above-mentioned skewered dumpling method may be executed by the earth surface data generation device 1. For example, the skewered dumpling method may be executed by having the processor of the control unit 15 read and execute a skewered dumpling method program stored in the storage unit 14. In addition, the earth surface data generation device 1 may visualize the search results as shown in FIG. 12 and output the image to the outside via the output unit 13.

[0081] As mentioned above, the Kushi-dango method requires a long processing time, which is a disadvantage in that the calculation cost is high. Therefore, pairing may be usually performed using the 2D inscribed circle method or the 3D inscribed sphere method. The Kushi-dango method may be used only when accurate pairing is required. After pairing is performed using the inscribed circle method or the inscribed sphere method, a slope or ground surface may be generated from each pair connection line, and when the slope and ground surface intersect, the Kushi-dango method may be used to consider the position and direction of the switching line that switches the slope and ground surface.

[0082] After performing the pairing search, the pairing unit 158 ​​sets the sections where pairing is established in each of the multiple shared connection lines L3 as paired connection lines. For example, in the example shown in Fig. 7, as a result of performing pairing search for a certain connection line A, when a section from one node to an adjacent node is considered as one section, one or more sections included in the connection line A are paired with a section connection line BA included in the connection line B, and one or more other sections are paired with a section connection line CA included in the connection line C, the pairing unit 158 ​​removes the section connection line AB and the section connection line BA including the certain section, and sets them as paired connection lines. Then, the pairing unit 158 ​​removes the section connection line AC and the section connection line CA including the other section, and sets them as other paired connection lines.

[0083] When performing pairing search, a self-intersecting portion may be found in the shared connection line L3. The self-intersecting portion refers to a state in which, when a circle or a sphere is generated from a node on a shared connection line L3 that is in contact with the shared connection line L3 and the circle or the sphere is enlarged so that the junction does not move, the junction that the circle or the sphere first has, apart from the original junction, is on itself (a shared connection line L3). The self-intersecting portion occurs, for example, when the shared connection line L3 has a closed shape. A closed shape refers to a case in which the angle that the two connection lines connected at the node P2 make toward the outside of the structure is smaller than 180 degrees. Conversely, an open shape refers to a case in which the angle that the two connection lines connected at the node P2 make toward the outside of the structure is 180 degrees or more. In such a case, the pairing unit 158 ​​pairs with itself.

[0084] Since there are no connection lines further outward from the outside of the drawing, the search range may be limited to a length of about 30m to 200m in order to avoid paying unnecessary calculation costs in the pairing search. If no pairing partner is found, the pair information may be set to "no pair information." If there is no pair information, a slope line or ground surface is generated on a rule basis. Note that the connection lines between shared points at an intersection also do not have pair information, but since the connection lines in this part can be recognized as connection lines between shared points, the ground surface or slope may be determined by referring to the pair information of adjacent connection lines.

[0085] In the case of a three-dimensional intersection, since each structure exists independently, it is necessary to generate a model independently of each other. The common points P1 of each connection line L2(a) generated on both the left and right sides of one skeleton line L1(a) that forms a three-dimensional intersection and each connection line L2(b) generated on both the left and right sides of the other skeleton line L1(b) are not connected to each other, but are independent of each other. As a result, the connection line L2(a) and the connection line L2(b) generate a slope or ground surface from the connection line L21 between the common points in each structure. Specifically, if it is determined in the above-mentioned determination step S5 that the common point P1 is in a three-dimensional intersection, the slope or ground surface is generated from the section connection line between the common points in the surface generation step S11 described later. However, the section connection line between the common points does not have pair information because pairing search is not performed. Therefore, the slope or ground surface is generated by referring to the pair information of the connection line adjacent to the section connection line. Details are as follows.

[0086] In the case of a three-dimensional intersection, since the angle is likely to be closed at the shared point, the connection line adjacent to the section connection line is likely to obtain pair information with the connection line itself. In other words, there is a high possibility that a section will occur that has no pair information other than its own connection line. For this reason, a normal line or ground surface line is generated for the section connection line by referring to the pair information of the two section connection lines adjacent to the section connection line. Note that even at the point of actual intersection, since the angle is closed at the shared point, there is a high possibility that it will be a self-intersection. In other words, there are many cases where a section connection line does not have pair information other than its own connection line. In this case, the normal line or ground surface line is generated in the same manner as above.

[0087] Although a pair connection line is generated by the pairing search, the pair connection line may not be divided at an appropriate position depending on the method of the pairing search. For this reason, in the pairing step S8, the pairing unit 158 ​​may be configured to receive an instruction to change the division position. The instruction to change is given by the user using the operation unit 12. Even if a pairing search is performed, a partner to be paired may not be found depending on the position or shape of the connection line L2.

[0088] (9. Pair information setting step) After the pair connection line is generated, the process proceeds to a pair information setting step S9 as shown in FIG. 3. In the pair information setting step S9, the pair information setting unit 159 sets pair information for each section included in the pair connection line based on the overall global ranking. The pair information is information indicating a master-slave relationship between the sections, and there are two types of pair information: master (main) and slave (slave). The pair information setting unit 159 sets the pair information by referring to the global ranking set for each section included in the pair connection line. Specifically, the pair information setting unit 159 sets the pair information of a section with a relatively high global ranking among the sections included in the pair connection line to the master. On the other hand, the pair information setting unit 159 sets the pair information of a section with a relatively low global ranking among the sections to the slave. Furthermore, when the global rankings of the sections are the same, the pair information setting unit 159 sets the same pair information (master or slave) for both sections.

[0089] Furthermore, the pair information setting unit 159 sets different colors for the section where the master pair information is set (where a slope occurs) and the section where the slave pair information is set (where a ground surface line occurs). As a result, in the data output step S13 described later, the section where the slope occurs and the section where the ground surface line occurs are displayed in different colors. Furthermore, the pair information setting unit 159 sets information indicating the direction in which the ground surface line or the slope line occurs at each node. As a result, in the data output step S13 described later, an arrow or the like indicating the direction in which the ground surface line or the slope line occurs is displayed. Furthermore, the pair information setting unit 159 sets information to generate a switching line at a node where the ground surface and the slope are replaced. As a result, in the data output step S13 described later, the switching line is displayed in a color different from that of the ground surface line or the slope line.

[0090] When the intersection of two skeleton lines L1 is a real intersection point, each connection line L2 generated based on these skeleton lines L1 also intersects in the same way as the skeleton lines L1. In this case, the elevations at the common point P1, which is the intersection point of each connection line L2 with the other, are set to be the same, and each connection line L2 belongs to the same common connection line L3. Each skeleton line L1 is assigned a global order. And the connection lines L2 generated based on each skeleton line L1 inherit the global order of the skeleton line L1.

[0091] (10. Switching line generation step) After the pair information is set, the process proceeds to a switching line generating step S10. In the switching line generating step S10, the switching line generating unit 160 searches for a point where a ground surface line or a normal line generated from one of the pair connection lines switches from one to the other, and generates a switching line L5 as shown in FIG. 13. Specifically, the switching line generating unit 160 searches for a point where a ground surface line or a normal line switches from one to the other and a direction in which the other line extends. When generating the switching line L5, the direction of the switching line L5 is also specified.

[0092] (11. Surface generation step) After generating the paired connection lines, the process proceeds to a surface generating step S11 as shown in FIG. 3. In the surface generating step S11, the surface generating unit 161 generates a slope or a ground surface from each paired connection line based on the pair information of each section included in the paired connection line. The slope (line) or the ground surface (line) is generated from a normal connection line (not having a common point) and a linking connection line. As described above, the linking connection line is a connection line obtained by connecting the common points where the connection lines of the structures actually intersect. The linking connection line includes a section connection line that does not have pair information, but the slope or the ground surface is generated by referring to the pair information of the connection line adjacent to the section connection line. When the connection lines of the structures intersect as an entity and mesh data (hereinafter also simply referred to as "mesh") of the intersection is generated, the slope or the ground surface is generated from the linking connection line obtained by connecting the common points. When the connection lines of the structures intersect as an entity and mesh data of the intersection (hereinafter also simply referred to as "mesh") is generated, the slope or the ground surface is generated from the linking connection line obtained by connecting the common points. When the connection lines of the structures intersect with each other in a multi-level intersection and mesh data of the intersection is not generated, the slope or the ground surface is generated from each of the intersecting connection lines.

[0093] Specifically, the surface generating unit 161 first sets a plurality of nodes P2 on the pair connection line. Alternatively, the nodes P2 may be nodes already set on the shared connection line. Then, as shown in FIG. 7, the surface generating unit 161 generates a ground surface line L6 from the nodes P2 set on the pair connection line, or a normal line L6 having a predetermined inclination angle (defined by the shape data) from the horizontal plane. The surface generating unit 161 refers to the pair information set for each section of the pair connection line, generates a normal line L6 from the connection line L2 for which the master pair information is set, and generates a ground surface line L6 from the connection line L2 for which the slave pair information is set.

[0094] In the case of a ground surface line L6 where the angle between the connection lines on both sides of the starting point (node) is 180 degrees or less, as described above, a normal line or a ground surface line is generated in a vertical plane perpendicular to the two connection lines that form an angle. Then, a ground surface or a slope is generated for each connection line. On the other hand, when the angle between the connection lines is greater than 180 degrees, the connection lines are discretized at a predetermined angle from the node toward the outside, and a normal line or a ground surface line is generated for each angle. Then, a ground surface or a slope is generated for each connection line. Specifically, the surface generating unit 161 generates a plane (mesh) that becomes a ground surface or a slope between the adjacent ground surface lines L6, the slope line L6, or the switching line L5 generated in the switching line generating step. Note that, when the pair information of the low-lying structure is the master and the pair information of the high-lying structure is the slave, the surface generating unit 161 generates an upslope from the connection line L2 of the low-lying structure.

[0095] If the angle between the connection lines on both sides of the starting point (node) exceeds 180 degrees, the angle is discretized (divided) at a specified angle, and a ground surface line or normal line of a specified length is generated radially. When generating a ground surface, the tip of the ground surface line of a specified length is connected to form a ground edge line, and the range surrounded by the connection line, adjacent ground surface lines, and ground edge lines is the ground surface. When generating a slope, a normal line with a discretized angle from the starting point is generated to the base ground with a specified downward gradient (inclination angle). Then, the surface consisting of the starting point and the two points where the two adjacent normal lines intersect with the base ground is the slope. The range in which the ground surface line or normal line is generated radially is the range of the angle formed by two vertical planes having the orthogonal components of the line segment obtained when the connection line is projected vertically onto a horizontal plane through the node, with respect to each connection line, toward the outside of the connection line. The base ground is a ground surface with an elevation lower than the elevation of the lowest part of all structures. Specifically, for example, the lowest elevation value of the node elevations of all the connection lines can be obtained, and the elevation value can be lowered by any height from that elevation value to become the elevation of the base ground. This allows the elevation of the base ground to be set in the program. The base ground is the reference surface for determining the elevation up to which the downward slope is generated in 3D model generation.

[0096] All structures belong to one of the loops (multiple) that are made up of a series of section connection lines. The loops may be normal connection lines or linked connection lines, and may include end lines in some cases. In the surface generation step S11, the connection lines and end lines of one or more structures are expressed as loops, and a surface is generated for each loop. Next, a Boolean operation is performed on the surface generated for each loop using the plane method within the loop to generate a mesh that is connected with meshes of only the ground surface of the structures included in the same loop. At this time, meshes below the ground surface are removed. This process is performed for all structures included in the same loop. Then, a Boolean operation is performed again on all the ground surface meshes generated for each loop, and meshes that are connected with meshes of only the ground surface of all structures are generated by removing meshes below the ground surface.

[0097] When the same pair information is set for each section of the pair connection line, the surface generating unit 161 generates the same type of surface (ground surface or slope) from each section of the pair connection line. When the pair connection lines have the same order, the model (ground surface or slope) generated at the point where the order of proximity is changed is adopted. Also, in the above pairing step S8, when there is a connection line L2 for which a partner to be paired cannot be found, the surface generating unit 161 generates a surface from the connection line L2 according to a predetermined rule (for example, generating a slope from a connection line L2 for which a partner cannot be found).

[0098] When the connection line of the intersection model has been generated, the surface generating unit 161 also generates a ground surface or a slope from the connection line L4 of the intersection model as shown in FIG.

[0099] The surface generating unit 161 may generate a surface from the section connecting line L21 that is the same type as a surface extending from another section connecting line L21 that connects to the section connecting line L21, or may generate a different surface. For example, when generating a slope and a ground surface adjacent to each other, the surface generating unit 161 may generate a slope that becomes gentler as it approaches the ground surface, so that the ground surface and the slope are smoothly connected.

[0100] The surface generating unit 161 also generates a ground surface or a slope from the end line. The surface generating unit 161 basically generates a downward slope. However, depending on the surface extending from the left and right connecting lines L2 of the skeleton line L1, the surface generating unit 161 generates a surface that can be continuously connected to the ground surface line or the slope line extending from the intersection of the end line and the connecting line L2. When the surfaces extending from the left and right connecting lines L2 are the same (symmetrical), the surface generating unit 161 generates a surface of the same type as the surface extending from the connecting line L2 from the end line. When both the surfaces extending from the left and right connecting lines L2 are slopes and each slope includes a step, the surface generating unit 161 generates a slope including a step from the end line. In addition, when the surfaces extending from the left and right connecting lines L2 are slopes with different inclinations, the surface generating unit 161 generates a slope whose gradient gradually decreases from a steep slope to a gentle slope. Furthermore, when the surface extending from the right connection line L2 is either the ground surface or a slope, and the surface extending from the left connection line L2 is the other, the surface generating unit 161 generates a slope whose gradient gradually decreases from the slope to the ground surface. Furthermore, when the surfaces extending from the left and right connection lines L2 are slopes and one of the slopes includes a berm, the surface generating unit 161 generates a slope whose width gradually narrows from the slope including the berm to the slope not including the berm. The loop formed by the connection lines and the end lines is formed by one or more structures.

[0101] If the ground surface or slope is simply generated from each section connection line L21, the surface may intersect with another surface, and a part of one surface may overlap a part of the other surface in the vertical direction. Therefore, in the ground surface data generation method according to this embodiment, in the surface generation step S11, the surface generation unit 161 deletes the other surfaces from among the overlapping surfaces, leaving only the top surface (ground surface). The surface generation unit 161 performs this process using Boolean operations (plane method). As a result, the three-dimensional model consisting of the structure, the ground surface, and the slope is composed only of meshes representing the ground surface. Note that if a part of one surface overlaps a part of the other surface in the vertical direction, in the surface generation step S11, the surface generation unit 161 reconstructs the top surface.

[0102] In the surface generating step S11, the surface generating unit 161 executes the above-described processing, thereby generating a three-dimensional model such as that shown in FIG.

[0103] (12. Warning information extraction step) After the three-dimensional model is generated, the process proceeds to warning information extraction step S12. In warning information extraction step S12, warning information extraction unit 162 determines whether or not the generated three-dimensional model has any of the following problems. - The downward slope extending from a higher structure crosses the connection line L2 of the lower structure, or the upward slope extending from a lower structure passes under the connection line L2 of the higher structure. - The slope of the slope exceeds the specified tolerance (value specified in the design standards). - The gradient of the waterway is above or below the specified tolerance range. - The gradient of the driving surface (paved surface or approach road to the field) exceeds the specified tolerance. - The difference in elevation between two structures on either side of the slope is less than the specified tolerance (value specified in the design standards).

[0104] The determination as to whether or not the downward slope extending from the high structure crosses the connection line L2 of the low structure is performed as follows. Note that this determination is performed for the connection line L2 that the slope crosses first, and is not performed for the connection line L2 that the slope crosses second. Specifically, the warning information extraction unit 162 refers to a cross section of the structure and the slope cut by a plane perpendicular to the skeleton line L1, and determines whether or not the slope line, which is the cross section of the slope, passes over a point that is the cross section of the connection line L2 of the low structure. If it is determined that the slope line passes over the point, the downward slope extending from the high structure crosses the connection line L2 of the low structure. In this case, the warning information extraction unit 162 assigns warning information to the slope that passes over the point. Note that in the above acquisition step S1, if the section that becomes an underpass on the skeleton line L1 is drawn with a broken line, processing may be performed so that it is not determined that there is a problem even if the downward slope crosses the broken line.

[0105] When generating a slope connecting one section and the other section included in a pair of connection lines, a slope with a gradient larger than the allowable value may be generated. Whether or not the slope inclination exceeds the allowable value is determined as follows. First, as shown in FIG. 15, a point sequence vector V extending from a point on the connection line L2 of a high-altitude structure (road) to a point on the connection line L2 of a low-altitude structure (waterway) is generated, and the angle θ between the point sequence vector V and the horizontal plane H is extracted. Then, it is determined whether or not the extracted angle θ exceeds the allowable value. Here, if the angle θ exceeds the allowable value, the slope inclination exceeds the allowable value. In this case, the warning information extraction unit 162 assigns warning information to the slope.

[0106] To determine whether the gradient of the waterway exceeds or falls below the range of the allowable value, the angle between the waterway's skeleton line L1 (directed polyline) and the horizontal plane is extracted. Then, it is determined whether the extracted angle exceeds or falls below the range of the allowable value. If the angle exceeds the allowable value, the gradient of the waterway exceeds the allowable value. In this case, the warning information extraction unit 162 assigns warning information to the waterway. Similarly, to determine whether the gradient of the travel road surface exceeds a predetermined allowable value, the angle between the travel road's skeleton line L1 (directed polyline) and the horizontal plane is extracted. Then, it is determined whether the extracted angle exceeds the range of the allowable value. The same applies to the warning information.

[0107] The determination of whether the elevation difference between two structures sandwiching a slope is less than the allowable value is performed as follows. First, the connection line L2 of one structure that pairs with the connection line L2 of the other structure is searched for using any one of the two-dimensional inscribed circle method, the three-dimensional inscribed sphere method, and the three-dimensional skewer-and-dumpling method used in the pairing step S8. Then, the elevation values ​​of the pair of connection lines L2 that form a pair are calculated. Then, the elevation difference, which is the difference between the calculated elevation values, is calculated, and the elevation difference is compared with the allowable value. Here, if the elevation difference is smaller than the allowable value, it means that the elevation difference between the structures is insufficient. In this case, the warning information extraction unit 162 assigns warning information to a point or section on the connection line L2.

[0108] When a waterway is installed between the road and the field, the warning information extraction unit 162 cannot directly compare the elevation difference between the road and the field scene. In such a case, a node on the road connection line and a node on the waterway connection line corresponding to that node are obtained, and a node on the waterway connection line that is paired with that node on the opposite side is extracted. Furthermore, a node on the field connection line corresponding to this node is obtained. The node on the field connection line can access field elevation data. This makes it possible to obtain elevation difference information between the node on the road connection line and the field. This information is compared with the allowable elevation difference value, and if it is smaller, the warning information extraction unit 162 assigns warning information to a point or section on the connection line L2.

[0109] When a waterway is included in the generated 3D model, the warning information extraction unit 162 according to this embodiment adds an arrow indicating the water flow direction to the waterway as warning information. The warning information extraction unit 162 determines the water flow direction based on the elevation values ​​of both ends of the waterway skeleton line L1. The warning information extraction unit 162 adds an arrow to all generated waterways. This allows the user to confirm the water flow direction.

[0110] When a structure or the like to which warning information has been assigned is present, the warning information extraction unit 162 performs processing to notify the user of the warning information. Specifically, the warning information extraction unit 162 colors the structure, surface, or line to which warning information has been assigned in a warning color that is different from normal. When the structure in which a problem exists is a waterway, the warning information extraction unit 162 colors the arrow indicating the water flow or the waterway in a warning color. This enables the user to check whether there is a problem with the gradient of the waterway.

[0111] Even if the warning information extraction unit 162 judges that a problem exists, there are cases where it does not actually become a problem. For example, in the case of a multi-level intersection of roads or waterways, a downward slope extending from an upper road or waterway may cross a connecting line L2 of the road or waterway that passes underneath. Also, in terraced rice fields in steep mountainous areas, there may be places where the difference between the road surface and the rice field surface is reversed (the elevation difference becomes negative). Even in such cases, the warning information extraction unit 162 will not stop the execution of other processes even if it colors the structure, surface, or line with the problem in a warning color different from normal (it only notifies the user).

[0112] When the warning information extraction unit 162 according to the present embodiment determines that a downward slope extending from a high-altitude structure crosses the connection line L2 of a low-altitude structure, it colors the downward slope in a warning color and generates a reference line L7. The reference line L7 is a line that serves as a guide when moving the position of the skeleton line L1 in a modification step S14 described later. Note that the movement of the skeleton line L1 using the reference line L7 is premised on the assumption that no change is made to the elevation value and slope shape of the skeleton line L1 (only horizontal movement). Specifically, the warning information extraction unit 162 first sets a plurality of vertical planes with intervals between them that coincide with the direction in which the slope line is generated with respect to the connection line L2. Then, on each vertical plane, as shown in FIG. 16, it obtains point A that is directly above the connection line L2 and on the slope, and point B that is directly below point A and on the connection line L2. Next, it obtains point C that is on the extension line of the slope and coincides with the elevation of point B. Furthermore, it obtains the horizontal distance d1 between point B and point C. Also, find point D of intersection between a vertical plane passing through points A, B, and C and the skeleton line L1 of the high structure. Point E is the point located a horizontal distance d1 from point D in a direction away from the low structure. Point G is the point located a horizontal distance d1 from point F on the skeleton line L1 of the low structure in a direction away from the high structure. The straight lines connecting points E on each vertical plane and the straight line connecting points G on each vertical plane are each designated as reference lines L7.

[0113] If point D (skeleton line L1 of the high-altitude structure) is moved to the reference line L7 formed by connecting point E, the regenerated slope will not cross the connection line L2 of the low-altitude structure. Conversely, if point F (skeleton line L1 of the low-altitude structure) is moved to the reference line L7 formed by connecting point G, the slope will also not cross the connection line L2 of the low-altitude structure. Conventionally, when a downward slope extending from a high-altitude structure crosses the connection line L2 of a low-altitude structure, trial and error was required to move the skeleton line L1 to an appropriate position. However, the warning information extraction unit 162 according to this embodiment generates the reference line L7. Therefore, in a modification step S14 described later, the user can solve the problem of the three-dimensional model simply by moving the skeleton line L1 so that it coincides with the reference line L7.

[0114] (13. Data output step) After determining whether or not there is a problem, the process proceeds to data output step S13. In data output step S13, the data output processing unit 163 causes the output unit 13 to output the 3D CAD data. If the output unit 13 is a terminal to which a cable leading to a monitor is connected, or the monitor itself, this step causes the 3D model to be displayed on the monitor. If the output unit 13 is a communication unit that communicates with other devices, or a drive that writes 3D model data to media, this step causes the 3D CAD data to be provided to other devices, etc. The user can refer to the output data and make corrections, if necessary, in the modification step described below.

[0115] When the process for notifying the user of the warning information is performed in the warning information extraction step S12, the data output processing unit 163 displays the structure, surface, or line in which the problem exists in the 3D model displayed on the monitor in a warning color different from normal. This allows the user to easily grasp the position of the structure, surface, or line having the warning information. Furthermore, the user can easily consider the cause of the problem from the position or shape of the structure, surface, or line displayed in the warning color. Furthermore, when the data output processing unit 163 displays a 3D model of a waterway, it displays an arrow indicating the direction of the water flow on or near the waterway together with the waterway. This allows the user to easily check whether the water is flowing as intended.

[0116] In addition, in response to an output request from a user, in the data output step S13, the data output processing unit 163 converts the 3D CAD data of the 3D model in which the skeleton line L1 and the elevation value have been corrected into 2D CAD data and outputs it. When the skeleton line L1 is corrected, the data output processing unit 163 outputs 2D CAD data in which the plane coordinate value of the skeleton line L1 has been corrected. On the other hand, when the elevation value is corrected or added, the data output processing unit 163 outputs 2D CAD data in which the numbers written near the elevation identifier have been corrected or a new elevation identifier and number have been added. Note that the 2D CAD data cannot hold shape data. Therefore, when outputting the 2D CAD data, the shape data set for each skeleton line L1 is output together with the 2D CAD data. The 3D model can be reproduced by reading this 2D CAD data and shape data into the earth surface data generating device. Note that the data output processing unit 163 may be configured to output the 3D CAD data of the 3D model in which the skeleton line L1 and the elevation value have been corrected without converting it into 2D CAD data (as 3D CAD data). In this case, the data output processing unit 163 may output only the skeleton line data (in this case, additional shape data is required to reproduce the three-dimensional model), or may output both the skeleton line and the shape data. Furthermore, the data output processing unit 163 may output shape data (shape parameters) including the skeleton line data, which is linked to the layer.

[0117] (14. Change Step) If the generated 3D model has a surface contrary to the user's intention (a slope surface is created in spite of the intention to make it a ground surface, or vice versa), or if a surface colored in a warning color is present and the user judges it necessary, the 3D model needs to be modified. Therefore, in the ground surface data generation process according to this embodiment, after the 3D model is generated and a modification operation by the user is accepted, the process proceeds to a modification step S14. In the modification step S14, the modification unit 164 performs processing according to the modification operation. Specific examples of modification operations include, for a skeleton line, adding and deleting points constituting the skeleton line, and changing the coordinates of the constituent points, for a field, adding and deleting points constituting a polygon, and changing the altitude. For a road, the shape parameters include width and gradient, and for the ground surface, the parameters include modification to the ground surface line, slope line, and switching line to be generated between structures.

[0118] When an operation to replace the pair information of the pair connection lines is received, the change unit 164 changes the slope or ground surface generated from each of the pair connection lines. Specifically, the change unit 164 changes the slope line extending from the connection line to a ground surface line, or changes the ground surface line extending from the connection line to a slope line. Note that the pair information may be changed from master to slave, or from slave to master. When the slope line / ground surface line or the pair information is changed, the process proceeds to the surface generation step again, and the surface generation unit 161 regenerates the three-dimensional model. At that time, the surface generation unit 161 regenerates the slope or ground surface from each of the pair connection lines based on the pair information, slope line, or ground surface line changed by the user. Note that in the change step S14, the change unit 164 may receive an operation to specify the section connection line L21 and a surface to be generated from the section connection line L21. In that case, the change unit 164 changes the surface already generated on the specified section connection line L21 to the specified surface. The change unit 164 may also receive an operation to change the overall global ranking. In that case, the global ranking is changed according to the received operation, and the changed global ranking is then reflected in the pair information. A switching line can also be set at the boundary where the ground surface line and the normal line switch, and the position of this switching line can also be changed.

[0119] On the other hand, when an operation to move the plane coordinates of the skeleton line L1 or an operation to add or change an elevation point is received, the modification unit 164 modifies at least one of the position, extension direction, and gradient of the skeleton line L1. Thereafter, the process moves again to the connection line generation step S6 and the surface generation step to regenerate the 3D model. At that time, it is determined whether or not the problem that existed before receiving the operation has been resolved, and if it is determined that it has been resolved, the surface to be generated is colored in a normal color.

[0120] Furthermore, if the shape of the structure is changed due to the modification of the skeleton line L1, the process returns to the pairing step S8, where the pairing unit 158 ​​performs pairing search again. If the combination of sections that become paired connection lines is changed as a result, the pairing unit 158 ​​resets the pair information within the changed paired connection lines.

[0121] [Action and Effect] Conventionally, when a user wants to generate a slope on a certain connection line L2 and generate a ground surface in a certain part, the user needs to change the model by dividing the sections one by one, which is time-consuming. However, the above-described ground surface data generating device, method, and program generate a ground surface or a slope from the section connection line L21 according to the program in accordance with pair information linked to each section that is the starting point for generating the surface. Therefore, according to the ground surface data generating device, method, and program, when designing a three-dimensional model of the ground surface including multiple structures by parametric modeling, it is possible to easily generate a three-dimensional model of the ground surface or the slope between structures.

[0122] Currently, 3D design is becoming mainstream in the civil engineering industry. Using a 3D model generated by 3D design, the completed image can be easily communicated to the other party. However, small and medium-sized enterprises still cannot prepare dedicated software for 3D design and computers with high processing power, and cannot secure enough designers to perform 3D design. The reasons for this include the fact that dedicated software and computers are very expensive, high skills and experience are required to master the dedicated software, and the fact that it takes a huge amount of time to draw, making it poorly cost-effective. However, by using the above-described earth surface data generation device, method, and program, it is possible to obtain elevation data from 2D CAD data in which numbers indicating the elevation are written together with elevation identifiers, and generate a 3D model. Therefore, designers can easily perform design using inexpensive 2D design software while generating a 3D model.

[0123] [Embodiment 2] Next, as the second embodiment, a method for generating mesh data for design and construction, a device for generating mesh data for design and construction, and a program for generating mesh data for design and construction will be described. Hereinafter, the "mesh data for design and construction" will also be simply referred to as "mesh data for construction". For convenience of explanation, the same reference numerals will be used for members having the same functions as those described in the first embodiment, and the explanations will not be repeated. The device 2 for generating mesh data for design and construction (hereinafter, the device 2 for generating) described here is used when implementing the method for generating mesh data for design and construction (hereinafter, the method for generating) according to the second embodiment. As shown in FIG. 17, the device 2 for generating includes a storage unit 24 and a control unit 25 in addition to the input unit 11, the operation unit 12, and the output unit 13 similar to those of the earth's surface data generating device 1 according to the first embodiment.

[0124] (Storage part) The storage unit 24 stores a generation program 241 for generating mesh data for design and construction (hereinafter, the generation program 241). The generation program 241 describes the flow of the generation process executed by the control unit 25. The storage unit 24 according to this embodiment is configured with a semiconductor memory or a hard disk. Note that when the generation program is not required (for example, when the control unit 25 performs all of the various calculations described below using logic circuits), the generating device 2 does not need to be provided with the storage unit 24.

[0125] (Control unit) The control unit 25 includes a control block including a second acquisition unit 152, an interpolation unit 153, a global ranking setting unit 154, a judgment unit 155, a connection line generation unit 156, a shared connection line generation unit 157, a pairing unit 158, a pair information setting unit 159, a switching line generation unit 160, a surface generation unit 161, a warning information extraction unit 162, and a change unit 164 similar to the control unit 15 of the earth surface data generation device 1 of embodiment 1, as well as an acquisition unit 251, a first generation unit 252, a second generation unit 254, a third generation unit 255, a fourth generation unit 256, a fifth generation unit 257, a sixth generation unit 258, a seventh generation unit 259, and an output processing unit 260.

[0126] The first generating unit 252 generates mesh data of the current structure and the planned structure in the leveling stage. The second generating unit 254 generates mesh data of the structure in the drainage channel construction stage. The third generating unit 255 generates mesh data of the structure in the levee construction stage. The fourth generating unit 256 generates mesh data of the structure in the road construction stage. The fifth generating unit 257 generates mesh data of the structure in the irrigation channel construction stage. The sixth generating unit 258 generates mesh data of the structure after completion. The seventh generating unit 259 generates mesh data of the land other than the current structure of the current construction site from the current topographical information. Note that the mesh data of the land other than the current structure of the current construction site may be generated by the first generating unit 252 instead of the seventh generating unit 259.

[0127] The control unit 25 is composed of a processor. The control unit 25 executes a generation processing method as shown in FIG. 18 according to the generation program 241 stored in the storage unit 24. The generation processing method includes an acquisition step S21, a generation step S22, and an output step S23. Each step in the generation processing corresponds to each step included in the generation method of mesh data for design and construction according to this embodiment. Note that the control unit 25 does not need to include all of the first generation unit 252, the second generation unit 254, the third generation unit 255, and the fourth generation unit 256, and may include one or more according to the 3D mesh of the construction stage to be generated.

[0128] (1. Acquisition step) In the first acquisition step S21, the acquisition unit 251 acquires skeleton line data of the current state structure on the construction site and shape data defining the shape of the current state structure, and skeleton line data of the planned (designed or completed) planned structure and shape data defining the shape of the planned structure. This acquisition unit 251 also has the function of the acquisition unit 151 according to the first embodiment. The current state structure is a structure that already exists. The acquisition unit 251 acquires elevation data, ground data, etc. of the current state structure. The "ground data" of the current state structure is, for example, data indicating the shape and elevation of the surface (base surface) of the base layer on which the cultivation layer is arranged, and the value of the survey data is acquired. The acquisition unit 251 may acquire data of land other than the current state structure (position data, elevation data, ground data, etc.). The land other than the current state structure is, for example, grassland, sandy land, forest, etc. Information on the current state structure and other land is called current state topographical information.

[0129] As described in the first embodiment, a skeleton line is a line that serves as a reference for a structure. Skeleton line data is data that defines a skeleton line, and includes position data, elevation data, ID, type, etc. Shape data is parameter data that defines the shape of a parametric model of a structure, and is specifically as described in the first embodiment.

[0130] A planned structure is a structure that is designed to be newly constructed. "The skeleton line data of the planned structure and the shape data that defines the shape of the planned structure" refers to the skeleton line data and shape data of roads, fields, ridges, waterways, and other structures that are planned to be newly constructed. The skeleton line data and shape data are as described above.

[0131] The acquisition unit 251 according to the present embodiment may acquire three-dimensional point cloud data, and generate skeleton line data, elevation data, and shape data of the current state structure from a plurality of coordinate values ​​(x, y, z) included in the three-dimensional point cloud data. If skeleton line and shape data of the current state structure exist, the data may be acquired. The three-dimensional point cloud data is survey data obtained based on photos taken by UAVs (Unmanned Aerial Vehicles), aircraft, artificial satellites, etc., of the ground surface, and reflected laser light from the ground surface collected by these. In this case, the acquisition unit 251 first reproduces a point cloud based on the acquired three-dimensional point cloud data in a three-dimensional space. Then, the acquisition unit 251 recognizes the current state structure from the reproduced point cloud, and draws the skeleton line L1 of the current state structure on a layer to which the corresponding layer name (current state, work type, and ID) is assigned. The acquisition unit 251 generates shape data of the current state structure and records it in the storage unit 24. Alternatively, if the current state structure is constructed using a parametric model, the acquisition unit 251 may acquire the skeleton line data and shape data thereof. The first generation unit 252 generates skeleton line data and shape data of the current state structure as necessary from the point cloud data acquired by the acquisition unit 251. Note that the recognition of the current state structure and the drawing of the skeleton line L1 may be performed by a user.

[0132] As described above, in the acquisition step S21, the acquisition unit 251 also acquires skeleton line data of the planned structure and shape data that defines the shape of the planned structure. Hereinafter, the "planned structure" is also simply referred to as a "structure." Specifically, the acquisition unit 251 acquires skeleton line data and a layer name (ID) of each structure stored as design data in the storage unit 24. The acquisition unit 251 also acquires shape data linked to the skeleton line data. Furthermore, the acquisition unit 251 associates the shape data with the ID.

[0133] For example, when the construction stage is a drainage channel construction stage, multiple excavation cross sections may be set following the construction stage. Specifically, for example, in the construction of a drainage channel, a temporary drainage channel is first constructed for drainage during construction work. This is called primary excavation. In order to perform this primary excavation, the second generation unit 254 generates a primary excavation mesh having position information for the primary excavation. The primary excavation mesh may include a small step. Based on this information, the ICT construction machine can perform excavation work on a part higher than the current topography. This primary excavation mesh is an uphill slope as seen from the drainage channel since it is mainly used for excavation. The excavation slope length may have a certain height higher than the surrounding current topography, the excavation slope length may be specified by a parameter, or a ground surface mesh between structures may be generated as in the first embodiment. The temporary drainage channel allows rainwater to be quickly drained during the construction period. Then, after the field preparation is completed, the ICT construction machine lays foundation materials such as gravel using the secondary excavation mesh generated by the second generation unit 254 in order to install a concrete flume, and installs the concrete flume. After that, the completed mesh is used to shape the surroundings of the waterway and the slopes. Although there are three steps in the above example, the construction cross section determined by the shape parameters may be increased as necessary.

[0134] FIG. 19 is a schematic diagram showing an example of shape data (shape parameters) of the primary excavation and secondary excavation of a drainage channel. In the drainage channel construction stage or the irrigation channel construction stage, the shape data includes basic parameters, slope parameters, berm parameters, and ICT construction parameters. The primary excavation parameters define the cross-sectional shape of the temporary drainage channel (earthen waterway) after the primary excavation. The secondary excavation parameters define the cross-sectional shape after the secondary excavation. The basic parameters include the width of the structure (concrete flume, etc.), the height of the structure, the width of the foundation concrete, the height of the foundation concrete, the height of the spread mortar, and the distance from the skeleton line to the left and right shoulders. The slope parameters include the gradient of the right slope and the gradient of the left slope. The berm parameters include the presence or absence of berms in the middle of the slope, and if there are berms, the number of berms installed, the installation height of each berm, and the width of each berm. The ICT construction parameters include the primary excavation parameters and the secondary excavation parameters. The primary excavation parameters include the height of the construction base from the skeleton line, the excavation width, the excavation slope length, the excavation gradient, and the excavation mesh length, as shown on the left side of Fig. 18. The secondary excavation parameters include the bed excavation height, bed excavation width, bed excavation gradient, and the excavation slope length, as shown on the right side of Fig. 18.

[0135] The data required for the construction stage of the land leveling stage are the mesh of the base surface layer and the mesh of the cultivated surface layer. The height of the mesh of the cultivated surface layer is the altitude of the field. The surface layer that is the thickness of the cultivated layer below the altitude of the field is the base surface layer. Therefore, it is possible to generate the mesh of the cultivated surface layer and the base surface layer by simply specifying the thickness of the cultivated layer. The shape data includes the thickness of the cultivated layer and the expected subsidence amount. The "expected subsidence amount" is the amount of subsidence that is expected to occur during construction due to the travel of construction machinery, etc., until the completion of the development of the field and the handover to the farmer. Note that each field may have different subsidence characteristics. Therefore, the acquisition unit 251 may acquire the expected subsidence amount for each of the multiple divided areas. The expected subsidence amount is used to calculate the amount of soil required when leveling the field.

[0136] When the construction stage is the road construction stage, the acquisition unit 251 first acquires the pavement type. Then, the shape data corresponds to the pavement type. The pavement type includes, for example, gravel pavement, asphalt pavement, concrete pavement, and other pavements. For example, when the pavement type is gravel pavement, the road has, from the bottom, a road body, a roadbed, and a surface layer, as shown in the upper part of FIG. 20. In this case, the meshes that need to be generated are, from the bottom, a road body surface mesh, a roadbed surface mesh, and a surface layer mesh. When the pavement type is asphalt pavement, the road has, from the bottom, a road body, a roadbed, a lower subgrade, an upper subgrade, a base layer, and a surface layer, as shown in the lower part of FIG. 20. In this case, the meshes that need to be generated are, from the bottom, a road body surface mesh, a roadbed surface mesh, a lower subgrade surface mesh, an upper subgrade surface type, a base layer surface mesh, and a surface layer surface mesh. The shape data includes the thickness of each of these layers. Sectional construction, which will be described later, is required for each such layer. In this case, the shape data acquired in the acquisition step includes shape data required for the sectional construction stage. Then, in the generation step, mesh data of at least one of the current structure and the planned structure scheduled for each construction stage of the sectional construction of each layer is generated.

[0137] FIG. 21 is a schematic diagram showing an example of a setting screen for shape data for generating construction mesh data in a drainage channel construction stage. The second acquisition unit 152 according to this embodiment may acquire, for example, numerical data input by a user to an input screen as shown in FIG. 21 as shape data. Then, the second acquisition unit 152 links the acquired shape data to the corresponding skeleton line. The linking method by the second acquisition unit 152 is the same as the linking method by the second acquisition unit 152 of the earth surface data generation device 1 according to the first embodiment. Note that the setting screen for shape data is not limited to the configuration and input items shown in FIG. 21.

[0138] (Generation step) After acquiring the skeleton line data and shape data of the current structure and the planned structure, the process proceeds to the generation step S22. In the generation step S22, each generation unit generates mesh data of at least one of the current structure and the planned structure scheduled for each construction stage using the skeleton line data and shape data of each of the current structure and the planned structure. Specifically, in the generation step S22, at least one of the generation units from the first generation unit 252 to the seventh generation unit 259 generates mesh data of the structure or the land other than the current structure. For example, in the generation step according to this embodiment, mesh data of the surface of the structure or the construction surface in the section construction stage is generated based on the acquired shape data. In addition, the mesh displayed based on the mesh data according to this embodiment is a triangular mesh. However, the shape of the mesh is not limited to this. That is, the mesh displayed based on the mesh data may be a quadrangle or the like.

[0139] In the generation step S22, the first generation unit 252 generates mesh data of the current structures and planned structures of the construction site (construction site), and the seventh generation unit 259 generates mesh data of the land other than the current structures of the construction site from the current topographical information. When the current construction site is a field, two meshes, a base layer and a cultivated layer, are required as mesh data of the current structures. The cultivated layer exists from the ground surface to a specified depth, and the base layer exists below the cultivated layer. In addition, the mesh data of the current construction site may include flumes of irrigation channels, pavement, etc., in addition to the base layer and cultivated layer. These structures are removed during construction, so by understanding their amount, the amount of industrial waste generated by construction can be estimated.

[0140] In the generating step S22, the first generating unit 252 to the sixth generating unit 258 generate mesh data of the structure planned for each construction stage from various data of the current structure and various data of the planned structure. The "mesh data of the structure" is generated using the skeleton line data and the shape data. Specifically, it is generated using the same method as the method used by the earth surface data generating device 1 according to the first embodiment to generate the 3D model. The "construction stage" includes any of the following: land leveling (field) construction, drainage channel construction, ridge construction, road construction, and irrigation channel construction. The "construction" may also include the type of work to bury underground structures such as buried pipes for passing sewerage, water supply, and gas pipes, and box culverts for passing subways, underground electric wires, roads, etc. In this case, the construction is performed, for example, by the second generating unit 254 generating an excavation mesh of a buried trench in the same manner as the drainage channel, and after the ICT construction machine excavates the buried trench, the underground structure is placed in the buried trench and backfilled. The "construction stage" also includes the stage after completion. The mesh data of the structure generated in the generating step according to this embodiment is design mesh data of the surface of the construction target at each construction stage.

[0141] In addition, each construction stage may include a further subdivided section construction stage. For example, in the construction of a field, there is a section construction for excavating to the top surface of the base layer or stripping off the existing cultivated layer for the planned range of the field, and a section construction for constructing a new cultivated layer on the base layer. In such a case, each generation unit generates mesh data of the construction surface in the section construction stage of each structure. That is, in the section construction for excavating to the base surface or stripping off the existing cultivated layer, the base surface is the construction surface of the section construction, and in the section construction for constructing a new cultivated layer on the base surface, the surface (cultivated surface) of the new cultivated layer is the construction surface of the section construction. Therefore, it is necessary to generate mesh data of the construction surface of each section construction. In addition, in the construction stage of a road, as described above, the road body, roadbed, lower subgrade, upper subgrade, base layer, and surface layer are constructed (constructed) in that order. In that case, a mesh of the construction surface of the necessary section construction is generated. Below, we will explain the specific construction procedures for several construction stages and the generation of the necessary construction mesh data, including section construction.

[0142] ·Drainage works (drainage construction) Drainage works are carried out at the very beginning of construction work to handle rainwater generated during the construction period. Specifically, first, primary excavation is carried out to construct a temporary drainage channel. The surface of the primary excavation area is soil. In other words, the temporary drainage channel becomes an earthen channel. After construction such as ground leveling and road construction is completed, secondary excavation is carried out. In secondary excavation, excavation is carried out up to a floor for constructing the foundation (crushed stone or dry-mixed concrete, etc.). The foundation is laid on top of that, and the body of the channel is installed on the foundation. After the body is installed, the area around the body is backfilled, the surrounding slopes are shaped, etc., and a proper drainage channel (open channel) is constructed. In addition, if necessary, a cover is placed on the body to make it an open or closed channel. This method can also be applied to underground pipelines by changing the concrete flume to a pipeline.

[0143] In order to have the ICT construction machine perform the primary excavation and secondary excavation in the drainage work, mesh data of the structure in the drainage channel construction stage is required. When generating mesh data of the structure in the drainage channel construction stage, in the generation step S22, the second generation unit 254 generates mesh data of the structure in the drainage channel construction stage. Specifically, the second generation unit 254 generates mesh data showing the surface shape of the construction site after the primary excavation is completed, mesh data showing the surface shape of the construction site after the secondary excavation, and mesh data including the surface of the drainage channel's skeleton (after the drainage work is completed). The mesh data may include not only the mesh of the outer surface that appears on the ground surface, but also the mesh data of the surface of the skeleton on the underground side. The drainage channel is specified by skeleton line data and shape data, but if the position of the skeleton line (skeleton line data) is changed, the construction mesh is changed accordingly. Also, if the shape of the drainage channel (shape data) is changed, the construction mesh is changed accordingly. This is similar for other structures.

[0144] ·Land preparation work (land preparation work) In land leveling work, for example, when carrying out work to level multiple small fields into one large field, the cultivated layer of each small field is first stripped off. The ICT construction machine recognizes the position of the base layer and strips off the cultivated layer while controlling the blade (blade) so that it does not go below the base layer. The stripped cultivated soil is then stored in another location. If the existing field is to be used as is, there is no need to strip off the cultivated layer. After that, cutting and filling are performed on each base layer of each small field with different altitudes to create a single base layer with the same altitude. The ICT construction machine recognizes the height of the new base layer to be built, cuts off the soil that exists above the recognized height, and moves the cut soil to places below the recognized height. Next, if the field is a rice paddy, a ridge is created on top of the base layer. The ICT construction machine may create an embankment larger than the planned ridge and build the ridge by cutting the embankment so as not to excavate inside the recognized surface shape. The removed cultivated soil is then replaced to create a new cultivated layer. The ICT construction machine recognizes the height of the new cultivated layer and performs leveling work so that the surface of the cultivated layer is at the recognized height.

[0145] In the case where mesh data of the current state structure is required in the ground preparation stage to allow the ICT construction machine to perform the above ground preparation work, the first generating unit 252 generates mesh data of the current state structure and the planned structure in the ground preparation stage. In addition, for land other than the current state structure, the current state topographical information may be used. In the above ground preparation work, there are section construction in which excavation or filling is performed from the surface of the current state structure and the land other than the current state structure to the base layer, section construction in which a ridge is created in the case of a paddy field, and section construction in which a cultivated layer is created. Therefore, the first generating unit 252 generates mesh data of the construction surface of each section construction. Specifically, the first generating unit 252 generates mesh data of the surface of the base layer at the construction position of the field using the skeleton line representing the polygon of the field and the shape data. The mesh data of the surface layer of the cultivated layer is generated using the skeleton line data and the shape data of the field. Furthermore, when the field is a paddy field, the first generating unit 252 also generates mesh data of the surface of the ridge using the skeleton line data and shape data of the ridge.

[0146] The first generating unit 252 also calculates the amount of cultivated soil required to create the cultivated layer of the planned field based on the mesh data of the surface of the current base layer and the mesh data of the surface of the cultivated layer. Specifically, the volume of the space between the surface of the base layer and the surface of the planned cultivated layer is the volume of the required cultivated soil. Meanwhile, the volume of the space between the surface of the current base layer and the surface of the current cultivated layer is the volume of the current cultivated soil. If there are multiple current cultivated layers, the total value of these is used. The volume obtained by subtracting the volume of the current cultivated soil from the volume of the required cultivated soil is the volume of the newly required cultivated soil, which is the amount of soil. This is the amount of soil required for the cultivated layer of the planned field.

[0147] However, when performing land leveling work, the field subsides as the construction machine travels. If the work is performed while ignoring this subsidence, a situation occurs in which the amount of soil required to develop the field so that the surface height of the cultivated layer is a predetermined height is insufficient. For this reason, in designing the field, it is necessary to predict this subsidence and accurately predict the amount of cut and filled soil in advance. Therefore, in the generation step according to this embodiment, the first generation unit 252 generates mesh data of the surface of the base layer, taking into account the expected amount of subsidence (anticipated amount of ground subsidence) that will occur during land leveling work. Specifically, when performing soil volume calculation, the surface height of the current base layer is lowered by the height of the predicted amount of subsidence to calculate the soil volume. Alternatively, the surface height of the planned field may be calculated by raising it by the height of the predicted amount of subsidence.

[0148] ·Round construction (Round construction) When generating mesh data of a structure in the ridge construction stage, in the generation step S22, the third generation unit 255 generates mesh data of the structure in the ridge construction stage. In the generation step S22 according to this embodiment, the third generation unit 255 generates mesh data of the surface of the ridge to be placed on the base layer at the field construction position. The third generation unit 255 according to this embodiment generates mesh data of the surface of the ridge by dividing it into mesh data of the inner top end, mesh data of the outer top end, mesh data of the inner slope, and mesh data of the outer slope, for example. These mesh data can be integrated using dedicated software to form mesh data of the surface of one ridge. The integration of this mesh data may be performed by the third generation unit 255.

[0149] Fig. 22 is a schematic diagram showing an example of a screen on which mesh data for the base surface, cultivated surface, and ridges used in field leveling work is generated. The procedure for generating such mesh data and its use are explained below.

[0150] 2201 in FIG. 22 shows the cross section and elevation of the bedrock surface, cultivated surface, and ridge of the current field acquired by the generating device 2 of mesh data for design and construction. In the parametric model set for each field in the current state, the user can input the thickness (t) of the cultivated layer. Based on this, the first generating unit 252 generates mesh data of the bedrock layer below the current field scene by the thickness of the cultivated layer. The current ridge mesh data is left. The upper side of the figure is the 2D plan view (input data) to be read, and the elevation value of the field scene is written in the upper part, and the thickness of the cultivated layer is written in the lower part. The lower part is what is read by the generating device 2 of mesh data for design and construction (same below). The elevation of the field scene and the thickness of the cultivated layer are reflected in the 3D model. The thickness of the cultivated layer may be written in the 2D plan view in advance, or the user may input it later.

[0151] When ICT construction machinery (mainly bulldozers) is provided with mesh data of the current base layer (base surface) and mesh data of the ridge (surface), the ICT construction machinery can recognize the position of the base layer and refer to the mesh data to control the bulldozer's blade (blade) so that it does not drop below the base layer, and remove the soil in the cultivated layer.

[0152] 2202 to 2204 in Figure 22 show the mesh positions of the base surface, cultivated surface, and ridges of the planned field. 2202 displays the mesh position of the base surface to be created. In the parametric model set for each field in the design, the user can input the thickness of the cultivated layer. Alternatively, it may be specified in advance in a 2D plan view. This generates mesh data for the base surface below the designed field scene by the thickness of the cultivated layer. The mesh data for the ridges is not used at this stage. The elevation of the base surface to be created is determined taking into account the volume of earthwork to be filled and cut. The elevation of the base surface may be set arbitrarily by the user.

[0153] After the ICT construction machinery has stripped away all the cultivated soil in the field, mesh data of the planned foundation surface is provided to the ICT construction machinery (mainly a bulldozer).The ICT construction machinery can then recognize the location of the new foundation layer to be constructed, and will then excavate the areas higher than that location and move the excavated soil to lower areas.

[0154] 2203 is a display image showing the position of the mesh of the ridge to be constructed. In the parametric model set for each field in the design, the user can input the shape of the ridge. In this way, the third generating unit 255 generates a 3D mesh of the designed ridge. Although not shown in 2203, the outer top and outer slope of the ridge may be included.

[0155] Once the construction of the new base layer is complete, mesh data of the planned ridge is provided to ICT construction machinery (mainly backhoes). The backhoe creates embankments larger than the planned ridge, and then the backhoe's blade uses the position information from the mesh data of the ridge to scrape away the soil and build the ridge, being careful not to excavate the inside of the ridge.

[0156] 2204 is a display image showing the position of the mesh of the cultivated layer to be developed. In the parametric model set for each field in the design, the thickness of the cultivated layer is set in the plan, and the first generating unit 252 generates a model of the field scene having mesh data of the base layer and the cultivated layer.

[0157] Once the ridges are completed by the ICT construction machinery, the stockpiled cultivated soil is transported by a carrier dump or similar, and mesh data of the planned cultivated layer is provided to the ICT construction machinery (mainly a bulldozer). The bulldozer can recognize the height of the new cultivated layer, so it carries out leveling work to the specified height.

[0158] ·Road construction (road construction) When generating mesh data of a structure in a road construction stage, in a generation step S22, the fourth generation unit 256 generates mesh data of the structure in a road construction stage. In the generation step according to the present embodiment, the fourth generation unit 256 generates at least one of road surface mesh data, roadbed surface mesh data, lower layer roadbed surface mesh data, upper layer roadbed surface mesh data, base layer surface mesh data, and surface surface (road surface) mesh data in road construction. Note that the fourth generation unit 256 does not need to generate all of these mesh data, and it is sufficient to generate at least one of them.

[0159] ·Irrigation canal construction (Irrigation canal construction) When generating mesh data of a structure in the irrigation channel construction stage, in the generation step S22, the fifth generation unit 257 generates mesh data of the structure in the irrigation channel construction stage. The method of generating mesh data of a structure in the irrigation channel construction stage is basically the same as the method of generating mesh data of a structure in the drainage work construction stage. If the position of the skeleton line is changed, the construction mesh is changed accordingly.

[0160] In the generation step S22, the sixth generation unit 258 also generates mesh data of the completed structure. The completed mesh data is generated using the field elevation value after land grading, which is set by comprehensively considering the amount of fill and cut in the construction area, the required height from the bottom of the drainage channel, and the required height from the bottom of the irrigation channel. The completed mesh data may be reviewed and changed from time to time before or during construction in response to requests from local residents and the amount of land subsidence. The elevations of the field areas to be land grading and each field area are determined by taking into consideration the elevations of the drainage channel and irrigation channel, the amount of fill and cut, the difference in elevation between the road and the rice field surface, and the economics of construction costs. If various data (skeleton line data and / or shape data) are changed in the planning stage, each generation unit regenerates the design mesh data together with the mesh data for each construction stage. If various data are changed in the construction stage, each generation unit regenerates the design mesh data together with the mesh data for each construction stage.

[0161] When the first generation unit 252 to the seventh generation unit 259 generate mesh data, they link the mesh data to an ID assigned to each structure (e.g., a field, etc.). As a result, each mesh data is managed as a construction surface mesh (e.g., a cultivated surface mesh, a base surface mesh, a ridge mesh, etc.) for the sectional construction of the structure. When the structure is a field and one field ID corresponds to multiple fields, it becomes necessary to manage a mesh for each field. For this reason, a branch number is assigned to each field corresponding to the same field ID, and the mesh data is linked to the branch number.

[0162] (13. Output Step) After the various mesh data are generated, the process proceeds to an output step S23. In the output step S23, the output processing unit 260 outputs the generated mesh data to the output unit 13. This output processing unit 260 also has the function of the data output processing unit 163 according to the first embodiment. If the output unit 13 is a terminal to which a cable leading to a monitor is connected, or the monitor itself, the 3D mesh is displayed on the monitor in this step. If the output unit 13 is a communication unit that communicates with other devices, or a drive that writes 3D model data to media, the mesh data is provided to other devices, etc. in this step.

[0163] The following are some of the characteristics of the output mesh. First, the meshes are managed according to the construction stage. Specifically, mesh groups are linked to a certain skeleton line in descending order of size. Furthermore, for a drainage channel, a concrete flume mesh, a ground surface mesh (divided into left and right) from the outer edge of the concrete flume to the connection line, and a ground surface mesh or slope mesh (also divided into left and right) generated from the connection line are generated and output. In addition, a ground surface mesh or slope mesh generated from the end connection line, and a mesh for ICT construction used for each construction stage are generated and output. Furthermore, data for the completed mesh is saved as several parts, such as left and right meshes, and output. These meshes are classified into at least one category by skeleton line, and multiple categories within the skeleton line. Since they are classified in this way, the user can select and use the mesh he needs.

[0164] [Action and Effect] According to the generating device, generating method, and generating program described above, a 3D model is generated using skeleton lines and shape data, and a construction mesh can also be created. In other words, when the skeleton line data or shape data of a structure is changed, the mesh data for each construction stage is changed accordingly. This reduces the effort required to generate and change the 3D mesh after completion of the field and the 3D mesh for each construction stage. In addition, since the mesh after completion and the mesh at the construction stage are linked, it is expected that human errors during work will be reduced. In the conventional technology, the 3D model is generated individually by direct modeling, but in this embodiment, in addition to generating the ground surface between the structures by the parametric model, construction mesh data and completed mesh data can also be generated.

[0165] [Modifications of the first and second embodiments] The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope of the claims.

[0166] For example, some of the functions of the above control blocks may be performed by devices other than the earth's surface data generating device 1 and the device 2 for generating mesh data for design and construction.

[0167] At least one of the earth surface data generating program 141 and the design and construction mesh data generating program 241 may be recorded in one or more computer-readable recording media, not temporarily. The recording media may or may not be included in the earth surface data generating device 1 or the design and construction mesh data generating device 2. In the latter case, the programs may be supplied to the earth surface data generating device 1 or the design and construction mesh data generating device 2 via any wired or wireless transmission medium.

[0168] In addition, some or all of the functions of each of the control blocks can be realized by a logic circuit. For example, an integrated circuit in which a logic circuit that functions as each of the control blocks is formed is also included in the scope of the present invention. In addition, the functions of each of the control blocks can be realized by, for example, a quantum computer. The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope of the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention.

[0169] [Embodiment 3] (Approach road data generation device) Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. FIG. 23 is a block diagram showing the configuration of an approach road data generating device 4 according to this embodiment 3. The approach road data generating device 4 is a device that generates an approach road that satisfies design standards or an approach road that matches shape data set by a user according to the shape and layout of other structures. The approach road data generating device 4 particularly generates rectangular approach roads. A rectangular approach road is an approach road in which the approach route of the slope section is limited to one direction, and is a name used to distinguish it from a cone-shaped approach road that connects the road and the approach destination with a circular or elliptical ramp.

[0170] The approach road according to this embodiment is generated in association with a previously generated structure model after a structure model other than the approach road is generated. The structure model other than the approach road is, for example, a road, a ridge, a waterway, etc. In other words, data of a structure previously generated to generate an approach road model is acquired, and an approach road model adapted to the structure model is generated. Therefore, for example, even if the shape of a road or a ridge is changed, an approach road adapted to the changed shape can be mechanically generated.

[0171] 23, the approach road data generating device 4 includes a control unit 45, a storage unit 44, an input unit 11, and an output unit 13. The control unit 45 controls the entire approach road data generating device 4. The storage unit 44 stores an approach road data generating program 441.

[0172] The input unit 11 is composed of, for example, a terminal to which a cable linking to a device in which data is stored is connected, a communication unit that communicates with the device in which data is stored via wired or wireless communication, or a drive that reads a medium in which data is stored. In addition to the input unit 11, the approach path data generating device 4 may also include an operation unit 12 (not shown). The operation unit 12 accepts various input operations by a user. The operation unit 12 may include a keyboard, a mouse, a touch panel, a monitor, or a dedicated device.

[0173] The output unit 13 outputs the generated approach road data (created / corrected numerical data, completed image data, etc.). The output unit 13 is composed of, for example, a terminal to which a cable leading to a monitor is connected, a communication unit for communicating with other devices by wire or wirelessly, or a drive for writing data of ground surface information to media. The output unit 13 may be the monitor (display device) itself that displays the approach road information.

[0174] The control unit 45 includes a structure data acquisition unit 450, an approach road skeleton line data acquisition unit 451, a position information acquisition unit 452, a shape data acquisition unit 453, and a model data generation unit 454. The model data generation unit 454 includes a cross slope elimination section generation unit 4541, a horizontal section generation unit 4542, and a slope section generation unit 4543. The control unit 45 may further include a determination unit 455, a corner cutting section generation unit 456, a rubbing slope generation unit 457, an error display generation unit 458, and an output processing unit 459.

[0175] The structure data acquisition unit 450 acquires the skeleton lines and shape data (connecting lines, etc.) of structures including roads. Structures including roads include roads, structures at the approach destination, and structures that exist between the roads and the approach destination. The roads referred to here refer to roads that have an entrance to an approach road. Approach roads are not included in structures including roads. In other words, the structures in this case refer to structures that were designed (i.e., for which a parametric model was generated) before the approach road was designed.

[0176] The approach road skeleton line data acquisition unit 451 acquires the skeleton line of the approach road drawn by the user from (the skeleton line of) the road to (the polygon of) the approach destination. The skeleton line of the approach road is specified by the user as a polyline connecting at least two points including an arbitrary point on the skeleton line of the road and an arbitrary point in the polygon of the approach destination. In other words, there may be a turning point between an arbitrary point on the skeleton line of the road and an arbitrary point in the polygon of the approach destination. The skeleton line of the approach road is drawn by the user specifying these points. More specifically, the user generates an intersection on the skeleton line of the road on the layer of the road having the same ID. This intersection becomes the starting point of the skeleton line of the approach road. The user draws the skeleton line of the approach road from the intersection to the polygon of the approach destination (for example, a field). At this time, the skeleton line of the approach road may be of a different line type such as a dashed line, or the line color may be changed. The approach road skeleton line data acquisition unit 451 reads this vector information drawn by the user and determines which road skeleton line the approach road is generated from and which field polygon the end point of the approach road's connection line is included in. The approach road skeleton line may be created in a layer with the same ID as the road. Even if the approach road skeleton line data exists in a layer with the same ID as the road, it is possible to distinguish between the road skeleton line and the approach road skeleton line by recognizing that the data has a different line type or color from the road skeleton line.

[0177] The position information acquisition unit 452 acquires position information of structures including roads. The structures including roads are as described above. That is, the position information acquisition unit 452 acquires position information of roads, structures at the approach destination, structures existing between the road and the approach destination, and the like. The structures existing between the road and the approach destination are, for example, ridges, waterways, and the like. The position information requires acquisition of position information of the slope lines of ridges and waterways (which ultimately coincide with the connection lines, but a place other than the slope lines can also be used as the connection lines) in addition to position information of the connection lines of the roads. In particular, information on the relationship between the skeleton lines of the approach roads and these connection lines, as well as the positional relationship between the connection lines of the approach roads and these connection lines, is also required. The position information is three-dimensional coordinate position information. The coordinate position information includes the elevation of the road and the elevation value of the surface of the polygon of the approach destination.

[0178] The shape data acquisition unit 453 acquires shape data that specifies the approach road set (input) by the user. The shape data includes the longitudinal gradient of the slope section. The user sets the longitudinal gradient so that it is equal to or less than the limit value. The limit value is a value that is specified by laws, regulations, etc. and that must be observed. On the other hand, a value that the user sets according to the situation is called a set value. The set value may be the same as the limit value. Hereinafter, both may be referred to as the "limit value or set value". The slope section needs to be designed with a longitudinal gradient equal to or less than this limit value. The cross gradient of the slope section may be the set value set by the user. The cross gradient at the entrance of the cross gradient elimination section is the longitudinal gradient of the entrance road. Therefore, the cross gradient of the cross gradient elimination section is designed to gradually approach zero from the longitudinal gradient of the entrance road.

[0179] Specifically, the cross-slope elimination section may be designed, for example, in the following procedure. First, the user (designer) sets the attachment angle of the approach road (longitudinal gradient of the road at the entrance of the cross-slope elimination section), the longitudinal gradient of the cross-slope elimination section, and the length of the cross-slope elimination section. Based on these set values, the cross-slope elimination section generation unit 4541 described later generates a 3D model of the cross-slope elimination section. A vehicle running simulation is performed on this 3D model when entering and exiting the cross-slope elimination section, and it is verified whether the roll angle, pitch angle, and twist angle are sufficient to prevent vehicle running. If the verification result shows that these angles are greater than the limit value or the set value, the shape data of the approach road is set again, and trial and error is repeated until the roll angle, pitch angle, and twist angle satisfy the limit value or the set value. In this manner, an appropriate shape of the approach road may be obtained.

[0180] The model data generating unit 454 generates data of a model of the approach road using the skeleton line and shape data of the approach road. The functions of a cross gradient eliminating section generating unit 4541, a horizontal section generating unit 4542, and a slope section generating unit 4543 included in the model data generating unit 454 will be described later.

[0181] The approach road is defined by, for example, a skeleton line connecting the road skeleton line to the field and left and right connecting lines spaced a predetermined distance from the skeleton line. The start point of the approach road is the connecting line of the road. There may be structures such as ridges and waterways between the road and the field. As described above, the structure data acquisition unit 450 acquires the connecting lines of existing structures such as ridges and waterways. In this case, the approach road is an approach road that continues to the field across the ridges and waterways. The shape data that determines the shape of the approach road include the road width, the length of the cross-slope elimination section, the longitudinal gradient of the cross-slope elimination section, the length of the horizontal section, the gradient of the slope section, the length of the corner cut section, the gradient of the slope and the rubbing slope of each section, etc. These shape data are appropriately set by the user based on design information, various gradient limit values, etc. In addition, the user can change various setting values ​​on the data input screen and display the resulting changes in the shape of the structure to check the validity of the setting values.

[0182] The determination unit 455 determines whether the access road is an access road for entering two or more fields. Usually, an access road is designed to enter one field, but in some cases, it is designed to be able to enter two or more adjacent fields. The determination unit 455 may determine, for example, whether the ends of the connection lines on both sides of the access road reach the same field. If the connection lines on both sides do not reach the same field (if not), the access road is determined to be an access road for entering two or more fields.

[0183] The cross-slope elimination section generating unit 4541 generates data of a cross-slope elimination section to be placed at a position of the approach road that contacts the road, based on the shape data acquired by the shape data acquiring unit 453. The data of the cross-slope elimination section is the discretized elevation and coordinates of the connecting line from the entrance to the end of the cross-slope elimination section. Generating data of the cross-slope elimination section is also called "generating a cross-slope elimination section". The same applies below. The cross-slope elimination section may be straight or curved, but the cross-slope and longitudinal gradient are equal to or less than a predetermined limit value or set value. The cross-slope elimination section may be not only a downhill section toward a field, but also an uphill section. When entering an approach road from a road with a longitudinal gradient, the front and rear wheel axles of the vehicle are not parallel, and a twist occurs. If the twist angle of the vehicle exceeds the allowable range, one of the rear wheels will lift off the ground, which is considered dangerous. For this reason, a section is provided in which the twist is gradually eliminated so that the vehicle proceeds to the approach road without exceeding the allowable range. This section is called the cross-slope elimination section. The cross slope at the end of the cross slope elimination section is zero (horizontal). If the road surface at the entrance to the approach road is horizontal, it is not necessary to provide a cross slope elimination section. Also, there may be cases where the longitudinal slope of the road is too large to provide an entrance to the cross slope elimination section. In such cases, the entrance to the cross slope elimination section is provided at a point on the road where the longitudinal slope is smaller.

[0184] The cross slope elimination section may have a predetermined downward or upward slope. The length of the cross slope elimination section is set to a length required for reducing to a predetermined range the twist of the vehicle axle caused by the slope of the road surface at the entrance of the approach road. Furthermore, if a structure exists between the road and the approach destination, the cross slope elimination section may be generated at a position higher than the elevation of the structure. Examples of structures that exist between the road and the approach destination include rice levees and waterways. Hereinafter, structures that exist between the road and the structure at the approach destination are also referred to as obstacles.

[0185] The slope section is generated from the cross-slope elimination section or the horizontal section to a position where the surface of the structure at the entrance is reached at a predetermined slope gradient (longitudinal gradient of the slope section). The slope section generation unit 4543 generates data of the slope section from the cross-slope elimination section toward the field based on the shape data. The data of the slope section is the discretized elevation and coordinates of the connecting line from the entrance to the end of the slope section. The slope section may be straight or curved, but the longitudinal gradient must be equal to or less than a predetermined limit value. The length of the slope section is generated from the elevation of the start point of the slope section, the elevation of the end (field), and the set value of the longitudinal gradient. When the user draws the skeleton line of the approach road, the user may draw any one point of the skeleton line of the road and any one point within the polygon when the polygon of the entrance is viewed in plan. The end point of the skeleton line of the approach road drawn by the user does not necessarily have to be drawn to have the same elevation as the entrance. For example, the slope section generating unit 4543 determines the destination (entrance destination) of the skeleton line from the end point of the skeleton line of the entrance road drawn by the user. Then, the slope section generating unit 4543 calculates and corrects the elevation of the end point of the skeleton line so that it has the same elevation as the surface elevation of the entrance destination. Since the gradient of the skeleton line of the entrance road is fixed and the elevation of the entrance of the slope section is obtained by sequentially calculating from the elevation of the connecting line of the road, the slope section generating unit 4543 can calculate and set how far the skeleton line should be extended to reach the same elevation as the entrance destination.

[0186] The horizontal section generating unit 4542 generates a horizontal section between the cross gradient elimination section and the slope section. The horizontal section is a section for the vehicle to face the slope section before the vehicle enters the slope section that descends to the field. In other words, the horizontal section is a section for moving the vehicle so as to head in a straight line or for reducing the twist angle occurring in the vehicle.

[0187] The output processing unit 459 generates image data that visualizes the generated cross slope elimination section and slope section. The output processing unit 459 may generate image data that visualizes horizontal sections, corner cutting sections, and other structures as well. The output processing unit 459 also generates image data of a display area (input screen) for shape data and the like input by the user.

[0188] The corner cutting part generation unit 456 generates a corner cutting part at the position where the road and the approach road intersect. A corner cutting part is an extended part of the road shoulder, and is provided to make it easier for a vehicle to turn when entering the approach road from the road, or when exiting the approach road from the approach road. The corner cutting part is generated by adding it after the model of the parts other than the corner cutting part is procedurally generated. The corner cutting part is generated by setting the corner cutting length on the left and right sides of the entrance toward the approach direction of the approach road.

[0189] The rubbing slope generator 457 generates a slope from the connection line of the approach road including the corner cut. The rubbing slope is a slope that is rubbed against the outermost edge line including the generated corner cut. The rubbing slope is generated up to the position where it intersects with the existing mesh.

[0190] When an error occurs in the generated data, the error display generating unit 458 generates an error display indicating that the error has occurred and / or the location where the error has occurred. The generated error display is output to a display device or the like by the output processing unit 459. For example, the error display generating unit 458 may generate an error display indicating that an error has occurred when the generated approach road interferes with another structure or when at least one of the two connecting lines of the approach road does not reach the field. The error display generating unit 458 may also generate an error display when the generated cross slope elimination section, slope section, etc. exceeds a predetermined slope limit value or set value.

[0191] According to the approach road data generating device 4 having the above-mentioned configuration, an approach road that satisfies the design standard values ​​or that conforms to the shape data set by the user can be generated between the road and the approach destination according to the shapes and layout conditions of other structures.

[0192] (Entry route data generation method) FIG. 24 is a flowchart showing the flow of the approach road data generation method S40 executed by the approach road data generation device 4. As shown in FIG. 24, the approach road data generation method S40 includes steps S41 to S49. The skeleton line of the approach road is specified (drawn) by the user as a polyline connecting at least two points including an arbitrary point on the skeleton line of the road and an arbitrary point in the polygon of the approach destination. If the approach road is not straight but curved, a skeleton line bent at a turning point on the way is drawn. The terms used in the following steps are as explained in the explanation of the configuration of the approach road data generation device 4.

[0193] Step S41 is a structure data acquisition step for acquiring skeleton lines and shape data of structures including roads. The structures including roads are as described above. The structure data acquisition step is executed by the structure data acquisition unit 450.

[0194] Step S42 is a position information acquisition step for acquiring position information of structures including roads. The position information acquisition step is executed by the position information acquisition unit 452.

[0195] Step S43 is an approach road skeleton line data acquisition step for acquiring a skeleton line of an approach road from a road to an approach destination, the skeleton line being drawn by the user. The approach road skeleton line data acquisition unit 451 executes the approach road skeleton line data acquisition step.

[0196] In step S44, if the entry destination is a field, a judgment step 421 may be performed to judge whether or not the acquired skeleton line of the entry road is an entry road that crosses two fields. The judgment step is executed by the judgment unit 455. The judgment unit 455 may judge whether or not the ends of the connection lines on both sides of the entry road reach the same field, for example, by referring to the position information acquired in the position information acquisition step. Details of the judgment are as described above.

[0197] Step S45 is a shape data acquisition step for acquiring shape data defining the entry road input by the user. The shape data acquisition step is executed by the shape data acquisition unit 453.

[0198] Step S46 is a model data generating step of generating model data of the approach road using the skeleton line and shape data of the approach road. The model data generating step is executed by the model data generating unit 454.

[0199] Step S47 is an error display step for generating an error display when a predetermined error occurs. A specific example of the case where an error display is displayed is as described above. The error display generating step is executed by error display generating unit 458.

[0200] Step S48 is a correction step in which the user performs correction processing on the error location as necessary. The correction step is executed by each generation unit of the model data generation unit 454 based on the correction data input by the user. Note that this step may be omitted if no approach road is provided.

[0201] Step S49 is an output processing step for generating image data of the generated structure (the approach road and / or structures related thereto). The output processing step may generate data for displaying, for example, the display area of ​​the acquired shape data and images of the cross slope elimination section and the slope section on one display screen. The output processing step is executed by the output processing unit 459.

[0202] According to the above-described approach road data generation method S40, an approach road that satisfies the design standard values ​​or that conforms to the shape data set by the user can be generated between the road and the approach destination according to the shapes and layout conditions of other structures.

[0203] Next, the model data generating step S46 will be described in detail. Fig. 25 is a flowchart showing a detailed flow of the model data generating step S46. As shown in the figure, step S46 includes steps S461 to S465.

[0204] Step S461 is a cross-slope eliminating section generating step for generating data of a cross-slope eliminating section to be placed at a position of the approach road adjacent to the road. The cross-slope eliminating section generating step is executed by the cross-slope eliminating section generating unit 4541. As described above, if the road surface at the entrance of the approach road is horizontal, it is not necessary to generate a cross-slope eliminating section.

[0205] Step S462 is a horizontal section generating step of generating data of a horizontal section between the cross slope eliminating section and the slope section. The slope section generating step is executed by the slope section generating unit 4543.

[0206] Step S463 is a slope section generating step of generating data of a slope section from the cross slope eliminating section toward the field. The horizontal section generating step is executed by the horizontal section generating unit 4542.

[0207] Step S464 is a corner cutting portion generating step for generating data of a corner cutting portion to be placed at a position where the road and the entrance road intersect. The corner cutting portion generating step is executed by the corner cutting portion generating unit 456.

[0208] Step S465 is a rubbing slope generating step for generating a slope (rubbing slope) for the connection line of the approach road including the corner cut portion. The rubbing slope generating step is executed by the rubbing slope generating unit 457.

[0209] According to the approach road data generation method S40 including the above model data generation step S46, an approach road that satisfies the design standard values ​​or that conforms to the shape data set by the user can be generated between the road and the approach destination in accordance with the shape and layout of other structures. Furthermore, even if the position and shape of the road or the position and shape of an obstacle such as a ridge are changed in design, an approach road that matches the changed position and shape can be mechanically generated. This can significantly reduce the labor of the user (designer). Note that if an approach road that satisfies the design standard values ​​cannot be installed, it is not necessary to generate an approach road.

[0210] Next, specific examples of the various data processing methods described above will be described with reference to the drawings. FIG. 26 is a schematic diagram showing an example of a position indicated by shape data when an approach road Z is generated from a road X. The road X is defined by a skeleton line XA and connecting lines XB and XC on both sides thereof. The approach road Z is defined by a skeleton line ZA extending from a point on the skeleton line XA of the road X and connecting lines ZB and ZC on both sides thereof. The path and the approach destination of the approach road Z are determined by drawing (drawn by the user) the skeleton line ZA from a point on the skeleton line XA of the road X to within the polygonal area of ​​the field of the approach destination. The road gradient of the approach road Z is mechanically determined by interpolating between points that are given elevation values ​​among the points that make up the skeleton line ZA.

[0211] In FIG. 26, the shape data shown by No. 1 is the width of the approach road. The shape data shown by No. 2 is the gradient of the slope provided from the skeleton line XC of road X. The shape data shown by No. 3 is the length along the connection line XC of road X with the left corner cut. The shape data shown by No. 4 is the length along the connection line ZB of approach road Z with the left corner cut. The shape data shown by No. 5 is the length along the connection line XC of road X with the right corner cut. The shape data shown by No. 6 is the length along the connection line ZC of approach road Z with the right corner cut. The shape data shown by No. 7 is the length of the cross slope elimination section. The longitudinal gradient of the cross slope elimination section is also predetermined and cannot be changed. The shape data shown by No. 8 is the longitudinal gradient of the slope section. The length of the slope section is determined from the elevation difference and gradient of both ends of the slope section.

[0212] FIG. 27 is a schematic diagram showing the input screen for shape data shown in FIG. 26. Shape data input to this input screen is acquired by shape data acquisition unit 453. The left side of the screen displays the name of the layer that stores data related to approach road Z. The center of the screen is the shape data input area. The input area displays the data No. (number), element, symbol, and value in that order, and these can be changed. The right side of the screen displays a diagram showing the position indicated by the shape data, as explained in FIG. 26.

[0213] Figure 28 is a schematic diagram showing the position indicated by the shape data when a horizontal section is provided between the cross slope elimination section and the slope section. The position indicating the length of the horizontal section is shown as No. 9. The input screen for this shape data is not shown, but since the horizontal section has a horizontal gradient, it is specified by its length.

[0214] Fig. 29 is a schematic diagram for explaining the position indicated by the shape parameters of the corner cutting portion. Fig. 30 is a detailed diagram showing the positions of the shape data No. 3 to No. 6. As shown in Fig. 30, the shape data No. 3 to No. 6 (length of the corner cutting portion) are lengths starting from the intersection of the travel lane boundary line (connecting line XC of road X) and the approach road boundary line (connecting lines ZB, ZC of approach road Z).

[0215] Figure 31 is a schematic diagram showing an example of how a user can draw an access road to a field. A dotted line is drawn from point V on the road skeleton line XA, shown in solid line, to point B on the field surface. The intersection point of the road connection line XC and the skeleton line of the field access road is designated as point A, and the other end as point B. Point B is drawn within the area of ​​the field polygon in order to identify which field the field access road is accessing. However, there is an exception when the access road straddles two fields, which will be explained later.

[0216] The shape of the approach road is specified by shape data such as the width of the approach road and the slope gradient generated from the connection line of the approach road. The slope of the approach road surface is mechanically calculated by interpolating between points that are given elevation values ​​among the points that make up the skeleton line of the approach road. As described above, the parameters that define the approach road include, for example, the cross-slope elimination section length LnO and the longitudinal slope SA of the slope section. In addition to these, a horizontal section may be provided between the cross-slope elimination section and the slope section. Corner cutting lengths may be set on the left and right sides of the entrance to the approach road. The slope gradient of the approach road is set by the user. When the cross-slope elimination section, horizontal section, and slope section are generated, respectively, the respective slopes are generated based on the specified slope gradient from these connection lines.

[0217] FIG. 32 is a schematic diagram showing the skeleton line information of the approach road. The road connection line is polyline CD, the outer slope line of the ridge is polyline EF, and the inner slope line of the ridge is polyline GH. The skeleton line of the approach road is polyline AB, the right connection line is polyline IJ, and the left connection line is polyline KL. The intersections of the road connection line CD and the approach road connection lines IJ and KL are points I and K, respectively. Points I and K are the same as the elevations of the road connection lines. The intersection of the polyline IK and the polyline AB is point M. The point N is the point from point M to point B, which is the cross slope resolution length LnO along the skeleton line AB of the approach road. In addition, in the part where a horizontal section is to be provided, the horizontal section length Y may be taken up to the slope section. The start point of the slope is point O, and from there, point B, which intersects with the field at a specified slope toward the field, is obtained. Point B of the polyline AB is a point obtained by calculation. If the skeleton line of the approach road is shorter than point B, it is extended to the field in the direction of the line segment vector between the end point of the skeleton line of the approach road starting from point A and the two points before that end point. If the skeleton line of the approach road is long, it is extended to the intersection with the field. In this way, with the function of adjusting the length to reach the field, point B is obtained automatically even if values ​​such as the elevation of the field, the position of the road, or the gradient of the approach road are changed, so the user does not have to modify the skeleton line of the approach road.

[0218] FIG. 33 is a schematic diagram showing a method in which the determination unit 455 determines whether an approach road is an approach road that crosses two fields. When a designer (user) draws an approach road that crosses two fields, the end point B of the polyline AB may exist in one of the field polygons or may not exist in either field. When the end points J and L of the approach road connection line are in the same field, or when one of them is in the field and the other is outside the field, the determination unit 455 determines that the approach road is a single approach road. When both end points are in different fields, the determination unit 455 determines that the approach road is an approach road that crosses both fields. Note that when it is determined that neither of the end points of the approach road connection line is in the field polygon, the approach road may not be generated. In addition, the error display generation unit 458 may generate an error display indicating that an error has occurred at the approach destination.

[0219] The end points J and L are the elevation values ​​within each field polygon, and a horizontal plane passing through each point is generated, and the perpendicular line to the polyline AC on the horizontal plane is set as the field edge (i.e., the end of the approach road entering each field). The rest is the same as the method for generating a rectangular approach road. Since the two quadrilaterals IJBA and ARLK are placed on the ridge, the process of adjusting the elevation of the approach road taking into account the elevation of the ridge, as explained in the obstacle processing method described later, is not performed, and the mesh of the approach road that has entered the ridge is removed by Boolean calculation. The width of the approach road does not need to be changed whether it is a single one or straddles both. In other words, the approach road width WA = line segment JB + line segment RL.

[0220] FIG. 45 is a flowchart showing what kind of processing is performed depending on whether the approach road is an approach road that crosses two fields. First, the determination unit 455 determines where the end points J, L of the left and right connecting lines of the approach road are located. In this case, there are four possibilities. The first is when the end points J, L are within the same field polygon. In this case, a single approach road is generated. Then, the process moves to the generation of a cross-slope elimination section. The second is when the end points J, L are within different field polygons. In this case, an approach road that crosses two fields is generated. Then, the process moves to the generation of a cross-slope elimination section. The third is when one of the end points J, L is within the field and the other is outside the field. In this case, the approach road is generated by adopting the elevation inside the field. However, since the approach road is generated even outside the field, an error message may be output. Then, the process moves to the generation of a cross-slope elimination section. The fourth is when both end points J, L are outside the field. In this case, an error is output and no approach path is generated.

[0221] Figures 34 to 37 are schematic diagrams showing a method for generating a cross-slope elimination section. An approach road attached to a road with a slope has a twisted surface. If the degree of twisting is extremely large, the angle between the rear and front wheels of the vehicle becomes large when the vehicle enters or exits the approach road, that is, the front and rear wheels are twisted. This twisting is inevitable when an approach road is attached to a road with a longitudinal slope. In Figure 34, the line segment IK is not horizontal, but has a slope. In order to gradually alleviate this twisting, the elevations of the polyline IP section and the polyline KQ section are calculated with the aim of eliminating the cross-slope from point M to point N.

[0222] (First step) The intersections of the perpendicular line to polyline AB through point N with polyline IJ and polyline KL are respectively point P and point Q. The intersections of the perpendicular line to polyline AB through point M with polyline IJ, polyline KL, and road connection line CD are respectively point T, point U, and point U'.

[0223] As shown in FIG. 35, the section MN is the cross-slope elimination section. In other words, the gradient of the line segment TU is made horizontal at the line segment PQ. Therefore, it is necessary to obtain the gradient of the line segment TU. For this purpose, the elevations of points T and U are obtained. The intersections of the perpendicular line passing through point M to the skeleton line and the boundary line of the approach road are points T and U. Points T and U are either on the road boundary line, or one of them is outside the road. Points that are inside the road are the elevation of the road surface. On the other hand, points that are outside the road must be estimated. Now, assuming that point T is outside the road, the elevation value of point T on the approach road boundary line is obtained from the straight line connecting point M and point U' (point U' is a point on the road boundary line, and the elevation value is known). The cross-slope at point M is the line segment TU'.

[0224] (Second step) As shown in FIG. 36, multiple perpendicular lines are generated between the line segment TU having a cross slope and the line segment PQ having a zero cross slope for the MN section, and the cross slope is gradually decreased from point M to point N. Multiple perpendicular lines are generated between the line segment TU and the line segment PQ, and multiple intersections between the polyline IJ and the polyline KL are obtained, and a mesh is generated from these intersections within the quadrangle IPQK. The elevation value of point N is indefinite, while the elevation value of point M is fixed. When the polyline MN is made horizontal in the twist elimination section, that is, when point N is set to the same elevation value as point M, the average elevation of the perpendicular direction to the polyline AB is always the same as the elevation of point M. By performing such processing, a cross slope elimination section can be generated from the line segment IK having a slope to the horizontal line segment PQ, as shown in FIG. 37.

[0225] By setting the elevation of point N higher or lower than point M, it is possible to generate a downhill section or an uphill section while eliminating the cross slope. If it is desired to design a more economical approach road by shortening the section of the approach road from the road to the field, the elevation of point N may be set slightly lower than point M within a safe range for the vehicle. If the length of the cross slope elimination section is short, the torsion angle of the vehicle increases, but a vehicle can actually be driven in the virtual space to determine whether the torsion angle of the vehicle obtained at that time is within an allowable value, and if it appears to exceed the allowable value, the torsion elimination length can be set longer and repeated trials can be performed until the torsion angle of the vehicle is within an allowable value.

[0226] 38 and 39 are schematic diagrams showing a method of generating a horizontal section. In general, when a vehicle travels on a slope, it is considered safe to construct a slope section that does not generate a roll angle on the vehicle. However, if there is no distance between the cross slope elimination section and the slope section, the rear wheels are in the cross slope elimination section when entering the slope section, so a roll angle is generated on the vehicle. A horizontal section is installed to avoid or mitigate this. The length of the horizontal section depends on the wheelbase of the vehicle, the roll angle of the vehicle generated in the cross slope elimination section, and the roll angle that the vehicle can tolerate when traveling on a slope. For this reason, the attitude angle of the vehicle is simulated from the travel trajectory of the vehicle, and a safe and economical horizontal section length can be determined from the roll angle of the vehicle. When the length of Y is set by the user, a horizontal line segment PQ passing through point N is prepared, and point N is moved by Y along the approach road skeleton line to point O (the elevation maintains the z coordinate of point N), and the plane formed by the trajectory of line segment PQ becomes the horizontal section. A horizontal section can also be provided when changing the direction of the approach road. When entering a slope section, the vehicle needs to face the slope section head on. If it is not necessary to change the direction of entry in the middle of the slope section, it is preferable to change direction in a horizontal section.

[0227] Figures 40 and 41 are schematic diagrams showing a method for generating a slope section. In the slope section, the cross gradient is set to zero with respect to the line segment OB, and a slope is constructed with a set gradient until the scene is reached, and a mesh is generated.

[0228] Figure 42 is a schematic diagram showing how to generate a corner cutting section. Corner cutting is set on the right and left sides in the direction of approach to the field. The corner cutting length is set in the road direction (LLC1 / RLC1) and the approach road direction (LLC2 / RLC2), and the elevations on the road connection line and the approach road connection line are obtained, and the triangular mesh of the corner cutting section (shaded area) is generated by connecting them. Then, the outermost edge of the corner cutting section and the approach road of the main body are used as a connection line, and the slope is rubbed in the direction of the outside of the approach road against the connection line. The slope is up to the point where it intersects with the existing mesh. In the process, a long slope mesh is first created, and then the slope mesh that has entered the existing mesh is removed by Boolean operations with the existing mesh.

[0229] Figures 43 and 44 are schematic diagrams showing how to generate an approach road when there is an obstacle between the road and the field. When obstacles such as ridges and waterways must be crossed before reaching the field, the mesh of the approach road in the polygon representing a section of the approach road having vertices IJLK is composed of a group of perpendicular lines to the polyline AB. If there is another mesh with an elevation higher than the group of perpendicular lines to the polyline AB, the height of the perpendicular lines must be adjusted so that they do not fall below the elevation of the other mesh.

[0230] As an example, when there is a ridge between the road and the field as shown in Figure 44, the case where polyline EF and polyline GH are at a higher elevation than the generated field approach road (when the elevation of the ridge is higher than the field approach road) will be explained. Basically, the elevation of the skeletal line AB of the approach road is scanned, and the elevation on the skeletal line AB is corrected so that the elevation of the approach road is higher than that of the ridge. Similarly, the elevations of the connecting lines IJ and KL are also scanned, and corrected so that they are higher than the elevation of the ridge. Then, after correcting the elevations of the skeleton lines and connecting lines, the case with the highest elevation is adopted. Specifically, since the elevations of points A, M, and B are specified, the distance (LnO) or elevation (elevation of point N) to point N of the other twist elimination sections, the distance of the horizontal section (length of Y) (elevation is the same as point N), and the distance to the slope start point O (elevation of point O is the same as point N) are scanned, and mechanically corrected to an elevation value higher than that of the ridges and waterways. This correction may be made by the model data generation unit 454.

[0231] An example of a specific method for generating an access road has been described above, but the method for generating an access road is not limited to the above example. The above processes may be modified, added, or replaced as appropriate. Also, known information processing methods may be combined as appropriate. In the above description, the access road is assumed to be an access road to a field, but the access destination does not have to be a field. For example, it may be a parking lot, an office site, etc.

[0232] [Software implementation example] The functions of the approach road data generating device 4 (hereinafter referred to as the "device") can be realized by a program for causing a computer to function as the device, and by a program for causing a computer to function as each control block of the device (particularly each part included in the control unit 45).

[0233] In this case, the device includes a computer having at least one control device (e.g., a processor) and at least one storage device (e.g., storage unit 44) as hardware for executing the program. The control device and storage device execute the program, thereby realizing each function described in each of the above embodiments.

[0234] The program may be non-transitory and may be recorded in one or more computer-readable recording media. The recording media may or may not be included in the device. In the latter case, the program may be provided to the device via any wired or wireless transmission medium.

[0235] In addition, some or all of the functions of each of the control blocks can be realized by a logic circuit. For example, an integrated circuit in which a logic circuit that functions as each of the control blocks is formed is also included in the scope of the present invention. In addition, the functions of each of the control blocks can be realized by, for example, a quantum computer. The configuration using software as described above can be similarly applied to other devices.

[0236] The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope of the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention.

[0237] (summary) The approach road data generation method according to aspect 1 of embodiment 3 includes a structure data acquisition step of acquiring skeleton lines and shape data of structures including roads, a position information acquisition step of acquiring position information of the structures, an approach road skeleton line data acquisition step of acquiring skeleton lines of an approach road from the road to the approach destination drawn by a user, a shape data acquisition step of acquiring shape data input by a user that defines the approach road, and a model data generation step of generating model data of the approach road using the skeleton lines and shape data of the approach road.

[0238] In the approach road data generation method of aspect 2, in aspect 1, the skeleton line of the approach road is defined by the user as a polyline connecting at least two points including any point on the skeleton line of the road and any point within the destination polygon.

[0239] In the approach road data generation method of aspect 3, in aspect 1 or 2, the model data generation step includes a cross slope elimination section generation step of generating data for a cross slope elimination section to be placed at a position of the approach road adjacent to the road based on the shape data, and a slope section generation step of generating data for a slope section extending from the cross slope elimination section toward the approach destination based on the shape data.

[0240] In the approach road data generation method of aspect 4, in addition to aspect 3, the model data generation step further includes a horizontal section generation step of generating data for a horizontal section to be placed between the cross slope elimination section and the slope section.

[0241] An approach road data generating method according to a fifth aspect is the method according to the fourth aspect, wherein the longitudinal gradient of the slope section is equal to or smaller than a predetermined limit value.

[0242] The approach road data generating method according to aspect 6 is any one of aspects 1 to 5, further comprising a corner cutting generating step of generating a corner cutting portion at a position where the road and the approach road intersect.

[0243] The approach road data generating method according to aspect 7 is any one of aspects 1 to 6, further including a determination step of determining whether or not the approach road is an approach road for entering two or more of the approach destinations.

[0244] In the approach road data generation method of aspect 8, in aspect 2, the structure includes a structure located between the road and the approach destination, and the skeleton line of the approach road is defined so that its elevation exceeds the elevation of the structure.

[0245] The approach road data generation method of aspect 9, in any one of aspects 1 to 8, further includes an error display generation step of generating an error display indicating that an error has occurred when the generated approach road interferes with an existing structure or when at least one of the two connecting lines of the approach road does not reach the approach destination.

[0246] The approach road data generation method of aspect 10, in aspect 3, further includes an output processing step for generating data to display the display area of ​​the acquired shape data, as well as images of the cross slope elimination section and the slope section on a single display screen.

[0247] An approach road data generating device according to an eleventh aspect of the present invention comprises: a structure data acquisition unit for acquiring skeleton lines and shape data of structures including roads; A location information acquisition unit that acquires location information of the structure; an approach road skeleton line data acquisition unit for acquiring a skeleton line of an approach road from the road to an approach destination drawn by a user; The system includes a shape data acquisition unit that acquires shape data defining the approach road input by a user, and a model data generation unit that generates model data of the approach road using the skeleton line and the shape data of the approach road. a structure data acquisition unit for acquiring skeleton lines and shape data of structures including roads; A location information acquisition unit that acquires location information of the structure; an approach road skeleton line data acquisition unit for acquiring a skeleton line of an approach road from the road to an approach destination drawn by a user; a shape data acquisition unit that acquires shape data that defines the approach path input by a user; a model data generating unit that generates model data of the approach path using the skeleton line and the shape data of the approach path; An approach road data generating device comprising:

[0248] The program of embodiment 12 is an approach road data generation program for causing a computer to function as the approach road data generation device described in embodiment 11, and causes the computer to function as the structure data acquisition unit, the position information acquisition unit, the approach road skeleton line data acquisition unit, the shape data acquisition unit and the model data generation unit.

[0249] A recording medium according to a thirteenth aspect is a computer-readable recording medium having the approach road data generation program according to the twelfth aspect recorded thereon. [Explanation of symbols]

[0250] 4... Approach road data generation device 45...Control section 451…Approach road skeleton line data acquisition unit 452...Location information acquisition unit 453…Shape data acquisition unit 454…Model data generation unit 4541…Cross slope elimination section generation section 4542…Horizontal section generation section 4543…Slope section generation section 455...Judgment section 456…Corner cutting section 457…Slope generation section 458…Error display generation unit 459...Output processing section 44...Storage section 441…Approach road data generation program 11...Input section 13...Output section

Claims

1. a structure data acquisition step of acquiring skeleton lines and shape data of structures including roads; a position information acquisition step of acquiring position information of the structure; an approach road skeleton line data acquisition step of acquiring a skeleton line of an approach road drawn by a user from the road to an approach destination; a shape data acquisition step of acquiring shape data input by a user and defining the approach path; a model data generating step of generating model data of the approach path using the skeleton line and the shape data of the approach path; An approach road data generation method comprising:

2. The approach road data generation method according to claim 1, wherein the skeleton line of the approach road is defined by a user as a polyline connecting at least two points including any one point on the skeleton line of the road and any one point within the polygon of the approach destination.

3. The model data generating step includes a cross-slope eliminating section generating step of generating data of a cross-slope eliminating section to be disposed at a position of the approach road adjacent to the road based on the shape data; 3. The approach road data generating method according to claim 1, further comprising: a slope section generating step of generating data of a slope section extending from the cross slope eliminating section toward the approach destination based on the shape data.

4. 4. The approach road data generating method according to claim 3, wherein said model data generating step further includes a horizontal section generating step of generating data of a horizontal section to be placed between said cross slope eliminating section and said slope section.

5. The approach road data generating method according to claim 4 , wherein a longitudinal gradient of the slope section is equal to or less than a predetermined limit value.

6. 3. The approach road data generating method according to claim 1, further comprising a corner cutting generating step of generating a corner cutting at a position where said road intersects with said approach road.

7. The approach road data generating method according to claim 1 or 2, further comprising a determining step of determining whether or not the approach road is an approach road for entering two or more of the approach destinations.

8. 3. The approach road data generation method according to claim 2, wherein the structure includes a structure existing between the road and the approach destination, and the skeleton line of the approach road is defined such that its elevation exceeds an elevation of the structure.

9. 3. The approach road data generation method according to claim 1 or 2, further comprising an error display generation step of generating an error display indicating that an error has occurred when the generated approach road interferes with an existing structure or when at least one of the two connecting lines of the approach road does not reach the approach destination.

10. The approach road data generation method according to claim 3, further comprising an output processing step of generating data for displaying on a single display screen a display area of ​​the acquired shape data, as well as images of the cross slope elimination section and the slope section.

11. a structure data acquisition unit for acquiring skeleton lines and shape data of structures including roads; A location information acquisition unit that acquires location information of the structure; an approach road skeleton line data acquisition unit for acquiring a skeleton line of an approach road from the road to an approach destination drawn by a user; a shape data acquisition unit that acquires shape data that defines the approach path input by a user; a model data generating unit that generates model data of the approach path using the skeleton line and the shape data of the approach path; An approach road data generating device comprising:

12. An approach road data generation program for causing a computer to function as the approach road data generation device described in claim 11, comprising an approach road data generation program for causing a computer to function as the structure data acquisition unit, the position information acquisition unit, the approach road skeleton line data acquisition unit, the shape data acquisition unit and the model data generation unit.

13. A computer-readable recording medium having recorded thereon the approach road data generating program according to claim 12.

Images