search.noResults

search.searching

dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
EARTH BY THE NUMBERS


FIGURE 2


FIGURE 3


STANDARDS TO SCALE


SE Core created a scale specification table to standardize how features are captured on terrain representations. SE Core’s common specifications rely on industry-standard graphics, so that those producing the require- ments and those meeting them speak the same language. At top, a KML representation of joint operations graphics, with examples of topographic line map series (TLM-100, bottom left; TLM-50, bottom right), capture requirements for Fort Bliss terrain. (SOURCE: Google Earth Pro)


Te SE Core team, a synthetic terrain stakeholder, or the capability manager can generate a graphical DCR by refer- encing the KML color code associated with each scale specification standard. Figure 1 on Page 178 provides an exam- ple of this using the SE Core Fort Bliss terrain requirements. A box of approxi- mately 300 km squared represents the 1:250K ancillary area of the terrain repre- sentation. Te figure illustrates the 1:50K area comprising the primary Fort Bliss training reservation. A primary live-fire range, the Digital, Multi-purpose Range Complex (DMPRC), is captured as a


180


VISUAL AND VERBAL Maps and text aren’t mutually exclusive ways to capture requirements. Creators of terrain requirements can add comments to Google Earth Pro, embedded in an overlay file. Here, a metadata comment gives additional reference data on the DMPRC live-fire range at Fort Bliss. (SOURCE: Google Earth Pro)


1:25K area, and the associated DMPRC air-to-ground integration villages are captured through the 1:12.5K fidelity area. Google Earth Pro’s measurement functions also allow for accurate area and perimeter calculations for each overlay to aid in the collection of metrics and gen- erating reports.


Te Google Earth Pro KML file approach to a DCR also allows for the capture of other required terrain representation components that would otherwise be burdensome to represent in a textual for- mat, such as aerial imagery requirements,


elevation data requirements, associated raster map


products and geospecific


model locations. Additionally, the KML standard allows for the inclusion of embedded metadata in the overlay file, which can be used to add comment fields to the KML overlays that can easily be displayed through the Google Earth Pro interface. (See Figures 3 and 4.) Tese comments can add useful reference data on a particular training area or provide additional requirements commentary— for example, the required terrain export formats and files for a given geographic area. Tis data can be useful for the


Army AL&T Magazine October-December 2015


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