<?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://usworld29.omeka.fas.harvard.edu/items/browse?collection=2&amp;output=omeka-xml&amp;page=5" accessDate="2026-08-03T06:17:04-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>5</pageNumber>
      <perPage>10</perPage>
      <totalResults>93</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="57" public="1" featured="0">
    <fileContainer>
      <file fileId="57">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/774885d7f8c54ec3848081bbc2b8a328.png</src>
        <authentication>c1a4768e66102f6f67ef97c9302e2a9d</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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>Eric Ronda</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="116">
                <text>I began my first sketch with outlining as well as detailing the buildings on the side of the river with the Athletic Facilities. After finishing the Athletic buildings I realized I had taken up over half of the page and still needed to include all of Harvard Square area and the Yard so I threw that sketch out and decided to start a new one. With the new sketch the first thing I did was map out the major buildings/parks on both the top and bottom sections of my paper to provide a basic outline and boundaries that I then filled in while completing the sketch. The basic grid outline of Harvard Square area was pretty simple to remember and sketch, however I ran into some difficulty trying to draw the tiny roads interviewing the river houses as well as which buildings were supposed to go on which plot of land. I also found it difficult to scale the roads and the buildings after creating the initial scale of the buildings on the athletic side of the river. Many of the buildings on the Academic side of the river turned out to be scaled differently because I was running out of room.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="56" public="1" featured="0">
    <fileContainer>
      <file fileId="56">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/f4f9647cbbe6f324d7bc3ba9c1f804cd.pdf</src>
        <authentication>d64cae6f1a2bf550cda4dfe7480c8f4c</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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>Carl Rogers</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="114">
                <text>I think that, just from looking at this sketch, it would be pretty obvious to any Harvard student where I live, at least to an extent. I began my sketch starting with my house, Dunster, in the bottom right corner, and planned to work northwest-ward as I went. Unfortunately, after getting caught up in the intricacies of the streets and other River houses, I realized too late that my scale was off, and that there was no way I would be able to include both the Yard and the Quad in my sketch. I’m fairly pleased with how I represented the River Houses (apart from Adams…which was affected by my confusion regarding “that one slanted street”—I couldn’t remember how Bow and Arrow street fit into the overall picture). My focus son the Houses, though, left a lot of the interesting parts of Harvard Square unsketched, and didn’t give me the chance to dig into my memory to see how much I could remember of my one year in the Yard.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="55" public="1" featured="0">
    <fileContainer>
      <file fileId="55">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/8155e2ac7d5f9e977b1d1be400845122.JPG</src>
        <authentication>bb632548aa96f1b3681b8886533c5f6d</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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>Daniel Prosky</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="112">
                <text>The first striking difference between my map and an accurate one is the scale and spacing, especially between streets. I found that I drew relatively accurate depictions of areas I know well, and either exaggerated or reduced the distance between these areas. For example, the true distance between Harvard Yard and Dunster House is far smaller than depicted on my map, while the distance between Harvard Yard and the Quad is a bit larger than I drew. The streets are generally correctly placed, though they are far less straight on the actual map than on my map from memory. I omitted some streets from my map, imagining connections between certain blocks that do not exist. These differences likely stem from my familiarity with certain areas and how I navigate between them. I was far more likely to imagine streets as straight North-South paths as opposed to the curved, sometimes winding avenues that they are. This exercise really shows that the way one moves and stops throughout a city has a great impact on how one imagines it to be physically organized.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="54" public="1" featured="0">
    <fileContainer>
      <file fileId="54">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/bd9f2892bd9e8b2cae0b4abfee5d24ee.JPG</src>
        <authentication>22c95c2d9c91773e5f693460676b4460</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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>Todd Preston</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="110">
                <text>My sketch includes a map of the Undergraduate campus at Harvard University, noting major roads and sidewalks that travel throughout the campus. An important note about my sketch is that it does not include all sidewalks, but rather the most congested sidewalks that can be found in Harvard Yard and throughout the Athletic fields. Additionally, the running trail along the river is another sidewalk that is heavily used and I found it was very important to include in my map. Roads are marked with arrows in order to indicate the direction of travel since most roads in the town of Cambridge are one-ways with an occasional two-way street. &#13;
