Custom Query (1067 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (49 - 51 of 1067)

Ticket Resolution Summary Owner Reporter
#68 fixed Navit goes into tight loop if gpsd socket is closed KaZeR mattcallow
Description when using gpsd (for example with gpsfake, but possibly with a real gps as well), if gpsd is stopped (and the socket closed) Navit does into an endless loop. This is beacuse it does not detect that the socket has closed.

Possible patch:
{{{
Index: vehicle/gpsd/vehicle_gpsd.c
===================================================================
RCS file: /cvsroot/navit/navit/src/vehicle/gpsd/vehicle_gpsd.c,v
retrieving revision 1.4
diff -u -r1.4 vehicle_gpsd.c
--- vehicle/gpsd/vehicle_gpsd.c 10 Jan 2008 17:56:33 -0000 1.4
+++ vehicle/gpsd/vehicle_gpsd.c 11 Jan 2008 04:26:19 -0000
@@ -85,8 +85,10 @@
} else
priv->gps = gps_open(source + 7, NULL);
g_free(source);
- if (!priv->gps)
+ if (!priv->gps) {
+ dbg(0, "gps_open failed\n");
return 0;
+ }
gps_query(priv->gps, "w+x\n");
gps_set_raw_hook(priv->gps, vehicle_gpsd_callback);
priv->iochan = g_io_channel_unix_new(priv->gps->gps_fd);
@@ -124,7 +126,12 @@
if (condition == G_IO_IN) {
if (priv->gps) {
vehicle_last = priv;
- gps_poll(priv->gps);
+ if (gps_poll(priv->gps)) {
+ dbg(0, "gps_poll failed\n");
+ vehicle_gpsd_close(priv);
+ vehicle_gpsd_open(priv);
+ }
+
}
return TRUE;
}
}}}

Would a retry mechanism be appropriate if gps_open fails ?
#75 fixed The voice message "Turn right/left NOW" comes too late somebody hafting
Description A navit conversation typically goes like this:
"Turn left soon"
"Turn left in 200 m"
"Turn left now"

("Soon" is wrong when driving in a city - "turn left in a while" is what it feels like.")
But that is just words.

The real problem is timing. I usually get the "turn left now" message in the middle of the intersection, I am already making the turn.

The message needs to come earlier, so the driver have time to react. Plus some time to make up for gps inaccuracy (and similiar map inaccuracy. Perhaps map inaccuracy needs to be a parameter in the xml file. Those with a good map don't want the messages too early, those with a bad map don't want to be told what turn they just missed half the time.)

The driver needs time to hear the entire message+reaction time. Message time vary with language, but perhaps it can be tested by timing the messages during compile? Message distance can then be computed from current speed.

Then there is the reaction time. The driver may need to brake from high speed, especially if it is a hard turn. Motorways usually don't need braking before the turn, but a good map should show the turn as a slow turn and tag the road as motorway anyway.
#76 fixed wrong import of dual-tagged OSM ways breaks routing cp15 grenzdebil@…
Description The osm2navit script imports ways tagged with both highway=some value and railway=some value as railways and thus prevents navit from using them for routing.

Tagging ways as highway and railway is commonly used in OSM when for example tram rails are located directly on a road and tram and car traffic share the same space.

The way osm2navit imports this breaks the routing in my town and I'm sure it does in many places.

One solution would be to create two different ways in the mapnik file for the street and the rails, so the information is not lost - the other one could be to simply consider such ways as a normal street.
Note: See TracQuery for help on using queries.