What's this?

WhereBlogger is a tool for Android phones, for keeping a location-based journal.

WhereBlogger can automatically collect GPS points for you, or you can add them manually. When an internet connection is available, maps will be downloaded for each logged point, and you can annotate each point with a title and a longer description. The program aims to be kind to your phone's battery and does not require a data connection or switch the GPS on at random times, as both electricity and data can be scarce while traveling.

Everything recorded by WhereBlogger can be published online (to a blog of your choice), or exported to the SD-card and copied to your PC to use as you see fit.

You can download WhereBlogger from the Android market (or just view the listing here).

Sunday, October 11, 2009

WhereBlogger 0.9.1

Minor updates today:

  • Time zone handling is better now, the app will assume you keep the time-zone settings of your phone up-to-date and record those along with the GPS data for each point. Future versions should expose the time-zone offset for editing.
  • Points can now be marked as excursions ('Went right back'), which changes how the route is drawn in the KML file. Instead of the path continuing from an excursion point to the next, it returns to the last non-excursion point before continuing. For multi-point excursions, you are still going to need to re-add your 'base' when you return, if you want the route to be drawn correctly. The next feature makes that a bit less annoying...
  • Points can now be hidden. Hidden points won't show up in the trip view listing, and won't have (visible) placemarks in the generated KML files. There is a new Trip Op to hide all points with blank descriptions, so you don't have to edit each point by hand.
  • Cleaned up the JSON output a bit, the zoom field now has a sane name.
  • Added in-line help explaining excursion and hidden points to the point editor.


This is also the first on-the-fly database upgrade. Hopefully I got the code right and won't lose anyone's data. It worked fine on my phone anyway... :-)

No comments:

Post a Comment