<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://hist1952-17.omeka.fas.harvard.edu/items/browse?output=omeka-xml&amp;page=7" accessDate="2026-05-11T13:43:00-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>7</pageNumber>
      <perPage>10</perPage>
      <totalResults>88</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="33" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="133">
                <text>Layer 4: Military Administrative Details - Security Classification &amp; Reference Info</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134">
                <text>This layer contains the security classification level of the map, as well as the name of the location, date the map was created, and information on who prepared it. The latter three items serve as important reference points for the map reader(s), who would need to: (1) distinguish beach #3 from other military beach sites in close proximity, (2) know how far in advance/up-to-date the map was created prior to the planned Lingayen Gulf landing, particularly if dates for the landing were to change, and (3) know who to contact with questions or hold accountable if an unfortunate situation were to play out based on the information provided through this map.&#13;
&#13;
The ‘Top Secret’ security classification is particularly important because it indicates that only a select few have the authorization to read the map and how they should treat the information contained in it. More specifically, the contents of the map are of such importance that unauthorized disclosure of the information could cause damage to U.S. national security. Without yet scrutinizing the rest of the map, the reader(s) would immediately know that its contents carry significant weight. Visually, it contains the largest written font and is the only information that exists outside of the map’s grid lines, again suggesting its importance.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135">
                <text>Map Layer</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="136">
                <text>Joa Alexander</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="32" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="130">
                <text>Layer 3: Roads</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="131">
                <text>Another critical function of this map was to show the reader(s) how to move personnel and supplies around the beach area and, more importantly, further inland. This layer shows the roads—perhaps existing (represented by the solid lines) and planned (represented by the dashed lines)—that would be used for such movement and transportation purposes.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="132">
                <text>Map Layer</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="137">
                <text>Joa Alexander</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="31" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="127">
                <text>Layer 2: Base Camp Layout</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="128">
                <text>One of the key purposes of this map was to provide the reader(s) with a plan for where to place specific military personnel and supplies/equipment upon landing on the beach. This information is conveyed through symbols, numbers, and acronyms, which the intended reader(s) was arguably trained to comprehend on sight as there is no key/legend provided on the map. This layer contains the symbols the planner used in creating the military base layout and in conveying information on placement of personnel and supplies.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="129">
                <text>Map Layer</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138">
                <text>Joa Alexander</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="30" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="122">
                <text>Layer 1: Water</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="124">
                <text>This layer shows the map reader(s) where bodies of water are located. Knowing the location and layout of water was important for at least two reasons: (1) it indicated where barriers and entryways to accessing land further inland existed, and (2) it helped planners determine where to station personnel, and subsequently supplies/equipment. More specifically, personnel were situated close to water, presumably for washing and perhaps drinking purposes.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="126">
                <text>Map Layer</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="139">
                <text>Joa Alexander</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="28" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="115">
                <text>Layer 4: Celestial Context</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="116">
                <text>This layer is a zoomed out "frame of reference" composed of the illustrations around the circles containing the geographic information of the other three layers. Following Harley, I argue that this is more than just a pretty picture but actually says something about how the mapmaker sees the world. The presence of angels, cherubs, and Zodiac motifs (including Pisces, Gemini, and Cancer) implies a sort of "Celestial context," showing how the earth is surrounded by the abodes of stars and angels. Situating the map's world within Hellenic and Christian cosmology expresses a particular view of the world and its environs that is more than incidental to the map's meaning.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="120">
                <text>Julian Rauter</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="27" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="113">
                <text>Layer 3: Sociopolitical Context</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="114">
                <text>This layer is composed of toponyms and added color. Though the map includes names of regions and even a few cities, I was unable to reliably trace anything smaller than the names of continents and oceans. I call these "sociopolitical" because they represent what the evidently European cartographers called these bodies of land and water. They paint the world from a specific perspective that draws on the totalizing power of the map as an instrument of colonial control over land. I believe this is further demonstrated by the outlines of continents. Europe is in pink, Africa in green, and the Americas and Australasia in yellow. There seems to be some organizing scheme to this peculiar choice of color, but I cannot completely identify it. The fact that Asia is in yellow defeats the idea that it might be New World vs. Old World. It seems more likely to be highlighting a divide between Europe and the rest of the world, but if so why is Africa a different color? Though I cannot exactly identify the reasoning, it seems evident that the continents are outlined differently for more than a simple geographic reason. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="119">
                <text>Julian Rauter</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="26" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="111">
                <text>Layer 2: Physical Forms</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="112">
                <text>This layer contains the physical shapes of continents and islands as understood at the time of the map's creation. It is in many ways the real substance of the map, whose intention seems to be showing "the whole world." The majority of detail is in the coastlines, but there are a few places with small mountain ranges. There is also an extensive mapping of rivers and lakes. The physical forms are presented as they were understood, and unmapped territory literally just peters off into nothing, as can be seen notably in the areas that we now call Eastern Australia and Alaska. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="118">
                <text>Julian Rauter</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="25" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="109">
                <text>Layer 1: Geometric Template</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="110">
                <text>This layer is the combined latitude and longitude lines of the map, complete with degrees and other lines of reference. It demarcates the physical system of space measurement that lends credence to the map's representation of area. It also serves as a reference point for distance and the respective shapes and positions of landmasses. I made it the first layer because the drawing of landmasses presupposes a reliable system for determining the relative positions and areas of objects in space. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="117">
                <text>Julian Rauter</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="24" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="106">
                <text>Layer 4: Periphery</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107">
                <text>Layer four serves to expand upon layer three’s introduction of geographic sense of space, while also complementing and contributing to a developing narrative of inner city centrality. A large number of geographic features and indicators are introduced giving a sense that, relative to the center city, the periphery is defined by these natural features whereas the center is defined by its density (taking the overflow index as a comparative analog). These features include large swaths of map area populated trees colored green along with others which remain uncolored. This simultaneously adds a sense of pastoralism through use of green, along with a lack of spatial cohesion via the seemingly inconsistent use of color in contrast to the uniformly shaded city center. This sense of fragmentation is further exaggerated by the use of pink, and the fact that both of these colors are used over several different districts. This characterizes the periphery as an area which while districted (D,E,F, G, and H), has less definite boundaries than the city center, and is more fluid. To this end it is also worth mentioning that it is impossible to look at layer four and not see, simultaneously, the area that defines layer three by exclusion, adding to this distinct separation between the center and the periphery. Adding to this contrasting pastoral sense  are the graded hills which appear in the map’s lower right corner. With this one exception, this hill feature is shown exclusively outside the city’s walls. This further serves to connect districts D, E, F, G, and H with an already defined element of extra-mural space. Likewise, dashes in green colored space give a sense of lush grassland, which stands in contrast to the dense center. The only two arrows indicating river flow are also located at the ends of the map, giving a sense that the importance of natural phenomenon are more peripheral. Open featureless space which takes up large swaths of district F also serve to strongly deemphasize the importance of peripheral space. Potentially most striking, however, is the idea that the relative size of districts D, E, and F to G and H may have informed the map maker’s decision to flip the maps orientation upside down. Flipping the map in this way (accounting for space taken up by the perspective illustration) allows the city center to remain close to the geometric center of the paper. Traditional orientation would have left the city center awkwardly close to the top of the map. As a reasonable explanation for the inverted orientation, this decision would work strongly with other evidence of the maps inclination toward a city center spatial emphasis. The benefit of this geometric centrality comes, in a way, at the expense of much of what seems “natural.”&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="108">
                <text>Ryan Taras</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="23" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="103">
                <text>Layer 3: Center</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="104">
                <text>The purpose of layers three and four is to build on the functionality established in layers one and two by introducing elements of physical geography, while also showing how the map presents geographical elements in a way which helps to further a narrative of an emphasized center city. Layer three builds on layers one and two by imparting geographical sense to the perspective, measuring tools, and elements of the built urban environment introduced in the first two layers. With two indices, large amounts of text, densely drawn buildings, and a perspective illustration it is easy to get lost in a plethora of “unnatural” or non-geographical information. The lines in layer three which outline three separately districted islands in the river Spree complement the spatially separated (but not explicitly bounded) capital letter markers of layer two by imposing geographical elements to classify and bound these points in representations of real space on the ground. Where before we had a cartesian plane, we now have points bounded by clearly identifiable elements of geography which could be seen on the ground (or in our perspective illustration). In this sense layer three brings the reader into the geographic reality of Berlin. Furthermore, the way the reader is engaged to interact with this defined geographic space begins to further a narrative of an emphasis on this sectionalized center city denoted by index sections A, B, and C (Berlin, Coln, and Federichs Werder). An entire “overflow index” in the map’s top right hand corner is is devoted to naming streets and other features in these three dense inner city districts. This represents a concerted effort on the part of the mapmaker to emphasize the importance of labeling these inner city features by taking up space elsewhere on the page in order to ensure that they are easily referenced. The city center is also shaded uniformly in a darker hue than spaces elsewhere on the map. This uniformity points to segmentation of these three districts within the city at large, and likewise emphasizes centrality of this geographical area. Additionally, the title box in the map’s lower left corner tells us that the city we are looking at is in fact called Berlin. This may seem a pedestrian or inconsequential observation, however, our index in layer two suggests that “Berlin” is just one of eight districts represented. This serves to strongly imply central importance of district A, and by extension of the uniform colorization of B and C, these districts as well. &#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105">
                <text>Ryan Taras</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
