Media 3 – Ghosts & Space – Brief 2
Jake Baldwin – s3435078
Shannon Briggs – s3400914
George Downing – s3435908
Imogen Hanrahan – s3378324
- Introduction
We are researching Google related apps for place/map making. This is to determine if and how we can use Google Maps to potentially create our own prototype app. In order to do this, we will be looking at current apps that use Global Positioning Systems to implement augmented space material, where users have virtual experiences based on their surroundings. As a result, we will need to have a sound understanding of what the term “augmented place” means.
We will also be researching laws surrounding the use of Google Maps and whether other app creators are able to use or build upon information already supplied. Furthermore, we will examine the limitations and issues that arise from companies compiling metadata.
Ideally, this research will provide us with inspiration for how we can go about creating an augmented reality app related to the Ghosts of RMIT Studio. For this reason, our group will also research the technicalities of actually building a smartphone app.
- Annotated Bibliography – Method of Citation: Harvard
Augmented Space (George)
Albanesius, C 2013, ‘Google’s location-based field trip app comes to iOS’, PC Mag, 7 March, viewed 16 March 2015, <http://www.pcmag.com/article2/0,2817,2416372,00.asp>.
In this article Albanesius writes about the release of Google’s Field Trip app for iOS. The author details the different features of the app and recounts her personal user experience. The article is useful for our research topic as it is an example of one type of app that uses information from Google Maps to create an interactive augmented space experience for users, based on their surroundings.
Chandra, S 2013, ‘Top 20 augmented reality apps for android and iphone/ipad users’, DeepKnowHow, 4 April, viewed 25 March 2015, <http://deepknowhow.com/2013/04/04/top-20-augmented-reality-apps-for-android-and-iphoneipad-users/>.
Chandra lists 20 successful and popular augmented reality apps and provides a brief summary of each one. This article is particularly useful for our research purposes as it provides example of apps that are successful and ideas to model our own potential app on.
Dvorak, JC 2012, ‘Google: world cartographers’, PC Mag, 10 December, viewed 15 March 2015, <http://www.pcmag.com/article2/0,2817,2413049,00.asp>.
Dvorak provides a brief account of Google’s advancements in relation to Maps. He writes about how they revolutionised Street View, and asks whether Google Maps will outpace the competition as Google Web Search has done. The author also discusses the gamification of Google’s augmented reality game Ingress, explaining how users are providing Google with valuable information as they play, allowing the company to improve their Maps services. The article is useful for our research topic in that it provides another example of an augmented reality app, while also showing how such an app is intentionally created to improve Google Maps’ accuracy and usability.
FitzGerald, E 2012, ‘Towards a theory of augmented place’, Bulletin of the Technical Committee on Learning Technology, vol. 14, no. 4, pp. 43-45.
FitzGerald aims to inspire more debate surrounding theories underpinning learning in augmented places. She provides a brief summary of a few current theories, and argues that they are lacking in their understanding of technology-enhanced augmented space environments. As it is a very short article, it is limited in it’s research and is therefore somewhat superficial. However, it is still useful as it provides concise summaries of various theoretical frameworks surrounding augmented place.
Hodson, H 2012, ‘Google’s ingress game is a gold mine for augmented reality’, New Scientist, vol. 216, no. 2893, p. 19.
Hodson recounts his experience playing Ingress, and examines how the app represents an advance towards accurate augmented reality. According to him, augmented reality (AR) is where real-world objects are annotated with a virtual layer of information displayed on the user’s smartphone camera. Similarly to Dvorak, Hodson contends that the record of where players wander while playing the game is a ‘data gold mine’ for Google. The article is useful because it explains in more detail how data collected from Ingress is contributing to improving augmented reality apps in the future, as it helps to fix accuracy issues.
Jacucci, G, Lemmela, S, Morrison, A, Mulloni, A, Oulasvirta, A, Peltonen, P, Regenbrecht, H & Schmalstieg, D 2011, ‘Collaborative use of mobile augmented reality with paper maps’, Computers & Graphics, vol. 35, no. 4, pp. 789-799.
The writers review data from two experiments where the app MapLens is used in small-group collaborative tasks. This app augments paper-based city maps and overlays digital information. The reason for these trials is that the authors claim little research has been done on augmented reality applications in real-settings. Their main findings were that groups chose to work together even when not necessary, and that collaboration is useful even with smaller mobile phones. These findings are useful for our research as they indicate the importance of collaborative use of AR (Augmented Reality) apps, which we will keep in mind if developing our own.
Manovich, L 2002, ‘The poetics of augmented space’, Manovich.net, viewed 13 March 2015, <http://manovich.net/content/04-projects/033-the-poetics-of-augmented-space/31_article_2002.pdf>.
In this essay, Manovich discusses how the dynamic between spatial form and information function differently in contemporary computer culture. He aims to re-conceptualize the concept of augmented space in a historical and cultural sphere as opposed to purely technological. In order to do this, Manovich uses examples of various practices such as cinema, art and vernacular architecture. His research focuses on assessing past technological advances in relation to Virtual Reality and how these contribute to creating augmented space. The essay is useful to our research topic as it outlines technologies that allow augmented space to exist: surveillance, cellspace and electronic displays. These technologies could all be useful in creating our own app.
Marzia, M 2011, ‘Augmented reality and iphone applications: narration, mobile devices and urban space’, in E Biserna & P Brown (eds), Cinema, Architecture, Dispositif, Campanotto Editore, Udine.
Marzia aims to underline the relation between mobile devices and Augmented Reality. She focuses on iPhone applications that create a geospatial experience by reshaping urban landscapes, using features that reveal the history of spaces surrounding users in the real world. The author identifies three iPhone applications that do this: Nearest Tube, Nearest Wiki and Cyclopedia. Her research draws on Manovich’s definition of augmented space. The essay will be useful for our own research as it provides more examples of current apps which create augmented space with the use of Google Maps, hopefully inspiring ideas for the type of app our studio could build.
Nield, D 2014, ‘Google plugs its field trip app into google now’, Digital Trends, 17 August, viewed 15 March 2015, <http://www.digitaltrends.com/mobile/google-plugs-field-trip-app-google-now/>.
Nield writes about the different functions of the Google app ‘Field Trip’. This is mainly useful to our research as it is an example of a successful app which locates points of interests for users based on their location.
Ritchie, R 2014, ‘Ingress, Google’s augmented reality game, hits iPhone and iPad’, iMore.com, 13 July, viewed 15 March 2015, <http://www.imore.com/ingress-googles-augmented-reality-game-hits-iphone-and-ipad>.
In this article, Ritchie addresses the issue of privacy in using Ingress. He contends that by playing the game, users are ‘paying with [their] personal data’ (p. x). However, he does not provide any evidence to support this claim. The article would be useful for our research only in that it reminds us to be mindful of privacy issues when designing an app that requires access to users’ location services.
Legalities of using Google Maps to create our own app (Shannon)
Brown, M 2006, Hacking Google Maps and Google Earth, Wiley Publishing, Indianapolis, IN, p.p 36-44.
Chapter 3 in Brown’s Hacking Google Maps and Google Earth helped me better understand the Google Maps API which is so commonly referred to in Google’s Geo Guidelines. API stands for Application Programming Interface and is based on a ‘very simple suite of classes that you use within a Javascript container, directly within an HTML.’ This chapter informs readers that in order to incorporate Google Maps into a web-based application one must adhere to Google Maps API Terms of Service and register with Google to obtain a ‘Web API key.’ The Google Maps API cannot be used without a key and will not work without it. Brown informs that the Google Maps API key must be referenced in every Google Maps application you create. This book is an important reference as it provides important information about the use of Google maps in app development and the legal requirements involved.
Chivers, T 2013, ‘The story of Google Maps’, Telegraph.co.uk, 4 June, viewed 25 March 2015, <http://www.telegraph.co.uk/technology/google/10090014/The-story-of-Google-Maps.html>.
Tom Chivers’ article ‘The story of Google Maps’ gives an overview of the history of Google Maps and its impact on society. The article provides little information of legal issues surrounding the use of google maps, however it is easy to read and provides a background that helps put the program into context. It is important to have an understanding of a program that is central to the development of our projects.
Clarke, K. (2015). Maps Mania. [online] Googlemapsmania.blogspot.com.au, viewed 27 Mar 2015, <http://googlemapsmania.blogspot.com.au>
Keir Clarke is the author of the blog Maps Mania. He posts updates about alternative mapping programs. This is a useful reference as it provides information on interactive mapping applications. There is little information on legal issues however the blog is updated regularly and provides current information on the latest interactive mapping programs.
DuVander, A 2010, Map scripting 101, No Starch Press, San Francisco, Calif.pp 1-45
I found chapters 1 and 3 to be useful in learning about the basics of mapping and geocoding. There was little information on legal requirements however this is an important reference that will be of assistance in the future. Chapter 1 covered mapping basics in simple terms. The language in this book is clear and concise and serves as a useful tool for beginners. Chapter 3 covers Geocoding and teaches readers how to take addresses, city names and post codes and turn them into latitude and longitude points.
Garrett, J 2005, Ajax: A New Approach to Web Applications, viewed 25 March 2015, <https://courses.cs.washington.edu/courses/cse490h/07sp/readings/ajax_adaptive_path.pdf>.
In this article, Garrett discusses Ajax applications such as Google Maps. The article focuses on the increasing use of Ajax and uses Google Maps as an example of its success in the web industry. This article has some relevance to our research in that it unpacks the programs Google Maps runs on but gives little information on building applications or legal issues involved.
Google.com.au 2015, Permissions – Google, viewed 25 March 2015, <http://www.google.com.au/permissions/geoguidelines.html>.
Google’s geo guidelines page provides valuable information on the legal requirements of using Google Maps in an application. It provides a terms of service specific to using Maps API that states the requirements of utilising Google Maps. This page is an essential reference point to any app developer incorporating Google Maps into their project. It provides a series of guidelines every user must adhere to in order to legally use the Maps API. The Geo Guidelines provide instructional information, vital to the development of any Map based application. This site has proven to be the most relevant to the topic of legal issues surrounding the usage of Google Maps in applications.
Hoetmer, K 2014, ‘A few updates to the Google Earth/Google Maps APIs Terms of Service’, weblog post, 12 December, Geo Developers Blog, viewed 25 March 2015, <http://googlegeodevelopers.blogspot.com.au/search?updated-max=2015-01-07T18:42:00-08:00&max-results=7>.
The Google Geo Developers blog is run by Google and covers all aspects of Google Maps API’s. It consists of updates on launches and case studies written by developers. While some of the entries were irrelevant to the research topic, many were educational and assisted me in better understanding the Maps API and its many functions. Google is constantly updating the Maps API, adding new features to create a more interactive experience for application users. These changes are posted on the Google Geo Developers blog which is regularly updated by contributors. One post in particular was of interest to me as it informed readers of updates made to the Google Maps/ Google Earth APIs Terms of Service. This entry written by Keith Hoetmer, product manager of Google Maps APIs, describes minor changes to the terms of service that would impact very few developers. However it is interesting to note that the Terms of Service is constantly being altered and updated, so is therefore worth checking regularly.
JISC Legal Information 2013, How to: Use Google Street View Legally in Your Resources, 8 October, viewed 25 March 2015, <http://www.jisclegal.ac.uk/ManageContent/ViewDetail/ID/3312/How-to-Use-Google-Street-View-Legally-in-Your-Resources.aspx>.
This article provided by JISC Legal Information gives legal advice on using Google Street View in an application. This information could be useful if we decided on incorporating a street view element into an app. Street view allows for a more virtual interactive experience and could be an effective tool for telling a story. The article provides useful advice and informs readers that they are able to incorporate Street View imagery into their project if the imagery comes directly from the Google Maps API or is embedded on your website using the HTML and URL provided on Google Maps.
Jeff, W 2014, ‘Google Maps usage policy enforcement’, JJW Design, 19 February, viewed 25 March 2015, <http://www.jjwdesign.com/google-maps-usage-policy-enforcement/>.
This article written by Jeff Waters, discusses alternative mapping solutions to Google Maps. He raises the issue that ‘aggressive’ changes to Google’s usage policy could see costs arising for businesses using Map APIs internally. Waters references OpenStreetMap, a collaborative project that creates a free editable map of the world. While he doesn’t find OpenStreetMap comparable to the effectiveness Google Maps he believes it is a cost effective alternative for businesses using the Google Map API internally.
Perry, M & Margoni, T 2010, ‘From music tracks to Google maps: who owns computer-generated works?’, Computer Law & Security Review, vol. 26, no. 6, pp. 621-629.
In volume 26 of Computer Law & Security Review, Perry and Margoni discuss the various approaches taken by common law in Canada and the United Kingdom in relation to copyright infringement and web-based applications. There is little mention of Google Maps, however it was beneficial to read of the seriousness of copyright infringement and be reminded of the importance of adhering to the Google MAps APIs terms of service.
Limitations and Privacy Issues (Imogen)
Basso, M 2002, ‘Advantages and disadvantages in a location-aware society’, Gartner, 25 July, viewed 20 March 2015, <https://www.gartner.com/doc/365155/advantages-disadvantages-locationaware-society>.
In this article, Basso discusses the use of location in conjunction with small mobile devices and associated benefits/issues with employing an individual’s personalised information, transactions and interactions. The author states the popularity of using such a service in Asian markets and predicts that any wireless device will become capable of sensing location with increasing accuracy and a useful tool to enterprises. As a society becomes a completely “location-aware” society, the author points out that although increased surveillance of mobile devices may offer security, privacy issues come into effect. This is relevant to our project as it clearly outlines security complications associated with MLS.
Bearman, N & Appleton, K 2012, ‘Using Google Maps to collect spatial responses in a survey environment’, Area, Vol. 44, no.2, pp. 160-169, viewed 21 March 2015, Royal Geographical Society.
This paper examines the use of Google Maps-based tools to collect spatial responses from participants during research surveys conducted via the internet. Google Maps is regularly used for presenting data to users, but it is less common to ask users to provide their own spatial information. The article discusses the context of the survey and how Google Maps can be related, issues surrounding the implementation of these tools, and how the data is then used. The authors also consider how this type of research can be recorded in a way that it can then be reproduced, and reflects on how researchers may employ similar methods in the future.
Flux, E 2014, ‘Google Maps has been tracking your every move, and there’s a website to prove it’, Junkee, viewed 20 March 2015, <http://junkee.com/google-maps-has-been-tracking-your-every-move-and-theres-a-website-to-prove-it/39639>.
Elizabeth Flux’s article on Junkee brings attention to Google Maps’ location history service and its continuous tracking without most smartphone users knowing or understanding. Flux shows that by logging into Google’s web service, a detailed map of every location your smartphone has stopped within the last month will appear. The article presents this matter in a negative way and plays on the security concerns of readers demonstrating popular culture’s influence on its audience in employing what may be a useful service.
Johnston, LR & Jensen, KL 2009, ‘Map-happy: a user-centred interface to library map collections via a Google Maps “mashup”’, Journal of Map & Geography Libraries: Advances in Geospatial Information, Collections & Archives, Vol. 5, No. 2, viewed 19 March 2015, Taylor & Francis Online.
This article by Johnston and Jensen discusses how providing users with access to cartographic materials found in libraries has been a constant challenge for map librarians. The authors describe how librarians at the University of Minnesota developed MapHappy, a “mashup” of their existing map records into a geospatial web app providing access to the print maps in their collections. The issue of missing or faulty map coordinates and aligning the interface design with user expectations are discussed. This project demonstrates how geospatial library records make accessible a wide range of data previously meaningless or invisible to users, something worth investigating for our research project.
Maron, M 2011, ‘We need to stop Google’s exploitation of open communities’, Brain Off: Building Digital Technology for Our Planet, 11 April, viewed 19 March 2015, <http://brainoff.com/weblog/2011/04/11/1635>.
Maron’s aim in this blog post is to raise awareness to Google’s exploitation of user-generated mapping where the company adopts open data community procedures yet maintains control of what should technically be a public resource. Although this post only serves to open negative discussion on Google’s practices, it brings to our attention the idea of user-generated street mapping and how we may wish to avoid Google Maps in order to retain rights to usage.
Meuli, G & Finn, C 2007, ‘Google: trust, choice, and privacy’, Ethica Publishing, viewed 19 March 2015, <http://www.ethicapublishing.com/ethical/3CH15.pdf>.
Meuli and Finn focus on the ethical issues in companies like Google capturing large amounts of users’ personal information from their web services such as Google Maps. They state that Google has overstepped the boundary of ethics and further discuss it in the sections “Data Merging” and “The Privacy Policy”. The authors’ work is relevant to ours as we must explore all limitations in employing Google Maps’ services when creating a hypothetical RMIT application.
Ross, N 2015, ‘What metadata retention looks like: prepare to be shocked’, Abc.net.au, 20 February, viewed 27 March 2015, <http://www.abc.net.au/technology/articles/2015/02/19/4183553.htm>.
In this article, Ross provides a link to users’ location history. The map shows how Google has been automatically recording users’ locations every 45 seconds and time stamping each coordinate. He writes about how the Government wants to store this information for at least two years for purposes of crime prevention. This is extremely useful for our research purposes as it is a current example of disputes over individual privacy and government access to metadata collected from Google Maps.
Small Business Magazine 2014, The Pros and Cons of Geo-Location Apps for Your Business, WaspBarcode, viewed 19 March 2015, <http://www.waspbarcode.com/buzz/pros-cons-geo-location-apps-business/>.
As stated by the title, the pros and cons of geo-location apps are briefly compared here in this online article. It offers different limitations to the pressing privacy issues and focuses more upon the downsides to using MLS in a business. It points out that web-based companies cannot participate as there is no real “location”, and that some app users may “abuse the system” by reaping rewards without visiting the business’ location. These are important points to consider when creating our own RMIT app but are likely not to hinder our progress.
Welinder, Y 2013, ‘Facing real-time identification in mobile apps & wearable computers’, Santa Clara Computer & High Technology Law Journal, Vol. 30, no. 1, p. 89(50), viewed 20 March 2015, State Library of Victoria.
Welinder broadly states that the use of face recognition technology in mobile apps challenges individuals’ ability to remain anonymous in public places, a process that is essential to a productive and democratic society. This article lays out face recognition apps and emerging responses to initial policy considerations. It argues that any regulation with respect to identification in real time should be technology neutral. Our project would take into consideration this point, leaving our users the ability to retain their private information safely.
Zhu, Y, Zhang, J & Meng, L 2008, ‘Ethical concerns of online geoinformation services’, Department of Cartography, Technische Universitat München, viewed 19 March 2015, <http://icaci.org/files/documents/ICC_proceedings/ICC2009/html/nonref/22_3.pdf>.
The authors of this article tell us that developer-centred web map services have now evolved into user-centred interactive map services. Companies such as Google and Yahoo Map have developed easy-to-use mapping platforms for users to add information and publish their new map services. Like many other articles, this paper discusses how such services can be intentionally or unintentionally misuse and focuses on the interactive map services and the associated ethical problems. Based on case studies in Munich, the paper analyses content provided by internet users. The ethical problems embedded in online spatial information services are categorized and their (potential) seriousness is indicated. Our project can make reference to these case studies when we need to draw upon outside data to create our “app”.
How to build a Google maps-based app (Jake)
Cheong, F, Cheong, C & Jie, F 2012, ‘Re-purposing Google Maps Visualisation for Teaching Logistics Systems’, Journal of Information Technology Education: Innovations in Practice, Vol. 11, RMIT University, Australia.
This journal article presents a case study of a program that has been designed, using Google Maps as a routing tool for logistics systems. It outlines the definitions of visualisation and notes it’s importance as a tool to help users understand the system better. It also explains how the system was taught to users, and how Google Maps works within this system. Users input addresses which are converted to coordinates for Google Maps to pinpoint on a map for the user to see. This article is a good example of how Google Maps can be implemented into a program, as well as details on how it was implemented and how it was received by the users including data on how effective the implementation was.
Dincer, A & Uraz, B 2013, ‘Introduction’, Google Maps API Javascript Cookbook, Packt Publishing, Birmingham, UK
This book provides an insightful and broad reference on the details of drawing on Google Maps using the Google Maps API with Javascript. The Introduction section offers some useful basic information on the technical limitations of the data such as the 25,000 map refreshes per user per day. Such information would prove valuable if coding for Google Maps with Javascript as the technical details would help guide the overall design process. It also provides some network based information which would be required if the final product interacts with the user online.
Erica, A 2010, ‘When Google Maps Gets it Wrong’, Maclean’s, Vol. 123, No. 46, p. 26
This article outlines an example of the automatic features of Google Maps, and where limitations in it’s automatic capacity lie. It details a case where the Google Maps software mislabelled land under the wrong territory, causing governments to request Google change the way the system had labelled it. This case study represents where the technical capability of the data can mislead, or be outright wrong. It is the sort of circumstance that a team should be made aware of during the design process, as to prevent any automatically generated errors in location labelling, or misdirecting users.
Google Developers website, ‘Adding a Google Map to your website’, Google Maps Tutorials, Google Developers website, viewed 23 March 2015, <https://developers.google.com/maps/tutorials/fundamentals/adding-a-google-map>
Google’s developer website provides information relating to the use of their products. This set of tutorials explains using simple instructions how to implement Google Maps into a website, providing precise coding instructions and explanations of each piece of code and why it is being used. It explains that only a text editor and a web browser is necessary to implement (albeit a simple version) of Google Maps, and that the only code required is HTML and Javascript. This page and the other tutorials all provide concise and simple instructions on interacting with and implementing Google Maps, as well as some tips on customising the consequent Maps display to better fit into a custom design scheme.
Francis, N 2012, ‘Collection of the Coolest Uses of the Google Maps API’, noupe.com, 22 March, viewed 24 March 2015, <http://www.noupe.com/development/collection-of-the-coolest-uses-of-the-google-maps-api.html>
This article from 2012 lists 10 uses of the Google Maps API to achieve different outcomes. Some include game type uses such as a tower defence type map where a user places virtual turrets on the map to prevent markers from travelling a route and reaching their destination. Another simpler app ‘AllTrails’ uses Google Maps to allow people to map and share hiking trails for other users to visit. An app made in England allows users to tag locations of crimes to help authorities pinpoint trouble areas, and allow users to avoid any particularly dangerous areas. This list of uses of the Google Maps API shows a wide variety of ways that the Maps can be implemented, some more creative and some more functional. It provides several good examples of what can be done with location data, and other aggregated data from outside of Google Maps.
Hoetmer, K 2012, ‘Building great websites and apps with the google maps API’, Google-latlong.blogspot.com, 3 October, viewed 15 March 2015, <http://google-latlong.blogspot.com.au/2012/10/building-great-websites-and-apps-with.html>.
This web page is a blog post by Ken Hoetmer, Product Manager for the Google Maps API (Application Programming Interface). The page is written to showcase the prominence of Google Maps as a way to augment apps and websites. It marks the launch of a website morethanamap.com that further showcase how Google Maps can be used as a part of a larger app, website, as well as a number of other niche uses such as data visualisation. Hoetmer uses the flight data in and out of Heathrow airport in London as an example of how the maps can be used as a way to demonstrate information. As a piece of research this web page is a prime example of how Google Maps can be incorporated into a prototype app, or as another option to demonstrate information or data in the spaces we are exploring.
Mullen, T 2011, Prototyping augmented reality, Wiley, New York, USA, viewed 15 March 2015, Ebook Library.
In this book by Tony Mullen the theoretical and technical aspects of Augmented Reality (AR) is explored, with a notable focus on the technical requirements to implement AR. Mullen describes AR as “a combination of technologies that enable real-time mixing of computer-generated content with live video displays. Later in the book Mullen goes into great details regarding skills and technologies required to create and implement AR, such as superimposing 3D models into live video footage. There is potential for this kind of AR technology to be used in parallel with Google Maps and with Mullen’s detailed description of implementation we can be more aware of how this is done, and how it is best taken out.
Map-embed.com, viewed 23 March 2015, <http://www.map-embed.com/>
This website is an automatic code generator that generates embed codes that can be used in website design and code to create a real time Google Maps window in the website. A privately owned website, it outlines some perks to using Google Maps such as the kinds of data available through Google Maps, and how Google makes it’s APIs available for free to the public. This website provides a very simple option for implementing Google Maps into a potential web page that avoids coding.
Nathoo, A 2012, ‘How to build a location-based hybrid mobile app with reverse geocoding’, Cross Platform App Dev Blog, 15 May, viewed 15 March 2015, <http://trigger.io/cross-platform-application-development-blog/2012/05/15/how-to-build-a-location-based-hybrid-mobile-app-with-reverse-geocoding/>.
This blog post is from a developer blog, written by Amir Nathoo. In his post Nathoo explores how he used Google Maps as a foundation for his location based wine rating app. He goes into the details of the coding behind the app and precisely how he built the app to draw from Google Maps then allow a user to create custom location tags complete with user generated photographs and ratings for the wine. This in depth blog post provides us with insight into the core of apps that use Google Maps and provide a clear piece of background information to base our other research on when looking at how Google Maps may interact with a prototype app or system.
W3Schools, ‘Google Maps Basics’, w3schools.com, viewed 26 March 2015, <http://www.w3schools.com/googleapi/google_maps_basic.asp>.
W3 Schools provides a wide range of tutorials and education on coding and IT related information through their website. This particular tutorial focuses on implementing Google Maps with detailed explanations of each section of code. The final product is a map embed that can be focused to start on a particular location, which for our case could be Melbourne city, or even closer, to focus in on what location we’re investigating. If we we’re to follow through and create an app or website this resource would be an invaluable way to put together the functions of the final product.
- Interview Findings
George
I spoke to Betty Sargeant, a children’s app developer and tutor at RMIT. She explained that she designs story apps for young children, however they do not include features which use any Google Maps technologies or augment space. When I asked her what the most difficult aspect of app development is, she said that animation, interaction design and testing are the most time-consuming, even if you have a sound understanding to start with.
Shannon
Keir Clarke is an online map developer. His blog, Google Maps Mania, posts updates on changes and developments in various mapping programs. He specialises in interactive maps and advised that programs other than Google Maps are better suited to creating a virtual experience. However he believes that if you are after a hassle free, cost effective method of incorporating maps into your application Google Maps is the answer.
- Body
Augmented Space (George)
According to Hodson (2012), augmented reality is where real-world objects are annotated with a virtual layer of information displayed on the user’s smartphone camera. Example of these apps include Google Field Trip, Google Sky Map, Ingress, Wikitude World Browser and Cyclopedia (Abanesius 2013, Chandra 2013, Marzia 2011). Research indicates that AR (Augmented Reality) apps are most successful when they encourage collaborative group participation (Jacucci et. al 2011). This is important to keep in mind if we are to develop our own app.
While most of these are free to use, there is skepticism as to what companies do with valuable information collected from maps-based apps which require access to users’ location services. Dvorak (2012) contends that Google’s Ingress was created for the sole purpose of improving their Maps’ accuracy by encouraging players to take photos of their surroundings and record their everyday journeys. Hodson (2012) similarly contends that this record is a ‘data gold mine’ for Google (p. 19), while Ritchie (2014) purports users are ‘paying with [their] personal data’ (p. x). This is a limitation we need to be aware of which we will research in greater depth.
Legalities of using Google Maps (Shannon)
Research shows that incorporating google maps into an application does not require explicit permission from Google. Google is unable to sign any letter or contract specifying that a project has permission to use their services. Those wishing to incorporate Google maps into their application must agree to the Maps/API Terms of Service which can be accessed on Google’s Geo Guidelines page. A series of restrictions on how you may use the maps are included in the terms and vary from no hiding of identity to no modification of search results. In order to utilise the Maps APIs the user cannot violate Google policies which include but are not limited to promoting or providing instructional information about illegal activities, defaming, abusing, stalking, harassing, or otherwise violating the legal rights of others, and restricting or inhibiting any other user from using or enjoying the Service or any other Google Services. In relation to content license, Google states that they claim no ownership over the user’s content and do not retain copyright or any other rights already held in the users content.
Limitations (Imogen)
In terms of limitations when creating a map-based application for either phones or on the web, the main issue expressed is that of privacy. As early as 2002, concern was raised over how surveillance and compilation of user data could be a breach of consumer security (Basso, 2002). In particular, we must take into account how ethical it is to use an application such as Google Maps when many believe they are the main violator of ethics in mobile location services. This is shown in both peer-reviewed articles such as the Santa Clara High Technology & Law Journal (2013) where facial-recognition is the issue, and throughout online culture such as Junkee (2015) and blogs (Maron, 2011). Both Junkee and BrainOff are examples of public users realising their privacy has been violated after using Google applications and appealing to a broader audience – if we were to employ Google Maps, a social media lashback like these could cripple appeal to our target market of RMIT students.
Other issues to become aware of are more technology based and more easily dealt with. Johnston and Jensen discuss the problems involved with integrating existing map APIs with Google Maps as experienced by the University of Minnesota (Johnston & Jensen, 2009). Creating an interface that satisfies users is difficult and it may be easy for us to model our own app off existing RMIT apps and similar. We may also run into trouble when creating incentives for our audience to use the app – the Small Business Magazine highlights how some consumers may “outsmart” the app should we decide to use a check-in reward feature (WaspBarcode, 2014). This challenges us to restrict proposed or create other incentives such as requiring users to use their location to prove they have visited the building site.
It seems that our main limitations are involved with ensuring our target market’s privacy stays a priority, as technological issues can be fixed as they appear. Our aim should be to create an open yet specific app that does not require much more than a user’s location to operate so that we do not experience trouble with Google Maps retaining other personal information.
How to build a Google Maps-based App (Jake)
The most prominent feature of Google Maps that we found was that Google heavily encourages the use of their maps, and is quick to show it’s capabilities (Hoetmer, K 2012). There are a wide array of resources available to learn how to properly implement Google Maps as a part of a larger system such as a website or app. Some websites offer the ability to generate code for embeds (map-embed.com), while others provide in depth tutorials (W3Schools) (Google developers website). Blogs and other informational websites provide user generated case studies on the implementation of Google Maps (Nathoo, A 2012) as well as more thorough studies of the implementation of full programs that include the use of Google Maps (Cheong, F, Cheong, C & Jie, F 2012). Searching for examples of apps that utilise the Google Maps API returns a huge number of examples (Francis, N 2012), showing the versatility and capabilities of Google Maps, not only as an online service, but as an API that can be repurposed and manipulated to suit a massive range of needs. During this research other avenues were considered including Augmented Reality technology and how it is implemented (Mullen, T 2011) the potential of which could include visualisation of information inside of Google Maps itself.
- How what we found out applies to the Ghost of RMIT Project (Conclusion)
After broadly researching app development, we focused on four specific areas. These were: augmented space, legal requirements in using Google Maps in an application, privacy issues related to location-based apps, and finally how to create our own app. Our focus was therefore on the technical aspects of the Ghosts of RMIT Project.
- Reference list
Albanesius, C 2013, ‘Google’s location-based field trip app comes to iOS’, PC Mag, 7 March, viewed 16 March 2015, <http://www.pcmag.com/article2/0,2817,2416372,00.asp>.
Basso, M 2002, ‘Advantages and disadvantages in a location-aware society’, Gartner, 25 July, viewed 20 March 2015, <https://www.gartner.com/doc/365155/advantages-disadvantages-locationaware-society>.
Bearman, N & Appleton, K 2012, ‘Using Google Maps to collect spatial responses in a survey environment’, Area, Vol. 44, no.2, pp. 160-169, viewed 21 March 2015, Royal Geographical Society.
Brown, M 2006, Hacking Google Maps and Google Earth, Wiley Publishing, Indianapolis, IN, p.p 36-44.
Chandra, S 2013, ‘Top 20 augmented reality apps for android and iphone/ipad users’, DeepKnowHow, 4 April, viewed 25 March 2015, <http://deepknowhow.com/2013/04/04/top-20-augmented-reality-apps-for-android-and-iphoneipad-users/>.
Cheong, F, Cheong, C & Jie, F 2012, ‘Re-purposing Google Maps Visualisation for Teaching Logistics Systems’, Journal of Information Technology Education: Innovations in Practice, Vol. 11, RMIT University, Australia.
Chivers, T 2013, ‘The story of Google Maps’, Telegraph.co.uk, 4 June, viewed 25 March 2015, <http://www.telegraph.co.uk/technology/google/10090014/The-story-of-Google-Maps.html>.
Clarke, K. (2015). Maps Mania. [online] Googlemapsmania.blogspot.com.au, viewed 27 Mar 2015, <http://googlemapsmania.blogspot.com.au>
Dincer, A & Uraz, B 2013, Google Maps JavaScript API cookbook, Packt Publishing, Birmingham, UK. pp 23-31.
DuVander, A 2010, Map scripting 101, No Starch Press, San Francisco, Calif.pp 1-45.
Dvorak, JC 2012, ‘Google: world cartographers’, PC Mag, 10 December, viewed 15 March 2015, <http://www.pcmag.com/article2/0,2817,2413049,00.asp>.
Erica, A 2010, ‘When Google Maps Gets it Wrong’, Maclean’s, Vol. 123, No. 46, p. 26.
FitzGerald, E 2012, ‘Towards a theory of augmented place’, Bulletin of the Technical Committee on Learning Technology, vol. 14, no. 4, pp. 43-45.
Flux, E 2014, ‘Google Maps has been tracking your every move, and there’s a website to prove it’, Junkee, viewed 20 March 2015, <http://junkee.com/google-maps-has-been-tracking-your-every-move-and-theres-a-website-to-prove-it/39639>.
Francis, N 2012, ‘Collection of the Coolest Uses of the Google Maps API’, noupe.com, 22 March, viewed 24 March 2015, <http://www.noupe.com/development/collection-of-the-coolest-uses-of-the-google-maps-api.html>.
Garrett, J 2005, Ajax: A New Approach to Web Applications, viewed 25 March 2015, <https://courses.cs.washington.edu/courses/cse490h/07sp/readings/ajax_adaptive_path.pdf>.
Google Developers website, ‘Adding a Google Map to your website’, Google Maps Tutorials, Google Developers website, viewed 23 March 2015, <https://developers.google.com/maps/tutorials/fundamentals/adding-a-google-map>.
Google.com.au 2015, Permissions – Google, viewed 25 March 2015, <http://www.google.com.au/permissions/geoguidelines.html>.
Hodson, H 2012, ‘Google’s ingress game is a gold mine for augmented reality’, New Scientist, vol. 216, no. 2893, p. 19.
Hoetmer, K 2012, ‘Building great websites and apps with the google maps API’, Google-latlong.blogspot.com, 3 October, viewed 15 March 2015, <http://google-latlong.blogspot.com.au/2012/10/building-great-websites-and-apps-with.html>.
Hoetmer, K 2014, ‘A few updates to the Google Earth/Google Maps APIs Terms of Service’, weblog post, 12 December, Geo Developers Blog, viewed 25 March 2015, <http://googlegeodevelopers.blogspot.com.au/search?updated-max=2015-01-07T18:42:00-08:00&max-results=7>.
Jacucci, G, Lemmela, S, Morrison, A, Mulloni, A, Oulasvirta, A, Peltonen, P, Regenbrecht, H & Schmalstieg, D 2011, ‘Collaborative use of mobile augmented reality with paper maps’, Computers & Graphics, vol. 35, no. 4, pp. 789-799.
Jeff, W 2014, ‘Google Maps usage policy enforcement’, JJW Design, 19 February, viewed 25 March 2015, <http://www.jjwdesign.com/google-maps-usage-policy-enforcement/>.
JISC Legal Information 2013, How to: Use Google Street View Legally in Your Resources, 8 October, viewed 25 March 2015, <http://www.jisclegal.ac.uk/ManageContent/ViewDetail/ID/3312/How-to-Use-Google-Street-View-Legally-in-Your-Resources.aspx>.
Johnston, LR & Jensen, KL 2009, ‘Map-happy: a user-centred interface to library map collections via a Google Maps “mashup”’, Journal of Map & Geography Libraries: Advances in Geospatial Information, Collections & Archives, Vol. 5, No. 2, viewed 19 March 2015, Taylor & Francis Online.
Manovich, L 2002, ‘The poetics of augmented space’, Manovich.net, viewed 13 March 2015, <http://manovich.net/content/04-projects/033-the-poetics-of-augmented-space/31_article_2002.pdf>.
Map-embed.com, viewed 23 March 2015, <http://www.map-embed.com/>.
Maron, M 2011, ‘We need to stop Google’s exploitation of open communities’, Brain Off: Building Digital Technology for Our Planet, 11 April, viewed 19 March 2015, <http://brainoff.com/weblog/2011/04/11/1635>.
Marzia, M 2011, ‘Augmented reality and iphone applications: narration, mobile devices and urban space’, in E Biserna & P Brown (eds), Cinema, Architecture, Dispositif, Campanotto Editore, Udine.
Meuli, G & Finn, C 2007, ‘Google: trust, choice, and privacy’, Ethica Publishing, viewed 19 March 2015, <http://www.ethicapublishing.com/ethical/3CH15.pdf>.
Mullen, T 2011, Prototyping augmented reality, Wiley, New York, USA, viewed 15 March 2015, Ebook Library.
Nathoo, A 2012, ‘How to build a location-based hybrid mobile app with reverse geocoding’, Cross Platform App Dev Blog, 15 May, viewed 15 March 2015, <http://trigger.io/cross-platform-application-development-blog/2012/05/15/how-to-build-a-location-based-hybrid-mobile-app-with-reverse-geocoding/>.
Nield, D 2014, ‘Google plugs its field trip app into google now’, Digital Trends, 17 August, viewed 15 March 2015, <http://www.digitaltrends.com/mobile/google-plugs-field-trip-app-google-now/>.
Perry, M & Margoni, T 2010, ‘From music tracks to Google maps: who owns computer-generated works?’, Computer Law & Security Review, vol. 26, no. 6, pp. 621-629.
Ritchie, R 2014, ‘Ingress, Google’s augmented reality game, hits iPhone and iPad’, iMore.com, 13 July, viewed 15 March 2015, <http://www.imore.com/ingress-googles-augmented-reality-game-hits-iphone-and-ipad>.
Ross, N 2015, ‘What metadata retention looks like: prepare to be shocked’, Abc.net.au, 20 February, viewed 27 March 2015, <http://www.abc.net.au/technology/articles/2015/02/19/4183553.htm>.
Small Business Magazine 2014, The Pros and Cons of Geo-Location Apps for Your Business, WaspBarcode, viewed 19 March 2015, <http://www.waspbarcode.com/buzz/pros-cons-geo-location-apps-business/>.
W3Schools, ‘Google Maps Basics’, w3schools.com, viewed 26 March 2015, <http://www.w3schools.com/googleapi/google_maps_basic.asp>.
Welinder, Y 2013, ‘Facing real-time identification in mobile apps & wearable computers’, Santa Clara Computer & High Technology Law Journal, Vol. 30, no. 1, p. 89(50), viewed 20 March 2015, State Library of Victoria.
Zhu, Y, Zhang, J & Meng, L 2008, ‘Ethical concerns of online geoinformation services’, Department of Cartography, Technische Universitat München, viewed 19 March 2015, <http://icaci.org/files/documents/ICC_proceedings/ICC2009/html/nonref/22_3.pdf>.
