tylerpierce (tylerpierce) wrote,
tylerpierce
tylerpierce

Look back at where you came from

My attempts to map my home range and frequent haunts took a good step forward this weekend. All my GPS data is now being extracted from the horrible, incomprehensible NMEA 0183 format into gpsbabel's "unified CSV" format, from whence the bits I particularly care about are migrated into a simple database.

I have about a million data points now. Some are likely of low quality; I haven't worried too much about that yet. I'm not logging altitude or heading, so some of the various "degraded" GPS modes might work for me.

The next step is to do something more useful with the normalized data. First I need to fill in some dead spaces; for example, if the GPS dies while I'm at work and I don't go out for another day, that would put all the accumulated time into the wrong location. The current best guess algorithm for that is to scan for large breaks in the time sequences that have measurable changes in distance, then prompt for human intervention with the details. If the last entry is arriving at work on a Tuesday morning, and the next is leaving home Wednesday morning, I can at least guess how long I usually remain at work and when I got home. I'll lose the transit points, which I consider inconsequential for this project.

Once I've accounted for those gaps, I'll put together a script that iterates across all the data points and comparing it to a list of defined places, adding up all the time that was spent within radius r of it. Once I have those values, I can feed everything into the Google Maps javascript I wrote and then I'll have some answers.

I may not like them, but I'll have them.
Subscribe
  • Post a new comment

    Error

    default userpic

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 2 comments