&#13;
Scale plays an important role in my sketch because the building, roads, and sidewalks are not all drawn to scale. It is also important to note that the scale tends to vary between the different “main parts” of campus, including the River Housing, Harvard Yard, the Quad and the Athletic fields. Most of the blank space that surrounds the map is less detailed than the rest because I am very unfamiliar with the territory and felt it was best to leave it blank. As a Senior who is an athlete, I am very familiar with the Athletic fields but as a resident of Dunster, I have never been to the quad and am very unfamiliar with the layout of the Quad’s campus. &#13;
&#13;
On a related note to scale, there is an issue with spacing between buildings and sidewalks/roads. Although some buildings are nearly touching the road/sidewalk, it was important to draw them as separate lines and the spacing allowed me to provide a more detailed rendering of the areas and allowed me to provide insight including the direction of travel.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="53" public="1" featured="0">
    <fileContainer>
      <file fileId="53">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/565af3c0559029e2d2365f4c8be85685.jpg</src>
        <authentication>480b0784c7caf80ca07f0cc2336fbcd3</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="107">
                <text>Ellen Poile</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="108">
                <text>I found this exercise surprisingly difficult. Trying to layout my mental image of the square onto paper stumped me. First, I could not figure out how to orient Harvard Square onto the dimensions of my notebook paper. The question of fitting everything on the page with the proper scale left me grasping for the right size and direction of my landmarks. Not surprisingly, the yard occupies a much larger area than appropriate, as it was the easiest starting point. I knew how the buildings related to each other and I knew that it was generally a rectangle. This left me squeezing other parts onto too small areas of paper. However, even in the yard, I didn’t know the footprint or the number of certain dorms and buildings that I had never visited. In the bottom area of my map (between the yard and the river) I became overwhelmed in the details and number of features. As these blocks are where I live and spend most of my time, I knew the buildings and the streets the best. However, towards the river (down JFK) I do not spend as much time, so I became more confused. In fact, I ended up excluding an entire block and street between Mt. Auburn and Memorial Drive that consisted of buildings I do not use; I had simplified this area to only the houses. This led to a problem on the other side of JFK, where I knew there were commercial buildings and a park, yet I couldn’t make the streets match up. As a result, the scale on one side of JFK is different than the other. Interestingly, I found the streets the most difficult aspect of the map to draw. I remembered what buildings they led to and their names, but not their lengths and directions, particularly the streets that are not in a grid (such as Eliot St., Brattle St., Arrow St.). However, when I began my map, I instinctively began with the main streets. For my studies, this led me to zoom in on certain difficult areas to organize them, such as the intersection by the T and how the JFK and Mt. Auburn intersection (which I knew was a 90 degree intersection) related to the river. I discovered later that it was actually easier to place the buildings I knew in relation to each other and connect them with the appropriate streets. As I added more buildings, I realized how little space I had left. I had to erase and redraw many of my landmarks as smaller and re-angle my streets to fit everything. In the end, I was most surprised by what I had to omit. I knew I was missing things, such as Winthrop St, buildings in the yard, the streets leading to the quad, but I genuinely did not know what they were; I just sensed a lack. Things I had noticed and moved around but never used or named. I learned that after four years, I still do not know how to get to the Quad, so I left it out of my map.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="52" public="1" featured="0">
    <fileContainer>
      <file fileId="52">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/5cdf34b27891e1f1aea7a706135cf7cd.pdf</src>
        <authentication>31e087c33d7503595d3a69f59ec0fc76</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="105">
                <text>Adam Oh</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="106">
                <text>After having finished my sketch, I compared what I drew with some of the Google map renderings and realized a significant difference. Where I decided to notate things so that it was easier for me to draw, google maps shows much more detail. However, I have decided to include topological features to my map showing where there are slopes in the streets and the places most traveled by pedestrians and students. Google maps fails to include these features because their rendering is much more informational. Similarly, both my sketch and Google maps include the directionality of the traffic which I found to be pretty cool. The difference in both renderings could be due to the humans’ tendency to remember things based on landmarks. When I was drawing, I constantly tried to relate things to certain landmarks that I remembered seeing as I was walking. I also associated certain locations to certain memories so my renderings include much more of what I perceived as I walked through the square. In the end, our renderings achieve the same goal of showing the idea of what the square looks like, but they are represented in different perspectives.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="51" public="1" featured="0">
    <fileContainer>
      <file fileId="51">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/6cb4e461c5afcaa73ac95944f44b577a.jpg</src>
        <authentication>3ee0a0211a1ea9a8b8ffa727340453e4</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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>Harry NP</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="104">
                <text>The most notable difference between the actual plan of Harvard square (from the quad to the athletic ﬁelds) and my drawing was the overall shape of it. While on the small scale many of my areas were fairly accurate in terms of shape and size, overall the area from the quad, to Harvard yard, down to the athletic ﬁelds has a bit of a backwards C arch to it, whereas in my drawing they are much more directly in line with each other. I think this is indicative of how I experience this area. I don’t remember where all of the different streets are necessarily and how everything ﬁts together in the big picture (i.e. where the river changes course), but I have a decent memory for the local relations between buildings (i.e. what buildings I can see from the entrance to another). I knew almost all of the major landmarks, but their orientations were not precise.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="50" public="1" featured="0">
    <fileContainer>
      <file fileId="50">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/64ba4c7601ee2d29157d2d8077350c6a.JPG</src>
        <authentication>323c3e12ab4649c1e28862baa4b0eb10</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="101">
                <text>Quinn Mulholland</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="102">
                <text>I was surprised by how accurate my depiction of Harvard Yard and the&#13;
