<?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=Dublin+Core%2CTitle" accessDate="2026-05-08T07:20:03-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>3</pageNumber>
      <perPage>10</perPage>
      <totalResults>88</totalResults>
    </pagination>
  </miscellaneousContainer>
  <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="2" 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="2">
                <text>Layer 1: Water Obstacles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3">
                <text>The dominant features, and therefore first layer of this map are the various water obstacles.  The water obstacles are denoted in dark blue and frame the map on the north, west, and east sides.  The water must be the first layer, as the rest of the layers deal with either circumventing or otherwise neutralizing the effects of the water on further military operations. Furthermore, the water and beach area represent the natural disorder associated with this type of terrain and the subsequent map layers show 533rd Engineer Beach and Shore Regiment’s attempt to organize and delineate this section of beach.  The map is small in scale and affords the creator a great of amount of detail.  Interestingly, he carefully depicted the current of the narrow rivers and individually drew trees and plant life in the marsh area.  I interpret this to mean that he thought it necessary to convey to the map users the in-accessibility of the areas outside of the road network. </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="57" 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="205">
                <text>Layer 2: Bodies of Water</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="206">
                <text>Description: Red bodies of water, 「西紅海」「東紅海」can be seen to the right of Libya and running down North America out into the Pacific Sea (which is not shown on the map), respectively.　「西南海」(Southwest Sea)「大南海」(Big South Sea)「東南海」(Southeast Sea) are all now non-existent seas that were originally from a map made in China in the 1400s. 「メカラ海」(Mekala Sea) at the South Pole is a body of water North of a hypothetical continent, Terra Australis. There is also a mysterious body of water in Africa named 「古水」(Old Water).&#13;
 &#13;
