Re: [talk-ph] Car navigation using Garmin with OSM
maning sambale wrote, On Monday, 07 June, 2010 01:39 PM: I have been reviewing estimated time of arrival (ETA) for garmin gps routing. I noticed that as Sehested reported, the speed calculation is over-optimistic. Due to the absence of complete maxspeed data in PH streets, I think the reason they don't have maximum speed data is because there's no way anyone will ever reach it! I read somewhere that the average traffic speed in Makati is 12 km/h. Which means you might as well tag them all with Type 0. Suggesting a new slogan for Makati; Normal rules don't apply Jim PS. OK yes, I know that the max speed data is used to calculate the fastest possible time. Just having a bit of fun here. ___ talk-ph mailing list talk-ph@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ph
Re: [talk-ph] Car navigation using Garmin with OSM
Wrong suggestion more apt.. Rules don't apply The speeds should be set to the real speed limits by law not a vague Traffic flow limitation imposed by Traffic (Jam) Enforcers... If I do 30KM/H will my garmin later report speeding? 5KM per hour is walking speed, I do faster than that most of the time in Makati. (I walk everywhere in Makati..) On Monday 07 June 2010 2:16:51 pm Jim Morgan wrote: maning sambale wrote, On Monday, 07 June, 2010 01:39 PM: I have been reviewing estimated time of arrival (ETA) for garmin gps routing. I noticed that as Sehested reported, the speed calculation is over-optimistic. Due to the absence of complete maxspeed data in PH streets, I think the reason they don't have maximum speed data is because there's no way anyone will ever reach it! I read somewhere that the average traffic speed in Makati is 12 km/h. Which means you might as well tag them all with Type 0. Jim PS. OK yes, I know that the max speed data is used to calculate the fastest possible time. Just having a bit of fun here. ___ talk-ph mailing list talk-ph@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ph ___ talk-ph mailing list talk-ph@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ph
Re: [talk-ph] Car navigation using Garmin with OSM
On Mon, Jun 7, 2010 at 2:48 PM, Michael Cole colemic...@gmail.com wrote: (I walk everywhere in Makati..) And my cycling speed is faster than most primary/secondary roads in Marikina :) I agree that most of this speed limits isn't followed, but the default road_speed (in the osm-ph map) is very inaccurate. My route simulation along NLEX is 230 kph! This why I demoted all speed in the osm-ph garmin to below 90 kph (for now). -- cheers, maning -- Freedom is still the most radical idea of all -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ -- ___ talk-ph mailing list talk-ph@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ph
Re: [talk-ph] Car navigation using Garmin with OSM
Hi, Again apologies for somewhat off-topic garmin posts. I have been reviewing estimated time of arrival (ETA) for garmin gps routing. I noticed that as Sehested reported, the speed calculation is over-optimistic. Due to the absence of complete maxspeed data in PH streets, I have assigned default speed limits to streets in the garmin map (not in the osm database). I followed some of rally and ianlopez's notes. http://wiki.openstreetmap.org/wiki/User:Ianlopez1115/Philippine_Tagging Garminmaps has 8 speed levels: # 7No speed limit # 670 mph / 110 kmh # 560 mph / 90 kmh # 450 mph / 80 kmh # 335 mph / 60 kmh # 225 mph / 40 kmh # 115 mph / 20 kmh # 03 mph / 5 kmh I assigned the speed limits 0-5 to osm-ph roads. The assigned speed limits for each highway type are the following: highway=motorway road_speed=5 highway=motorway_link road_class=3 highway=trunk road_speed=4 highway=trunk_link road_speed=2 highway=* motorroad=yes road_speed=4 highway=primary road_speed=4 highway=primary_link road_speed=1 highway=secondary road_speed=3 highway=secondary_link road_speed=1 highway=tertiary road_speed=3 highway=tertiary_link road_speed=1 highway=minorroad_speed=2 highway=unclassified road_speed=2 highway=pedestrian area!=yes road_speed=0 highway=living_street road_speed=1 highway=residential road_speed=2 highway=bridleway road_speed=0 highway=byway road_speed=0 highway=service service=parking_aisle road_speed=1 highway=service road_speed=1 highway=cycleway road_speed=1 highway=footway road_speed=0 highway=path road_speed=1 highway=steps road_speed=0 highway=track road_speed=1 highway=unsurfaced road_speed=1 Another important note is when there is a traffic_signal, speed is reduced to one level down. My limited testing showed better time estimation. For garmin users, please test some more and report if ETA calculations are better or needs further improvement. On Sat, Jan 9, 2010 at 4:27 PM, riber101-...@yahoo.com wrote: Hi, I have now been using OSM to navigate around Metro Manila and a trip to Mindoro and have some experience to share: On several occasions Garmin tried to guide me through on way streets going counter flow The OSM maps keeps getting better and each time I find a missing oneway info I just add it when I get home, so next time I will get the proper routing. So that should take care of that problem. Some roads are not connected as having separate ending points Guess this is due to the editors we use that doesn't warn about this. When funny routings occur I make a note and correct the issue when I get back to the computer. So time will solve this as well. Garmin routing times are overly optimistic as typical speed in Manila is 15 km/h and 20-40 km/h on SLEX Garmin often routes through narrow streets rather that using dedicated through fares The main reason Garmin is unable to provide better routing is the lack of maxspeed info for most roads. I suggest to add the maxspeed info for all roads according to the traffic code RA4136 as follows: SPEED LIMIT Passengers Cars and Motorcycle Motor trucks and buses Open country roads, with no blinds corners not closely bordered by habitations. 80 km. per hour 50 km. per hour Through streets or boulevards, clear of traffic, with no blind corners, when so designated. 40 km. per hour 30 km. per hour City and municipal streets, with light traffic, when not designated through streets. 30 km. per hour 30 km. per hour Through crowded streets, approaching intersections at blind corners, passing school zones, passing other vehicles which are stationery, or for similar dangerous circumstances. 20 km. per hour 20 km. per hour Garmin is able to use the maxspeed info to calculate the fastest route and by this automatically select roads with the higher speed limits. So I will advocate that maxspeed is added to all roads in the Philippines. Until this happens Garmin will keep preferring roads WITHOUT speed limits as is thinks they are the fastest. Happy mapping Sehested ___ talk-ph mailing list talk-ph@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ph -- cheers, maning -- Freedom is still the most radical idea of all -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ -- ___ talk-ph mailing list talk-ph@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ph
Re: [talk-ph] Car navigation using Garmin with OSM
I am in favor of adding maxspeed to roads whenever it is shown on the ground either as street sign or a local legislation. However, I am wary with simply adding maxspeed following RA4136. I am thinking of adding these default speedlimits to the garmin map, however, I don't know how we can classify the roads according to the law's definition. Open country roads, with no blinds corners not closely bordered by habitations. Seems to vague for me. On Sat, Jan 9, 2010 at 4:27 PM, riber101-...@yahoo.com wrote: Hi, I have now been using OSM to navigate around Metro Manila and a trip to Mindoro and have some experience to share: On several occasions Garmin tried to guide me through on way streets going counter flow The OSM maps keeps getting better and each time I find a missing oneway info I just add it when I get home, so next time I will get the proper routing. So that should take care of that problem. Some roads are not connected as having separate ending points Guess this is due to the editors we use that doesn't warn about this. When funny routings occur I make a note and correct the issue when I get back to the computer. So time will solve this as well. Garmin routing times are overly optimistic as typical speed in Manila is 15 km/h and 20-40 km/h on SLEX Garmin often routes through narrow streets rather that using dedicated through fares The main reason Garmin is unable to provide better routing is the lack of maxspeed info for most roads. I suggest to add the maxspeed info for all roads according to the traffic code RA4136 as follows: SPEED LIMIT Passengers Cars and Motorcycle Motor trucks and buses Open country roads, with no blinds corners not closely bordered by habitations. 80 km. per hour 50 km. per hour Through streets or boulevards, clear of traffic, with no blind corners, when so designated. 40 km. per hour 30 km. per hour City and municipal streets, with light traffic, when not designated through streets. 30 km. per hour 30 km. per hour Through crowded streets, approaching intersections at blind corners, passing school zones, passing other vehicles which are stationery, or for similar dangerous circumstances. 20 km. per hour 20 km. per hour Garmin is able to use the maxspeed info to calculate the fastest route and by this automatically select roads with the higher speed limits. So I will advocate that maxspeed is added to all roads in the Philippines. Until this happens Garmin will keep preferring roads WITHOUT speed limits as is thinks they are the fastest. Happy mapping Sehested ___ talk-ph mailing list talk-ph@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ph -- cheers, maning -- Freedom is still the most radical idea of all -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ -- ___ talk-ph mailing list talk-ph@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ph
