Notices

12. Allow "mouse selection" in the "Download by Area" functionality.

Gnuite,

Maemo-mapper now seems to work even if my Globalstar BT is in static navigation mode.

There's a 'gps data valid' flag available in many of the nmea sentences. Why not use it instead of figuring out the validity of the fix by our self?

Please see this page for more: http://www.werple.net.au/~gnb/gps/nmea.html

Pekka

I'm having a strange problem using my Socket BT GPS with Maemo Mapper. When I use it with Maemo Mapper, it seems to leave the "Establishing GPS fix" window up forever, and the bar appears empty. It does put the dot at my correct location on the map, but it won't move from there.

Maemo Mapper v0.2.1 has been released to the masses!

Device-Installable .DEB File
Source Code

New Features:
* Added support for satellite map data.
* Added support to save last center location.
* Added support to specify announcement advance notice in Settings.
* Added estimate for number of maps to download with Download By Area.

Bugfixes:
* Force creation of the map cache directory (including parents).
* Fixed some locale-related bugs.
* Made the flite call safer, and the path is specifiable in Settings.
* Changed the look of the HildonControlbars in Settings a tad.
* Changed the way routes are followed to better support single-point, "point-of-interest"-style routes.
* Fixed bug in route-drawing.
* Fixed some bugs in download-by-route functionality.
* Trying some fixes for when the bluetooth connection mysteriously drops.
* Added some error-handling to NMEA parsing.
* Fixed some other minor, workaround-able bugs.
* Added some more comment documentation to the code.


The current priority-ordered TODO list, targeted for a future version of Maemo Mapper:
1. Support multiple map repositories between which you can dynamically switch. (If you need something like this now, take a look at mgedmin's repository-switcher scripts if you are reasonably command-line savvy.
2. Support for two new modes of GPS receiver connection: GPSD, and direct RFCOMM (via the Maemo Bluetooth Plugin).
3. Publicize subversion repository (it's current private to my LAN - if you would like to hack at the code now, PM me and we'll talk; I might be able to set you up with an account on my box that would allow you to access the repo for writing).
4. Add temporal data to track export.
5. Incorporate the GPX Driving Directions web service code directly into Maemo Mapper.
6. Make all drawing colors (circles and lines) configurable.
7. Localization (I'll need input from native speakers - volunteers?).
8. Add optional textual information (location, speed, heading, etc.) in upper-left corner of map.
9. Integrate with the dbus-based flite (if it actually works).
10. Integration with Maemo's Connectivity API's to auto-connect to the internet as necessary (like the web browser does).
11. Create official user documentation.
12. Allow "mouse selection" in the "Download by Area" functionality.
13. Replace the "Approaching Waypoint" prefix with a loud chime of some sort.

The next version of Maemo Mapper will be version 1.0 and will be the first version targeted for the new 2006 Operating System. If time permits, I will also release a backported v0.3 that will contain most of the same new features as v1.0 but will work with the old 2005 OS. If the new 2006 OS takes too long, it is possible that v0.3 will be released before v1.0.

Feel free to provide feedback and/or bug reports in this thread or via private message. If you like Maemo Mapper and would like to see it improve and/or show your appreciation, you can help me by providing suggestions for version 1.0 (in this forum) or by donating via credit card or PayPal (see the Maemo Mapper website for details).

Thanks to everyone who has contributed with bug reports, suggestions, and donations. Maemo Mapper is greatly improved because of you all, and I am confident that that trend will continue.

After having problems with disconnections from my bluetooth GPS receiver, and maemomapper v 0.1 and v0.2 lockups, I found the following:

I had been using the Bluetooth connection program from the Maemo wiki apps site to initialize connection to the GPS receiver prior to running MaemoMapper. Then, maemomapper would successfully find the receiver, but when either a power down from the display settings timout occurred, or just about anything else happened on the 770, Maemomapper would either lose connection to the receiver, or the program would lock up.
So, I just power cycled the 770 and started Maemomapper without invoking the Bluetooth program first, and everything works just fine!
Now, before I first ran the Bluetooth program, Maemomapper could not find the GPS, so I assume the bluetooth program did something to store pairing information which is subsequently used by Maemomapper.

Anyone else see this?

I've released Maemo Mapper v0.2.1 to address the "Invalid NMEA input from receiver!" message.

That's weird. I don't even use the Maemo Bluetooth Plugin, and Maemo Mapper finds my GPS receiver fine. Using Maemo Mapper in conjunction with the plugin may produce strange effects (unless you don't pair the receiver with the plugin). This should improve with the next version, which will hopefully work with the bluetooth plugin.