Significance: The body of water named 「東紅海」runs from the middle of the North American continent toward the Pacific Ocean. This ocean, also called at the time, “Vermilion Sea” (or presumably the current day Gulf of Mexico) in European contexts, was thought to have completely separated and isolated the land of California from the North American continent, leaving the state’s boundaries untouched. This theory became popular in the 1700s and 1800s, when Japan was still in its “isolation” period, hence why the theory is not reflected in this map and providing possible evidence that Japan closed off its information network. Such occurrences can also be observed in the depiction of 「西南海」(Southwest Sea)「大南海」(Big South Sea)「東南海」(Southeast Sea), as they were originally bodies of water that were shown on Chinese maps produced in the 1400s. The cartographer may have attempted to compensate for his lack of knowledge in foreign bodies of water, especially in the Southern regions by bringing features from already existing Chinese maps. 「メカラ海」(Mekala Sea) located north of the fantasized continent of Terra Australis, or as the Japanese called it, “Megallanica”, could possibly represent the effort of the cartographer to stress the possible reality of the hypothetical continent’s existence. 「古水」(Old Water) located in the Southern regions of Libya (Africa) is difficult to identify as there are currently no bodies of water in the continent comparable to the size of this illustration.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="207">
                <text>Joki Kano</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="40" 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="158">
                <text>Layer 2: Fences and Fortifications</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="159">
                <text>This layer depicts the fortifications that mark the boundaries of the territory of Berlin, and which focus the viewer's attention on the center of the map. The northern boundary of the city appears to be a walled fortification, which gives way to a more primitive (perhaps wooden) fenced boundary on the southern side. The map depicts the materials from which the fortifications were made, and the layer seeks to reproduce this information. In the center of the map is another fortification that surrounds the heart of the city on what appears to be a man-made island in the center of the river Spree. While the map features numerous smaller fences that depict boundaries between private territories, I chose in this layer to isolate the main boundaries of the city as a distinct feature of the map that depicts these boundaries as structures in their own right.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="214">
                <text>Olga Kuzmina</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="44" 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="168">
                <text>Layer 2: Land Masses</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169">
                <text>This layer features colored depictions of the continents included in the map. I chose this layer to focus on the Japanese perspective of the globe, which includes very basic depictions of the continents. I noticed nearly every land mass, including even the smallest islands, has a label in Japanese. I hypothesized that perhaps this is connected to the fact that Japan itself is an island, located near even smaller islands and thus the mapmaker was accustomed to paying close attention to even the smallest of lands. The only topographical depictions included are mountains, what appears to be a small body of water, and an illustration I interpret to be Mount Fuji. The ocean is left uncolored, while all the land is filled in.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221">
                <text>Esther</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="51" public="1" featured="0">
    <fileContainer>
      <file fileId="3">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/hist1952-17/original/5c398a94f8a30aa46c4124dcbbad421e.JPG</src>
        <authentication>383e1b32a67a7972cd174891836eb28d</authentication>
      </file>
    </fileContainer>
    <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="186">
                <text>Layer 2: Land/Water Boundaries&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="187">
                <text>This layer shows the lines on the map corresponding to boundaries between land and water. This includes continental borders, seas, lakes, islands, and rivers. As this is a world map, including a layer for the continents and oceans was essential, yet it is important to emphasize that the continents aren’t just land masses: they have complex water systems in and around them. Additionally, many of these land/water boundaries are missing, incomplete, or even incorrect. These include Eastern Australia, the Northwest of North America, and the island of California.&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="188">
                <text>Matthew Goodman</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="37" 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="151">
              <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="148">
                <text>Layer 2: North &amp; South Poles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="149">
                <text>The North and South Poles, while taking up less space on the map, prove just as integral to the arguments of the map as the East-West Hemisphere split. They are depicted via azimuthal projections in which the distance from a center point is recorded while distorting size. More specifically, Vischer applies gnomonic map projection in which circles are depicted as straight lines. The fact that both the poles are relatively uninhabited allows Vischer to apply this method without worrying too much about the effect of such distortion. Novissima totius terrarum orbis tabula follows ptolemaic map projection in that it depicts two “frigid zones” however the map is absent of any conception of a southern land mass like Antarctica. The North Pole includes depictions of modern day Northern European countries and Russia. The depiction of the poles bolster the North-South bias of the map, portraying the North as the height of exploration and expansion and the south as vast and empty. As Professor Nicole De Armendi in Map as Political Agent, projections such as that included in Vischer’s map, “Antarctica is frequently eliminated and the equator is located much lower than midway on the grid, enhancing the North’s dominant position.” While the equator constitutes another layer of the map, the portrayal of the poles serves to fortify a notion of European domination.&#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="150">
                <text>Reade Rossman</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="22" 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="100">
                <text>Layer 2: Plane and Scale</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="101">
                <text>After being spatially situated via the perspective of the vantage point featured in layer one, layer two builds on this sense of location and place by introducing scale, and classification of points of interest in both space and text through use of alphanumerically coded districts. Upper case letters in the map space correspond to eight districts labelled in layer two’s index. Printed numbers in the map space likewise correspond to points of interest within these districts which are also enumerated in the layer two index. In the bottom left hand corner of the map, a scale in the archaic Ruthen (not standard, but roughly 15 feet) provides scale, while in the upper right hand corner, latitude and longitude readings situate Berlin more globally. Building on layer one, layer two accomplishes a number of things for the map’s reader. For one, It notably situates the reader globally via latitude and longitude, allowing for spatial comparison and integration with other maps. Use of the scale now enables quantifiable point to point spatial comparison. Additionally, categorization of points through district classification attaches recognizable linguistic meaning to spatial divisions, and imparts a sense of both spatial and linguistic order to what may otherwise seem an overwhelming distribution of points. More crucially, however, many of the features listed in layer two’s index are also featured in layer one’s index. This provides the reader with an easily referenceable link between what is shown pictorially in layer one, and spatially in layer two. Shown as an example are Dorotheen Stadt Kirche (number 27 in layer one and D3 in layer two) and Jerusalems Kirche (22 in layer one E3 in layer two). These churches are shown in layer one’s perspective picture, but now with the help of layer two, both can be situated in the xy plane, quite literally adding a dimension to the comprehension of these places. Their separating distance, and their respective distances from our windmill perspective can now be quantified definitively, endowing the reader with a sense of space entirely different than is offered in layer one. Furthermore, layer two’s index tells the reader that one church is situated in Dorotheen Stadt, and the other in Friderich’s Stadt which could prove useful information for on the ground navigation. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="102">
                <text>Ryan Taras</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
