1. Photographic Memory Ben Pomerenke Kenny Ortmann Adam Schade Brandon Berwald

2. Intro ► What is geospatial data? ► What is Photographic Memory? ► Why would someone want to use our program?

3. Market Analysis ● ● Panoramio ● ● Flickr

4. Requirements Analysis ► Functional Requirements  Import user pictures  Setup location information  Add pictures to trip, with the ability to edit these pictures  Package all information into KML  Upload KML to website for sharing

5. Requirements Analysis ► Non-functional Requirements  Easy to use interface  Efficient and reliable processing  Revolutionary way to share pictures

6. Photographic Memory: GUI

7. Photographic Memory: Window Controller ► Object that controls the different components of the system ► Used to give access to all widgets from each other

8. Photographic Memory: PSession ► Loads and saves data to and from XML source file ► Gives all other widgets access to this data ► Handles exporting KML files

9. Photographic Memory: Gallery Widget Load Folders Collapsible Folders Right click menu, with options having shortcuts

10. Photographic Memory: ViewerWidget ► EarthViewer ► Image Editor

11. Photographic Memory: OrganizerWidget Trips Locations Location Pictures

12. Dialogs ► Trip Manager ► Image Properties ► Map It!

13. Photographic Memory: Website ► Store trips ► Connect users together ► Ability to allow known users to view trips ► Allow for public trips ► Wiki and tutorials

14. Photographic Memory: Prototype ► Demonstration

15. Future Development ► Implement more image editing functionality ► Compress and package images ► Allow for quick upload to Website

16. Conclusion: Google My Maps How an image would be displayed in My Maps. (see above) Adding an image to My Maps. (see below)