<?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=3&amp;sort_field=added" accessDate="2026-05-05T21:33:59-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>3</pageNumber>
      <perPage>10</perPage>
      <totalResults>88</totalResults>
    </pagination>
  </miscellaneousContainer>
  <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="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="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="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="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="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="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="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="35" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
      <elementContainer>
        <element elementId="7">
          <name>Original Format</name>
          <description>The type of object, such as painting, sculpture, paper, photo, and additional data</description>
          <elementTextContainer>
            <elementText elementTextId="144">
              <text>map layer</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </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="142">
                <text>Layer 1: Spheres</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="143">
                <text>Perhaps the most intrinsic element of a map are the shapes which guide and inform the reader’s perspective. The art of transforming a three dimensional land mass into a two dimensional piece of paper is reliant on orienting the reader’s line of sight. Vischer’s Novissima totius terrarum orbis tabula relies on four spheroids with two depicting the East-West hemispheres that lie between a proposed meridian. The second set depict azimuthal projections of the North and South Poles where the Earth’s axis meets its surface–this means that the poles are mapped according to flat planes rather than the conic projections of the East-West Hemispheres. I chose not to include these projection lines, however, because of the symbolic nature of empty spheroids. Whereas layers of the map such as the continents, and land-water hemispheres inevitably depict the cartographer’s bias, spheroids are a simplistic and rather equalizing element of the map. They rid the map of the scale distortion that comes from projection lines as well as the colonial distortion that comes from continent/country inclusion.&#13;
I believe the spheroids to be the map in its most raw form.&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="147">
                <text>Reade Rossman</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="36" 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="145">
                <text>Layer 1: Field Terrain</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="146">
                <text>This layer depicts the fields on the outskirts of the territory of Berlin. They are distinct from the enclosed properties in and around the city, and are set off with horizontal lines. This field terrain is the most peripheral area depicted on the map of Berlin before the map turns to negative space, which suggests the field terrain was an important marker of the outer bounds of the city. I initially hesitated to isolate the field terrain from other types of terrain depicted on the map (for example, the map contains territories with gardens or other enclosed plots of land, populated with tiny trees), because terrain would technically belong in single layer. In the end, however, the field terrain stood out to me because its lack of definitive enclosure (unlike the contained plots of land), and its distinct color and shading. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="217">
                <text>Olga Kuzmina</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
