View source for Mokomapper

From Openmoko

Jump to: navigation, search

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Administrators.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page:

Return to Mokomapper.

Personal tools

Introduction

This is the content of an email of Risto H. Kurppa on the mailing list

 I found mokomapper
 (http://tui.cvs.sourceforge.net/viewvc/tui/tui/mokomapper.py?view=markup)
 some months ago (=I didn't write it, Pavel did (CC'd this mail to him))
 and mentioned it in the thread. Someone requested some screenshots so
 here you are: http://kurppa.fi/freerunner/mokomapper/ The readme file
 also has some output log of the script. I think the output is not in
 valid OSM format because of the broken GPS connection (maybe, I don't
 know..).
 I don't know how to use the app or how to import the stuff to OSM but
 to me it looks like it really is going to the right direction. It
 allows you easily to pinpoint road to left, road to right, different
 types of roads, crossroads etc etc and I'd think you could add some
 more items there quite easily since it's a simple python script..
 So if there's anyone with some python skills, it'd be great to give
 some love to this script so we all could easily do OSM mapping with
 only FR around.
 To use:
 wget http://tui.cvs.sourceforge.net/viewvc/*checkout*/tui/tui/mokomapper.py?revision=1.4
 -O mokomapper.py
 chmod 755 mokomapper.py
 DISPLAY=:0 ./mokomapper.py

Ideas

 - we need some icons for each button to help finding the things
 - I think it is a good start, but why not ask for any osm mapper and try to redefine all the hierarchy. I think for this a tool as freemind is the best : easy and quick. I am not saying the hierarchy used is wrong, but I think we should take the chance to have a discussion on it while trying it