I tried in the "add POI" window with this coordinate: N 55° 33.144 E 8° 6.278 with or without the degree character (which hasn't made it into illume's default keyboard, used ssh -X to test that). The SQL command executed by tGPS looks like this:
SQL: INSERT INTO poi (idmd5, lat, lon, visibility, cat, subcat, keywords, desc, price_range, extended_open) VALUES ('833501616702973561',0.000000,0.000000,1,1,0,'Leuchtturm 1','',3,0) So the lat/lon values silently fall to zero, I guess because of the characters instead of ciphers in the text input field. -- Marcel Am Donnerstag, 9. Juli 2009 08:30:49 schrieben Sie: > AFAIK, tangogps should accept the other formats happily if you enter > them correctly, I do not know if it works in all input fields, though. > For geocaching ( which is the main use of my Freerunner ) I added a > bunch of extras to tangogps waiting to be included - if you're > interested, check > > http://n2.nabble.com/tangogps-%2B-geocaching-(DL-link-inside)-td2983362 >.html > > Feel free to contact me with any specific questions, > > Stefan > > On Wed, Jul 8, 2009 at 11:55 PM, Marcel <tan...@googlemail.com> wrote: > > Hello, > > > > I'm using TGPS for geocaching. The coordinates always get listed as > > f.e. N 55° 33.218 E 008° 08.493 (WGS84 degrees and minutes) > > If I have to "build" the coordinates for the cache's second "stage" > > by hand, I only get these coordinates as reference, but TGPS needs > > WGS84 Decimal Degrees as POI coordinates. > > As a feature wish: Could someone please make TGPS understand degrees > > and minutes? :) > > > > -- > > Marcel (who hasn't even understood how to convert the two formats in > > an own program yet.... :/ ) > > > > _______________________________________________ > > Openmoko community mailing list > > community@lists.openmoko.org > > http://lists.openmoko.org/mailman/listinfo/community _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community