Skip to content
Alexander Vdolainen edited this page Aug 25, 2016 · 1 revision

Welcome to the mapserver wiki!

Features:

  1. updates for map data (i.e. patching)
  2. all data (update chunks, map directory, maps and patches) will be signed
  3. maps and misc data will available via http, ftp (and via sxmp in future, see plans below)
  4. server will automatically updating the maps (guess once per week)

What to be stored on the server:

  1. Map directory structure:
    • region - file name - update list - latest available
  2. List of latest versions if maps
  3. Files with patches list
  4. Latest maps

What will be required to include in navit application itself:

  1. libmapdiff (to apply patches) (libz and libbz2 as well)
  2. libsxt (to verify signed packages, still thinking about that) (libcrypto as well)
  3. libcurl (to access http/ftp)
  4. some small pieces of code to deal with misc data (to determine updates available etc ...)
  5. GUI to manage maps (download, remove, update)

Plans:

  1. Add traffic information to navit, see below:
  • a) it should be secure and fast
  • b) user accounts required
  • c) visualization and data format - still not designed
  1. Add some social stuff like in waze
  2. a lot of other things

Currently:

  1. sign and verify works
  2. libmapdiff under development (just started today, spent some time with navit formats and compare)
  3. daemon is works, just required to describe tasks for it, and find a better way to sync with external processes
  4. map directory doesn't complete yet

Estimation:

couldn't spent a lot of time with that (contract job eats a lot of my time), hope somebody will join to this subproject.