Maemo Mapper v1.0 for the 2006 OS - Page 10 - maemo.org

Active Topics

Maemo repository (12)
to Community by teroyk - 48 mins ago
Error after installing Leste on sdcard (18)
to Maemo 7 / Leste by Maemish - 1 day, 10 hrs ago
Maemo 20th Anniversary (4)
to Brainstorm by teroyk - 3 days, 5 hrs ago
Nokia Booklet 3G (RX-75) Drivers (64)
to Alternatives by teroyk - 3 days, 5 hrs ago
Porting apps to Leste (46)
to Maemo 7 / Leste by teroyk - 5 days, 8 hrs ago
more...

Page 10 of 39

Thread Tools

Ceklund	2006-07-10 , 02:09
Posts: 112 \| Thanked: 6 times \| Joined on Feb 2006	#91

Just finished your release notes... I am very curious about temporal track data... and wondered if you might provide a couple examples of how someone might use it... ie, what it is for.

Please forgive me if this is common knowledge... I didn't seem to get it... my fault.

Thanks, gnuite.

__________________

1 Gig Generic MMC, Sprint EV-DO for data(25-45 Kb/s d/l speeds), & Samsung A940: one GREAT phone!

Quote & Reply |

	gnuite	2006-07-10 , 12:56
	Posts: 1,245 \| Thanked: 421 times \| Joined on Dec 2005	#92

Originally Posted by Ceklund

Just finished your release notes... I am very curious about temporal track data... and wondered if you might provide a couple examples of how someone might use it... ie, what it is for.

It just means that each track point now that Maemo Mapper keeps track of now also has a timestamp with it. So now, when you Save a track, Maemo Mapper not only saves the coordinate data, but also the time at which you were at each coordinate.

Most commonly, it is used to "play back" a trip using special replay software. It can also be used to estimate average speed or total trip time (or time between any two points, etc.).

Quote & Reply |

Ceklund	2006-07-10 , 17:13
Posts: 112 \| Thanked: 6 times \| Joined on Feb 2006	#93

Okay, that makes sense, thanks...

gnuite, will you comment about post #89 (a few posts back)? If you have the time, that is.

Thank you, good sir.

__________________

1 Gig Generic MMC, Sprint EV-DO for data(25-45 Kb/s d/l speeds), & Samsung A940: one GREAT phone!

Quote & Reply |

armin	2006-07-10 , 18:02
Posts: 39 \| Thanked: 13 times \| Joined on May 2006 @ Bonn, Germany	#94

Originally Posted by gnuite

A quick google search yields this treasure trove of geocache-related scripts:

http://geo.rkkda.com/

I believe the geo-dist script is what you're looking for. They're general unix-compatible shell scripts - mostly (if not entirely) bash scripts.

Andrew Turner <ajturner AT highearthorbit DOT com> pointed me to this Ruby-Script:
http://highearthorbit.com/projects/geolocation/gpx.rb

Slightly modified variant (km instead of miles, output track segment length, workaround for a -0.000 rounding error leading to a sqrt-abort):
http://armin-warda.de/gpx.rb

Quote & Reply |

hallax	2006-07-10 , 18:44
Posts: 14 \| Thanked: 0 times \| Joined on Jul 2006	#95

Hi,

First, Gnuite, thanks for developing Mapper! I have been using it for a few days now when cruising in southern Finland and it works just great! Also I just upgraded to 1.1 and no problems there either. I use Nokia LD-3W for GPS.

Of course there are a few things I´m missing ;-)

1) Is there a way to download and save POI data? It would be great if I could download for example certain gas stations, stores and hotels in selected countries. I belive many of these companies provide their POI data in their websites, so it should be possible to save this for Mapper?

2) It would be great if I could create some fixed locations like home, work, etc... And before downloading a route, I could browse for fixed locations to be used as origin or destination.

3) Also it would be good if all the other POI locations downloaded (gas stations, hotels, etc. mentioned in the first chapter...) could be used as fixed locations.

4) I´m not sure how the lenght of the velocity vector is calculated. But it would be great if it would present the estimated distance travelled in next 30 seconds (or mayby configurable time for each zoom level?) with current speed.

These are just my ideas after using Mapper for a few days as an incar navigation system. See pics.

I also miss some other features but they have already been listed in the Mapper Garage site.

I think Mapper definitely already is quite usable. Of course there are some nice features more expensive and focused TomTom offers but this is a very good start. Keep up the good work!

- Hallax

Attached Images

Quote & Reply |

	gnuite	2006-07-10 , 20:02
	Posts: 1,245 \| Thanked: 421 times \| Joined on Dec 2005	#96

Originally Posted by Ceklund

1) I've noticed that I'm needing quite often now to find my way home from wherever I am, I wonder if you won't add a 'Home' function that gets our current location, puts our predefined 'home' address in automatically and brings up the green route line all with the touch of a button or something ike that? Route>'Home' ?

