Warning: Constant FS_CHMOD_DIR already defined in /home/elizab17/public_html/wp-config.php on line 101

Warning: Constant FS_CHMOD_FILE already defined in /home/elizab17/public_html/wp-config.php on line 101

Warning: Constant FS_CHMOD_DIR already defined in /home/elizab17/public_html/wp-config.php on line 101

Warning: Constant FS_CHMOD_FILE already defined in /home/elizab17/public_html/wp-config.php on line 101

Warning: Cannot modify header information - headers already sent by (output started at /home/elizab17/public_html/wp-config.php:101) in /home/elizab17/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/elizab17/public_html/wp-config.php:101) in /home/elizab17/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/elizab17/public_html/wp-config.php:101) in /home/elizab17/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/elizab17/public_html/wp-config.php:101) in /home/elizab17/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/elizab17/public_html/wp-config.php:101) in /home/elizab17/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/elizab17/public_html/wp-config.php:101) in /home/elizab17/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/elizab17/public_html/wp-config.php:101) in /home/elizab17/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/elizab17/public_html/wp-config.php:101) in /home/elizab17/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831
{"id":84,"date":"2016-02-25T00:24:40","date_gmt":"2016-02-25T00:24:40","guid":{"rendered":"http:\/\/elizabethgrab.com\/?p=84"},"modified":"2018-03-20T19:32:02","modified_gmt":"2018-03-20T23:32:02","slug":"google-maps-as-a-means-of-enacting-digital-humanities","status":"publish","type":"post","link":"https:\/\/elizabethgrab.com\/digital-humanities\/google-maps-as-a-means-of-enacting-digital-humanities\/","title":{"rendered":"Google Maps as a means of enacting digital humanities"},"content":{"rendered":"

For our second assignment in JJ’s Digital Art History course, we created a map that would incorporate multiple layers and associated multimedia.\u00a0 For my map, the layers represent the places in which I’ve lived.\u00a0 The individual locations and routes represent oft frequented or well enjoyed locations.<\/p>\n

The England layer is far more detailed, with supplemental information from the addition of attributes to its data table (Link and Time period).\u00a0 It also holds more images and even a YouTube video (see the Bodleian Library pin).<\/p>\n

The only real trouble I encountered was the number of layers the map would accommodate.\u00a0 When trying to add another route, the option was greyed out, informing me that I’d reached my limit.\u00a0 Other than that, the application was primarily intuitive and allowed me the freedom to manipulate it as I wished.<\/p>\n

Post-publishing realization<\/em>: The map automatically adds photos associated with the location after the photos (and singular video) that I linked to it myself.\u00a0 I’m working to figure out how to disable these media that aren’t mine.<\/p>\n