Jun Hee Park
College of Computing
Georgia Institute of Technology
Atlanta, GA, 30332-0280 USA jhpark@cc.gatech.edu
Unkyong Lee
College of Computing
Georgia Institute of Technology
Atlanta, GA, 30332-0280 USA uk.a.lee@gatech.edu
Motivation and Objectives
Widely available these days, GPS Navigation systems and electronic maps such as
Google Maps plays a significant role in helping users moving one place to another by providing detail maps or showing routes. Also the recent growth in mobile devices caused various mobile applications have boundless potentialities and indispensable to our lives. These technologies enabled users to access maps from wherever they want.
These maps, however, are created only for huge public area. Although some relatively small places such as theme parks, shopping malls, or large buildings would be better to have electronic maps, these places currently use board or paper maps.
The paper based maps often make users confused because they provide limited information – no sign of current position. Therefore having electronic maps for small particular area can be very useful to everyday people’s lives.
In this project, we proposed to build the mobile application name “Lost in KLAUS”, a prototype of Location-Based Service to help students to find their way to their destination without much of a hassle. Most students who have classes in the Klaus building have hard time finding their classrooms on the first day. This application will guide not only students to find their class rooms but also help visitors find their destination in Klaus building.
Related Work
Google Mobile Maps and Weybridge are electronic maps serviced on mobile phones.
Both of them are general world map to travel cities but they contain similar

functionalities required the Lost in Klaus system such as showing image maps, finding shortest paths, providing information related with each location, and input and output methods for hand-held devices. Google Mobile Maps is based on internet and
Weybridge is based on stand-alone application. The Lost in Klaus, the navigation system we propose, provides both methods for users.
Proposed Work
We propose the Lost in Klaus, a navigation system with interactive maps on handheld devices to guide to Klaus, a multi-story building. Users can use the Lost in
Klaus through the Web browser of their own device and also through setting up the application with Java virtual machine. The Lost in Klaus consists of 4 parts: construction of maps, shortest path searching, navigation, and providing extra information. z Construction of maps
The Lost in Klaus manages map information composed by nodes identifying every place of Klaus, connections among the nodes, and lengths (or weights) of the connections. The nodes include rooms as well as stairs, elevators, exits and other places which do not have numbers but are necessary for the maps. This map information will be mapping with 2D and 3D map images to show users routes.
Figure 1. Example of nodes map

z Shortest path searching
Users can search a location they want by entering a room number, a room name, a purpose, and so on. For an instance, users can input 2015 as a room number and input conference room as a purpose.
Dijkstra algorithm will be used to find shortest path. For faster searching, blocks each of which has some connected nodes will be constructed, and shortest path information from a block to another block will be stored and re-used without
Dijkstra algorithm. z
Navigation
The hand-held devices have smaller screen than computers and limited input methods, and effective UI is important. The Lost in Klaus will provide shortest path a user requests on map image by lines. Users can zoom in/out the maps, and browse it by clicking arrow keys (up, down, left and right). Menus to help navigation will be served.
In addition, it is also important to clearly show levels. Most of electronic maps are for a single story, but the map is for a multi-story building. The system shows not only the floor plan but also exterior perspective. Lines of each level will have separate colors to clearly show the path in a multiple story building.
Figure 2. Example of map images z Providing extra information
The Lost in Klaus can provide additional information and search method for it.
Additional information can be various. For example, room information such as position, purpose, name and capacity, and people information such as people list

of the lab (room) and who are staying in a certain room will be offered by RFID database.
For the system architecture side, the Lost in Klaus is mainly consist of 6 components and database having all information of every nodes and maps on a file system.
Following image shows the architecture of the system.
Figure 3. Components of Lost in Klaus
Because of the restriction and features of hand-held devices such as CPU, memory, and small screen, the system should guarantee performance on hand-held device, memory management, efficient display, and easy input/search methods.

Plan of Action
1 Week
•Feb 11 2008 - Feb 17 2008
•Read reference / Write Proposal
2 Week
•Feb 18 2008 - Feb 24 2008
•Construct map images, nodes and other resources
3 Week
•Feb 25 2008 - Mar 2 2008
•Design detail architecture, DB, and UIs
4-6 Week
•Mar 3 2008 - Mar 20 2008
•Implementation I (finding shortest path)
7-8 Week
•Mar 21 2008 - Mar 30 2008
•Implementation II (displaying image maps)
9 Week
•Mar 31 2008 - Apr 6 2008
•Implementation III (the other parts)
10 Week
•Apr 7 2008 - Apr 13 2008
•User test and debugging
11 Week
•Apr 14 2008 - Apr 20 2008
•Write up final documentation and prepare demo
12 Week
•Apr 21 2008 - Apr 27 2008
•project demo and deliverable
Evaluation and Testing method
Evaluation and testing for performance and UI will be done. z
Performance:
1. How fast to find the shortest path
2. Accuracy of the found shortest path
3. How fast to response image map requests z UI:
1. User test and survey

Deliverables
Deliverables include the following:
3. Final Report
Bibliography
[1] Maps for mobile phone http://vision.eng.shu.ac.uk/mediawiki/index.php/Maps_for_Mobile_Phones
[2] Google Mobile Map http://www.google.com/gmm