Data processing device, data processing method, and data processing program
The data processing device generates a line-of-sight table with elevation and distance pairs for each azimuth angle, addressing the inaccuracies in conventional systems by accurately determining visibility in terrains with mountains and valleys, enhancing precision and memory efficiency.
Patent Information
- Application Number
- JP2025078699
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-19
AI Technical Summary
Conventional line-of-sight availability determination systems struggle to accurately determine visibility in terrains with multiple mountains and valleys, erroneously determining areas as line-of-sight available when they are actually not.
A data processing device that generates a line-of-sight table by deriving pairs of line-of-sight elevation angles and horizontal distances for each azimuth angle, considering the elevation of surrounding areas to set reference points, allowing for accurate visibility determination even in complex terrains.
Enables precise determination of visibility in environments with peaks and valleys, reducing data storage requirements and optimizing memory usage.
Smart Images

Figure 2026182451000001_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a technique for determining line-of-sight availability from a specific position.
Background Art
[0002] For example, in simulations of the motion state of a moving object and the observation state of a sensor that observes the moving object, line-of-sight availability determination may be performed. In such simulations, the line-of-sight availability determination determines whether the sensor can have a line of sight to the moving object from a specific position. In conventional line-of-sight availability determination systems represented by Patent Document 1, a line-of-sight table that records the minimum elevation angle and the limit distance for each azimuth angle is generated. Then, the line-of-sight availability determination is performed based on the generated line-of-sight table.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] The above conventional line-of-sight availability determination system has a problem that it is difficult to accurately determine line-of-sight availability in terrain with a plurality of mountains and valleys.
[0005] Figure 1 illustrates the problems of the conventional line-of-sight availability determination system. In the conventional line-of-sight availability determination system, an area that is closer than the limit distance as viewed from the observation point and has an elevation angle value smaller than the minimum elevation angle is determined to be line-of-sight available. However, although area A is closer than the limit distance as viewed from the observation point and has an elevation angle value smaller than the minimum elevation angle, it cannot actually be seen due to the mountain in the foreground. As described above, the conventional line-of-sight availability determination system has a problem that it erroneously determines an area that is actually not line-of-sight available as line-of-sight available.
[0006] The primary purpose of this disclosure is to address these challenges. More specifically, the primary purpose of this disclosure is to enable accurate determination of whether or not visibility is possible, even when peaks or valleys exist. [Means for solving the problem]
[0007] The data processing device related to this disclosure is A unit for setting line-of-sight reference points, The system includes a line-of-sight table generation unit that, based on the elevation of the area surrounding the line-of-sight reference point, derives two or more pairs for each azimuth angle: a line-of-sight elevation angle, which is the angle of elevation required to see from the line-of-sight reference point to a line-of-sight limit point, which is the horizontal distance from the line-of-sight reference point to the line-of-sight limit point; and a line-of-sight table generation unit that generates a line-of-sight table in which the line-of-sight reference point is associated with two or more pairs of the line-of-sight elevation angle and the line-of-sight horizontal distance for each azimuth angle. [Effects of the Invention]
[0008] According to this disclosure, it is possible to accurately determine whether visibility is possible even when there are peaks or valleys. [Brief explanation of the drawing]
[0009] [Figure 1] A diagram illustrating the challenges of conventional technology. [Figure 2] A diagram showing an example of the functional configuration of the simulation device according to Embodiment 1. [Figure 3] A diagram showing an example of a forecast table according to Embodiment 1. [Figure 4] A diagram showing an example of the relationship between the line of sight limit point and the line of sight table according to Embodiment 1. [Figure 5] A diagram showing an example of the perspective according to Embodiment 1. [Figure 6] A flowchart illustrating an example of the operation of the forecast table processing unit according to Embodiment 1. [Figure 7](FIG. 1 is a diagram showing an example of line-of-sight azimuth angle, line-of-sight elevation angle candidates, and line-of-sight horizontal distance candidates according to Embodiment 1.) [Figure 8] A flowchart diagram showing an operation example of the line-of-sight availability processing unit according to Embodiment 2. [Figure 9] A diagram showing the relationship between an observation point, target azimuth angle, target elevation angle, and target horizontal distance according to Embodiment 2. [Figure 10] A diagram showing an example of line-of-sight availability between an observation point and a target according to Embodiment 2. [Figure 11] A diagram showing a functional configuration example of a simulation apparatus according to Embodiment 3. [Figure 12] A flowchart diagram showing an operation example of the line-of-sight table processing unit according to Embodiment 3. [Figure 13] A diagram showing an example of line-of-sight azimuth angle, line-of-sight elevation angle candidates, and line-of-sight horizontal distance candidates according to Embodiment 3. [Figure 14] A diagram showing a hardware configuration example of a simulation apparatus according to Embodiment 1. [Mode for Carrying Out the Invention]
[0010] Hereinafter, embodiments will be described with reference to the drawings. In the following description of the embodiments and the drawings, parts denoted by the same reference numerals indicate the same or corresponding parts.
[0011] In the following Embodiments 1 to 4, a configuration will be described in which a plurality of pairs of line-of-sight elevation angles and line-of-sight horizontal distances for one azimuth angle are recorded in a line-of-sight table, so that the determination of line-of-sight availability can be performed accurately even when a plurality of mountains and valleys exist for one azimuth angle.
[0012] In Embodiment 1, generation of such a line-of-sight table will be described. In Embodiment 2, a line-of-sight availability determination method using the line-of-sight table will be described. In Embodiment 3, updating of the line-of-sight table and the line-of-sight availability determination method when a structure such as a building is added will be described. In the fourth embodiment, a method for specifying a distant area will be described. Details of the distant area will be described later. Note that, although the first embodiment and the second embodiment describe examples in which a certain position on the ground is set as an observation point, the target is not limited to the ground, and may be on the sea or in the sky.
[0013] First Embodiment. ***Description of Configuration*** Figure 2 shows an example of the functional configuration of the simulation apparatus 100 according to the first embodiment. In addition, Figure 14 shows an example of the hardware configuration of the simulation apparatus 100 according to the first embodiment. The simulation apparatus 100 corresponds to a data processing apparatus. Further, the operation procedure of the simulation apparatus 100 corresponds to a data processing method. Further, a program that realizes the operation of the simulation apparatus 100 corresponds to a data processing program.
[0014] As shown in Figure 14, the simulation apparatus 100 is a computer, and includes a processor 101, a main storage device 102, an auxiliary storage device 103, and a communication device 104. Although not illustrated in Figure 14, the simulation apparatus 100 may include an input / output device. Further, as shown in Figure 2, the simulation apparatus 100 includes an elevation data storage unit 200, a line-of-sight table processing unit 300, a line-of-sight table storage unit 400, and a simulation execution unit 500.
[0015] The line-of-sight table processing unit 300 includes, as internal components, an elevation data acquisition unit 301, a line-of-sight reference point setting unit 302, a distant area determination unit 303, and a line-of-sight table generation unit 304. Further, the simulation execution unit 500 includes, as internal components, a moving object simulation unit 600, a sensor simulation unit 700, and a line-of-sight availability processing unit 800 (a line-of-sight calculation unit 801, a line-of-sight table acquisition unit 802, and a line-of-sight availability determination unit 803). These internal components of the line-of-sight table processing unit 300 and internal components of the simulation execution unit 500 are elements that realize the functions of the simulation apparatus 100, and are referred to as functional components. These functional components are implemented, for example, by a program. The auxiliary storage device 103 stores programs that implement the functions of these functional components. These programs are loaded from the auxiliary storage device 103 into the main memory device 102. Then, the processor 101 executes these programs to perform the operation of the functional components shown in Figure 2. The elevation data storage unit 200 and the line-of-sight table storage unit 400 in Figure 2 are implemented by the auxiliary storage device 103 or the main storage device 102.
[0016] In Figure 2, the elevation data storage unit 200 stores the elevation data 201. Elevation data 201 is data that defines height information for specific points within a certain geographical area. Elevation data 201 is data that defines the mean sea level elevation at mesh points indicated by latitude and longitude, similar to the digital elevation model published by the Geospatial Information Authority of Japan. The Geographical Survey Institute's digital elevation model can be used as elevation data 201. Alternatively, similar data where height information from a reference point at each coordinate is defined may be used as elevation data 201.
[0017] The forecast table storage unit 400 stores the forecast table 401 and the temporary storage table 406. The forecast table 401 is a table used for determining whether or not a forecast is possible, as described in Embodiment 2. Temporary storage table 406 is a table for temporarily storing candidate line-of-sight elevation angles, which will be described later.
[0018] Figure 3 shows an example of a forecast table 401. The line-of-sight table 401 consists of columns for line-of-sight reference point 402, line-of-sight azimuth angle 403, line-of-sight elevation angle 404, and line-of-sight horizontal distance 405. Figure 4 also shows the relationship between the topography of the area surrounding line-of-sight reference point 402, line-of-sight azimuth angle 403, line-of-sight elevation angle 404, and line-of-sight horizontal distance 405.
[0019] The column for line-of-sight reference point 402 indicates line-of-sight reference point 402. Line-of-sight reference point 402 is the location that serves as the criterion for determining whether or not visibility is possible. Line-of-sight reference point 402 is a location where sensors, etc., may be placed in the simulation. The column for line-of-sight reference point 402 shows, for example, the latitude and longitude of line-of-sight reference point 402. Note that in Figure 3, "x1" represents latitude, and "y1" and "y2" represent longitude.
[0020] The column for line-of-sight azimuth 403 displays the line-of-sight azimuth 403. In the line-of-sight azimuth 403 column, the azimuth is shown as a discrete value with an arbitrary step size. In Figure 3, the line-of-sight azimuth 403 is shown with a step size of 5 degrees. In the example in Figure 3, "0 degrees" represents the range from 0 degrees to less than 5 degrees. "5 degrees" represents the range from 5 degrees to less than 10 degrees. Note that the step size of 5 degrees is just an example, and the step size for line-of-sight azimuth 403 can be arbitrarily chosen. With a line-of-sight azimuth of 403 degrees, for example, one could consider the north direction to be 0 degrees. Although not shown in Figure 3, the column for line-of-sight azimuth angle 403 shows the angle in 5-degree increments from 0 to 355 degrees.
[0021] The column for line-of-sight elevation angle 404 shows the line-of-sight elevation angle 404. The line-of-sight elevation angle 404 is the elevation angle required to see the line-of-sight limit point, which is a point within line of sight from the line-of-sight reference point 402, from the line-of-sight reference point 402. The column for line-of-sight elevation angle 404 shows multiple line-of-sight elevation angles 404 for each step size of the line-of-sight azimuth angle 403. In other words, the column for line-of-sight elevation angle 404 shows the elevation angle required to see each of the multiple line-of-sight limit points located in the direction of the line-of-sight azimuth angle 403 in the area surrounding the line-of-sight reference point 402 from the line-of-sight reference point 402. The surrounding area is the area centered on the line-of-sight reference point 402, excluding the distant area.
[0022] The column for horizontal line of sight distance 405 shows the horizontal line of sight distance 405. Horizontal line of sight distance 405 is the horizontal distance from the line of sight reference point 402 to the line of sight limit point. The column for horizontal line of sight distance 405 shows multiple horizontal line of sight distances 405 associated with multiple elevation angles 404 for each step size of the azimuth angle 403. In other words, the column for horizontal line of sight distance 405 shows the horizontal distance between each of the multiple line of sight limit points located in the direction of the azimuth angle 403 in the area surrounding the line of sight reference point 402 and the line of sight reference point 402 as the horizontal line of sight distance 405.
[0023] As shown in Figure 3, in the line-of-sight table 401, a line-of-sight reference point 402 is associated with a pair of line-of-sight elevation angle 404 and line-of-sight horizontal distance 405 for each line-of-sight azimuth angle 403. More specifically, two or more pairs of line-of-sight elevation angle 404 and line-of-sight horizontal distance 405 are associated with the line-of-sight reference point 402. In the example in Figure 3, the line-of-sight reference point 402 "x1y1" is associated with pairs of line-of-sight elevation angle 404 and line-of-sight horizontal distance 405 for a line-of-sight azimuth angle 403 "0 degrees," such as "15 degrees" and "500m," "25 degrees" and "600m," and "34 degrees" and "700m." Additionally, the line-of-sight reference point 402 "x1y1" is associated with pairs of line-of-sight elevation angle 404 and line-of-sight horizontal distance 405 for a line-of-sight azimuth angle 403 "5 degrees," such as "18 degrees" and "500m," "24 degrees" and "600m," and "37 degrees" and "700m."
[0024] Here, "line of sight" means that there are no obstacles between the observation point where sensors are placed and the target, such as a moving object, and that the target can be observed visually or by radar from the observation point. For example, in Figure 5, there is a mountain between the observation point and target A, so target A cannot be observed from the observation point. Therefore, target A is "not visible" from the observation point. On the other hand, there is no mountain between target B and the observation point, so target B can be observed from the observation point. Therefore, target B is "visible" from the observation point. Furthermore, the process of determining whether or not it is possible to see the target from the observation point is called "line of sight determination." The line-of-sight elevation angle 404 in Figure 3 is the elevation angle required when observing the line-of-sight limit point that is visible from the line-of-sight reference point 402.
[0025] Returning to Figure 2, the elevation data acquisition unit 301 performs the elevation data acquisition process. In other words, the elevation data acquisition unit 301 acquires elevation data 201 from the elevation data storage unit 200.
[0026] The line-of-sight reference point setting unit 302 performs line-of-sight reference point setting processing. In other words, the line-of-sight reference point setting unit 302 sets the line-of-sight reference point 402.
[0027] The remote area determination unit 303 performs remote area determination processing. In other words, the remote area determination unit 303 determines that an area is remote.
[0028] The forecast table generation unit 304 performs the forecast table generation process. In other words, the forecast table generation unit 304 generates the forecast table 401. More specifically, the line-of-sight table generation unit 304 refers to the elevation data 201 and derives two or more pairs of line-of-sight elevation angle 404 and line-of-sight horizontal distance 405 for each line-of-sight azimuth angle 403, based on the elevation of the line-of-sight reference point 402 and the elevation of the area surrounding the line-of-sight reference point 402. Then, the line-of-sight table generation unit 304 generates a line-of-sight table 401 by associating the line-of-sight reference point 402 with two or more pairs of line-of-sight elevation angle 404 and line-of-sight horizontal distance 405 for each line-of-sight azimuth angle 403.
[0029] The forecast table output unit 305 performs forecast table output processing. In other words, the forecast table output unit 305 stores the forecast table 401 generated by the forecast table generation unit 304 in the forecast table storage unit 400.
[0030] The internal components of the simulation execution unit 500 will be described in Embodiment 2.
[0031] ***Explanation of operation*** Next, an example of the operation of the forecast table processing unit 300 according to this embodiment will be described with reference to the flowchart in Figure 6.
[0032] First, in step S601, the elevation data acquisition unit 301 acquires elevation data 201. Here, the elevation data 201 is assumed to be divided into meshes of a certain size, as illustrated in Figure 4. The elevation data acquisition unit 301 outputs the elevation data 201 to the line-of-sight reference point setting unit 302, the distant area determination unit 303, and the line-of-sight table generation unit 304.
[0033] The processing from step S602 to step S613 (or up to step S614) is performed for each line of sight reference point 402.
[0034] In step S602, the line-of-sight reference point setting unit 302 sets the line-of-sight reference points 402 to be included in the line-of-sight table 401. The line-of-sight reference point setting unit 302 sets line-of-sight reference points 402 for the geographical area covered by the elevation data 201, for example, based on an externally set line-of-sight reference point calculation interval. The line-of-sight reference point setting unit 302 may also set points where height information is set in the elevation data 201 (for example, mesh points of the elevation data 201) as line-of-sight reference points 402. The line-of-sight reference point setting unit 302 notifies the line-of-sight table generation unit 304 of the line-of-sight reference point 402.
[0035] Next, in step S603, the line-of-sight table generation unit 304 determines whether the mesh to be processed (hereinafter referred to as the processed mesh) is a mesh in a distant area. In other words, the line-of-sight table generation unit 304 determines whether the processed mesh is a mesh corresponding to the area surrounding the line-of-sight reference point 402. In this embodiment, the line-of-sight table generation unit 304 performs the processing described in step S604 on a mesh-by-mesh basis for the elevation data 201. In step S603, the line-of-sight table generation unit 304 selects an arbitrary number of meshes to be processed from multiple meshes around the line-of-sight reference point 402. The line-of-sight table generation unit 304 then determines whether the selected meshes to be processed are meshes in the distant area. More specifically, the line-of-sight table generation unit 304 notifies the distant area determination unit 303 of the mesh to be processed and the line-of-sight reference point 402. The line-of-sight table generation unit 304 then queries the distant area determination unit 303 to determine whether the area to be processed is a distant area for the line-of-sight reference point 402. The remote area determination unit 303 determines whether the mesh to be processed is a mesh in a remote area.
[0036] The distant area is an area that is too far away to be seen from line-of-sight reference point 402 due to the curvature of the Earth. In other words, the distant area determination unit 303 determines whether the mesh to be processed corresponds to an area that is so far away that it cannot be seen from the line-of-sight reference point 402 because it is affected by the curvature of the Earth when observed from the line-of-sight reference point 402. The method by which the distant area determination unit 303 identifies the distant area of the line-of-sight reference point 402 may be an existing method. The specific method for identifying the distant area will be explained in Embodiment 4.
[0037] The remote area determination unit 303 notifies the forecast table generation unit 304 of the determination result. If the remote area determination unit 303 determines that the target mesh is not a remote area mesh (NO in step S603), the line-of-sight table generation unit 304 performs the process in step S604. On the other hand, if the remote area determination unit 303 determines that the target mesh is a remote area mesh (YES in step S603), the line-of-sight table generation unit 304 selects an unselected mesh as the target mesh. Then, it queries the remote area determination unit 303 about the newly selected target mesh.
[0038] In step S604, the line-of-sight table generation unit 304 calculates the line-of-sight azimuth angle 403 for the mesh to be processed with respect to the line-of-sight reference point 402. The line-of-sight table generation unit 304 calculates the line-of-sight azimuth angle 403 in accordance with the angle value of the line-of-sight azimuth angle 403 in the line-of-sight table 401. Furthermore, the line-of-sight table generation unit 304 extracts multiple line-of-sight limit points in the target area based on the elevation of the area in the direction of the calculated line-of-sight azimuth angle 403 (hereinafter referred to as the target area) and the elevation of the line-of-sight reference point 402. Then, for each line-of-sight limit point, the line-of-sight table generation unit 304 calculates a candidate line-of-sight elevation angle 404 and a candidate line-of-sight horizontal distance 405. Finally, the line-of-sight table generation unit 304 adds the line-of-sight reference point 402, the line-of-sight azimuth angle 403, the line-of-sight elevation angle candidate, and the line-of-sight horizontal distance candidate to the line-of-sight table 401. At this point, the line-of-sight table 401 is provisional. Note that the line-of-sight elevation angle candidate is also referred to as the elevation angle candidate. Similarly, the line-of-sight horizontal distance candidate is also referred to as the horizontal distance candidate.
[0039] Figure 7 shows an example of the operation of the forecast table generation unit 304 in step S604. In the example in Figure 7, meshes A, B, C, and D are selected as the meshes to be processed. The line-of-sight table generation unit 304 calculates the line-of-sight azimuth angle α for the line-of-sight reference point α. Then, it extracts multiple line-of-sight limit points in the target area located in the direction of the line-of-sight azimuth angle α. In the example shown in Figure 7, the line-of-sight table generation unit 304 extracts line-of-sight limit point 1 and line-of-sight limit point 2. The line-of-sight table generation unit 304 then calculates the elevation angle when line-of-sight limit point 1 is visible from line-of-sight reference point α as line-of-sight elevation angle candidate 1. Furthermore, it calculates the horizontal distance from line-of-sight reference point α to line-of-sight limit point 1 as line-of-sight horizontal distance candidate 1. Similarly, the line-of-sight table generation unit 304 calculates the elevation angle when line-of-sight limit point 2 is visible from line-of-sight reference point α as line-of-sight elevation angle candidate 2. Furthermore, it calculates the horizontal distance from line-of-sight reference point α to line-of-sight limit point 2 as line-of-sight horizontal distance candidate 2. In Figure 7, only two line-of-sight limit points, line-of-sight limit point 1 and line-of-sight limit point 2, are extracted. However, in actual operation, the line-of-sight table generation unit 304 extracts multiple line-of-sight limit points between line-of-sight reference point α and line-of-sight limit point 1. Furthermore, the line-of-sight table generation unit 304 extracts multiple line-of-sight limit points between line-of-sight limit point 1 and line-of-sight limit point 2. In addition, the line-of-sight table generation unit 304 extracts multiple line-of-sight limit points beyond line-of-sight limit point 2.
[0040] The line-of-sight table generation unit 304 can, for example, calculate the line-of-sight azimuth angle 403, extract the line-of-sight limit point, calculate candidate line-of-sight elevation angles, and calculate candidate line-of-sight horizontal distances by the method described in Embodiment 3 of Patent Document 1.
[0041] Returning to the flow in Figure 6, in step S605, the line-of-sight table generation unit 304 determines whether or not the processing in step S604 has been performed for all meshes corresponding to the area surrounding the line-of-sight reference point 402. If the process in step S604 has been performed for all meshes corresponding to the area surrounding the line-of-sight reference point 402 (YES in step S605), the process proceeds to step S606. On the other hand, if there are meshes that have not undergone the processing in step S604 (NO in step S605), the process returns to step S603.
[0042] In step S606, the line-of-sight table generation unit 304 categorizes the data according to the angle value of the line-of-sight azimuth angle 403 calculated in step S604. The data subject to classification is the pair of line-of-sight elevation candidate and line-of-sight horizontal distance calculated in step S604. In other words, the line-of-sight table generation unit 304 classifies multiple pairs of line-of-sight elevation candidate and line-of-sight horizontal distance calculated for multiple line-of-sight limit points in the same line-of-sight azimuth angle 403 according to the angular value of the line-of-sight azimuth angle 403.
[0043] The processing from step S604 to step S613 (or up to step S614) is performed for every 403m of line-of-sight azimuth.
[0044] In step S607, the line-of-sight table generation unit 304 arranges multiple line-of-sight elevation angle candidates, each categorized for the line-of-sight azimuth angle 403 to be processed, in ascending order of their paired line-of-sight horizontal distance candidates within the line-of-sight table 401.
[0045] In step S608, the line-of-sight table generation unit 304 selects one line-of-sight elevation angle candidate as a comparison line-of-sight elevation angle candidate in the order of the rows in the line-of-sight table 401 after arrangement. The line-of-sight table generation unit 304 then compares the selected comparison line-of-sight elevation angle candidate with the line-of-sight elevation angle candidate to be compared. The candidate for the comparative forecast elevation angle is the forecast elevation angle candidate that is one row prior to the comparative forecast elevation angle candidate in forecast table 401. The candidate for the comparative forecast elevation angle, which is the forecast elevation angle candidate one row prior, is the largest forecast elevation angle candidate among the forecast elevation angle candidates that precede the comparative forecast elevation angle candidate. "Prior to" means that it was selected as a comparative forecast elevation angle candidate prior to the current comparative forecast elevation angle candidate. The candidate for comparative line of sight elevation angle will also be referred to as the comparative candidate. Similarly, the candidate for the line of sight elevation angle being compared will also be referred to as the candidate being compared.
[0046] If, as a result of comparing the candidate for the comparison line of sight elevation angle with the candidate for the line of sight elevation angle being compared, the candidate for the comparison line of sight elevation angle is greater than the candidate for the line of sight elevation angle being compared (YES in step S608), the process proceeds to step S609. On the other hand, if the candidate for the comparison line of sight elevation angle is less than or equal to the candidate for the line of sight elevation angle being compared (NO in step S608), the process proceeds to step S610.
[0047] In step S609, the forecast table generation unit 304 deletes the data from the previous row and leaves the data from that row in the forecast table 401. In other words, the line-of-sight table generation unit 304 deletes the line-of-sight elevation angle candidate from the row before the comparison elevation angle candidate, and the line-of-sight horizontal distance candidate that is paired with this line-of-sight elevation angle candidate, from the line-of-sight table 401. On the other hand, the line-of-sight table generation unit 304 leaves in the line-of-sight table 401 the line-of-sight elevation angle candidate of the row that was selected as the comparison target elevation angle candidate, and the line-of-sight horizontal distance candidate that is paired with this line-of-sight elevation angle candidate. As a result, the candidate elevation angle for that row remaining in the line of sight table 401 is treated as a new candidate elevation angle to be compared. In other words, the candidate elevation angle for that row remaining in the line of sight table 401 becomes the candidate elevation angle to be compared for the next selected candidate elevation angle to compare.
[0048] In step S610, the line-of-sight table generation unit 304 determines whether the data from the previous row is temporarily stored in the temporary storage table 406. If the data from the previous row is not temporarily stored in the temporary storage table 406, the line-of-sight table generation unit 304 temporarily stores the data from the previous row in the temporary storage table 406. The line-of-sight elevation angle candidate (comparable elevation angle candidate) and line-of-sight horizontal distance candidate from the previous row, which are temporarily stored in the temporary storage table 406, are treated as the line-of-sight elevation angle 404 and line-of-sight horizontal distance 405 in step S613 or step S614, which will be described later. Furthermore, in step S610, the forecast table generation unit 304 deletes the data for the relevant row from the forecast table 401, while leaving the data from the previous row in the forecast table 401. In other words, the line-of-sight table generation unit 304 deletes the line-of-sight elevation angle candidate for the row selected as the comparison target elevation angle candidate, and the line-of-sight horizontal distance candidate paired with this line-of-sight elevation angle candidate, from the line-of-sight table 401. On the other hand, the line-of-sight table generation unit 304 leaves in the line-of-sight table 401 the line-of-sight elevation angle candidate from the row before the comparison elevation angle candidate, which was compared with the comparison elevation angle candidate, and the line-of-sight horizontal distance candidate paired with this line-of-sight elevation angle candidate. As a result, the previous candidate elevation angle in the line-of-sight table 401 also becomes the candidate elevation angle to be compared to for the next selected candidate elevation angle to compare against.
[0049] In step S611, the line of sight table generation unit 304 determines whether the processing in steps S608 and S609 or S610 has been performed for all rows of the line of sight azimuth angle 403 that is currently being processed. If processing has been performed on all rows (YES in step S611), the process proceeds to step S612. On the other hand, if there are rows that have not been processed (NO in step S611), the process returns to step S608.
[0050] In step S612, the line-of-sight table generation unit 304 determines whether the data for the maximum line-of-sight elevation angle candidate for the line-of-sight azimuth angle 403 currently being processed is temporarily stored in the temporary storage table 406. The maximum line-of-sight elevation angle candidate is the line-of-sight elevation angle candidate that ultimately remains in the line-of-sight table 401 as the line-of-sight elevation angle candidate for the line-of-sight azimuth angle 403 currently being processed. In other words, the line-of-sight table generation unit 304 determines whether the line-of-sight elevation angle candidate that ultimately remains in the line-of-sight table 401 for the line-of-sight azimuth angle 403 currently being processed, and the line-of-sight horizontal distance candidate paired with this line-of-sight elevation angle candidate, are temporarily stored in the temporary storage table 406. If the data for the maximum line-of-sight elevation angle candidate is temporarily stored in the temporary storage table 406 (YES in step S612), the process proceeds to step S614. On the other hand, if the data for the maximum line-of-sight elevation angle candidate is not temporarily stored in the temporary storage table 406 (NO in step S612), the process proceeds to step S613.
[0051] In step S613, the line-of-sight table generation unit 304 temporarily stores the data of the maximum line-of-sight elevation angle candidate for the line-of-sight azimuth angle 403 currently being processed in the temporary storage table 406. Furthermore, the line-of-sight table generation unit 304 overwrites the line-of-sight table 401 with data stored in the temporary storage table 406, which contains the data for the maximum line-of-sight elevation angle candidate. In other words, the line-of-sight table generation unit 304 writes to the line-of-sight table 401 the pairs of line-of-sight elevation angle candidates and their corresponding line-of-sight horizontal distance candidates, which were previously saved in the temporary storage table 406 in step S610, and the pairs of the maximum line-of-sight elevation angle candidate and its corresponding line-of-sight horizontal distance candidate. At this stage, these line-of-sight elevation angle candidates become line-of-sight elevation angles 404, and these line-of-sight horizontal distance candidates become line-of-sight horizontal distances 405.
[0052] In step S614, the line-of-sight table generation unit 304 overwrites the line-of-sight table 401 with data stored in the temporary storage table 406, which contains data for the maximum line-of-sight elevation angle candidate. Step S614 is equivalent to the process in step S613, excluding the process of temporarily saving the data of the maximum line-of-sight elevation angle candidate to the temporary storage table 406.
[0053] The forecast table 401 obtained by overriding in step S613 and the forecast table 401 obtained by overriding in step S614 are the same. As a result of the processing in step S613 or step S614, the line of sight table 401 contains multiple pairs of line of sight elevation angle 404 and line of sight horizontal distance 405 for each line of sight reference point 402, as shown in Figure 3.
[0054] When the processing for one line-of-sight azimuth angle 403 reaches step S613 or step S614, the line-of-sight table generation unit 304 calculates a new line-of-sight azimuth angle 403 for the line-of-sight reference point 402 that is the subject of processing in step S604, and performs the processing from step S604 onwards for the new line-of-sight azimuth angle 403.
[0055] For one line-of-sight reference point 402, all line-of-sight azimuth angles 403 from 0 degrees to 355 degrees are calculated. Once the processing reaches step S613 or step S614 for all line-of-sight azimuth angles 403, the line-of-sight reference point setting unit 302 sets a new line-of-sight reference point 402 in step S602. Then, the processing from step S603 onward is performed for the new line-of-sight reference point 402. Once the processing from step S603 onward is completed for all line-of-sight reference points 402, in step S615, the line-of-sight table output unit 305 outputs the line-of-sight table 401 to the line-of-sight table storage unit 400.
[0056] ***Explanation of the effects of the embodiment*** Thus, according to this embodiment, a line-of-sight table 401 is generated in which multiple pairs of line-of-sight elevation angle 404 and line-of-sight horizontal distance 405 are described for each line-of-sight azimuth angle 403 for a line-of-sight reference point 402. The line-of-sight table 401 contains multiple pairs of line-of-sight elevation angle 404 and line-of-sight horizontal distance 405 for each line-of-sight reference point 402, so that even if there are multiple mountains or valleys in a single azimuth angle, the visibility can be accurately determined. Furthermore, using such a forecast table 401 makes it possible to reduce the amount of data to be stored, and as a result, it becomes possible to make effective use of the memory space.
[0057] Embodiment 2. This embodiment describes a method for determining whether or not a view is visible using the view table 401 generated in Embodiment 1. This embodiment will primarily describe the differences from Embodiment 1. Matters not described below are the same as in Embodiment 1.
[0058] ***Explanation of the structure*** In this embodiment, the simulation execution unit 500 shown in Figure 2 will be described. The simulation execution unit 500 consists of a moving object simulation unit 600, a sensor simulation unit 700, and a line-of-sight processing unit 800.
[0059] The moving object simulation unit 600 simulates the behavior of the target (moving object). The moving object simulation unit 600 specifies the position of the target and notifies the line-of-sight processing unit 800 of the position of the specified target.
[0060] The sensor simulation unit 700 simulates the behavior of the sensor that observes the target. The sensor simulation unit 700 specifies the position where the sensor will observe the target (hereinafter referred to as the observation point) and notifies the line-of-sight processing unit 800 of the specified observation point.
[0061] The line-of-sight processing unit 800 determines whether the sensor can see the target from the observation point. The line of sight processing unit 800 includes a line of sight calculation unit 801, a line of sight table acquisition unit 802, and a line of sight feasibility determination unit 803.
[0062] The forecast calculation unit 801 performs forecast calculation processing. Specifically, the line-of-sight calculation unit 801 calculates the target azimuth angle AZ and the target elevation angle EL. The line-of-sight calculation unit 801 also calculates the target horizontal distance L as needed. The target azimuth angle AZ is the azimuth angle of the target relative to the observation point. The target elevation angle EL is the elevation angle required to see the target from the observation point. The target horizontal distance L is the horizontal distance from the observation point to the target. Figure 9 shows an example of an observation point, a target, a target azimuth angle AZ, a target elevation angle EL, and a target horizontal distance L.
[0063] The forecast table acquisition unit 802 performs the forecast table acquisition process. Specifically, the forecast table acquisition unit 802 acquires the forecast table 401 from the forecast table storage unit 400.
[0064] The line-of-sight determination unit 803 performs a line-of-sight determination process. Specifically, the line-of-sight determination unit 803 determines whether the sensor can see the target from the observation point based on the target azimuth angle AZ and target elevation angle EL calculated by the line-of-sight calculation unit 801 and the line-of-sight table 401. In addition, the line-of-sight determination unit 803 determines whether the sensor can see the target from the observation point based on the target horizontal distance L calculated by the line-of-sight calculation unit 801, if necessary.
[0065] ***Explanation of operation*** Next, the process for determining visibility according to this embodiment will be explained with reference to the flowchart in Figure 8.
[0066] First, in step S801, the line-of-sight calculation unit 801 calculates the target azimuth angle AZ and the target elevation angle EL. Specifically, the line-of-sight calculation unit 801 is notified of the observation point from the sensor simulation unit 700 and the target position from the moving object simulation unit 600. The line-of-sight calculation unit 801 then calculates the target azimuth angle AZ and target elevation angle EL, which are the azimuth angle and elevation angle when observing the target from the observation point. Furthermore, the line-of-sight calculation unit 801 can calculate the target azimuth angle AZ and target elevation angle EL using existing methods. The line-of-sight calculation unit 801 notifies the line-of-sight determination unit 803 of the observation point, target azimuth angle AZ, and target elevation angle EL.
[0067] Next, in step S802, the line-of-sight table acquisition unit 802 acquires the line-of-sight table 401 from the line-of-sight table storage unit 400. The line-of-sight table acquisition unit 802 outputs the line-of-sight table 401 to the line-of-sight feasibility determination unit 803. The line-of-sight determination unit 803 refers to the line-of-sight table 401 and obtains the maximum line-of-sight elevation angle ELMAX at the line-of-sight azimuth angle 403 corresponding to the target azimuth angle AZ with respect to the line-of-sight reference point 402 corresponding to the observation point, as shown in the line-of-sight table 401. The line-of-sight elevation angle ELMAX corresponds to the first line-of-sight elevation angle.
[0068] Next, in step S803, the line-of-sight determination unit 803 compares the target elevation angle EL with the maximum line-of-sight elevation angle ELMA obtained from the line-of-sight table 401. If the target elevation angle EL is greater than the maximum line-of-sight elevation angle ELMAX, the line-of-sight determination unit 803 determines that the target is visible from the sensor (step S804). On the other hand, if the target elevation angle EL is less than or equal to the maximum line-of-sight elevation angle ELMAX, the process in step S805 is performed.
[0069] In step S805, the line-of-sight calculation unit 801 calculates the target horizontal distance L. The line-of-sight calculation unit 801 can calculate the target horizontal distance L using existing methods. The line-of-sight calculation unit 801 notifies the line-of-sight determination unit 803 of the target horizontal distance L.
[0070] Next, in step S806, the line-of-sight determination unit 803 extracts the maximum line-of-sight horizontal distance L2 that does not exceed the target horizontal distance L from the line-of-sight horizontal distance 405 at the line-of-sight azimuth angle 403 corresponding to the target azimuth angle AZ with respect to the line-of-sight reference point 402 corresponding to the observation point, as shown in the line-of-sight table 401. The line-of-sight determination unit 803 then extracts the line-of-sight elevation angle 404, which is paired with the line-of-sight horizontal distance L2, as the line-of-sight elevation angle EL2. The line-of-sight elevation angle EL2 corresponds to the second line-of-sight elevation angle.
[0071] Next, in step S807, the line-of-sight determination unit 803 compares the target elevation angle EL with the line-of-sight elevation angle EL2. If the target elevation angle EL is greater than the line-of-sight elevation angle EL2, the line-of-sight determination unit 803 determines that the target is visible from the sensor (step S808). On the other hand, if the target elevation angle EL is less than or equal to the line-of-sight elevation angle EL2, the line-of-sight determination unit 803 determines that the target cannot be seen from the sensor (step S809).
[0072] For example, in the example shown in Figure 10, the visibility determination unit 803 determines that target A is not visible and that target B is visible.
[0073] Using the results of the above visibility determination, the simulation execution unit 500 performs a simulation. For example, the simulation execution unit 500 performs a simulation based on the premise that target A shown in Figure 10 is not visible and target B is visible.
[0074] ***Explanation of the effects of the embodiment*** By performing the visibility determination described in Embodiment 2 using the visibility table 401 generated in Embodiment 1, visibility determination can be performed with greater accuracy than conventional methods, even in terrain with multiple mountains and valleys.
[0075] Embodiment 3. This embodiment describes a method for generating a line-of-sight table 401 and determining whether a line of sight is possible when structures such as buildings are placed in the surrounding area. This embodiment will primarily describe the differences from Embodiment 1. Matters not described below are the same as in Embodiment 1.
[0076] ***Explanation of the structure*** Figure 11 shows an example of the functional configuration of the simulation device 100 according to this embodiment. Compared to Figure 2, Figure 11 includes the addition of a line-of-sight table acquisition unit 306, a structure height data acquisition unit 307, a structure height data storage unit 900, and structure height data 901.
[0077] The forecast table acquisition unit 306 acquires the forecast table 401 from the forecast table storage unit 400. Then, the forecast table acquisition unit 306 outputs the forecast table 401 to the forecast table generation unit 304.
[0078] The structure height data storage unit 900 stores the structure height data 901. The structure height data storage unit 900 is implemented, for example, by an auxiliary storage device 103.
[0079] Structure height data 901 is data that defines the coordinates and height information of structures located at specific points within a certain geographical range.
[0080] The structure height data acquisition unit 307 acquires structure height data 901 from the structure height data storage unit 900. Then, the structure height data acquisition unit 307 outputs the structure height data 901 to the remote area determination unit 303.
[0081] ***Explanation of operation*** Next, an example of the operation of the forecast table processing unit 300 according to this embodiment will be described with reference to the flowchart in Figure 12.
[0082] This embodiment describes a method for generating a line-of-sight table 401 when the elevation changes due to structures recorded in the structure height data 901.
[0083] First, in step S1201, the line-of-sight table acquisition unit 306 checks whether an existing line-of-sight table 401 based on elevation data 201 exists. If there is no existing line of sight table based on elevation data 201, the line of sight table generation unit 304 generates a line of sight table 401 based on elevation data 201 according to the procedure described in Embodiment 1 (step S1202).
[0084] If an existing line of sight table 401 based on elevation data 201 exists, or if the line of sight table 401 is generated in step S1202, in step S1203, the line of sight table acquisition unit 306 acquires the line of sight reference points 402 that exist in the line of sight table 401.
[0085] Next, in step S1204, the structure height data acquisition unit 307 acquires structure height data 901 from the structure height data storage unit 900. The structure height data acquisition unit 307 outputs the structure height data 901 to the remote area determination unit 303.
[0086] Next, in step S1205, the distant area determination unit 303 identifies structure height data 901 corresponding to structures in the area surrounding the line-of-sight reference point 402. In other words, the distant area determination unit 303 identifies structure height data 901 corresponding to structures in areas other than the distant area. The remote area determination unit 303 identifies structures located in areas other than the remote area using existing methods. The specific method for identifying the remote area will be explained in Embodiment 4. The distant area determination unit 303 outputs structure height data 901 corresponding to structures present in the surrounding area to the line-of-sight table generation unit 304.
[0087] Next, in step S1206, the line-of-sight table generation unit 304 determines whether the mesh to be processed is a mesh in a distant area. The operation in step S1206 is the same as the operation in step S603 in Figure 6, so the explanation is omitted.
[0088] Next, in step S1207, the line-of-sight table generation unit 304 calculates line-of-sight elevation angle candidates for the target mesh at the line-of-sight azimuth angle 403 with respect to the line-of-sight reference point 402, using the same method as the method for calculating line-of-sight elevation angle candidates in step S604 of Figure 6. However, in step S1207, the line-of-sight table generation unit 304 calculates a candidate line-of-sight elevation angle based on the corrected elevation. The corrected elevation is the elevation obtained by adding the elevation of the point where the structure is placed and the height of the structure. The line of sight table generation unit 304 obtains the elevation of the location where the structure is placed from the elevation data 201. The line of sight table generation unit 304 also obtains the height of the structure from the structure height data 901.
[0089] Figure 13 shows an example of the operation of the forecast table generation unit 304 in step S1207. In the example shown in Figure 13, the line-of-sight table generation unit 304 treats the corrected elevation obtained by adding the elevation of the location where structure 1 is located and the height of structure 1 as the line-of-sight limit point 1, and calculates the line-of-sight elevation angle candidate 1. Similarly, the line-of-sight table generation unit 304 treats the corrected elevation obtained by adding the elevation of the location where structure 2 is located and the height of structure 2 as the line-of-sight limit point 2, and calculates the line-of-sight elevation angle candidate 2.
[0090] Next, in step S1208, the line-of-sight table generation unit 304 determines whether or not the processing in step S1207 has been performed for all meshes corresponding to the area surrounding the line-of-sight reference point 402. If the process in step S1207 has been performed for all meshes corresponding to the area surrounding the line-of-sight reference point 402 (YES in step S1208), then the operations from step S608 onwards in Figure 6 will be performed. On the other hand, if there are meshes that have not undergone the processing in step S1207 (resulting in NO in step S1208), the process returns to step S1206.
[0091] The line-of-sight visibility determination using the line-of-sight table 401 generated based on the corrected elevation according to this embodiment can be performed in the same manner as in Embodiment 2.
[0092] ***Explanation of the effects of the embodiment*** Through the above process, it is possible to accurately determine whether visibility is possible even when structures are present.
[0093] Furthermore, in this embodiment, since the existing forecast table 401 can be utilized, the processing time can be reduced compared to generating a new forecast table 401.
[0094] Embodiment 4. This embodiment describes a method for identifying distant areas that are affected by the curvature of the Earth when observed from an observation point.
[0095] For mesh data where the distance from the line-of-sight reference point exceeds the threshold α, the line-of-sight effect is affected by the curvature of the Earth, making it impossible to see through the data. Therefore, this data does not need to be used to generate line-of-sight table 401. Here, the distance threshold α can be calculated using the altitude H0 of line-of-sight reference point 402 and the altitude HMAX of the highest altitude point around line-of-sight reference point 402, as shown in equation (1) below. However, θ in equation (1) is obtained from equation (2), and R in equation (2) is obtained from equation (3).
[0096]
number
[0097] Here, K is the mean Earth radius, and RE is the equivalent Earth radius ratio.
[0098] Although embodiments 1 to 4 have been described above, two or more of these embodiments may be combined and implemented. Alternatively, one of these embodiments may be partially implemented. Alternatively, two or more of these embodiments may be partially combined and implemented. Furthermore, the configurations and procedures described in these embodiments may be modified as needed.
[0099] ***Supplementary explanation of hardware configuration*** Here, we will provide a supplementary explanation of the hardware configuration of the simulation device 100. Processor 101 includes CPU, DSP, etc. CPU stands for Central Processing Unit. DSP stands for Digital Signal Processor. The main memory 102 is RAM. RAM stands for Random Access Memory. The auxiliary storage device 103 is a ROM, flash memory, HDD, etc. ROM stands for Read Only Memory. HDD stands for Hard Disk Drive. The communication device 104 is an electronic circuit that performs data communication processing. The communication device 104 is, for example, a communication chip or a NIC. NIC stands for Network Interface Card.
[0100] The auxiliary storage device 103 also stores the OS. OS stands for Operating System. Then, at least a portion of the OS is executed by processor 101. The processor 101 executes a program that implements the functions of the functional components shown in Figure 1, while executing at least a part of the OS. Processor 101 executes the OS, performing tasks such as task management, memory management, file management, and communication control. Furthermore, at least one of the information, data, signal values, and variable values indicating the processing results of the functional components shown in Figure 2 is stored in at least one of the main memory 102, auxiliary memory 103, registers in the processor 101, and cache memory. Furthermore, the programs that realize the functions of the functional components shown in Figure 2 may be stored on portable recording media such as magnetic disks, flexible disks, optical disks, compact disks, Blu-ray® disks, and DVDs. Portable recording media containing the programs that realize the functions of the functional components shown in Figure 2 may also be distributed.
[0101] Furthermore, at least one of the "parts" of the functional components shown in Figure 2 may be read as "circuit," "process," "procedure," "process," or "circuitry." Furthermore, the simulation device 100 may be implemented by a processing circuit. Examples of processing circuits include logic ICs, GAs, ASICs, and FPGAs. IC stands for Integrated Circuit. GA stands for Gate Array. ASIC stands for Application Specific Integrated Circuit. FPGA stands for Field-Programmable Gate Array. In this case, the functional components shown in Figure 2 are each implemented as part of the processing circuit. In this specification, the higher-level concept encompassing both the processor and the processing circuit is referred to as "processing circuitry." In other words, a processor and a processing circuit are specific examples of "processing circuits," respectively.
[0102] The various aspects of this disclosure are summarized below as an appendix. (Note 1) A unit for setting line-of-sight reference points, A data processing device having a line of sight table generation unit that, based on the elevation of the area surrounding the line of sight reference point, derives two or more pairs for each azimuth angle of line of sight elevation angle, which is the angle of elevation required to see from the line of sight reference point to a line of sight limit point, which is a point that is visible from the line of sight reference point, and line of sight horizontal distance, which is the horizontal distance from the line of sight reference point to the line of sight limit point, and generates a line of sight table in which the line of sight reference point is associated with two or more pairs of line of sight elevation angle and line of sight horizontal distance for each azimuth angle. (Note 2) The aforementioned forecast table generation unit, For each azimuth angle, based on the elevation of the target area which is the area in the direction of the target azimuth angle, the elevation angle required to have a clear view of each of the multiple observation points in the target area from the line-of-sight reference point is calculated as a candidate line-of-sight elevation angle, and the horizontal distance from the line-of-sight reference point to each of the multiple observation points is calculated as a candidate line-of-sight horizontal distance. The data processing device according to Appendix 1, which derives two or more pairs of line-of-sight elevation angle and line-of-sight horizontal distance from a plurality of pairs of line-of-sight elevation angle candidates and line-of-sight horizontal distance candidates for each of the plurality of observation points for each azimuth angle. (Note 3) The aforementioned forecast table generation unit, The data processing device according to Appendix 2, which arranges a plurality of candidate line-of-sight elevation angles in ascending order of the line-of-sight horizontal distance candidates that form a pair for each azimuth angle, and analyzes the arranged plurality of candidate line-of-sight elevation angles to derive two or more pairs of line-of-sight elevation angles and line-of-sight horizontal distances. (Note 4) The aforementioned forecast table generation unit, The data processing device according to Appendix 3, which repeats the following operations: selecting one line-of-sight elevation angle candidate at a time from a plurality of line-of-sight elevation angle candidates arranged in sequence as a comparative line-of-sight elevation angle candidate; comparing the comparative line-of-sight elevation angle candidate with the line-of-sight elevation angle candidate that is the largest line-of-sight elevation angle candidate among the line-of-sight elevation angle candidates preceding the comparative line-of-sight elevation angle candidate in sequence; treating the line-of-sight elevation angle candidate that is paired with the line-of-sight elevation angle candidate as the line-of-sight elevation angle candidate if the comparative line-of-sight elevation angle candidate is less than or equal to the line-of-sight elevation angle candidate; and treating the line-of-sight horizontal distance candidate paired with the line-of-sight elevation angle candidate as the line-of-sight horizontal distance if the comparative line-of-sight elevation angle candidate is greater than the line-of-sight elevation angle candidate; thereby deriving two or more pairs of line-of-sight elevation angles and line-of-sight horizontal distances. (Note 5) The aforementioned forecast table generation unit, A data processing device according to any one of the appendices 1 to 4, which derives two or more pairs of the line-of-sight elevation angle and the line-of-sight horizontal distance for each azimuth angle, based on a corrected elevation obtained by adding the height of structures located in the surrounding area to the elevation of the surrounding area. (Note 6) The data processing device further, It has a distant area determination unit that determines distant areas that cannot be seen from the aforementioned line-of-sight reference point due to the effect of the curvature of the Earth, The aforementioned forecast table generation unit, A data processing device according to any one of the appendices 1 to 4, wherein the area obtained by excluding the distant area determined by the distant area determination unit from the area centered on the aforementioned line of sight reference point is treated as the surrounding area. (Note 7) The data processing device further, A data processing device according to any one of the appendices 1 to 6, comprising a line-of-sight determination unit that determines whether or not a target can be seen from a designated observation point using the line-of-sight table generated by the line-of-sight table generation unit. (Note 8) The data processing device further, The unit includes a line-of-sight calculation unit that calculates the azimuth angle of the target relative to the observation point as the target azimuth angle, and the elevation angle required to see the target from the line-of-sight reference point as the target elevation angle. The aforementioned unit for determining whether or not the view is visible is: A data processing device according to Appendix 7, which compares a first line of sight elevation angle, which is the largest of two or more line of sight elevation angles for the azimuth angle corresponding to the target azimuth angle with respect to the line of sight reference point corresponding to the observation point shown in the line of sight table, with the target elevation angle, and determines that the target can be seen from the observation point if the target elevation angle is greater than the first line of sight elevation angle. (Note 9) The aforementioned forecast calculation unit, If the target elevation angle is less than or equal to the first line-of-sight elevation angle, the horizontal distance from the observation point to the target is calculated as the target horizontal distance. The aforementioned unit for determining whether or not the view is visible is: The data processing device according to Appendix 8, which extracts the largest horizontal line of sight distance that does not exceed the target horizontal distance from among two or more horizontal line of sight distances for an azimuth angle corresponding to the target azimuth angle with respect to a line of sight reference point corresponding to the observation point shown in the line of sight table, extracts the elevation angle paired with the extracted largest horizontal line of sight distance as a second elevation angle of sight, compares the second elevation angle of sight with the target elevation angle, and determines that the target can be seen from the observation point if the target elevation angle is greater than the second elevation angle of sight. (Note 10) The computer sets a line-of-sight reference point, A data processing method in which the computer derives two or more pairs of line-of-sight elevation angles, which are the elevation angles required to see a line-of-sight limit point (a point that is visible from the line-of-sight reference point) from the line-of-sight reference point, and line-of-sight horizontal distances, which are the horizontal distances from the line-of-sight reference point to the line-of-sight limit point, based on the elevation of the area surrounding the line-of-sight reference point, for each azimuth angle, and generates a line-of-sight table in which the line-of-sight reference point is associated with two or more pairs of line-of-sight elevation angles and line-of-sight horizontal distances for each azimuth angle. (Note 11) The process of setting a reference point for line of sight, A data processing program that causes a computer to perform a line-of-sight table generation process, which, based on the elevation of the area surrounding the line-of-sight reference point, derives two or more pairs for each azimuth angle of line-of-sight elevation angle, which is the angle of elevation required to see a line-of-sight limit point (a point that is visible from the line-of-sight reference point), and line-of-sight horizontal distance, which is the horizontal distance from the line-of-sight reference point to the line-of-sight limit point, and generates a line-of-sight table in which the line-of-sight reference point is associated with two or more pairs of line-of-sight elevation angles and line-of-sight horizontal distances for each azimuth angle. [Explanation of Symbols]
[0103] 100 Simulation device, 101 Processor, 102 Main memory, 103 Auxiliary memory, 104 Communication device, 200 Elevation data storage unit, 201 Elevation data, 300 Line of sight table processing unit, 301 Elevation data acquisition unit, 302 Line of sight reference point setting unit, 303 Distant area determination unit, 304 Line of sight table generation unit, 305 Line of sight table output unit, 306 Line of sight table acquisition unit, 307 Structure height data acquisition unit, 400 Line of sight table storage unit, 401 Line of sight table, 402 Line of sight reference point, 403 Line of sight azimuth angle, 404 Line of sight elevation angle, 405 Line of sight horizontal distance, 406 Temporary storage table, 500 Simulation execution unit, 600 Moving object simulation unit, 700 Sensor simulation unit, 800 Line of sight feasibility processing unit, 801 Line of sight calculation unit, 802 Line of sight table acquisition unit, 803 Line of sight determination unit, 900 Structure height data storage unit, 901 Structure height data.
Claims
1. A unit for setting line-of-sight reference points, A data processing device having a line of sight table generation unit that, based on the elevation of the area surrounding the line of sight reference point, derives two or more pairs for each azimuth angle of line of sight elevation angle, which is the angle of elevation required to see from the line of sight reference point to a line of sight limit point, which is a point that is visible from the line of sight reference point, and line of sight horizontal distance, which is the horizontal distance from the line of sight reference point to the line of sight limit point, and generates a line of sight table in which the line of sight reference point is associated with two or more pairs of line of sight elevation angle and line of sight horizontal distance for each azimuth angle.
2. The aforementioned forecast table generation unit, For each azimuth angle, based on the elevation of the target area which is the area in the direction of the target azimuth angle, the elevation angle required to have a clear view of each of the multiple observation points in the target area from the line-of-sight reference point is calculated as a candidate line-of-sight elevation angle, and the horizontal distance from the line-of-sight reference point to each of the multiple observation points is calculated as a candidate line-of-sight horizontal distance. The data processing device according to claim 1, wherein for each azimuth angle, two or more pairs of line-of-sight elevation angle and line-of-sight horizontal distance are derived from a plurality of pairs of line-of-sight elevation angle candidates and line-of-sight horizontal distance candidates for the plurality of observation points.
3. The aforementioned forecast table generation unit, The data processing device according to claim 2, wherein for each azimuth angle, a plurality of candidate line-of-sight elevation angles are arranged in ascending order of the pair of candidate line-of-sight horizontal distances, and the arranged plurality of candidate line-of-sight elevation angles are analyzed to derive two or more pairs of line-of-sight elevation angles and line-of-sight horizontal distances.
4. The aforementioned forecast table generation unit, The data processing device according to claim 3, which selects one line of sight elevation angle candidate at a time from a plurality of line of sight elevation angle candidates arranged in sequence as a comparative line of sight elevation angle candidate, compares the comparative line of sight elevation angle candidate with the line of sight elevation angle candidate to be compared, which is the largest line of sight elevation angle candidate among the line of sight elevation angle candidates preceding the comparative line of sight elevation angle candidate in sequence, treats the line of sight elevation angle candidate to be compared as the line of sight elevation angle candidate if the comparative line of sight elevation angle candidate is less than or equal to the line of sight elevation angle candidate to be compared, and treats the line of sight horizontal distance candidate paired with the line of sight horizontal distance if the comparative line of sight elevation angle candidate is greater than the line of sight elevation angle candidate to be compared, and repeats this operation to derive two or more pairs of line of sight elevation angle and line of sight horizontal distance.
5. The aforementioned forecast table generation unit, The data processing device according to claim 1, which derives two or more pairs of the line-of-sight elevation angle and the line-of-sight horizontal distance for each azimuth angle, based on a corrected elevation obtained by adding the height of structures located in the surrounding area to the elevation of the surrounding area.
6. The data processing device further, It has a distant area determination unit that determines distant areas that cannot be seen from the aforementioned line-of-sight reference point due to the effect of the curvature of the Earth, The aforementioned forecast table generation unit, The data processing device according to claim 1, wherein the area obtained by excluding the distant area determined by the distant area determination unit from the area centered on the line of sight reference point is treated as the surrounding area.
7. The data processing device further, The data processing device according to claim 1, further comprising a line-of-sight determination unit that determines whether or not a target can be seen from a designated observation point using the line-of-sight table generated by the line-of-sight table generation unit.
8. The data processing device further, The unit includes a line-of-sight calculation unit that calculates the azimuth angle of the target relative to the observation point as the target azimuth angle, and the elevation angle required to see the target from the line-of-sight reference point as the target elevation angle. The aforementioned unit for determining whether or not the view is visible is: The data processing device according to claim 7, which compares a first line of sight elevation angle, which is the largest of two or more line of sight elevation angles for the azimuth angle corresponding to the target azimuth angle with respect to the line of sight reference point corresponding to the observation point shown in the line of sight table, with the target elevation angle, and determines that the target can be seen from the observation point if the target elevation angle is greater than the first line of sight elevation angle.
9. The aforementioned forecast calculation unit, If the target elevation angle is less than or equal to the first line-of-sight elevation angle, the horizontal distance from the observation point to the target is calculated as the target horizontal distance. The aforementioned unit for determining whether or not the view is visible is: The data processing device according to claim 8, which extracts the largest horizontal line of sight distance that does not exceed the target horizontal distance from among two or more horizontal line of sight distances for an azimuth angle corresponding to the target azimuth angle with respect to a line of sight reference point corresponding to the observation point shown in the line of sight table, extracts the elevation angle paired with the extracted largest horizontal line of sight distance as a second elevation angle of sight, compares the second elevation angle of sight with the target elevation angle, and determines that the target can be seen from the observation point if the target elevation angle is greater than the second elevation angle of sight.
10. The computer sets a line-of-sight reference point, A data processing method in which the computer derives two or more pairs of line-of-sight elevation angles, which are the elevation angles required to see a line-of-sight limit point (a point that is visible from the line-of-sight reference point) from the line-of-sight reference point, and line-of-sight horizontal distances, which are the horizontal distances from the line-of-sight reference point to the line-of-sight limit point, based on the elevation of the area surrounding the line-of-sight reference point, for each azimuth angle, and generates a line-of-sight table in which the line-of-sight reference point is associated with two or more pairs of line-of-sight elevation angles and line-of-sight horizontal distances for each azimuth angle.
11. The process of setting a reference point for line of sight, A data processing program that causes a computer to perform a line-of-sight table generation process, which, based on the elevation of the area surrounding the line-of-sight reference point, derives two or more pairs for each azimuth angle of line-of-sight elevation angle, which is the angle of elevation required to see a line-of-sight limit point (a point that is visible from the line-of-sight reference point), and line-of-sight horizontal distance, which is the horizontal distance from the line-of-sight reference point to the line-of-sight limit point, and generates a line-of-sight table in which the line-of-sight reference point is associated with two or more pairs of line-of-sight elevation angles and line-of-sight horizontal distances for each azimuth angle.
Citation Information
Patent Citations
Information processor
JP2010224198A
