Custom Query (1067 matches)


Show under each result:

Results (19 - 21 of 1067)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Ticket Resolution Summary Owner Reporter
#582 Incomplete/Missing infos Distinguish between legal and routing speed / Add "maxspeed:practical" tag support KaZeR
Description As I understand currently "maxspeed" tag is used, which is "official speed limitation". In OSM there is also "maxspeed:practical" which is used to describe usual speed, which can be achieved on the way. It is widely used, when speed is limited due to poor road quality.
However it can be higher, than "maxspeed" if official limitation is small and everybody on that road drives faster, than allowed. This situation is quite usual too.
Actually, this tag is used when it is needed to adjust road graph to get correct routing, but there are no official limitations. So it should be used instead "maxspeed", where available.
#584 Incomplete/Missing infos No transparency with gtk graphics cp15
Description OSD transparency settings are not used when using gtk_drawing_area graphics. Navit is running on openmoko freerunner.
#603 Incomplete/Missing infos GPS augmentation in Navit KaZeR mvglasow (2)
Description This ticket is a result of splitting #567 into one ticket per issue.

Some time ago I passed through the area at (errors in OSM data were fixed afterwards) on the highway, eastbound lane. Shortly before, I had set Navit (build 3134, WinCE) to a destination in Milan, just off the highway.

I was in a tailback in front of the border, thus moving slowly. As I passed the point just east of the border where a local road goes underneath the highway, Navit determined that my position was on that road, just in the middle between the two highway lanes, and instructed me to turn around if possible.

A later analysis of OSM data revealed that neither the highway nor the local road had any layer/tunnel/bridge information, thus making it look almost like a level crossing - except for the fact that the ways do not have any points in common.

One key ingredient to the problem was certainly the erroneous OSM data (which has now been fixed at this spot); possible ways to deal with bad data will be discussed in a separate ticket.

The other source of problems is the apparent lack of GPS augmentation in Navit: The GPS signal is somewhat crude by design and may be a few meters off (the error is expressed by the DOP values, and even a low DOP does not guarantee an accurate reading as errors due to reflectors might go unnoticed).

A first approach to coping with that is "snap to roads". This mechanism reaches its limits when multiple roads are in "range". Here, we will need some more information. In the present case it might have helped to consider history information: if prior readings made it somewhat certain that the vehicle was following one particular road, then only those roads that can be reached from there are eligible for the "snap to roads" feature. That is: if the vehicle is traveling towards a bridge, it is highly unlikely that in the next moment it is following the road going underneath that bridge - it is almost certainly crossing the bridge.

Admittedly, GPS augmentation is a huge chapter and one could write a paper or even a book on this - I have been collecting a few ideas for some time, which I am planning to make available, so that we can discuss what makes sense to implement in Navit.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Note: See TracQuery for help on using queries.