EARTH BY THE NUMBERS


FIGURE 5


CATALOGING COVERAGE Google Earth users can store multiple KML documents, which has allowed SE Core to create a portfolio—easily accessible and ready for collaboration—of its current terrain coverage. (SOURCE: Google Earth Pro)


create a slide presentation or PDF con- taining screenshots of each scale and AOI included in the KML file. Tis can be time-consuming, but is still more effi- cient and user-friendly than a traditional text-based requirements document. Te SE Core program is looking at methods to better automate the screen capture of KML overlays on Google Earth.


Unlike traditional word processing soft- ware, Google Earth Pro and KML files currently do not include any functions for tracking changes or edits. To view differences between two identical KML files, they must be laid onto each other and toggled on and off to visualize the changes. Other methods can also be used, such as temporarily swapping the color of an AOI overlay when sending it to


182


the requirements management authority. Until Google provides a better mecha- nism for tracking changes, it is imperative that users apply a rigorous configuration management process to maintain KML- based requirements documents.


CONCLUSION Te SE Core program and its confeder- ate simulation-system programs, such as the Aviation Combined Arms Tactical Trainer


(AVCATT), the Close Com-


bat Tactical Trainer and the Games for Training program, have met with great success using Google Earth Pro and KML files to visually track live, vir- tual, constructive and gaming terrain representation requirements. In conjunc- tion with the U.S. Army Training and Doctrine Command’s Program Office


Army AL&T Magazine October-December 2015


for Terrain at the National Simulation Center in Fort Leavenworth, KS, terrain representation requirements can be gen- erated in a fraction of the time previously spent on a text-based solution. Moreover, the requirements are in a portable and graphical format for efficient feedback and collaboration by terrain and simula- tion stakeholders.


Unambiguous terrain requirements are a key feature of the graphical DCR process, and the union of visual indicators with a graphical geographic interface guaran- tees that all stakeholders have a common frame of reference, which reduces the time spent communicating and solidify- ing a given synthetic terrain requirement. Tis explicit requirements capability, cou- pled with rapid requirements generation


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176  |  Page 177  |  Page 178  |  Page 179  |  Page 180  |  Page 181  |  Page 182  |  Page 183  |  Page 184  |  Page 185  |  Page 186  |  Page 187  |  Page 188  |  Page 189  |  Page 190  |  Page 191  |  Page 192  |  Page 193  |  Page 194  |  Page 195  |  Page 196  |  Page 197  |  Page 198  |  Page 199  |  Page 200  |  Page 201  |  Page 202  |  Page 203  |  Page 204  |  Page 205  |  Page 206  |  Page 207  |  Page 208