The "Download Route" dialog uses autocomplete based on previously entered sources and destinations, so that's a bit of a shortcut already. When POI is implemented, you'll also be able to select from a list of points of interest. Neither of these particularly addresses your requested functionality exactly, so I'll consider adding the concept of a "Home" location.

Originally Posted by Ceklund

2) Another idea I had was to offer a 'Swap' button near the windows we put in our start and end addresses inside of Route>Download?

Again, the autocomplete can be used to address this, but I'll consider saving the last used addresses. The swap button is a good idea regardless, so I'll definitely add that.

Originally Posted by Ceklund

3) I have several blocks of google maps where the image was just starting to download when my cell dropped the connection, and now those maps have gaps in them...literal black spots and zoomed big blocky cells, Maemo Mapper thinks it's already been totally downloaded, but it hasn't. It's frustrating to look at, the center of town where I use the most (naturally, heh)... I could delete my map folder and reload, but I spent too much time getting it all setup... all I'd ike is a 'force reload of this map page' feature... in case this happens, we can just fix it.

See Feature Request Tracker Item #25.

Quote & Reply |

	penguinbait	2006-07-11 , 01:43
	Posts: 3,096 \| Thanked: 1,525 times \| Joined on Jan 2006 @ Michigan, USA	#97

Is there any chance there would be an easy way to log all nmea output while mapper is running?

Quote & Reply |

	gnuite	2006-07-11 , 01:59
	Posts: 1,245 \| Thanked: 421 times \| Joined on Dec 2005	#98

Originally Posted by penguinbait

Is there any chance there would be an easy way to log all nmea output while mapper is running?

Not until GPSD is ported to the 2006 OS (is it?) and Maemo Mapper gets GPSD support (see Feature Request Tracker Item #8).

Edit: until then, there is at least one (rather ugly) workaround that I can think of (NOTE: I haven't tested this and I don't know if it will work. I'm not responsible for any damage this procedure may cause to you or your software/hardware):

1. Connect to the GPS receiver using rfcomm to, e.g., /dev/rfcomm5

2. Set up a "named pipe" called, e.g., "/tmp/my_pipe", by entering the following commands into an xterm (or create a script an run that):

Code:

mkfifo /tmp/my_pipe
tail -f /dev/rfcomm5 | tee /tmp/my_pipe >> /home/user/MyDocs/Documents/MyNMEA.txt

The script should "hang", waiting for input.

3. Use "/tmp/my_pipe" as your "Receiver MAC" in Maemo Mapper, utilizing its "undocumented" rfcomm support.

4. When you're done with Maemo Mapper, you can rm kill the script with ctrl-C or "kill", and remove /tmp/my_pipe, or you can keep them both around, leaving the "cat"/"tee" running in the background until the next time you run Maemo Mapper. You can even run the above script at startup if you always want it to be available, and set up a cool naming scheme based on the time of day or the number of NMEA files you've created.
(Note: tee will probably "queue up" the NMEA data from /dev/rfcomm5 until something (in this case, Maemo Mapper) reads it, so it's probably not a good idea to leave the GPS receiver on and Maemo Mapper off at the same time for a long period of time. It won't wreck your system, but it might cause the tee to crash, meaning you'll have to restart the script.)

Last edited by gnuite; 2006-07-11 at 02:40.

Quote & Reply |

	gnuite	2006-07-11 , 02:48
	Posts: 1,245 \| Thanked: 421 times \| Joined on Dec 2005	#99

Originally Posted by hallax

1) Is there a way to download and save POI data? It would be great if I could download for example certain gas stations, stores and hotels in selected countries. I belive many of these companies provide their POI data in their websites, so it should be possible to save this for Mapper?

Not yet - see Feature Request Track Item #22

Originally Posted by hallax

2) It would be great if I could create some fixed locations like home, work, etc... And before downloading a route, I could browse for fixed locations to be used as origin or destination.

3) Also it would be good if all the other POI locations downloaded (gas stations, hotels, etc. mentioned in the first chapter...) could be used as fixed locations.

When POI's come, you will be able to select them in the "Download Route" dialog as either a source or destination. Arbitrary numbers of "fixed locations" starts to turn into a POI set, so I don't think I'll provide any additional functionality specifically for "fixed locations" - just use a POI set (you will be able to load as many as you want).

Originally Posted by hallax

4) I´m not sure how the lenght of the velocity vector is calculated. But it would be great if it would present the estimated distance travelled in next 30 seconds (or mayby configurable time for each zoom level?) with current speed.

The length of the velocity vector is based on (surprise!) speed, so you can sort of use it to judge "distance travelled in next 30 seconds", but the ratio is fixed relative to the screen size, so you'd have to scale it based on your zoom level. I decided not to make it fixed relative to actual geographical distance because that would make it either invisible in the "very zoomed out" case or entirely too long in the "very zoomed in" case.