Resultados 1 al 5 de 5

Tema: Estimated time for navigation on TeleAtlas

  1. #1
    Fecha de ingreso
    06 Aug, 09
    Mensajes
    26

    Predeterminado Estimated time for navigation on TeleAtlas

    Hi, sorry for my english, i'm french.

    Running an EvadeoX60 based on compegps sotfware i was using NavTeq maps, with a very good estimated arrival time.
    I migrate to a Teleatlas map (10Q2), all estimated time are VERY optimistic.
    An exemple:
    yesterday from my home to a place in the center of Marseille i got :
    distance : 44km
    estimated time : 23mn
    that's 114km/h
    there no place where i can drive over 110, and at least 30% ot the route is limited to 50km/h

    How that's possible.

    I'm also running Twonav 2.3.1 on my Evadeo X60 (works fine except the standby mode with th upper button of the Evadeo)
    ans i made different test :
    NT-Q1 is Evadeo 2.1.10/NT-Q1 2008
    TA10Q2 is Twonav 2.3.1/TA10Q2
    ViaMichelin is a Web Calculator

    Martigues(13)-Yutz(57)
    NT-Q1 : 803km - 7h45
    TA10Q2 : 803km - 6h33
    Viamichelin : 804km - 7h08
    Normally 7h30

    Martigues(13) - Gap(05)
    NT-Q1 : 199km - 2h06
    TA10Q2 : 199km - 1h46
    Viamichelin : 200km - 2h03
    Normally 2h00

    Martigues(13) - Carnoux(13) (crossing of Marseille)
    NT-Q1 : 65km -0h49
    TA10Q2 : 63km - 0h35
    Viamichelin : 63km - 0h49
    Normally 0h45

    Can you explain me these difference ? And more the Navteq maps don(t speed limit for cities and many secondary roads)

    Great thanks

  2. #2
    Fecha de ingreso
    04 Mar, 08
    Ubicación
    Poble Nou - Freedom for P9
    Mensajes
    223

    Post Information

    Cita Iniciado por jcoillard Ver mensaje
    Hi, sorry for my english, i'm french.

    Running an EvadeoX60 based on compegps sotfware i was using NavTeq maps, with a very good estimated arrival time.
    I migrate to a Teleatlas map (10Q2), all estimated time are VERY optimistic.
    An exemple:
    yesterday from my home to a place in the center of Marseille i got :
    distance : 44km
    estimated time : 23mn
    that's 114km/h
    there no place where i can drive over 110, and at least 30% ot the route is limited to 50km/h

    How that's possible.

    I'm also running Twonav 2.3.1 on my Evadeo X60 (works fine except the standby mode with th upper button of the Evadeo)
    ans i made different test :
    NT-Q1 is Evadeo 2.1.10/NT-Q1 2008
    TA10Q2 is Twonav 2.3.1/TA10Q2
    ViaMichelin is a Web Calculator

    Martigues(13)-Yutz(57)
    NT-Q1 : 803km - 7h45
    TA10Q2 : 803km - 6h33
    Viamichelin : 804km - 7h08
    Normally 7h30

    Martigues(13) - Gap(05)
    NT-Q1 : 199km - 2h06
    TA10Q2 : 199km - 1h46
    Viamichelin : 200km - 2h03
    Normally 2h00

    Martigues(13) - Carnoux(13) (crossing of Marseille)
    NT-Q1 : 65km -0h49
    TA10Q2 : 63km - 0h35
    Viamichelin : 63km - 0h49
    Normally 0h45

    Can you explain me these difference ? And more the Navteq maps don(t speed limit for cities and many secondary roads)

    Great thanks

    Could you be so kindly to upload a waypoint with the starting points and finish points in order to reproduce it ?

    Regards
    --LUKhAcK--

  3. #3
    Fecha de ingreso
    06 Aug, 09
    Mensajes
    26

    Predeterminado

    Here is the content of a wpt file corresponding to the 1st case (44km in 23mn)

    B UTF-8
    G WGS 84
    U 1
    z 5.042684,43.275663,5.408751,43.405022
    W Martigues A 43.41160739ºN 5.04786607ºE 08-JUN-2011 15:07:02 35.732449
    w Waypoint,0,-1.0,16316664,248,1,39,,0.0,0,-1,0
    W Marseille_Pugette A 43.26911252ºN 5.40276591ºE 08-JUN-2011 15:07:59 12.844738
    w Waypoint,0,-1.0,16316664,248,1,39,,0.0,0,-1,0

  4. #4
    Fecha de ingreso
    10 Sep, 08
    Ubicación
    Darmstadt (Germany)
    Mensajes
    344

    Predeterminado

    Cita Iniciado por jcoillard Ver mensaje
    I migrate to a Teleatlas map (10Q2), all estimated time are VERY optimistic.
    My experience is the same.
    I compare it with other GPS Navigation systems, also using Teleatlas maps, the calculated times with TwoNav are always shorter.
    I think the problem is not the Teleatlas maps, it's the way how TwoNav calculate it.
    But I could also be wrong.


    @lukhash, in TwoNav I can assign average speed for car, biking and walking.
    Which effect does this adjustment have?
    - travel time ?
    - route ? (I don't think so)

    It would be nice, when the average speed would have an effect on the calculated route.
    With a car, a route using much as possible the motorway is faster.
    With a bike using a shorter route following small roads is mostly faster.

    ray
    www.melibokus-biker.de
    Anima+ 3.3.4, , Samsung S5 with TwoNav Android 3.3.4
    (old devices Aventura W.E. 3.1/OS 1.3.60R, Sportiva+ 3.0/OS 2.2.1, Garmin 60CSx, Magellan Meridian Platinum)
    CompeGPS Land 8.1.1 & 7.7.* (Win & Mac) running on Mac OS X using a virtual machine for Win XP
    dt. TwoNav-SubForum im Naviboard
    Perl-Script gpsconv.pl a Converter for Tracks and Waypoints (e.g. GPX, KML and CompeGPS, ...)

  5. #5
    Fecha de ingreso
    06 Aug, 09
    Mensajes
    26

    Predeterminado

    Cita Iniciado por ray Ver mensaje
    @lukhash, in TwoNav I can assign average speed for car, biking and walking.
    Which effect does this adjustment have?
    - travel time ?
    - route ? (I don't think so)

    It would be nice, when the average speed would have an effect on the calculated route.
    With a car, a route using much as possible the motorway is faster.
    With a bike using a shorter route following small roads is mostly faster.

    ray
    I tested with different average speed ... No change
    Notice that when i specify a speed, the selected is different :
    say 65 it takes 64
    say 85 it takes 82

Permisos de publicación

  • No puedes crear nuevos temas
  • No puedes responder temas
  • No puedes subir archivos adjuntos
  • No puedes editar tus mensajes
  •  


About us

    CompeGPS Team SL All rights reserved © 2012

Follow us on

Twitter Facebook youtube Google Plus Flickr