From Navit's Wiki
Revision as of 08:46, 4 April 2010 by Mifritscher (talk | contribs) (Issues)
Jump to: navigation, search

Basic Functions

Navit has the basic functions:

  • planning and viewing a route from a location A to B on the map. The location A and B are stored in the bookmarks. And navit calculates the root from A to B. Subprocesses are
    • Selecting location to start (location A -- enter A or select from bookmarks)
    • Selection destination (location B -- enter A or select from bookmarks)
    • Show selected vehicle -- optional: change selected vehicle to get the correct distances and travelling time for the trip.
    • Calculating the route and show user that navit is calculating the route.
    • Showing distance and time of the trip from A to B with selected vehicle
    • View trip on the map.
  • navigation with the support of navit from a location A to B. Subprocesses are
    • (unvisible for users) Set location to start as GPS locaction and do not overwrite location A for root planning.
    • Selection destination (location B -- enter A or select from bookmarks)
    • Press Button (Start) for navigation
    • Calculating route and users see that navit is calculating
    • Navigate from A to B
    • Stop Navigation (Stop Navigation Button - already implemented)
  • Settings of:
    • Select country (maybe not necessary, if navit.xml has a tag in the mapset definition where the country selection of e.g. a OpenStreetMap is already defined.
    • Select vehicle

With the current structure of the navit menu you can do all these things already, but the menu is not consistent to the main functions of navit. Furthermore the user does not see at moment on the main menu page what is the processing status of Navit. The main Informations on a Main Menu are (as options for changing):

  • Main Navit-Mode: (1) Navigation or (2) Route Planning
  • Starting Point A (e.g. Berlin with GPS Info) or current GPS location (depending on route planning or navigation mode)
  • Destination B (if set by user or stored and saved)
  • Distance and Time to destination (if calculated by Navit - like OSD in map)
  • Selected Vehicle for the trip.

Clicking on the shown infos will guide the user to that part of menu where they can change it.


while the enigne seems to be fine, in my opinion (Mifritscher 08:46, 4 April 2010 (UTC)) there are still many flaws in the usability:

  • the internal GUI isn't very useable - no symbols activivated (always need to go in the menu), zomming etc. is very frustating -> please make the gtk the standard!
  • add scrollbars for scrolling, zomming, detail-depth (both for streets and text,
  • slowiness - why is it so slow on a c2d with Intel x3100 running Ubuntu 10.4?
  • add subitems for the favorites like in the internal gui - show in map, set as position, target etc, delete it.
  • add a ruler for estimating distances etc.
  • add options for default zoom, show whole route
  • add a much simpler map style: high contrast, streets are only lines, no POIs - alternative: make this configurable during runtime (not via editing a xml-file...)
  • white streets on a yellow background aren't that readable
  • add items to the scrollbar: set as positon, set as target, save as favorite, show infos (street name!), which operate on the next point which is clicked on (on many cases, you have no right mousekey...)
  • sync route commandos and the map: by clicking a commando, show the regarding position on the card
  • add the possibility to save current views so sey can be reloaded later
  • in general: make it configurable via the gui, I don't want to feedle with the xml while I'm on the road...
  • add processbar for routing