New proposal

This past week I prepared a new proposal. I wanted to do a similar location-based mobile app, preferably one that uses the accelerometer. The proposal may be found at:

https://www.dropbox.com/s/9lfrr7ocj1mpfnc/ProjectPropsal-KevinShen-location_tracking.pdf

I agree with Mike that it is best to push this project to the spring semester.

Scaled back

After realizing my last idea was not feasible because it's impossible to have GPS accuracy within a only a few feet, I've decided to write a new proposal for a scaled back idea with a similar goal.

After reading more about the Google Location API (intro here, article describing some more capability here), a navigation app is still possible. Instead of drawing markers on a video feed, which requires accuracy within a few feet or computer vision work out of the scope of this project, I instead propose an app that alerts the user if they are deviating from the path to their intended destination.

This would be accomplished with the Location API's geofences, which allow an application to know if a user has crossed a threshold. Setting up multiple geofences on either side of a user's walking path and buzzing or playing a sound when the user crosses these fences would help the user stay in the right direction. I haven't played with the API enough to know the exact technical challenges, which will be outlined in a revised formal proposal.

This is especially useful for walking in urban areas at night, when stopping to use your phone for directions can be dangerous. This may also be useful for people with sight disabilities, or even normal users who are listening to music and prefer to hear walking directions through their headphones.

Pivoting

Since the last post, I have implemented reading raw sensor data from the phone. This was demoed during alpha reviews this past Tuesday.

One major problem that came up during alpha review was that GPS may be inaccurate to the point where location can only be known within a 30 foot radius. This is solved by some mapping applications by using wifi networks to increase location accuracy. Such GPS localization is out of scope for this project, and Dr. Badler suggested looking at other apps based on data from the accelerometer and other hardware sensors.

Currently I'm considering other applications that use the accelerometer in a creative way to try to come up with a new idea. Health and wellness apps like Sleep as Android, which measures movement when you place it on the bed next to you as you sleep, seem like a very useful application (and more interesting than games). 

Navigation APIs

Unfortunately, I wasn't able to make much progress this week. In my proposal, I suggested OpenStreetMaps as a possible alternative to Google Maps. After more digging, OpenStreetMaps only gives raw map data and does not publish a navigation API, so I will use the Google Maps Navigation API to get navigation points.

Development of the Android app is at the same place it is last week, but I should be able to meet my alpha review goals in time for my review on Tuesday.