Statistics for occurrence #1 of “Cross Keys” in chapter 11 of Brig.-Gen. Bradley T. Johnson, Confederate Military History, a library of Confederate States Military History: Volume 2.1, Maryland:
... found in the war records.)
Battles and actions in which the First Maryland infantry was engaged: Manassas, Mason's Hill, Munson's Hill, Rappahannock River, Front Royal, Winchester, Harrisonburg, Cross Keys , Mechanicsville, Gaines' Mill, Dispatch Station, Malvern Hill, Harrison Landing.
Lieutenant-Colonel, James R. Herbert; Major, Wm. W. Goldsborough; Surgeon, Richard P. Johnson; Assista...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
| † |
Cross Keys (Virginia, United States) |
424 |
18 |
20 |
0 |
0 user votes |
| † |
Cross Keys (Virginia, United States) |
2 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Alabama, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Alabama, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Delaware, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Jamaica) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Louisiana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Missouri, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (New Jersey, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Ohio, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Ohio, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Oregon, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Pennsylvania, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Pennsylvania, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Pennsylvania, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Pennsylvania, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (South Carolina, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Tennessee, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cross Keys (Tennessee, United States) |
0 |
0 |
0 |
0 |
0 user votes |
† This entity has been selected by the automated classifier as the most likely match in this context. It may or may not be the correct match.