Notices

I'll have a look at it. The client side is not that mature yet as I'm more used to php than python.

@all: The server got many improvements. The settings and addresses are now in an extra file so that working with the svn gets easier (as I don't want my SQL settings on the SVN ).
Some easy Javascript Google Map is also now supported and also a page which creates the networked kml file for Google Earth which fetches the recent data from the server.
Source is at: https://garage.maemo.org/projects/pygeotrack/

By the way: At the moment this is more for the fun of "nearly" real-time tracking of the device (e.g. let the family know when I'm at home).
The lost-phone features will come later.

is it possible i'm not seeing the sql create file somewhere?
or how is the mysql db constructed?

I forgot about the file as I always create tables by hand.
I'll add one tomorrow. In short its an int called id, floats for lat, lon, bear and speed, datetime for date and varchar for the key. You can get the names from the .php files if you need it faster.

I'm working on a simular (but different purpose) solution with Phil. Phil created a client and i created a server (php and db). It allows you to track a route while on the go. The logged route can be plotted on Google maps (or any other service that supports KML).

We don't have any release yet but you can get all the current files from SVN:

https://garage.maemo.org/projects/livegpslog/

My searching skills have become very bad. I didn't find any of the projects named here before Your's, robbie, seems to be very similar. I also implemented tracks (either all points in the db or the last n ones) and it works good but if you enable the TimeStamps in the .kml real-time tracking doesn't work anymore (as Google Earth sets the timeline to the current view and won't display the new points by itself). If you are using TimeStamps (didn't check the source yet) did you find a solution to this?

EDIT: I just did a co on your svn. Seems you didn't make much with the kml yet, too. Just a line. So if you open the kml file it will display the whole track, right? This was one of my problems, I wanted the whole track but focus and zoom on the current position (just think you drive 130km on a motorway, then enter a city and someone wants to see where in the city you are, he sees the whole track and if he zooms in it will zoom back every 10 seconds to the whole track). The whole camera system in the .kml format is still a bit strange to me.

May I suggest a way to do both? If there is no network connection store the points locally with a time stamp. Upload them when there is a network connection. I know this adds quite a lot of work.

I'll have a look at it at some point.

By the way: I fixed the problem with the viewpoint when using track by using a LookAt for the whole file with the coordinates of the last position. This way Google Earth follows the device in real time but you can also see the track if you want.

You're right but that's on purpose. I'm mainly using it to display the progress while walking long distance marches (40 km and more a day) and people are not only curious where you are but also what progress i've made. They can zoom in any time.

I've also added a marker thats clickable and then shows you the kilometers i've walked. Google automatically zooms in on the marker once you've clicked.

If you want real-time (or near real time) tracking, you'll have to use ajax to add points and move the marker.

Edit: now i see that you solved it already

There are some apps that log the track locally and allows you to upload it later (i believe manually only).

Phil (the author of the client we're working on) added some caching of points. We store 10 points and then upload. Theoretically it allows you to store more points when not connected but i'm not sure if it's foolproof.

If you find one that does it automatically let us know. I tried manual upload today and it is too cumbersome.