Any place on the surface of the earth can be located in terms of three coordinates:
latitude, longitude, and elevation (height above sea level). In most of our work,
we are concerned with only the first two, latitude and longitude, because we don’t
(currently) envisage any rendering or data processing that would make use of elevation.
Traditionally, latitude and longitude were expressed in degrees, like this:
51°30'49.25"N 0° 5'58.42"W
These are the coordinates of St. Paul’s Cathedral. Notice that the longitude coordinate starts with zero. St. Paul’s is very close to Greenwich, through which the zero line of longitude, the prime meridian, runs.
In modern GIS systems, latitude and longitude are expressed in decimal numbers, which
look like this:
51.513557 -0.098369
You can see that these are the same basic numbers—latitude measured as distance north
or south from the equator, longitude measured as distance east or west from the prime
meridian—but they’re expressed in a form that enables computers to do math with them
more easily.
Coordinates like this are usually comma-separated, like this:
51.513557,-0.098369
and if elevation is also included, it comes last, like this:
At the moment, historical geo-coordinates are not nearly as readily available as modern-day
geo-coordinates. Generally speaking, those who wish to work with historical geographic
data are expected to infer geo-coordinates from their own research. We can infer the
geo-coordinates of early modern locations from the geo-coordinates of modern administrative
boundaries, sites, and structures. Despite the Great Fire of 1666, subsequent rebuilding, Victorian expansion, and the
massive destruction from air raids during the second World War, London’s street layout,
administrative boundaries, and property lines have been remarkably stable. Changes to administrative boundaries are well documented, which means we can work
backwards from modern boundary maps if necessary. Sometimes building plans and street
surveys survive (such as Ralph Treswell’s property surveys; see Schofield). Archaeological finds in London are geo-referenced, which gives us corroborating
evidence for some locations (especially the footprint of structures now lost, such
as theatres). The following is a list of web resources that provide geo-coordinates
for some locations in early modern London:
London Archaeological Archive and Research Centre Online Catalogue (LAARC) LAARC is a database of site records from archaeological digs in London. Each site record
has been assigned geo-coordinates that correspond with the point where historical
evidence of the location was discovered by archaeologists. Site records are searchable
via the website’s home page. Note that even though it is possible to search by street
name, LAARC provides point-based geo-coordinates for archaeological finds under modern streets,
not line-based geo-coordinates for the early modern streets themselves. LAARC usefully lists all the scholarly articles and monographs about a particular dig,
from which we can derive further information.
Shakespearean London Theatres (ShaLT) ShaLT maps all the early modern London theatres and provides resources, maps, and suggested
walking tours. Each location (exclusively playhouses and related locations) has been
assigned geo-coordinates that define where the location existed in Shakespeare’s London
(defined as 1570s to 1642). Locations are indexed on the locations page. We have now added all of the ShaLT coordinates to our playhouse location files.
GeoNames
GeoNames is a global database of geo-coordinates that contains over 100 modern-day
locations in the City of London. Locations are searchable by toponym at the website’s
home page and visually via the website’s map widget. Note that GeoNames is a modern-day
gazetteer. Geo-coordinates for a modern-day location may not perfectly correspond
with the location’s early modern predecessor.
Locating London’s Past Locating London’s Past is a GIS interface that links various seventeenth- and eighteenth-century datasets
with a georectified version of John Rocque’s Survey of London, Westminster, and Southwark, 1746. Geo-coordinates are not visible to the user. However, Tim Hitchock (one of
the project directors) has kindly supplied MoEML with the project’s .KMZ files that contain geo-coordinates for streets and parishes.
MoEML team members may ask Janelle Jenstad for access to these files, which you can open and search in oXygen.
In many cases, you will be unable to find geo-coordinates for a location using the
resources listed in the previous section. When this happens, you must use your own
research on the location to infer its location on a modern-day, Google map of London.
The following sections describe how to extract geo-coordinates manually for user-selected
points, lines, and polygons using Vertexer—a Google Maps markup tool developed by Greg Newton at HCMC.
Vertexer is an open-source web application that allows users to draw points, lines,
and polygons onto a Google Maps widget with map, satellite, and terrain views. It
may be accessed via the following url: http://hcmc.uvic.ca/people/greg/maps/vertexer/?la=51.51&lo=-0.1&z=15&t=roadmap. The preceding url uses bookmarks to preset the application to zoom in and centre
on the City of London. You may navigate the map by dragging it with the white hand
cursor (
) or using the search field in the top-left corner of the screen. You may switch modes
between a traditional map view and satelite view of an area using the drop down menu
in the top-left corner.
A point consists of two geo-coordinates, a latitudinal and a longitudinal coordinate,
separated by a comma. We use points to infer the approximate location of buildings
and other topographical features that no longer exist in present-day London. To extract
geo-coordinates for a point in Vertexer, select the point marker (
from the toolbar in the top-right corner). Click on the map to produce geo-coordinates
for a point (i.e., the point where you click). Geo-coordinates will appear in a pop-up.
These coordinates may be copied to your clipboard and pasted into the TEI document
for the coordinates’ corresponding location.
For example, suppose that I want to extract geo-coordinates for St. Olave, Silver
Street (STOL4.xml). There is a present-day monument at the southeast corner of London
Wall and Noble Street that marks where the church once stood. By referencing this
monument, I can easily place a point marker on the former location of St. Olave, Silver
Street in Vertexer:
Notice that the geo-coordinates for the point marker (and, by association, St. Olave,
Silver Street) appear in the bottom half of the screen. They are as follows: 51.517297,-0.095127.
A line consists of at least two sets of latitudinal and longitudinal coordinates.
Regardless of how many sets of geo-coordinates make up a line, the first and last
set of coordinates will always be different. We use lines to trace present-day streets and other linear features that have early
modern equivalents (e.g., Carter Lane) as well as to infer, whenever possible, the
approximate paths of early modern streets and other linear features that no longer
exist. To extract geo-coordinates for a line in Vertexer, select the line marker (
) from the toolbar in the top-right corner. Click on the map to produce the starting
point in the line (i.e., the point where you click will be the starting point); click
on the map again to produce another point in the line. Repeat this process until
you have connected a series of points in the appropriate linear form. The geo-coordinates
for your line will appear in a pop-up. These coordinates may be copied to your clipboard
and pasted into the TEI document for the coordinates’ corresponding location.
For example, suppose that I want to extract geo-coordinates for Carter Lane (CART1.xml).
Carter Lane still exists in present-day London, so I can easily trace the present-day
Carter Lane in Vertexer:
Notice that the geo-coordinates for the line (and, by association, Carter Lane) appear
in the bottom half of the screen. They are as follows: 51.513361,-0.102725 51.513313,-0.102248 51.513291,-0.101983 51.513289,-0.101963 51.513283,-0.101892
51.513272,-0.101785 51.513258,-0.101681 51.51325,-0.101636 51.513148,-0.101284 51.513137,-0.101239
51.513126,-0.101197 51.513099,-0.101073 51.513041,-0.100525 51.51296,-0.100191 51.512924,-0.09914
51.512888,-0.098421 51.512883,-0.098297 51.512794,-0.09733 51.512796,-0.097315 51.512808,-0.097288
51.512822,-0.097272 51.51283,-0.097262 51.512852,-0.097245 51.51295,-0.097186 51.513033,-0.097205
Notice also that the various points along the line are marked with a white circle.
After you have finished drawing a line, you may edit its shape and geo-coordinates
by clicking on and moving these point markers. You may also right-click on any point
marker to delete it.
A polygon consists of at least three sets of latitudinal and longitudinal coordinates.
Regardless of how many sets of geo-coordinates make up a polygon, the first and last
set of coordinates will always be the same. We use polygons to trace present-day buildings and other polygonal features that
have early modern equivalents (e.g., St. Paul’s Cathedral, Goldsmiths’ Hall). We also
use polygons to trace early modern administrative boundaries of wards, parishes, neighbourhoods,
etc. To extract geo-coordinates for a polygon in Vertexer, select the polygon marker
(
) from the toolbar in the top-right corner. Click on the map to produce the starting
point of the polygon (i.e., the point where you click will be the starting point);
click on the map again to produce another point of the polygon. Repeat this process
until you have connected a series of points in the appropriate linear form. Make sure
that the first and last points of the polygon are the same. The geo-coordinates for
your polygon will appear in a pop-up. These coordinates may be copied to your clipboard
and pasted into the TEI document for the coordinates’ corresponding location.
For example, suppose that I want to extract geo-coordinates for St. Paul’s Cathedral
(STPA2.xml). St. Paul’s still exists in present-day London, so I can easily trace
the present-day St. Paul’s in Vertexer:
Notice that the geo-coordinates for the polygon (and, by association, St. Paul’s)
appear in the bottom half of the screen. They are as follows: 51.513412,-0.099565 51.513425,-0.099074 51.513375,-0.098548 51.513327,-0.098267 51.513405,-0.097975
51.513615,-0.097346 51.513829,-0.097254 51.514032,-0.097449 51.514108,-0.098133 51.514195,-0.098399
51.514088,-0.098687 51.513987,-0.099116 51.51393,-0.099637 51.513412,-0.099565
Notice also that the various points in the polygon are marked with a white circle.
After you have finished drawing a polygon, you may edit its shape and geo-coordinates
by clicking on and moving these point markers. You may also right-click on any point
marker to delete it.
Do toggle between the map view and the satellite view when drawing a polygon. Features
of a building or site can be clearer in one view than they are in the other. For example,
the map view of St. Paul’s Cathedral does not show clearly that the north and south
semi-circular features are gardens. The satellite view helps one determine the shape
of the structure, even though it is easier to trace the structure on the map view.
It is possible to edit a complex line or polygon even once it has been encoded inside
an existing locations document. To edit a pre-existing line or polygon, copy and paste
its geo coordinates (tagged using the <geo> element) into the New Shape field in the bottom-centre of the interface. Next, click on the Add shape to map button. The line or polygon will then appear on the map, where you may edit it by
moving and/or deleting its white point markers. You can then copy and paste the shape’s
edited geo coordinates back into the existing locations document.
Once you have retrieved geo-coordinates for a location, the next step is to encode
them in the location’s TEI file. Each TEI file for a location will have a <div> in its <body> that looks something like this:
<div type="placeInfo"> <head>St. Paul’s Cathedral</head> <listPlace> <place> <placeName>St. Paul’s Cathedral</placeName> <location> <geo><!-- Geographical coordinates will go here when available. --></geo> </location> </place> </listPlace> </div>
The comment indicates where the coordinates should go. Paste the coordinates inside
the <geo> tags, separating the latitudinal coordinates from the longitudinal coordinates with
a comma (,) and separating latitude-longitude coordinate pairs from each other with
a space ( ). It is vital that you DO NOT put a space after the comma between latitudinal and longitudinal coordinates. For
example, a geographical point should be encoded thus:
It is important that we remain transparent about the source of the geographic data
that we use and who has acquired it on behalf of MoEML. To this end, MoEML encodes source information and responsibility information for each set of geo-coordinates
(demarcated by the <location> tag) in a document.
To encode source information for a set of geo-coordinates, add a @source attribute to the <location> tag containing the coordinates. The value field associated with the @source attribute should contain
a mol:uri that points to the source’s @xml:id as it appears in BIBL1.xml (if the source has not yet been added to BIBL1.xml, add
it)
the http:// address from which the geo-coordinates derive (if applicable)
Separate the first and second value components with a single space character ( ).
If you used Vertexer to extract geo-coordinates, cite Vertexer (VERT3) as the source.
Do not include an http:// address in the @source value field when Vertexer is the source.
¶Encode Responsibility Information for Geo-coordinates
To encode responsibility information for a set of geo-coordinates, add a @resp attribute to the <location> tag containing the coordinates. The value field associated with the @resp attribute should contain a mol:uri that points to the @xml:id for the contributor who found the geo-coordinates. The following example presents
the geo-coordinates for Silver Street as sourced by Kim McLean-Fiander:
Note that the @resp attribute must occur in addition to the @source attribute (as previously described). Therefore, a set of geo-coordinates for Silver
Street sourced by Kim McLean-Fiander from Shakespearean London Theatres should be encoded thus:
We also encode responsibility information for geo-coordinates in responsibility statements
in the <teiHeader>. Each person who contributed geo-coordinates to a document should have their own
responsibility statement (tagged using the <respStmt> element) crediting him/her as a Geographic Information Specialist for the document. Use the molRelator code gis in the @ref value field associated with the <resp> element. The following responsibility statement serves as an example:
<respStmt> <resp ref="molresp:gis">Geographic Information Specialist<date when="2014"/></resp> <name ref="mol:JENS1">Janelle Jenstad</name> </respStmt>
Whenever possible, it is best practice to define a date range for geo-coordinates
(i.e., identify from when to when the location corresponded with the given geo-coordinates).
Refer to the source of the geo-coordinates as well secondary material about the geocoded
location to obtain relevant date information. To define the date range for a set of
geo-coordinates, add @notBefore-custom, @notAfter-custom, and @datingMethod attributes to the <location> element containing the geo-coordinates. For example,
Occasionally, you will encounter locations that existed in both early modern London
and present-day London. With a few exceptions, such locations will have moved — slightly
or significantly — from their early modern site. For example, St. Paul’s Cathedral
and Goldsmiths’ Hall have been rebuilt on the same sites but not with the same building
footprint. Most sites within the walls were rebuilt after the Great Fire of 1666.
The surviving streets might be truncated, blocked at one or both ends, or bisected.
The few surviving alleys and lanes have been truncated. We therefore supply today’s
date (i.e., the date you extracted the geo-coordinates) in lieu of a date range for
the present-day geo-coordinates. To define a present-day date for a set of geo-coordinates,
add @when and @datingMethod attributes to the "location" element containing the geo-coordinates. For example,
¶Encode Multiple Geo-coordinates for a Single Location
Locations in the MoEML document collection cannot always be represented using a single set of geo-coordinates.
There are many reasons why an encoder may choose to provide two or more sets of geo-coordinates
for a single location. For instance,
A location’s geo-coordinates may be discontinuous
A location’s geo-coordinates may change over time (due to moving, rebuilding, etc.)
Different sources may provide different geo-coordinates for the location
Multiple geo-coordinates can be encoded in a location document using one of two methods:
Method One: add two or more <geo> elements inside the document’s <location> element
Method Two: add two or more <location> elements inside the document’s <place> element, containing one or more <geo> element(s)
Use Method One if a location is discontinuous or if its geography is interrupted in any way. For
example, Abchurch Lane (ABCH1) is discontinuous because there is a jog where it encounters
King William Street. The encoder therefore supplies two <geo> elements, each containing one part of Abchurch Lane’s two-part geography, inside
a single <location> element nested inside the document’s <place> and <listPlace> elements. For example,
Use Method Two if a location has moved over time or if different sources provide different geo-coordinates
for the location. For example, Shakespearean London Theatres and The Museum of London Archaeological Archive both provide slightly different geo-coordinates for Silver Street. To represent both
sets of data concurrently, the encoder supplies two <location> elements (with different @source values), each containing one or more <geo> element(s), nested inside the document’s <place> and <listPlace> elements. For example,
Note that you may encounter situations or complexities when working with geographic
information that are not covered in this tutorial. In such instances, use your discretion
to decide which method of encoding is best suited to the geographic information you
are working with and flag the issue for discussion with Janelle and/or at a team meeting.
Complexities are an opportunity to refine our practices. As a general rule, use Method One (multiple <geo> tags) if a location is discontinuous or composed of two or more parts but is generally
regarded as a single geographic event in space and time; alternatively, use Method Two (multiple <location> tags) if a location is disputed or if it consists of multiple geographic events in
space and time. Remember that these two methods are not mutually exclusive: discontinuous
geographic coordinates may be included in one or more of the multiple geographic events
that make up a disputed, rebuilt, or moved location. Abchurch Lane (ABCH1) serves
as an example:
In certain instances, you may wish to add geo-coordinates to a non-location document.
For example, the encyclopedia article on the Revels Office (REVE2.xml) contains location information and geo-coordinates for the various sites of the Revels
Office between 1578 and 1642:
Seeing as non-location documents do not by default contain a <div> element with a @type value of "placeInfo", you will need to add such a <div> to the top of the non-location document. Nest <head>, <listPlace>, <place>, <placeName>, <location>, and <geo> elements inside the new <div> element thus:
<div type="placeInfo"> <head>[Name of Place]</head> <listPlace> <place> <placeName>[Name of Place]</placeName> <location> <geo><!-- [Insert geo-coordinates.] --></geo> </location> </place> </listPlace> </div>
Follow the instructions in the previous section to add content to the above template and, in doing so, encode geo-coordinates in
a non-location document.
References
Citation
Davies, Matthew, Tim
Hitchcock, and Robert Shoemaker, eds. Locating London’s Past. U of Hertfordshire, U of London, and U of
Sheffield. http://www.locatinglondon.org/.
Rocque, John. A Plan of the Cities of London and
Westminster, and Borough of Southwark with Contiguous Buildings. London:
Printed by John Rocque, 1746. Reprint. The A to Z of Georgian
London. Introduced by Ralph Hyde. London: London Topographical Society, 1982. [We cite by
index label thus: Rocque 15Db.]
Landels-Gruenewald, Tye, Martin D. Holmes, and Janelle Jenstad. Geocode MoEML Locations.The Map of Early Modern London, edited by Janelle Jenstad, U of Victoria, 26 Jun. 2020, mapoflondon.uvic.ca/geo.htm.
Chicago citation
Landels-Gruenewald, Tye, Martin D. Holmes, and Janelle Jenstad. Geocode MoEML Locations.The Map of Early Modern London. Ed. Janelle Jenstad. Victoria: University of Victoria. Accessed June 26, 2020. https://mapoflondon.uvic.ca/geo.htm.
APA citation
Landels-Gruenewald, T., Holmes, M. D., & Jenstad, J. 2020. Geocode MoEML Locations. In J. Jenstad (Ed), The Map of Early Modern London. Victoria: University of Victoria. Retrieved from https://mapoflondon.uvic.ca/geo.htm.
RIS file (for RefMan, EndNote etc.)
Provider: University of Victoria
Database: The Map of Early Modern London
Content: text/plain; charset="utf-8"
TY - ELEC
A1 - Landels-Gruenewald, Tye
A1 - Holmes, Martin
A1 - Jenstad, Janelle
ED - Jenstad, Janelle
T1 - Geocode MoEML Locations
T2 - The Map of Early Modern London
PY - 2020
DA - 2020/06/26
CY - Victoria
PB - University of Victoria
LA - English
UR - https://mapoflondon.uvic.ca/geo.htm
UR - https://mapoflondon.uvic.ca/xml/standalone/geo.xml
ER -
RefWorks
RT Web Page
SR Electronic(1)
A1 Landels-Gruenewald, Tye
A1 Holmes, Martin
A1 Jenstad, Janelle
A6 Jenstad, Janelle
T1 Geocode MoEML Locations
T2 The Map of Early Modern London
WP 2020
FD 2020/06/26
RD 2020/06/26
PP Victoria
PB University of Victoria
LA English
OL English
LK https://mapoflondon.uvic.ca/geo.htm
TEI citation
<bibl type="mla"><author><name ref="#LAND2"><surname>Landels-Gruenewald</surname>,
<forename>Tye</forename></name></author>, <author><name ref="#HOLM3"><forename>Martin</forename>
<forename>D.</forename> <surname>Holmes</surname></name></author>, and <author><name
ref="#JENS1"><forename>Janelle</forename> <surname>Jenstad</surname></name></author>.
<title level="a">Geocode <title level="m">MoEML</title> Locations</title>. <title
level="m">The Map of Early Modern London</title>, edited by <editor><name ref="#JENS1"><forename>Janelle</forename>
<surname>Jenstad</surname></name></editor>, <publisher>U of Victoria</publisher>,
<date when="2020-06-26">26 Jun. 2020</date>, <ref target="https://mapoflondon.uvic.ca/geo.htm">mapoflondon.uvic.ca/geo.htm</ref>.</bibl>
Junior Programmer, 2018-present. Tracey is a PhD candidate in the English Department
at
the University of Victoria. Her research focuses on Critical Technical Practice, more
specifically Algorhythmics. She is interested in how technologies communicate without
humans, affecting social and cultural environments in complex ways.
Programmer, 2018-present. Junior Programmer, 2015-2017. Research Assistant, 2014-2017.
Joey Takeda was a graduate student at the University of British Columbia in the Department
of English (Science and Technology research stream). He completed his BA honours in
English
(with a minor in Women’s Studies) at the University of Victoria in 2016. His primary
research interests included diasporic and indigenous Canadian and American literature,
critical theory, cultural studies, and the digital humanities.
Data Manager, 2015-2016. Research Assistant, 2013-2015. Tye completed his undergraduate
honours degree in English at the University of Victoria in 2015.
Director of Pedagogy and Outreach, 2015–present. Associate Project Director, 2015–present.
Assistant Project Director, 2013-2014. MoEML Research Fellow, 2013. Kim McLean-Fiander
comes
to The Map of Early Modern London from the Cultures of Knowledge
digital humanities project at the University of
Oxford, where she was the editor of Early Modern Letters Online, an open-access union
catalogue and editorial interface for correspondence from the sixteenth to eighteenth
centuries. She is currently Co-Director of a sister project to EMLO called Women’s Early Modern Letters Online (WEMLO). In the past, she held an internship with the
curator of manuscripts at the Folger Shakespeare
Library, completed a doctorate at Oxford on
paratext and early modern women writers, and worked a number of years for the Bodleian Libraries and as a freelance editor.
She has a passion for rare books and manuscripts as social and material artifacts,
and is
interested in the development of digital resources that will improve access to these
materials while ensuring their ongoing preservation and conservation. An avid traveler,
Kim
has always loved both London and maps, and so is particularly delighted to be able
to bring
her early modern scholarly expertise to bear on the MoEML project.
Janelle Jenstad is Associate Professor of English at the University of Victoria, Director
of The Map of Early Modern London, and PI of Linked Early Modern Drama Online. She has taught at Queen’s University, the Summer
Academy at the Stratford Festival, the University of Windsor, and the University of
Victoria. With Jennifer Roberts-Smith and Mark Kaethler, she co-edited Shakespeare’s Language in Digital Media (Routledge). She has prepared a documentary edition of John Stow’s A
Survey of London (1598 text) for MoEML and is currently editing The Merchant of Venice (with Stephen Wittek) and Heywood’s 2 If
You Know Not Me You Know Nobody for DRE. Her articles have appeared in Digital Humanities Quarterly, Renaissance and
Reformation,Journal of Medieval and Early Modern Studies,
Early Modern Literary Studies, Elizabethan
Theatre, Shakespeare Bulletin: A Journal of Performance
Criticism, and The Silver Society Journal. Her book
chapters have appeared (or will appear) in Institutional Culture in Early
Modern Society (Brill, 2004), Shakespeare, Language and the Stage,
The Fifth Wall: Approaches to Shakespeare from Criticism, Performance and Theatre
Studies (Arden/Thomson Learning, 2005), Approaches to Teaching
Othello (Modern Language Association, 2005), Performing Maternity
in Early Modern England (Ashgate, 2007), New Directions in the
Geohumanities: Art, Text, and History at the Edge of Place (Routledge, 2011), Early
Modern Studies and the Digital Turn (Iter, 2016), Teaching Early Modern
English Literature from the Archives (MLA, 2015), Placing Names:
Enriching and Integrating Gazetteers (Indiana, 2016), Making
Things and Drawing Boundaries (Minnesota, 2017), and Rethinking
Shakespeare’s Source Study: Audiences, Authors, and Digital Technologies
(Routledge, 2018).
Janelle Jenstad authored or edited the following items in MoEML’s bibliography:
Jenstad, Janelle. Building a Gazetteer for Early Modern London, 1550-1650.Placing Names. Ed. Merrick Lex Berman, Ruth
Mostern, and Humphrey Southall. Bloomington and
Indianapolis: Indiana UP, 2016. 129-145.
Jenstad, Janelle. The
Burse and the Merchant’s Purse: Coin, Credit, and the Nation in Heywood’s 2 If You Know Not Me You Know Nobody.The
Elizabethan Theatre XV. Ed. C.E. McGee and A.L.
Magnusson. Toronto: P.D. Meany, 2002. 181–202.
Print.
Jenstad, Janelle. The City Cannot Hold You: Social Conversion in the Goldsmith’s
Shop.Early Modern Literary Studies 8.2 (2002): 5.1–26..
Jenstad, Janelle. The Gouldesmythes Storehowse: Early Evidence for
Specialisation.The Silver Society Journal 10 (1998): 40–43.
Jenstad, Janelle. Lying-in Like a Countess: The Lisle Letters, the Cecil
Family, and A Chaste Maid in Cheapside.Journal of Medieval and Early Modern Studies 34 (2004): 373–403. doi:10.1215/10829636–34–2–373.
Jenstad, Janelle. Public
Glory, Private Gilt: The Goldsmiths’ Company and the Spectacle of Punishment.Institutional Culture in Early Modern Society. Ed.
Anne Goldgar and Robert Frost. Leiden: Brill, 2004. 191–217. Print.
Jenstad, Janelle. Smock
Secrets: Birth and Women’s Mysteries on the Early Modern Stage.Performing Maternity in Early Modern England. Ed. Katherine
Moncrief and Kathryn McPherson. Aldershot: Ashgate, 2007. 87–99. Print.
Jenstad, Janelle. Using
Early Modern Maps in Literary Studies: Views and Caveats from London.GeoHumanities: Art, History, Text at the Edge of Place. Ed.
Michael Dear, James Ketchum, Sarah
Luria, and Doug Richardson. London: Routledge, 2011. Print.
Stow, John. A SVRVAY OF
LONDON. Contayning the Originall, Antiquity, Increase, Moderne estate, and description
of that Citie, written in the yeare 1598. by Iohn Stow Citizen of London. Also an
Apologie (or defence) against the opinion of some men, concerning that Citie, the
greatnesse thereof. With an Appendix, containing in Latine, Libellum de situ &
nobilitate Londini: written by William Fitzstephen, in the raigne of Henry the
second. Ed. Janelle Jenstad and
the MoEML Team. MoEML. Transcribed. Web.
Programmer at the University of Victoria Humanities Computing and Media Centre (HCMC).
Martin ported the MOL project from its original PHP incarnation to a pure eXist database
implementation in the fall of 2011. Since then, he has been lead programmer on the
project
and has also been responsible for maintaining the project schemas. He was a co-applicant
on
MoEML’s 2012 SSHRC Insight Grant.
St. Paul’s Cathedral was—and remains—an important church in London. In 962, while London was occupied by the Danes, St. Paul’s monastery was burnt and raised anew. The
church survived the Norman conquest of 1066, but in 1087 it was burnt again.
An ambitious Bishop named Maurice took the opportunity to build a new St. Paul’s, even petitioning the king
to offer a piece of land belonging to one of his castles (Times 115). The building Maurice initiated would
become the cathedral of St. Paul’s
which survived until the Great Fire of London.
St. Paul’s Cathedral is mentioned in the following documents:
List documents mentioning Geocode MoEML Locations