upperclassmen houses along the river was. I have a lot of familiarity with that area,&#13;
having lived in the Yard last year and spending a lot of time in the Kennedy School&#13;
or visiting friends in river houses. I think my map emphasizes roads almost as&#13;
prominently as buildings, which makes sense because I bike almost everywhere&#13;
(since I live in the Quad), so I have to navigate those roads everyday. I made the&#13;
roads that I bike on a lot, like Garden Street, Mass Ave, Mt. Auburn, and Brattle&#13;
Street bigger, because I’m more familiar with them. My depiction of other locations,&#13;
however, like buildings north of the Yard or east of Quincy Street, was less accurate,&#13;
probably because I spend less time in those locations. Something that surprised me&#13;
was that I completely forgot about some streets, even in parts of campus that I see&#13;
everyday, because I rarely go down them. I also severely underestimated the&#13;
distance between the Quad and the Yard, probably because I travel that distance&#13;
everyday. Additionally, I completely forgot about some of the freshman dorms in the&#13;
Yard—because I rarely went in them, but made my own dorm, Canaday, much larger&#13;
and more prominent than it really is.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="49" public="1" featured="0">
    <fileContainer>
      <file fileId="49">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/95895bf1eaec3751f0be7409d1b2d824.png</src>
        <authentication>3b3dedaed9d93f629d3a07095e8c6f21</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="99">
                <text>Drisana Mosaphir</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="100">
                <text>The main focus of this image was centered on finding where I experience the most motion within Harvard Square. Coming to the cross-section facing Mass. Ave. and the Yard from the T station, more specifically from the point of view of someone slightly above (e.g., in one of the stores behind the T station a few floors up) pinpointed the area in which I’ve been able to note, especially as a tour guide, the coming-together of so many people, from the groups who live outside the stores and spend much of their time on the benches in front of Mass Ave’s banks and businesses, to tourists attempting to orient themselves by the visitor center, to students throughout campus, to people commuting in and out of the station. Additionally, the bustle of the square and the openness of this area gave a good backdrop on which to reflect about the gates closing off the houses and the pathway to the Charles River. While campus is largely intertwined with the city, it is also evident through the opening and closing of these gates that the campus can be selective of how much access people get to us, despite the fact that the relationships doesn’t necessarily work in reverse.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="48" public="1" featured="0">
    <fileContainer>
      <file fileId="48">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/usworld29/original/c2d34a639c465349869fbe30a548810b.jpeg</src>
        <authentication>a312c78d49700ad997fbd98a9f053317</authentication>
      </file>
    </fileContainer>
    <collection collectionId="2">
      <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>SKETCH 1</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="97">
                <text>Urban design still remains a foreign concept: space, dimensions, structure can easily clutter the mind when drawing our fondest roads from memory. Despite the initial hesitation and frequent erasure marks, I believe the product that came out captured the spatial distribution of Harvard very closely. The map is not completely accurate, by no stretch of the imagination, but it really does encapsulate the most important landmarks of Harvard while respecting the spatial distribution of the urban/suburban settlement. Right off the back, the biggest difference I see is that of perception, meaning that in comparison to the actual map, my map elongates certain bottom portions. This is most apparent with Winthrop House which is my home, as well as the point of origin for the sketch. Winthrop is by no means the same size as the Science Center but the way I went about designing this map started from home and worked its way abroad causing certain levels of exaggeration in size for Winthrop (but not substantial). Furthermore, my map has very accurate points at times, the Yard, the walk to the Quad, the houses along the river symbolize places that matched up almost identically to the real map. This is most likely do to these places being centers of my life, and thus my memories that I can perfectly sketch them out. It seems that these three foci served as the triangle of urban planning for my mental map in which the great challenge was filling the in-between space and the peripheries with landmarks that I could easily recognize. &#13;
&#13;
As compared to a flat map, my map makes use of height in buildings that are stereotypically tall for the rather low (five floors or below) heights of the buildings in the area. The way it became manifested in the map was in the form of visual stylizations where a level of three-dimensionality was added to buildings like Memorial Hall, Annenberg Hall, The Smith Campus Center, the Leveret Towers among others. As a final note, somewhere that the two maps do align is with the demarcation of parks, green with the Google Maps and shaded in with my map. Parks and green spaces are extremely important in these areas, particularly considering the masses of brick buildings that align the streets, so there is extra attention placed on them for this unique purpose.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="98">
                <text>Daniel Montoya</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
